seamless image geneartion missing perlin noise filter

after installing was node suite and using the preset from wiki to generate seamless rock texture was met with missing perlin noise filters

The old perlin noise was removed for a faster more optimized node with more functionality

what's the workflow example for how to generate seamless images using the more optimized node?

Look into:
https://github.com/WASasquatch/PowerNoiseSuite
And
https://github.com/WASasquatch/PowerNoiseSuite
They contain new generators, and the nodes can be used in place of the missing one.


Contribution question - publishLocal

Hi,
I am trying to fix one problem, when I do publishLocal and try to use library ( without changes still )  I have then errors like:
error: not found: value guardrailTasks
guardrailTasks in Compile := List(
^
/home/baku/Dev/workspace/job/os/http4s-guardrail-example/build.sbt:37: error: not found: value ScalaServer
 ScalaServer(
 ^
/home/baku/Dev/workspace/job/os/http4s-guardrail-example/build.sbt:38: error: not found: value specPath
   specPath = (Compile / resourceDirectory).value / "api.yaml",
   ^
/home/baku/Dev/workspace/job/os/http4s-guardrail-example/build.sbt:39: error: not found: value pkg
   pkg = "com.example.http4sguardrailexample",
   ^
/home/baku/Dev/workspace/job/os/http4s-guardrail-example/build.sbt:40: error: not found: value framework
   framework = "http4s",
   ^
/home/baku/Dev/workspace/job/os/http4s-guardrail-example/build.sbt:41: error: not found: value tracing
   tracing = false
   ^

any of you occured similar issue ?

Hello @maciejbak85! Due to the fact that the sbt plugin is in a separate project, https://github.com/twilio/sbt-guardrail, you'll likely need to build and publishLocal that project as well if you want the full chain to function as expected.
When developing changes, I typically use cli on the SBT console from inside guardrail to run my configuration,
sbt> ~cli scala --server --specPath ~/example/api.yaml --framework http4s --packageName com.example.http4sguardrailexample --outputPath ~/example/src/main/scala/generated

for example.
This has the benefit of having a quick iteration cycle from both sides, if you make modifications by hand inside ~/example/ you can see the effect immediately, and as you migrate those changes into the guardrail generator you can compare the generated code with what you expect by verifying the git diff as you go.

Closing this out, but feel free to comment if you still feel as though there is an opportunity to improve this workflow.


[stable/falco] Add nestorsalceda as an approver in OWNERS file

Signed-off-by: Néstor Salceda<EMAIL_ADDRESS>
What this PR does / why we need it:
I'm adding myself as an approver in the OWNERS file
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/lgtm
/approve


Bug: MM Spawn Set from Soaring from OOT in non-ER

Just putting this here so it doesn't get forgotten. The MM spawn changes should only apply when OW ER is on.

Fixed

This issue hasn't actually been fixed, reopening so it doesn't get forgotten.

Fixed (for real)


Document the import order of the common msbuild extension points.

It is not clear to users how the import order looks like, considering that there are implicit top and bottom imports for:

directory.build.props and directory.build.targets
nuget package based build logic
msbuild SDK top and bottom imports

Users need to know how to compose all three of these entities to achieve the import ordering that they want.

Current (upto v16) Import Order, with and without the SDK-style
Microsoft.Common.props

Directory.Build.props
<ProjectFileNameWithExt>.<Vendor>.<Tag>.props
MSBuildUserExtensions Wildcard-ImportBefore
MSBuildExtensions Wildcard-ImportBefore
CustomBeforeMicrosoftCommonProps
<CommonProps>
CustomAfterMicrosoftCommonProps
MSBuildUserExtensions Wildcard-ImportAfter
MSBuildExtensions Wildcard-ImportAfter

.NET SDK props

AlternateCommonProps (Added in v3.0) OR Microsoft.Common.props
<SDK props>

Project File

<Project File>

.NET SDK targets

<SDK Before targets>
<LanguageTargets> Microsoft.Common.targets
<SDK After targets>
NuGet.Build.Tasks.Pack.targets

Microsoft.<Lang>.targets

<Lang Before imports>
<Lang Compiler targets>
<Lang DesignTime targets>
Microsoft.Common.targets
<Lang After imports>

Microsoft.Common.targets

Microsoft.Common.props (if not imported before)
<ProjectFileNameWithExt>.user.targets
MSBuildUserExtensions Wildcard-ImportBefore
MSBuildExtensions Wildcard-ImportBefore
CustomBeforeMicrosoftCommonTargets
<CommonTargets>
CustomAfterMicrosoftCommonTargets
MSBuildUserExtensions Wildcard-ImportAfter
MSBuildExtensions Wildcard-ImportAfter (NuGet Restore targets, imported here)
<ProjectFileNameWithExt>.<Vendor>.<Tag>.targets
Directory.Build.targets

Note: The Xaml, CSharp, VisualBasic, FSharp targets wrap around Common targets and have similar extension points. I didn't include the imports of the inbox targets for simplicity. You can use MSBuild Log Viewer to inspect your own projects' imports.

So, How will we put the above monstrosity into docs and make people understand them easily?

Thanks for looking it up. Can you create a PR and add them to https://github.com/microsoft/msbuild/tree/master/documentation?
The binlog viewer should also aid users in understanding the import order.

OK. Will do.


It should be possible to get the bazelisk release number.

It would save debugging time if I could do something like
bazelisk bazeliskversion
to print the version (and build date) of bazelisk I am using. That makes it easy to see if you are behind on features and need to update or not.

bazelisk version already shows the Bazelisk version - does this help?
$ curl -LO https://github.com/bazelbuild/bazelisk/releases/download/v1.11.0/bazelisk-darwin-arm64
$ chmod +x bazelisk-darwin-arm64
$ ./bazelisk-darwin-arm64 version
Bazelisk version: v1.11.0
Build label: 5.1.1
Build target: bazel-out/darwin_arm64-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Fri Apr 8 15:58:49 2022<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>


fix handling of ACK frames serialized after CRYPTO frames

Thanks for the review @mholt! I really hope this is the last critical bug in the v0.37 release line. Turns out that switching out the underlying TLS stack (that's in fact what we did, given that the crypto/tls API is completely different (better!) from what we had in qtls) is a minefield.

Thank you @marten-seemann  -- absolutely understandable and no worries :) We have released Caddy 2.7.3 with the patches.


elixir: 1.11.4 -> 1.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/elixir/versions.
meta.description for elixir is: "A functional, meta-programming aware language built on top of the Erlang VM"
meta.homepage for elixir is: "https://elixir-lang.org/"
meta.changelog for elixir is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/elixir passed the binary check.

/nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/elixirc passed the binary check.

/nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/iex passed the binary check.

Warning: no invocation of /nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/mix had a zero exit code or showed the expected version

/nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/.elixir-wrapped passed the binary check.

/nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/.elixirc-wrapped passed the binary check.

/nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin/.iex-wrapped passed the binary check.

3 of 7 passed binary check by having a zero exit code.

6 of 7 passed binary check by having the new version present in output.

found 1.12.0 with grep in /nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0

found 1.12.0 in filename of file in /nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0

directory tree listing: https://gist.github.com/7e3836598d64191c1059973ba1696064

du listing: https://gist.github.com/959db70bcbd4fc79b5bacc3d42a7f8ae

Rebuild report (if merged into master) (click to expand)

12 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
elixir
elixir_1_11
elixir_ls

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A elixir https://github.com/r-ryantm/nixpkgs/archive/2c40a35a3396b9b96d9e73fc683b90319f5e3d8b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0
ls -la /nix/store/xcsvawy4pfxj0zy2zaad3g516w05p3hp-elixir-1.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

elixir
elixir_ls
mix2nix

Maintainer pings
cc @ankhers @Br1ght0ne @DianaOlympos @gleber @happysalada @yurrriq for testing.

Result of nixpkgs-review pr 123809 at 2c40a35a run on x86_64-linux 1

3 packages built successfully:

elixir (elixir_1_11)
elixir_ls
mix2nix

1 suggestion:

warning: name-and-version
Did you mean to pass pname instead of name to mkDerivation?
Near pkgs/development/interpreters/elixir/generic-builder.nix:19:5:
   |
19 |     name = "${baseName}-${version}";
   |     ^

Near pkgs/development/interpreters/elixir/generic-builder.nix:21:12:
   |
21 |     inherit src version;
   |            ^


Modify so both underscore and lodash users can use

I was attempting to use your project earlier today and was required to ditch it due to its specific use of lodash. My team uses underscore instead which does not provide the same functionality as lodash. Specifically, the use of _.get here is the main issue. If this call were replaced with something less specific to lodash, underscore users could use this package as well. Food for thought.

Happy to incorporate changes if you want to make a pull request


New sliders in 2022.12 are not ommited

This add-on doesn't work over sliders and that's great.

Features:
[...]
Option to ignore swipes over certain elements (e.g. sliders or maps)

(Although I don't know where the option is. It has worked great by default on all my sliders incl. Mushroom.
However, 2022.12 (released today) introduced the new Features for some Tile cards like lights, and swipe navigation acts when sliding them.
https://www.home-assistant.io/blog/2022/12/07/release-202212/#tile-card-gets-features
Hoping an update can easily fix this, or happy to learn if this needs to be configured on my end.
Thank you :)

Yeah, I know, the new slider uses a different element. Update is coming in some minutes (v1.7.0).
By the way, there is no need for extra configuration, the exception list is built-in.

Thanks a lot @zanna-37 for the fast update! It now skips the new Tile slider.
I'm raising a separate issue just to keep things focused 😄


Escape text used for mentions and links

Fixes https://github.com/matrix-org/matrix-rich-text-editor/issues/986

I actually wanted to do this at a more internal level, but at that point the String passed to the RTE is now a Utf16String and html_escape won't work on that.


Performance issue

Issue Type: Performance Issue
Happen: after recent update. Occur: after a little while of usage.
VS Code version: Code 1.27.2 (f46c4c469d6e6d8c46f268d1553c5dc4b475840f, 2018-09-12T16:17:45.060Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Pentium(R) CPU G3240 @ 3.10GHz (2 x 3093)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: disabled_offnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.92GB (3.86GB free)

Process Argv
D:\Programs\Microsoft VS Code\Code.exe

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
    0	    86	  4740	code main
    1	    68	  8828	   window (Issue Reporter)
    1	   132	 11040	   gpu-process
    0	   181	 11456	   window (carousel-home.blade.php - hoangkhangevent - Visual Studio Code)
    0	    36	  3968	     searchService
    0	    12	  4544	     electron-crash-reporter
    0	    13	  8152	     watcherService
    0	     9	  2576	       console-window-host (Windows internal process)
   41	    65	 12324	     extensionHost
    0	    71	  3048	       electron_node htmlServerMain.js
    0	    70	  4588	       "D:\Programs\Microsoft VS Code\Code.exe" "d:\Programs\Microsoft VS Code\resources\app\extensions\html-language-features\server\dist\htmlServerMain" --node-ipc --clientProcessId=12324
    0	    65	 11640	   shared-process

Workspace Info
|  Window (carousel-home.blade.php - hoangkhangevent - Visual Studio Code)
|    Folder (hoangkhangevent): 9393 files
|      File types: php(7020) md(245) phpt(227) js(196) json(187) test(177)
|                  xml(165) txt(114) yml(98) jpg(87)
|      Conf files: makefile(4) package.json(2);

Extensions (12)

Extension
Author (truncated)
Version

path-intellisense
chr
1.4.2

es7-react-js-snippets
dsz
1.8.6

vscode-phpmd
eco
1.1.0

prettier-vscode
esb
1.6.1

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

beautify
Hoo
1.4.3

vscode-phpfmt
kok
1.0.30

php-namespace-resolver
Meh
1.1.0

php-docblocker
nei
1.6.0

laravel-blade
one
1.18.0

colonize
vms
2.2.2

What's the perceived performance issue? Anything that becomes slow?
@aeschli Since its seems to come from htmlServer.

RAM goes high. VS code has taken almost 50% CPU without me doing anything. Code suggestion no longer works

@VNXtreme Can you open the VSCode process explorer (Help > Process Explorer) and see which VSCode process is busy?


Change metadata messages to use Active Messages

Closes https://github.com/NVIDIA/spark-rapids/issues/1588
Closes https://github.com/NVIDIA/spark-rapids/issues/980
Please set whitespace off when reviewing the bulk of this, it makes it easier to understand. Also there are changes here to the flatbuffer java files, and those are generated. I did do some minor withResources cleanup, can split that up into another PR.
This PR changes the metadata/transfer request messaging from UCX tags to UCX Active Messages. The advantage of Active Messages is that error handling in UCX is going this way, and when things go wrong Active Messages will clean up resources that UCX is using (like fragments from their pools for pipelined protocols). The other big one is that it removes the need to worry about the max metadata size. I haven't refactored the metadata pool yet to make it remove this setting alltogether, can do as a follow up.
It was tested with UCX 1.10.x, and 1.11. With UCX 1.10.x the RNDV mode is the only mode supported (Active Messages could also be EAGER, and they have an automatic mode to switch based on size), so I set "rndv" set as default. The config is internal, but I should say also there doesn't seem to be a big need for EAGER mode right now, not from the 3TB tests I've run.
I had to tweak client/server/iterator tests here, and they all pass. I made some changes and need to retest in a cluster setup. There is some bit manipulation I'll write tests for in this PR.

If anyone would like me to walk them throw the code, I am happy to do so.

@jlowe I think I have addressed your comments. Could you take another look?

build


[DOC] update mxnet version in installation doc

Description
The doc is wrong. Updated to 1.6.
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

cc @dmlc/gluon-nlp-team

Job PR-1072/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1072/2/index.html

I think this only applies to the doc for master branch, which is updated automatically.

@szha yes, but it's currently broken even for the master branch. So the command should be fixed once the html page listing mxnet pre-releases for pip is ready.

That's reasonable. i bought up that we should publish the nightly build links to mxnet website on the dev list. But they are not yet available there. Then we can add a link on the gluonnlp master branch to all nightly builds.


SPM: Update min SDK & fix linker misses

This removes errors and warnings when building with Xcode 12.

bump

Thanks!


Uncaught TypeError: Cannot read property 'getSelectedBufferRanges' of null

[Enter steps to reproduce:]

...
...

Atom: 1.39.0 x64
Electron: 3.1.10
OS: Mac OS X 10.14.6
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Cannot read property 'getSelectedBufferRanges' of null
At /Applications/Atom.app/Contents/Resources/app/static/<embedded>:11

TypeError: Cannot read property 'getSelectedBufferRanges' of null
    at BufferSearch.search (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:747766)
    at FindView.liveSearch (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:767805)
    at findEditor.onDidStopChanging (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:763524)
    at Function.simpleDispatch (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1207528)
    at Emitter.emit (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:1208969)
    at TextBuffer.emitDidStopChangingEvent (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:11:504055)
    at later (/Applications/Atom.app/Contents/Resources/app/static/<embedded>:14:103239)

Commands
     -8:32.1.0 core:save (input.hidden-input)
  2x -7:08.7.0 core:close (input.hidden-input)
     -7:06.9.0 project-find:show (input.hidden-input)
     -7:06.5.0 core:paste (input.hidden-input)
     -7:05.6.0 core:confirm (input.hidden-input)
     -1:02.6.0 find-and-replace:show (input.hidden-input)
     -1:02.3.0 editor:consolidate-selections (input.hidden-input)
     -1:02.3.0 core:cancel (input.hidden-input)
  2x -0:48.9.0 core:close (input.hidden-input)
     -0:28.4.0 tree-view:collapse-directory (div.tool-panel.tree-view)
     -0:11.5.0 project-find:show (div.tool-panel.tree-view)
     -0:11.5.0 pane:show-previous-item (input.hidden-input)

Non-Core Packages
atom-beautify 0.33.4
atom-liquid-snippets 0.3.0
language-liquid 0.7.0
sass 0.5.0
shopify-helper 0.6.0

Thanks for contributing!
We noticed that this looks like a duplicate of https://github.com/atom/find-and-replace/issues/998 so you can subscribe there for updates if you'd like.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Is this project still under development?

Hey @marionebl @kotzendekrabbe @Palmaswell
This project will receive any update or it's really dead?
The last commit was in April and there's a few PR's opened...
I'm asking just to know if I can fork to fix some problems that I'm facing or if you'll fix in the next months.

Hi @AdrianoCahete ,
Thanks so much for reaching out.  This project is currently not under development, yet it's not dead :)
Please feel to create a PR out of your fork and assigned the PR to me.
Please let me know if you have any further questions.


Update dependencies to fix vulnerability regarding CVE-2024-23342

python-keycloak replaced python-jose with jwcrypto recently, because it uses ecdsa, which is deemed to be unsafe. As fastapi-keycloak-middleware still catches exceptions from python-jose, I got import errors in one of my company's projects using this package when I tried to update our dependencies to address this issue. Therefore, I decided to fix this problem from my private GitHub account.
I also updated FastAPI to 0.110.0 as well because it fixes the following vulnerabilities:

CVE-2024-24762
CVE-2024-27454

Please release an update for fastapi-keycloak-middleware including this PR as soon as possible. Otherwise we will have to substitute the package in our company's project and I really don't want to deal with all that hustle 😅

Hi @vagas87, thanks for your contribution! I'm happy to change to jwcrypto, however I have a few comments regarding the version constraints. Please check the review and let me know what you think

Thanks again for your contribution. I looked into it a bit more, there's some backwards incompatibilities where I'm not sure how to handle them.
Audience claim
The default behaviour of python-jose was that the aud claim was not required, but would be validated if present. Compare the part in their code base.
jwcrypto doesn't expose that much control anymore, so python-keycloak have made an effort to somehow map the old verify_aud option. This results in a change in default behaviour:
With verify_aud set to True, the authentication now fails if no aud claim is present, which used to work in the old version as require_aud was False. In my case that did break the application, I don't consider this a minor issue
JWT Decode Options
So far we've been exposing the JWT decode options to the user, see also the docs. This wouldn't be possible anymore, as it would not have any effect with the new version of python-keycloak. We'd need to rewrite the doc section and somehow hope no one is making use of these options.
Around the same topic there's still ongoing discussions in the upstream repo around backwards incompatibility. Especially the fact that enabling verify_aud (which is currently the default) prohibits exp and nbf validation does concern me.
To summarize, I do see the need for the change, but I'd rather have the upstream python-keycloak changes settled before releasing a new version.

That's unfortunate, but I understand your concerns. Would it at least be possible to release a patch version that temporarily bounds python-keycloak to below v3.9.1 in the pyproject.toml until these problems are solved?
Right now, everyone is getting import errors when including fastapi-keycloak-middleware and running anything, because of the package incompatibilities that the dependencies don't account for. The vulnerability (if there even is a real threat, I don't know, I'm just hunting down Dependabot warnings right now for an upcoming release in my company 🙈) would be there nonetheless, but at least nobody is scratching heads wondering why their code isn`t running anymore after trying to fix the CVE.

Yes absolutely, I have that planned for later today, once I’m back at home.

On 3. Mar 2024, at 17:57, Marcus Mai @.***> wrote:
That's unfortunate, but I understand your concerns. Would it at least be possible to release a patch version that temporarily bounds python-keycloak to below v3.9.1 in the pyproject.toml until these problems are solved?
Right now, everyone is getting import errors when including fastapi-keycloak-middleware and running anything, because of the package incompatibilities that the dependencies don't account for. The vulnerability (if there even is a real threat, I don't know, I'm just hunting down Dependabot warnings right now for an upcoming release in my company 🙈) would be there nonetheless, but at least nobody is scratching heads wondering why their code isn`t running anymore after trying to fix the CVE.
—
Reply to this email directly, view it on GitHub https://github.com/waza-ari/fastapi-keycloak-middleware/pull/29#issuecomment-1975229513, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABCM2MCA5DOCAAAGT2KFZRLYWNI7LAVCNFSM6AAAAABEDDWEQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVGIZDSNJRGM.
You are receiving this because you commented.

Awesome, that helps a lot. Thanks 👍

@vagas87 released version 0.3.1 with the pinned version. if you don't mind we can keep the PR open and I'll work on that once the upstream discussions are settled

Sure, why not.

Thanks again for your contribution. I've taken parts of it and incorporated it into the v1.0.0 release. Its currently being published on test PyPi, I'll probably release it later today after some more testing.

That's great, thanks you for that 🚀


will it need to be reinstalled after 7 day?

will it need to be reinstalled after 7 day?

If you do not own a developers account then yes.

why does pangu's jailbreak not need to?

Bc it's signed by the devs already.
And people don't see the point by wasting their precious time by signing over beta's.

will yalu102 sign this too after the release version?

It should. Now we are not prophets who can predict the future.
But there are always other signing providers available.

can u give me an email ,so i can contect u?

https://github.com/kpwn/yalu102/issues/64

#162

http://udidregistrations.com

This isn't code related.


Some syntax changes coming down in 0.9.0

Hi @matthias-Q !
Just to flag a couple of big changes coming down in 0.9.0.
I'm happy to help with things if needed. I don't think they're complicated changes — e.g. the tuple syntax is a straight swap, even though it's pervasive.

Totally missed this one. I will take a look in the next days. Sorry for the silence @max-sixty

No prob! Thanks1

@max-sixty is there a changelog or something? It is quite hard to find out what will be changed in 0.9.0

Yes! All the breaking changes should be labeled.
I just put a PR to make the working a bit better: https://github.com/PRQL/prql/pull/3007
Let me know anything at all I can do to help...

Thanks, a short example of the new function declaration and arrays would be nice.
I just added modules following https://github.com/PRQL/prql/blob/58c391a5b4011c6841f0d67711adf82a696927e6/web/book/src/internals/modules.md

Great re modules!
The biggest change is the array / struct change.
Then regex & functions are the only other significant ones.
Thanks!


[Bug]: Module "@telegram-apps/sdk-react" has no exported member "SDKProvider". ts(2305)

Telegram Application
Telegram for iOS, Telegram for macOS
Describe the Bug
package.json
"dependencies": {
"@next/third-parties": "^15.0.1",
"@nextui-org/react": "^2.4.1",
"@nextui-org/theme": "2.2.4",
"@tanstack/react-query": "^5.40.0",
"@telegram-apps/sdk-react": "^2.0.9",
"axios": "^1.7.2",
"bignumber.js": "^9.1.2",
"clsx": "^2.1.1",
"framer-motion": "^11.1.1",
"jotai": "^2.10.1",
"moment": "^2.30.1",
"next": "14.2.3",
"next-themes": "^0.2.1",
"react": "18.3.1",
"react-copy-to-clipboard": "^5.1.0",
"react-dom": "18.3.1",
"react-photo-view": "^1.2.6",
"sonner": "^1.5.0",
"tailwindcss": "3.4.3",
"vconsole": "^3.15.1"
},
To Reproduce
import {  SDKProvider } from '@telegram-apps/sdk-react'
// ^ Module "@telegram-apps/sdk-react" has no exported member "SDKProvider". ts(2305)

Expected Behavior
Why?

Because it has no SDKProvider. Read documentation

You are using another version
https://docs.telegram-mini-apps.com/packages/telegram-apps-sdk-react/2-x


URL (web) service?

[Product question but UserVoice is unavailable]
The article lists a spreadsheet with the URLs that must be allowed through the proxy. Once configured this requires periodic checks for changes, which is inconvenient.
Perhaps it is possible to create a webservice like described for Office365 ? Please?

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

ID: 944b7b97-efbf-e83d-9330-a825d901819d
Version Independent ID: 6c49c1c5-a178-0c9d-4768-fef1507b1a55
Content: Microsoft Defender for Endpoint on Linux
Content Source: microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-linux.md
Product: m365-security
Technology: mde
GitHub Login: @Dansimp
Microsoft Alias: dansimp

@Dansimp Please help us in resolving this issue. Thanks

This request requires developer assistance, which we don't have at this point in time. We'll keep this in mind for the future, but not something our team can support at the moment.


[nnpack] update && support more op

this pr is moved from https://github.com/dmlc/mxnet/pull/4373 @mli @clcarwin

@mli @tornadomeet
nnpack performance on android
cpu: 4xARM Cortex-A53 1.21GHz
system: armv7l  32bit android 4.4.4

network
batch size
nnpack+openblas(ms)
openblas(ms)
speedup

caffenet
1
1469
1540
1.05x

caffenet
2
3027
2456
0.81x

caffenet
4
4444
3941
0.89x

caffenet
8
7191
6898
0.96x

caffenet
16
12724
13224
1.04x

vgg16
1
5719
17567
3.07x

vgg16
2
12836
OOM

vgg16
4
16954
OOM

vgg16
8
27548
OOM

inception-bn
1
4275
6520
1.52x

inception-bn
2
8798
10308
1.17x

inception-bn
4
11667
17646
1.51x

inception-bn
8
17073
30554
1.79x

inception-bn
16
29097
54431
1.87x

inception-v3
1
12524
12388
0.99x

inception-v3
2
22660
22324
0.98x

inception-v3
4
40081
40017
0.99x

inception-v3
8
71303
70954
0.99x

gen_v3
1
3012
66429
20.05x

gen_v3
2
11724
141053
12.03x

gen_v3
4
16689
OOM

gen_v3
8
31948
OOM

gen_v3
16
57284
OOM

gen_v3: mxnet/example/neural-style/end_to_end/gen_v3.py

@clcarwin thanks very much!   it seems NNPACK is very useful for 3*3 conv, like gen_v3,vgg.

@piiswrong had moved use_nnpack to CreateOp() of convolution operator.

LGTM after changing FC layer CreateOp

@piiswrong done.

@clcarwin  would your add a description to https://github.com/dmlc/mxnet/blob/master/docs/how_to/nnpack.md of how to build/install nnapck with MXNet on ARM/android, this should be very helpful for some newbies. thanks.

@tornadomeet I use Android.mk and Application.mk to build my android mxnet projects for using ndk-build system. It is incompatible and more complex than mxnet's amalgamation method. My experience may not suit for newbies.
If mxnet team want to deprecate amalgamation method someday, I can pr ndk-build method.

@clcarwin got it, thanks.


It's able to read binary data xlsx file?

I have to read a xlsx file but it is a binary data file and in momery.I read the source and hpp files but not found.

Hi @Jiejiewai
I'm sorry, but no. OpenXLSX only supports .xlsx (and .xlsm) files, not the binary .xlsb format.


Create saifrahman.json

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

You can remove the slashes after the links for your blog, instagram and linkedIn has that isnt really needed and the site will load even without that.

@saifrahmn Please merge https://github.com/saifrahmn/LinkFree/pull/1 and request a re-review from me.


Added 2 Array concepts

Thanks for your contribution @harshchan 🎈

Please make your repo hacktober fest accepted 2021
it would be a great help.
Looking for contributing more ;)


Bug? LeftNav route not working.

http://material-ui.com/#/components/left-nav
The routes get-started, css-framework and components didn't do anything.

Hi mewben, I found this confusing too. The route attribute isn't actually a property, you could call it anything you want. You need to handle this in the onChange callback: (see https://github.com/callemall/material-ui/blob/2eb14e69c411e9165d696df1a88d4ac8036591bf/docs/src/app/components/app-left-nav.jsx#L56)
Alternatively you can use the LINK menu item type and pass in the url like shown in the doc you linked.

Ahh.. I see.. Thanks @afhammad

I'm having a problem with this... the callback onChange never fires.... why?
I followed the docs aswell having:
Component
<LeftNav
  ref="leftNav"
  docked={true}
  isInitiallyOpen={false}
  header={header}
  menuItems={menuItems}
  selectedIndex={this._getSelectedIndex()}
  onChange={this._onLeftNavChange} />

_onLeftNavChange function
_onLeftNavChange(e, key, payload) {
  this.context.router.transitionTo(payload.route);
}

but the _onLeftNavChange never fires.. what's my mistake?
thanks

Nevermind.
I forgot the injectTapEventPlugin(); ^^


🚀 Feature: Autogenerated sidebar

🔖 Feature description
Any reason why not using feature avialable with docusaurus
link
🎤 Context
devs have too manual manage sidebar.json
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

Worth a shot!
I'd expect things to be reordered in ways that we might not want, but that can be fixed by adopting the numbering system we use in some places though, e.g. https://github.com/backstage/backstage/tree/master/docs/backend-system/architecture
It might also be worth waiting with this until more of the documentation restructure is complete, #21946


gmail rate limits exceeded

HttpError: <HttpError 429 when requesting https://www.googleapis.com/gmail/v1/users/me/labels?alt=json returned "User-rate limit exceeded.  Retry after 2018-04-27T17:20:36.724Z">
The error hits on labels but it appears the root issue is greedy gmail.users.threads.list

TODO: optimize threads.list calls

tuned this down by:
changing label cron from 5->15 min schedule
migrating attachments daily instead of hourly
TODO: see if this remains an issue. logs suggest this was an infrequent but recurring problem

appears to be fixed. no 429 errors on console this week. closing.

Reopening to include crontab

fixed in 9be3d21


Holding shift allows the player to turn the camera with the mouse

Also made visual feedback to show the player is holding shift. The mouse becomes a crosshair instead of a pointer. I played with hiding it, but the technique is to move mouse to one side or the other, then release shift, recenter, repeat. It becomes natural after a short while, but knowing the location of the mouse is important.


Add uwp support via the dlls

I extracted these DLLs from the official download here: https://sqlite.org/2017/sqlite-uwp-3210000.vsix
I used this in a HoloLens project to much success.

Hi @jwittner, thanks for this PR! I'm doubting about accepting it because I would normally use sqlite dlls via nuget when dealing with UWP projects. What would be the benefit of having the dlls here in the project? Why didn't you choose to install them via nuget? (I'm just curious about it 😜)

When building UWP apps from Unity we don't preserve the UWP solution that Unity generates. By putting the UWP dlls into this project I'm able to build UWP builds for my Unity project. Specifically, my team builds HoloLens projects and these dlls enabled us to use your awesome library. =)

I guess people will be able to use these dlls or others if they want so... merged! Thanks!

I am getting some issues while running the example project on unity5.3.4f1 targeting universal windows 10 build.
"Assets\Scripts\SQLite.cs(1584,47): error CS0731: The type forwarder for type 'Windows.Storage.ApplicationData' in assembly 'Windows' causes a cycle
Assets\Scripts\SQLite.cs(1584,47): error CS1069: The type name 'ApplicationData' could not be found in the namespace 'Windows.Storage'. This type has been forwarded to assembly 'Windows, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime' Consider adding a reference to that assembly.
Assets\Scripts\SQLite.cs(225,51): error CS0731: The type forwarder for type 'Windows.Storage.ApplicationData' in assembly 'Windows' causes a cycle
Assets\Scripts\SQLite.cs(225,51): error CS1069: The type name 'ApplicationData' could not be found in the namespace 'Windows.Storage'. This type has been forwarded to assembly 'Windows, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null, ContentType=WindowsRuntime' Consider adding a reference to that assembly."
I have successfully created builds targeting WP 8.1 and targeting UWP 8.1 platforms but getting error when doing this for UWP 10.Any Help would be really appreciated. Thanks

Thanks for your reply, I did not changed any thing in player settings, Can you send me the screen shot of what player settings is required against successful building for UWP 10?

I have tried to build by switching compilation overrides to "Use Dot Net Core Partially" but got same errors. I am really struggling to solve this. Please help me on this ASAP.Thanks

I don't have such an old build of Unity available to me. Can you send me a capture of your player properties and maybe I can suss out what you need set?

Sure sending it to you.

Which unity version you have used to make the build? other than this please let me know which visual studio version you have used and the windows 10 sdk version too.

Can you discuss this in #77? It would be easier for other users to follow and help. 😉


runtime/race: eliminate dependency on cmd/cgo

There is a circular dependency between runtime/race and cmd/cgo in -race build.
Everything depends on runtime/race, but runtime/race is a cgo package.
Currently it's resolved by a hack in go tool:

    // If we are not doing a cross-build, then record the binary we'll
    // generate for cgo as a dependency of the build of any package
    // using cgo, to make sure we do not overwrite the binary while
    // a package is using it.  If this is a cross-build, then the cgo we
    // are writing is not the cgo we need to use.
    if goos == runtime.GOOS && goarch == runtime.GOARCH && !buildRace {

We pretend that packages do not depend on cmd/cgo. But as the result we can overwrite
cmd/cgo binary while it is used.

A better solution is to make runtime/race to be not dependent on cmd/cgo.

Gentle ping @dvyukov @ianlancetaylor how are we doing here? Is this issue still a concern? Could I be of help here with your guidance?

This is still an issue. Fixing it will require wiping all dependencies on libc from race runtime. I've removed the main one -- on malloc/free -- some time ago, but there are still some minor ones.
If we eliminate dependency on libc/cgo, it will also allow using -race without enabling cgo, which would be nice as well.
But nobody actively complained about this as far as I know, so this was never high on my list.

Gotcha gotcha, thanks @dvyukov! Oh right, you opened https://github.com/golang/go/issues/9918 which is still open.

If we eliminate dependency on libc/cgo, it will also allow using -race without enabling cgo, which would be nice as well.
But nobody actively complained about this as far as I know, so this was never high on my list.

In the meantime, many people actively complained about that issue :) Many (including me!) seem to want to build scratch-based Docker images with race-detector-enabled binaries copied from the previous Docker build stage.
What are minor things that are left?

What are errors when cgo is disabled for -race build?

https://github.com/golang/go/blob/3fb1d95149fa280343581a48547c3c3f70dac5fb/src/cmd/go/internal/work/init.go#L169
If that check is commented out, it fails with:
runtime/race/internal/amd64v1(.text): relocation target getuid not defined
runtime/race/internal/amd64v1(.text): relocation target pthread_self not defined
runtime/race/internal/amd64v1(.text): relocation target abort not defined
runtime/race/internal/amd64v1(.text): relocation target mkdir not defined
runtime/race/internal/amd64v1(.text): relocation target isatty not defined
runtime/race/internal/amd64v1(.text): relocation target pthread_attr_getstack not defined
runtime/race/internal/amd64v1(.text): relocation target sigaction not defined
runtime/race/internal/amd64v1(.text): relocation target getrusage not defined
runtime/race/internal/amd64v1(.text): relocation target syslog not defined
runtime/race/internal/amd64v1(.text): relocation target getrlimit not defined
runtime/race/internal/amd64v1(.text): relocation target pipe not defined
runtime/race/internal/amd64v1(.text): relocation target sched_getaffinity not defined
runtime/race/internal/amd64v1(.text): relocation target __sched_cpucount not defined
runtime/race/internal/amd64v1(.text): relocation target pthread_attr_init not defined
runtime/race/internal/amd64v1(.text): relocation target pthread_getattr_np not defined
runtime/race/internal/amd64v1(.text): relocation target pthread_attr_destroy not defined
runtime/race/internal/amd64v1(.text): relocation target exit not defined
runtime/race/internal/amd64v1(.text): relocation target __errno_location not defined
runtime/race/internal/amd64v1(.text): relocation target setrlimit not defined
runtime/race/internal/amd64v1(.text): relocation target sysconf not defined
runtime/race/internal/amd64v1(.text): relocation target clock_gettime not defined
/go/pkg/tool/linux_amd64/link: too many errors

which looks similar to https://github.com/golang/go/issues/9918#issuecomment-187610493

To fix most of these one would need to add more ifdef's similar to this one:
https://github.com/llvm/llvm-project/blob/ca003ee06d0eac7e8facc179181298a05e4d03ed/compiler-rt/lib/tsan/rtl/tsan_platform_linux.cpp#L152
I would assume most uses of these libc functions can be simply removed as not needed for the Go version (e.g. isatty/pthread_self).
Some may need to replaced with calls to internal analogs. E.g. for exit we have Die in sanitizer runtimes. Not sure why we ever need to call exit.
Few may be harder to remove. These need to be dealt on a case-by-case basis.
Once all of these are removed, we also need a test in llvm upstream to prevent introduction of new libc calls in future.
The test can be added here: https://github.com/llvm/llvm-project/blob/ca003ee06d0eac7e8facc179181298a05e4d03ed/compiler-rt/lib/tsan/go/buildgo.sh


UP5K with internal osc breaks..

hi Luke, the "poor man" USB bootloader concept is a VERY clever idea! thanx.. :-)
i've just tried to "compile" the Icebreaker-bitsy flavour with just a little tweak for using the internal OSC (to test eventually on UPDuino,, [*]).
ifdef INT_CLK   wire pin_clk;         // try with the internal clock, i've put the VCCPLL caps..     SB_HFOSC OSCInst0(                      .CLKHFEN(1'b1),                      .CLKHFPU(1'b1),                      .CLKHF(pin_clk)   );    defparam OSCInst0.CLKHF_DIV = "0b00";  // 48MHz DIVIDED by 1 endif
..but the place&route step breaks this way
BTW this log is about when i tried to skip also the instantiation of the PLL, but the break-up is the same..
is this report triggering any hint about solution?
thanx
andrea
[*] i know the UPDuino is a very broken design, in term of signal integrity! i just added small caps for improving PLL, but anyway, i know it would be more difficult for USB to works, then other board.
the issue on the "firmware" routing is anyway independent. and if those Lattice guys put a 48MHz int OSC, it means probably that the USB interfaces was a "use case" to be considered IMHO.

This seems to be an arachne-pnr issues, which I'll look into - it seems that its promoting a global net onto the global used for the HFOSC output. I'm not sure why that is, I fixed an issue like that a while back and haven't seen it since but this seems to be a case not covered by that fix.
In the mean time, put the following attribute immediately before the SB_HFOSC as a workaround:
(* ROUTE_THROUGH_FABRIC=1 *)

yeah, thanx Dave for the quick workaround.
now i can create the bootloader.asc -> and then the .bin with icepak.
icetime still bumps this way:
icetime -d up5k -mtr bootloader.rpt bootloader.asc
// Reading input .asc file..
// Reading 5k chipdb file..
// Creating timing netlist..
terminate called after throwing an instance of 'std::invalid_argument'
  what():  stoi
Makefile:40: recipe for target 'bootloader.rpt' failed
make: *** [bootloader.rpt] Aborted (core dumped)
make: *** Deleting file 'bootloader.rpt'

just a followup about "the real test". short summary: still no joy!
here the connection.
here the dmesg excerpt:
[127313.191670] usb 1-2.4.2: new full-speed USB device number 27 using xhci_hcd
[127313.275707] usb 1-2.4.2: device descriptor read/64, error -32
[127313.483730] usb 1-2.4.2: device descriptor read/64, error -32
[127313.691685] usb 1-2.4.2: new full-speed USB device number 28 using xhci_hcd
[127313.791743] usb 1-2.4.2: device descriptor read/64, error -32
[127313.999741] usb 1-2.4.2: device descriptor read/64, error -32
[127314.207688] usb 1-2.4.2: new full-speed USB device number 29 using xhci_hcd
[127314.207778] usb 1-2.4.2: Device not responding to setup address.
[127314.415802] usb 1-2.4.2: Device not responding to setup address.
[127314.623702] usb 1-2.4.2: device not accepting address 29, error -71
[127314.723719] usb 1-2.4.2: new full-speed USB device number 30 using xhci_hcd
[127314.723818] usb 1-2.4.2: Device not responding to setup address.
[127314.931788] usb 1-2.4.2: Device not responding to setup address.

next move, as i have an UART handy, i plan to setup some kind of instrumentation  for it (at least to check the internal clk is really 48MHz..)  to deal with printing out the internal state machine and check where it hangs. of course USB is a HUUGE spec, so it's a bit of a shot in the dark.
anyway i suppose this "issue" about FW creation could be closed now.

I think @esden is also working on this, you might want to talk to him.
Please could you put your exact code, constraints and Makefile somewhere, so I can look into the arachne and icetime issues?

you can find the modded files in Upduino dir on this repo/branch:
https://github.com/aventuri/TinyFPGA-Bootloader/tree/20180228_intOsc
i'd like to give you the 'icetime' version but i miss to see the param that could print out the "git commit" that sourced it .. could be an useful addendum, as there's still some development ongoing, in the foreseable future..

...my icetime binary has been compiled from this source code:
commit 1d84b7a53183df3d2d620d5633ca82db6ab90186 (HEAD -> master, origin/master, origin/HEAD)
Merge: edbf5fc 58e2e74
Author: Clifford Wolf<EMAIL_ADDRESS>Date:   Wed Feb 14 18:48:09 2018 +0100

    Merge pull request #124 from daveshah1/ultra

    Add iCE40 Ultra (ice5lp) support to icepack
[andrea@CHUWI123 ~/fpga/icestorm/icetime (master)] $

Thanks for sharing your code.
The icetime issue has been fixed in icestorm PR #129 (I hadn't tested the use of route_through_fabric with icetime before), but beware that icetime is still not giving a useful result because there are logic loops in the design (that is a bigger issue, and as much of a problem with the design as icetime IMO).
The arachne-pnr issue still needs investigation.

I don't believe that the UP5K internal oscillator is stable enough or accurate enough to be used as a source clock for USB.


Expand tracker database fields

The informational fields on trackers should be expanded to provide richer information on each entity. Fields to be added:

Operating country
Privacy contact / Data protection officer
Description/in their own words: A short description of what the tracker/company does which can be displayed on the website.

as well as link to:

privacy policy

Purposes. Can be scraped from here

Descriptions can be scraped from here


Leap

This needs some refactoring of the state machine to match our intended setup.

@saams4u ready for review


Add student's address

As a new user, I can include a student's address while adding the student's entry, so that I can have a record of where they live.

Closing as it's already done in AB3.


Task reschedule, How to do?

Hello,
I have a question about task (re)schedule. How to schedule a task ‘B’ in order to start 10 secondes (for example) after the last execution of a task ‘A’, as a timeout behaviour.
I seen example with SpawnHandle and reschedule but I am not able to integrate this solution into my code.
I tried to store SpawnHandle into Local ressource of task ‘A’ in order to task ‘A’ spawn the task ‘B’ and store the SpawnHandle of task ‘B’. But I have this compilation error
« cannot move out of *ctx.local.handler_B which is behind a mutable reference »
Bellow extraction of program to tried to explain my situation :
Local {
    handler_B : SpawnHandle,
}

// INTO TASK A

match task_B::spawn_after(10.secs()) {
                Ok(val) => {
                    ctx.local.handler_B= val;
                }
                Err(e) => {
	ctx.local.handler_B.reschedule_after(10.secs())

         // Below code tried too
         //*ctx.local.handler_B.reschedule_after(10.secs())
	}
}

Certainly there is some information that I have not understand fully, What is wrong ?
Anyone have a solution for this situation ?
Thank you for your help.

Hi,
What's missing is that you don't have a way to encode if you have a spawn handle or not.
You need to change handler_B: SpawnHandle to handler_B: Option<SpawnHandle> so you can move a spawn handle into the storage and then take it out with ctx.local.handler_B.take().map(|handle| handle.reschedule_after(10.secs())).

Thanks for your help, with Option encapsulation and take function it's work well.

Awesome! Sounds like you got it working, so I'll close the issue


another way to test jupyter-book

Can I use jupyter-book without GitHub webpage upload or ruby server?

Hmmm - right now I can't think of any other way to build the books. What else are you imagining?
There's an issue to discuss moving the build system to nikola (#83) and folks have also mentioned gatsby/react, but that'd be a while before those get implemented.


Add some Listing model tests

#143 raised the question of some tests on the Listing model: the belongs_to :creator, has_many_attached :photos, and acts_as_taggable_on :tags lines. We should write these tests! 😄

Can I try to do this?


Support persist docs on BigQuery: columns

Child issue of https://github.com/fishtown-analytics/dbt/issues/1573
To do:

Support persisting docs for columns in tables and views

If the project specifies a column that does not exist in the destination table, the comment on column statement may fail. This is the desired behavior.
BigQuery does not support adding column-level descriptions in DDL unless all columns in the relation are specified. Instead, we should pursue the following approach:

Create a relation without column comments
Fetch the relation schema from the BigQuery API
Update the relation schema with descriptions from the corresponding .yml file
Save the relation schema to persist these changes back to BigQuery

Just like in the generated docs, could the column descriptions also include the schema tests? We are using the schema tests as documentation as well as tests, and I think it would be helpful to show whether a column is UNIQUE, NOT NULL, etc in BigQuery too.

I think I'd recommend using the dbt documentation website for that purpose. I'm super on board with persisting column descriptions into the database, but I'd hesitate to add a bunch of free-form text generated by dbt at the same time.
What I can imagine is providing tools to generate a list of tests for a column as a string, then include that string in the stated column description. I'm also open to figuring out a way to add this to every column comment so that it happens automatically, but that's out of scope for the feature described in this issue IMO

In case it helps, here's the code we use for this:
from typing import Dict, List, Sequence

from google.cloud import bigquery
from google.cloud.bigquery.schema import SchemaField

def update_schema_documentation(
    client: bigquery.Client,
    table_name: str,
    table_description: str,
    field_descriptions: Dict[str, str],
) -> None:  # pragma: no cover
    """Update the documentation for a BigQuery table.

    Known limitations:

    - Does not support nested field definitions

    Feel free to fix these limitations!
    """
    table = client.get_table(table_name)
    table.description = table_description
    table.schema = _document_schema(table_name, table.schema, field_descriptions)
    client.update_table(table, ["description", "schema"])

def _document_schema(
    table_name: str, schema: Sequence[SchemaField], field_descriptions: Dict[str, str]
) -> List[SchemaField]:
    """Create a documented version of the given BigQuery schema."""
    existing_fields = set()
    new_schema = []
    for field in schema:
        description = field_descriptions.get(field.name)
        new_schema.append(
            SchemaField(
                name=field.name,
                field_type=field.field_type,
                mode=field.mode,
                description=description,
                fields=field.fields,
            )
        )
        existing_fields.add(field.name)
    undescribed_fields = existing_fields - set(field_descriptions)
    # TODO: Also raise an exception if we have described fields that don't exist.
    if undescribed_fields:
        # TODO: Raise a more specific exception so we don't have to pass table_name in.
        raise RuntimeError(f"Unexpected fields defined in {table_name}: {undescribed_fields}")
    return new_schema

Tests:
def test_document_schema_undocumented_fields() -> None:
    # _document_schema raises RuntimeError if we are missing documentation for
    # a field.
    with pytest.raises(RuntimeError):
        _document_schema("foo", [SchemaField("name", "INTEGER")], {})

def test_document_schema_empty() -> None:
    # We successfully document an empty schema by returning the same thing.
    assert _document_schema("foo", [], {}) == []

def test_document_schema_adds_docs() -> None:
    # _document_schema returns a new schema with the given descriptions added.
    new_schema = _document_schema(
        "table",
        [SchemaField("foo", "INTEGER"), SchemaField("bar", "STRING")],
        {"foo": "Full of fooness", "bar": "As you'd expect"},
    )
    assert new_schema == [
        SchemaField("foo", "INTEGER", "NULLABLE", "Full of fooness"),
        SchemaField("bar", "STRING", "NULLABLE", "As you'd expect"),
    ]

thanks @jml - that's super helpful! Are you able to submit a PR with a change like this? It would be super welcomed!

I'd genuinely love to, but I doubt I'll have an opportunity to do so any time soon.

I need this feature, so I'll take a stab at it. But I'm new to the codebase so might be slow... if anybody else wants to work on this please do!

hey @oliverxchen - we're wrapping up all of the code for v0.17.0, and we anticipate releasing a "release candidate" in the next couple of days! To that end, I submitted #2402 which adds column-level docs persistence for BigQuery.
Just wanted to give you a quick heads up in case this was something you're still chipping away at. Let me know if there's another issue that catches your eye - would be happy to help out with a contribution however I can!

@drewbanin great, thank you for the feature and up coming release! Sorry I couldn't get this in, was still trying to understand the code. I'll look for other issues I can try to help on

Hello guys,
Sorry to bother you, but I cannot make persist_docs configuration work on dbt with BigQuery to have persistent column descriptions while I suppose I am using the right syntax:
persist_docs={ "relation": true, "columns": true, "schema": true },
It is working fine for the table descriptions, but not the columns. Is there a known issue about that? Or did I miss something in the documentation?
Thanks a lot for your help.


Added documentation for flask implementation

Added documentation for flask implementation

Thank you very much, this is what I need.


Rollback: using timestamp 0 does not rollback the disk to latest as expected

Using a 0 timestamp does not rollback the disk to latest transaction as expected.

More info from telegram chat
Muhamad Azmy, [02.10.17 13:51]
@zaibon when i did a rollback to 'now' timestamp the machine booted again

Muhamad Azmy, [02.10.17 13:51]
so apparently it's the rollback to '0' that is broken

The odd thing here : when user specify 0 as the --end-timestamp, the player will replace it with current timestamp.

Are you guys talking about the same timestamp. What timestamp do you mean @muhamadazmy when you talk about now? and What timestamp do you talk about @iwanbk when you say current timestamp? Please be more specific and technical at all times... This tends to give communication problems if you're not careful.

@muhamadazmy I tried to restore by the way without giving any timestamp (and thus having 0 for both begin and ending):
zeroctl restore vdisk lede --parity-shards 1 --data-shards 1

and that restore works for me.
So are you sure that you are not really doing something wrong OR facing a bug not related to the timestamp at all?

@muhamadazmy @iwanbk any more progress on this issue, or can it be closed as wontfix?

@GlenDC Sorry for the late response.
We were trying the built in rollback feature of zero-disk to redistribute the keys on the available ardbs when one of the master ardbs is gone forever. So for example, if the ardb cluster consists of 4 nodes, and one is gone, we want to replay the entire tlog server for (all) vdisks to the latest point in time (now) so the rollback will rewrite the blocks back to the remaining 3 nodes. Of course the broken node was already marked as disabled.
According to @zaibon we should use timestamp 0 which means replay to the end of the tlog. But testing with this timestamp didn't produce the expected results.
I am not sure if this still a valid issue, this was like 26 days ago. Also rollbacking to timestamp now works fine.

But even at the time of reporting this issue both @iwanbk and me tested with timestamp 0, and that worked just fine as it was back then.
I'll close it for now, feel free to re-open if you think the issue you had was a problem in 0-Disk that's still in there.

@GlenDC sure, thanks for your time.


feat: allow peerDeps as import entry points

PR context
Let's say I have next in peerDependencies, and the following import in my package:
import something from "next/head"

When building the package with unbuild, it shows a warning: Potential implicit dependencies found: next/head, while I think it should be legal to use import from peerDeps.
Let me know if I should make any changes.

Thank you for building unbuild 🔥

Thanks!


Console is missing as a dependency

https://github.com/cprussin/purescript-httpure/blob/fe2e3f5f6de170002e23df6979561b1a59ab6660/src/HTTPure/Server.purs#L14
This breaks package set validation. Please add this to your bower.json and publish a patch version.

Ah will do. Don't know how I missed that, I thought the package set validation succeeded. Is there something I missed?

Fixed in v0.8.1

Thanks. I was pulling the latest version and that failed. This can be normally validated on bower with bower i -p (production) first, followed by then using normal bower i to install test dependencies

Aha, so something got installed into devDependencies instead of dependencies. That helps. I thought this was a psc-package.json issue. Thanks for that added context!


"Dynamic Island" improvement

The new "dynamic island" type of song display is excellent, but it would be better if we had some more details like the song name, artist name, and others...

This is weird, because dynamic island notification actually contains the things that you mentioned:

What macOS and Mac are you running?

I am using a M2-Pro MacBook Pro, macOS 15.1 (24B83).

I realized what the Issue is - I use light mode. If I switch to dark mode, it is working. Can you please make it compatible with light mode, too?? (Hardcoding the color of the font to white should work, I guess @martinfekete10)

Also, consider updating Tuneful on homebrew 🍺 (it downloads version 1.6 by default)...

+1. Same issue, switching to dark mode fixes it. I'm on macOS 15.2 beta.

Just released a new v1.7.1 with this issue fixed 🎉 Let me know if there is anything else


Internal description for the container

Could add an interanl description field for the container? So the users have the possibility to share certain infomations about the container.

Closing this issue for now,
Docker UI doesn't keep any internal DB to keep this information, and I don't see any easy way to show/share this info.


Webdriver Tests - Complete

page.object.model.demo - Demo Script with Page Object Model Approach with Page factory.
Assertions - TestNG - assert equals

Hi, I'm getting compilation error package webdriver does not exist on your submission:


URL Tracker stop redirecting Invalid URLs to 404 page

Hi
Using Umbraco 9.5 version with .net 6, When URL Tracker is enabled, it stops redirecting Invalid URLs to 404 custom page. though the URLs are not specifying in the URL Tracker list, It keeps on redirecting 404 requests to one specific application page. Which i think is invalid.
Though URL Tracker is enabled, It should redirect user to 404 page, If there is no matching page found in the application.

Hi @Daxesh59 ! Thank you very much for reaching out. Are you able to reproduce this behaviour on a clean installation and could you provide some steps to reproduce this? That will help me to analyse the exact issue that you're experiencing


Improve up.json-less directory workflow

[x] detect up.json
[x] validate .name
[ ] make it obvious to the user which directory they're attempting to deploy

quite a few people accidentally deploying the wrong dir, but we still want to help them set up the config

[ ] test for AWS credentials and guide them through that a bit better
[ ] maybe parse ~/.aws/credentials and display those

You probably meant this, but I'd display the profile name of the credentials used, not the credentials themselves.

haha yep, I had it already in a branch but I think I deleted it :(

Might be worth moving this to up init later and implying it, though it really doesn't do that much haha..


mapvote plugin

synced the fork and resolved conflicts, had to recreate pr

As this is now part of the core game, could we close this pull request? Are there any objections to me doing so?

As per the above, I am closing this pull request. The map voting feature that is part of the core game seems popular so I do not personally see a reason for map voting plugins to still exist at least in a chat voting format.


docs: update README

Update the README with correct information about passing env variables.

:tada: This PR is included in version 1.3.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Minor cleanup

@zmarkan: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@zmarkan: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Updates for Open Beta Program

Rolling out the Open Beta Program.

What do you think about adjusting the docs to that early on myrepos is added to liquibase.properties as repository= myrepos. This will prevent typing this parameter repeatedly.

 Didn't know we could do that! Ha!!!


Refine Create Project from Template progress notification messages and increments

[x] Refine Open new Workspace prompt when trying to create new project in an existing workspace with files.
[x] Revert template repo cloning progress increment changes made in #56
[x] Change Progress message title to shorter Create Project
[x] Shorten other notification messages for the different steps in template project creation process.
[x] Show incremental info messages during repo cloning in the progress notification message just like we do in the Evidence Output view
[x] Add started cloning template repo info message to the progress display
[x] Bump Install Dependencies delay to 30 secs in build.ts

Originally posted by @RandomFractals in https://github.com/evidence-dev/evidence-vscode/issues/57#issuecomment-1574379001

@archiewood see the changes applied above for the changed progress increment, open new workspace prompt and create project from template progress messages.
The issue you recorded in #58 with Finished creating message lingering is very minor because eventually it goes away, and there is only 15 sec delay timer set for the github repo cloning. Eventually that message goes away, and you can expand it to see full message and the final Finished step.
I bumped that clone repo delay timer and progress display to 25 secs to reproduce it on windows 10 b/c that timing was set to expire perfectly in my prior testing.
See recorded finished step expand delay with the longer timer. We'll use the 15 sec as is now, and can revisit this when we switch to embedding template project content into extension package for faster cloning and creation.

Final Create project from a template UX from start to finish.
Note: We can't improve it more unless we embed template project in the extension package code under /templates.

Shorter template prompt and dialog title:

New error message display when the provided url is not a github url. We also reopen template dialog with the default template displayed for the users to use it to provide a valid github url:

Refined repo cloning git info messages display in Output view:


Magento 1 -> Shopware 6: Include inactive shipping methods in premapping

When doing Magento 1 migrations, the current query for loading out shipping methods for mapping into Shopware 6 looks like this:
$sql = <<<SQL
SELECT
    DISTINCT carrier.*
FROM
      (
          SELECT
            REPLACE(REPLACE(config.path, '/title', ''), 'carriers/', '') AS carrier_id,
            config.*
          FROM {$tablePrefix}core_config_data config
          WHERE path LIKE 'carriers/%/title' AND scope = 'default'
      ) AS carrier,
      (
          SELECT
            REPLACE(REPLACE(config.path, '/active', ''), 'carriers/', '') AS carrier_id
          FROM {$tablePrefix}core_config_data config
          WHERE path LIKE 'carriers/%/active' AND value = 1
      ) AS carrier_active
WHERE carrier.carrier_id = carrier_active.carrier_id;
SQL;

This filters out any inactive shipping methods which is a problem if you have old orders using shipping methods that are no longer active. We've also often seen merchants who have several carriers installed in Magento and deactivate/activate them regularly depending on what rates they can get from the providers. That means that right now, any orders that use inactive shipping methods in the moment of the migration cannot be migrated.
I suggest simplifying the SQL into this, which includes inactive shipping methods:
$sql = <<<SQL
          SELECT
            REPLACE(REPLACE(config.path, '/title', ''), 'carriers/', '') AS carrier_id,
            config.*
          FROM {$tablePrefix}core_config_data config
          WHERE path LIKE 'carriers/%/title' AND scope = 'default'
SQL;

That way, all shipping methods can be mapped.

[public] Shopware automated response: This issue is linked to the internal issue: MIG-267
[created from MIG-267, comment 501699]


[BUG] Rename "users" API to "profiles"

Description
We use the model profile but the api path is users, this should be renamed to profiles
Screenshots
No response
Additional information
No response

Hey folks,
This issue would be perfect for me who is making the first ever open source contribution, has some BE knowledge, but no experience with Next.js.
Would it be possible to assign me this one? Thank you.

Sure @daxitpatel I have assigned it to you

All the best, @daxitpatel 🥳

@daxitpatel how are you getting on with raising a PR for this Issue?

Hey @SaraJaoude . Hope you are doing well.
Actually, I was away the last week. So, could not look much into this. Set up the project and GitHub OAuth2 flow in my local machine 🎉. PR should be available tomorrow.
Thank you,


Need patch for OSVDB-131677 against 2.5.x

A security advisory was issued for the mail gem recently: https://github.com/rubysec/ruby-advisory-db/blob/master/gems/mail/OSVDB-131677.yml
It indicates that the vulnerability was fixed in 2.6.0. However, actionmailer 3.2 (part of rails 3.2) has a dependency on ~> 2.5.4. See https://github.com/rails/rails/blob/3-2-stable/actionmailer/actionmailer.gemspec#L23
According to https://github.com/rails/rails/pull/22631, the rails project is unwilling to bump the version to 2.6.0.
How hard would it be to backport that fix to 2.5 and cut a new release?

+1, would also be great to have a 2.4.x backport as well for rails 3.1.

Here's a monkey patch.  You can also apply this when you can't update the gem version for some reasons.
require 'mail'

if Gem::Version.new(Mail::VERSION.version) < Gem::Version.new('2.6')
  Mail::Field.class_exec do
    original_method = instance_method(:create_field)
    define_method(:create_field) do |name, value, charset|
      value = value.gsub(/[\r\n \t]+/m, ' ') if value.is_a?(String)
      original_method.bind(self).call(name, value, charset)
    end
  end
end

Is there anything preventing this from being fixed and released?

:wave: @jeremy: Are there any blockers to #949 and #950 being merged into their relevant version branch targets? I'm interested in getting this applied to the 2.5-stable branch.

This is backporting a change that's not meant to fix the underlying vuln (with input validation on net/smtp) but happens to mask it with a coincidental behavior change. It was called out the sec advisory only because it bisected as the fix.
We can introduce stronger input validation at the mail handling layer and backport it without breaking compat, but 1. this isn't that change and 2. it won't conclusively address the original vuln, SMTP injection via email address.
Will keep this issue open to track resolution.

@jeremy: Could you elaborate on what other input validations would be needed to address the vulnerability in older versions of the mail gem? I'd be happy to try and lend a hand getting things back-ported, since I'd also find this very useful in dealing with older Rails version
In reading the whitepaper, it seems like stripping the line break characters (as @wktk's original patches did) would largely mitigate the primary issue, or am I missing something else? The one other item I see is "CRLF-less attack" in section 4.2, which seems like it could be mitigated by enforcing length limits on the input.
Are there other issues you're aware of that would need to be addressed in the older mail versions? They do recommend validating for compliance with RFC 5321, but I'm not sure that's strictly necessary as long as line breaks are rejected or stripped, since they also mention:

Of course, a little more relaxed rule can be an option, as a small proportion of existing and actually used addresses is known to be incompliant to the standard. Needless to say, when a relaxed rule is employed, addresses containing line-breaks must not be allowed.

Fixed in https://github.com/mikel/mail/pull/1097. Backported to 2.6.x in https://github.com/mikel/mail/pull/1098 and 2.5.x in https://github.com/mikel/mail/pull/1099.


multithreading support

I wanted to load resources in the background
ResourceLoader.load_threaded_request("res://main.tscn", "", false);

but my game crashed, but boon was the message)
ERROR: multi-threaded call not supported yet
   at: check_internal_state (modules/GodotJS/bridge/jsb_environment.h:276)

I'd like to ask how hard it is to add support, and if it can be done on the Godot side since thread execution is not required in GodotJs or am I missing something?

I'll try to fix this case right away. But overall, this part still needs to be finished/improved in future versions (finding a simple but robust solution, especially for isolated threaded execution).

I tested on my side with similar logic but did not encounter this check. Could you please provide more details about the loader and loaded scene?
My test case contains 2 scene, and a script attached on each scene.
main.tscn with MainControl.ts:
import { Error as GDError, Node2D, PackedScene, ResourceLoader } from "godot";

function load_scene_async(path: string) {
    return new Promise<PackedScene | null>(resolve => {
        let err = ResourceLoader.load_threaded_request(path, "", true);
        console.log(path, GDError[err]);

        let timerid: NodeJS.Timeout;
        timerid = setInterval(() => {
            let status = ResourceLoader.load_threaded_get_status(path);
            if (status != ResourceLoader.ThreadLoadStatus.THREAD_LOAD_IN_PROGRESS) {
                clearInterval(timerid);
                if (status == ResourceLoader.ThreadLoadStatus.THREAD_LOAD_LOADED) {
                    resolve(<PackedScene>ResourceLoader.load(path));
                } else {
                    resolve(null);
                }
            }
        }, 20);
    })
}

export default class MainControl extends Node2D {
    async _ready() {
        console.log(MainControl.name, "ready");
        let path = "res://secondary.tscn";

        let scene = await load_scene_async(path);
        if (scene) {
            let node = scene.instantiate();
            this.add_child(node);
        }
    }
}

secondary.tscn with SecondaryControl.ts:
import { Node2D } from "godot";

export default class SecondaryControl extends Node2D {
    _ready(): void {
        console.log(SecondaryControl.name, "ready");
    }
}

Hmm, I don't seem to see much difference, I also execute inside the promise, here is my code I specifically commented out that it falls on load.
export default class AssetsPromiseLoader extends Node {
	private promises: AssetsPromiseData[] = [];

	public load(items: LoadItem[], onProgress?: ProgressCallback): Promise<any[]> {
		return new Promise((resolve, reject) => {
			for (let item of items) {
				ResourceLoader.load_threaded_request(item.url, "", false);
			}
			this.promises.push({resolve, reject, items, onProgress});
		});
	}

	_process(_delta: float64) {
		// const deletePromises: number[] = [];
		// for (let i = 0; i < this.promises.length; i++) {
		// 	const data = this.promises[i];
		// 	let loadedCount = 0;
		// 	let fullProgress = 0;
		// 	for (let item of data.items) {
		// 		const progress = new GArray<number>();
		// 		const status = ResourceLoader.load_threaded_get_status(item.url, progress);
		// 		fullProgress += progress.get_indexed(0);
		// 		switch (status) {
		// 			case ResourceLoader.ThreadLoadStatus.THREAD_LOAD_INVALID_RESOURCE:
		// 				data.reject(`Invalid resource: ${item.url}`);
		// 				deletePromises.push(i);
		// 				break;
		// 			case ResourceLoader.ThreadLoadStatus.THREAD_LOAD_FAILED:
		// 				data.reject(`Failed to load: ${item.url}`);
		// 				deletePromises.push(i);
		// 				break;
		// 			case ResourceLoader.ThreadLoadStatus.THREAD_LOAD_LOADED:
		// 				loadedCount++;
		// 				break;
		// 		}
		// 	}
		// 	if (data.onProgress) {
		// 		data.onProgress(fullProgress / data.items.length);
		// 	}
		// 	if (loadedCount === data.items.length) {
		// 		data.resolve(data.items.map(item => ResourceLoader.load_threaded_get(item.url)));
		// 		deletePromises.push(i);
		// 	}
		// }
		// this.promises = this.promises.filter((_, i) => !deletePromises.includes(i));
	}
}

I also think there are no essential differences in the sample code. I'll try it again on other platforms.
BTW, could you provide the stacktrace of the assertion failure by debugging your project in play mode (or from the log file of godot)?

OS: linux (mint)
If I understand how to run it correctly, that's all it gives me.
Log
Initialize godot-rust (API v4.3.stable.official, runtime v4.3.stable.custom_build)
Godot Engine v4.3.stable.custom_build.77dcf97d8 - https://godotengine.org
TextServer: Added interface "Dummy"
TextServer: Added interface "ICU / HarfBuzz / Graphite (Built-in)"
JoypadLinux: udev enabled and loaded successfully.
Xshape 1.1 detected.
Xinerama 1.1 detected.
Xrandr 1.6 detected.
Xrender 0.11 detected.
Xinput 2.2 detected.
XInput: Refreshing devices.
XInput: No touch devices found.
WARNING: XOpenIM failed
     at: DisplayServerX11 (platform/linuxbsd/x11/display_server_x11.cpp:6103)
WARNING: GENERAL - Message Id Number: 0 | Message Id Name: Loader Message
        terminator_CreateInstance: Failed to CreateInstance in ICD 3.  Skipping ICD.
        Objects - 1
                Object[0] - VK_OBJECT_TYPE_INSTANCE, Handle<PHONE_NUMBER>5232
     at: _debug_messenger_callback (drivers/vulkan/rendering_context_driver_vulkan.cpp:305)
WARNING: XCreateIC couldn't create wd.xic
     at: _create_window (platform/linuxbsd/x11/display_server_x11.cpp:5708)
Devices:
  #0: NVIDIA NVIDIA GeForce RTX 4060 Ti - Supported, Discrete
  #1: Unknown llvmpipe (LLVM 15.0.7, 256 bits) - Supported, CPU
- Vulkan Variable Rate Shading supported:
  Pipeline fragment shading rate
  Primitive fragment shading rate
  Attachment fragment shading rate, min texel size: (16, 16), max texel size: (16, 16), max fragment size: (4, 4)
- Vulkan multiview supported:
  max view count: 32
  max instances: 134217727
- Vulkan subgroup:
  size: 32
  min size: 32
  max size: 32
  stages: STAGE_VERTEX, STAGE_TESSELLATION_CONTROL, STAGE_TESSELLATION_EVALUATION, STAGE_GEOMETRY, STAGE_FRAGMENT, STAGE_COMPUTE, STAGE_RAYGEN_KHR, STAGE_ANY_HIT_KHR, STAGE_CLOSEST_HIT_KHR, STAGE_MISS_KHR, STAGE_INTERSECTION_KHR, STAGE_CALLABLE_KHR, STAGE_TASK_NV, STAGE_MESH_NV
  supported ops: FEATURE_BASIC, FEATURE_VOTE, FEATURE_ARITHMETIC, FEATURE_BALLOT, FEATURE_SHUFFLE, FEATURE_SHUFFLE_RELATIVE, FEATURE_CLUSTERED, FEATURE_QUAD, FEATURE_PARTITIONED_NV
  quad operations in all stages
Vulkan 1.3.277 - Forward Mobile - Using Device #0: NVIDIA - NVIDIA GeForce RTX 4060 Ti
Startup PSO cache (0.8 MiB)
XcursorGetTheme could not get cursor theme
ScreenSaver: DBus 1.12.20 detected.
FreeDesktopScreenSaver: Acquired screensaver inhibition cookie:<PHONE_NUMBER>
PortalDesktop: DBus 1.12.20 detected.
Using "default" pen tablet driver...
Creating VMA small objects pool for memory type index 1
Shader 'CanvasSdfShaderRD' (group 0) SHA256: f65579ae334cdfb6901aee2527afd18ed626d1067a35c91f12fb632b45ce7f21
Shader 'SkeletonShaderRD' (group 0) SHA256: 4964fd59acf4406110ae7bca4b716f23ae52cc19864e21a8a35aee53e141e17e
Shader 'SortShaderRD' (group 0) SHA256: 0b1e36114ab5330dc340cc740b0b946ed2dbf43098119b8d29cfa0222da18b7a
Shader 'ParticlesShaderRD' (group 0) SHA256: 47fcf57848349fdf54197e5c1f64750a69c8d54787d3509ade4781c9faa31654
Shader 'ParticlesCopyShaderRD' (group 0) SHA256: 69566a7b0235d75ec40f504cd5555856aace22b5273899269166fde57287d26e
Shader 'CanvasShaderRD' (group 0) SHA256: 165f6964cfc63fea91c4221f04e7b8a54b5dc39d76b5a57aed5f99b20050b148
Shader 'CanvasOcclusionShaderRD' (group 0) SHA256: 42f2245b35206bcace1cda9e39e9282519e9967978ba6d5956472809525b1150
Shader 'SceneForwardMobileShaderRD' (group 0) SHA256: e902df56af9ca9d9d9416d71378d35cb342cbc94502027ef4929feede81891a9
Shader 'SkyShaderRD' (group 0) SHA256: 4bc541bfde1c30032df77bb4c98974909ad0368d22557f44e6cf095b26c0490a
Shader 'BokehDofRasterShaderRD' (group 0) SHA256: f30ffa9b63b7111cdeebc9cfd845e16bce37fb3def0098b0ea4291c5cba4c56c
Shader 'BlurRasterShaderRD' (group 0) SHA256: 1491fde07959e0231c42129c86e0b36750d05d340fa12a234e747a34c291ab85
Shader 'CopyShaderRD' (group 0) SHA256: 4a43f34799f84bc5a387aff816d36330149d91299172af9be2d3ab05cc0c4e9d
Shader 'CopyToFbShaderRD' (group 0) SHA256: 8668028c5ceed89276611359329de4a0f5d40702546caecc31456f63f6f9ffe8
Shader 'CubeToDpShaderRD' (group 0) SHA256: e3db5adc31b15e80112f4d7497dc8563c39b7d64675a53dcce7f9511c5ca9f80
Shader 'CubemapDownsamplerRasterShaderRD' (group 0) SHA256: 7b25ae2b6822705c2714ecbc0e14d2af08ab7d08e88a1c3b7fa0ecc9bb281250
Shader 'CubemapFilterRasterShaderRD' (group 0) SHA256: 41fc5058a6a86412a99e75cfc00cb64be45eb0aa6d46278a0a0355ed01bc5487
Shader 'CubemapRoughnessRasterShaderRD' (group 0) SHA256: 2b317415ef9a47a49583fda31b04795e8751db94b488132f8816daa29362958a
Shader 'SpecularMergeShaderRD' (group 0) SHA256: a119881bb41d0ec2f36a7f060866ec38b88afa6d0e484a431c65b35b5a2e820b
Shader 'ShadowFrustumShaderRD' (group 0) SHA256: c9c1b6421f8f6625effc9ddfa4bb2c09cafda0942b62fb8e1414e90820e18fa0
Shader 'MotionVectorsShaderRD' (group 0) SHA256: cbf3cbdcba0d0a2026c9fbf248556f1acd11beacc38a2e8c5ce7009ee49a1560
Shader 'LuminanceReduceRasterShaderRD' (group 0) SHA256: 3ccd96a23701d47b6b28640ac3624f391cf503bff4453adcf9486ce1f753c572
Shader 'TonemapShaderRD' (group 0) SHA256: 1c4748b3de350503048a1f9eca4f1dc2b308086460692ea0a81bababfd80542a
Shader 'VrsShaderRD' (group 0) SHA256: def705023965d273a669c1ac6acfd7494138bde25b3e3bde0969c3c7a32c3aae
Shader 'BlitShaderRD' (group 0) SHA256: 09b63e5347ccb6779fd79e54b093cfc915ec80510efa1f613c9ada9ff2e0f70d
PulseAudio 15.99.0 detected.
PulseAudio: context other
PulseAudio: context other
PulseAudio: context other
PulseAudio: context ready
PulseAudio: Detecting channels for device: alsa_output.pci-0000_01_00.1.hdmi-stereo-extra1
PulseAudio: detected 2 output channels
PulseAudio: audio buffer frames: 512 calculated output latency: 11ms
Using present mode: Enabled
TextServer: Primary interface set to: "ICU / HarfBuzz / Graphite (Built-in)".
[jsb][Verbose] v8 version: <IP_ADDRESS>
[jsb][Verbose] EditorSettings is not available when initialising jsb::internal::Settings
[JSDebugger][Debug] devtools://devtools/bundled/inspector.html?v8only=true&ws=<IP_ADDRESS>:9229/1
[jsb][Verbose] add search path: res://.godot/GodotJS
[jsb][Verbose] add search path: res://
[jsb][Verbose] add search path: res://node_modules
CORE API HASH:<PHONE_NUMBER>
EDITOR API HASH: 444927587
[jsb][Verbose] checked file path res://.godot/GodotJS/src/__assets_promise_loader.js
[jsb][Verbose] instantiating module res://.godot/GodotJS/src/__assets_promise_loader.js
[jsb][Verbose] load main module res://.godot/GodotJS/src/__assets_promise_loader.js
[jsb][Log] [EXPERIMENTAL] res://.godot/GodotJS/src/__assets_promise_loader.js script: 64962 inherits super: 0 native: 59138
[jsb][Verbose] create instance<PHONE_NUMBER>0960 of Node(64962)
[jsb][Verbose] cross binding from C++. Node(59138)
Loaded system CA certificates
[jsb][Verbose] checked file path res://.godot/GodotJS/src/loader.js
[jsb][Verbose] instantiating module res://.godot/GodotJS/src/loader.js
[jsb][Verbose] checked file path res://.godot/GodotJS/src/__utils.js
[jsb][Verbose] instantiating module res://.godot/GodotJS/src/__utils.js
[jsb][Log] [EXPERIMENTAL] res://.godot/GodotJS/src/loader.js script: 64898 inherits super: 0 native: 59010
[jsb][Verbose] create instance<PHONE_NUMBER>9280 of Control(64898)
[jsb][Verbose] cross binding from C++. Control(59010)
Using present mode: Enabled
ERROR: multi-threaded call not supported yet
at: check_internal_state (modules/GodotJS/bridge/jsb_environment.h:277)
ERROR: multi-threaded call not supported yet
at: check_internal_state (modules/GodotJS/bridge/jsb_environment.h:277)

godot.log
I don't use anything extra I have a clean build of godot 4.3. I build the editor like this:
scons platform=linuxbsd target=editor

I tried more platforms but still can't reproduce this problem (both on macos and linux mint 22, with godot branch 4.3 and tag 4.3-stable). However, it must be triggered by GodotJSScript::ensure_module_loaded() unexpectedly from somewhere.
Can you debug from source via VSCode (or other IDE/debugger you have) to get the exact stacktrace of this assertion failure?
For VSCode, this godot docs may help. And for convenience,  here is my config to debug in VSCode on Linux Mint:
tasks.json
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "build",
            "group": "build",
            "type": "shell",
            "command": "scons",
            "args": [
              "p=linuxbsd",
              // enable this if v8 not available
              // "use_quickjs=yes",
              "compiledb=yes",
              "dev_build=yes",
              "target=editor"
            ],
            "problemMatcher": "$msCompile"
          }
    ]
}

launch.json
{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "lldb",
            "request": "launch",
            "name": "CodeLLDB launch",
            // path to your built godot executable file
            "program": "${workspaceFolder}/bin/godot.linuxbsd.editor.dev.x86_64",
            "args": [
                "res://main.tscn",
                "--rendering-driver", "opengl3",
                "--path",
                "!!!FULL_PATH_TO_YOUR_PROJECT!!!",
                "--verbose"
            ],
            "cwd": "!!!FULL_PATH_TO_YOUR_PROJECT!!!",
            "externalConsole": false,
            "preLaunchTask": "build"
        }
    ]
}

The exact Call Stack is available in Debug in VSCode on the breakpoint of the assertion failure triggered.

I don't understand anything... I built as you have, I added a config for debug, I started godot to test and it worked, I checked on my old build also works, it somehow fixed itself, I'll try to look for something else, maybe I missed something.


Terms that include Slash Character

Terms that include a slash "/" in them return "Not Found" results. Some examples are:
https://yamz.link/term/alternates/Deglaciation/glacial termination
https://yamz.link/term/alternates/Alas/alass
https://yamz.link/term/alternates/Ablation area/zone
I attempted a general search using / and "/" which yielded no results; they might need to be located manually within the database.

Interestingly, "Strip/Patch" https://yamz.link/term/ark/h6719 provides a definition, probably due to PID


Yields invalid spec with operations null

The current version master and v1.5.3-M1 both return operations that are null. This is not a valid spec as discussed here https://github.com/swagger-api/swagger-js/issues/268 and thus swagger-ui fails to parse the returned json.

I've created a pull request that I hope will fix this.
https://github.com/swagger-api/swagger-core/pull/1010
Sadly, I'm not able to run the tests as they seem to fail on the master branch.

As you can see on the pull request, this is not an issue with the code but with the documentation, so I'm closing it.


header ui update closes #3263

Summary
Commit 1:
Removes the LogoTile from the AppBar
Commit 2:
Adds a SearchBar component with an optional renderEnd parameter.
The design was inherited from existing CollectionSearch component and extended.
Test plan
Snapshot of the newly added component with renderEnd enabled

Note
Some changes on the AppBar component are pending and will be done soon.

@austincondiff Please review the PR.


Table in new tab for selected genes subnetwork

Pretty much what it says on the tin. I just like having things to check off.

#22 implements this!


bug: nova-post job crashloop

Is this a bug report or feature request? (choose one):

Kubernetes Version (output of kubectl version):
1.5.2
Helm Client and Tiller Versions (output of helm version):
2.1.3
Development or Deployment Environment?:
development
Release Tag or Master:
master
Expected Behavior:
nova jobs run to completion
What Actually Happened:
nova-post is stuck in a crashloop
How to Reproduce the Issue (as minimally as possible):
Any Additional Comments:
Logs:
$ kubectl logs nova-post-1qnf7
+ export HOME=/tmp
+ HOME=/tmp
+ ansible localhost -vvv -m kolla_keystone_service -a 'service_name=nova service_type=compute description='\''Openstack Compute'\'' endpoint_region=RegionOne url='\''http://nova-api.default:8774/v2/%(tenant_id)s'\'' interface=admin region_name=RegionOne auth='\''{'\''auth_url'\'':'\'''\'', '\''username'\'':'\''admin'\'','\''password'\'':'\''password'\'','\''project_name'\'':'\''admin'\'','\''domain_name'\'':'\''default'\''}'\''' -e '{'\''openstack_nova_auth'\'':{'\''auth_url'\'':'\'''\'', '\''username'\'':'\''admin'\'','\''password'\'':'\''password'\'','\''project_name'\'':'\''admin'\'','\''domain_name'\'':'\''default'\''}}'
No config file found; using defaults
<localhost> ESTABLISH LOCAL CONNECTION FOR USER: ansible
<localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1489081561.39-206444123242715 `" && echo ansible-tmp-1489081561.39-206444123242715="` echo $HOME/.ansible/tmp/ansible-tmp-1489081561.39-206444123242715 `" ) && sleep 0'
<localhost> PUT /tmp/tmpKEGlqA TO /tmp/.ansible/tmp/ansible-tmp-1489081561.39-206444123242715/kolla_keystone_service
<localhost> EXEC /bin/sh -c 'LANG=en_US.UTF-8 LC_ALL=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 /usr/bin/python /tmp/.ansible/tmp/ansible-tmp-1489081561.39-206444123242715/kolla_keystone_service; rm -rf "/tmp/.ansible/tmp/ansible-tmp-1489081561.39-206444123242715/" > /dev/null 2>&1 && sleep 0'
localhost | FAILED! => {
    "changed": true,
    "failed": true,
    "invocation": {
        "module_args": {
            "api_timeout": null,
            "auth": {
                "auth_url": "",
                "domain_name": "default",
                "password": "password",
                "project_name": "admin",
                "username": "admin"
            },
            "auth_type": null,
            "availability_zone": null,
            "cacert": null,
            "cert": null,
            "cloud": null,
            "endpoint_type": "public",
            "key": null,
            "region_name": "RegionOne",
            "timeout": 180,
            "verify": true,
            "wait": true
        },
        "module_name": "kolla_keystone_service"
    },
    "msg": "'Traceback (most recent call last):\\n  File \"/tmp/ansible_oSM3Lj/ansible_module_kolla_keystone_service.py\", line 55, in main\\n    for _service in cloud.keystone_client.services.list():\\n  File \"/usr/local/lib/python2.7/dist-packages/shade/openstackcloud.py\", line 292, in keystone_client\\n    \\'identity\\', keystoneclient.client.Client)\\n  File \"/usr/local/lib/python2.7/dist-packages/shade/openstackcloud.py\", line 258, in _get_client\\n    **kwargs)\\n  File \"/usr/local/lib/python2.7/dist-packages/os_client_config/cloud_config.py\", line 304, in get_legacy_client\\n    endpoint = self.get_session_endpoint(service_key)\\n  File \"/usr/local/lib/python2.7/dist-packages/os_client_config/cloud_config.py\", line 245, in get_session_endpoint\\n    session = self.get_session()\\n  File \"/usr/local/lib/python2.7/dist-packages/os_client_config/cloud_config.py\", line 188, in get_session\\n    \"Problem with auth parameters\")\\nOpenStackConfigException: Problem with auth parameters\\n'"

The logs indicate that the auth url is returning empty, so the ansible tasks to authenticate with keystone are failing.  This is failing because of how helm-toolkit handles looking up the various URI's for the services.  We can see the difference in a service that works, like cinder for example.  Because nova's structure differently, the URI look ups fail.  I can handle the reorganization here if desired.  Should be an easy enough fix to test out.

Should have read "because novas endpoint values in values.yaml are named differently".  I'm not sure if we mention this in the docs, but would be a good piece to add to your docs tidying up and getting the community on the same page @v1k0d3n

looks like @intlabs pull request for nova endpoints will fix this.
https://github.com/att-comdev/openstack-helm/compare/master...portdirect:0.2.ß/ks-endpoint-normalization-nova

@larryrensing Yeah, it will.  We can go ahead and close this out


CookieFilter

The cookie filter can be used to keep track of all the cookies sent by the server and use them in subsequent requests. It might come in handy when more than just the SessionFilter is needed.

Lol, I just realized that my test is wrong... will update PR

Nice initiative, I'm sure this could be handy as well. Thanks for the PR.


Verify BLE calls can be made within callbacks

While messing around with my ble113-ota project, I was running into issues writing to the BLE stack inside a BLE callback, might have been an oversight, might have been nothing.
Needs to be verified/fixed.

Most of this will be handled by ensuring all BLE stack calls are on the main thread (which I believe they are)

Not an issue here - all calls happen on the main thread via a handler. Ditto for when the queue system comes out.


Add curly brackets to mutation example for TypeScript error

This adds curly brackets to the arrow function which "disables" the implicit return value for TypeScript users, who see an error for this example.
CodeSandbox, which shows the error:

https://codesandbox.io/s/laughing-chaplygin-u1mdr?file=/src/App.tsx

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: