[Issue report]Misuse of iaminstanceprofile in aws_ec2_iaminstance.json due to missing EC2InstanceProfile object

Title: Misuse of iaminstanceprofile in aws_ec2_iaminstance.json due to missing EC2InstanceProfile object
Description:

In aws_ec2_iaminstance.json (found here), Cartography incorrectly assumes a direct connection between the iaminstanceprofile name and the IAM Role. This assumption is not accurate, as AWS uses IamInstanceProfile as a distinct resource that links to a single IAM Role.

The misuse happens because Cartography does not currently create a separate EC2InstanceProfile object, leading to incorrect modeling of the relationship between EC2 Instances and IAM Roles.
Expected behavior:
A separate EC2InstanceProfile object should be created and properly linked to EC2 Instances.
The relationship between the EC2InstanceProfile and its associated IAM Role should be accurately represented, avoiding the incorrect assumption about the name correlation.
[optional Relevant Links:]

here

@xiaoen-liu - Thanks for reporting, this is a valid issue.
To make sure I understand, the current model is
EC2 Instance ←→ IAM Role

but it should be this instead:
EC2 Instance ←→ IamInstanceProfile ←→ IAM Role

Is this right?

Yes, without having the IamInstanceProfile as a separate model, it's not possible to correctly establish the node relationships between EC2 Instances and IAM Roles.

I would like to further clarify the cause of this confusion. The creation of an AWS Instance Profile and the binding of an Instance Profile to an IAM Role are two separate API calls: IAM.Client.create_instance_profile and IAM.Client.add_role_to_instance_profile. These APIs do not require the instance profile name and the IAM role name to have any relationship.
However, the AWS Console design makes it appear as though the instance profile name and the IAM role name are identical, which leads to confusion. This issue becomes more pronounced when using Infrastructure as Code (IaC) tools like Terraform, CloudFormation, or CDK, where instance profile names and IAM role names are often completely different.
This discrepancy can cause significant issues in environments where IaC is used to manage AWS resources, making it important to properly model the distinction between instance profiles and IAM roles.

From what I understand and also from looking at our tfstate files
aws_iam_instance_profile -(one-to-one)→ role

while
role -(one-to-many)→ aws_iam_instance_profile

So not sure what the issue issue!
@xiaoen-liu Are you able to provide an example please?


Support Application Default Credentials

I originally opened this over in google-apis-rs/generator#20, so let me know if you think this is a better fit for that project.
What do you think about supporting Application Default Credentials? To start we could just check GOOGLE_APPLICATION_CREDENTIALS.
Down the road, we could also communicate with the metadata server to automatically obtain credentials if GOOGLE_APPLICATION_CREDENTIALS wasn’t provided. This would obviously be more involved but I think reverse engineering this process from one of the official client libraries wouldn’t be too bad.
I envision adding a new top level function like: yup_oath2:: service_account_key_from_application_default_credentials, although that is rather verbose...
So the flow would be:
Try to use an explicitly provided service account.
If None, check GOOGLE_APPLICATION_CREDENTIALS
(Future work) If None, communicate with metadata server to use default service account
If still not found, Err.
 It is so seamless and uniform across all their APIs. This would be a big step towards that UX.
Once we decide on a direction, I would be happy to open a PR.

I am quite sympathetic towards supporting them. I also have #44 lying around for some time now, which I think is related.
The flow sounds good to me, however I am tending very much towards modular and optional approaches rather than magic intransparent ones (I want to be clear so we're on the same page). So as long as the change works well with other providers too, although yes - yup-oauth2 is mostly Google focused still, and is somewhat transparent to users of the library, I would be extremely happy to take a PR from you!
Also apologies for the delay :(

Yeah #44 and #186 are both what I am proposing here. Although I was proposing doing #44 at a later stage.
I am trying to think of the best API for this because I agree I don’t like “magic” solutions, but the entire Google Application Default Credentials flow (which is pretty much what I described above but for some reason forgot to link this) is fairly automatic/magical which is kind of its strength—to make auth a lot less of a hassle in production. I am mostly interested in this as a feature parity with official Google cloud SDK libraries.

I think magic is fine if it is well-documented. So taking the credentials from environment variables or the GCE sidecar server is fine, if we say so in the module's documentation (and explain how it works and what to do if it doesn't).
Feature parity with google cloud libraries would be awesome!

I am hoping to have time to work this soon...
It looks like we just need to:

If GOOGLE_APPLICATION_CREDENTIALS is set, call
yup_oauth2::read_service_account_key() and
yup_oauth2::ServiceAccountAuthenticator::builder()

If not, make the equivalent HTTP request:
curl "http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token" -H "Metadata-Flavor: Google"

which returns:
{ "access_token": "...", "expires_in": 2801, "token_type": "Bearer" }

Else: return an Err

In the end, I am envisioning an API that looks something like (definitely need to think of a better name):
let authenticator = yup_oauth2::ApplicationDefaultCredentialsAuthenticator::new().await?;

or we could use the builder pattern to match the other flows, but there isn't
really anything to configure (pretty much the point of using ADC 🙃)... Although, there might be other things to configure, like persist_tokens_to_disk etc...

I agree with your approaches, it looks similar to what I had thought of before. If you were to send a PR, I will gladly integrate it! For me to built/test it, I'd first have to set up a proper environment on Google Cloud again.

Boosting signal on this linked issue as well:
I have created a small bare bones impl of this and would requests comments/contributions on it before creating an pull request: https://github.com/braincow/yup-oauth2/tree/gcp_instance_metadata


Clown Resprite

About the PR

Changed the clown uniform to have more details
Why / Balance

to bring clown outfit up to date with other uniforms of goob station
Technical details

Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog

changed clown jumpsuit and jumpskirt
change clown mask
changed clown shoes

please dont, he's too iconic to change

can't even notice the difference

still, it's the principal

can't even notice the difference

if you look at the shirt there are a few more pixels

still, it's the principal

its not that different looking its just a few more pixels on the shirt and mask

i like the clown jumpskirt

update the credits and don't remove equipped sprites that you don't have new versions for

what credits?

how do i do that?

edit the meta.json files in each of the folders where you changed the sprites and add credit to where you got them from by going to the github of where you took it from, going into the data folder or wherever they keep their sprites then at the near-top-right clicking on the 3 dots and pressing "copy permalink" and adding "Taken from paradise station at commit https://blablablainsertyourlinkhere" to the copyright section.

oh no i edited the sprites myself i didnt take it from anywhere

then credit yourself

done

don't remove equipped sprites that you don't have new versions for

you mean the clown masks?
the new ones have a little bit more detail on the wig

You deleted some equip sprites like the hamlet ones it looks like, you don't have to redo them but don't delete them.

how do i do this because i didn't delete the sprites they are still in the repo folder


Navbar Button Visibility Issue on Mobile & Dashboard Duplication in Header

On mobile devices, the navbar buttons are not visible, impacting user navigation and accessibility. Additionally, the dashboard link appears redundantly in the header alongside the logo, despite already being included in the navbar. This redundancy not only clutters the UI but also affects usability. Resolving these issues will improve mobile navigation and create a cleaner, more streamlined interface.
Kindly assign this issue to me under GSSoC-Extd and Hacktoberfest.

On mobile devices, the navbar buttons are not visible, impacting user navigation and accessibility. Additionally, the dashboard link appears redundantly in the header alongside the logo, despite already being included in the navbar. This redundancy not only clutters the UI but also affects usability. Resolving these issues will improve mobile navigation and create a cleaner, more streamlined interface.
Kindly assign this issue to me under GSSoC-Extd and Hacktoberfest.

Oky do it


How to pass args to native fzf preview

Hi. I am trying to port something similar to https://github.com/debugloop/telescope-undo.nvim/tree/main to fzf-lua because I can't find any information on how to customise the :changes command and ideally I want the diff to be presented by delta or even vimdiff.
But when I encounter the line https://github.com/debugloop/telescope-undo.nvim/blob/main/lua/telescope-undo/init.lua#L141 I can't figure out how to pass stuff from lua to delta. I am looking for a way to pass custom arguments to delta. Is it the case that the only solution is to implement something like https://github.com/ibhagwan/fzf-lua/wiki/Advanced#explore-changes-from-a-git-branch with the preview option?
Thank you

You probably need a custom provider of at least a custom previewer, read the advanced wiki, especially previewer section and twke it from there
https://github.com/ibhagwan/fzf-lua/wiki/Advanced#neovim-builtin-preview
Once you have a semi-working code sample and have a more specific question/issue, post it in this thread and I’ll help you adjust the code.

Here is what I have got so far. Things are working but I kind of have to put the index of the undo item in the "string" itself so that I can use that to index the corresponding entry in the undolist
M.undo_tree = function()
  local undolist = utils.get_undolist()

  require('fzf-lua').fzf_exec(function(fzf_cb)
    coroutine.wrap(function()
      local co = coroutine.running()
      vim.schedule(function()  -- Ignore this. I will try to make it use coroutine later
        for i, undo in ipairs(undolist) do
          fzf_cb(string.format("[%d] seq %d (%s)", i, undo.seq, undo.time),
            function() coroutine.resume(co) end)
        end
      end)
      coroutine.yield()
      fzf_cb()
    end)()
  end, {
    prompt = 'UndoTree❯ ',
    preview = require 'fzf-lua'.shell.raw_preview_action_cmd(function(selected)
      local undo = undolist[tonumber(selected[1]:match("%[(.-)%]"))]
      local delta_opts = ""
      return string.format([[echo '%s' | delta "%s" %s]], undo.diff:gsub([[']], [['"'"']]), undo.time, delta_opts)
    end),
    actions = {
      ['ctrl-a'] = {
        -- See action reload
        -- https://github.com/ibhagwan/fzf-lua/wiki/Advanced#action-reload
        fn = function(selected, opts)
          local undo = undolist[tonumber(selected[1]:match("%[(.-)%]"))]
          vim.cmd(string.format("slient undo %s", undo.seq))
          vim.notify(string.format("Undo %s", undo.seq))
        end,
        reload = true,
      },
      ['ctrl-o'] = function(selected, opts)
        local undo = undolist[tonumber(selected[1]:match("%[(.-)%]"))]
        local before_and_after = utils.get_undo_before_and_after(undo.seq)
        utils.open_diff_in_new_tab(before_and_after[1], before_and_after[2])
      end
    }
  })
end

function M.undolist_entry_producer(opts, entries, alt_level)
  return coroutine.create(function()
    for i = #entries, 1, -1 do
      local undo_before_and_after = M.get_undo_before_and_after(entries[i].seq)

      local before_lines = undo_before_and_after[1]
      local before = table.concat(before_lines, "\n")
      local after_lines = undo_before_and_after[2]
      local after = table.concat(after_lines, "\n")

      -- create temporary vars and prepare this iteration
      local diff = ""
      local brief = ""
      local additions = {}
      local deletions = {}
      local on_hunk_callback = function(start_a, count_a, start_b, count_b)
        -- build diff file header for this hunk, this is important for delta to syntax highlight
        -- TODO: timestamps are being omitted, but could be included here
        diff = vim.fn.expand("%")
        diff = "--- " .. diff .. "\n+++ " .. diff .. "\n"
        -- build diff location header for this hunk, this is important for delta to show line numbers
        diff = diff .. "@@ -" .. start_a
        if count_a ~= 1 then
          diff = diff .. "," .. count_a
        end
        diff = diff .. " +" .. start_b
        if count_b ~= 1 then
          diff = diff .. "," .. count_b
        end
        diff = diff .. " @@"
        -- get front context based on options
        local context_lines = 0

        if opts.diff_context_lines ~= nil then
          context_lines = opts.diff_context_lines
        end
        for j = start_a - context_lines, start_a - 1 do
          if before_lines[j] ~= nil then
            diff = diff .. "\n " .. before_lines[j]
          end
        end
        -- get deletions
        for j = start_a, start_a + count_a - 1 do
          diff = diff .. "\n-" .. before_lines[j]
          table.insert(deletions, before_lines[j])
          brief = brief .. before_lines[j]
        end
        brief = brief .. " -> "
        -- get additions
        for j = start_b, start_b + count_b - 1 do
          diff = diff .. "\n+" .. after_lines[j]
          table.insert(additions, after_lines[j])
          brief = brief .. before_lines[j]
        end
        -- and finally, get some more context in the back
        for j = start_a + count_a, start_a + count_a + context_lines - 1 do
          if before_lines[j] ~= nil then
            diff = diff .. "\n " .. before_lines[j]
          end
        end
        -- terminate all this with a newline, so we're ready for the next hunk
        diff = diff .. "\n"
      end

      vim.diff(before, after, {
        result_type = "indices",
        on_hunk = on_hunk_callback,
        algorithm = "patience",
      })

      brief = vim.trim(brief)
      if #brief > 80 then
        brief = brief:sub(1, 80) .. "..."
      end
      if #brief == 0 then
        brief = "<empty>"
      end

      local entry = {
        seq = entries[i].seq,  -- save state number, used in display and to restore
        alt_level = alt_level, -- current level, i.e. how deep into alt branches are we, used to graph
        first = i == #entries, -- whether this is the first node in this branch, used to graph
        timestamp = entries[i].time,
        time = timeago(entries[i].time),
        brief = brief,         -- brief message to describe the change
        diff = diff,           -- the proper diff, used for preview
        additions = additions, -- all additions, used to yank a result
        deletions = deletions, -- all deletions, used to yank a result
        bufnr = vim.api.nvim_get_current_buf(),
      }

      if opts.debug then
        vim.notify(string.format("Yielding successfully: %s", vim.inspect(entry)))
      end
      coroutine.yield(entry)

      -- descend recursively into alternate histories of undo states
      if entries[i].alt ~= nil then
        local alt_undotree_producer = M.produce_undotree_entry(opts, entries[i].alt, alt_level + 1)
        repeat
          local ok, alt_undolist_entry = coroutine.resume(alt_undotree_producer)
          if not ok then
            error("Failed to produce undotree entry")
          end

          if opts.debug then
            coroutine.yield(alt_undolist_entry)
          end
          coroutine.yield(alt_undolist_entry)
        until coroutine.status(alt_undotree_producer) == "dead"
      end
    end
  end)
end

M.get_undolist = function(opts)
  opts = opts or {}
  opts = vim.tbl_deep_extend("force", opts, {
    diff_context_lines = 10, -- Number of surrounding lines to add to the preview for context
    max_entries = 100,       -- Maximum number of entries to process
    debug = true             -- Whether to log out entry inside coroutine
  })

  -- save our current cursor
  local cursor = vim.api.nvim_win_get_cursor(0)

  -- get all diffs of current buf
  local ut = vim.fn.undotree()

  -- procedurally generate undotree entries w/ coroutine
  local undolist = {}
  local undolist_entry_producer = M.undolist_entry_producer(opts, ut.entries)
  for i = 1, opts.max_entries do
    local ok, entry = coroutine.resume(undolist_entry_producer)
    if not ok then
      error("Failed to produce undotree entry: " .. entry)
    end

    table.insert(undolist, entry)
    if coroutine.status(undolist_entry_producer) == "dead" then
      break
    end

    if i == opts.max_entries then
      coroutine.close(undolist_entry_producer)
    end
  end

  -- restore everything after all diffs have been created
  -- BUG: `gi` (last insert location) is being killed by our method, we should save that as well
  vim.cmd("silent undo " .. ut.seq_cur)
  vim.api.nvim_win_set_cursor(0, cursor)

  return undolist
end

Thank you for your help

Things are working but I kind of have to put the index of the undo item in the "string" itself so that I can use that to index the corresponding entry in the undolist

Since fzf is run in a separate process you need to have some sort of index in the entry to be able to understand what item to preview, I’m assuming you wish to hide that item, for that you need to use fzf’s delimiter combined with the nth option, add this to your fzf_exec options:

this tells fzf both ] and : are used as delimiters (which the string is split by)
the nth options tells fzf to display only fields 2 onwards (man fzf for more info)

fzf_opts = {
    ["--delimiter"] = "'[\\]:]'",
    ["--with-nth"]       = "2..",
}

This technique is used throughout fzf-lua to hide/reformat the display of many providers (help, lines/blines, tags, symbols, etc).

Thanks all good now. Just one more question. How do I add custom config for commands like registers and lsp_references and the others? They aren't in the manual so does that mean they cannot be configured?

The manual is just too big as it is to hold it all, you can add any options under registers and it will be accepted, all lsp providers aside from symbols inherit from lsp, if you wish the do something specific to refs you can add the same options to the call lsp_referneces({ … }).
You can explore the default at:
https://github.com/ibhagwan/fzf-lua/blob/main/lua/fzf-lua/defaults.lua


Hashes are assumed to be only usize

h1 will fail on 32-bit targets if a hasher yields a u64 greater than u32::MAX:
https://github.com/Amanieu/hashbrown/blob/9068eb7a2268d879dc4453ac72238e8a992f1469/src/raw/mod.rs#L120-L126
The comment in h2 gives some insight to this, but that only applies to FxHash:
https://github.com/Amanieu/hashbrown/blob/9068eb7a2268d879dc4453ac72238e8a992f1469/src/raw/mod.rs#L131-L138
See also the failure in https://github.com/rust-lang/rust/pull/58623#issuecomment-482373125

Yes, this assert was mistakenly added as part of the clippy support, it should be removed.

Are there any tests using alternate hashes? Even RandomState should trigger this.

Replacing the assert with a comment explaining why the truncation is ok and adding a test that triggers this sounds good to me.

Is there an issue open to add a test for this ?

Tests were added in #63.

Awesome, thank you both for fixing this, and sorry that I broke it!


Adds 'purview sensitivitylabel list' command. Closes #4424

Adds purview sensitivitylabel list command. Closes #4424

Thanks for your awesome contribution 👍. You rock 🤩. We'll review it ASAP

Merged manually, thank you! 👏


Unable to build release version with react native 0.70.6

Describe the bug
While trying to build the release version of the android app, following error occurs:
* What went wrong:
Execution failed for task ':react-native-rtmp-publisher:verifyReleaseResources'.
> A failure occurred while executing com.android.build.gradle.tasks.VerifyLibraryResourcesTask$Action
   > Android resource linking failed
     ERROR:<path_to_project>/node_modules/react-native-rtmp-publisher/android/build/intermediates/merged_res/release/values/values.xml:2729: AAPT: error: resource android:attr/lStar not found.

To Reproduce
Steps to reproduce the behavior:

Create a project with latest react native version
Install and setup react-native-rtmp-publisher
Navigate to android folder and run ./gradlew assembleRelease
See error

Expected behavior
Release variant of the .apk should have been built successfully
Desktop (please complete the following information):

OS: macOS Ventura 13.1
React Native version 0.70.6
react-native-rtmp-publisher version 0.4.4

Hello @rranjan14,
It should be fixed at 0.4.6. Can you update and try it again?
PS: Android permission section is updated too, you should check that section after update


Demand Modifier

Hi I am looking at the code here, I notice that the demandmodifier.cs has a comment and a snippet that suggests that it is disabling residential levelup. Is that correct?

I've been usin the mod, with configured XML, and no - buildings do level up.

I have no idea how I missed this.
The code is to disable residential buildings from reporting that land value is too low. This is an open issue, although I'm not sure if it is still accurate.


Installation fails on ghc 7.10.2

Command ghc install hsdev fails with following error:
Resolving dependencies...
Configuring hsdev-<IP_ADDRESS>...
Building hsdev-<IP_ADDRESS>...
Failed to install hsdev-<IP_ADDRESS>
Build log ( /Users/kruk/.cabal/logs/hsdev-<IP_ADDRESS>.log ):
Configuring hsdev-<IP_ADDRESS>...
Building hsdev-<IP_ADDRESS>...
Preprocessing library hsdev-<IP_ADDRESS>...
[ 1 of 62] Compiling HsDev.Tools.Ghc.Prelude ( src/HsDev/Tools/Ghc/Prelude.hs, dist/build/HsDev/Tools/Ghc/Prelude.o )
[ 2 of 62] Compiling HsDev.Tools.Ghc.MGhc ( src/HsDev/Tools/Ghc/MGhc.hs, dist/build/HsDev/Tools/Ghc/MGhc.o )

src/HsDev/Tools/Ghc/MGhc.hs:31:1: Warning:
    The import of ‘Packages’ is redundant
      except perhaps to import instances from ‘Packages’
    To import instances alone, use: import Packages()
[ 3 of 62] Compiling HsDev.Version    ( src/HsDev/Version.hs, dist/build/HsDev/Version.o )
[ 4 of 62] Compiling HsDev.Tools.Ghc.Compat ( src/HsDev/Tools/Ghc/Compat.hs, dist/build/HsDev/Tools/Ghc/Compat.o )
[ 5 of 62] Compiling System.Directory.Paths ( src/System/Directory/Paths.hs, dist/build/System/Directory/Paths.o )
[ 6 of 62] Compiling System.Directory.Watcher ( src/System/Directory/Watcher.hs, dist/build/System/Directory/Watcher.o )
[ 7 of 62] Compiling HsDev.Util       ( src/HsDev/Util.hs, dist/build/HsDev/Util.o )

src/HsDev/Util.hs:77:19: Not in scope: ‘Dir.isSymbolicLink’
cabal: Error: some packages failed to install:
hsdev-<IP_ADDRESS> failed during the building phase. The exception was:
ExitFailure 1

ghc --version
The Glorious Glasgow Haskell Compilation System, version 7.10.2

The issue was already fixed in master via d62352c3fe99ee147ab5cfb4e5f05ef678b9a65f
I'm trying to fixup the meta-data on Hackage, but it's a bit more involved because there's almost no upper bounds so I stumble from one compile failure into the next one... :crying_cat_face:

@lonelyelk you could try to cabal update and retry... it /should/ work now w/ GHC 7.10.*

Thank you! It's resolved!

@hvr, could you explain, how can it be installed with 7.10.3? I get this:
rejecting: ghc-7.10.3/installed-99f... (conflict: ghc =>
directory==<IP_ADDRESS>/installed-825..., hsdev => directory>=<IP_ADDRESS>)

How do you fix it?

@mvoidex the latest version doesn't work w/ GHC 7.10.3, however the previous one does, and that's what cabal install hsdev will install for you, as that's what the cabal solver will select when using GHC 7.10.3.
Maybe a picture explains this a bit better: http://<IP_ADDRESS>:8080/package/hsdev

@hvr, thanks for explanation! I missunderstood and thought that there's a way to install hsdev-<IP_ADDRESS> with ghc-7.10.*

@lonelyelk, i've uploaded hsdev-<IP_ADDRESS>, which is buildable with ghc-7.10.3

@mvoidex worked like a charm. Thank you!


Pod topology hints

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind api-change
/kind bug
/kind cleanup
/kind deprecation
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

This should not be merged before #28

Just noticed: need to write unit tests for two new funcs. (GetPodTopologyHints(), GetPodRequestedResources)

@pablitoergosum Can you please rebase once we will merge MemoryManager unittests and put a little more description under commits messages and probably squash it to the single commit(adding the support for the GetPodTopologyHints). Because we will need to have more explanatory commit history

@cynepco3hahue Of course, I will do it with pleasure.


Feauture request: Add support for opacity map in .fbx files

After digging trough the default material source code I am not sure if opacity maps should even work with .fbx files (or general).
1. Reason why opacity maps should be supported:
Modelling package 3DsMax needs opacity maps in standard renderer (no alpha channel supported)
2. How to use opacity maps with sceneform at the time -requires workaround / steps performed by artists
Either follow workaround b) as described here #696
Or do it manually:
a) Add opacity map via 'injections' as described in #696 a)
b) Then create your own material definition with support for opacity map.
Example: (line 137 in fbx_material.sfm)
{         name: "opacity",         description: "Workaround for opacity map",         options: [           {             default: null,             valid_if: propUseOpacityMap != 1.0,             //blending: "opaque",             fragment: ""           }, {             default: sfm.sourceTexture("Opacity"),             valid_if: sfm.hasSourceTexture("Opacity"),              requires: ["uv0"],              fragment: |||                float myOpacityValue = texture(materialParams_opacity, getUV0()).r;                material.baseColor = material.baseColor * myOpacityValue;              |||           }         ]       }
3. What I would like to see change in Sceneform:
a) Modify the Sceneform importer to include support for opacity map textures
b) Add the lines default: sfm.sourceTexture("Opacity"),             valid_if: sfm.hasSourceTexture("Opacity"),              requires: ["uv0"],              fragment: |||                float myOpacityValue = texture(materialParams_opacity, getUV0()).r;                material.baseColor = material.baseColor * myOpacityValue;              |||
to the default .fbx material ( perhaps with a nicer layout, e.g. values opacity & opacityMap for sampled texture (like baseColor and baseColorMap)

your fix doesn't seem to work anymore. I force blending to transparent in a custom material .sfm and a png with transparency that is used as a texture doesn't have any transparency.


fixed metadata

:x: Validation status: errors

File
Status
Preview URL
Details

docs-ref-autogen/azure-arm-devtestlabs/FormulaPropertiesFromVm.yml
:x:Error

Details

:x:Error

Details

docs-ref-autogen/azure-arm-devtestlabs/FormulaPropertiesFromVm.yml

[Error] Publishing of document 'docs-ref-autogen/azure-arm-devtestlabs/FormulaPropertiesFromVm.yml' to document hosting service failed with asset id: api/azure-arm-devtestlabs/formulapropertiesfromvm locale: en-us, depot name: MSDN.node-api, branch name: pr-en-us-384. Error: The client could not finish the operation within specified timeout.

[Error] An exception occurred during the build process. Please check the raw log and retry building your content again. If the issue persists, please open a ticket in http://SiteHelp and include the URL of publishing report.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/billing.md
:white_check_mark:Succeeded
View (azure-node-latest)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off
@rloutlaw - can you merge this metadata fix?


FontSize?

I'm trying :-)
I noticed there is a FontSize property on a Label but there doesn't appear to be on a Button. The Xamarin button does have a FontSize (I believe). I'm trying to use Xamarin tutorials as a guide but can't quite figure out how to do similar things with Blazor.
Would my reading all the project source fill in the blanks do you think?

Hi @tleylan thanks for checking out this project! You're not missing anything - some properties were forgotten in the initial release, including Button's FontSize property.
I added the missing property (plus several others) in this commit from a few days ago:
https://github.com/xamarin/MobileBlazorBindings/commit/eee7d5fae64befb51ca6a807e02444410caa16fa#diff-68da0bdd265e5970cfdce0e8442e7635R26
We're planning to publish an update next week so stay tuned and we'll have this available very soon!

@Eilon Thanks for the answer and the reassurance that I'm not just old :-) I think I should read through the code a bit more but some of the systems like ASP.Net,, Blazor and such contain so much code it seems that would be all I would have time for.
I am looking forward to the next release.

Reading large code bases can be intimidating, I completely agree. I found it best to learn how the things I directly interact with work. For example, just reading the code of one Mobile Blazor Bindings component (easy). Then perhaps one handler (also easy). Seeing how they interact, where they reference each other, what else they reference, etc. Then, one day, like a year later, it starts to make sense as a system 😉


Action. Not Routing to Siblings?

Version
Tell us which versions you are using:
  "dependencies": {
    "native-base": "^0.5.18",
    "navbar-native": "^1.6.1",
    "react": "15.4.1",
    "react-native": "0.39.2",
    "react-native-drawer": "^2.3.0",
    "react-native-router-flux": "^3.37.0",
    "react-native-vector-icons": "^3.0.0"
  },

Expected behaviour
When navigating to the next scene in a collection of scenes, i.e.

outerScene

innerSceneA
innerSceneB

outerSceneB

I should be able to call Actions.innerSceneB() from innerSceneA.
Actual behaviour
When I call Actions.innerSceneB() it seems that the router pushes another copy of A. This is evidenced by the fact that I have to pop N times (where I click my button N times) to get back to the original scene that triggered the sequence.
Steps to reproduce

Create a simple application with nested scenes as per the above.
Attempt to navigate to the adjacent scene.
The pushed route will instead be another copy of the first scene.

Example routing setup:
           <Router>
                <Scene key="root">
                    <Scene key="ImageCover" component={ImageCover}>
                        <Scene key="ImageCoverNavigation" component={NavigationBar}>
                            <Scene key="welcomeScreen" component={WelcomeScreen} title="Welcome Steve" />
                        </Scene>
                    </Scene>
                </Scene>
                <Scene key="journey" component={SequenceNavigation}>
                    <Scene key="search" component={SearchScreen} title="Search" />
                    <Scene key="results" component={ResultsScreen} title="Results"  />
                </Scene>
            </Router>

Basically I can't Actions.results() from search. I've also tried stripping off the wrapper component on the journey element, but no dice either.

Problem existed at the keyboard/chair interface layer. Has been resolved.


iina: fix 1.3.2 hash mismatch and add update script

Description of changes

https://github.com/NixOS/nixpkgs/pull/242290 introduces a hash mismatch to iina 1.3.2
nix build .#iina
error: hash mismatch in fixed-output derivation '/nix/store/xhpwbllrvvild7zq3rlm60jdnl1kc3bd-IINA.v1.3.2.dmg.drv':
         specified: sha256-yieAcMc3rqoURsAcc8iAbe1pohlAU3r76FsgUeiNTP8=
            got:    sha256-rF5yv2QHWVUUsyf/u78jWRn4C629GBJgB/i8YnaKHBk=

fix the mismatch
add update script to prevent hash mismatch in the future

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

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

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

On aarch64-darwin:
$ nix run nixpkgs#nixpkgs-review -- pr 242520
1 package updated:
iina
1 package built:
iina

No, the update script cannot prevent hash mismatch in this case, see https://github.com/iina/iina/discussions/4479#discussioncomment-6392096.

Thanks! I didn't even know passthru.updateScript, nix-update-script { }, gitUpdater { } are available.


Add readme, logo

closes #6, closes #7

@rultor merge

@rultor merge

@l3r8yj OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@l3r8yj Done! FYI, the full log is here (took me 1min)


Allow contextually visible whitespace

I would love a Render Whitespace setting that only renders outliers as visible. Since vscode already does indentation detection a fairly intuitive implementation seems possible:
Use the local Insert Spaces setting.

if it is true, render visible tabs but invisible spaces
if it is false, render  visible spaces but invisible tabs

This is inspired by vims listchars option: http://vimdoc.sourceforge.net/htmldoc/options.html#'listchars'
To give an example the following configuration is unobstrusive when spaces are used but makes tabs or trailing spaces visible:
set listchars=tab:␉·,trail:␠,nbsp:⎵

What setting names would you suggest? Another option in editor.renderWhitespace?


No JSON examples

The examples folder has all yaml.  No JSON.
https://github.com/OAI/OpenAPI-Specification/tree/master/examples/v3.0

See #1385 and the discussion on #1357


Stop using links for buttons and vice versa

The "Create Plan" link looks like a button, but is actually a link. This can cause confusion for screen reader users, as screen reading software allows the user to bring up a list of links on a page, as well as a list of just buttons. This "Create Plan" item can actually use the  tag, since it's performing an action. This will solve any confusion issues.
From old pivotal ticket: https://www.pivotaltracker.com/story/show/131647237

Just focus on non org-admin/super-admin pages for this first pass

I've looked through some explanations about this and found that its appropriate to use a link if the user will be directed away from the current page. If the clicking the element does something but the user is not redirected then a button should be used.
So, a form should have a submit button if the user is returned to the existing page and a link for 'cancel' if they are returned elsewhere.

What exactly is the desired outcome from this ticket?
Looking at the documentation on aria buttons, would it be acceptable to just add the 'button' role to any links which do not redirect the user to another page?  This is the approach I am currently taking with this.
I also wanted to know if replacing submit buttons with accessible_submit_button's is within the scope of this ticket, or if it will be the subject of another ticket.
@briri

I think that we can go with the role attribute for now. They will provide recommendations to us after the test if there are any issues with it.
We should ideally use the accessible submit button but they each require a bit of JS. I was going to open a separate ticket for that after the accessibility test.

ok, thanks.  I'll continue on with the role attribute (and aria-labelledby/aria-label) for the buttons then.

@xsrust I added the role="button" attribute to all of the popover links on the forms while I was in adding aria tags for the font-awesome icons.

Closing this pending next round of accessibility testing


add support for EG6832 mcu

EG6832 is made by EGmicro.com.
this little MCU has 8k sram +64k flash.
flash is located at 0x00000000 rather than 0x8000000 :)
must first use  pyocd erase -t eg6832 --chip, then pyocd load -t eg6832 xxx.hex
now tested by the eval board selled at EG6832 eval board

why these checks are not run?

This is a good question, I'm trying to understand that. (thank you for leaving this message as it helps track when it started to fail).


add screenshot

More changes coming.

@LukasReschke at your service: added screenshot. If we don't get a vid, this'll do.

@jospoortvliet Shouldn't this go against the stable8.0 branch as @tomneedham pointed out?

@MorrisJobke on the Database - I would need a screenshot of that, I don't have this myself. On the branch - no clue... Don't we always go against master? I am clueless, officially :dancer:
Besides, I'd like to get this live... If there's nothing badly wrong, that is.

Now checking this out :)

@jospoortvliet Checkout skype :)


Let's upgrade the docs to use actions/setup-python@v5

Like

#18767

https://github.com/actions/setup-python/releases
- actions/setup-python@v4
+ actions/setup-python@v5

https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-python#installing-dependencies
@dmitry-shibanov @HarithaVattikuti Your reviews, please.

Why:
See improvements and bug fixes at https://github.com/actions/setup-python/releases

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@cclauss Thanks so much for opening a PR! I'll get this triaged for review ✨

@cclauss Thanks so much for opening a PR with this fix! I'll update the branch and get this merged once tests are passing 🍏


defaultIndex does not work as expected

The defaultIndex prop does not work as expected, for the following example it results in:

defaultIndex=0, index 0 shown
defaultIndex=1, index 6 shown
defaultIndex=2, index 5 shown
defaultIndex=3, index 4 shown
defaultIndex=4, index 3 shown
defaultIndex=5, index 2 shown
defaultIndex=6, index 1 shown

export default function App() {
  return (
    <View
      style={{
        flex: 1,
        backgroundColor: 'black',
      }}>
      <View style={{height: 300}}>
        <Carousel
          loop={true}
          width={width}
          data={data}
          defaultIndex={0}
          renderItem={({color}, index) => {
            return (
              <View
                style={{
                  backgroundColor: color,
                  flex: 1,
                }}>
                <View
                  style={{
                    flex: 1,
                    backgroundColor: color,
                    justifyContent: 'center',
                    alignItems: 'center',
                  }}>
                  <Text style={{fontSize: 80}}>{index}</Text>
                </View>
              </View>
            );
          }}
        />
      </View>
    </View>
  );
}

video

I think I know what happened, I will fix it as soon as possible.

I am sorry that I have been busy recently. I am still paying attention to the problem and I will fix it as soon as possible, maybe this week.

v1.0.5
THX! 🍺！！～

Thanks, just tested it, it works!


Remove duplicated '-' on the groupId when sending a message via Telegram

The '-' is already appended to the groupId on the setGroupId. I forgot to remove it from here

It is working fine now. Tested locally and got the messages


Fix incorrect URL

This probably explains why the Wiki GettingStarted page keeps getting re-created by random people. Nice work!

Thanks.
I see that you have signed the CLA. However, we need to add an entry to AUTHORS as well. Since the AUTHORS file is on master we will need to do two PR. Sorry about that.
I can also just make the change to index.html if you do not are about getting the commit?

The patch needs to be applied to master then pushed to gh-pages when we
publish.
On Thu, Jan 29, 2015 at 8:47 AM, Erik Arvidsson<EMAIL_ADDRESS>wrote:

Thanks.
I see that you have signed the CLA. However, we need to add an entry to
AUTHORS as well. Since the AUTHORS file is on master we will need to do two
PR. Sorry about that.
I can also just make the change to index.html if you do not are about
getting the commit?
—
Reply to this email directly or view it on GitHub
https://github.com/google/traceur-compiler/pull/1665#issuecomment-72059039
.

True. I thought that we only had index.html on the gh-pages branch.

I don't need to be added to AUTHORS.

Thanks the fix is in the repo and will be pushed on the next publish.  See #1679


dev-dependencies are not allowed to be optional

Because dev-dependencies are not allowed to be optional (cc @ehuss), I have to make serde_test an unconditional dev-dependency, which means that it will always be part of the dependency graph of my crate when building it, and because serde_test requires std, this means that building my crate ends up always linking against the standard library.
My crate is a #[no_std] crate, so I cannot accept that, therefore, I cannot use serde_test for testing.
The only workaround I can think of, is to make serde_test an optional dependency of serde, and for serde to re-export it when this optional dependency is enabled. This way, I can optionally depend on serde, without any features, and I can add a cargo feature to my crate that is enabled only for testing, and that enabled the serde_test feature of serde. This would allow me to pull in serde_test optionally only when testing, allowing my application to only link against the standard library there, and not unconditionally (as it would be caused by an unconditional dev-dependency to serde_test).

I suppose that, alternatively, I can add serde_test as an optional, non-dev dependency. Hmm. Don't know what will work best.

Currently serde_test is designed to depend on serde so serde can't also depend on serde_test. I would recommend giving your crate an optional ordinary dependency on serde_test and following up with Cargo to improve the flexibility on their end.

Ran into this same issue, and wanted to add here that using -Z features=dev_dep on nightly was sufficient to resolve this problem.


Use SVG flag icons only on Windows

Made a small change using @tananaev old code to determine whether to use emojis or svg icons

Maybe a good change? Feel free to close without merging if its overkill!

I think it's fine to use SVGs for all platforms. I actually like how they look more. And also more consistency.


Fix type errors in jessidhia/patch-1

This is the same thing as #960 but with the type errors fixed, maybe.
If it's desirable I could make this a PR against jessidhia/patch-1 instead of against master.
I am getting some really weird feedback when I run npm test though, so I am just starting this PR to see what Travis thinks of it.

Pull Request Test Coverage Report for Build 2438

5 of 7 (71.43%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 91.933%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/config/config-set.ts
5
7
71.43%

Totals

Change from base Build 2437:
0.02%

Covered Lines:
913

Relevant Lines:
958

💛  - Coveralls

Oh neat, the tests appear to have passed.
Note that this PR doesn't address https://github.com/kulshekhar/ts-jest/pull/960#issuecomment-464074343 (unfortunately I don't understand enough about Babel to address that), it just fixes typings so the PR doesn't break the build.

Thanks @GeeWee!  Since you merged this into master, should #960 be closed?
Also, how soon do you think you will publish a new release to npm?  I originally tried setting my package.json's entry for ts-jest to https://github.com/kulshekhar/ts-jest#670503f65a79ec62712e5e4488b734c092b20a0f but that doesn't seem to work because it looks like this project has a build step that runs before publishing to npm...

Ack, ignore the part about re-publishing to npm--I realized ts-jest has a npm prepare script and that it wasn't executing on my CI system for a funky reason. Just fixed that and I'm able to use 670503f65a79ec62712e5e4488b734c092b20a0f directly now!

Why should #960 be closed? Isn't it about more than the typings?

Er yes, #960 is about more than the typings, but it contains broken typings... This PR was meant to fix #960's broken typings, and as such it builds upon #960 (note that its first two commits are ebe823780b39867bb8eff4a5b86ff96b22854f42 and
3c2b1cf, the same two commits that constitute #960)... 😣

Aw dang, I actually thought this was just a fix that allowed #960 to move on. I shouldn't have merged this in. Oh well.


Create codeql-analysis.yml

Integrate with Github static code analysis.

don't do. not ready for prime time. come back later.


Improve commands to use defaults as supplied in NoxMetaData

NoxMetaData is defined for each command addin
This metadata includes a default value for each input
It would be nice if these defaults can be accessed in the BeginAsync method of the addin

Completed in PR #24


UCP limitation of UCP disk free monitoring and associated Prom metric

Deploy preview for docsdocker ready!
Built with commit 68fb45b34a754330d1798ca6db637af78b82a83e
https://deploy-preview-8270--docsdocker.netlify.com

@cameronmartin Thank you for the quick responses and help!

@david-yu Hi David, can you confirm what UCP versions are affected by this? Thank you in advance!

This affects 3.0.x and 3.1.x not 2.2.x since it does not use Kube. As Cameron suggested I would use the following wording for both versions.

Web UI disk usage metrics, including free space, only reflect the Docker managed portion of the filesystem: /var/lib/docker.  To monitor the total space available on each filesystem of a UCP worker or manager, you must deploy a third party monitoring solution to monitor the operating system.

@david-yu @cameronmartin Thank you!! I've removed the older version changes and incorporated Cameron's wording.


comparing the hardcoded high density param-set to the json in wiki

Required Info

Camera Model
D435

Firmware Version
5_12_8_200

SDK Version
2.39.0

Language
C++

Issue Description
after changing the preset params to HIGH-DENSITY and reading the json file It seems different than the one in the wiki page.
I used this function to change the values - sensor.set_option(RS2_OPTION_VISUAL_PRESET, _val);
while _val was casted to "High Density" using this function rs2_rs400_visual_preset_to_string((rs2_rs400_visual_preset)_val)
After that I read the json params again using this code:
    rs2::device device =  m_profile.get_device();
    auto advanced = device.as<rs400::advanced_mode>();
    auto new_parmasAsJson = advanced.serialize_json();
    std::cout << new_parmasAsJson <<std::endl;

therefore these lines was printed:
{
"aux-param-autoexposure-setpoint": "1536",
"aux-param-colorcorrection1": "0.298828",
"aux-param-colorcorrection10": "-0",
"aux-param-colorcorrection11": "-0",
"aux-param-colorcorrection12": "-0",
"aux-param-colorcorrection2": "0.293945",
"aux-param-colorcorrection3": "0.293945",
"aux-param-colorcorrection4": "0.114258",
"aux-param-colorcorrection5": "-0",
"aux-param-colorcorrection6": "-0",
"aux-param-colorcorrection7": "-0",
"aux-param-colorcorrection8": "-0",
"aux-param-colorcorrection9": "-0",
"aux-param-depthclampmax": "65536",
"aux-param-depthclampmin": "0",
"aux-param-disparityshift": "0",
"controls-autoexposure-auto": "True",
"controls-autoexposure-manual": "8500",
"controls-color-autoexposure-auto": "True",
"controls-color-autoexposure-manual": "166",
"controls-color-backlight-compensation": "0",
"controls-color-brightness": "0",
"controls-color-contrast": "50",
"controls-color-gain": "64",
"controls-color-gamma": "300",
"controls-color-hue": "0",
"controls-color-power-line-frequency": "3",
"controls-color-saturation": "64",
"controls-color-sharpness": "50",
"controls-color-white-balance-auto": "True",
"controls-color-white-balance-manual": "4600",
"controls-depth-gain": "16",
"controls-laserpower": "150",
"controls-laserstate": "on",
"ignoreSAD": "0",
"param-amplitude-factor": "0",
"param-autoexposure-setpoint": "1536",
"param-censusenablereg-udiameter": "9",
"param-censusenablereg-vdiameter": "3",
"param-censususize": "9",
"param-censusvsize": "3",
"param-depthclampmax": "65536",
"param-depthclampmin": "0",
"param-depthunits": "1000",
"param-disableraucolor": "0",
"param-disablesadcolor": "0",
"param-disablesadnormalize": "0",
"param-disablesloleftcolor": "1",
"param-disableslorightcolor": "0",
"param-disparitymode": "0",
"param-disparityshift": "0",
"param-lambdaad": "850",
"param-lambdacensus": "19",
"param-leftrightthreshold": "32",
"param-maxscorethreshb": "1949",
"param-medianthreshold": "276",
"param-minscorethresha": "68",
"param-neighborthresh": "4",
"param-raumine": "7",
"param-rauminn": "1",
"param-rauminnssum": "6",
"param-raumins": "3",
"param-rauminw": "6",
"param-rauminwesum": "14",
"param-regioncolorthresholdb": "0.0107632",
"param-regioncolorthresholdg": "0.645793",
"param-regioncolorthresholdr": "0.0166341",
"param-regionshrinku": "4",
"param-regionshrinkv": "1",
"param-robbinsmonrodecrement": "1",
"param-robbinsmonroincrement": "4",
"param-rsmdiffthreshold": "5.0625",
"param-rsmrauslodiffthreshold": "1",
"param-rsmremovethreshold": "0.446429",
"param-scanlineedgetaub": "4",
"param-scanlineedgetaug": "542",
"param-scanlineedgetaur": "982",
"param-scanlinep1": "479",
"param-scanlinep1onediscon": "4",
"param-scanlinep1twodiscon": "25",
"param-scanlinep2": "342",
"param-scanlinep2onediscon": "69",
"param-scanlinep2twodiscon": "225",
"param-secondpeakdelta": "6",
"param-texturecountthresh": "1",
"param-texturedifferencethresh": "0",
"param-usersm": "1",
"param-zunits": "1000"
}

I do see that the values was changed because I also printed the json before the process.
comparing this json to the json in the wiki reveled that the values are different. I used text-compare.com to compare then and here is a small part of it.

you can see that the max/median/min score THR are different and that the lambda ad/census are also different.
Can you maybe check what should we use? the default hardcoded version or the wiki one?

Hi @avizipi  If you are using one of the built-in presets then I recommend using the RS2_OPTION_VISUAL_PRESET instruction to apply it and not use the json file version of the preset on the Visual Presets web-page.  This should ensure that your script has the same configuration changes as when choosing that preset in the RealSense Viewer tool.
The scripting for loading a json from a file instead of applying a built-in preset is different and more complicated, so using a built-in preset in your script if possible is much easier.

Thanks for your replay.
Did you also notice the different between using the RS2_OPTION_VISUAL_PRESET preset values and the wiki values?

I tested in the Viewer with both the built-in High Density preset and the json file version of it and there was no difference in the depth image for each.

Also in my indoor scene I didn't see any visible changes in the depth image.
But what about the values them self, can you confirm that the wiki and hardcoded params are different? and if so can you elaborate on these differences?

I checked the Advanced Mode values of the High Density built-in preset in my Viewer with a D435i and compared them to the json file values.  Some of the values for my built-in preset were different to yours.  I do not think that it is significant though.  Advanced Mode parameters are managed by a machine learning algorithm because of the complex ways in which they interact with each other, which is the reason why Advanced Mode options do not have documentation (though RealSense users are free to experiment with the options to see how changes affect the image).
So if built-in and json files produce the same visual results, I would recommend not being concerned by it.


angularAMD + UI Router + Multiple named views

Hi,
I am just exploring angularAMD to use in my project, its been working great, but just not sure how should i configure for multiple named views,
about.html:

The About Page
This page demonstrates multiple and named views.

ColumnOne View

ColumnTwo View

app.config.js:
 .state('about', angularAMD.route({
                    url: '/about',
                    templateUrl: 'app/partials/about.html',
                    'columnOne@about': { template: 'Look I am a column!' },
                    'columnTwo@about': {
                        templateUrl: 'app/partials/table-data.html',
                        controller: 'scotchController'
                    }
                }));
I cannot show the columnone and columntwo besides about html.

If I had to guess without looking at all the code I would recommend trying this:
angular.state('about', {
    url: '/about',
    templateUrl: 'app/partials/about.html',
    'columnOne@about': { template: 'Look I am a column!' },
    'columnTwo@about': angularAMD.route({
        templateUrl: 'app/partials/table-data.html',
        controller: 'scotchController'
    })
});

If you don't have a controller for the other two views you don't need to use angularAMD.route() with them.
If this doesn't work - set up a plunker with your problem and link it.
Best,
Mike

I am sorry Mike, the code I posted above was missing views {}, and I also applied angularAMD.route only where needed as you said, we don't need if we don't controller to the view as below:
.state('about', {
url: '/about',
views: {
// the main template will be placed here (relatively named)
'': { templateUrl: 'app/partials/about.html' },
                        // the child views will be defined here (absolutely named)
                        'columnOne@about': { template: 'Look I am a column!' },

                        // for column two, we'll define a separate controller
                        'columnTwo@about': angularAMD.route({
                            templateUrl: 'app/partials/table-data.html',
                            controller: 'scotchController',
                            controllerAs: 'table',
                            controllerUrl: 'app/partials/scotch.controller'
                        })
                    }

                });

Thanks alot Mike, closing the issue now.


draft: [DIR-548] webkit workaround

Please do not merge, we should discuss this first.
See the comments in the file.
This will "force" clicks only in the context where this is needed (when tests run locally on webkit).
However, I am not really comfortable with the logical complexity this adds to the tests. I think I'd rather keep them simple and live with tests failing locally in webkit until we know more.

Closed, we decided against implementing this as it would add too much complexity to the tests.


Fails to run

Windows 10, Gimp 2.10.36. webui is running with --api as a command-line argument. Plug-in directory is properly set in Gimp preferences.
I don't get an "AI" menu, but I do have a "GimpFusion" menu. All menu items are grayed out. Having run Gimp with --verbose. Searching that output for keyword "stable" it only appears once:
Querying plug-in: 'C:\Users\Dave\AppData\Roaming\GIMP\2.10\plug-ins\stable_gimpfusion.py'
I do notice that in the plug-ins folder there is now a stable_gimpfusion.json file, whose contents are below:
{"cfg_scale": 7.5, "cn_models": ["None"], "prompt": "", "models": ["realcartoon3d_v14.safetensors [6ac3a48031]", "v1-5-pruned-emaonly.safetensors [6ce0161689]"], "mask_blur": 4, "api_base": "http://<IP_ADDRESS>:7860", "denoising_strength": 0.8, "is_server_running": true, "batch_size": 1, "height": 512, "width": 512, "seed": -1, "steps": 50, "sd_model_checkpoint": "v1-5-pruned-emaonly.safetensors [6ce0161689]", "sampler_name": "Euler a", "model": "", "negative_prompt": ""}
It seems that it is indeed picking up my running installation of SD. Any ideas?

GAH! My apologies. I didn't even think to open or create a new document. Once I created a new document the menu items are all available.


refactor all

fix metadata acquisition, at this point expecting images for batch annotator to be opened with napari-aicsimageio
match ome metadata between image and labels layer by switching to OmeTiffWriter and explicitly stating metadata
remove label_dims from batch_training because dims of label and img should always match
now properly save physical pixel sizes to metadata

Codecov Report

Merging #10 (ae77f70) into main (f95912b) will decrease coverage by 17.26%.
The diff coverage is 24.13%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main      #10       +/-   ##
===========================================
- Coverage   47.72%   30.46%   -17.26%
===========================================
  Files           3        3
  Lines         132      128        -4
===========================================
- Hits           63       39       -24
- Misses         69       89       +20

Impacted Files
Coverage Δ

src/napari_ndev/_widget.py
23.00% <12.00%> (-19.24%)
:arrow_down:

src/napari_ndev/_tests/test_widget.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Feature/quest window

Added the quest panel
Moved current quest text to show up in that panel
TODO:
show all quests at the same time in the panel - add scrollbar
use colors to indicate quest completion
have a popup when quest completed detailing the new unlocks
new quests appear after finishing one e.g. 10/10 rats -> 10/100 rats
add stats to one of the inner quest panel tabs

Implementation is pretty straight forward and looks fine. I’ll test it when I get home


[3.6] Editor error message: editor/script_editor_debugger.cpp:419 - Condition "!connection->is_connected_to_host()" is true

Godot version
v3.6.beta3.official [21ab700f2]
System information
Linux Debian 11.8
Issue description
I can't repro this on demand, but I'm seeing it happen fairly frequently with v3.6.beta3 (Linux) when working in the editor for a while.  Never saw this on 3.5.2.stable.  Happens sometimes after stopping a running scene, not always.
Seems harmless, with no ill effect; nonetheless it's definitely a new error or regression for 3.6.

--- Debugging process started ---
Godot Engine v3.6.beta3.official.21ab700f2 - https://godotengine.org
OpenGL ES 3.0 Renderer: Mesa Intel(R) HD Graphics (BDW GT1)
Async. shader compilation: OFF
editor/script_editor_debugger.cpp:419 - Condition "!connection->is_connected_to_host()" is true.
--- Debugging process stopped ---

I'm going to switch to previous 3.6 betas for my regular daily use to see if I can pinpoint which build introduced it, and will record observations here.
UPDATE: Could not trigger the error in 3.6-beta2 after an hour of heavy editor use and frequent runs.  After switching back to 3.6-beta3 I encountered the error message within 10 minutes of use.  Pretty sure this is a regression for Beta3.  Now focusing on trying to repro, but it does not exhibit any consistency.
Steps to reproduce
No identified trigger steps yet.
Minimal reproduction project
No MRP yet.

I was running some earlier official editor builds for other reasons, and I noticed this same error being reported in 3.4.5-stable.

Because I now know this error appears in much earlier stable builds, and isn't limited to the 3.6 beta build, I'm going to close this issue on the belief that something has changed on my end recently with my Linux/Debian setup, and whatever changed is likely triggering the error message.  Were it a widespread issue, it should have been reported long ago.

Closing, as noted above.


Change publish button to “save”  in admin portal>aid packages

[ ] Change publish button to “save”  in admin portal>aid packages

Hi, this needs to be deleted. There was a new requirement today, Manoj.
Check the other issue on publish buttton.
On Mon, 18 Jul 2022 at 21:31, Manoj Lakshan @.***>
wrote:

Shall I work on this?
—
Reply to this email directly, view it on GitHub
https://github.com/LSFLK/MedicinesforLK/issues/208#issuecomment-1187679741,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKTGXTA42JWBDTW676B4YNLVUV5VDANCNFSM53ZZUIKA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Sherazad Hamit
Executive Director
Lanka Software Foundation https://opensource.lk/
M: +94 777 37 49 57
E: @.***
https://www.linkedin.com/in/sherazadhamit/


forward proxy problem

if (ctx.containsKey("forward.to")) {
    return null;
}

Code excerpt from org.springframework.cloud.netflix.zuul.web.ZuulHandlerMapping.lookupHandler at line 87-89
Why do you return null when RequestContext contains "forward.to" ?
returning null causes forward proxy to follow the request, ZuulHandler is not found,
This can cause forward to zuul local services not available.
so, i want remove "forward.to" from RequestContext In a custom SendForwardFilter,  I'm not sure if it will cause other problems.

Can you explain what you are trying to accomplish rather than specific symptoms?

I have the same issue, could you please explain why this null check is required?
What I'm trying to achieve is to rewrite all urls, for example:
routes:
foo:
path: /foo/**
url: forward:/bar
bar:
path: /bar/**
serviceId: bar
This way if I request /foo/id/123, it will forward to /bar/id/123 and then this will be handled by the Zuul filters through the service discovery. However, at the moment, because of that null check, I'm getting a No handler mapping found for from ZuulHandlerMapping. I tried removing that key from the context and it seems to be working without a problem.

@spencergibb
There’s no exceptions, I’m just seeing that with trace enabled in the logs. What’s basically happening is:

My forward to mapping is detecting a valid request
The request reaches the Forward Zuul filter.
The filter forwards and the request goes back to ZuulHandlerMapping
Because “forward.to” was set by the PreDecorationFilter, the ZuulHandlerMapping now goes into the if mentioned above and returns a null
As a result I get a 404, even though the forwarded to path does exist in the routes and if I request it on its own everything works fine

I suppose that the Forwarding feature was not meant for this use case, but I don’t see why it cannot be enabled. Are there any concerns for the request looping back through all the Zuul Filters after a forward?


Release 1.7 - Store CSV properties as strings

Signed-off-by: Mandy Chessell<EMAIL_ADDRESS>Signed-off-by: Nigel Jones<EMAIL_ADDRESS>Partial backport of #2966
Draft ... testing ..

CTS passed ok, asset management notebook fine. Looks good to merge @mandy-chessell


document.write broken the Turbolinks

Describe the bug
I've implemented divisima html template from colorlib, and in the footer there's script like this
<script>document.write(new Date().getFullYear());</script>, after i run it whenever i click on a link helper
<%= link_to ... %> it will return blank page, head is empty and body is only have 2020 text.
To Reproduce
Implement divisima template from colorlib on your app, take the footer section.
Steps to reproduce the behavior:

click on any link helper <%= link_to ... %>
It will return blank page with 2020 text

Details (please complete the following information):

Operating System: MacOS Catalina 10.15
Browser: Edge Version 84.0.522.44
Turbolinks Version 5.2.1

Screenshots

See: #267 and #513


Leading is too large and text over-blurred

please attach the document.

https://yadi.sk/i/qhiuBiGdxF3ugA

resolved with 815dad028f809f732405ac1db9d054075a2da409


Store roles & qualifications for Users

Store roles & qualifications for Users
Add two new tables for storing roles & qualifications
Implement GET /profile endpoint
This returns info for the logged in user for the frontend to use

 Basic allocation of applications to assessors


[Suggestion] Auto-Use Treasure

It'd be nice not to have to manually watch the treasure cooldowns and have the script use treasure whenever it's not on cooldown.

#181


Create a Nightly Beta tests workflow

This pull request creates a Nightly beta test workflow to run the tests agains the latest Docker beta tag and detect any issue before the final version is released.

coverage: 100.0%. remained the same
when pulling 2c11c40415ac2a4051bd6a3fb12e633e4a25dc97 on create_nightly_beta_tests
into 1a81f407809efc5d2b5def69d37bce2fb1743276 on master.


changed testcase to load lua string instead of vipsImage

Sorry, but i had understood that load_from_buffer method had to be used to load a lua string with an image instead of an vipsImage. This will be needed for images got from curl requests for example.

Yes, that's right, it's
local string = im:write_to_buffer(".jpg")

and string will hold the image, but formatted as a jpg file. You can write this to a file called "something.jpg" and it'll load into an image viewer. Conversely:
local im2 = vips.Image.new_from_buffer(string)

Will sniff the filetype from the string, then decode with a jpeg decoder to make a new image.

Oh hang on, what do you mean about curl requests? Is there some feature missing?

if i have a lua string with an image (read from file with f:read("*all") or from a curl request or something else then vips) then it won't work.
Because of this i had changed the testcase to load image with lua into a lua string und give this string to new_from_buffer method. This is the exact opposite to write_to_buffer where we save a lua string with lua file write method.
For me it's not working in this case.

It should work, just load the file into a string and call vips.Image.new_from_buffer. This is what the "can load a jpeg from a buffer" test is doing, isn't it? It's working for me:
$ busted .
●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●●
67 successes / 0 failures / 0 errors / 0 pending : 0.252777 seconds

Though there seems to be a reference counting problem, about 50% of the time it's failing because of objects becoming lost. I'll try to fix that next.

Yes, that is what the test is doing.
Strange, because for me it's not working.
If i call it in a simple script i've get segfaults every time. :-(


Add initial version of the search extension

Description
This pr adds the new search extension which indexes files and directories and makes them searchable using the search service from within the web UI.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Checklist:

[X] Code changes
[X] Unit tests added
[ ] Acceptance tests added
[ ] Documentation ticket raised:

file names are indexed and show up in search results on the API, the web ui/owncloudsdk still filters them though and it seems folder are not indexed, yet. still, the PoC works!

:boom: Acceptance test Core-API-Tests-ocis-storage-1 failed. Further test are cancelled...

runsh: Total unexpected failed scenarios throughout the test run:
apiFavorites/favorites.feature:115
apiFavorites/favorites.feature:116
apiFavorites/favorites.feature:141
apiFavorites/favorites.feature:142
apiFavorites/favorites.feature:267
apiFavorites/favorites.feature:268

fail because the proxy would have to route REPORT requests to /remote.php/dav based on the body:

reva ocdav implements favorites
ocis webdav implements search

[ ] use search to provide lookup for favorites?
[ ] needs to add favorite to index


use make update-go-verison to update go version in Dockerfile

Thanks for contributing!

What type of PR is this?
Required labels:

release/none

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Keep the Go version in the go.mod file consistent with the one in the Dockerfile

/close


Wrong code generatation for expression lambdas

Describe the bug
Code generation for lambdas does not work properly if the lambda declares new local declarations.
To Reproduce
package train

pipeline house {

    val data = Table.fromCsvFile("data/train.csv");
    val heat = data.plotCorrelationHeatmap();

    val remove = data.removeColumns(["Id","MSSubClass","MSZoning","LotFrontage","LotArea","Street","Alley","LotShape","LandContour","Utilities","LotConfig","LandSlope","Neighborhood","Condition1","Condition2","BldgType","HouseStyle","OverallCond","YearBuilt","YearRemodAdd","RoofStyle","RoofMatl","Exterior1st","Exterior2nd","MasVnrType","MasVnrArea","ExterQual","ExterCond","Foundation","BsmtQual","BsmtCond","BsmtExposure","BsmtFinType1","BsmtFinSF1","BsmtFinType2","BsmtFinSF2","BsmtUnfSF","TotalBsmtSF","Heating","HeatingQC","CentralAir","Electrical","1stFlrSF","2ndFlrSF","LowQualFinSF","BsmtFullBath","BsmtHalfBath","FullBath","HalfBath","BedroomAbvGr","KitchenAbvGr","KitchenQual","TotRmsAbvGrd","Functional","Fireplaces","FireplaceQu","GarageType","GarageYrBlt","GarageFinish","GarageQual","GarageCond","PavedDrive","WoodDeckSF","OpenPorchSF","EnclosedPorch","3SsnPorch","ScreenPorch","PoolArea","PoolQC","Fence","MiscFeature","MiscVal","MoSold","YrSold","SaleType","SaleCondition"]);

    val removedoutliers = remove.filterRows((row) -> ((row.getValue("GarageCars") as Int) < 4));
}

Expected behavior
Code generation should work.
Screenshots (optional)
No response
Additional Context (optional)
No response

:tada: This issue has been resolved in version 0.14.1 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.14.1
GitHub release

Your semantic-release bot :package::rocket:


https://www.tensorflow.org/install/errors

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug, a feature request, or a significant problem with documentation (for small docs fixes please send a PR instead).
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version (use command below):
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

You can collect some of this information using our environment capture script:
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

@Ruma-Dhanawate
please update the template, we cannot find the tensorflow version, steps followed before you faced the error and error logs for us to analyze the issue.
We ask for this in the issue submission template, because it is really difficult to help without that information. Thanks!

@Ruma-Dhanawate
please update as per above comment

Automatically closing due to lack of recent activity. Please update the issue when new information becomes available, and we will reopen the issue. Thanks!


refactor: build docker images without local dev environment

[ ] Update README before merging

With this PR, building images works without any local environment (except that we use yarn as a task runner). This is mostly so that the production images don't rely on our local environment (that might be different depending on OS). For development, we still need yarn for most tasks (e.g. running tests) and the workflow part of the docker-compose relies on local node_modules (If really needed/desired, we can install that in the container, too, but I'd rather avoid additional abstractions)


mdpdf console command fails on windows if the markdown file is within a folder that has a pound sign (#)

Command:
mdpdf "D:\Dev\00 Research\C#\C# Cheat Sheet.md" --style C:\bin\github.css
Error:
12-24 03:49:32 C:\Users\username\Desktop> mdpdf "D:\Dev\00 Research\C#\C# Cheat Sheet.md" --style C:\bin\github.css
Error: net::ERR_FILE_NOT_FOUND at file:D:\Dev\00 Research\C#\_temp.html
    at navigate (C:\Users\username\AppData\Roaming\nvm\v20.10.0\node_modules\mdpdf\node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:194:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async FrameManager.navigateFrame (C:\Users\username\AppData\Roaming\nvm\v20.10.0\node_modules\mdpdf\node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:170:21)
    at async Frame.goto (C:\Users\username\AppData\Roaming\nvm\v20.10.0\node_modules\mdpdf\node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:589:16)
    at async Page.goto (C:\Users\username\AppData\Roaming\nvm\v20.10.0\node_modules\mdpdf\node_modules\puppeteer\lib\cjs\puppeteer\common\Page.js:1089:16)
    at async C:\Users\username\AppData\Roaming\nvm\v20.10.0\node_modules\mdpdf\src\index.js:174:7

Despite the error stating ERR_FILE_NOT_FOUND at file:D:\Dev\00 Research\C#\_temp.html, _temp.html IS actually created in the target folder. But node seems unable to find it?
Hopefully this is an easy fix.

Hey, thanks for reporting this. It looks like the error is coming from the Puppeteer call to get chrome to navigate to the intermediary html file. I'm not entirely sure why Chrome would be unhappy with that path. I imagine it's because the result of the resolve call to get the file path isn't quite fit for a URL on windows. Looking at that URL, it looks like it's missing some prefix /'s at least.
Unfortunately I don't have access to a windows machine which I can install nodejs on at the moment as I only use linux and macos these days. If that changes I'll give this a crack but I can't promise anything any time soon.
If you'd like to open a PR, I'd be more than happy to review and merge. I suspect the change will be somewhere around https://github.com/BlueHatbRit/mdpdf/blob/01f2e38e1e85b0839de3c89d0d24c18b20aae5fa/src/index.js#L175 where we get the file path.


Remove userStatus feature flag

Issue Ticket Number:-

#1224

Backend changes

[x] Yes
[ ] No

Frontend Changes

[ ] Yes
[x] No

Database changes

[] Yes
[x] No

Breaking changes (If your feature is breaking/missing something please mention pending tickets)

[ ] Yes
[x] No

Deployment notes
None
Description:
This pull request (PR) aims to removes the userStatus flag, which is currently in use to track user status based on task. The feature is now stable and has been in prod since more than 3 weeks and as confirmed with Ankush we can remove this feature flag.
Testing Stats:
Controllers:

Validator

please add test case stats

Added validator and controller file testing stats. the files which I modified. Thanks.


feat: added header gap function to settings

Hi,
Great repo, just what I was looking for. Is it still maintained?
I was missing a settings function to add gap after headings, so I made this PR.

@karlwir Thank you for your contribution! Yes, the project is maintained, although probably not widely used, and changes are not frequently needed. Probably releasing a stable version 1.0.0 would be appropriate.

@karlwir I have published version 0.2.0 including your change. Feedback is appreciated, but I think I can release 1.0.0 soon.

@fellmann cool. I might come in with another PR later today


omitObjectDecorator option in @@TypeGraphQL.type

I think this is the implementation of #345 that makes the most sense to me! Happy to keep this in a fork if you think it's feature/edge-case creep, but I'd bet allowing support for a very common pattern (pagination/refetching) in one of the most popular gql clients (Relay) makes it worth it.
More than happy to write a quick doc page/tests if you think they're necessary once we're sure this is the correct implementation - thanks for all your hard work on this!

@MichalLytek anything I can do to keep the ball rolling on this? would love to get this merged asap :)

Closing as superseded by 0f3236f2 🔒


🥅 Better handling of required android environment values

Problem
The state of the current Android Chat app's build.gradle file is pretty hostile. It won't build without a file at Android/secure/creds.properties, but even if that file is present and contains the expected property keys, the resulting BuildConfig.java file won't compile because the strings aren't quoted.
/Users/phatblat/dev/ditto/demoapp-chat/Android/app/build/generated/source/buildConfig/debug/live/dittolive/chat/BuildConfig.java:13: error: ';' expected
  public static final String DITTO_APP_ID = 9fd5c173-edd6-40e1-8407-744bd9784a85;
                                              ^

Solution
This PR addresses these issues by fixing the BuildConfig class generation, adding an explicit error with instructions when the properties file is missing and adds a template file that can be copied to configure an app more quickly without guesswork.
Build file '/Users/phatblat/dev/ditto/demoapp-chat/Android/app/build.gradle' line: 27

A problem occurred evaluating project ':app'.
> Missing env.properties file. Please copy the env.properties.example template and fill in with your app details.

I've also moved the required file to Android/env.properties so that a directory doesn't need to be created, removing another required step. This will require someone who has already set up the app properties in Android/secure/creds.properties to move that file to Android/env.properties.

@bplattenburg Readme updated.


Subs.rs example uses .subscribe() which is unlisted in docs as opposed to .confirm()

The subs.rs example here https://github.com/petergmiller/ntex-mqtt/blob/master/examples/subs.rs uses .subscribe to indicate successful subscription, as opposed to using confirm.  While either appear to be acceptable (as subscribe just calls confirm), it seems that confirm would be preferable as subscribe is hidden in docs (https://github.com/ntex-rs/ntex-mqtt/blob/58141768f7532d1193bf7b725d311a2097dfb1b3/src/v5/control.rs#L287).

i dont really remember reason

i will make new release later today


pdm export some packages with wrong platform

Steps to reproduce
The pyproject.toml file content is:
[tool]
[tool.pdm]
name = "test"
version = "0.0.1"
description = ""
author = " <>"
license = "MIT"
homepage = ""
python_requires = ">=3.7"

[tool.pdm.dependencies]
aiofiles = "<1.0.0,>=0.6.0"
certifi = "<2021.0.0,>=2020.12.5"
chardet = "<4.0.0,>=3.0.4"
concurrent-log-handler = "<1.0.0,>=0.9.19"
dbutils = "<3.0.0,>=2.0"
future = "<1.0.0,>=0.18.2"
grpcio-tools = "<2.0.0,>=1.34.0"
grpcio = "<2.0.0,>=1.34.0"
h11 = "<1.0.0,>=0.9.0"
httpcore = "<1.0.0,>=0.11.1"
httptools = "<1.0.0,>=0.1.1"
httpx = "<1.0.0,>=0.15.4"
idna = "<3.0.0,>=2.10"
joblib = "<1.0.0,>=0.17.0"
loguru = "<1.0.0,>=0.5.3"
portalocker = "<3.0.0,>=2.0.0"
protobuf = "<4.0.0,>=3.14.0"
pyhive = "<1.0.0,>=0.6.3"
pymysql = "<1.0.0,>=0.10.1"
python-dateutil = "<3.0.0,>=2.8.1"
redis = "<4.0.0,>=3.5.3"
requests = "<3.0.0,>=2.25.0"
sanic = "<21.0.0,>=20.9.1"
sasl = "<1.0.0,>=0.2.1"
scikit-learn = "<1.0.0,>=0.23.2"
scipy = "<2.0.0,>=1.5.4"
six = "<2.0.0,>=1.15.0"
sniffio = "<2.0.0,>=1.2.0"
threadpoolctl = "<3.0.0,>=2.1.0"
thrift = "<1.0.0,>=0.13.0"
thrift-sasl = "<1.0.0,>=0.4.2"
ujson = "<5.0.0,>=4.0.1"
urllib3 = "<2.0.0,>=1.26.2"
uvloop = "<1.0.0,>=0.14.0"
numpy = "==1.19.1"
elasticsearch = "==7.9.1"

[tool.pdm.dev-dependencies]

[build-system]
requires = ["pdm-pep517"]
build-backend = "pdm.pep517.api"

then export requirements on CentOS 7.
pdm export --without-hashes -v

Actual behavior
aiofiles==0.6.0
certifi==2020.12.5
chardet==3.0.4
colorama==0.4.4; sys_platform == "win32"
concurrent-log-handler==0.9.19
dbutils==2.0
elasticsearch==7.9.1
future==0.18.2
grpcio==1.34.0
grpcio-tools==1.34.0
h11==0.9.0
httpcore==0.11.1
httptools==0.1.1
httpx==0.15.4
idna==2.10
joblib==0.17.0
loguru==0.5.3
multidict==5.0.0
numpy==1.19.1
portalocker==2.0.0
protobuf==3.14.0
pyhive==0.6.3
pymysql==0.10.1
python-dateutil==2.8.1
pywin32==300; platform_system == "Windows"
redis==3.5.3
requests==2.25.0
rfc3986==1.4.0
rfc3986[idna2008]==1.4.0
sanic==20.9.1
sasl==0.2.1
scikit-learn==0.23.2
scipy==1.5.4
setuptools==51.0.0
six==1.15.0
sniffio==1.2.0
threadpoolctl==2.1.0
thrift==0.13.0
thrift-sasl==0.4.2
ujson==4.0.1
urllib3==1.26.2
uvloop==0.14.0
websockets==8.1
win32-setctime==1.0.3; sys_platform == "win32"

Expected behavior
why it exports package like pywin32 and packages which platform is win32?
Environment Information
# Paste the output of `pdm info && pdm info --env` below:
PDM version:        0.12.0
Python Interpreter: /usr/local/bin/python3.7 (3.7.3)
Project Root:       /root/output
{
  "implementation_name": "cpython",
  "implementation_version": "3.7.3",
  "os_name": "posix",
  "platform_machine": "x86_64",
  "platform_release": "3.10.0-957.el7.x86_64",
  "platform_system": "Linux",
  "platform_version": "#1 SMP Thu Nov 8 23:39:32 UTC 2018",
  "python_full_version": "3.7.3",
  "platform_python_implementaiton": "CPython",
  "python_version": "3.7",
  "sys_platform": "linux"
}

@rihkddd It is not an issue, you may notice all requirements are pinned with ==X.Y versions. They come from pdm.lock, which is the only supported source. We may provide an option to export from pyproject.toml.

@rihkddd It is not an issue, you may notice all requirements are pinned with ==X.Y versions. They come from pdm.lock, which is the only supported source. We may provide an option to export from pyproject.toml.

@frostming yes, I checked the pdm.lock file, it has the same info with exported file requirements. But I still don't understand why lock  window platform only packages on linux, that's the point of this issue. In product environment, I prefer to use pip install -r requirements.txt(the simplest and solid way, easy to troubleshoot). So, it strongly depends on the correctness of exported requirements.txt file.

@rihkddd The lock file is generated in that way to try the best to make the lock file eligible on multiple platforms. The platform-specific packages have environment markers so they won't be installed on platforms that don't match. No worry about it.

@rihkddd The lock file is generated in that way to try the best to make the lock file eligible on multiple platforms. The platform-specific packages have environment markers so they won't be installed on platforms that don't match. No worry about it.

@frostming Many thanks, I try to install requirements export by pdm, it works like you said. So I can use it as our new python package management tool instead of Pipenv. But I still think export result should filter other platform packages causes may not all python developer are familiar with this.

I would keep this behavior so that you can copy this requirements.txt to the Windows platform, and things will work there. After all, I  am glad to see that my project is adopted, we are still in the alpha stage so more features and changes are expected.

It seem that I have some misunderstanding on environment markers, I will learn more about it later.
I would like pdm have huge success in the future, the standard way for python project dependency management. - from a user suffer from Pipenv and other tools.


Mechanism to bump the defaults stemcell version in kubecf

The default values for the stemcell os and version are currently defined here:
https://github.com/SUSE/kubecf/blob/0f374044d1a86f27d1f9c0b3ba88137e785ad413/deploy/helm/kubecf/values.yaml#L20-L26
Since kubecf pipelines must use the images built with the latest available stemcell version so there needs to be a separate pipeline in order to bump the stemcell version in kubecf repo as soon as there is a new release. The pipeline can make use of the following config:
https://github.com/SUSE/cf-ci/blob/75aea2a2e55d865a38556a861584b71a682f6474/kubecf-build-pipelines/release-images-cf-deployment/config.yml#L13-L16
Also, the buildpacks` ops file should be modified to use the following structure in order to make the stemcell version consistent across all releases:
- type: replace
  path: /releases/-
  value:
    name: suse-binary-buildpack
    url: registry.suse.com/cap-staging
    version: "<IP_ADDRESS>"
    stemcell:
      os: {{ default (index .Values.releases "suse-binary-buildpack").stemcell.os .Values.releases.defaults.stemcell.os | quote }}
      version: ...

Note: These changes have to be co-ordinated between upstream and suse pipelines.

Covers https://github.com/SUSE/kubecf/issues/28.

Blocked by https://github.com/SUSE/kubecf/issues/171.

Unblocked by https://github.com/SUSE/cf-ci/pull/343.
This task would need grooming due to https://github.com/SUSE/kubecf/issues/220.

Here is the summary of discussion with @mudler regarding implementation details:

There must be new pipeline which will first check if the images exists for the latest stemcell version.
If all the cf-deployment and external-releases images are available then it will go ahead and create PR for bumping the default stemcell version.
For now now all releases with custom stemcell settings will be left untouched.
The PR will be merged if the CI passes as usual.

Note: We were unable to reach to a conclusion regarding trigger point for this pipeline. Ideally this pipeline should be triggered once you have all the images built but due to this process being spread-ed across different pipelines we will for now keep the trigger manual.

After discussing with @f0rmiga we decided that its not necessary to check whether an image exists in the pipeline as it will automatically be discovered in the bump PR.
There were also discussions on using a sentinel file as triggers for this pipeline.

You mean that the PR will be tested in the CI and the deployment of a cluster will fail because of missing images? Since we don't have infinite resources in the CI, it would be a lot cheaper to check if images are there before trying to deploy. Unless, the images appear after a couple or minutes or so after starting the CI job and the job continues. What would be the case?

The CI will just wait for the deployment to finish, which means it will wait for the ig job to complete.
That won't give much clues on the reason of the failure, and it will occupy the CI job for the whole timeout span which could be used instead by other jobs.
Then someone have to deploy locally to debug... as the failure is just indicating a timeout waiting for the ig job to complete, and that sounds a bit of a waste. The automation should do the right thing, or we will just be tricked by it :smiley_cat:

You mean that the PR will be tested in the CI and the deployment of a cluster will fail because of missing images? Since we don't have infinite resources in the CI, it would be a lot cheaper to check if images are there before trying to deploy. Unless, the images appear after a couple or minutes or so after starting the CI job and the job continues. What would be the case?

yes I meant the build will fail/pass depending the image availability.
I initially thought it would be better to perform the checks in this pipeline, however another problem is that currently we don't have any synchronization mechanism between the image building pipeline and this pipeline. So basically we don't know what images to check for.
I think this problem will automatically be addressed by the follow up task - to figure out a trigger for this pipeline which will automatically ensure the images are available before triggering this pipeline.
And for now the triggering mechanism for this pipeline is manual so that shouldn't be a problem.
@mudler regarding your comment regarding errors, I think the CI clearly shows if its a Image Pull Error: https://concourse.suse.dev/teams/main/pipelines/kubecf/jobs/deploy-diego/builds/254#L5e67ec21:478
Although it won't be clear what image is missing unless you dive deeper.


Missing details of specific event logged via diagnostic logs

The AWS equivalent of this Databricks audit log page actually lists the specific event types logged under each category as well as the related input parameters. For example for under the "account" category we have the following events:

https://docs.databricks.com/administration-guide/account-settings/audit-logs.html#workspace-level-audit-log-events.
Is there equivalent documentation for the Azure Databricks offering documented somewhere? Alternatively does the detailed workspace audit log event list on the AWS Databricks documentation page apply for Azure Databricks diagnostic logs too?

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

ID: aa60fa41-f753-9c55-c799-a870bdb219a4
Version Independent ID: 786b27ec-7f4d-ad35-e26d-5832c072536e
Content: Diagnostic logging in Azure Databricks - Azure Databricks - Workspace
Content Source: databricks/administration-guide/account-settings/azure-diagnostic-logs.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@pnarsi  Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and the content has been updated. We are closing the issue.
#please-close

#please-close


Not compatible with the new version of rust nightly

Description
In the "2022-08-06' version of rust nightly. Seaorm cannot compile
Steps to Reproduce

Upgrade to latest rust nightly which release in 2022-08-07
Run the program.

Expected Behavior
successfully compiled
Actual Behavior
Compilation failed
Reproduces How Often
Everytime
Versions

rustc 1.65.0-nightly (2befdefdd 2022-08-06)
cargo 1.65.0-nightly (4fd148c47 2022-08-03)
sea-orm v0.9.1
mysql 8.0.29
Try in mac, windows10 and linux.

Additional Information

This is an issue with the toolchain itself, see rust-lang/rust#100215 for more info.

This is an issue with the toolchain itself, see rust-lang/rust#100215 for more info.

Ok, Thank you very much!

Thanks! @HigherOrderLogic

I'll keep this issue open and wait for reply from the Rust team :)

I'll keep this issue open and wait for reply from the Rust team :) Thanks! @phidiaLam

I think versions after rustc 1.65.0-nightly (75b7e52e9 2022-08-13) are no longer a problem.
Or maybe Maybe after version 2022-08-10.
You can close this issue.
Thank you very much!!!

Thanks for the ping! @phidiaLam


Allow multiple triggers on same event

Currently if multiple triggers are defined on :insert, for example, the second trigger overwrites the first one as the trigger naming in the auto-generated migration is based only on model and event.  Adding an auto-incrementing integer at the end of the trigger name would allow for multiple triggers.
An example use case here is needing multiple pg_advisory_xact_locks on another table based on different fields in the triggering record.  For example, a Message sent from from_user_id to to_user_id would need two separate locks on User to handle messages_received_count and messages_sent_count respectively.  If there is another way to handle this or if multiple triggers on :insert is a bad idea, please comment.

Update: Using pg_advisory_unlock_all() and related functions (depending on your database) within a given set of SQL in a single trigger seems to work fine.  This overcomes the need for multiple triggers for me but interested in others' opinions.

I was just caught by this in migrating to using hair_trigger with my Postgres database. Multiple triggers per-event would be amazing.


Update useApproximateDelegationRewards.ts

Formula gives daily, no need to get seconds

PR breaks the calculation even more, resulting in a couple hundred thousand percent APR's.

PR breaks the APR calculation even more, resulting in a couple hundred thousand percent APR's.

PR breaks the APR calculation even more, resulting in a couple hundred thousand percent APR's.

Wait until you see my next pr 💀