Annotation Issues [Please report any annotation errors here, thanks!]

Hi,
Even though our group spent a lot of time and effort on creating the Spider dataset, there definitely exist some annotation errors. We would appreciate your input if you report your findings here. Our group will try our best to correct the errors in our next release.
Thanks for your interest!
Best,
Tao

SQL annotation errors: issue 23,
Schema errors: issue 17, issue 20

Hi, thanks again for providing this valuable resource.
Wanted to report some errors in the dev set:

NLQ: What is the name and capacity of the stadium  with the most concerts after 2013?. The resulting SQL query has >= 2014, but while technically correct, don't think it makes as much semantic sense as > 2013.
NLQ: What is the smallest weight of the car produced with 8 cylinders on 1974? The SQL query incorrectly references Cylinders = 4.
NLQ: What is the minimu weight of the car with 8 cylinders produced in 1974? Same as the previous one, and minimum is spelled incorrectly.
NLQ: Among the cars that do not have the minimum horsepower, what are the make ids and names of al those with less than 4 cylinders? Similar to 1, it should be < 4 in the SQL, not <= 3.
NLQ: List the name of teachers whose hometown is not "Little Lever Urban District". The SQL query condition is missing a t: little lever urban distric.
NLQ: What are the names of the teachers whose hometown is not "Little Lever Urban District"? same as above.
NLQ: What is the mobile phone number of the student named Timothy Ward? The actual database has the value Timmothy, as does the SQL query. (This is debatably incorrect.)
NLQ: What is the total population and average area of countries in the continent of North America whose area is bigger than 3000？ The question mark symbol uses a strange character for this one.
NLQ: Give the total population and average surface area corresponding to countries in Noth America that have a surface area greater than 3000. North America is spelled incorrectly.
NLQ: Return the names of cities that have a population between 160000 and 900000. The query incorrectly uses 90000 (missing a 0).

@chrisjbaik Thanks a lot!

There is a bug in the table of players in wta_1database.
The wta_1.sql file contains wrong contents on the first line which is :
"CRloser_rank_pointsEATE TABLE players("
If you run: "select * from players" or any other related to table players, you will get an error.

Do you plan to incorporate the annotation fixes in future data release? If so that would be great.
The dataset .zip file released on the website still contain the original errors.

Yes! We are planning to fix annotation errors and release Spider 2.0 by January 2020. Also, we will update the evaluation script. Thanks!

I love this dataset, however one big problem that the nlp community will have to face is that these questions seem to be created from somebody who actually knows SQL. The entire focus of translating natural language to SQL is for user to never have to know SQL in the first place. I am not trying to hate on this dataset, because I believe it to be the best dataset we currently have. All I am trying to say is that these queries are representative of people who may have prior knowledge of SQL.

NLQ: "How many acting statuses are there?"
SQL: "SELECT count(DISTINCT temporary_acting) FROM management"
I feel like there is some ambiguity here, it could be distinct or it could just be the total number

Hi!
I would like to inform you small inconsistency db_id = formula_1 table in tables.json,
The order of tables presented in "table_names" & "table_names_original" fields are different making in difficult to automatically match between them.
Thanks!

In the follow interaction(train.json):
NLQ:"How about the problems on which closure is authorized by him?"
SQL:"SELECT  FROM staff AS T1 JOIN problems AS T2 ON T1.staff_id = T2.closure_authorised_by_staff_id WHERE T1.staff_first_name = "Rylan" AND T1.staff_last_name = "Homenick""
NLQ:"List records of customers living in city Lockmanfurt."
SQL:"SELECT  FROM Customers AS T1 JOIN Addresses AS T2 ON T1.customer_address_id = T2.address_id WHERE T2.city = "Lockmanfurt";
The select part is null.

Hi
In dev dataset, I found that
QuestionA: What is the average and the maximum capacity of all stadiums ?
QuestionB: What is the average and maximum capacities for all stations ?
PS: The stadiums table has a column named "AVERAGE".
They are all annotated to the same SQL: SELECT avg(capacity) ,  max(capacity) FROM stadium.
I suppose that QuestionB is right, but the QuetionA should be annotated as select Average , max ( Capacity ) from stadium
Thanks!

@taoyds Hi, when will the spider 2.0 be released?
I notice that in prediction results, many cases were correct generated except they had a distinct format with the gold sql. In this way, the upper bound of spider 1.0 would be about 70~75 (maybe).
I am designing my model on spider 1.0 and prepare for IJCAL (ddl:1/22/2020). It's would be great to see spider 2.0 before this ddl.
Thanks,

adding issue #10 for the train.sql file which is still unfixed
for the question What is the description of the type of the company who concluded its contracts most recently?
the correct SQL should be SELECT T1.company_type FROM Third_Party_Companies AS T1 JOIN Maintenance_Contracts AS T2 ON T1.company_id  =  T2.maintenance_contract_company_id  ORDER BY T2.contract_end_date DESC LIMIT 1

Sorry for the delay! We finally corrected some annotation errors and label mismatches (not errors) in Spider dev and test sets (~4% of dev examples updated, click here for more details).  Thanks for your inputs!

Schema error: issue #53

@taoyds ygan already told about this problem in Apr 19, 2019. Please fix it.

As I didn't want to wait one more year for fixes to come I've already done everything by myself.
Spider Dataset from 06/07/2020 with fixed wta_1: https://drive.google.com/file/d/1m68AHHPC4pqyjT-Zmt-u8TRqdw5vp-U5/view
Fixed evaluation.py which is stable to decoding issues in wta_1 database and gives 1.0 accuracy, recall and F1 when dev_gold.sql are supposed to be gold and predicted labels simultaneously: https://github.com/CrafterKolyan/spider-fixed/blob/master/evaluation.py

After correction of Spider dataset there are now some strange markers in select clauses:
See the next example:
"select": [
                false,
                [
                    [
                        1,
                        [
                            0,
                            [
                                0,
                                "__stadium.capacity__",
                                false
                            ],
                            null
                        ]
                    ],
                    [
                        0,
                        [
                            0,
                            [
                                0,
                                "__stadium.average__",
                                false
                            ],
                            null
                        ]
                    ]
                ]
            ]

What are "__stadium.capacity__" and  "__stadium.average__"? There should be numbers of columns.
This can be found on the lines 1850-1878 of dev.json

See #56

See #57

See #58

In the train set, the NL question:
What are the first names of the faculty members playing both Canoeing and Kayaking?
The gold SQL is incorrect:
SELECT T1.lname FROM Faculty AS T1 JOIN Faculty_participates_in AS T2 ON T1.facID = T2.facID JOIN activity AS T3 ON T2.actid = T2.actid WHERE T3.activity_name = 'Canoeing' INTERSECT SELECT T1.lname FROM Faculty AS T1 JOIN Faculty_participates_in AS T2 ON T1.facID = T2.facID JOIN activity AS T3 ON T2.actid = T2.actid WHERE T3.activity_name = 'Kayaking'

Should be:
SELECT T1.fname FROM Faculty AS T1 JOIN Faculty_participates_in AS T2 ON T1.facID = T2.facID JOIN activity AS T3 ON T2.actid = T3.actid WHERE T3.activity_name = 'Canoeing' INTERSECT SELECT T1.lname FROM Faculty AS T1 JOIN Faculty_participates_in AS T2 ON T1.facID = T2.facID JOIN activity AS T3 ON T2.actid = T3.actid WHERE T3.activity_name = 'Kayaking'

a few unexpected table names found in tables.json. e.g. sqlite_sequence table in world_1 database in tables.json.
credits to Pedro

See #70

As I didn't want to wait one more year for fixes to come I've already done everything by myself.
Spider Dataset from 06/07/2020 with fixed wta_1: https://drive.google.com/file/d/1m68AHHPC4pqyjT-Zmt-u8TRqdw5vp-U5/view
Fixed evaluation.py which is stable to decoding issues in wta_1 database and gives 1.0 accuracy, recall and F1 when dev_gold.sql are supposed to be gold and predicted labels simultaneously: https://github.com/CrafterKolyan/spider-fixed/blob/master/evaluation.py

#75  Can you please look into it?

Tables.json > "useracct" should be "user account"


UI Configuration Help

Hello, a new Hygieia user,
Following tis documentation: https://hygieia.github.io/Hygieia/ui.html, I can I select custom feature for  the dashboard.
Can I please get some help

hello, you can close this issue, I figured it out, I see my UI working,


Failure binding .framework with cocoapod dependencies

I'm trying to generate bindings for a third party framework (iProov.framework, https://github.com/iProov/ios). This library was written in Swift en has three cocoapods dependencies which are specified in the iProov.podspec file. The library works fine in a XCode project. I need C# bindings for use in a Xamarin iOS project.
Steps:

I have cloned the repo https://github.com/iProov/ios to a local folder.
I installed objectivesharpie-3.4.47.pkg
In the Terminal within the repo folder, I executed the following command:
sharpie bind -sdk iphoneos13.2 -framework iProov.framework

This results in the following errors:
./iProov.framework/Headers/iProov-Swift.h:189:9: fatal error: module 'SocketIO'
not found
@import SocketIO;
/private/var/folders/pz/qrnhtw956h319sp7v16jl6h00000gn/T/com.xamarin.ObjectiveSharpie/95b1763679444344a1bff1e3f2841d1f.h:1:9: fatal error:
     could not build module 'iProov'
@import iProov;

I tried a very lot more with pod init/install, sharpie pod init, created a static library xcode project, etc. but without success.

@deelw You need to pass dependency frameworks/libraries paths to clang on sharpie so it can resolve third-parties imports. e.g:
sharpie bind -sdk iphoneos13.2 -framework iProov.framework -c -Fpath/to/dependency1/folder -Fpath/to/dependency2/folder
or you can point to the Headers folder of the framework/library:
sharpie bind -sdk iphoneos13.2 -framework iProov.framework -c -Ipath/to/dependency1/Foo1.framework/Headers -Ipath/to/dependency2/Headers
You can play with -F and -I. Hope this helps you.

@SotoiGhost I have done and played with -F and -I but without success.
I referenced the dependency folders and subfolders of a pod install of the dependencies, including
KeychainAccess 3.2.0, Socket.IO-Client-Swift 15.1.0, SwiftyJSON 4.0.0 and Starscream 3.1
Because that did not solve my problem, I also downloaded the complete git repos of the dependencies and built the .framework files and referenced the path as a sharpie command (clang) -F parameter. I could not compile Socket.IO-Client-Swift succesfully because module Starscream not found while I did make a podfile including pod 'Starscream', '~> 3.1' and succesfully did run pod install. I also created .m files referencing #import <ProductName/ProductModuleName-Swift.h>
I tried a lot more, and also consulted colleges, without success.. I hope you would try to create the bindings yourself? Is it impossible or am I doing something wrong?

@deelw I think I made it work. Here's a zip that contains files that bind iProov using sharpie. You will need to install cocoapods-rome to make it work.
After you install cocoapods-rome. Just unzip the attached zip and run make in the command line.
Hope this helps you.
iProov.zip

@SotoiGhost Yes, it works!! Thanks you very much for your help!

Yw @deelw! Glad that I could help. Closing this issue now. Best!


Outfunnel destination

Proposed changes
Added documentation for Outfunnel destination
Merge timing

ASAP once approved

Thanks for the submission, @tammesalu!
I've created #4430 to deploy this today, as we needed to push some updates and your org did not allow it.


Videos.

Any option for adding videos onto a site, or is instafeed just for images?

https://github.com/evejweinberg/instafeed.js/commit/e370f7a294f1f0a10de28b49883a7a4faed1a088
It only works for standard_resolution for now, but you can access the video variable in the template and change width/height:
template: ''

Is {{video}} no longer supported? It doesn't seem to be pulling in the links to videos from feeds for me and it's not mentioned in the documentation.

@alifeinbinary - is {{model.videos.standard_resolution.url}} or {{model.videos.low_bandwidth.url}} still working for you? I haven't been able to get either to work in my filter function that gets thrown into my template.

@laurelstreng I'm using {{link}}. Check out this Gist to see how I made it work. https://gist.github.com/alifeinbinary/d2738575bdce3358b24016b9f0f84d09


How to use a same session_id with multi script on ruby

Appium On Ruby
1. demo script file
test_app.rb
...
opts = {
      caps: {
        session_id: "87504a5f-fa9e-44c0-bc24-6d4c40d39616",
        platformName: :android,
        deviceName: client,
        udid: client,
        app: File.expand_path('../../apks/test_app.apk', __FILE__),
        :noReset => 'true',
        appActivity: 'xxxxxx',
        appPackage: 'xxxxx',
        unicodeKeyboard: 'true',
        resetKeyboard: 'true'
      },
      appium_lib: {
        export_session: true,
        wait_timeout: 30000,
        wait_interval: 1,
        newCommandTimeout: 3000,
        appium_port: 4723,
        server_url: 'http://<IP_ADDRESS>:4723/wd/hub',
        debug: false,
        sauce_username: nil,
        sauce_access_key: nil
      }
    }
driver = Appium::Driver.new(opts)
driver.start_driver

2. I begin run script file
 ruby test_app.rb

3. how to use session_id of step 2 session
I can get session_id by driver
session_id = driver.session_id
or
get session info with browser
http://<IP_ADDRESS>:4723/wd/hub/session/:session_id

but I look source code of appium:
 # Creates a new global driver and quits the old one if it exists.
    #
    # @return [Selenium::WebDriver] the new global driver
    def start_driver
      @client ||= Selenium::WebDriver::Remote::Http::Default.new
      @client.timeout = 999_999

      begin
        driver_quit
        @driver = Selenium::WebDriver.for :remote, http_client: @client, desired_capabilities: @caps, url: server_url
        # Load touch methods.
        @driver.extend Selenium::WebDriver::DriverExtensions::HasTouchScreen
        @driver.extend Selenium::WebDriver::DriverExtensions::HasLocation

        # export session
        if @export_session
          # rubocop:disable Style/RescueModifier
          File.open('/tmp/appium_lib_session', 'w') do |f|
            f.puts @driver.session_id
          end rescue nil
        end
      rescue Errno::ECONNREFUSED
        raise 'ERROR: Unable to connect to Appium. Is the server running?'
      end

      @driver.manage.timeouts.implicit_wait = @default_wait

      @driver
    end

it don't have a way for loading session_id
help me
After the app start_driver, how can I use the previous session directly

Ruby doesn't provide the way.
What would you like to do?
If you'd like to connect to the installed app, you can do simply below with new session.
      caps: {
        platformName: :android,
        deviceName: client,
        udid: client,
        :noReset => 'true',
        appActivity: 'xxxxxx',
        appPackage: 'xxxxx',
        unicodeKeyboard: 'true',
        resetKeyboard: 'true'
      },

Or do you have any special use case to use the same session_id in several places?

If you have a user case, we probably can consider.
But a similar suggestion haven't merged into selenium-webdriver side.


UI Bug

Selecting cars and maps with Q/E doesn't actually select them. It will switch your view, so if i click E on pic below I'll see Spa, but then clicking select will revert the map back to Party Parks when the race actually starts. Same goes for cars.

This UI update has been rolled back but that is a great callout - I had not tested with the hotkeys and did not map their actions - this will be fixed when the UI update goes back live

https://github.com/PartyKarts-io/UnityGame/commit/f33733279034cdfdb6871ffa81b8ab0c1d4d0e97
Fixed in this commit ^


Complementary functions with concurrency control

We have some handy functions to work with promises, but they don't support concurrency control.
This PR adds complementary functions with concurrent control (like each_limit()):

all_limit()
some_limit()
any_limit()
settle_limit()

@mtdowling, @sagikazarmark, could you take a look?

@alexeyshockov sorry for the delay, I had a lot on my plate lately, but hopefully things will be a bit more relaxed. Will take a look at it soon.

@sagikazarmark @stevenwadejr  @Tobion
Is there anyone can review this?

Sorry guys it took so long to review.
@alexeyshockov can you please add some tests?

I think instead of adding all these permutations of functions, it would be cleaner to have a builder for promises resolving where you can configure the mode like any, some and the concurrency independently.
This would be related to #108 by putting those functions in a builder instead.

This implementation needs replacing to only implement this as public static class methods, instead of functions, all of which are being deprecated in the next release.

Stale.


An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=164): Unable to lookup in current state: Shutdown

Context: Before this my simulator used to work until I followed the instructions I had on my error screen to clear an error.
Environment:
OS: macOS High Sierra 10.13.5
Node: 6.11.2
Yarn: 1.3.2
npm: 6.0.0
Watchman: 4.9.0
Xcode: Xcode 9.4.1 Build version 9F2000
Android Studio: 3.1 AI-173.4697961
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4
I have spent already 4 hours to get it back working, and I am still in the same spot.
In the terminal this is the end result when I execute react-native run-ios

** BUILD SUCCEEDED **
The following commands produced analyzer issues:
Analyze Base/RCTModuleMethod.mm normal x86_64
(1 command with analyzer issues)
Installing build/Build/Products/Debug-iphonesimulator/application.app
An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=164):
Unable to lookup in current state: Shutdown
Launching org.reactjs.native.example.application
An error was encountered processing the command (domain=com.apple.CoreSimulator.SimError, code=164):
Unable to lookup in current state: Shutdown

Attempted: I tried clearing my cache, and reinstalling modules. Creating a new application, the same error appears
Android Simulator Works, but does not connect/ display anything other than connecting...

Reason: https://forums.developer.apple.com/thread/66665#192972

Still seeing this issue. The above solution did not do much.


Fix the wrong return in locate function of ROSLaunchManager

I'm not sure what's the difference between filename and filename_original. Should I remove the latter?

I'm not sure what's the difference between filename and filename_original. Should I remove the latter?

Thanks for spotting this! There's a few code smells that led to this issue. The intent behind filename and filename_original is that filename is a mutable variable that should be returned, and filename_original is immutable and used for the sake of logging. I messed up the code by a new variable, path, into the mix, which removes the need for the filename_original and filename distinction. I think that a slightly better fix here is to replace all references to path with filename to restore the original intent.


Cross compile for embedded ARM using preset file does not create cacheVariables before calling CMakeLists.txt

Brief Issue Summary
Using cmake --preset debug works from the command line. It does not work from CMake:Configure. Some command line defines provided by preset cacheVariables are not set before calling root CMakeLists.txt. CMakeLists.txt outputs a message which indicates that the define has not been provided.
CMakePresets.json
CMakeLists.txt
arm-none-eabi-gcc.cmake.txt
CMake Tools Diagnostics
{
  "os": "win32",
  "vscodeVersion": "1.85.1",
  "cmtVersion": "1.16.32",
  "configurations": [
    {
      "folder": "e:\\VCU2\\repository\\vcu\\Application\\vcu_app",
      "cmakeVersion": "3.27.1",
      "configured": true,
      "generator": "Ninja",
      "usesPresets": false,
      "compilers": {}
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "Debug",
    "buildTypesSeen": [
      "Debug"
    ],
    "requests": [],
    "responses": [],
    "partialMatches": [],
    "targetCount": 5,
    "executablesCount": 1,
    "librariesCount": 4,
    "targets": [
      {
        "name": "app_assy_lib",
        "type": "OBJECT_LIBRARY"
      },
      {
        "name": "app_src_lib",
        "type": "OBJECT_LIBRARY"
      },
      {
        "name": "cw_stm32f746_core",
        "type": "OBJECT_LIBRARY"
      },
      {
        "name": "stm32CubeF7_core",
        "type": "OBJECT_LIBRARY"
      },
      {
        "name": "vcu_app.elf",
        "type": "EXECUTABLE"
      }
    ]
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": true
    }
  ]
}

Debug Log
[main] Configuring project: vcu_app
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SE:/VCU2/repository/vcu/Application/vcu_app -Be:/VCU2/repository/vcu/Application/vcu_app/build/Debug -G Ninja
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Start of file ARM_TOOLCHAIN_BIN_DIR
[cmake] -- The C compiler identification is unknown
[cmake] -- The CXX compiler identification is unknown
[cmake] CMake Error at CMakeLists.txt:21 (project):
[cmake]   The CMAKE_C_COMPILER:
[cmake]
[cmake]     /arm-none-eabi-gcc.exe
[cmake]
[cmake]   is not a full path to an existing compiler tool.
[cmake]
[cmake]   Tell CMake where to find the compiler by setting either the environment
[cmake]   variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
[cmake]   the compiler, or to the compiler name if it is in the PATH.
[cmake]
[cmake]
[cmake] CMake Error at CMakeLists.txt:21 (project):
[cmake]   The CMAKE_CXX_COMPILER:
[cmake]
[cmake]     /arm-none-eabi-g++.exe
[cmake]
[cmake]   is not a full path to an existing compiler tool.
[cmake]
[cmake]   Tell CMake where to find the compiler by setting either the environment
[cmake]   variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
[cmake]   to the compiler, or to the compiler name if it is in the PATH.
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_BUILD_TYPE:STRING=Debug -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SE:/VCU2/repository/vcu/Application/vcu_app -Be:/VCU2/repository/vcu/Application/vcu_app/build/Debug -G Ninja exited with code: 1

Additional Information
No response

Thanks for letting us know @davepregan ! Could you provide a repro project so that we can investigate?
This definitely seems to be stemming from our extension since it reproduces with the extension but not on the command-line, so a repro project would be very useful. Thanks!

Well I don't really understand what is happening here. I started to prepare a repro project and re-ran the generation/build. This time it worked but the command line seems to have changed
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" -DCMAKE_BUILD_TYPE=Debug -DARM_TOOLCHAIN_BIN_DIR=C:/ST/STM32CubeIDE_1.6.1/STM32CubeIDE/plugins/com.st.stm32cube.ide.mcu.externaltools.gnu-tools-for-stm32.11.3.rel1.win32_<IP_ADDRESS>309141235/tools/bin "-DGIT_BASH_CMD=C:/Program Files/Git/usr/bin/bash" -DCMAKE_TOOLCHAIN_FILE=E:/VCU2/repository/vcu/Application/vcu_app/arm-none-eabi-gcc.cmake -SE:/VCU2/repository/vcu/Application/vcu_app -BE:/VCU2/repository/vcu/Application/vcu_app/build/debug -G Ninja
Note that --no-warn-unused-cli is missing, along with -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE. Cmake:ExportCompile Commands File is checked in both User and Workspace settings. I don't know what has removed --no-warn-unused-cli

@davepregan It sounds like the issue has been fixed. In the past year some fixes have been merged about the --no-warn-unused-cli, though I don't have specific commits in mind. Please create a new issue if I'm incorrect and this hasn't been fixed. Thanks!


Fixed worm() face normals.

I'm not actually happy with the jagginess of the worm surface, but the real solution will require a rewrite.  This at least makes for a functional worm.


Updated ForgotPass

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 6

Complexity increasing per file
==============================
- src/components/auth/ForgotPassword.js  1

See the complete overview on Codacy


The only songs that have crashed so far have spaces in their data folder names, so im assuming something doesn't load.

Quoting back from https://github.com/KadeDev/Kade-Engine/issues/746#issuecomment-855347499
Not a bug, Kade forgot to mention that Winter Horrorland, Satin Panties, Philly Nice and Dad Battle were all conformed to #480. If you're compiling the game, delete your export folder entirely and recompile the game completely again and it should be fixed.

Quoting back from #746 (comment)
Not a bug, Kade forgot to mention that Winter Horrorland, Satin Panties, Philly Nice and Dad Battle were all conformed to #480. If you're compiling the game, delete your export folder entirely and recompile the game completely again and it should be fixed.

Hi - adding -clean to the end of the build command should also fixit.

This is a known bug and we are fixing it -- closing all issues reporting this because y'all don't know how to use the search bar (and I dunno which one was first)
(pasted response)


feat: add set nullable generator

Adds add/drop not null constraint generator and tests.

@mescanne Is there a specific problem / question with this PR? Or did it slip of your radar by accident?


linear.nice() ticks do not always span the domain

const scale = d3
  .scaleLinear()
  .domain([0.98, 1.13])
  .nice()

scale.domain() // [0.98, 1.14] as expected
scale.ticks() // [0.98, 1, 1.02, 1.04, 1.06, 1.08, 1.1, 1.12]
scale.ticks(17) // [0.98, 0.99, 1, 1.01, 1.02, 1.03, 1.04, 1.05, 1.06, 1.07, 1.08, 1.09, 1.1, 1.11, 1.12, 1.13]

I believe this issue is a floating point number precision error in the d3-array/ticks
For this specific example and following the bouncing ball, if ticks is called with (0.98, 1.14, 10) then we get the following on line 23
step = -50; // -> 50
start * step = 0.98 * 50 = 49;
end * step = 1.14 * 50 = 56.999999999999;

Naturally calling floor unintentionally reduces the stop value by 1.
PR #164 was added to solve #162 however I think it just inverted the issue.
In this scenario the precision is not important so I think a possible solution is to call toPrecision() or use d3-format?
Happy to submit a PR after discussion.
Note:
This issue is more an issue for d3-array than d3-scale but I have submitted it here as this is where the issue surfaced for me. Happy to close this and open one for d3-array if required.
Edit:
I note that most of the tests covering this are using integer domains and a relatively small count (2,3,4). If I call check([0.98, 1.14], 2/3/4); then they all pass but not with count = 10; (default).
Should this test suit be expanded a little?
Second Edit:
On second thoughts toPrecision wouldn't work due to the unknown size of the start on stop but possible something as simple as the following:
function round (x) {
  return Math.round(x * 100) / 100
}

if (step > 0) {
  start = Math.ceil(round(start / step));
  stop = Math.floor(round(stop / step));
  ticks = new Array(n = Math.ceil(stop - start + 1));
  while (++i < n) ticks[i] = (start + i) * step;
} else {
  step = -step;
  start = Math.ceil(round(start * step));
  stop = Math.floor(round(stop * step));
  ticks = new Array(n = Math.ceil(stop - start + 1));
  while (++i < n) ticks[i] = (start + i) / step;
}

There is possibly a wider issue/effect that I am unaware on but this patch does fix my issue and make all the test pass including that of d3-array.

Using the d3-array API:
d3.nice(0.98, 1.13, 10) // [0.98, 1.14]
d3.ticks(0.98, 1.14, 10) // [0.98, 1, 1.02, 1.04, 1.06, 1.08, 1.1, 1.12]

Rounding to some arbitrary precision is not going to work in general. I think we might need to do something like this instead:
step = -step;
start = Math.ceil(start * step);
const r = Math.round(stop * step);
stop = r - (r / step > stop);

I was unsure of the wider effect or use so makes sense it's not as simple as rounding.


Missing start-here branch

The instructions say to "checkout the start-here branch", but that branch doesn't seem to exist.

Thank you for checking go-caskdb and opening the issue. I hadn't pushed the branch earlier, now I did.
https://github.com/avinassh/go-caskdb/tree/start-here


Provide more information about the 'Support' filter to avoid confusion

Fixes https://github.com/godotengine/godot/issues/70598
-> May help to avoid confusion as written down in the issue.

Before
After

I would suggest explicitly listing the Support levels that were chosen. For example:

No results compatible with Godot 4.0 for support levels "Official".
Check the enabled support levels using the Support button in the top-right corner.

This is a good start, but I suggest explicitly listing the support levels that were chosen.

Done. I also added this to the normal filter search result, as it can also happen there.
I also updated the screenshots.
Open for feedback. :)

Hey @Maran23 thanks for this little but helpful addition. I also was confused about this message and apart from the missing explanation this could be triggered two other things:

I did not realize that the support-filter button is in fact ... a button. It is styled like the labels (Sort, Category, Site) without any border or highlight (color, shading) to make it look like a button. Also, all dropdowns in this window have this little triangle on the right side to indicate that the field is a dropdown element. The support-filter button does not have a triangle.
The naming 'Support' might also be confusing. When looking at it in this menu, my thought as a first time user is 'This must lead to the asset-lib support page'. But I have no clue what kind of renaming could help here.

Would it be possible to incorporate some minor UI changes next to the textual explanation to improve this dialog even further?

I did not realize that the support-filter button is in fact ... a button. It is styled like the labels (Sort, Category, Site) without any border or highlight (color, shading) to make it look like a button. Also, all dropdowns in this window have this little triangle on the right side to indicate that the field is a dropdown element. The support-filter button does not have a triangle.

I agree. Unfortunately this is probably a bigger task, since this component (MenuButton) is used more often around the engine. So not only this location suffers from this.

We may want to open a proposal to improve the look and feel of MenuButtons.

The naming 'Support' might also be confusing. When looking at it in this menu, my thought as a first time user is 'This must lead to the asset-lib support page'. But I have no clue what kind of renaming could help here.

Not sure here too. I also find this name quite confusing. This is more likely some kind of category.
This PR is just a low hanging fruit, trying to improve the current state without much refactoring or more.

Thanks!


Impossible removal of non-empty directory after previous deletion by a rm command within a dedicated RUN directive

Description
I discovered an issue related to Docker but limited to a specific environment configuration.
The issue consists in the impossibility to delete a non-empty directory, both at build-time and run-time, when it was already deleted by a rm command within a dedicated RUN directive.
To make an example the following set of RUN directives leads to a build fail:
RUN cd /root && mkdir test && touch test/file.txt
RUN rm -rf /root/test && [ ! -e /root/test ]
RUN cd /root && mkdir test && touch test/file.txt
RUN rm -rf /root/test && [ ! -e /root/test ]  # This test fails!

But the following works:
RUN cd /root && mkdir test && touch test/file.txt && \
rm -rf /root/test && [ ! -e /root/test ]
RUN cd /root && mkdir test && touch test/file.txt && \
rm -rf /root/test && [ ! -e /root/test ]

I found this issue occurs with the following environment configuration:
Docker: 1.12.5
Storage Driver: aufs
Operating System: Debian 8 "Jessie"
Kernel: 3.16.0-4-amd64

The issue doesn't occur with the following environment configurations:
Docker: 1.12.5
Storage Driver: devicemapper
Operating System: Debian 9 "Stretch" (testing)
Kernel Version: 4.8.0

Docker: 1.12.5
Storage Driver: aufs
Operating System: Alpine Linux 3.4
Kernel Version: 4.4.39-moby

It might be an issue related to the combination of an outdated Linux kernel and the aufs file system.
Steps to reproduce the issue:
FROM alpine

RUN cd /root && mkdir test && touch test/file.txt
RUN rm -rf /root/test && [ ! -e /root/test ]
RUN cd /root && mkdir test && touch test/file.txt
RUN rm -rf /root/test && [ ! -e /root/test ]

Describe the results you received:
Step 1 : FROM alpine
 ---> baa5d63471ea
Step 2 : RUN cd /root && mkdir test && touch test/file.txt
 ---> Running in caed4be9b143
 ---><PHONE_NUMBER>b5
Removing intermediate container caed4be9b143
Step 3 : RUN rm -rf /root/test && [ ! -e /root/test ]
 ---> Running in fc5a3220cc51
 ---> 33e29c42f53b
Removing intermediate container fc5a3220cc51
Step 4 : RUN cd /root && mkdir test && touch test/file.txt
 ---> Running in b9a8131f541a
 ---> 24d3056e7b1e
Removing intermediate container b9a8131f541a
Step 5 : RUN rm -rf /root/test && [ ! -e /root/test ]
 ---> Running in 6dc79a4eeecd
The command '/bin/sh -c rm -rf /root/test && [ ! -e /root/test ]' returned a non-zero code: 1

Describe the results you expected:
Step 1 : FROM alpine
 ---> baa5d63471ea
Step 2 : RUN cd /root && mkdir test && touch test/file.txt
 ---> Running in caed4be9b143
 ---><PHONE_NUMBER>b5
Removing intermediate container caed4be9b143
Step 3 : RUN rm -rf /root/test && [ ! -e /root/test ]
 ---> Running in fc5a3220cc51
 ---> 33e29c42f53b
Removing intermediate container fc5a3220cc51
Step 4 : RUN cd /root && mkdir test && touch test/file.txt
 ---> Running in b9a8131f541a
 ---> 24d3056e7b1e
Removing intermediate container b9a8131f541a
Step 5 : RUN rm -rf /root/test && [ ! -e /root/test ]
 ---> Running in 6dc79a4eeecd
 ---> xxx
Removing intermediate container 6dc79a4eeecd
Successfully built xxx

Output of docker version:
Client:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:21:54 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:21:54 2016
 OS/Arch:      linux/amd64

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 14
Server Version: 1.12.5
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 10
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host overlay bridge
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 3.873 GiB
Name: labtech8
ID: YOSF:AJSF:NTMK:ALXN:7U7C:X5PC:T7O2:BBVA:ANHS:IDBA:XRGO:QOYD
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
The environment is a VMware vSphere virtual machine.

I suspect this is a duplicate of https://github.com/docker/docker/issues/24309, and an issue in aufs, not docker; @AkihiroSuda created a test-script for that case; perhaps you can try running that to verify it's the same problem; https://github.com/AkihiroSuda/test24309-without-docker

I prepared a Dockerfile as @AkihiroSuda suggested in #24309.
For each one of my environments I respectively built the image and run it. The result are:

In
Docker: 1.12.5
Storage Driver: devicemapper
Operating System: Debian 9 "Stretch" (testing)
Kernel Version: 4.8.0

the following message has been printed:
cat: can't open '/x/a': No such file or directory

So, everything is OK.

In
Docker: 1.12.5
Storage Driver: aufs
Operating System: Debian 8 "Jessie"
Kernel: 3.16.0-4-amd64

the string "hey2" string has been printed, which is an error.

Thank you for testing! It looks like a duplicate of the linked issue indeed. Unfortunately, I don't have a direct solution for that, other than working around the problem in your docker files, or using a different storage driver. I see you're running devicemapper on the other machine, which "works", but overall performs a lot less than aufs, and to be suitable for production requires manual setup, otherwise performance will be very poor.
Depending on your use case, one of the other options (such as btrfs, or zfs) could work, but also require some setup.
If you are able to run on a more recent kernel (such as the "Debian 9 stretch" machine), have a look at the overlay storage drivers as well. The overlay and overlay2 drivers perform very well; The overlay2 driver resolves  the  "running out of inodes" issue that the overlay driver could have if you run a lot of containers (https://docs.docker.com/engine/userguide/storagedriver/selectadriver/#/overlay-vs-overlay2). More info on those here; https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/
I'll close this issue because this is a duplicate of https://github.com/docker/docker/issues/24309, but please subscribe to the linked issue to stay informed on updates.
My teammate prepared a new Debian 9 Stretch VM, just for emergency. Anyway the workaround seems sufficient at the moment.
Regarding overlay2, would it really be as performant as AUFS?

Regarding overlay2, would it really be as performant as aufs?

It may depend on your use case, but it's definitely worth a try; perhaps if you have a test-system available


Add missing BPF_MAP_TYPE_STACK in BPF code

Currently BPF_MAP_TYPE_STACK is supported by user code (aya/src/maps/stack.rs),
but it does not support the BPF_MAP_TYPE_STACK in BPF code.
This patch fixes it.

https://github.com/nak3/aya-showcase/tree/main/stack demonstrates this PR.


phenotypes should link to genotypes not genes by default

I think that is what was decided.
I prefer genes but I guess we need to be consistent between single and multi allele so it needs to be genotypes...
then we will need a basic list with genes and products for all genes contributing to the genotype:

[ ] need a link to a list of "genotypes with this term" from the phenotype term page

[ ] multi allele phenotypes (genes) (maybe later if required)
I haven't done this bit yet. The link is there on the phenotype term pages but the list includes all genes for all genotypes annotated with that term. I'm working on fixing that.

"genes from single-allele genotypes associated with this term"

from
https://github.com/pombase/website/issues/168

phenotypes should link to genotypes not genes by default

So put the genotypes column back in the full details annotation table on the term and publication pages?  And remove the gene column?

then we will need a basic list with genes and products for all genes contributing to the genotype

Is this the list you mean?:
http://pombase2.bioinformatics.nz/genotype/addd2b43e02fbb5c-genotype-4
I can add the gene products to that table.

need a link to a list of "genotypes with this term" from the phenotype term page

I'll add that.

need a link to a list of "genotypes with this term" from the phenotype term page

Should that be the single allele genotypes or all genotypes?

I think we need to discuss this one on Tuesday as a group, because I'm not sure  what others would like, and I'm too biased towards "genes"

Should that be the single allele genotypes or all genotypes?

I've added a link the single allele genotypes because I had that code ready to go.

Wow!. That's helpful.  Now we can see these it will help us to decide the best way to display.

Phenotype term pages, currently show genes list (mixed for multi and single gene)
Need to:

[ ] Change genes to genotypes
[ ] Order single gene first, multi later
[ ]  hide penetrance and expressivity on term page summary view
later we'll add a filter
later we'll consider separate tables (after consultation)

Change genes to genotypes

Done.

Order single gene first, multi later

I've done that but the summary is still a bit messy.  It will improve once the duplicate genotypes are fixed.

hide penetrance and expressivity on term page summary view

Done (I think that was fixed by a different issue).

need a link to a list of "genotypes with this term" from the phenotype term page

Isn't that what the phenotype term page is? Like this page?:
http://pombase2.bioinformatics.nz/term/FYPO%3A0000082

multi allele phenotypes (genes) (maybe later if required)

Does this need doing?

need a link to a list of "genotypes with this term" from the phenotype term page

Isn't that what the phenotype term page is?

I think so, but Val might mean a list of just the genotypes, without the evidence, conditions, etc. from the annotations (and with each genotype listed only once). There is a link for single-allele genotypes but not for multi-allele genotypes.
On the phenotype term page, it would probably be good to list single-allele genotypes first, and then multi-allele genotypes. In the detailed view they could be separate tables if V&A prefer.

multi allele phenotypes (genes) (maybe later if required)

Does this need doing?

To clarify, this refers to adding links for "Multi-allele genotypes associated with this term ..." and "Genes from multi-allele genotypes associated with this term ..." analogous to the existing single-allele links. I'm not sure how important or urgent it is. From Val's comment the multi-allele genotype
list sounds like a higher priority than the "genes from" list.

Lets open new tickets for outstanding here...


Minor improvements and code refactoring.

Currently I don't know why the build is failing. Let me know if I can fix it myself ;)


Add a file system watcher for rapid local development

Similar to the way Jeykll works for web development projects, many designers like to work on their projects locally.

[ ] add a filesystem watcher, so if you run bakery locally and point it to a directory (instead of a git repo) then each time the UFOs change on disk, a bake process is run.
[ ] at the end of each build, as part of the build finished message, it would be good to show the total size of the /builds directory, with a tip about how to count the size of only the immediate children with du, so that as the builds dir grows the user knows to trim it :)

https://github.com/facebook/watchman can help with this

I consider this out of scope for FontBakery-core.


log writing failed. can't be called from trap context

After starting resque-pool via
bundle exec resque-pool --daemon --environment production
resque-pool.stdout.log is populated without issue, but resque-pool.stderr.log complains
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context
log writing failed. can't be called from trap context

It's related to logging inside a signal handler--resque and resque-scheduler have migrated to mono_logger to work around this issue.
https://github.com/resque/resque/issues/1493
https://github.com/steveklabnik/mono_logger
Any help would be greatly appreciated, thanks!

We are encountering a similar issue.
I found this on the interwebs:
LOG_QUEUE = Queue.new
Thread.start do
  logger = Logger.new(STDOUT)
  nil while logger.info(LOG_QUEUE.pop)
end

https://github.com/resque/resque/issues/1493#issuecomment-358711299


Running with cuda=true fails with FileNotFound error.

I'm on an A100 arch linux box, latest master at the time of this issue.
I attempt to run llama 3.1 with cuda=true runtime parameter like so:
bazel run -c opt //llama:Llama-3.1-8B-Instruct --@zml//runtimes:cuda=true -- --prompt="Once upon a time,"

and that results in the following output:
INFO: Analyzed target //llama:Llama-3.1-8B-Instruct (49 packages loaded, 859 targets configured).
INFO: Found 1 target...
Target //llama:Llama-3.1-8B-Instruct up-to-date:
  bazel-bin/llama/Llama-3.1-8B-Instruct.exe
INFO: Elapsed time: 1.969s, Critical Path: 0.06s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/llama/Llama-3.1-8B-Instruct.exe '--model=../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/model.safetensors.index.json' '--tokenizer=../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/tokenizer.json' '--num-heads=32' '--num-kv-heads=8' '--rope-freq-base=500000' '--prompt=Once upon a time,'
info(llama):    LLama was compiled with builtin.OptimizeMode.ReleaseSafe
info(pjrt): Loaded library: libpjrt_cpu.so
info(pjrt): Loaded library: libpjrt_cuda.so
error: FileNotFound

Running without results in it working correctly(on CPU only)
❯ bazel run -c opt //llama:Llama-3.1-8B-Instruct -- --prompt="Once upon a time,"
WARNING: Build option --@@zml~//runtimes:cuda has changed, discarding analysis cache (this can be expensive, see https://bazel.build/advanced/performance/iteration-speed).
INFO: Analyzed target //llama:Llama-3.1-8B-Instruct (0 packages loaded, 26068 targets configured).
INFO: Found 1 target...
Target //llama:Llama-3.1-8B-Instruct up-to-date:
  bazel-bin/llama/Llama-3.1-8B-Instruct.exe
INFO: Elapsed time: 46.532s, Critical Path: 43.27s
INFO: 8 processes: 5 internal, 3 linux-sandbox.
INFO: Build completed successfully, 8 total actions
INFO: Running command line: bazel-bin/llama/Llama-3.1-8B-Instruct.exe '--model=../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/model.safetensors.index.json' '--tokenizer=../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/tokenizer.json' '--num-heads=32' '--num-kv-heads=8' '--rope-freq-base=500000' '--prompt=Once upon a time,'
info(llama):    LLama was compiled with builtin.OptimizeMode.ReleaseSafe
info(pjrt): Loaded library: libpjrt_cpu.so
info(llama): Model file: ../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/model.safetensors.index.json
info(llama): ✅ Parsed llama config: llama.LlamaOptions{ .gen_opts = nn.SamplingStrategy{ .topk = 2, .temperature = 1e0 }, .max_seq_len = 256, .num_heads = 32, .num_kv_heads = 8, .rms_norm_eps = 1e-5, .rope_opts = nn.RopeOpts{ .impl = nn.RopeOpts.Implementation.sequential, .freq_base = 5e5 } }
info(llama):    Loading tokenizer from ../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/tokenizer.json
info(llama): ✅ Loaded tokenizer from ../zml~~huggingface~Meta-Llama-3.
info(llama):    Loading Llama weights from ../zml~~huggingface~Meta-Llama-3.1-8B-Instruct/model.safetensors.index.json...
info(llama): ✅ Loaded weights in 42957ms
2024-11-25 23:45:11.401525: I xla/service/dump.cc:556] HloModule dump enabled with path prefix: , suffix: before_optimizations
info(llama): ✅ Compiled model in 64583ms
info(llama): ✅ Prompt: Once upon a time,
debug(llama): Tokenized Prompt { 128000, 9843, 5304, 264, 892, 11 }
...

Same thing happens with OpenLLaMA-3B.
I attempt to use cuda=true with mnist and get unreachable code:
 bazel run -c opt //mnist --@zml//runtimes:cuda=true
INFO: Analyzed target //mnist:mnist (3 packages loaded, 7 targets configured).
INFO: Found 1 target...
Target //mnist:mnist up-to-date:
  bazel-bin/mnist/mnist
INFO: Elapsed time: 28.992s, Critical Path: 28.54s
INFO: 7 processes: 4 internal, 3 linux-sandbox.
INFO: Build completed successfully, 7 total actions
INFO: Running command line: bazel-bin/mnist/mnist ../_main~_repo_rules~com_github_ggerganov_ggml_mnist/file/mnist.pt ../_main~_repo_rules~com_github_ggerganov_ggml_mnist_data/file/mnist.ylc
info(pjrt): Loaded library: libpjrt_cpu.so
info(pjrt): Loaded library: libpjrt_cuda.so
thread 17772 panic: reached unreachable code
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/2085/execroot/_main/external/libxev~/src/backend/epoll.zig:0:0: 0x145bfc8 in tick (mnist_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/2085/execroot/_main/external/zigcoro~/src/asyncio.zig:95:50: 0x145d7e8 in waitForCompletion (mnist_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/2085/execroot/_main/external/zigcoro~/src/asyncio.zig:329:34: 0x14c001a in write (mnist_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/2085/execroot/_main/external/zml~/async/zigcoro.zig:316:32: 0x14c014e in flush (mnist_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/2085/execroot/_main/external/zml~/async/zigcoro.zig:519:17: 0x14e51fc in err__anon_4414 (mnist_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/2085/execroot/_main/external/rules_zig~~zig~zig_0.14.0-dev.363_Pc3faae6bf_x86_64-linux/lib/std/start.zig:533:28: 0x145cdfc in main (mnist_lib)
???:?:?: 0x720d37634e07 in ??? (libc.so.6)
Unwind information for `libc.so.6:0x720d37634e07` was not available, trace may be incomplete

???:?:?: 0x720d37634ecb in ??? (libc.so.6)
external/hermetic_cc_toolchain~~toolchains~zig_sdk/lib/libc/glibc/sysdeps/x86_64/start-2.33.S:120:0: 0x1453c59 in ??? (external/hermetic_cc_toolchain~~toolchains~zig_sdk/lib/libc/glibc/sysdeps/x86_64/start-2.33.S)

Here is my GPU info:
❯ nvidia-smi
Mon Nov 25 23:53:57 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.90.07              Driver Version: 550.90.07      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  GRID A100D-2-20C               On  |   00000000:06:00.0 Off |                   On |
| N/A   N/A    P0             N/A /  N/A  |       0MiB /  20480MiB |     N/A      Default |
|                                         |                        |              Enabled |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| MIG devices:                                                                            |
+------------------+----------------------------------+-----------+-----------------------+
| GPU  GI  CI  MIG |                     Memory-Usage |        Vol|      Shared           |
|      ID  ID  Dev |                       BAR1-Usage | SM     Unc| CE ENC DEC OFA JPG    |
|                  |                                  |        ECC|                       |
|==================+==================================+===========+=======================|
|  0    0   0   0  |               0MiB / 18412MiB    | 28      0 |  2   0    1    0    0 |
|                  |                 0MiB /  4096MiB  |           |                       |
+------------------+----------------------------------+-----------+-----------------------+

I switched over to this machine and believe I set it up identically to the A40 machine I was on before that did successfully have cuda execution on OpenLlama but not Llama3.1. I talked about those issues over in issue 19.  I was hoping this switch would alleviate my issues.
This might end up being a git bisect type of situation, I'll see if an older commit works successfully and update this issue. If it doesn't then I guess this may be a hardware/setup specific issue which is a worse result for me.

Hello @AdjectiveAllison I will take a look and address the reported issue. Thank you very much for these details!! I will keep you updated here. It seems that our CUDA sandboxing is leaking, with shared libraries loaded from the OS. And at first glance I think it's the same root cause that you observe here: https://github.com/zml/zml/issues/19 .
If you change the topk parameter to 1 you should observe that the program is running: ./bazel.sh run --@zml//runtimes:cuda=true --@zml//runtimes:cpu=false //llama:TinyLlama-Stories-15M -- --topk=1 cause when we compile the model through pjrt/xla some passes are done and the HLO graph vary. With topk=2 a custom call to a custom cuda kernel is made while with topk=1 it's "vanilla" without custom call.
For the record, you can have detailed informations while running targets. Eg: ./bazel.sh run --@zml//runtimes:cuda=true --@zml//runtimes:cpu=false --run_under="XLA_FLAGS=\"--xla_dump_to=-\" TF_CPP_MAX_VLOG_LEVEL=2 TF_CPP_MIN_LOG_LEVEL=0" //llama:TinyLlama-Stories-15M  . We should definitely provide troubleshooting helpers / doc.
I keep you informed asap.
- Hugo

Awesome, I gave it a try.
I ran bazel run --@zml//runtimes:cuda=true --@zml//runtimes:cpu=false --run_under="XLA_FLAGS=\"--xla_dump_to=-\" TF_CPP_MAX_VLOG_LEVEL=2 TF_CPP_MIN_LOG_LEVEL=0" //llama:TinyLlama-Stories-15M -- --topk=1
I tried to use the bazel.sh script in case my local bazel is weird or different or something and got the same result. Below are the full logs/output.

Full logs
INFO: Analyzed target //llama:TinyLlama-Stories-15M (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //llama:TinyLlama-Stories-15M up-to-date:
  bazel-bin/llama/TinyLlama-Stories-15M.exe
INFO: Elapsed time: 0.232s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: /bin/bash -c 'XLA_FLAGS="--xla_dump_to=-" TF_CPP_MAX_VLOG_LEVEL=2 TF_CPP_MIN_LOG_LEVEL=0 bazel-bin/llama/TinyLlama-Stories-15M.exe '\''--model=../zml~~huggingface~Karpathy-TinyLlama-Stories/stories15M.tinyllama'\'' '\''--tokenizer=../_main~_repo_rules~Karpathy-TinyLlama-Tokenizer/file/stories260K.tinyllama'\'' '\''--topk=1'\'''
info(llama):    LLama was compiled with builtin.OptimizeMode.Debug
info(pjrt): Loaded library: libpjrt_cuda.so
2024-11-27 02:45:05.670223: I external/tsl/tsl/platform/default/dso_loader.cc:73] Successfully opened dynamic library libcuda.so.1
2024-11-27 02:45:05.713981: I xla/service/platform_util.cc:191] Initializing devices
2024-11-27 02:45:05.714508: I xla/service/platform_util.cc:198] Started device init 0
2024-11-27 02:45:05.714552: I xla/stream_executor/executor_cache.cc:43] building executor
2024-11-27 02:45:05.714561: I xla/service/platform_util.cc:198] Started device init 1
2024-11-27 02:45:05.714590: I xla/stream_executor/executor_cache.cc:43] building executor
2024-11-27 02:45:06.011569: I xla/stream_executor/cuda/cuda_context.cc:181] created or reused context 0x2f222b90 for this thread
2024-11-27 02:45:06.011620: I xla/stream_executor/cuda/cuda_runtime.cc:54] Get CUDA runtime version
2024-11-27 02:45:06.011747: I xla/service/platform_util.cc:210] Finished device init 0
2024-11-27 02:45:06.016484: I xla/stream_executor/cuda/cuda_context.cc:181] created or reused context 0x2f27a730 for this thread
2024-11-27 02:45:06.016526: I xla/stream_executor/cuda/cuda_runtime.cc:54] Get CUDA runtime version
2024-11-27 02:45:06.016633: I xla/service/platform_util.cc:210] Finished device init 1
2024-11-27 02:45:06.016797: I xla/service/platform_util.cc:239] Device initialization complete
2024-11-27 02:45:06.016983: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f230b60 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017007: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f230b80 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017020: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f23f000 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017032: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f235140 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017043: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f23fcb0 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017052: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f23ff70 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017063: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f2402c0 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017074: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f240610 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017263: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f240a80 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017279: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f210630 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017287: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f210980 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017299: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f210cd0 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017308: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f211020 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017319: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f211370 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017330: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f2116c0 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017342: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f211c40 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017375: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f211f90 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017386: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f23a570 for executor 0x7ee444001740 on thread
2024-11-27 02:45:06.017913: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f21bb90 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.017940: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f22d860 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.017954: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32ab40 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.017965: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32aef0 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.017979: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32b240 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.017989: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32b590 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.017999: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32b8e0 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018010: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32bc60 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018172: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f32bfb0 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018188: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f337cd0 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018201: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f338020 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018212: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f3383a0 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018223: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f3386f0 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018233: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f338a40 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018240: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f338d90 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018249: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f339340 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018281: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f339690 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.018291: I xla/stream_executor/cuda/cuda_stream.cc:98] successfully created stream 0x2f342460 for executor 0x7ee428001a70 on thread
2024-11-27 02:45:06.019353: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: GPU_0_bfc
2024-11-27 02:45:06.019374: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.019383: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.019390: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.019394: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.019397: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.019402: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.019406: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.019410: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.019417: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.019421: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.019428: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.019432: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.019436: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.019439: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.019443: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.019453: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.019457: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.019462: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.019466: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.019470: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.019473: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.019502: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: GPU_1_bfc
2024-11-27 02:45:06.019511: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.019516: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.019523: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.019531: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.019540: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.019547: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.019550: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.019554: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.019560: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.019567: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.019570: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.019577: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.019583: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.019590: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.019596: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.019602: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.019609: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.019615: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.019622: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.019625: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.019629: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.019651: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: GPU_collectivememory_0_bfc
2024-11-27 02:45:06.019660: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.019666: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.019673: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.019679: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.019686: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.019691: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.019698: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.019705: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.019711: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.019718: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.019724: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.019729: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.019735: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.019741: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.019748: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.019757: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.019765: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.019769: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.019774: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.019778: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.019785: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.019805: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: GPU_collectivememory_1_bfc
2024-11-27 02:45:06.019815: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.019819: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.019826: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.019829: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.019833: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.019839: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.019845: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.019852: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.019857: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.019864: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.019871: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.019878: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.019885: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.019891: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.019896: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.019903: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.019910: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.019916: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.019923: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.019928: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.019934: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.019945: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: xla_gpu_host_bfc
2024-11-27 02:45:06.019951: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.019957: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.019964: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.019971: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.019977: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.019984: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.019991: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.019997: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.020004: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.020011: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.020018: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.020025: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.020029: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.020036: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.020043: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.020050: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.020057: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.020064: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.020070: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.020077: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.020082: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.020090: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: xla_gpu_host_bfc
2024-11-27 02:45:06.020096: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.020103: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.020109: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.020116: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.020123: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.020129: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.020136: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.020141: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.020148: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.020154: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.020161: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.020167: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.020173: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.020180: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.020186: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.020191: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.020198: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.020205: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.020211: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.020218: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.020228: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.021420: I xla/parse_flags_from_env.cc:206] For env var XLA_FLAGS found arguments:
2024-11-27 02:45:06.021509: I xla/parse_flags_from_env.cc:208]   argv[0] = <argv[0]>
2024-11-27 02:45:06.021515: I xla/parse_flags_from_env.cc:208]   argv[1] = --xla_dump_to=-
2024-11-27 02:45:06.021546: I xla/tsl/framework/bfc_allocator.cc:84] Creating new BFCAllocator named: xla_gpu_host_bfc
2024-11-27 02:45:06.021551: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256B
2024-11-27 02:45:06.021555: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512B
2024-11-27 02:45:06.021561: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.0KiB
2024-11-27 02:45:06.021564: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.0KiB
2024-11-27 02:45:06.021568: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.0KiB
2024-11-27 02:45:06.021572: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.0KiB
2024-11-27 02:45:06.021576: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.0KiB
2024-11-27 02:45:06.021580: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.0KiB
2024-11-27 02:45:06.021583: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.0KiB
2024-11-27 02:45:06.021587: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.0KiB
2024-11-27 02:45:06.021591: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.0KiB
2024-11-27 02:45:06.021595: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 512.0KiB
2024-11-27 02:45:06.021599: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 1.00MiB
2024-11-27 02:45:06.021602: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 2.00MiB
2024-11-27 02:45:06.021606: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 4.00MiB
2024-11-27 02:45:06.021610: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 8.00MiB
2024-11-27 02:45:06.021613: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 16.00MiB
2024-11-27 02:45:06.021617: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 32.00MiB
2024-11-27 02:45:06.021621: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 64.00MiB
2024-11-27 02:45:06.021624: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 128.00MiB
2024-11-27 02:45:06.021628: I xla/tsl/framework/bfc_allocator.cc:87] Creating bin of max chunk size 256.00MiB
2024-11-27 02:45:06.021675: I xla/stream_executor/cuda/cuda_runtime.cc:54] Get CUDA runtime version
2024-11-27 02:45:06.021812: I xla/stream_executor/cuda/cuda_runtime.cc:54] Get CUDA runtime version
error: FileNotFound
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/1862/execroot/_main/external/zigcoro~/src/coro.zig:409:17: 0x3fb92d9 in xreturned (llama_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/1862/execroot/_main/external/zigcoro~/src/coro.zig:79:5: 0x3f2491f in xawait__anon_4399 (llama_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/1862/execroot/_main/external/zigcoro~/src/asyncio.zig:60:5: 0x3f247d6 in run__anon_4290 (llama_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/1862/execroot/_main/external/zml~/async/zigcoro.zig:236:16: 0x3f24dbb in main__anon_2283 (llama_lib)
/home/allison/.cache/bazel/_bazel_allison/36225b4c74aea3b4d2da3f021042a9ba/sandbox/linux-sandbox/1862/execroot/_main/llama/main.zig:109:5: 0x3f254ba in main (llama_lib)

Still FileNotFound.
I did run a git bisect overnight but ended up waking up to a commit that timed out execution completely (hung) and muddied results instead of me finding the branch.

FWIW I believe it's a different issue. I just tested with openLLama (which worked in the other issue) and get the same results that I pasted above.

Hey @AdjectiveAllison thanks for these great details, we worked intensively today on fixing leaks between our sandboxed cuda install and the ones from the host if user installed them (dlopen story..). We successfully closed #19 and we are waiting for feedbacks on this matter.
I noticed that you use archlinux as OS and virtualized GPUs I'm ask myself if something can go wrong with this setup. As of today we dev/test with Ubutu/Debian only and we never used virtualized GPUs.
I added some log messages to have a better understanding of the failing point around FileNotFound.
Would you mind to run these two examples on your machine:

./bazel.sh run --@zml//runtimes:cuda=true --@zml//runtimes:cpu=false  //simple_layer
./bazel.sh run --@zml//runtimes:cuda=true --@zml//runtimes:cpu=false  //loader:safetensors -- </path/to/safetensors>

The first one will allow us to determine if it's a computation related problem while the second is more about communication between devices.
Also I don't know if you are aware but the -c opt if the command line is for optimized, this act on the build of zig code and all stuffs around so if you have errors don't use it cause you will be not able to see some stacktraces like when you hit unreachable.
- Hugo

It looks like You were right, your fix for #19 did fix my issues here! I'm good to go now! I super duper appreciate ya'll working to get this resolved and I am very excited about being able to move forward now :D

Also I don't know if you are aware but the -c opt if the command line is for optimized

I did not know this, thanks a bunch for letting me know!
I'll go ahead and close this issue now, thanks again!


deployer auto scaling and destruction

Is your feature request related to a problem? Please describe.
There are either too much or too less deployers available. During breaks, nights, weekends they are either running of have to be stopped and started - that is quite expensive from resources or manual activities perspective.
Describe the solution you'd like
The number of deployers are a static number today. It would be nice to have deployers created and configured based on the need and also destroyed if not needed. So the idea is to have a very small watcher VM just checking that there are requests from the pipelines which are queuing. With pending requests a deployer is created fresh with the sufficient size and destroyed after 1hour of idle time. So you have an automatic scaling.
Describe alternatives you've considered
Yes, create a set of deployers and send them to sleep and start them if your pipeline is queuing.

@PankajMeshramCSA @KimForss - The deployer should be created per region and contains the configuration files for the environments. Policy, auto start and stop, etc can be used to start and deallocate VMs on a schedule. Deallocated VMs incur no cost and there will be no manual intervention. Having a watcher VM introduces additional cost. I believe this is over engineering a simple issue. LMK what you think.


chore: release main

:robot: I have created a release beep boop
ui5-cc-spreadsheetimporter: 0.31.6
0.31.6 (2024-02-14)
Bug Fixes

turn off continue anyway on error dialog after upload button press (#494) (fb82978)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/spreadsheetimporter/ui5-cc-spreadsheetimporter/releases/tag/ui5-cc-spreadsheetimporter-v0.31.6 :sunflower:


OKAY FINE I'LL DO IT

About the PR
Draft because they need more fixup
Changelog

:cl: Rane

add: Added moths. I was not forced to do this at gunpoint.

it's passable (i.e. better than all the wiz den species mechanically) but i didn't add enough yet for nyano standards, merging anyway


update to jwt-kit v5beta

This updates google-cloud-kit to use the new v5 version of jwt-kit. Currently a beta tag.
The new release contains some API improvements and no longer vendors BoringSSL!

Is the signature change a breaking change?

The signature change is most definitely breaking. Judging that the package is already in an RC state, it makes sense to tag a 1.0 that uses v4 and then a v2 that uses v5 as @owainhunt says (and also take the opportunity to migrate it to Swift Concurrency)

I'll have a look on that, that's a great idea, I'll make the tags and everything.
For Swift concurrency there is an ongoing PR #44, it might not be available right now

@nathanfallet let me know if you need this updated :) Or if there's other plans first

I would say it's probably worth keeping this open to track the JWTKit changes until a stable release is tagged

Understand the desire as above to wait until a stable release is tagged before moving this forward, though was curious if this branch, as is, works for others? Adding it to my project gets a compiler error on this payload.

We're planning to tag the release this week and the API should be stable now so worth updating ready for that

@0xTim I see there was an RC tag in august. Can we cut a v2 branch for google-cloud-kit to then adopt jwt-kit v5? Or what would you like to see here ideally?

@JaapWijnen If you want to do it under a major version then yep that's the way to go

Hey folks, any plans to move forward with this PR? 🙂

Just updated it to compile, tests pass locally.
I'll let people merge and tag this when ready


G-drive  exportSizeLimitExceeded

Hi, how to solve the problem with exportSizeLimitExceeded
What is the problem you are having with rclone?
%File Name:Failed to copy: failed to open source object: open file failed: googleapi: Error 403: This file is too large to be exported., exportSizeLimitExceeded
What is your rclone version (eg output from rclone -V)
rclone v1.42

os/arch: linux/amd64
go version: go1.10.1

Which OS you are using and how many bits (eg Windows 7, 64 bit)
Debian GNU/Linux 9.4 (stretch)
Which cloud storage system are you using? (eg Google Drive)
Google Drive

Try this flag
  --drive-alternate-export              Use alternate export URLs for google documents export.

...Also see the docs on what it does: https://rclone.org/drive/#drive-alternate-export

thx)


[Tutorials-05] —PASCAL 3D+数据集上使用 PointNet 实现5类点云的分割

 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.

Details

请补全pr信息。


加载西班牙和日语模型的时候，报错：RuntimeError: Error(s) in loading state_dict for CFM:

Checks

[X] This template is only for question, not feature requests or bug reports.
[X] I have thoroughly reviewed the project documentation and read the related paper(s).
[X] I have searched for existing issues, including closed ones, no similar questions.
[X] I confirm that I am using English to submit this report in order to facilitate communication.

Question details
加载Discussions中提供的训练好的日语和西班牙语模型的时候报错：
日语报错：
model :  /root/F5-TTS/ckpts/.../model_1108224.pt
RuntimeError: Error(s) in loading state_dict for CFM:
size mismatch for transformer.text_embed.text_embed.weight: copying a param with shape torch.Size([2743, 512]) from checkpoint, the shape in current model is torch.Size([2546, 512]).
西班牙语报错：
model :  /root/F5-TTS/ckpts/jpgallegoar/model_1200000.safetensors
RuntimeError: Error(s) in loading state_dict for CFM:
Missing key(s) in state_dict: "mel_spec.mel_stft.spectrogram.window", "mel_spec.mel_stft.mel_scale.fb".

RuntimeError: Error(s) in loading state_dict for CFM:
size mismatch for transformer.text_embed.text_embed.weight: copying a param with shape torch.Size([2743, 512]) from checkpoint, the shape in current model is torch.Size([2546, 512]).

Use corresponding vocab.txt

RuntimeError: Error(s) in loading state_dict for CFM:
Missing key(s) in state_dict: "mel_spec.mel_stft.spectrogram.window", "mel_spec.mel_stft.mel_scale.fb".

pull latest repo commit

ok.fix .good

@SWivid I have the same problem. My case is different is that I'm training for a new language, which vocab.txt is extended from the corresponding vocab. any suggestion here?


add encryptedPath to lsjson-  fixes 3094

What is the purpose of this change?

Was the change discussed in an issue or in the forum before?

Checklist

[x ] I have read the contribution guidelines.
[ ] I have added tests for all changes in this PR if appropriate.
[x ] I have added documentation for the changes if appropriate.
[ ] All commit messages are in house style.
[x ] I'm done, this Pull Request is ready for review :-)

I think that fixed it unless I screwed something up. :)

I think that looks great now - will merge :-)


refactor(ES6): upgrade RawModule to ES6

What kind of change does this PR introduce?
ES5 => ES6 refactor

Did you add tests for your changes?
all tests are passing

Summary
Refactoring to ES2015/6

Does this PR introduce a breaking change?
No

Sure! will check his PR & see if he needs any help :)

Thank you so much!! Feel free to close this one.


Notifications.js - Code Typo

The 's' was left off of 'return ownsDocument(userId, doc)'. Should be 'return ownsDocuments...

Hey @DanSchatz - thanks for reporting this. Actually it is is ownsDocument() -- do we write ownsDocuments() somewhere else?


Fix rendering when tracks source_range is in play

This PR aims to fix the timeline rendering to correctly display items at the right location when a Track's source_range is set. Without this fix, a Track's source_range is not honored, and the display is incorrect.

This was fixed in a better way by https://github.com/jminor/raven/commit/bf2d33661a58fe99b0b54c6cf01f4685f3ffdce9


Enable pagination for collectibles

Closes #239

add collectibles pagination

@gnosis/safe-services

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

67 of 70 (95.71%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 88.445%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

safe_transaction_service/history/views_v2.py
29
30
96.67%

safe_transaction_service/history/services/collectibles_service.py
20
22
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
5840

Relevant Lines:
6603

💛  - Coveralls


Add CodeView directive documentation

I wanted a more central place to hold CodeView assembly directives. Most of this information was taken from AsmParser.cpp

Sorry but we don't use github, please use https://reviews.llvm.org/


Make mode and align_corners arguments in F.resize_image keyword-only

Following the policy
Introduced in #7429 and #7443

Jenkins, test this please

Jenkins CI test (for commit e198a77419c30b84e73bd27a3a37457b03d222df, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit e198a77419c30b84e73bd27a3a37457b03d222df, target branch master) failed with status FAILURE.

Jenkins, test this please


feat: add core js and regenerator runtime polyfills

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines

Description of change

Adds polyfills to uPortal, so that each component does not need to bundle the polyfills individually.
And avoid issues like https://github.com/Jasig/NotificationPortlet/issues/116
Resolves https://github.com/uPortal-contrib/uPortal-web-components/issues/117

/cc @jgribonvald @leighgordy @jonathanmtran @mrbenshef @mrapczynski

LGTM :+1:  I'm going to run this branch locally.  If I don't see any issues, I will merge it shortly.

Just tested this PR locally.  Everything seems to work.


EnhancementRefactoring maxCompute catalog using Storage API.(#40225 , #40888 ,#41386 )

bp #40225 , #40888 ,#41386
Proposed changes
Among them, #40225 is the new api of mc,
#40888 is used to fix the bug when reading null between the new and old apis,
#41386 is used for compatibility between the new and old versions

run buildall


Error: error loading model /root/.ollama/models/blobs when I use any other directory for the volume.

I am using docker-compose to create both the server and webgui of ollama. These compile fine. Going to either port shows that both are running. There are no errors in the logs. However, if I use exec in the container, or go to a console in portainer, there are problems loading any model (I tried openchat and llama2). It downloads the files fine, but then ends with the above error statement:
oot@c19165979f14:~/.ollama# ollama run openchat
pulling manifest
pulling 1cecc26325a1... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████▏ 4.1 GB
pulling 43070e2d4e53... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████▏  11 KB
pulling d68706c17530... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████▏   98 B
pulling 415f0f6b43dd... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████▏   65 B
pulling<PHONE_NUMBER>56... 100% ▕█████████████████████████████████████████████████████████████████████████████████████████████████▏  483 B
verifying sha256 digest
writing manifest
removing any unused layers
success
Error: error loading model /root/.ollama/models/blobs/sha256:1cecc26325a197571a1961bfacf64dc6e35e0f05faf57d3c6941a982e1eb2e1d

The problem seems to stem from trying to use a chosen directory to store all the data, instead of using /data/compose.  However, if I change that volume to something else, it fails. Changing permissions on that volume does not help.

Have you tried to create a symlink to the other volume?

Have you tried to create a symlink to the other volume?

No, I haven't, since idk how to do that. The directory is created by docker-compose automatically (with root owner, despite creating the container as user). I suppose that could be done after it is created by docker, and move everything? Would that persist on updates?
I suspected that maybe there was some assumption in the code about where it would be stored. It just seemed odd to me that we don't have the option to store the configuration wherever we want.

I, does this behavior changes by setting the env variable to the new folder in the container ?

Hi, can you try to set the env variable to the new folder in the container ?

Ahh, I missed that in the FAQs---my bad. Many thanks!