Propagate non-managed labels and annotations from SubnamespaceAnchor to Namespace

We have a use case where we would like to add labels and annotations to namespaces  but do not want them propagated down the tree. This is useful for Namespace overrides for specific values that are used by our policy engine.
We configure --managed-namespace-annotation=tenant.config/.* and want all of these to be propagated but we also have namespace.config/* annotations that we would like to be able to set on each Namespace. Ideally something like the following.
apiVersion: hnc.x-k8s.io/v1alpha2
kind: SubnamespaceAnchor
metadata:
  namespace: parent-namespace
  name: child-namespace
spec:
  annotations:
  # This will be propagated
  - key: tenant.config/env
    value: prd
  # This will be applied to the Namespace but not propagated down the tree
  - key: namespace.config/default-instance-size
    value: large

Currently if I try to do this I get the following error
The SubnamespaceAnchor "child-namespace" is invalid: spec.annotations: Invalid value: "namespace.config/default-instance-size": not a managed annotation and cannot be configured
I think that this could potentially be implemented with a flag to allow non-managed annotations and or labels in the annotation validation function  and the label validation function. I am happy to implement this if it is approved.

Hi, sorry for the delay in getting back to you.
The way we currently limit propagation from parents to children is Exceptions. Currently, these only apply to objects, but there's a proposal to add the same feature to HRQs. I believe we should use the same mechanism to limit the propagation of labels and annotations.
As a technical note, "non-managed" labels and annotations are exactly that - they are not managed or enforced by HNC, so asking HNC to manage them wouldn't really make sense. But adding a propagate field to the managed labels/annotations would be relatively straightforward:
apiVersion: hnc.x-k8s.io/v1alpha2
kind: SubnamespaceAnchor
metadata:
  namespace: parent-namespace
  name: child-namespace
spec:
  annotations:
  # This will be propagated
  - key: tenant.config/env
    value: prd
  # This will apply to the subnamespace but no others:
  - key: namespace.config/default-instance-size
    value: large
    propagate: none # like propagate.hnc.x-k8s.io/none

It's important to make propagate a string field, since we might one day want to allow arbitrary selectors, as we do with objects. But we don't need to do that today, and it's fine to say that the only allowed values for propagate are "none" and "all".
wdty?

@adrianludwin thanks for getting back to me!
That makes sense, I will have a look at adding the propagate field for labels and annotations.


Ollama Run provides numerical choice to run one of models from list

Hi,
I think it would be cool if ollama run without any extra arguments showed the models in ollama list, but with a number next to them.
Ie ollama run ->
TYPE NUMBER OF MODEL TO RUN
[0] gemma2:27b-instruct-q8_0
[1] qwen2:0.5b
[2] mistral:7b-instruct-v0.3-q8_0
[3] gemma:2b-instruct
[4] phi3:3.8b-mini-instruct-4k-fp16
[5] llama3:8b-instruct-fp16
[6] llama3:70b-instruct-q8_0

My workflow is always ollama list -> ollama run model-i-copy-pasted
Apologies if this has already been requested or if it isn't in the vision. Running in the shell is great, this would be a nice touch.

#!/bin/bash

OLLAMA_HOST=${OLLAMA_HOST:-localhost:11434}

list=($(curl -s $OLLAMA_HOST/api/tags | jq -r '.models[].name'))

i=0; for m in ${list[*]} ; do printf "[%2d] $m\n" $[i++] ; done

while
  read -p 'Select model: ' MODEL || { echo ; exit 0 ; }
  ! _=$(expr match "$MODEL" "[0-9][0-9]*$") || [ "$MODEL" -ge ${#list[*]} ]
  do
    :
done

ollama run ${list[$MODEL]}

NIce, thanks

@rick-github cool! Thanks for sharing


Update api-management-subscriptions.md

Added note that open products are not displayed on the "Products" page of developer portal

@dlepow
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Crash with on_the_fly parser if after $ character is not a word character

If register contains a string where after $ character is not a word character, then neovim uses 100% CPU and eventually OOM-killed.

Ouh no :|
I can reproduce, #462 fixes the problem for me, can you confirm?

Yes, it fixes it. Also with the patch we can use empty placeholders without preselected text.

Sorry for the bug @stasjok  I never thought about that use-case if the fix works,  it makes sense to have like this, let it be @L3MON4D3

It's been'd :+1:


OccupancyGridUpdate - Data is not being processed correctly

Using Ubuntu 20.04 with ros2-foxy.
The std::copy is faulty, replacing it by a for loop fixes the incorrect updating of the costmap.
You are currently not able to set each pixels value as the std::copy fills the entire x axis with the first value of itself.
Fixed in: https://github.com/ros2/rviz/pull/895

One can simply reproduce this issue by trying to upload a checker-board pattern. (x % 2 == 0 || y % == 0) and change the color depending on that:
                 if(bbX % 2 == 0 || bbY % 2 == 0)                     theMessage->data[bbX + bbY * bW] = 2;                 else                     theMessage->data[bbX + bbY * bW] = 50;

I will close this because the fix has been merged.


C++ migration: fix some Timestamp tests failing on Linux.

Some Timestamp tests check that constructor fails if given values beyond
the supported (pretty wide) range. In case Timestamp is created from
chrono::time_point, the time_point's underlying duration is
implementation-defined and may overflow when tests try to set it to
a value beyond Timestamp supported range. To work around this, make
these tests not run if time_point cannot represent boundary values on
this platform. For example, on OS X, time_point has microseconds
precision, so the tests may run, but on Linux, time_point has
nanoseconds precision, which would overflow.

@rsgowman, thanks for spotting this and for running tests!


Dot repeat not working

Hi, I have installed both vim-repeat and this plugin through lazy.nvim as follows:
  ...
  'tpope/vim-repeat',
  {
    'ggandor/leap.nvim',
    config = function()
      require('leap').create_default_mappings()
    end,
  },
  ...

However, using . to repeat last search by leap.nvim does not work, it repeats the last other repeatable action.
What could be the problem here?

I don't use lazy, but maybe try specifying the dependency explicitly:
  {
    'ggandor/leap.nvim',
    dependencies = { 'tpope/vim-repeat' },
    ...
  },

Thanks for the quick response, I did actually try that among other things after opening the issue and I did not change anything.
So you can confirm that for you using "." does work with latest master? If so, I will investigate further what's the problem with my specific setup.

So you can confirm that for you using "." does work with latest master?

Yes, I cannot reproduce.

Couldn't figure out what's wrong yet, but since it seems to be an issue with my setup I'll close this issue. Thanks for your help :)

Sanity check: put a print statement below this line in the source, and do an operation with leap:
https://github.com/ggandor/leap.nvim/blob/87d206bf678451301fa2de993db286c136cf383b/lua/leap/main.lua#L37

@jannes I'm having an identical issue -- did you ever find a fix?


Add void return type to Config__WriteInt

This prevents any compiler warnings/errors about implicit-int.

Excellent. More important question is why I forgot to enable /W3 /WX in build... will need to put it there. Thanks.


contrib: suppress noop taint removal

This change suppresses error messages in kind.sh that try to remove node taints.
If it fails, it means that taints were not there anyway, so it's ok to
not have these messages shown to user upon cluster creation

/test


Remove deprecated components

Can you explain why the react implementation is removed while the less is still around? Why not remove both in one breaking change?

This relates to #149 btw


Added Industrial_developed_hangman

Added example of Industrial developed game Hangman

screenshot of programm working?

screenshot of programm working?

Yes, would be better. This is all perfect. Just for those who wanna just scroll through the repo so that they can know better, what is this.

A screenshot would be better if it is embedded in to README.md file.

done

I also have a question about adding github workflow in file. Will it work correctly? I am talking about yml file

@OfficialAhmed Please, check this out.


Fixing an encodeEnum bug

I was trying to call (not send even, just call) spaceCenter.autoPilotSetSasMode(autoPilot, 'StabilityAssist'), but it threw. It seems that the encodeValueBasedOnEnum function will throw if the passed value is the 0th enum value. In this scenario, foundEnumVal === 0, yet that triggers the throw.
An alternate solution would be to set foundEnumVal = null and check for null instead of using Number.isInteger.

Thanks so much for your help, really appreciate it.
I added a unit test to reproduce the above behaviour which was failing, have now merged in your code which has caused the test to pass.
New version has been published to NPM (3.1.2)


Provision deployment alongside deploymentconfig

Part one of migration to Deployment workload.
Ticket: https://issues.redhat.com/browse/APPSRE-5932

In q-s, my worry with this approach is data, especially in prod. DC pods will have a large amount of data (many bundles) whereas D pods will only have the last one. Most likely we will want to scale DC pods to zero right after deploying (or even in the same promotion MR).

oh, forget about my comment. The deployment has different labels :)


Models using IRichTextContent don't resolve inline modular content

I've discovered that if my models use IRichTextContent for the type of a field, the default inline content resolver will not process it.
This appears to be because the CodeFirstModelProvider only adds properties of type string to the list of rich text properties to be processed, but I'm not sure if this is the full reason or not. See:
https://github.com/Kentico/delivery-sdk-net/blob/4d1701d04830f72d5f5571de31d59682a9d4e900/KenticoCloud.Delivery/CodeFirst/CodeFirstModelProvider.cs#L137

Hey @ChristopherJennings , this is intended.
The inline resolver is used only for the string-based resolution: https://github.com/Kentico/delivery-sdk-net/wiki/String-based-rendering-of-modular-content-items-in-Rich-text
The resolution of IRichTextContent and its IRichTextBlocks should happen later. For instance, within Views and Display templates in MVC as described in https://github.com/Kentico/delivery-sdk-net/wiki/Structured-Rich-text-rendering. The SDK just fills the IRichTextContent property with structured data.
If you want to use IRichTextContent outside MVC then you have to resolve the property yourself. The other option is to use just plain string properties in the model (you can instruct the model generator to do so).
Feel free to reopen the issue if you have more questions.


fix off-by-one in doTurbo

cPacket(3) tried to send "01 00 65 00" instead of "01 00 65", which has an invalid size header, which would immediately break the connection (due to the invalid packet size header)
The result was that "exiva turbo" functioned like "exiva close" ...

In Visual Basic 6, when you declare an array using Dim cPacket(3) As Byte, you're creating an array of Byte data type with 4 elements. This is because Visual Basic 6 arrays are zero-based, so the array cPacket(3) has elements indexed from 0 to 3.

in case you're wondering, Im playing on http://tibiafunevo.zapto.org/


Allow for ignoring other important files and save space

Ignore build, MacOSX and Windows files

@ahmedbaracat rather than duplicating OS-specific rules for all projects, these live in https://github.com/github/gitignore/blob/master/Global/OSX.gitignore and https://github.com/github/gitignore/blob/master/Global/Windows.gitignore.
The build-related changes seem relevant here - any supporting docs around what these files represent and why they can be excluded from version control would be greatly appreciated!

@shiftkey Thanks for pointing that out.
The main reason for excluding build-related changes is not to hit the file size limit which, I believe, is 100 MB. Normally, games developed with unity, especially 3D ones, have large build files and you can always build the project when you fork/clone/download it :)
Hope this helps
APK: "the package file format used to distribute and install application software and middleware onto Google's Android operating system" https://en.wikipedia.org/wiki/Android_application_package
Unity package: https://help.market.envato.com/hc/en-us/articles/202500634-Building-a-UnityPackage

@ahmedbaracat those details are good enough for me - and the files are Unity-specific, not OS-specific as I first thought...


fix: Restrict fill_internal_slices pass to acir functions

Description
Problem*
Resolves #3476
Summary*
This PR restricts the fill_internal_slices pass to only ACIR functions. The fill slices pass is made to occur right before ACIR gen and over a single flattened block. If a Brillig function uses slices of slices we have multiple blocks which the pass cannot handle. Additionally, the fill slices pass should not operate over Brillig functions in general as it is not required for dynamic array operations like it is for ACIR where we must know the length of dynamic arrays.
Additional Context
Documentation*
Check one:

[ ] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

This PR pulls out a change made in this PR (https://github.com/noir-lang/noir/pull/3617). However, as that PR is much more complex I think we could get this fix in separately.


typo fix in ScalaDoc

path[Long] -> path[String] for string

Codecov Report

Merging #848 into master will decrease coverage by 0.68%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #848      +/-   ##
==========================================
- Coverage   81.43%   80.74%   -0.69%
==========================================
  Files          50       50
  Lines         727      727
  Branches       33       33
==========================================
- Hits          592      587       -5
- Misses        135      140       +5

Impacted Files
Coverage Δ

core/src/main/scala/io/finch/endpoint/path.scala
82.85% <ø> (ø)
:arrow_up:

core/src/main/scala/io/finch/Input.scala
87.5% <0%> (-12.5%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ff7224...01feb9a. Read the comment docs.

Thanks!


Red line is not alligned centrally

Redline is not centrally aligned when we first open this page

can you assign me this?

Hey @lata-11,
Sure. Go ahead with it 🔥


Interface names do not begin with 'I'

Minor thing, but if it weren't for the fact that some classes inherit multiple, I would have assumed these were classes. I'm happy to do a PR for it if it would be accepted

I don't mind if you do ! If it's a standard / best practice for C# development, go for it ;)

Fixed in PR 9


[FEATURE]500 page on mobile

Describe how this feature will help us improve
Make the 500 error page looks good
Describe the solution you'd considered
Make the 500 error page on mobile as below:

Acceptance criteria

[ ]  the 500 page looks like on the picture above
[ ] after pressing the 'return to home' button the user is redirected to homepage

done

#595


Dependencies, Additional Repositories?

So, I see a definition for "AdditionalDependencies" in the debpackage builder...but having some trouble getting it to work.
Is it possible to provide an example of how to add a list of extra app dependencies?
Also, is there an option to add another repository before trying to install said depndencies?

Here's how you can define additional dependencies for Deb and RPM packages:
  <ItemGroup>
    <DebDependency Include="libgdiplus (>= 5.6)" />
    <RpmDependency Include="libgdiplus0" Version="5.6" />
  </ItemGroup>

That doesn't work.
The project fails to load afterwards.
The attribute "Include" in element  is unrecognized.

@aaronegger Do you have a sample project you can share? What's the exact error message? Are you sure you added the DebDependency/RpmDependency elements inside an ItemGroup element (and not inside a PropertyGroup)?

I tried to delete it before you read it, because i just found out that is indeed because i had it in an property group..

This leads to a question that may similar to this.
I read somewhere that i can supply the installscripts by setting a path.
But this haven't worked for me yet.
Should this also be within a subnode?

Currently i use it like that:

...


Delete link which is not exist.

Delete link which is not exist.

Related PR: https://github.com/Azure/azure-sdk-for-java/pull/18916


math: Fix bug in lagrange polynomial

Highlighted by issue #165, roots with wrong sign (-) were fed to lagrange polynomial co-efficients calculations. Also added a couple of unit-tests to catch the regression.
Signed-off-by: Faheem Sheikh<EMAIL_ADDRESS>

Thanks for this! I might adjust the test a bit, but I'm grateful for you to include it!


Adds a Go file to project root, for "dep" dependency manager

Signed-off-by: Ashish Ranjan<EMAIL_ADDRESS>

/approve

/lgtm


feat: plumb from through UTXOs buildThorTrade

Description
Does what it says on the box - plumbs from through buildThorTrade for UTXOs - Cosmos SDK was already handled, and EVM chains is the only one which will still need to be tackled and require quite a bit more lift.
Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
N/A
Risk

None, multi-hop isolated
Testing

Engineering

Implementation looks sane

Operations

Nothing to see here
Screenshots (if applicable)

Current dependencies on/for this PR:

develop

PR #4826

PR #4827   👈

This comment was auto-generated by Graphite.

Graphite rebased this pull request as part of a merge.

Graphite couldn't merge this PR because it was not satisfying all requirements.


Chrome "--app" windows causing scrobble issues

Hi,
Just to make sure this is known, starting Chrome with argument --app= allows you to start browser windows in "app" mode, which looks like this: https://i.gyazo.com/b19a9617be33144d1b26076fb31bfb13.png (right-click menu to show that extensions are still being loaded).
The issue is that it seems songs aren't being scrobbled when they are opened in this manner.
I've tried testing this with a few videos, both in 'normal' Chrome tabs and like this, and with 'simpler' video titles (ie, "Artist - Track" and "Track - Artist" as well as the more complicated ones with brackets and pipes etc).

I cannot figure out how to use this argument :c

@sphinx9 are you still experiencing this issue? I cannot reproduce it.
I opened Youtube in an 'app' mode and played a random song, that was scrobbled successfully.
I can only guess that you weren't authorized while scrobbling songs in the 'app' mode.
For those who also want to reproduce this issue but don't know how to run Chrome in this mode:
 > chrome --app=https:\\youtube.com\


Mldb 2040 pipeline join refactor

Refactor both the equi and cross join pipeline executor to better handle left, right and full outer joins.
We cannot output a row as an outer row until its been tested against every single other row it could match with.
For left or right cross joins, we choose the proper side to loop on first to be efficient (for example if its a right join, we loop on right first). This way we avoid having to cache all rows. For a full cross join, we dont have a choice but to cache all rows on one side and remember if they've ever been output.
For equi joins, we already had a sliding window row cache for the left side, so we now also keep track of whether each row was ever matched, and selectively output an outer row then it gets removed from the cache. This will also help with memory in many cases, as the cache was not emptied until the end, while not its size will be kept at a minimum.
Finally, we use the left and right pipeline scopes to determine how many empty elements to add when we output outer rows.

You give a good explanation of the optimization with the left or right outer join in the description above, we should also have it in the code.

+1 with very minor comment about alignment and missing comments


How to get --all-features to work again?

Tried the suggestions in #3897 as well but no matter what I try I cannot get rust-analyzer to activate all features.
nvim_lsp.rust_analyzer.setup {
    on_attach = custom_attach,
    root_dir = nvim_lsp.util.root_pattern("Cargo.toml", "rust-project.json"),
    settings = {
      ["rust-analyzer"] = {
          ["cargo"] = {
              ["allFeatures"] = true,
          },
          ["checkOnSave"] = {
              ["allFeatures"] = true,
              ["extraArgs"] = {"--all-features"},
          }
      }
    }
}

Currently at commit aa38fa1

rust-analyzer.cargo.allFeatures would be the correct setting for this. Are you sure this is the right way to set settings in nvim-lsp? You could e.g. try setting rust-analyzer.diagostics.enable to false just to see if it's working; if the settings are sent correctly then that should hide the diagnostics completely.

The syntax looks fine to me, I have:
nvim_lsp.rust_analyzer.setup({
    on_attach=on_attach,
    settings = {
        ["rust-analyzer"] = {
            assist = {
                importMergeBehavior = "last",
                importPrefix = "by_self",
            },
            cargo = {
                loadOutDirsFromCheck = true
            },
            procMacro = {
                enable = true
            },
        }
    }
})

I get the same thing in Code:

Setting rust-analyzer.diagostics.enable to false indeed turns off the diagnostics. The syntax is correct but according to https://github.com/rust-analyzer/rust-analyzer/issues/3897#issuecomment-655317883 :

rust-analyzer.checkOnSave.allFeatures was disabled in #4711 because a lot of people were working on projects with incompatible features (e.g. game engine backends) or that had a nightly feature. See also the discussion in #4704.
rust-analyzer.cargo.allFeatures was disabled in the same PR to keep things consistent, although it's less bad to have it always enabled.

The recommendation seemed to be to use rust-analyzer.checkOnSave.extraArgs but that is not helping either.

No, no, it should work. rust-analyzer.cargo.allFeatures is disabled by default, but you can enable it, and rust-analyzer.checkOnSave.allFeatures is unset and unless you change it, has the same value as rust-analyzer.cargo.allFeatures.
rust-analyzer.cargo.allFeatures controls our analysis of the code (which includes those "inactive due to #[cfg]" diagnostics) and rust-analyzer.checkOnSave.allFeatures is used when we run cargo check during save. You want the first one, but it might have stopped working.

@krkhan can you check whether your with_ctap1 feature is declared in Cargo.toml? I'm only able to reproduce this when it's not.

@lnicola Yes it does seem to be: https://github.com/google/OpenSK/blob/stable/Cargo.toml#L29

This was bugging me as well.
Code behind
#[cfg(...)]
#[test]

wasn't regocnized at all with the default settings.
Finally this worked for me:
nvim_lsp.rust_analyzer.setup({
capabilities=capabilities,
on_attach=on_attach,
settings = {
    ["rust-analyzer"] = {
        cargo = {
            allFeatures = true,
            },
        },
    },
})


configure.sh: Improve CRT header copying on BSDs

The *BSD C runtime header copying code is somewhat fragile and requires
manually keeping track of dependencies of each header that gets copied.
This change uses cc -M to gather a list of dependencies of all the
requested header files, and then cpio to copy the result including
intermediate directories to the target directory.
While I'm at it, remove osreldate.h from SRCS= on FreeBSD, since
as far as I can tell there's nothing that depends on that.
/cc @hannesm @adamsteen

AFAIK mirage-crypto also somehow needs x86intrin.h, clzerointrin.h and cpuid.h. Are you installing these too?

@samoht It's complicated:

On GCC-based systems: Solo5 uses -nostdinc which tells the compiler to not use any standard include paths (intrinsics, system, or anything else). configure.sh copies the compiler headers as a whole from the directory pointed to by cc -print-file-name=include, e.g. on my Debian system this is /usr/lib/gcc/x86_64-linux-gnu/8/include. This then contains std*.h, float.h and a bunch of the compiler intrinsics-specific headers cpuid.h, *intrin.h, etc.

On clang-based systems: Solo5 uses -nostdlibinc which tells the compiler to not use any system include paths, but still use its internal headers for intrinsics. We then copy only the std*.h and float.h from /usr/include, as unlike on GCC-based systems, on the BSDs these headers are not shipped alongside the intrinsics headers.

It was years since I wrote this code, but I believe the underlying reason for not copying the clang intrinsics headers as a whole (like we do for GCC) was that some clang/*BSD combination did not (and possibly still do not) support cc -print-file-name=include, thus we had no straightforward way of figuring out where to copy the headers from.
So, to answer your question, the intrinsics headers are installed only on GCC-based systems, on clang-based systems they are implicitly used by the compiler.

Anyway, I think I'm all done here. Better not fix anything else that's not broken :-) Merging.

Certainly the approach is legitimate to provide the minimal set of headers required for using solo5.h (btw, that could get rid of #include <stdbool.h> as far as I can tell), but from a more pragmatic point of view, the headers copied were "everything needed to compile an OCaml runtime and openlibm" (plus the extra endian for nocrypto - which as I mentioned in #453 was wrong), does this sound appropriate (at least from a historical point of view)?
I have not tested this PR, and neither looked deeper into it, but I recently tried to minimize that set of headers copied around, and stumbled upon osreldate.h being used by the OCaml runtime (this is no longer the case with the current trunk (OCaml release 4.12)), see https://github.com/ocaml/ocaml/pull/9506 for more details if interested. Of course osreldate.h can be patched or provided by ocaml-freestanding.
I'd suggest to define the SRCS="float.h stddef.h stdint.h stdbool.h stdarg.h" only once in configure.sh (to reuse for all clang platforms), and am still struggling with the GCC way of doing things (but maybe this is how to do it with gcc) - it would IMHO be cleaner to use the same approach for both compilers.

NB: I checked, and this PR works as advertised on FreeBSD :D

Of course osreldate.h can be patched or provided by ocaml-freestanding.

Ugh, so that (ocaml/ocaml#9506) is why it's in there. I'll re-instate it, since w/o it ocaml-freestanding will not build on FreeBSD.
We could clean it up, but right now I don't feel like spending effort on a boring API-breaking-upper-bounds-dance between solo5 and ocaml-freestanding for the sake of what is a very minor issue. I will, however, add an issue so that we don't forget about it, and if noting else, can remove it some years down the line once everyone is using OCaml >= 4.12.

I'd suggest to define the SRCS="float.h stddef.h stdint.h stdbool.h stdarg.h" only once

Doesn't make sense now due to the osreldate.h thing. Also, there may be more subtle variations between the *BSDs in future, so we'd just be back to defining multiple versions.

there does not seem to be a unified approach between compilers, so let's just keep it as is

Indeed. I'd also like a unified approach, but with the current state of compiler toolchains that's not possible, or at least not worth the effort.


[Feature] Improve the team related front-end part2 #1807

What changes were proposed in this pull request
Issue Number: close #1807
Most of the issue are solved in https://github.com/apache/incubator-streampark/issues/1753 . Two issue about the front-end have not been solved:

the same browser, while opening multiple pages, switch team, will affect all other pages, the correct should be isolated from each other, do not affect each other
team select box should show the name, not id

Brief change log

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (yes / no)

/cc @1996fanrui  PTAL.


We need discussion about SmartInventory#close(Player) method

Currently, the method manually fires InventoryCloseEvent, yet this can posses a problem.
Why this is a problem? I'm trying to create a trade plugin, so I pair two SmartInventory instances like gui1.other has gui2 and gui2.other has gui1.
So both instances are now depending on each other.
Now the problem happens when I want to close the GUI1 and GUI2 together. I'm trying to register listener to capture the InventoryCloseEvent, and what happens is that when GUI1 is closed by user, it will close the GUI2 using the close() method, and close() method will fire InventoryCloseEvent which will again invoke close() method of GUI1, and so on and so on.
In my opinion, just like the Bukkit API's Player#closeInventory() doesn't fire InventoryCloseEvent, the close() method shouldn't fire the InventoryCloseEvent as well.
What do you think? I have a commit ready for pull request if you agree on it. Or if you think this change will cause another problem instead.

I agree, but maybe we should replace it by a new event, like "SmartInventoryCloseEvent" so we're still able to know when SmartInventory#close(Player) is called.
If you do a PR for this, please use "master" as the target branch, I'm planning to do some branches/versioning rework.

Well, the commit was branched from 1.3.0 branch already, so it would be rather difficult to merge it on the master branch than fix it directly.

I will leave a link instead of PR for the future reference: https://github.com/wysohn/SmartInvs/commit/86af09db8421dae4299bcff9465c85b113babf2b
Or as you suggested, we can use SmartInventoryCloseEvent instead.


Resolved issues from build warnings

Docs Build status updates of commit 07c324c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

azps-6.6.0/toc.yml
:warning:Warning
View (azps-6.6.0)
Details

azps-6.6.0/Az.RedisCache/New-AzRedisCache.md
:white_check_mark:Succeeded
View (azps-6.6.0)

azps-7.0.0/Az.RedisCache/New-AzRedisCache.md
:white_check_mark:Succeeded
View (azps-7.0.0)

azps-7.1.0/Az.RedisCache/New-AzRedisCache.md
:white_check_mark:Succeeded
View (azps-7.1.0)

docs-conceptual/azps-0.10.0/release-notes-azureps.md
:white_check_mark:Succeeded
View (azps-0.10.0)

docs-conceptual/azps-7.0.0/release-notes-azureps.md
:white_check_mark:Succeeded
View (azps-7.0.0)

azps-6.6.0/toc.yml

Line 5, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#accounts' in 'azps-6.6.0/Az.Accounts/index.yml'.
Line 74, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#active-directory' in 'azps-6.6.0/Az.Resources/index.yml'.
Line 125, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#active-directory-domain-service' in 'azps-6.6.0/Az.ADDomainServices/index.yml'.
Line 140, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#advisor' in 'azps-6.6.0/Az.Advisor/index.yml'.
Line 153, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#alerts-management' in 'azps-6.6.0/Az.AlertsManagement/index.yml'.
Line 178, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#analysis-services' in 'azps-6.6.0/Az.AnalysisServices/index.yml'.
Line 207, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#api-management' in 'azps-6.6.0/Az.ApiManagement/index.yml'.
Line 486, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#app-configuration' in 'azps-6.6.0/Az.AppConfiguration/index.yml'.
Line 503, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#app-service' in 'azps-6.6.0/Az.Websites/index.yml'.
Line 692, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application-gateway' in 'azps-6.6.0/Az.Network/index.yml'.
Line 1009, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#application-insights' in 'azps-6.6.0/Az.ApplicationInsights/index.yml'.
Line 1046, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#attestation' in 'azps-6.6.0/Az.Attestation/index.yml'.
Line 1067, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#automation' in 'azps-6.6.0/Az.Automation/index.yml'.
Line 1246, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#az.rediscache' in 'azps-6.6.0/Az.RedisCache/index.yml'.
Line 1251, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#batch' in 'azps-6.6.0/Az.Batch/index.yml'.
Line 1396, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#billing' in 'azps-6.6.0/Az.Billing/index.yml'.
Line 1431, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#blockchain-service' in 'azps-6.6.0/Az.Blockchain/index.yml'.
Line 1466, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#blueprint' in 'azps-6.6.0/Az.Blueprint/index.yml'.
Line 1495, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#bot-services' in 'azps-6.6.0/Az.BotService/index.yml'.
Line 1512, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#cdn' in 'azps-6.6.0/Az.Cdn/index.yml'.
Line 1675, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#changeanalysis' in 'azps-6.6.0/Az.ChangeAnalysis/index.yml'.
Line 1680, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#cloud-services' in 'azps-6.6.0/Az.CloudService/index.yml'.
Line 1743, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#cognitive-services' in 'azps-6.6.0/Az.CognitiveServices/index.yml'.
Line 1776, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#communication-services' in 'azps-6.6.0/Az.Communication/index.yml'.
Line 1793, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#confluent' in 'azps-6.6.0/Az.Confluent/index.yml'.
Line 1806, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#connected-kubernetes' in 'azps-6.6.0/Az.ConnectedKubernetes/index.yml'.
Line 1817, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#connected-machine' in 'azps-6.6.0/Az.ConnectedMachine/index.yml'.
Line 1836, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#container-instances' in 'azps-6.6.0/Az.ContainerInstance/index.yml'.
Line 1879, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#container-registry' in 'azps-6.6.0/Az.ContainerRegistry/index.yml'.
Line 1942, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#cosmos-db' in 'azps-6.6.0/Az.CosmosDB/index.yml'.
Line 2197, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#cost-management' in 'azps-6.6.0/Az.CostManagement/index.yml'.
Line 2218, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#custom-resource-providers' in 'azps-6.6.0/Az.CustomProviders/index.yml'.
Line 2235, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#customlocation' in 'azps-6.6.0/Az.CustomLocation/index.yml'.
Line 2248, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-box-edge' in 'azps-6.6.0/Az.DataBoxEdge/index.yml'.
Line 2329, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-factories' in 'azps-6.6.0/Az.DataFactory/index.yml'.
Line 2496, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-lake-analytics' in 'azps-6.6.0/Az.DataLakeAnalytics/index.yml'.
Line 2561, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-lake-store' in 'azps-6.6.0/Az.DataLakeStore/index.yml'.
Line 2650, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-migration' in 'azps-6.6.0/Az.DataMigration/index.yml'.
Line 2695, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-protection' in 'azps-6.6.0/Az.DataProtection/index.yml'.
Line 2756, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#data-share' in 'azps-6.6.0/Az.DataShare/index.yml'.
Line 2831, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#database-for-mariadb' in 'azps-6.6.0/Az.MariaDb/index.yml'.
Line 2872, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#database-for-mysql' in 'azps-6.6.0/Az.MySql/index.yml'.
Line 2959, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#database-for-postgresql' in 'azps-6.6.0/Az.PostgreSql/index.yml'.
Line 3040, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#databox' in 'azps-6.6.0/Az.DataBox/index.yml'.
Line 3073, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#databricks' in 'azps-6.6.0/Az.Databricks/index.yml'.
Line 3092, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#datadog' in 'azps-6.6.0/Az.Datadog/index.yml'.
Line 3131, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#dedicated-hsm' in 'azps-6.6.0/Az.DedicatedHsm/index.yml'.
Line 3142, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#deployment-manager' in 'azps-6.6.0/Az.DeploymentManager/index.yml'.
Line 3193, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#desktopvirtualization' in 'azps-6.6.0/Az.DesktopVirtualization/index.yml'.
Line 3278, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devspaces' in 'azps-6.6.0/Az.DevSpaces/index.yml'.
Line 3289, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#devtest-labs' in 'azps-6.6.0/Az.DevTestLabs/index.yml'.
Line 3312, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#digital-twins' in 'azps-6.6.0/Az.DigitalTwins/index.yml'.
Line 3335, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#diskpool' in 'azps-6.6.0/Az.DiskPool/index.yml'.
Line 3370, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#dns' in 'azps-6.6.0/Az.Dns/index.yml', did you mean '#options'?
Line 3395, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#dns' in 'azps-6.6.0/Az.Network/index.yml', did you mean '#options'?
Line 3412, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#dps' in 'azps-6.6.0/Az.DeviceProvisioningServices/index.yml', did you mean '#options'?
Line 3469, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#elastic' in 'azps-6.6.0/Az.Elastic/index.yml'.
Line 3496, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#event-grid' in 'azps-6.6.0/Az.EventGrid/index.yml'.
Line 3537, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#event-hub' in 'azps-6.6.0/Az.EventHub/index.yml'.
Line 3614, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#expressroute' in 'azps-6.6.0/Az.Network/index.yml'.
Line 3717, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#front-door' in 'azps-6.6.0/Az.FrontDoor/index.yml'.
Line 3788, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#functions' in 'azps-6.6.0/Az.Functions/index.yml', did you mean '#options'?
Line 3821, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#guest-configuration' in 'azps-6.6.0/Az.GuestConfiguration/index.yml'.
Line 3828, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#hdinsight' in 'azps-6.6.0/Az.HDInsight/index.yml'.
Line 3923, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#health-bot' in 'azps-6.6.0/Az.HealthBot/index.yml'.
Line 3934, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#healthcareapis-service' in 'azps-6.6.0/Az.HealthcareApis/index.yml'.
Line 3945, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#hpccache' in 'azps-6.6.0/Az.HPCCache/index.yml'.
Line 3974, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#image-builder' in 'azps-6.6.0/Az.ImageBuilder/index.yml'.
Line 3995, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#import/export' in 'azps-6.6.0/Az.ImportExport/index.yml'.
Line 4012, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#iotcentral' in 'azps-6.6.0/Az.IotCentral/index.yml'.
Line 4023, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#iothub' in 'azps-6.6.0/Az.IotHub/index.yml'.
Line 4174, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#key-vault' in 'azps-6.6.0/Az.KeyVault/index.yml'.
Line 4325, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#kubernetes-configuration' in 'azps-6.6.0/Az.KubernetesConfiguration/index.yml'.
Line 4342, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#kubernetes-service' in 'azps-6.6.0/Az.Aks/index.yml'.
Line 4385, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#kusto' in 'azps-6.6.0/Az.Kusto/index.yml'.
Line 4478, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#load-balancer' in 'azps-6.6.0/Az.Network/index.yml'.
Line 4569, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#logic-apps' in 'azps-6.6.0/Az.LogicApp/index.yml'.
Line 4674, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#logz' in 'azps-6.6.0/Az.Logz/index.yml'.
Line 4729, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#machine-learning' in 'azps-6.6.0/Az.MachineLearning/index.yml'.
Line 4762, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#maintenance' in 'azps-6.6.0/Az.Maintenance/index.yml'.
Line 4787, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#managed-service-identity' in 'azps-6.6.0/Az.ManagedServiceIdentity/index.yml'.
Line 4796, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#managed-services' in 'azps-6.6.0/Az.ManagedServices/index.yml'.
Line 4811, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#management-partner' in 'azps-6.6.0/Az.ManagementPartner/index.yml'.
Line 4822, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#maps' in 'azps-6.6.0/Az.Maps/index.yml'.
Line 4847, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#marketplace' in 'azps-6.6.0/Az.Marketplace/index.yml'.
Line 4858, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#marketplace-ordering' in 'azps-6.6.0/Az.MarketplaceOrdering/index.yml'.
Line 4865, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#media-services' in 'azps-6.6.0/Az.Media/index.yml'.
Line 4886, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#migrate' in 'azps-6.6.0/Az.Migrate/index.yml'.
Line 4957, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#mixed-reality' in 'azps-6.6.0/Az.MixedReality/index.yml'.
Line 4980, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#monitor' in 'azps-6.6.0/Az.Monitor/index.yml'.
Line 5125, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#monitoring-solutions' in 'azps-6.6.0/Az.MonitoringSolutions/index.yml'.
Line 5136, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#netapp-files' in 'azps-6.6.0/Az.NetAppFiles/index.yml'.
Line 5231, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#network-watcher' in 'azps-6.6.0/Az.Network/index.yml'.
Line 5312, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#networking' in 'azps-6.6.0/Az.Network/index.yml'.
Line 5671, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#notification-hubs' in 'azps-6.6.0/Az.NotificationHubs/index.yml'.
Line 5716, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#operational-insights' in 'azps-6.6.0/Az.OperationalInsights/index.yml'.
Line 5821, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#peer-asn' in 'azps-6.6.0/Az.Peering/index.yml'.
Line 5834, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#peering' in 'azps-6.6.0/Az.Peering/index.yml'.
Line 5893, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy' in 'azps-6.6.0/Az.Resources/index.yml'.
Line 5930, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#policy-insights' in 'azps-6.6.0/Az.PolicyInsights/index.yml'.
Line 5951, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#portal' in 'azps-6.6.0/Az.Portal/index.yml'.
Line 5964, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#power-bi-embedded-capacity' in 'azps-6.6.0/Az.PowerBIEmbedded/index.yml'.
Line 5981, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#power-bi-workspace-collections' in 'azps-6.6.0/Az.PowerBIEmbedded/index.yml'.
Line 5996, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#private-dns' in 'azps-6.6.0/Az.PrivateDns/index.yml'.
Line 6029, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#providerhub' in 'azps-6.6.0/Az.ProviderHub/index.yml'.
Line 6072, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#purview' in 'azps-6.6.0/Az.Purview/index.yml'.
Line 6095, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#recovery-services' in 'azps-6.6.0/Az.RecoveryServices/index.yml'.
Line 6332, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#redis-cache' in 'azps-6.6.0/Az.RedisCache/index.yml'.
Line 6375, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#redis-enterprise' in 'azps-6.6.0/Az.RedisEnterpriseCache/index.yml'.
Line 6404, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#relay' in 'azps-6.6.0/Az.Relay/index.yml'.
Line 6447, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#reservations' in 'azps-6.6.0/Az.Reservations/index.yml'.
Line 6470, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#resource-mover' in 'azps-6.6.0/Az.ResourceMover/index.yml'.
Line 6501, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#resourcegraph' in 'azps-6.6.0/Az.ResourceGraph/index.yml'.
Line 6514, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#resources' in 'azps-6.6.0/Az.Resources/index.yml'.
Line 6699, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#route' in 'azps-6.6.0/Az.Network/index.yml'.
Line 6806, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#sap-hana-on-azure' in 'azps-6.6.0/Az.HanaOnAzure/index.yml'.
Line 6823, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#search' in 'azps-6.6.0/Az.Search/index.yml'.
Line 6860, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#security' in 'azps-6.6.0/Az.Security/index.yml'.
Line 7003, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#security-insights' in 'azps-6.6.0/Az.SecurityInsights/index.yml'.
Line 7054, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#service-bus' in 'azps-6.6.0/Az.ServiceBus/index.yml'.
Line 7151, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#service-fabric' in 'azps-6.6.0/Az.ServiceFabric/index.yml'.
Line 7270, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#signalr' in 'azps-6.6.0/Az.SignalR/index.yml'.
Line 7321, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#spring-cloud' in 'azps-6.6.0/Az.SpringCloud/index.yml'.
Line 7356, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#sql' in 'azps-6.6.0/Az.Sql/index.yml'.
Line 7901, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#sql-vm' in 'azps-6.6.0/Az.SqlVirtualMachine/index.yml'.
Line 7932, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#stack-edge' in 'azps-6.6.0/Az.StackEdge/index.yml'.
Line 8013, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#stack-hci' in 'azps-6.6.0/Az.StackHCI/index.yml'.
Line 8022, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#storage' in 'azps-6.6.0/Az.Storage/index.yml'.
Line 8327, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#storagesync' in 'azps-6.6.0/Az.StorageSync/index.yml'.
Line 8370, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#stream-analytics' in 'azps-6.6.0/Az.StreamAnalytics/index.yml'.
Line 8435, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#subscription' in 'azps-6.6.0/Az.Subscription/index.yml'.
Line 8446, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#support' in 'azps-6.6.0/Az.Support/index.yml'.
Line 8465, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#synapse-analytics' in 'azps-6.6.0/Az.Synapse/index.yml'.
Line 8844, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#time-series-insights' in 'azps-6.6.0/Az.TimeSeriesInsights/index.yml'.
Line 8879, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#traffic-manager' in 'azps-6.6.0/Az.TrafficManager/index.yml'.
Line 8926, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#virtual-machines' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9081, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#virtual-network' in 'azps-6.6.0/Az.Network/index.yml'.
Line 9192, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vm-disks' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9261, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vm-extensions' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9324, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vm-images' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9377, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vm-scale-sets' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9482, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vm-snapshots' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9511, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vm-vhds' in 'azps-6.6.0/Az.Compute/index.yml'.
Line 9518, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vmware' in 'azps-6.6.0/Az.VMware/index.yml'.
Line 9581, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#vpn' in 'azps-6.6.0/Az.Network/index.yml', did you mean '#options'?
Line 9698, Column 11: [Warning: bookmark-not-found] Cannot find bookmark '#windowsiotservices' in 'azps-6.6.0/Az.WindowsIotServices/index.yml'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Check if DFA needs to be fixed

Following the discussion in NeuroKit2 (https://github.com/neuropsychology/NeuroKit/issues/206) it seems that there are multiple ways to implement DFA. => Check that we really use the correct implementation according to Peng 1995 and update the reference list accordingly.

Hey @CSchoel I am also working on NeuroKit2 issue #206 and as far as I can judge from your code there shouldn't be any issues. I have compared it to my MFDFA and algorithm-wise, I can't detect any hiccups.
I will use you code and mine to serve as tests for NeuroKit2 fractal_dfa. I hope this also helps you out. I'll report on the tests later.

Hey @CSchoel I am also working on NeuroKit2 issue #206 and as far as I can judge from your code there shouldn't be any issues. I have compared it to my MFDFA and algorithm-wise, I can't detect any hiccups.
I will use you code and mine to serve as tests for NeuroKit2 fractal_dfa. I hope this also helps you out. I'll report on the tests later.

Hey, thank you very much for looking into this! :smile: And also thanks for the hint at Lévy motion in your NeuroKit2 comment. I am always happy to have data sets/processes with prescribed theoretical results against which I can test the algorithms in nolds.

Hey, thank you very much for looking into this! :smile: And also thanks for the hint at Lévy motion in your NeuroKit2 comment. I am always happy to have data sets/processes with prescribed theoretical results against which I can test the algorithms in nolds.

:) Cheers! Happy to help, I'll keep you in the loop with the work with NeuroKit2. I'll add some tests based on your nolds and my MFDFA, to be sure things we have to validating codes for NK2.

:) Cheers! Happy to help, I'll keep you in the loop with the work with NeuroKit2. I'll add some tests based on your nolds and my MFDFA, to be sure things we have to validating codes for NK2.

I finally came back to this: Retracing my steps from https://github.com/neuropsychology/NeuroKit/issues/206, there is indeed a change required:
We need to apply the square root only after we summed all of the individual squared differences and took the mean. This is consistent with the PhysioNet implementation and the (now discontinued) R-package fractal.
This does not change the unit tests for fractal brownian motion, random noise, and random walks. But it does change the output for the Lorenz system quite a bit. This makes me a bit suspicious about the reference paper for that experiment. I'll try to verify this by using the PhysioNet implementation on the Lorenz data to see if the output is closer to 1 (with the fix) or 1.5 (without the fix, prescribed by González-Salas et al. (2016)).

Another TODO: use Lévy motion as another unit test.

I looked for another paper reporting the Hurst parameter obtained by DFA from the Lorenz system and found Wallot et al. (2023). The authors actually report values that are closer to 1 than to 1.5.
I trust them more than González-Salas et al. (2016) because Wallot et al. link to the original paper and describe the algorithm very detailed and with the same square-root-last approach as in the fix I now want to apply to nolds. I think it is quite likely that González-Salas et al. just had the same error in their implementation of DFA that I had in nolds.

I compared the PhysioNet implementation against nolds. Fortunately, the PhysioNet binary outputs all data points on the log-log-plot, which allows a very fine-grained comparison of the two implementations. After correcting for the fact that nolds uses the natural logarithm and PhysioNet uses base 10, the plots are identical:

Looking at the code, I also found this comment:

dfa: Detrended Fluctuation Analysis (translated from C-K Peng's Fortran code)
Copyright (C) 2001-2005 Joe Mietus, C-K Peng, and George B. Moody

I think a 100% agreement with a ported version of C-K Peng's original Fortran implementation is as good as it gets for validating that the implementation in nolds is correct.
I think I want to add this experiment as a regression test.

I added the regression test.
Open TODOs:

[ ] Fix expected DFA value for Lorenz in unit tests and examples and change reference from González-Salas et al. (2016) to Wallot et al. (2023).
[ ] Use Lévy motion as another unit test.
[ ] Adjust explanation in the docstring of DFA to reflect change in formula.

Hey everyone,
I think there might be some material you can reuse for your tests in the documentation of MFDFA. There you can find some simple code to generate a Lévy motion (see here):
# Imports
# from MFDFA import MFDFA   #not needed, just copied from my docs.
from scipy.stats import levy_stable

# Generate 100000 points
alpha = 1.5
X = levy_stable.rvs(alpha=alpha, beta=0, size=10000)

Since these are purely Markovian processes, you should get a Hurst coefficient of H=0.5 in your DFA implementation :).
Hope it helps!

Thanks a lot for the hint. Much appreciated. :heart:

Unfortunately, I noticed that the error I had in my formula was due to the same error existing in Hardstone et al. (2012), which I based my entire explanation of DFA in the docstring on. This means I might have to re-write the whole docstring as the explanation involving standard deviations of individual detrended windows doesn't make any sense anymore. :see_no_evil:
I didn't find any other good explanation, so I might have to resort to explaining the how rather than the why. :slightly_frowning_face:

Another update for myself: After a bit of searching I, found Kantelhardt et al. (2001) which seems to include a decent explanation for at least some parts of the algorithm. It is mostly consistent with the original definition by Peng et al. (1995), so I think I can use that and maybe combine it with the parts of Hardstone et al. (2012) that don't involve the aforementioned error. Let's hope I can get a somewhat understandable introduction to DFA out of this.

I revised the explanation. It needs another proofread, and I still need to find a good motivation why we take the integral / random walk as the first step.

Explanation is finished, and Lévy motion is implemented. We're done here! :tada:


Support followup messages

Is your feature request related to a problem? Please describe.
D++ doesn't support folllowup messages.
Describe the solution you'd like
Add support for them
Describe alternatives you've considered
Constructing webhooks and using that instead webhooks to do it. It does work, but isn't as nice as a dedicated function, as this is part of the official API docs.
Additional context
links:
https://discord.com/developers/docs/interactions/receiving-and-responding#followup-messages
https://discord.com/developers/docs/interactions/receiving-and-responding#create-followup-message

this is now added in dev!


Possible complete rewrite based on Makie's new API

Makie v0.20 introduces a new declarative API - AoG may be rewritten to use this, and it might be good to do that for TidierPlots as well. The API is still experimental at this point: https://docs.makie.org/stable/explanations/specapi/

I think it should be compatible still - there's just an additional "declarative" API that has been added directly to Makie in 0.20 that makes it more feasible to go straight to Makie

Got it, thanks. In that case, we can leave our [compat] entry as-is for now. Will close this issue.


[Bug] text re-rendering on save

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
[x] Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
[x] Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
[x] Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
[x] Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When I hit Cmd + S to save some text i just changed, folded text above the current line is sometimes re-rendered to the right of what is already there.
Steps to Reproduce

Collapse several functions/methods, and then make a change on a line below the collapsed lines.
Hit Cmd + S to save, and see text re-rendered

Expected behavior:
No re-rendering
Actual behavior:
re-rendering
Reproduces how often:
Approximately 75% of the time
Versions
Atom    : 1.21.0
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0

Additional Information

/cc @maxbrunsfeld

Having the same issue in my mostly Python code, but I don't even need to save for it to manifest itself. Sometimes the rendering resets when I scroll the misrendered text off-screen, but it can pop in again at any given time simply by scrolling. Sometimes, the text is repeated more than once.
Can not reproduce it reliably; sometimes adding a space and backspacing it out again is sufficient, other times I need to add new lines, and sometimes the bug doesn't manifest itself at all. Most of the time though, it does.

I also have this issue although I haven't been able to replicate it in safe mode.
Given both screencaps show evidence of using a linter, I think that is the likely cause.
For reference, I am experiencing this issue when working with Typescript and using the following linting packages:

Linter
linter-tslint

It sounds like you might have "fix on save" enabled, in which case the text is likely being replaced.

@Arcanemagus are you able to expand on what you mean by 'replaced'?
For myself, the repeating text disappears when opening the collapsed segment or reopening the file. As far as I can tell, this is a graphical glitch.

Since you said that this only happens sometimes when you save, I'm guessing that what is happening is that your linter provider is running "fix on save" and making changes to the parts of the text that (were) folded.
Just making a guess as to what is triggering this 😉.

You might be onto something...
I get this issue pretty frequently so I'll give disabling "fix on save" a try.

Although this issue was automatically closed. Is there already a solution, because I still have this issue.... 😞

I just found the solution for my version of the problem. I synced my data to a cloud drive.  Now, that I save to local files, everything works as expected....


sample compiles with errors

First of all, thank you for sharing your project!
Your plugin looks promising and comes with very good documentation. But, the sample within your source code doesn't compile without twisting. It would be great if you can review the sample projects and  provide a sample solution which could be compiled and hence tested.
-- paulus
Bug Information
Version Number of Plugin: 1.0.4
Device Tested On:
Simulator Tested On:
Version of VS: 7.0.1 (build 24) on macOS 10.12.6
Version of Xamarin:
Versions of other things you are using:
Steps to reproduce the Behavior

Download the complete project from Github
Open the sample solution, FirebasePushSample, in VS for Mac
Restore Nuget Packages
Clean the FirebasePushSample
Rebuild the FirebasePushSample

Expected Behavior
Actual Behavior
Code snippet
Screenshotst
/Users/paulus/Projects/FirebasePushNotificationPlugin-master/samples/FirebasePushSample/FirebasePushSample/FirebasePushSample.csproj(5,5): Error: This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them.  For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ../../../packages/Xamarin.Forms.<IP_ADDRESS>/build/portable-win+net45+wp80+win81+wpa81+MonoAndroid10+Xamarin.iOS10+xamarinmac20/Xamarin.Forms.targets. (FirebasePushSample)

Seems you need to restore NuGet packages. Did you?

Just found the issue, were some reference that were messed up. Just pushed a fix

Hi, I download the sample within your source code, but this doesn't send the notification. It would be great if you can review the sample projects and provide a sample solution which could be compiled and hence tested.


fix(SearchBar): Clicking 'x' on a blank search now does nothing. #490

:+1:

See additional discussion on #490 before accepting PR.

:+1:


Avoid microfone permissions

Use case
To use this package image_picker the user has to give the microphone's permission
Proposal
Is it possible to use it without asking to use the microphone, and therefore not using this feature?

To use this plugin in the user has to give the microphone's permission

@marcodecarolisidt what plugin?

Sowwy the

To use this plugin in the user has to give the microphone's permission

@marcodecarolisidt what plugin?

Sorry I updated the description


Format data in a way that is useful during finetuning

Example for T2D exists in https://github.com/Aarhus-Psychiatry-Research/psycop-common/blob/main/psycop/common/feature_generation/sequences/cohort_definer_to_prediction_times.py

@KennethEnevoldsen This uses the PredictionTime dataclass. Code for finetuning should probably use that as well :-)


feat: add pbkdf2 algorithm

Fixes #5

@DarthBenro008 Please rebase your branch

I have rebased my branch @anilswm :)

I have made the requested changes @anilswm

Thanks @DarthBenro008


How do you specify in the app.py to not use flash_attn ??

How do you specify in the app.py to not use flash_attn ??
I did not install flash_attn (because it's giving me an error) but it still tries to use it. How do I prevent this?
Error trying to install flash_attn:
(trellis) C:\inetpub\wwwroot\TRELLIS>pip install flash-attn
Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com
Collecting flash-attn
Downloading flash_attn-2.7.0.post2.tar.gz (2.7 MB)
---------------------------------------- 2.7/2.7 MB 8.5 MB/s eta 0:00:00
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [22 lines of output]
fatal: not a git repository (or any of the parent directories): .git
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:\Users\jeffc\AppData\Local\Temp\pip-install-34xtqzwr\flash-attn_72812057375a47f494a81dc7ec330502\setup.py", line 162, in
_, bare_metal_version = get_cuda_bare_metal_version(CUDA_HOME)
File "C:\Users\jeffc\AppData\Local\Temp\pip-install-34xtqzwr\flash-attn_72812057375a47f494a81dc7ec330502\setup.py", line 82, in get_cuda_bare_metal_version
raw_output = subprocess.check_output([cuda_dir + "/bin/nvcc", "-V"], universal_newlines=True)
File "C:\Users\jeffc\anaconda3\envs\trellis\lib\subprocess.py", line 421, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "C:\Users\jeffc\anaconda3\envs\trellis\lib\subprocess.py", line 503, in run
with Popen(*popenargs, **kwargs) as process:
File "C:\Users\jeffc\anaconda3\envs\trellis\lib\subprocess.py", line 971, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Users\jeffc\anaconda3\envs\trellis\lib\subprocess.py", line 1456, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
  torch.__version__  = 2.4.0

  [end of output]

When I add the line os.environ['ATTN_BACKEND'] = 'xformers' to app.py I get the following error... Why does it still try and import flash_attn!!!
(trellis) C:\inetpub\wwwroot\TRELLIS>python app.py
[SPARSE] Backend: spconv, Attention: flash_attn
Warp 1.5.0 initialized:
CUDA Toolkit 12.6, Driver 12.7
Devices:
"cpu"      : "Intel64 Family 6 Model 158 Stepping 9, GenuineIntel"
"cuda:0"   : "NVIDIA GeForce RTX 2070" (8 GiB, sm_75, mempool enabled)
"cuda:1"   : "Tesla P40" (24 GiB, sm_61, mempool not supported)
CUDA peer access:
Not supported
Kernel cache:
C:\Users\jeffc\AppData\Local\NVIDIA\warp\Cache\1.5.0
Warp UserWarning:
Support for CUDA memory pools was not detected on devices ['cuda:1'].
This prevents memory allocations in CUDA graphs and may result in poor performance.
Is the UVM driver enabled?
C:\Users\jeffc\anaconda3\envs\trellis\lib\site-packages\gradio_client\utils.py:1097: UserWarning: file() is deprecated and will be removed in a future version. Use handle_file() instead.
warnings.warn(
[SPARSE][CONV] spconv algo: auto
[ATTENTION] Using backend: xformers
Traceback (most recent call last):
File "C:\inetpub\wwwroot\TRELLIS\app.py", line 247, in
pipeline = TrellisImageTo3DPipeline.from_pretrained("JeffreyXiang/TRELLIS-image-large")
File "C:\inetpub\wwwroot\TRELLIS\trellis\pipelines\trellis_image_to_3d.py", line 55, in from_pretrained
pipeline = super(TrellisImageTo3DPipeline, TrellisImageTo3DPipeline).from_pretrained(path)
File "C:\inetpub\wwwroot\TRELLIS\trellis\pipelines\base.py", line 39, in from_pretrained
models = {
File "C:\inetpub\wwwroot\TRELLIS\trellis\pipelines\base.py", line 40, in
k: models.from_pretrained(f"{path}/{v}")
File "C:\inetpub\wwwroot\TRELLIS\trellis\models_init.py", line 59, in from_pretrained
model = getattr(config['name'])(**config['args'], **kwargs)
File "C:\inetpub\wwwroot\TRELLIS\trellis\models_init_.py", line 22, in getattr
module = importlib.import_module(f".{module_name}", name)
File "C:\Users\jeffc\anaconda3\envs\trellis\lib\importlib_init_.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in find_and_load_unlocked
File "", line 688, in load_unlocked
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\inetpub\wwwroot\TRELLIS\trellis\models\structured_latent_vae_init.py", line 1, in
from .encoder import SLatEncoder
File "C:\inetpub\wwwroot\TRELLIS\trellis\models\structured_latent_vae\encoder.py", line 6, in
from .base import SparseTransformerBase
File "C:\inetpub\wwwroot\TRELLIS\trellis\models\structured_latent_vae\base.py", line 7, in
from ...modules.sparse.transformer import SparseTransformerBlock
File "C:\inetpub\wwwroot\TRELLIS\trellis\modules\sparse\transformer_init.py", line 1, in
from .blocks import *
File "C:\inetpub\wwwroot\TRELLIS\trellis\modules\sparse\transformer\blocks.py", line 7, in
from ..attention import SparseMultiHeadAttention, SerializeMode
File "C:\inetpub\wwwroot\TRELLIS\trellis\modules\sparse\attention_init.py", line 1, in
from .full_attn import *
File "C:\inetpub\wwwroot\TRELLIS\trellis\modules\sparse\attention\full_attn.py", line 9, in
import flash_attn
ModuleNotFoundError: No module named 'flash_attn'
(trellis) C:\inetpub\wwwroot\TRELLIS>

Hi,
Seems that you add os.environ['ATTN_BACKEND'] = 'xformers' after [SPARSE] module is imported, which already setup its backend base on unmodified environ. see
[SPARSE] Backend: spconv, Attention: flash_attn
[ATTENTION] Using backend: xformers

May you try adding this right after you import os, or just specify it the the command line? like ATTN_BACKEND=xformers python app.py.

You can edit the third line of _init_.py to run with xformers by default

You can edit the third line of init.py to run with xformers by default
@jdc4429

yes there is a quadro 6000 user : RTX 6000: Turing (TU102)
it doesnt work
how to make it not use flash attention?

Same problem please helps

Hi,
Seems that you add os.environ['ATTN_BACKEND'] = 'xformers' after [SPARSE] module is imported, which already setup its backend base on unmodified environ. see
[SPARSE] Backend: spconv, Attention: flash_attn
[ATTENTION] Using backend: xformers

May you try adding this right after you import os, or just specify it the the command line? like ATTN_BACKEND=xformers python app.py.

I can confirm that adding os.environ['ATTN_BACKEND'] = 'xformers' right  after os worked.

I think this should be merged into main repo
Check if gpu supports flash attention
If not use xformers

Just need to Write a bat file:
@echo off
call .\venv\Scripts\activate
set ATTN_BACKEND=xformers
python app.py


Hubot ROCKETCHAT_ROOM behaviour changed between RC 0.27 and 0.29

Rocket Chat Version: 0.29.
With RC 0.27, hubot would connect properly, with 0.29 it wouldn't.
The hubot error:
[Wed May 04 2016 15:55:27 GMT+0000 (UTC)] INFO Once connected to rooms I will respond to the name: Servo
[Wed May 04 2016 15:55:27 GMT+0000 (UTC)] INFO Connecting To: nn.nn.nn.nn:3000
[Wed May 04 2016 15:55:27 GMT+0000 (UTC)] INFO Successfully connected!
[Wed May 04 2016 15:55:27 GMT+0000 (UTC)] INFO 'GENERAL'
[Wed May 04 2016 15:55:27 GMT+0000 (UTC)] INFO Logging In
[Wed May 04 2016 15:55:28 GMT+0000 (UTC)] INFO Successfully Logged In
[Wed May 04 2016 15:55:28 GMT+0000 (UTC)] INFO Looking up Room ID for: 'GENERAL'
[Wed May 04 2016 15:55:28 GMT+0000 (UTC)] ERROR Unable to get room id: {"error":500,"reason":"Internal server error","message":"Internal server error [500]","errorType":"Meteor.Error"} Reason: Internal server error
[Wed May 04 2016 15:55:28 GMT+0000 (UTC)] ERROR {"error":500,"reason":"Internal server error","message":"Internal server error [500]","errorType":"Meteor.Error"}
[Wed May 04 2016 15:55:28 GMT+0000 (UTC)] ERROR Unable to complete setup. See https://github.com/RocketChat/hubot-rocketchat for more info.```

The RC error:

```Exception while invoking method 'getRoomIdByNameOrId' TypeError: Cannot read property 'usernames' of undefined
    at [object Object].Meteor.methods.getRoomIdByNameOrId (server/methods/getRoomIdByNameOrId.coffee:6:10)
    at [object Object].methodsMap.(anonymous function) (server/lib/debug.js:23:26)
    at maybeAuditArgumentChecks (livedata_server.js:1698:12)
    at livedata_server.js:708:19
    at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
    at livedata_server.js:706:40
    at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1)
    at livedata_server.js:704:46
    at tryCallTwo (/app/bundle/programs/server/npm/promise/node_modules/meteor-promise/node_modules/promise/lib/core.js:45:5)
    at doResolve (/app/bundle/programs/server/npm/promise/node_modules/meteor-promise/node_modules/promise/lib/core.js:171:13)```

Our configuration hasn't changed in some time. We have RC running with a connect hubot deployed with docker. The environment vars had `- ROCKETCHAT_ROOM='GENERAL'` though our room with the _id of 'GENERAL' is not named 'General'. Commenting out that env var allows hubot to connect again.

```[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Starting Rocketchat adapter...
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Once connected to rooms I will respond to the name: Servo
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] WARNING No services ROCKETCHAT_ROOM provided to Hubot, using GENERAL
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Connecting To: nn.nn.nn.nn:3000
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Successfully connected!
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO GENERAL
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Logging In
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Successfully Logged In
[Wed May 04 2016 19:27:32 GMT+0000 (UTC)] INFO Looking up Room ID for: GENERAL
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO Joining Room: GENERAL
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO rid:  [ 'GENERAL' ]
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO All rooms joined.
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO Successfully joined room: GENERAL
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO Preparing Meteor Subscriptions..
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO Subscribing to Room: GENERAL
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO All subscriptions ready.
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO Successfully subscribed to room: GENERAL
[Wed May 04 2016 19:27:33 GMT+0000 (UTC)] INFO Setting up reactive message list...```

Here is the link for some context: https://demo.rocket.chat/channel/support?msg=JjJAmhRPmqpj8DXoR
Not sure why the usernames property doesn't exist on room.  But this is probably where we need to start to get rid of that error, then see where we stand.

I've updated today and got the same issue. And there's no way to rollback as there's only latest tag on DockerHub. So could you please add a tag for each release version when pushing your images to DockerHub? And also please fix this issue asap, thanks

Simply remove ROCKETCHAT_ROOM env setting in docker-compose make hubot work again

We're now tagging each release of the docker images.  As well as this should be resolved with the newest version of Rocket.Chat 0.37.0 and adapter version v1.0.3


Style guide - best practice for use of use of ontology terms vs plain English in ontology annotations

See decision in #960.

Closing - duplicates #966.


chore(deps): update module github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper to v1.21.5

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.21.4 -> v1.21.5

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.21.5
Compare Source
Bug Fixes

fix script permissions bug (#644) (ec8a424)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 4.11.1 :tada:
The release is available on:

GitHub release
v4.11.1

Your semantic-release bot :package::rocket:


HLC 575 Mode Updating

The additional task for this mode not present in the SPC modes is the addition of a field stop

The previously supported SPC modes don't utilize a field stop mask, so this property must be added in the wfirst.py code. In order to do this appropriately we need to go back to how the CGI instrument is created. Clearly there is no problem with multiple pupil planes (SPC has an apodizer & a lyot stop) so two image planes shouldn't be a huge issue.

We start with a getter/setter for the field stop. The print statement isn't permanent and will just be used for troubleshooting. The path will be added when I figure out where the field stop mask is


polar

Codecov Report

Merging #129 (e12ec92) into master (143249b) will decrease coverage by 42.33%.
The diff coverage is 40.58%.

@@             Coverage Diff             @@
##           master     #129       +/-   ##
===========================================
- Coverage   76.77%   34.43%   -42.34%
===========================================
  Files          32       34        +2
  Lines        2790     2933      +143
  Branches      541      580       +39
===========================================
- Hits         2142     1010     -1132
- Misses        500     1815     +1315
+ Partials      148      108       -40

Impacted Files
Coverage Δ

...noptic/simulate/canonical_computations/__init__.py
100.00% <ø> (ø)

plenoptic/tools/straightness.py
11.11% <11.11%> (ø)

plenoptic/tools/display.py
10.93% <15.78%> (-55.35%)
:arrow_down:

plenoptic/synthesize/geodesic.py
19.20% <16.80%> (+1.01%)
:arrow_up:

plenoptic/tools/signal.py
30.06% <26.92%> (-19.59%)
:arrow_down:

plenoptic/tools/stats.py
47.82% <45.45%> (-12.18%)
:arrow_down:

plenoptic/tools/conv.py
57.81% <47.82%> (-0.53%)
:arrow_down:

plenoptic/tools/data.py
43.33% <47.82%> (-29.75%)
:arrow_down:

plenoptic/metric/perceptual_distance.py
13.55% <50.00%> (-67.80%)
:arrow_down:

plenoptic/synthesize/synthesis.py
21.83% <50.00%> (-53.63%)
:arrow_down:

... and 28 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 143249b...e12ec92. Read the comment docs.

I am closing this PR. The Geodesic object, which this was primarily related to, is deprecated as of #288 , and has been moved to a new repo. The relevant changes from this PR have been included in that new repo.


GDExtension Demo Project no longer works

Godot version
v4.0.alpha.tempp.custom_build [b4dc2e91e]
System information
Debian 11, Vulkan
Issue description
GDExtension Demo project no longer works since b4dc2e91e6143de6722aede77692fdacbfbe840c. (I verified, that it works with the previous commit)
Error message when loading the Demo project is:
SCRIPT ERROR: Parse Error: "Example" was not found in the current scope.
          at: GDScript::reload (res://main.gd:9)
SCRIPT ERROR: Parse Error: Identifier "ExampleRef" not declared in the current scope.
          at: GDScript::reload (res://main.gd:13)
ERROR: Method/function failed. Returning: ERR_PARSE_ERROR
   at: reload (modules/gdscript/gdscript.cpp:874)
ERROR: Condition "p_level <= int32_t(level_initialized)" is true.
   at: initialize_library (core/extension/native_extension.cpp:300)
SCRIPT ERROR: Parse Error: "Example" was not found in the current scope.
          at: GDScript::reload (res://main.gd:9)
SCRIPT ERROR: Parse Error: Identifier "ExampleRef" not declared in the current scope.
          at: GDScript::reload (res://main.gd:13)
ERROR: Method/function failed. Returning: ERR_PARSE_ERROR
   at: reload (modules/gdscript/gdscript.cpp:874)
ERROR: Cannot get class 'Example'.
   at: instantiate (core/object/class_db.cpp:510)
WARNING: Node Example of type Example cannot be created. A placeholder will be created instead.
     at: instantiate (scene/resources/packed_scene.cpp:188)

Steps to reproduce
Compile and run Demo project.
Minimal reproduction project
Demo project of GDExtension

CC @poiati

@poiati yes, that article describes the Demo project. Here is the repository: https://github.com/godotengine/godot-cpp

I see, I can't get it running using our current master as well. The Example node does not match what's expected from the extension definition, it behaves like a plain Node, not like a Control with the extension.

I don't know what I'm missing.

@poiati In some random cases, the project file itself gets unintentionally changed (I could not yet identify, what triggers this exactly). Try to reset the *.gd and *.tscn files its original state from the git repository. This workaround helped me to get around this issue in master.

Thank you @Sauermann! The files were indeed in a weird state.


Format completion in columns.

To resolve #31.
Please review as I am unsure if this is the right way to do it. (It works, but...)

Cool! I'll review it asap and bring it in!

It doesn't change lines for each entry for me.

Hmm. It's working for me:
$ goto foo<tab><tab>
foodata  /u/ddrucker/dmdenv/data/serial/foo/main
foo      /u/ddrucker/dmdenv/private_sand/foo/mp

$```

$ goto <tab><tab>
blog       /home/iridakos/development/projects/html/iridakos.github.io  goto       /home/iridakos/development/projects/bash/goto
duckrails  /home/iridakos/development/projects/ruby/duckrails           root       /

When my shell window is small it does display the entries each on a new line. But when maximized, two entries fit per line and are displayed this way. You can reproduce if your ~/.goto file has short aliased directories.

I can't seem to reproduce that:

Ah, I see the problem. I'll look into it and update.

@rupa Do you have any insight on this? I'm not great at bash arrays.

This Stack Overflow page seems relevant, but I don't understand why the current goto is displaying matches one per line.

@shmup maybe you could help as well?

Inactivity


Api Server use method - callback being called several times

With the changes shown in the meeting in this fork and with the following entry in the server's server.json file:
  "logging": {
    "enabled": true,
  },

Example:
...
  "port": 8080,
  "storage": "../apihub-root",
  "logging": {
    "enabled": true,
  },
  "preventRateLimit": true,
  "enableRequestLogger": true,
...

for a basic request we get the output bellow, where:

x/y means its running the middleware x of y registered middlewares;
Request handled in...  means the callback has been called by the middleware x;
any other output is cause by the acting middlewares (for instance, the logging middleware is the 3rd)

Should the callback be called so many times? I would expect only once, for the matching middleware (in this case it's 49: the '*' URL pattern)
0/52
- Request handled in 0 milliseconds
1/52
2/52
- Request handled in 1 milliseconds
[GET] /assets/images/cube.png
3/52
- Request handled in 3 milliseconds
4/52
5/52
6/52
7/52
8/52
9/52
10/52
11/52
12/52
13/52
14/52
15/52
16/52
17/52
18/52
19/52
20/52
21/52
22/52
23/52
24/52
25/52
26/52
27/52
28/52
29/52
30/52
31/52
32/52
33/52
34/52
35/52
36/52
37/52
38/52
39/52
40/52
41/52
42/52
43/52
44/52
45/52
46/52
47/52
48/52
- Request handled in 49 milliseconds
49/52
- Request handled in 52 milliseconds```

Just to inform duplication of the issue at https://github.com/PharmaLedger-IMI/epi-workspace/issues/61
(@salboaie  requested that the issue was moved to epi-workspace, but we cannot close it here).

Just to inform duplication of the issue at https://github.com/PharmaLedger-IMI/epi-workspace/issues/61
(@salboaie  requested that the issue was moved to epi-workspace, but we cannot close it here).

Hi Tiago,
I would like to propose a different approach in order to implement the middleware capable to measure and log how much time it takes for a request to be resolved.
I propose to create a middleware called "StopWatchLogger" and to write some code like in the followings:
function StopWatchLogger(server) {

    //the purpose of startStopWatch middleware will be to register the starting time
    //and to overwrite the end function of the response object in order to register the end time.
	function startStopWatch(request, response, next) {

        //we save the starting time
        let startTime = new Date().getTime();

        //at this point we save the response.end function reference for later use
        let end = response.end;

        //set response.end function to be ours
		response.end = function (...args) {
            //call the native response.end function with all the args received
			end(...args);
            //we save the ending time
            let endTime = new Date().getTime();
            console.log(`Resolving request ${request.url} took ${endTime-startTime}ms.`);
		}
	}

    //we register a middleware for all the paths/urls
	server.use(`*`, startStopWatch);
}

module.exports = StopWatchLogger;

After the middleware is created we need to ensure that is the first one that will be registered into apihub in order not to lose any requests.
Also the override of the response.end function needs a little bit more elaboration in order to handle the arguments properly if we need to count also the time it take from the call of end function until the response stream is done. As in nodejs http docs end function can receive a callback argument that will be called when the response stream will end.

JS Noob question:
The solution @asaccool gave (although it looks good) appears to fail in the line where we call end(...args):
...
[GET] /fgt-mah-wallet/loader/
Caught event type [uncaughtException]. Shutting down... uncaughtException TypeError: Cannot read property 'finished' of undefined
    at end (_http_outgoing.js:747:12)
    at ServerResponse.res.end (/export/home/jpsl/develop/PharmaLedger/fgt-workspace/privatesky/psknode/bundles/pskWebServer.js:4071:9) <--- this was my own local modification - line where end(...args) is called.
...

I do not really understand why it fails, as it seems a "clean" end() extension. The function end() appears to come from the Stream prototype.

@joaoluis-pdm i didn't run the code that i gave as exemple. At this point is seems there is an issue with the value of "this".
I think that if you change the line where we call the end function
end(...args);

with
end.call(response, ...args);

should work ok.

@asaccool your tip works well.

Just for warming up my JS I have an implementation proposal in
https://github.com/joaoluis-pdm/apihub/commit/2a3dcf10184f4cb6eb3cd0b1c9552ae866d5a787
It is opinionated:

has a timestamp prefix with resolution up to milisecond. (milisecond resolution is not enough in some other projects, where we have to link request/response with  uuid - for example - but if in this case might be enough).
makes no sense to keep both loggers (the original, and this one) turned on.
in no way this answers the problem reported by @TiagoVenceslau in this issue. (Although there seems to be no multiple response.end() calls - I don't really understands who calls the end() method.).

Let me know if you want a pull request.

in no way this answers the problem reported by  @TiagoV-PDMFC in this issue. (Although there seems to be no multiple response.end() calls - I don't really understands who calls the end() method.).

@joaoluis-pdm for my point of view the implementation done by @TiagoVenceslau doesn't show a bug, I can say that there is a misunderstanding of the code.
The server.use function allows us to register functions that will be registered in the middleware array of functions that will be iterated once a new request arrives on the server.
As the code shows
this.use = function use(url, callback) {
...
        if (arguments.length >= 2) {
// here we call the middlware.use to register for a specific url a handler function called cb
            middleware.use(url, cb);
        } else if (arguments.length === 1) {
            callback = url;
//here we call the middleware.use to register a handler function for all of the requests
            middleware.use(cb);
        }
    };

Even next functions are wrappers over middleware.use function and just playing with the args for that function.
this.get = function getReq(reqUrl, reqResolver) {
        middleware.use("GET", reqUrl, reqResolver);
    };

    this.post = function postReq(reqUrl, reqResolver) {
        middleware.use("POST", reqUrl, reqResolver);
    };

    this.put = function putReq(reqUrl, reqResolver) {
        middleware.use("PUT", reqUrl, reqResolver);
    };

    this.delete = function deleteReq(reqUrl, reqResolver) {
        middleware.use("DELETE", reqUrl, reqResolver);
    };

    this.options = function optionsReq(reqUrl, reqResolver) {
        middleware.use("OPTIONS", reqUrl, reqResolver);
    };

Let's consider that we have a server (a small stub for a messaging service) that knows to respond in the next cases:
OPTIONS *
PUT /create-channel/:channelName
POST /send-message/:channelName
GET /read-messages/:channelName

In our server implementation we will register the following handlers:
server.options("*", optionsHandler);
server.put("/create-channel/:channelName", createChannelHandler);
server.post("/send-message/:channelName", sendMessageHandler);
server.get("/read-messages/:channelName", readMessagesHandler);
//we always need a fallback in case there is any handler function capable to resolve the request
server.use("*", NotFoundHandler);

which will translate in a array of middlewares as followes
registeredMiddlewares = [
{url: "*", "method":"OPTIONS", "handler": optionsHandler},
{url: "/create-channel/:channelName", "method":"PUT", "handler": createChannelHandler},
{url: "/send-message/:channelName", "method":"POST", "handler": sendMessageHandler},
{url: "/read-messages/:channelName", "method":"GET", "handler": readMessagesHandler},
{url: "*", "handler": NotFoundHandler}
]

Each handler that is register needs the have the following signature:
function name(request, response, next){
//... business logic implementation for the handler
}

Once our server receives for example a request PUT /create-channel/support a list of middlewares will be "extracted" like [createChannelHandler, NotFoundHandler]. In this case only this two middlewares are selected because of the matching process based on method and url. Then an iteration over this array is started with the calling of createChannelHandler. If in that handler the conditions to execute the request are not satisfied and the next argument of the handler gets called the process will continue with the call the next handler registered and matched, in our case NotFoundHandler.
Now if we look at @TiagoVenceslau 's implementation we can see that the log message " - Request handled in " will be displayed right before each handler function call will be made and not at the end of the request handling process. And thus why I proposed a different approach to resolve the initial problem.


feat: always display next button in login page

To make the login page more intuitive, this PR changes the login page to always display the "next" button. When the data is not filled in, the button remains in a disabled state.
Before:

After:
!isReady

isReady

This is a good alternative, it makes sense to show the next button 👏🏼
Generally, for better UX, it's recommended to keep the button enabled and if clicked with empty fields, an error message is displayed below the fields indicating to the user what needs to be filled in, and the button is disabled.
But your solution can be an intermediate step towards that.

I agree it would be better to keep the button always visible and enabled (but show error if the form isn't filled out). Can we do that in this PR? Thanks.

Thanks @bybruno @gaearon
Done!

LGTM!!!


Files named .project in emacs have treemacs icons that are green and twice as big as others

I confirm that...

[X] I have searched the issue tracker, documentation, FAQ, Discourse, and Google, in case this issue has already been reported/resolved.
[X] I have read "How to Debug Issues", and will use it to provide as much information about this issue as possible.
[X] The issue can be reproduced on the latest available commit of Doom.
[X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. (Doom does not support development builds like 29+ or any version ending in .50 or .9x)

Expected behavior
Files named .project should have the same icons as other generic files.
Current behavior
Files named .project have treemacs icons which are twice as big, and in a different color (green) from the rest of the icons.

Steps to reproduce

Open Emacs
Open a project which contains a .project file
Open treemacs on that project
Notice how the .project file looks weird

System Information
https://gist.github.com/JonathanReeve/c51628e28c769c5351e6487ff95c26e3

It looks like this is related to lsp and to the lsp-treemacs theme. See https://github.com/emacs-lsp/lsp-treemacs/issues/89. I've added instructions for how to reproduce this issue at https://github.com/doomemacs/doomemacs/issues/7519.

Just jumping here before I go deeper.
The funny thing about this is that the icons are not the only inconsistent part, the directories with custom icons don't show the > symbol.
Not sure why, yet.


Add canonical url to the head section

This PR is intended to help with the issue #1964

Hi @gaearon and @sophiebits ! I'm willing to invest time on this wonderful community but I need some help to get involved, so if I got something wrong on this PR please provide me some feedback and I will be more than happy to work on it and learn more from the project.

Can you please:

Rename the property ogUrl to canonicalUrl
Check each page that uses the TitleAndMetaTags component and have it pass in a URL if possible
Change the canonical URL for the homepage from https://reactjs.org/index.html to just https://reactjs.org/

Count on me @sophiebits, thanks for that by the way :)

Done! This issue was perfect for me to get to know better this project.
I really appreciate your help and feedback @sophiebits, thanks for your time :)
Please let me know if there is anything else I can do, can't wait to continue working on this project!

This looks great. Thank you so much!

Hi @gaearon and @sophiebits ! I'm willing to invest time on this wonderful community but I need some help to get involved, so if I got something wrong on this PR please provide me some feedback and I will be more than happy to work on it and learn more from the project.

I wanted too, :)


Using Firebase Auth with custom API - am I doing this right?

Hey, I'm currently planning on using Firebase for everything except for data storing. Therefore I'm writing a custom API as a Cloud Function and am working on implementing Firebase's Auth into my API. From my research, the JWT from Firebase Auth is currently available under session.currentUser.Yd thanks to the Torii adapter.
At the moment this seems to be working as expected since Firebase-Admin is successfully decoding it, but I'd like to double check if I'm wrong somehow. Yd just seems to be an odd name for the JWT token, especially since the refresh token is under refreshToken.
Thanks!

I spent far too long researching, and realized that ember fire uses the 3.9.0 firebase SDK, (inject the firebaseApp service, and check it's SDK_VERSION property).
That means the firebaseApp service only has access to the deprecated getToken() method.
You'll find that session.currentUser.Yd returns the exact same thing as getToken().
Thanks for this, better late than never!


refactor util lib code

Currently it is not easy to share util shared code between libraries. Currently the project has duplicated code across libs.
Possible but not great solutions

symlink a util lib
publish a util lib
combine all libs into a core instead of stand alone packages (last resort, not ideal)

https://github.com/dherges/ng-packagr/issues/358

Hi coryrylan,
Nice plugin, I like this one but I need one help like how we can change the step to 1.5 or .5