Move up and down the list with different bindings

This may be a very dumb question but I don't seem to figure this one out.
I recently started trying out your plugin (great work, btw) and I usually navigate the FZF items with ctrl-j and ctrl-k. I saw that the arrows worked but every time I tried the bindings I mentioned it just cancels and goes back to my buffer.
I tried:
require('fzf-lua').setup {
  keymap = {
    builtin = {
      -- [...]
      ["ctrl-j"] = "down",
      ["ctrl-k"] = "up",
    }
  },
  fzf = {
    ["ctrl-j"] = "down",
    ["ctrl-k"] = "up",
  },
}

But I can seem to make it work. Any hints on what I may be doing wrong?

Just run into the same issue :) Thanks for your great work btw.

Ty!

I'm trying to move from init.vim to init.lua settings. And with init.lua C-J and C-D do not work - they close the window. When I switched to init.vim - it works as suspected.  I tried this thing https://github.com/ibhagwan/fzf-lua/issues/170#issuecomment-936991432 without any luck.
My config.
local status_ok, fzf_lua = pcall(require, "fzf-lua")
if not status_ok then
  return
end
local actions = fzf_lua.actions

fzf_lua.setup ({
previewers = {
    git_diff = {
     pager           = "delta"
    }
},
files = {
    -- previewer         = "cat",       -- uncomment to override previewer
    prompt            = 'files❯ ',
    cmd               = "rg --files --no-ignore-vcs  -g '!*venv*' -g '!*node_modules*' -g '!*pyc*' -g '!*.environ' -g '!*dist*' -g '!*build'",             -- "find . -type f -printf '%P\n'",
    git_icons         = true,           -- show git icons?
    file_icons        = true,           -- show file icons?
    color_icons       = true,           -- colorize file|git icons
    actions = {
      -- set bind to 'false' to disable
      ["default"]     = actions.file_edit,
      ["ctrl-s"]      = actions.file_split,
      ["ctrl-v"]      = actions.file_vsplit,
      ["ctrl-t"]      = actions.file_tabedit,
      ["alt-q"]       = actions.file_sel_to_qf,
      -- custom actions are available too
      ["ctrl-y"]      = function(selected) print(selected[1]) end,
    }
  },
  keymap = {
    -- These override the default tables completely
    -- no need to set to `false` to disable a bind
    -- delete or modify is sufficient
    builtin = {
      -- neovim `:tmap` mappings for the fzf win
      ["<F2>"]        = "toggle-fullscreen",
      -- Only valid with the 'builtin' previewer
      ["<F3>"]        = "toggle-preview-wrap",
      ["<F4>"]        = "toggle-preview",
      -- Rotate preview clockwise/counter-clockwise
      ["<F5>"]        = "toggle-preview-ccw",
      ["<F6>"]        = "toggle-preview-cw",
      ["<C-d>"]    = "preview-page-down",
      ["<C-u>"]      = "preview-page-up",
      ["<S-left>"]    = "preview-page-reset",
    },
    fzf = {
      -- fzf '--bind=' options
      -- Only valid with fzf previewers (bat/cat/git/etc)
      -- ["ctrl-u"]        = "unix-line-discard",
      ["ctrl-j"] = "down",
      ["ctrl-k"] = "up",
      ["ctrl-f"]        = "half-page-down",
      ["ctrl-b"]        = "half-page-up",
      ["ctrl-a"]        = "beginning-of-line",
      ["ctrl-e"]        = "end-of-line",
      ["alt-a"]         = "toggle-all",
      -- Only valid with fzf previewers (bat/cat/git/etc)
      ["f3"]            = "toggle-preview-wrap",
      ["f4"]            = "toggle-preview",
    },
  },
grep = {
    prompt            = 'grep❯ ',
    input_prompt      = 'Grep For❯ ',
    git_icons         = true,           -- show git icons?
    file_icons        = true,           -- show file icons?
    color_icons       = true,           -- colorize file|git icons
    rg_opts = '--hidden --column --line-number --no-heading --color=always --smart-case -g "!node_modules/" -g "!idea" -g "!.vscode" -g "!venv" -g "!.mypy_cache" -g "!build" -g "!dist"  -g "!__pycache__" -g "!tags" -g "!*.git" -g "!package-lock.json" -g "!.environ" -g "!*pot"'
  },
})

@LoydAndrew, it sounds to me like your setup function isn’t being called when used with init.lua, not sure which package manager you’re using but if using packer you have to call your setup function as part of the config event.

There is a hundred percent it's loading. Cause I replace prompt input

What if you create an empty function with a print statement inside, does that get called?

you can use window_on_create or on_create, should be the same thing

require'fzf-lua'.setup {
  winopts = {
    on_create        = function()
      print("on_create")
    end,
  }
}

Yeah, it is called.

Can you post how do you define the mappings inside on_create?
Once fzf win hs open can you press <c-w>:tmap<cr> and post the output, this will show us if the <C-j> mapping exist

Can you help, please. How can I press this sequence :tmap ?
My definition of on_create function
            require("fzf-lua").setup({
                on_create = function()
                    local tnoremap = function(lhs, rhs)
                        vim.api.nvim_buf_set_keymap(0, "t", lhs, rhs, { silent = true, noremap = true })
                    end

                    print("on_create")
                    tnoremap("<c-j>", "<down>")
                    tnoremap("<c-k>", "<up>")
                end,

But, the thing is I don't even have this mapping when I'm using init.vim. But on init.lua it doesn't work anyway (with or without).

The same code you posted works fine on my setup, perhaps you have another conflicting bind somewhere, maybe another plugin that takes over that bind with it's defaults? that would explain why you didn't need these bindings with init.vim as ctrl-j|k are the default for up|down in fzf and do not need to be defined.
You can also try to force these binds inside fzf by adding the below to the keymap.fzf table:
  keymap = {
    fzf = {
      ...
      ...
      -- Copy the default binds and add these below
      ["ctrl-j"]        = "down",
      ["ctrl-k"]        = "up",
    },
  },

Note that if you have something else that overrides <C-j>|<C-k> inside neovim the above will likely not help as the neovim binds will have priority of the terminal binds.

Yes, thank you! Found that bastard in toggleterm mappings, sorry for that. While, I'm on it maybe you can help me with this question, cause it applies to mappings as well:
 keymap = {
    -- These override the default tables completely
    -- no need to set to `false` to disable a bind
    -- delete or modify is sufficient
    builtin = {
      -- neovim `:tmap` mappings for the fzf win
      ["<F2>"]        = "toggle-fullscreen",
      -- Only valid with the 'builtin' previewer
      ["<F3>"]        = "toggle-preview-wrap",
      ["<F4>"]        = "toggle-preview",
      -- Rotate preview clockwise/counter-clockwise
      ["<F5>"]        = "toggle-preview-ccw",
      ["<F6>"]        = "toggle-preview-cw",
      ["<C-d>"]    = "preview-page-down",
      ["<C-u>"]      = "preview-page-up",
      ["<S-left>"]    = "preview-page-reset",
    },
    fzf = {
      -- fzf '--bind=' options
      -- Only valid with fzf previewers (bat/cat/git/etc)
      -- ["ctrl-u"]        = "unix-line-discard",
      ["ctrl-j"] = "down",
      ["ctrl-k"] = "up",
      ["ctrl-f"]        = "half-page-down",
      ["ctrl-b"]        = "half-page-up",
      ["ctrl-a"]        = "beginning-of-line",
      ["ctrl-e"]        = "end-of-line",
      ["alt-a"]         = "toggle-all",
      -- Only valid with fzf previewers (bat/cat/git/etc)
      ["f3"]            = "toggle-preview-wrap",
      ["f4"]            = "toggle-preview",
    },
  },

These mappings work with  live_grep, find_files etc. But don't work with git commands. Is it intentantional, is there a way to make it work. Again, sorry for polluting this closed issue
[""]    = "preview-page-down",
[""]      = "preview-page-up",

No problem @LoydAndrew, with git commands the preview is not a neovim buffer (AKA the “builtin” previewer) but a previewer drawn by fzf itself, to scroll up/down in the fzf previewer you need to add two more fzf-style bindings (shift-down instead of <S-down> etc) under keymap.Fzf:

fzf = {
      …
      ["shift-down"]  = "preview-page-down",
      ["shift-up"]    = "preview-page-up",
    },


Fixed typo

tx for the fix, but that text is flawed and we'll have to revisit it ;)

I agree that a distributed infinispan cache is NOT appropriate for Modeshape usage. We have tried it, but it leads to horrible inconsistencies.

@hchiorean, go ahead and merge. We need to fix this file anyway like you did for the documentation.

Btw, use case where infinispan might work in distributed mode is where there is no shared cache store. Have not tried though.


Slow startup due DNS.

Title: One line description
Description:
Envoy is slow to get ready in my IPv6 cluster.
I install envoy 1.12.2 as a part of a contour environment with the attached manifest.
Envoy is installed as a DaemonSet. Some of the pods can take up to 140s to get ready.
I suspect some kind of race condition during startup. If I add a new initcontainer to the DaemonSet, Sleeping 5 seconds, the issue is not reproducible for me.
I do also have another cluster with only IPv4 addresses, and installing with the manifest I also do not see the issue.
The only things I changed compared to the original contour example is:

getting rid of the internal security.
changes in the args for envoy to be ready for v6 use
contour.txt

Repro steps:
kubectl apply -f contour.yaml
kubectl get pods -n projectcontour
NAME                       READY   STATUS    RESTARTS   AGE
contour-58f47b9d8c-4k664   1/1     Running   0          2m20s
contour-58f47b9d8c-rpkcv    1/1     Running   0          2m20s
envoy-k59m9                        0/1     Running   0          2m20s
envoy-n4kw4                        1/1     Running   0          2m20s
envoy-vnnq2                         1/1     Running   0          2m20s
envoy-xrnr9                           0/1     Running   0          2m20s
I can include the debug logs from envoy-k59m9
envoy.pod.log
envoy.json used as config.
envoy.config.txt

Hi, Any ideas or questions? This is highly reproducible in multiple clusters.

Hi
I poked around the issue, as a novice.
I recorded some tcpdumps that I unfortunately can not share.
To my eye it seemed like the following happening:

Envoy starts up as a part of a contour cluster
when the pod starts in a v6 only cluster, the interface not immediately receives a global address, for a little while the only address on the interface is ::1
as soon as envoy starts it starts dns queries for the contour service. at first using the 1:: as source address?
In the meantime the interface has a working v6 IP address, and other traffic starts working
Envoy for some reason still uses the 1:: as source address for the DNS queries, resulting no answer.
Envoy hangs in this state until some external force (killed by liveness probe)

I'm not sure about the inner working of envoy, can it be that envoy chooses a source address for it's dns queries and not updating that with interface changes?

Looks like the underlying ares library create the socket fd to dns server.
It's not clear to me when that socket is created, what source address is bind. It's would be nice if Envoy has an ares channel rotation
A workround would be a  bootloader for envoy, heuristically, the bootloader starts envoy after a non ::1 address on nic


Does WSO2 EMM provide an abstraction layer API for push notifications to simplify app development?

Hi,
We are very interested in WSO2 EMM and considering migrate HP Anywhere to WSO2. Does WSO2 provide an abstraction layer for push notifications for app developers, in other words, how do I migrate existing apps in production to WSO2 with minimal code change in push notifications from HP Anywhere mobility framework?
In a nutshell, does WSPO2 provide a simple API to simplify implementing push notifications for app developers, pretty much the same way as HP Anywhere can do here:
HP Anywhere:
http://docs.hpanywhere.com/wp-content/uploads/10.12/HP_Anywhere_Online_Help/Default.htm#Best_Practices/Push_Notifications.htm
http://docs.hpanywhere.com/wp-content/uploads/10.12/HP_Anywhere_API_Reference/webframe.html#Simple_Push.html
BTW, where can I find an official forum for EMM (http://wso2.com/forums has none for EMM) discussions monitored by WSO2?
Thank you.
J

You can raise or open discussions in<EMAIL_ADDRESS>You should be looking at MDM 2.0 (https://github.com/wso2/product-mdm) which is the next version of EMM which is yet to release in May. In MDM 2.0 these will be exposed as APIs. If you have further questions you may raise them in stackoverflow with the tag wso2.

Thanks for the reply. Can you point me to the right code/folder for that API - abstraction layer to simply push notification implementation for app developers for different platforms(iOS, Android, Windows etc..) as seen in HP Anywhere, SAP SAP Kapsel Push plugin, Apache Cordova PushPlugin, etc..?
Also do you have a version that we can test run this product?
J

MDM suite only focuses on push notification strategies which is needed for MDB operations. Like send messages etc. However as app developers this is not the ideal way to integrate such services. Such push notifications only focuses on one single app which is the agent application for that corresponding platform. Hence ideally you might have to extend this behavior and derive your own to support such. Anyway the implementation of this in progress and will be available soon.


New subgraph via cli, yarn test tries to download 0.6.0/binary-linux-20 (not existing) instead of 0.6.0/binary-linux-22

Summary
Result: on Linux yarn test tries to download (inexisting, 404 error) https://github.com/LimeChain/matchstick/releases/download/0.6.0/binary-linux-20
Expected result: yarn test should download https://github.com/LimeChain/matchstick/releases/download/0.6.0/binary-linux-22
Details
Hi,
My OS: Fedora Liunux 39
Node version: v18.x LTS, tried also v20.x LTS
I'm creating a subgraph using the cli, see https://thegraph.com/docs/en/developing/creating-a-subgraph/#from-an-existing-contract
This creates a package.json as follows:
{
  "name": "my-test",
  "scripts": {
    "codegen": "graph codegen",
    "build": "graph build",
    "test": "graph test"
  },
  "dependencies": {
    "@graphprotocol/graph-cli": "0.51.0",
    "@graphprotocol/graph-ts": "0.30.0"
  },
  "devDependencies": { "matchstick-as": "0.5.0" }

When I run yarn test I get this error:
yarn test
yarn run v1.22.21
$ graph test
Fetching latest version tag...
Downloading release from https://github.com/LimeChain/matchstick/releases/download/0.6.0/binary-linux-20
Error fetching release: Request failed with status code 404
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I did yarn upgrade matchstick-as, which downloaded 0.6.0. When I run yarn test I get the exact same error. Seems both 0.5 and 0.6 try to download the file 0.6.0/binary-linux-20.
But the correct file is 0.6.0/binary-linux-22
Full URL: https://github.com/LimeChain/matchstick/releases/download/0.6.0/binary-linux-22
You can double check at https://github.com/LimeChain/matchstick/releases/tag/0.6.0
Can you fix this please? So that all subgraph users on Linux can use matchstick for testing without hassle*?
*"Hassle": I guess (hope) there is a workaround like manually downloading binary-linux22 and placing it somewhere? Can you tell me how/where until this is fixed? Thank you

Hi, the version which will be downloaded depends on the graph-cli and is defined by this function https://github.com/graphprotocol/graph-tooling/blob/main/packages/cli/src/commands/test.ts#L175-L231
There's a workaround for unsupported platforms, you can use docker to run the test by passing -d flag to the test command https://thegraph.com/docs/en/developing/unit-testing-framework/#docker
Further development of matchstick (for the time being) will be handled by TheGraph in the tooling repo https://github.com/graphprotocol/graph-tooling/pull/1549


Use React.cloneElement() for child elements.

Eliminates
Warning: Don't set .props.onClick of the React component <h3 />.
...
Warning: Don't set .props.className of the React component <h3 />.

on the http://elemental-ui.com/buttons page.

Off-topic question:
Why are you guys using TABs instead of 2xSpaces ?
I'm asking it  because of the weird GitHub diffs formatting.
http://stackoverflow.com/research/developer-survey-2015#tech-tabsspaces :wink:

Upon closer examination of the data, a trend emerges: Developers increasingly prefer spaces as they gain experience. Stack Overflow reputation correlates with a preference for spaces, too: users who have 10,000 rep or more prefer spaces to tabs at a ratio of 3 to 1.

I could help to migrate to spaces :wink:

This is an elegant solution, thanks Alex.

Regarding tabs vs spaces - we use tabs, that's just how it is. Need to put together a contributing.md file for this project

Regarding tabs vs spaces - we use tabs, that's just how it is.

No problem of course :cherries:
That was just my curiosity.

@AlexKVal @jossmac don't mind my commits here - I misunderstood how React.cloneElement deals with existing props, unfortunately read up on it after making the change so I merged it back.
Great solution @AlexKVal, thanks.

:blush:


For CoxPH - Parametric(baseline_estimation_method='spline'), given below scenarios need to be fixed for censored observations

Methods predict_cumulative_hazard() and predict_survival_function() when used with 'times' parameter do not show the effect of using 'times' parameter - means that the output of methods predict_cumulative_hazard() and predict_survival_function() have all time periods starting from min time period of training dataset to max time period of training dataset and the 'times' parameter does not have any effect on the output.

With regards to method predict_median(), I did observe many censored subjects for whom all(corresponding to different time periods) of survival probabilities are greater than 0.5 , but still then the corresponding median lifetime value is INFINITY.

Attaching python program (Cox_PH_Model_Parametric_GridSearchCV_sent_Cam_July_07_2020.txt) to replicate scenario.
Cox_PH_Model_Parametric_GridSearchCV_sent_Cam_July_07_2020.txt

is fixed in the latest lifelines, as for 2. can you isolate the problem into a smaller script and please open a more specific issue?


Updated npmignore (ignore .github folder)

added the / with commit b28c6c1e7cc88d69bb5188d69988a42b68cd2ac0.

Thanks, sorry I didn't see the mail notification :)

I reviewed this while sleepy and busy with conference stuff, I apologize. It should not have been merged - we WANT the .github folder for including our issue templates. I will push a revert.

Aaand I'm wrong again, this was for .npmignore. I should really not try to review things within like 7 days of travel. Sorry for the noise.

No worries ;-)
Great work for the conference btw, I'm still busy watching the videos


Error in the Query field - Field must contain valid SQL to be run against osquery tables

Hi,
We have windows machines with osqueryd installed pointing to doorman with the flags to be able to read the windows events:
--disable_events=false
--windows_event_channels='System,Application,Setup,Security'
When we try to create a query for the windows_events table we get this error:

Thanks.
Best regards.

Hey @rubenrodr-versia - we haven't updated the osquery schema we used to validate queries against in a while, but will shortly. I'll update this ticket once that's done and you can fetch a new release.
In the mean time, you can update the DOORMAN_EXTRA_SCHEMA configuration value with the following (and restart the Doorman app):
DOORMAN_EXTRA_SCHEMA = [
  'CREATE TABLE windows_events (time BIGINT, datetime TEXT, source TEXT, provider_name TEXT, provider_guid TEXT, eventid INTEGER, task INTEGER, level INTEGER, keywords BIGINT, data TEXT, eid TEXT);'
]

For context, we create an in-memory sqlite database to validate that queries will execute successfully. This database (because the schema hasn't been updated in a while), doesn't include the windows_events table, which can be overridden by updating the DOORMAN_EXTRA_SCHEMA configuration parameter.


Issue speccing with .net7.0

Currently, this version of yak is unable to spec assemblies built with .net7.0.
By "this version" I am referring to the files being fetched from https://files.mcneel.com/yak/tools/latest/yak.exe.
See here, here and here for further information.

Hi @kastnerp! thanks for bringing this up!
It's been a minute since i set this up so I'm not surprised something broke eventually 😅
I assume this will be "fixed automatically" when McNeel releases a new version with this fix, so I'll poke them in the forums too! 🙌🏼


Switch to git based repository in OBS

Part of rancher/elemental-obs#18

e2e tests will fail as they rely on a longer valid OBS build for PRs which won't be happening anymore after merging this. I'd like to track elemental-operator e2e tests in a separate issue. After moving Dev to git, e2e tests on PRs should be reconsidered.


outcome not in line with expectations (1 hour off)

Hi, I have been playing around with the tool for a few days and found that the outcome is not optimal, eg. in this case one hour off; what's the best way to debug?
I want the start time for the cheapest 4 hour period in a max 24 hour time horizon (rolling) - based on the nordpool sensor my binary planning sensor generates 19:00 with an average cost of 41cents [calculation is correct adding up 19 - 23pm / 4]; however, starting one hour later (20:00) would generate a lower average of 35cents. Any thoughts what I am doing wrong?
YAML code:
 binary_sensor:
 -  platform: nordpool_planner
    nordpool_entity: sensor.nordpool_kwh_nl_eur_3_10_009
    entity_id: optimal_start_time_dishwasher
    duration: 4
    moving:
      search_length: 24

Used nordpool data:
  - start: '2022-11-29T19:00:00+01:00'
    end: '2022-11-29T20:00:00+01:00'
    value: 0.506
  - start: '2022-11-29T20:00:00+01:00'
    end: '2022-11-29T21:00:00+01:00'
    value: 0.436
  - start: '2022-11-29T21:00:00+01:00'
    end: '2022-11-29T22:00:00+01:00'
    value: 0.365
  - start: '2022-11-29T22:00:00+01:00'
    end: '2022-11-29T23:00:00+01:00'
    value: 0.324
  - start: '2022-11-29T23:00:00+01:00'
    end: '2022-11-30T00:00:00+01:00'
    value: 0.278

It does not seem you are doing anything wrong, but the plug-in is doing something wrong.

The only way I know of to debug is to run it in the HASS development environment. Once you find the guide it's quite easy to follow and setup, and integrates well with VS Code.

Hi. Found your custom HACS integration and found it very cool. Thanks for your job! :)
As mentioned before - seems that best period found by sensor is off by 1 hour as commmented in 1st post.
I'm not good at programming at all, but hope You will find time to look at code any time soon :)

After fixing #13 in #14 I also found a spot in prices to try to reproduce this issue but seem to function as expected, could be that #14 fixed this one as well. Please update to v.0.2.3 and see if you agree.
binary_sensor:
  - platform: nordpool_planner
    entity_id: moving_1
    nordpool_entity: sensor.nordpool_kwh_se3_sek_3_10_025
    duration: 3
    moving:
      search_length: 6

Ignore noise in binary sensor history graph before 13:30 as that was during my testing of other prameters

Hi.
I play around with the planner the last days, because I want to charge my Luna Battery automaticly, when the prices are at the lowest at that day.
I used the planner, and I had the same issue like @ronaldt80 reported it. But at my setup, with a 3 hour off, today or better tomorrow night is the lowest price at 3, but the planner activate at 0.

Nordpool Data:
- start: '2023-12-28T22:00:00+01:00'
end: '2023-12-28T23:00:00+01:00'
value: 1.772
- start: '2023-12-28T23:00:00+01:00'
end: '2023-12-29T00:00:00+01:00'
value: 0.1
Raw tomorrow
- start: '2023-12-29T00:00:00+01:00'
end: '2023-12-29T01:00:00+01:00'
value: 0
- start: '2023-12-29T01:00:00+01:00'
end: '2023-12-29T02:00:00+01:00'
value: -0.008
- start: '2023-12-29T02:00:00+01:00'
end: '2023-12-29T03:00:00+01:00'
value: -0.028
- start: '2023-12-29T03:00:00+01:00'
end: '2023-12-29T04:00:00+01:00'
value: -0.093
- start: '2023-12-29T04:00:00+01:00'
end: '2023-12-29T05:00:00+01:00'
value: -0.095
- start: '2023-12-29T05:00:00+01:00'
end: '2023-12-29T06:00:00+01:00'
value: -0.026

My binary sensor:
binary_sensor:
  - platform: nordpool_planner
    nordpool_entity: sensor.nordpool_kwh_de_lu_eur_4_10_0
    entity_id: Planner
    duration: 2

    moving:
      search_length: 24

My expectation is, the the binary sensor activate at 3am and ends at 5am.
What I'm doing wrong? (I'm relative new to HA and all these things, but I can't solve this at the moment, cause I didn't know what to look after... ;-)
What do you need for files, maybe this is a bug? I would like to send you debug files, but I struggle to get them at the moment... Sorry.
Maybe you have an idea how to solve it?
Thanks in advance.
Kind regards.
Daniel

Good morning.
An addition to the problem.
The binary sensor activated at 1am last night when the price was below 0 cent, until 8am this morning when the price was above 0 cent.
This suggests that the problem could be with prices below 0 cent.
Please find attached my Nordpool prices and the status of the sensor last night.
I would be pleased to receive a reply.
Thank you very much.
Best regards
Daniel
today: 0, -0.008, -0.028, -0.093, -0.095, -0.026, -0.007, -0.001, 0.444, 0.109, 0.005, -0.001, 0.06, 0.099, 0.223, 0.999, 1.002, 2.512, 2.659, 1.717, 1.01, 0.504, 2.29, 1.889
tomorrow:
tomorrow_valid: false
raw_today:
- start: '2023-12-29T00:00:00+01:00'
  end: '2023-12-29T01:00:00+01:00'
  value: 0
- start: '2023-12-29T01:00:00+01:00'
  end: '2023-12-29T02:00:00+01:00'
  value: -0.008
- start: '2023-12-29T02:00:00+01:00'
  end: '2023-12-29T03:00:00+01:00'
  value: -0.028
- start: '2023-12-29T03:00:00+01:00'
  end: '2023-12-29T04:00:00+01:00'
  value: -0.093
- start: '2023-12-29T04:00:00+01:00'
  end: '2023-12-29T05:00:00+01:00'
  value: -0.095
- start: '2023-12-29T05:00:00+01:00'
  end: '2023-12-29T06:00:00+01:00'
  value: -0.026
- start: '2023-12-29T06:00:00+01:00'
  end: '2023-12-29T07:00:00+01:00'
  value: -0.007
- start: '2023-12-29T07:00:00+01:00'
  end: '2023-12-29T08:00:00+01:00'
  value: -0.001
- start: '2023-12-29T08:00:00+01:00'
  end: '2023-12-29T09:00:00+01:00'
  value: 0.444
- start: '2023-12-29T09:00:00+01:00'
  end: '2023-12-29T10:00:00+01:00'
  value: 0.109
- start: '2023-12-29T10:00:00+01:00'
  end: '2023-12-29T11:00:00+01:00'
  value: 0.005
- start: '2023-12-29T11:00:00+01:00'
  end: '2023-12-29T12:00:00+01:00'
  value: -0.001
- start: '2023-12-29T12:00:00+01:00'
  end: '2023-12-29T13:00:00+01:00'
  value: 0.06
- start: '2023-12-29T13:00:00+01:00'
  end: '2023-12-29T14:00:00+01:00'
  value: 0.099
- start: '2023-12-29T14:00:00+01:00'
  end: '2023-12-29T15:00:00+01:00'
  value: 0.223
- start: '2023-12-29T15:00:00+01:00'
  end: '2023-12-29T16:00:00+01:00'
  value: 0.999
- start: '2023-12-29T16:00:00+01:00'
  end: '2023-12-29T17:00:00+01:00'
  value: 1.002
- start: '2023-12-29T17:00:00+01:00'
  end: '2023-12-29T18:00:00+01:00'
  value: 2.512
- start: '2023-12-29T18:00:00+01:00'
  end: '2023-12-29T19:00:00+01:00'
  value: 2.659
- start: '2023-12-29T19:00:00+01:00'
  end: '2023-12-29T20:00:00+01:00'
  value: 1.717
- start: '2023-12-29T20:00:00+01:00'
  end: '2023-12-29T21:00:00+01:00'
  value: 1.01
- start: '2023-12-29T21:00:00+01:00'
  end: '2023-12-29T22:00:00+01:00'
  value: 0.504
- start: '2023-12-29T22:00:00+01:00'
  end: '2023-12-29T23:00:00+01:00'
  value: 2.29
- start: '2023-12-29T23:00:00+01:00'
  end: '2023-12-30T00:00:00+01:00'
  value: 1.889

starts_at: 2023-12-29 10:00
cost_at: 0.002
now_cost_rate: 222
icon: mdi:flash
friendly_name: nordpool_planner_Planner

Good morning.
So, today is another day while the planner switch to on and it is not the cheapest time of the day, later it was "cheaper", but another issue, the price is gone up to 4ct. and the planner did not switch off. Take a look in the attachment.
Do you have any ideas to solve this?
Thanks in advance,
Kind regards.
Daniel

Average
4,52
Off peak 1
0,44
Off peak 2
6,59
Peak
6,55
Min
-0,14
Max
8,3
Mean
5,76
Unit
kWh
Currency
EUR
Country
Germany and Luxembourg
Region
DE-LU
Low price
true
Price percent to average
0,9
Today
-0,01, -0,12, -0,13, -0,13, -0,13, -0,14, 0,11, 4,06, 5,96, 6,06, 5,7, 5,49, 5,39, 5,44, 6,09, 6,72, 7,36, 8,23, 8,3, 7,9, 7,32, 6,74, 6,5, 5,81
Tomorrow
Tomorrow valid
false
Raw today
- start: '2024-01-03T00:00:00+01:00'
end: '2024-01-03T01:00:00+01:00'
value: -0.008
- start: '2024-01-03T01:00:00+01:00'
end: '2024-01-03T02:00:00+01:00'
value: -0.123
- start: '2024-01-03T02:00:00+01:00'
end: '2024-01-03T03:00:00+01:00'
value: -0.13
- start: '2024-01-03T03:00:00+01:00'
end: '2024-01-03T04:00:00+01:00'
value: -0.131
- start: '2024-01-03T04:00:00+01:00'
end: '2024-01-03T05:00:00+01:00'
value: -0.131
- start: '2024-01-03T05:00:00+01:00'
end: '2024-01-03T06:00:00+01:00'
value: -0.138
- start: '2024-01-03T06:00:00+01:00'
end: '2024-01-03T07:00:00+01:00'
value: 0.109
- start: '2024-01-03T07:00:00+01:00'
end: '2024-01-03T08:00:00+01:00'
value: 4.059
- start: '2024-01-03T08:00:00+01:00'
end: '2024-01-03T09:00:00+01:00'
value: 5.961
- start: '2024-01-03T09:00:00+01:00'
end: '2024-01-03T10:00:00+01:00'
value: 6.061
- start: '2024-01-03T10:00:00+01:00'
end: '2024-01-03T11:00:00+01:00'
value: 5.7
- start: '2024-01-03T11:00:00+01:00'
end: '2024-01-03T12:00:00+01:00'
value: 5.489
- start: '2024-01-03T12:00:00+01:00'
end: '2024-01-03T13:00:00+01:00'
value: 5.389
- start: '2024-01-03T13:00:00+01:00'
end: '2024-01-03T14:00:00+01:00'
value: 5.442
- start: '2024-01-03T14:00:00+01:00'
end: '2024-01-03T15:00:00+01:00'
value: 6.086
- start: '2024-01-03T15:00:00+01:00'
end: '2024-01-03T16:00:00+01:00'
value: 6.718
- start: '2024-01-03T16:00:00+01:00'
end: '2024-01-03T17:00:00+01:00'
value: 7.359
- start: '2024-01-03T17:00:00+01:00'
end: '2024-01-03T18:00:00+01:00'
value: 8.228
- start: '2024-01-03T18:00:00+01:00'
end: '2024-01-03T19:00:00+01:00'
value: 8.297
- start: '2024-01-03T19:00:00+01:00'
end: '2024-01-03T20:00:00+01:00'
value: 7.903
- start: '2024-01-03T20:00:00+01:00'
end: '2024-01-03T21:00:00+01:00'
value: 7.323
- start: '2024-01-03T21:00:00+01:00'
end: '2024-01-03T22:00:00+01:00'
value: 6.741
- start: '2024-01-03T22:00:00+01:00'
end: '2024-01-03T23:00:00+01:00'
value: 6.5
- start: '2024-01-03T23:00:00+01:00'
end: '2024-01-04T00:00:00+01:00'
value: 5.812
Raw tomorrow
Current price
4,06
Additional costs current hour
0
Price in cents
true

Hi, have not really thought of negative prices until now. Spontaneously I would say it should work just fine, but apparently there is something strange happening.
I actually think I may have found something there where both the ACCEPT_COST and ACCEPT_RATE default to 0.0. And seem they are locked to not being possible to set negative values.
        vol.Optional(ACCEPT_COST, default=0.0): vol.All(
            vol.Coerce(float), vol.Range(min=0.0, max=10000.0)
        ),
        vol.Optional(ACCEPT_RATE, default=0.0): vol.All(
            vol.Coerce(float), vol.Range(min=0.0, max=10000.0)
        ),

One could try to allow negative range but specially the ACCEPT_RATE I'm not so sure how large negative value must be allowed.
In the example from 2023-12-29 it should not activate until the two [-0.093, -0.095] 03:00 and 04:00 (which has the lowest average in the up to 24h span ahead).
On the other hand it should likely not switch off when that time has passed as the "moving 24h" only looks at prices in the future. So at 07:00 when the price is -0.001 it's still the cheapest looking in the future.

Hello,
thanks for your answer.
The planner ignores the default duration completely, also my individual setting does not work.
It doesn't matter what is in the binary sensor. My workaround is, that I set the duration max=5 in /homeassistant/custom_components/nordpool_planner/binary_sensor.py to what I need, but this is only a workaround.

I have now published a pre-release of v2.0 (#33 & #31 ) which completely we-works the integration, both how it is configured but also how the searching for lowest (and highest) cost. If you want to please try it and give feedback if it helps.

With release of version 2 #45 I'm closing this as the code is completely rewritten. But feel free to reopen or create new issue if similar problem is still seen.


Enable data race safety label on package pages

We want this to go live with the blog post, don't we?

We do, but that's several days away.
We can enable this as soon as the run is complete, though. 👍

Several days? It should be done in the morning!

Several days? It should be done in the morning!

I meant the blog post. That will take several days of review etc…


Follow the XDG Base Directory Specification

Expands https://github.com/YosysHQ/yosys/pull/4093 PR by moving code and display messages only if used with debug parameter, since yosys is fully functional without setting variables, and also history is only useful in interactive mode, and logs could spam users using it for scripting.

As a side effect, if -g is not used and it can't create the file, this now prints <suppressed ~1 debug messages> after the first command that you run. This is a bit misleading since it happened before the first command, should we call log_suppressed() before, e.g. in yosys_setup()? That would print it before the first prompt which is more suitable IMO:
 /----------------------------------------------------------------------------\
   <header snipped>
 \----------------------------------------------------------------------------/

 Yosys 0.37+90 (git sha1 2797d6756, clang 15.0.0 -fPIC -Os)

<suppressed ~1 debug messages>

yosys>

Actually, maybe driver.cc:593 (after load_plugin) would be an even better place to put it, that way it accommodates plugins using log_debug during registration as well.


Showcase Submission for challenges/c5-marching-squares

Thank you Christian Manderla for your contribution! A member of the Coding Train team will review it shortly.

Marching Hexes
Christian Manderla

So cool!


No support for multiple commands in run

I tried to add tables for two days.
The query was:
db.run(`
    PRAGMA foreign_keys = ON;
    CREATE TABLE pkgs( .... );
    CREATE TABLE subs( ... );
`);

And this query do nothing. Wow!
The bug is only first command runs!
Solution? Yey, just change db.run to db.exec.
Please, fix multiple commands in run or tell about this on wiki docs.
sqlite3 version: 4.0.6
node version: 11.7.0

Just stumbled across this. Is it true that .run() and .get() only execute the first sql command/query in the given string argument?

Spent much time struggling with this.
Another thing you might want to know:  .exec doesn't accept any param.


Exception in Tkinter Callback During myCobot 280 Pi Calibration

Description
I am encountering an issue with my myCobot 280 Pi during the calibration process. The error occurs when running the rasp_mycobot_test_gui.py script. The script fails with a Tkinter callback exception. This issue is preventing me from completing the calibration process.
Steps to Reproduce

Ran the rasp_mycobot_test_gui.py script on a Raspberry Pi connected to myCobot 280 Pi.
Selected the appropriate serial port (/dev/ttyAMA0) and baud rate (115200 or 1000000). // I tried to use both
Attempted to calibrate the robot arm by clicking the "Start Calibration" button.

docs.elephantrobotics.com/docs/gitbook-en/4-BasicApplication/4.2-firmwares_intro/4.2.2-calibration/<IP_ADDRESS>-micro_CPU.html
Expected Behavior
The calibration process should start, and the robot arm should respond accordingly without any errors.
Actual Behavior
An exception is thrown in the Tkinter callback when the calibration function is invoked. The detailed error message is as follows:
Exception in Tkinter callback
Traceback (most recent call last):
  File "/usr/lib/python3.8/tkinter/__init__.py", line 1892, in __call__
    return self.func(*args)
  File "rasp_mycobot_test_gui.py", line 216, in calibration_mycobot
    self.mycobot.send_angle(self.calibration_num, 0, 0)
  File "/home/user/.local/lib/python3.8/site-packages/pymycobot/generate.py", line 246, in send_angle
    self.calibration_parameters(class_name=self.classname, id=id, angle=degree, speed=speed)
  File "/home/user/.local/lib/python3.8/site-packages/pymycobot/error.py", line 295, in calibration_parameters
    public_check(parameter_list, kwargs, robot_limit, class_name, MyCobotDataException)
  File "/home/user/.local/lib/python3.8/site-packages/pymycobot/error.py", line 108, in public_check
    raise exception_class("speed value not right! should be 1 ~ 100, the received speed is 0")
pymycobot.error.MyCobotDataException: speed value not right! should be 1 ~ 100, the received speed is 0

Environment

myCobot 280 Pi
Raspberry Pi
Atom v6.5

The last parameter of the send_angle interface ranges from 1 to 100. Please modify line 216 of the rasp_mycobot_test_gui.py file and change self.mycobot.send_angle(self.calibration_num, 0, 0) to self.mycobot.send_angle(self.calibration_num , 0, 20)


Fixes #100 : Use row major matrices rather than the default column major matrices

Use row major matrices rather than the default column major matrices in the vertex shaders. Also fixed incorrect window title names in the RasterizerState(1-3-5) and Camera(1-3-6) chapter source codes.

We could mention the reason of using row_major matrices in the markdown files for chapter 1-1-3-hello-triangle, as it mentions this:

To do this we will use DirectXMath which has types that map perfectly to HLSL, both of our inputs are float3 in HLSL, which means that this translates to DirectX::XMFLOAT3.

None of the chapters that actually use matrices have docs ready for them yet.
Should I add a note about DirectX::XMMatrix / DirectX::XMFLOAT4x4 beneath the notes on vector?

I think that's a good idea. Yes please.

OK, as discussed on discord, lets keep the XMMATRIX block of explanation for future chapters where matrices are actually used. This PR shall just fix the dissonance between column/row majorisms


Dashboard 'Technology Issue Scores' and 'High Score Items' not loading

Does anybody have any ideas why I get this error in the dashboard view?
Everything else is working perfectly.
main.dart.js:40376 GET https://URL/api/1/items?accounts=PD-AWS-Live&accounttypes=&active=true&count=1000000000&names=&page=1&regions=&summary=true&technologies= 500 (INTERNAL SERVER ERROR)
main.dart.js:43764 HTTP 500: {"message": "Internal Server Error"}
STACKTRACE:
null

I installed the SM as production, two UI servers under ALB, one scheduler server, and two workers servers.
I've got the same problem
"Dashboard 'Technology Issue Scores' and 'High Score Items' not loading."
where I can find the API logs ?

Hi. I am also facing the same problem. Every menu inside the SM UI works great, but the 'Technology Issue Scores' and 'High Score Items' dashboards does not.
When the UI requests the API:
/api/1/items?accounts=REDACTED&accounttypes=&active=true&count=1000000000&names=&page=1&regions=&summary=true&technologies=
It receives an HTTP 500 error with the following message:
{"message": "Internal Server Error"}
The error that is throw in the logs is:
2018-11-22 09:19:58,058 ERROR: Exception on /api/1/items [GET] [in /usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask-0.12.4-py2.7.egg/flask/app.py:1560] Traceback (most recent call last):   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask-0.12.4-py2.7.egg/flask/app.py", line 1612, in full_dispatch_request     rv = self.dispatch_request()   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask-0.12.4-py2.7.egg/flask/app.py", line 1598, in dispatch_request     return self.view_functions[rule.endpoint](**req.view_args)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask_RESTful-0.3.6-py2.7.egg/flask_restful/__init__.py", line 480, in wrapper     resp = resource(*args, **kwargs)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask-0.12.4-py2.7.egg/flask/views.py", line 84, in view     return self.dispatch_request(*args, **kwargs)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask_RESTful-0.3.6-py2.7.egg/flask_restful/__init__.py", line 595, in dispatch_request     resp = meth(*args, **kwargs)   File "/usr/local/src/security_monkey/security_monkey/views/item.py", line 270, in get     items = query.paginate(page, count)   File "/usr/local/src/security_monkey/venv/lib/python2.7/site-packages/Flask_SQLAlchemy-1.0-py2.7.egg/flask_sqlalchemy/__init__.py", line 405, in paginate     items = self.limit(per_page).offset((page - 1) * per_page).all()   File "build/bdist.linux-x86_64/egg/sqlalchemy/orm/query.py", line 2773, in all     return list(self)   File "build/bdist.linux-x86_64/egg/sqlalchemy/orm/query.py", line 2925, in __iter__     return self._execute_and_instances(context)   File "build/bdist.linux-x86_64/egg/sqlalchemy/orm/query.py", line 2948, in _execute_and_instances     result = conn.execute(querycontext.statement, self._params)   File "build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py", line 948, in execute     return meth(self, multiparams, params)   File "build/bdist.linux-x86_64/egg/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection     return connection._execute_clauseelement(self, multiparams, params)   File "build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement     compiled_sql, distilled_params   File "build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py", line 1200, in _execute_context     context)   File "build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception     exc_info   File "build/bdist.linux-x86_64/egg/sqlalchemy/util/compat.py", line 203, in raise_from_cause     reraise(type(exception), exception, tb=exc_tb, cause=cause)   File "build/bdist.linux-x86_64/egg/sqlalchemy/engine/base.py", line 1193, in _execute_context     context)   File "build/bdist.linux-x86_64/egg/sqlalchemy/engine/default.py", line 507, in do_execute     cursor.execute(statement, parameters) ProgrammingError: (psycopg2.ProgrammingError) table name "account" specified more than once  [SQL: 'SELECT anon_1.item_id AS anon_1_item_id, anon_1.item_region AS anon_1_item_region, anon_1.item_name AS anon_1_item_name, anon_1.item_arn AS anon_1_item_arn, anon_1.item_latest_revision_complete_hash AS anon_1_item_latest_revision_complete_hash, anon_1.item_latest_revision_durable_hash AS anon_1_item_latest_revision_durable_hash, anon_1.item_tech_id AS anon_1_item_tech_id, anon_1.item_account_id AS anon_1_item_account_id, anon_1.item_latest_revision_id AS anon_1_item_latest_revision_id, anon_1.itemrevision_date_created AS anon_1_itemrevision_date_created, itemaudit_1.id AS itemaudit_1_id, itemaudit_1.score AS itemaudit_1_score, itemaudit_1.issue AS itemaudit_1_issue, itemaudit_1.notes AS itemaudit_1_notes, itemaudit_1.action_instructions AS itemaudit_1_action_instructions, itemaudit_1.background_info AS itemaudit_1_background_info, itemaudit_1.origin AS itemaudit_1_origin, itemaudit_1.origin_summary AS itemaudit_1_origin_summary, itemaudit_1.class_uuid AS itemaudit_1_class_uuid, itemaudit_1.fixed AS itemaudit_1_fixed, itemaudit_1.justified AS itemaudit_1_justified, itemaudit_1.justified_user_id AS itemaudit_1_justified_user_id, itemaudit_1.justification AS itemaudit_1_justification, itemaudit_1.justified_date AS itemaudit_1_justified_date, itemaudit_1.item_id AS itemaudit_1_item_id, itemaudit_1.auditor_setting_id AS itemaudit_1_auditor_setting_id, technology_1.id AS technology_1_id, technology_1.name AS technology_1_name, account_1.id AS account_1_id, account_1.active AS account_1_active, account_1.third_party AS account_1_third_party, account_1.name AS account_1_name, account_1.notes AS account_1_notes, account_1.identifier AS account_1_identifier, account_1.account_type_id AS account_1_account_type_id \nFROM (SELECT item.id AS item_id, item.region AS item_region, item.name AS item_name, item.arn AS item_arn, item.latest_revision_complete_hash AS item_latest_revision_complete_hash, item.latest_revision_durable_hash AS item_latest_revision_durable_hash, item.tech_id AS item_tech_id, item.account_id AS item_account_id, item.latest_revision_id AS item_latest_revision_id, itemrevision.date_created AS itemrevision_date_created \nFROM item JOIN itemrevision ON item.latest_revision_id = itemrevision.id JOIN account ON account.id = item.account_id JOIN account ON account.id = item.account_id \nWHERE account.name IN (%(name_1)s) AND itemrevision.active = true AND account.active = true ORDER BY itemrevision.date_created DESC \n LIMIT %(param_1)s OFFSET %(param_2)s) AS anon_1 LEFT OUTER JOIN (issue_item_association AS issue_item_association_1 JOIN itemaudit AS itemaudit_1 ON itemaudit_1.id = issue_item_association_1.super_issue_id) ON anon_1.item_id = issue_item_association_1.sub_item_id LEFT OUTER JOIN technology AS technology_1 ON technology_1.id = anon_1.item_tech_id LEFT OUTER JOIN account AS account_1 ON account_1.id = anon_1.item_account_id ORDER BY anon_1.itemrevision_date_created DESC'] [parameters: {'name_1': '<REDACTED>', 'param_1':<PHONE_NUMBER>, 'param_2': 0}] (Background on this error at: http://sqlalche.me/e/f405)
Apparently this is the main error:
ProgrammingError: (psycopg2.ProgrammingError) table name "account" specified more than once (...)

@mikegrima
Hi again.
I believe that I might have found the issue. The stack trace complains about an error in:
"/usr/local/src/security_monkey/security_monkey/views/item.py", line 270, in get items = query.paginate(page, count) File
Looking for the query it is possible to identify that this join is made three times in the query (lines 228, 232 and 251):
            query = query.join((Account, Account.id == Item.account_id))
I have commented out lines 232 and 251 and kept line 228, then restarted SM and the two dashboards loaded normally.
One note: the query appears to be big and runs slowly, at least using a local Postgres only for testing.
Could someone, please, review this to see if it will not break any other functionality in SM?

Thanks, works
If I find some issue, I'll let you know.

Please submit a PR with the fix, and I will merge it in.

Merged in #1153 . Please test that things are working now.

Will test and let you know. Thanks for your time.


Per user datafiles

This should be very big optimisation boost for servers with large number of players. All file-saving actions are executed in the main thread, so interaction with 30MB inventory.yml and players.yml files was very good server killer. Splitting them into per-player filesystem makes saving process much less resource-hungry.
This pull contains both system rework and files migration, so updating will be effortlessly.

Hey, thank you for submitting this, I can appreciate the effort that went into it.
Parkour v6.X development (master) has seized while we continue to develop 7.0 as the codebase is considerably different.
A configuration rework was the main focus of 7.0 so per-file player and course json files have already been completed and the performance boost is magnificent.
That said, if you can see any further performance improvements with the new system and library I'd be happy to consider them. Thanks again.


FIX: hard coded /movies in SAAS templates view_edit

minor glitch made new user experience unwelcoming.

great catch!! thanks ❤


adding new clock

You can follow these steps.
Add your theme in the list using the same format in index.html

Move to the theme.css to style your theme using the data-theme you've set. Forexample


Query parsing breaks with encoded equals sign

The following code results in a crash
    let queryParsed = Query.Parse "one=two%3d"
    let queryPairs = queryParsed |> (fst <| Query.Pairs_)

I believe the issue is that percent decoding is being performed too early, leading to the parser thinking that the %3d is actually a key/value separator in the query.

Yes, you're right. For Arachne 3.0 I'm going to have to reconsider how we deal with encoding, as this (and similar issues) are causing some odd edge cases.

I think this should be fixed by #25 but I want to check it before the 3.0 release.

In fact this was not entirely fixed by that and exposed a bug in the percent-encoding logic - it didn't cope well with lowercase encodings! That will now be fixed for 3.0. I think this does imply some further design work needed around query and pairs optics, but that can be done post-3.0.

Fixed in PR #35


Update Unity.gitignore

Reasons for making this change:
TODO
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

added some stuff to the gitgnore


Godot freezes when doing basic things such as saving project.

Tested versions
4.2.2
System information
Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Mobile) - dedicated Radeon RX 560X Series (Advanced Micro Devices, Inc.; 31.0.21912.14) - AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx (8 Threads)
Issue description
When I save a scene it freezes, causing me to close godot and restart. It has also happened when trying to run the project to test.
Steps to reproduce
not sure how to reproduce other than save, I think this has to do with my system specs/hardware
Minimal reproduction project (MRP)
N/A

Seems to work fine with 4.3, thanks.


Task

Describe the task
Update the wording in the reporting system to reflect the changes introduced by the new ZEV Act and Regulations for the 2024 compliance period and beyond. Apply these changes only starting from MY2024 and avoid impacting previous model years. Implement the specific changes outlined in the table provided by the business area, which details updates for both the Supplier side and the internal side.
Purpose
This task aligns the reporting system with the updated ZEV Act and Regulations, maintaining compliance with new requirements while safeguarding the accuracy of data for previous model years.
Acceptance Criteria

[ ] Wording on each page and subpage is updated according to the specific changes listed in the table for both  IDIR and Supplier (BCeID) sides.
[ ] Conditional formatting is applied so that new wording only affects MY2024 and later model years.
[ ] All relevant pages and subpages are updated as specified in the table.

Additional context
Document with the table outlining changes for both IDIR and Supplier sides: Supplied_Registered_ZEV_Reporting_System_Changes.docx
The changes apply to the following pages:

Compliance Reporting

Model Year Reports (Main Page)
Specific Supplier MY Report Page
Supplementary Report

Credit Transactions

Credit Applications
Credit Transactions (Specific Supplier Credit Application Page)

ZEV Models

Vehicle Details
Main Page

Other housekeeping tasks (e.g., title changes)

Verify with the document that all changes have been captured. If you have questions about the documented changes, contact Tamara Garriock or Shauna Black, the authors of the table.

This work needs to part of the ZEVA release on Oct 21st, 2024.


How To color by secondary structure

how can i set secondary structure as default coloring on rendering it in code

this is my code
any help is appreciated.

Hi.
There is no option to achieve this directly. But you can add this code which changes the color theme for polymer component once the structure is loaded:
        function colorPolymerBySecStr() {
            const cells = Array.from(viewerInstance.plugin.state.data.cells.values());
            const polymerComponents = cells.filter(c => c.transform.tags?.includes('structure-component-static-polymer'));
            for (const component of polymerComponents) {
                const polymerRepresentations = viewerInstance.plugin.state.data.tree.children.get(component.transform.ref);
                for (const repr of polymerRepresentations) {
                    viewerInstance.plugin.build().to(repr).update({ colorTheme: { name: 'secondary-structure', params: {} } }).commit();
                }
            }
        }
        viewerInstance.events.loadComplete.subscribe(colorPolymerBySecStr);

You could also apply the color theme to all representations:
const representations = cells.filter(c => c.transform.transformer.id === 'ms-plugin.structure-representation-3d');

but I think it wouldn't make sense for non-polymers

Update:
With PDBe Molstar 3.3.0, this is now much easier. Follow the solution described here https://github.com/molstar/pdbe-molstar/issues/110
But instead of
polymer: { type: 'cartoon', color: 'sequence-id' },
use
polymer: { type: 'cartoon', color: 'secondary-structure' },


This reverts commit 637da7864eba15a638e212e22d6e271e8c0a53e7.
The author probably indented to run a script that regenerates the closure library gh-pages on the gh-pages branch and mistakenly executed the script on the master branch instead.
Luckily git can save us!

Woopsie daisy. You got it right :D. Master should be fixed.

We rewrote history... so please clone a new version...

Oh, I thought this was just one of those (╯°□°)╯︵ ┻━┻ moments...


hide missing battery

This PR will hide the battery symbol if the plenticore was not configured to work with a battery.

Hey, have a look at my commit history. I wanted to apply your changes 10 days ago.
After a test of your changes, I noticed that my battery was no longer displayed in standby mode at night. I have therefore undone your changes.
Has your code improved in this respect? If not, I would leave my version as it is.

Hey, yes, I noticed that. And therefore I've done some changes. So the battery should now be displayed.
But, i got my battery already. So I can not really check, if it is not shown on a Plenticore without a battery.
Is there anybody out there with a Plenticore without a battery?

Oh, I just remembered, that there can be differences in the API between the different plenticores? I have a Plenticore G3. Wich one do you have? So if your battery should not be displayed again, I have to look for any differences between the API on different plenticore models.

Hi, i gave it a try, but my battery is not visible after merging and pulling your version. I will revert it. I have a PLENTICORE plus 8.5

Thanks anywhere for your help!

A okay. Thanks for trying. Then the system.props are not present on your API. So i will have a look at it later. Maybe I will do another PR, if I'll find a way to test it for an inverter without a battery.


[Build] Disable compilation warnings for external projects

Summary of the Pull Request
What is this about:
What is include in the PR:
How does someone test / validate:
Quality Checklist

[ ] Linked issue: #8212
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

There are still warnings on the ci build


Native extension building still broken on RHEL 6

Description
Building native gems is broken on RHEL 6
Chef Version
chef-client 15 and chef-client 16
Platform Version
RHEL 6.10 and CentOS 6.10
Replication Case
build_essential 'ruby-augeas'
package 'augeas-devel'
chef_gem 'ruby-augeas'
Client Output
        * chef_gem[ruby-augeas] action install

           ================================================================================
           Error executing action `install` on resource 'chef_gem[ruby-augeas]'
           ================================================================================

           Mixlib::ShellOut::ShellCommandFailed
           ------------------------------------
           Expected process to exit with [0], but received '1'
           ---- Begin output of /opt/chef/embedded/bin/gem install ruby-augeas -q --no-document -v "0.5.0" --source=https://www.rubygems.org ----
           STDOUT: Building native extensions. This could take a while...
           STDERR: ERROR:  Error installing ruby-augeas:
                ERROR: Failed to build gem native extension.

        current directory: /opt/chef/embedded/lib/ruby/gems/2.6.0/gems/ruby-augeas-0.5.0/ext/augeas
           /opt/chef/embedded/bin/ruby -I /opt/chef/embedded/lib/ruby/2.6.0 -r ./siteconf20200508-3455-btgqtk.rb extconf.rb
           *** extconf.rb failed ***
           Could not create Makefile due to some reason, probably lack of necessary
           libraries and/or headers.  Check the mkmf.log file for more details.  You may
           need configuration options.

           Provided configuration options:
                --with-opt-dir
                --with-opt-include
                --without-opt-include=${opt-dir}/include
                --with-opt-lib
                --without-opt-lib=${opt-dir}/lib
                --with-make-prog
                --without-make-prog
                --srcdir=.
                --curdir
                --ruby=/opt/chef/embedded/bin/$(RUBY_BASE_NAME)
                --with-augeas-config
                --without-augeas-config
                --with-pkg-config
                --without-pkg-config
           /opt/chef/embedded/lib/ruby/2.6.0/mkmf.rb:478:in `try_do': The compiler failed to generate an executable file. (RuntimeError)
           You have to install development tools first.
                from /opt/chef/embedded/lib/ruby/2.6.0/mkmf.rb:563:in `try_link0'
                from /opt/chef/embedded/lib/ruby/2.6.0/mkmf.rb:581:in `try_link'
                from /opt/chef/embedded/lib/ruby/2.6.0/mkmf.rb:683:in `try_ldflags'
                from /opt/chef/embedded/lib/ruby/2.6.0/mkmf.rb:1843:in `pkg_config'
                from extconf.rb:26:in `<main>'

           To see why this extension failed to compile, please check the mkmf.log which can be found here:

             /opt/chef/embedded/lib/ruby/gems/2.6.0/extensions/x86_64-linux/2.6.0/ruby-augeas-0.5.0/mkmf.log

mkmf.log
"pkg-config --exists augeas"
| pkg-config --libs augeas
=> "-laugeas  \n"
"gcc -o conftest -I/opt/chef/embedded/include/ruby-2.6.0/x86_64-linux -I/opt/chef/embedded/include/ruby-2.6.0/ruby/backward -I/opt/chef/embedded/include/ruby-2.6.0 -I. -I/opt/chef/embedded/include -O2 -D_FORTIFY_SOURCE=2 -fstack-protector -O3 -g -pipe -I/opt/chef/embedded/include   -I/opt/chef/embedded/include -O2 -D_FORTIFY_SOURCE=2 -fstack-protector -O3 -g -pipe -fPIC conftest.c  -L. -L/opt/chef/embedded/lib -Wl,-rpath,/opt/chef/embedded/lib -L/opt/chef/embedded/lib -Wl,-rpath,/opt/chef/embedded/lib -L. -Wl,-rpath,/opt/chef/embedded/lib -L/opt/chef/embedded/lib -fstack-protector -rdynamic -Wl,-export-dynamic -L/opt/chef/embedded/lib  -Wl,-rpath,/opt/chef/embedded/lib     -Wl,-rpath,/opt/chef/embedded/lib -L/opt/chef/embedded/lib -lruby  -lm   -lc"
In file included from /opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:29,
                 from /opt/chef/embedded/include/ruby-2.6.0/ruby.h:33,
                 from conftest.c:1:
/opt/chef/embedded/include/ruby-2.6.0/ruby/defines.h:154:23: error: stdalign.h: No such file or directory
In file included from /opt/chef/embedded/include/ruby-2.6.0/ruby.h:33,
                 from conftest.c:1:
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1437: error: wrong number of arguments specified for ‘__deprecated__’ attribute
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1446: error: wrong number of arguments specified for ‘__deprecated__’ attribute
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h: In function ‘rb_mul_size_overflow’:
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1688: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘c2’
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1688: error: ‘c2’ undeclared (first use in this function)
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1688: error: (Each undeclared identifier is reported only once
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1688: error: for each function it appears in.)
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1688: error: expected ‘)’ before ‘__int128’
/opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:1688: error: expected ‘)’ before ‘__int128’
In file included from /opt/chef/embedded/include/ruby-2.6.0/ruby/ruby.h:2111,
                 from /opt/chef/embedded/include/ruby-2.6.0/ruby.h:33,
                 from conftest.c:1:
/opt/chef/embedded/include/ruby-2.6.0/ruby/intern.h: At top level:
/opt/chef/embedded/include/ruby-2.6.0/ruby/intern.h:192: error: wrong number of arguments specified for ‘__deprecated__’ attribute
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5:   return 0;
6: }
/* end */

Pretty sure Issue #9144 was never fully fixed.

Does installing devtoolset-7 and using scl to make it the default compiler fix the issue?
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/

Ruby 2.7 has now dropped support for the RHEL6 default compiler, so our build systems all had to be updated, so this likely won't get fixed short of having build_essentials upgrade RHEL6 to a later compiler.
(Unless its determined that something else is going on, but if its compiler versioning then the default RHEL6 compiler probably isn't ever coming back)

Running scl enable devtoolset-7 -- /opt/chef/embedded/bin/gem install ruby-augeas does seem to successfully build the native extensions.  Not sure what the correct thing to do going forward for RHEL/Centos 6 is.  I am probably just going to stick with version 14 since we are phasing out our RHEL 6 systems anyway as they are going to be out of normal support soon.  Maybe just document the issue and workaround.

@nhuff We have this listed as a breaking change in Chef Infra Client 16 with the workaround here: https://docs.chef.io/release_notes/#red-hat--centos-6-systems-require-c11-gcc-for-some-gem-installations

I'm going to close this one out since there isn't really a fix other than upgrading GCC on the host or upgrading off RHEL 6.


Doesn't work with React Native 0.17.0

As soon as running a project with this middleware on, a transform error is shown on simulator. It seems .babelrc file is the culprit.

Ah. That file should not be included when you install the middleware via npm. I'll push up a fix shortly.

Will you let me know if the release<EMAIL_ADDRESS>works?

Meanwhile this can be helpful. A gulptask for removing .babelrc files https://github.com/este/este/blob/72a8e68b2e47c1d6067c8d226d4425d18e7d0956/gulpfile.babel.js#L111

The new version works now.

Great!


Uncaught Exception: Command failed:<PHONE_NUMBER>

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.0
Time: Tue Mar 08 2016 17:12:55 GMT 0000 (GMT Standard Time)
Error:
Command failed:<PHONE_NUMBER>
Error: Command failed:<PHONE_NUMBER>
System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The remote name could not be resolved: 'update.googleplaymusicdesktopplayer.com'
   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)
   at System.Net.WebClient.DownloadBitsResponseCallback(IAsyncResult result)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.Utility.<LogIfThrows>d__50`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Squirrel.FileDownloader.<DownloadUrl>d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerS
...Some of the stack is missing

This issue was created automatically inside the uncaughtException handler

Client side network issues, error will not be reported next version


Directory.current differs from PWD on macos when built

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
Directory.current differs from PWD on macos. This happens only in Flutter, not in pure Dart apps.
Flutter macos:

Create a new Flutter app.
Replace main.dart with the attached file.
Add macos platform: flutter create --platforms macos .
Replace macos\Runner\Release.entitlements with the attached file (disable sandbox).
flutter build macos
open macos/Runner.xcworkspace
In Xcode, run the app.

Flutter linux:

Create a new Flutter app.
Replace main.dart with the attached file.
Add linux platform: flutter create --platforms linux .
flutter build linux
Run the built app: build/linux/x64/release/bundle/project_name

Dart macos:

dart compile exe main_pure_dart.dart
./main_pure_dart.exe

Expected results
Both Flutter and Dart apps show the same for the two sources of the current directory: Directory.current.path and Platform.environment['PWD'].
Actual results
With flutter build:
Flutter macos: Platform.environment['PWD'] is correct, but Directory.current.path shows the root directory /.
Flutter linux: Correct.
Dart: Correct.
With flutter run:
All platforms including macos show identical paths.
Code sample
main.dart (Flutter)
import 'dart:io';

import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Table(
          defaultColumnWidth: const IntrinsicColumnWidth(),
          children: [
            TableRow(
              children: [
                const Text('Directory.current:   '),
                Text(Directory.current.path),
              ],
            ),
            TableRow(
              children: [
                const Text('PWD:   '),
                Text(Platform.environment['PWD'] ?? ''),
              ],
            ),
          ],
        ),
      ),
    );
  }
}

Release.entitlements
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<!--<key>com.apple.security.app-sandbox</key>
	<true/>-->
</dict>
</plist>

main_pure_dart.dart
import 'dart:io';

void main() {
  print(Directory.current.path);
  print(Platform.environment['PWD']);
}

Screenshots or Video

Screenshots
flutter run -d macos

flutter build macos

flutter run -d linux

flutter build linux

Logs
No response
Flutter Doctor output
macos: flutter doctor -v
[✓] Flutter (Channel stable, 3.13.6, on macOS 13.6 22G120 darwin-arm64
    (Rosetta), locale en-GE)
    • Flutter version 3.13.6 on channel stable at /Users/ai/bin/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (2 days ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/ai/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b829.9-10027231)

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.6 22G120 darwin-arm64
      (Rosetta)
    • Chrome (web)    • chrome • web-javascript • Google Chrome 117.0.5938.92

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

linux: flutter doctor -v
[✓] Flutter (Channel stable, 3.13.6, on Ubuntu 22.04 LTS 6.2.0-33-generic,
    locale en_US.UTF-8)
    • Flutter version 3.13.6 on channel stable at
      /home/alexey/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (2 days ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[!] Android toolchain - develop for Android devices (Android SDK version
    32.1.0-rc1)
    • Android SDK at /home/alexey/Android/Sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/linux#android-setup for
      more details.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 10.0.0-4ubuntu1
    • cmake version 3.16.3
    • ninja version 1.10.0
    • pkg-config version 0.29.1

[✓] Android Studio (version 2021.1)
    • Android Studio at /home/alexey/bin/android-studio
    • Flutter plugin version 65.2.2
    • Dart plugin version 211.7811
    • Java version OpenJDK Runtime Environment (build 11.0.11+0-b60-7590822)

[✓] Connected device (3 available)
    • SM T585 (mobile) • 52006be146d18475 • android-arm    • Android 8.1.0 (API
      27)
    • Linux (desktop)  • linux            • linux-x64      • Ubuntu 22.04 LTS
      6.2.0-33-generic
    • Chrome (web)     • chrome           • web-javascript • Google Chrome
      116.0.5845.140

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

This is not a bug, it's a misunderstanding of how GUI apps work on macOS.

Flutter macos: Platform.environment['PWD'] is correct, but Directory.current.path shows the root directory /.

What you are describing as "correct" here is actually arbitrary. macOS provides no guarantees about the working directory of a GUI application, nor does it guarantee anything about the value of most environment variables. If you run it directly from Terminal you will inherit the working directory and environment from that context (as with all of your examples on other platforms, and the flutter run case on macOS). But when the application is launched through other mechanisms, such as Xcode, or opening the app from Finder (the usual way apps are launched), those values are decided by the OS.
You should never assume anything about the working directory of a GUI application. If you want to work with paths you should be starting from well defined locations.

Thanks for clarification @stuartmorgan
Still I believe if we have PWD environment variable then Directory.current should stick to it.
This variable may be arbitrary from the app's own perspective, but its value or absence for each use case is defined by the operating system and is reproducible.
It's one thing to have this variable content "arbitrary" as decided by the OS, and completely another thing to let Flutter mess with it on top of what the operating system supplies. It's just a different level of problem and indirection.
As for my case, I am building an internal tool for my team, so I am fine with forcing users to run it from terminal.
But I can think of many points why diverting Directory.current from PWD if it exists is wrong:

Inconsistent behavior between flutter run and the built app within macos.
Inconsistent behavior between operating systems.
Inconsistent behavior of some otherwise reusable Dart code between Flutter and non-Flutter.
Overriding of what the Dart documentation assumes without explicitly telling it to users.

What if someone has a valid use of Directory.current on Linux where it works correctly and needs to port it on Mac quickly to just work even with a weird way to run it? (My case.)
Should we bar this option for them just because it is not how things are traditionally done on the new target OS?
I don't think we should assume use cases and have this added uncertainty when we have chance to keep things more consistent, as the OS tells us.
So I still think this is a bug that should be re-opened.

Still I believe if we have PWD environment variable then Directory.current should stick to it.

Directory.current is implemented using native functionality that returns the actual working directory, rather than an environment variable that can be overridden. You will see exactly the same difference in a non-Flutter macOS application if you compare the current directory from NSFileManager and the environment from NSProcessInfo.

and completely another thing to let Flutter mess with it on top of what the operating system supplies.

It doesn't.

But I can think of many points why diverting Directory.current from PWD if it exists is wrong

Please feel free to file a bug against Apple if you want changes in how the current working directory of a process is defined.

Inconsistent behavior between flutter run and the built app within macos.

That difference is due to the way the process is launched, and has nothing to do with Flutter itself.

Inconsistent behavior between operating systems.

Flutter does not control operating system behavior.

Inconsistent behavior of some otherwise reusable Dart code between Flutter and non-Flutter.

There is no inconsistency between Flutter and non-Flutter. The difference is in how you are launching the application. If you want your Flutter application to behave like a command-line tool, you are welcome to run it exclusively as such (step 6 in my comment above).

Overriding of what the Dart documentation assumes without explicitly telling it to users.

Nothing on that page claims that the env variable PWD is how the current directory is defined.

What if someone has a valid use of Directory.current on Linux where it works correctly and needs to port it on Mac quickly to just work even with a weird way to run it?

Then they are welcome to do so, and run their app exclusively in the weird way that gives them the results that they want. But that's not what your steps to reproduce do; you launched the app from Xcode rather than directly running the executable.

when we have chance to keep things more consistent, as the OS tells us.

The behavior you are objecting to is the OS behavior.

So I still think this is a bug that should be re-opened.

Flutter is not going to unilaterally change the definition of a process's working directory on macOS.

Thanks for the details on the OS behavior, it makes all the sense now.
For anyone else finding this, the easiest workaround is
Directory.current = Directory(Platform.environment['PWD'] ?? '/');

Also, I recommend that you try running your pure-Dart example on Linux with:
$ PWD=something ./main_pure_dart.exe

I'm not sure why you believe that PWD controls working directory; it's not true on Linux either.

That was just a hint I was given here: https://stackoverflow.com/a/77197579/11382675
And it works in my controlled environment.

Nothing in that answer claims that the PWD environment variable defined the working directory of a process (on any platform), as you assert earlier should be true.


[SPARK-46118][SQL][SS][CONNECT] Use SparkSession.sessionState.conf instead of SQLContext.conf and mark SQLContext.conf as deprecated

What changes were proposed in this pull request?
There are some calls to SparkSession.sqlContext.conf in the Spark code, which is equivalent to SparkSession.sqlContext.sparkSession.sessionState.conf. This PR changes them to directly call SparkSession.sessionState.conf or expand to SQLContext.SparkSession.sessionState.conf
At the same time, this PR marks the internal API SQLContext.conf as deprecated, and SparkSession.sessionState.conf should be used directly.
Why are the changes needed?

SparkSession.sessionState.conf has a shallower call stack compared to SparkSession.sqlContext.conf
SQLContext has been marked as deprecated since Apache Spark 1.6, and its APIs should be avoided as much as possible in Spark's internal code.

Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass GitHub Actions
Was this patch authored or co-authored using generative AI tooling?
No

Merged into master. Thanks @hvanhovell ~


[BACKPORT][v1.3.x][BUG] Restore from backup sometimes failed if having high frequent recurring backup job w/ retention

Describe the bug
ref: #3055

Verified on v1.3.x-head 20220829

longhorn v1.3.x-head (cccabbf)
longhorn-manager v1.3.x-head ( 7f1634c)

The test steps

Install Longhorn 1.3.x-head
Create a volume "bak" on longhorn
Create volume "bak"'s PV(name:bak) & PVC (name:myclaim) from longhorn UI
Deploy pod “mypod1” via cli kubctl apply -f mypod1.yaml

kind: Pod
apiVersion: v1
metadata:
  name: mypod1
  namespace: default
spec:
  containers:
    - name: testfrontend
      image: nginx
      volumeMounts:
      - mountPath: "/usr/share/nginx/html/"
        name: mypod1
  volumes:
    - name: mypod1
      persistentVolumeClaim:
        claimName: myclaim

Enter mypod1 shell kubectl exec --stdin --tty mypod1 -- /bin/bash
execute echo 'Hello from Kubernetes storage' > /usr/share/nginx/html/index.html
Create recurring back job, 3 retain, 1 concurrency, every minute
Create a manual backup
Restore manual backup to volume-v1
Check whether or not the error was printed

Result Pass

After restored, we didn’t observe the error symptoms.
longhorn-support-bundle_ad053f1f-e8fc-478d-b3c4-0a72f9cafa0a_2022-08-29T07-21-02Z.zip