Fix White space (bottom right of Application Tab)

When I use WinUtil in dark mode I always get a small offcolored rectangle on the bottom right of the toolbox. I did following things to fix it:

created rectangle, color it with backgroundcolor and place it at the blank space.
added xName to Application ScrollViewer to get the state of it's scrollbars
added style for rectangle that triggers it to show if both scrollbars are visible

Before:

After:

bc of the trigger the rectangle will not show if not needed so it won't brake anything else.

The file you just edited it's auto generated. You should be looking other files that contains the code

The file you just edited it's auto generated. You should be looking other files that contains the code

It actually isn't an auto generated file, you can look at these lines of code inside the Compile.ps1 script, which in the firs 2 lines of the ones I've referenced, you'll notice that input.xaml is actually used to determine how will the GUI will look/behave.
Hope this provides some clarity on this subject, and if you have any questions in mind, feel free to ask them here, or more preferably through GitHub's discussions feature.

This is called don't get too outdated in winutil moment XDDD


FAIL: test_infix_repr

Hello Wassim, amazing work you are doing here!
I've followed the installation instructions of the README, and I'm getting the following failed test when running python -m unittest discover -p "*UnitTest.py" :
FAIL: test_infix_repr (physo.physym.tests.program_display_UnitTest.DisplayTest)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/user/PhySO/physo/physym/tests/program_display_UnitTest.py", line 77, in test_infix_repr
    self.assertTrue(works_bool)
AssertionError: False is not true

----------------------------------------------------------------------
Ran 70 tests in 27.472s

FAILED (failures=1)

Any idea how I can fix this?
Running on Pop OS 22.04
Cheers!

Hi @franfram,
This is probably  due to latex not being installed / available on your system.
I am working on instructions for how to do that properly on every system.
In the meantime, you can check out #16 and #21 ! ;)
Cheers.
Wassim

Thanks @WassimTenachi !


chore(tutorial): remove dead link to pilot.orca

This file is now gone from the examples directory so I'm cleaning out the old link.

thanks :)


Update bridge function in  IOptimismMintableERC20.sol

bridge() function is currently only set to  external, we can minimize gas costs by also setting it to view as it is a read-only function.

@FortisFortuna just wondering if you'd be able to review this and let me know what you think. Thanks!


Update CMakeLists.txt

libmkldnn.so does not exist.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@FunnyWii Which inference library did you download? It looks like the latest paddle inference library does not contain libdnnl.so.3

@FunnyWii Which inference library did you download? It looks like the latest paddle inference library does not contain libdnnl.so.3

https://www.paddlepaddle.org.cn/inference/master/guides/install/download_lib.html#linux
In the master branch, I use CUDA12.0/cuDNN8.9/TensorRT8.6 version

@FunnyWii Which inference library did you download? It looks like the latest paddle inference library does not contain libdnnl.so.3

直接拉下来的Paddle3D仓库中，没有找到 set(MKLDNN_LIB ${MKLDNN_PATH}/lib/libmkldnn.so.0)对应的.so文件，我修改了之后在本地可以编译通过


Run pest via sail when configured

This PR adds support for running Pest test suites via Laravel Sail automatically.
Sail is already detected for PHPUnit testsuites. This uses the same mechanism.
Make sure these boxes are checked before submitting your pull request:

[x] Add fixtures and spec when implementing or updating a test runner
[x] Update the README accordingly
[x] Update the Vim documentation in doc/test.txt

I have not updated the readme or docs as this feels more like an enhancement than a feature worth documenting.

Thank you!


Uncaught ReferenceError: instafeedCachexXxXxX is not defined

Hi @stevenschobert,
looking at Chrome v34.0.1847.132 console, I see the above error many times. Same unique identifier after instafeedCache. It seems to get logged in console randomly after a call to instafeed_obj.next() method.
Uncaught ReferenceError: instafeedCache4cb3eb627384a2a5 is not defined
I've developed an infinite scroll wallpaper of instagram thumbs filterd by tag. Everything works as expected (despite Instagram server 503s due to limited capacity), nevertheless that Uncaught ReferenceError makes me wonder.
You can have a look at this demo with development tags and hit F12 while scrolling down:
www.raccontareilfoodinrete.it
Any clues? Thanks.
btw great plugin! :+1:
Cheers,
Luca

Hi,
I have the same problem, but I´m using a basic script.
function instagram() {
    var feed = new Instafeed({
        get: 'user',
        userId: 'xxx',
        limit: 9,
        sortBy: 'most-recent',
        clientId: 'xxx'
    });
    feed.run();
}
instagram();

The first time that I load the page is OK, but when I refresh the page, I'm getting this same error.


[Bug] Copy annotation from stack viewport to another stack viewport(s) with different series (for Time-intensity curves)

Describe the Bug
I want to copy my annotations EllipticalROI from active viewport and dublicate it to another viewports. And then calculate MEAN property from all (Time-intensity curves).
Series in this viewports different, but FrameOfReferenceUID equal.
from

to

i use cornerstoneTools.state.annotation.getAnnotations() method, and then replace info at metadata such as annotationUID, FrameOfReferenceUID, referencedImageId (from viewport currentImageIndex and imageIds array) but it not work
Can you create new method "copyAnnotation" for this issue?
Steps to Reproduce

open 2 (and more) stack viewports with different series
at first viewport draw ellipse
try to use addAnnotation for another viewports
nothing happened

The current behavior
ellipses after addAnnotation NOT appear to another viewports.
i use cornerstoneTools.state.annotation.getAnnotations() method, and then replace info at metadata such as annotationUID, FrameOfReferenceUID, referencedImageId (from viewport currentImageIndex and imageIds array) but it not work
Can you create new method "copyAnnotation" for this issue?
The expected behavior
ellipses after addAnnotation appear to another viewports
OS
macos sonoma 14.0
Node version
16.20.2
Browser
124.0.6367.209

@sedghi

Fir these type of use cases you need to use the volume viewport

@sedghi how volume viewport can help with programatically create annotations?
annotations state from first viewport can be copied to another viewports as is i wrote if viewports type a volume?

You can take a look at this example which shows how to programmatically add annotations: https://www.cornerstonejs.org/live-examples/dynamicallyaddannotations. Additionally, there is a guide available here: https://docs.ohif.org/faq/technical#how-to-dynamically-load-a-measurement.

@sedghi thank you. I looked at the first link, but unfortunately the example is not working in the error console

This works for me

@sedghi right, now it works, thanks!
is the way do this for EllipticalROITool (at example i seen LenghtTool)?
is exist any docs?

It is really the same thing, if you look at the example you will see


Update Publish to IIS doc to react to VS2017 updates and IIS publishi…

Fixes #2682
I think the only thing we really need to do here is surface the new content in that new topic, which has all the juicy details. That comma splice in the title is killing me :smile:, but this should do the trick. We can leave the current image in place for importing a profile, since that's still relevant and the lowest bar to cross when a pub profile is available.

@guardrex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


⚖ Register Validator: CroutonDigital

Network Choice
dentrite-1
Who are you?
CroutonDigital is a professional validator since 2021 and has a EU license for crypto operations, we have 18 like-minded people on the team that are dedicated to achieve our targets. Our core team is located in our head office in Latvia, and some team members are located abroad (Asia, Canada), so we can cover most of the timezones without difficulties, as you know crypto never sleeps, so do we. Also we have rich infrastructure in different parts of the world, so we can cover any project needs about decentralization
Delegator address
axone1hzcar26aqp4u5mkaanyxxwatn6qtpce4sw8e4w
gentx
{
  "body": {
    "messages": [
      {
        "@type": "/cosmos.staking.v1beta1.MsgCreateValidator",
        "description": {
          "moniker": "CroutonDigital",
          "identity": "47B453B80ECFA342",
          "website": "https:/crouton.digital",
          "security_contact"<EMAIL_ADDRESS>          "details": "Your everyday crypto partner"
        },
        "commission": {
          "rate": "0.050000000000000000",
          "max_rate": "0.200000000000000000",
          "max_change_rate": "0.010000000000000000"
        },
        "min_self_delegation": "1",
        "delegator_address": "",
        "validator_address": "axonevaloper1hzcar26aqp4u5mkaanyxxwatn6qtpce4qmtt0v",
        "pubkey": {
          "@type": "/cosmos.crypto.ed25519.PubKey",
          "key": "6YhyuuvSpUUjjY29JU/E4/0SX+v2KIzVvi6tCV/3cIA="
        },
        "value": {
          "denom": "uaxone",
          "amount": "1000000000000"
        }
      }
    ],
    "memo": "fd68345e1d97873148b081d8963834998a9f7e3c@<IP_ADDRESS>:26656",
    "timeout_height": "0",
    "extension_options": [],
    "non_critical_extension_options": []
  },
  "auth_info": {
    "signer_infos": [
      {
        "public_key": {
          "@type": "/cosmos.crypto.secp256k1.PubKey",
          "key": "ApNcJnhyVGRyjXwtEPS930BEBnhvX/ynUxJlJSIe44n6"
        },
        "mode_info": {
          "single": {
            "mode": "SIGN_MODE_DIRECT"
          }
        },
        "sequence": "0"
      }
    ],
    "fee": {
      "amount": [],
      "gas_limit": "200000",
      "payer": "",
      "granter": ""
    },
    "tip": null
  },
  "signatures": [
    "RvKODGppZOBWX9/9q2ZqK8euM738VlTCTDyISogRoDdPTQCB/8jgpkFK7XtdtU4OPnrZVpl5Us2kEUImUboebg=="
  ]
}

😉 Here is the corresponding PR: https://github.com/axone-protocol/networks/pull/813


MWPW-132277 - Breakpoint content for Quiz Results

Add breakpoints classes in order to allow Authoring add device specific content. Results might will show different parts of content for mobile, tablet or desktop.

Resolves: MWPW-132277
Test URLs:

Before: https://uar-integration--milo--adobecom.hlx.page/drafts/borges/end-to-end/results?primary=express-edu&quizKey=cc-quiz-en-US
After: https://breakpoint-content--milo--elaineskpt.hlx.page/drafts/borges/end-to-end/results?primary=express-edu&quizKey=cc-quiz-en-US

@elaineskpt Can you fix this linting error:
223:3   error    React Hook "useEffect" is called conditionally. React Hooks must be called in the exact same order in every component render. Did you accidentally call a React Hook after an early return?                                     react-hooks/rules-of-hooks

and the unit test failures?
Once that's done we can merge.

@elaineskpt I didn't see that there are no js changes, so failures are not due to this PR.  Let's create a followup PR to address those failures in the uar-integration branch.

@elaineskpt I didn't see that there are no js changes, so failures are not due to this PR. Let's create a followup PR to address those failures in the uar-integration branch.

Hi @chrischrischris. We have these stories logged to specifically deal with unit tests: MWPW-133119 and MWPW-134984


feat(button): add github funding button

Signed-off-by: Felipe Zipitria<EMAIL_ADDRESS>

Thank you for this link at the right place.


Hi, I have stumbled upon this thing on Twitter.

But I have a question, can it decline biased content, like declining making any malware, inappropriate content, and other biased content, I’m curious

Yes, it uses OpenAI's moderation endpoint to decline nefarious requests.


GEODE-6827: Make windows not gate for Benchmark

Make the Windows tests not gating for Benchmark job, since benchmark is
run on Linux.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

it would also be nice to add a Benchmarks group that shows only Build, the jobs that are gating for benchmarks, and Benchmarks.  It's really hard to see it clearly in the complete view.

it would also be nice to add a Benchmarks group that shows only Build, the jobs that are gating for benchmarks, and Benchmarks. It's really hard to see it clearly in the complete view.

This might be a useful change to the pipeline, but it isn't part of the issue being addressed here. If you would like to see it done, please submit an issue!

Put the test.PLATFORM back. Comparing magic strings like startswith('windows') is not more informative

This might be a useful change to the pipeline, but it isn't part of the issue being addressed here. If you would like to see it done, please submit an issue!


[APIView GPT] "Generate AI Review" fails and provides no info

This makes it impossible to understand what went wrong. Since this is the staging site, it would be helpful to display the actual error.

Resolved and deployed


vukano-shader interpretes bool in glsl as u32 in rust

Hi,
I don't know if this is expected, but I have a struct:
layout(set = 2, binding = 0) uniform TextureUsageInfo {
  bool b_albedo;
  bool b_normal;
  bool b_metal;
  bool b_roughness;
  bool b_occlusion;
  bool b_emissive;
} u_tex_usage_info;

When I access it in my rust program via:
pbr_fragment::ty::TextureUsageInfo{
  b_albedo: true,
  b_normal: true,
  b_metal: true,
  b_roughness: true,
  b_occlusion: true,
  b_emissive: true,
}

The rustc/cargo complains:
error[E0308]: mismatched types
   --> src/core/resources/material.rs:117:21
    |
117 |                     false
    |                     ^^^^^ expected u32, found bool

Is this expected? I mean I can use a "if not 0 interpret as true " approach. But I just wanted to be sure it's not a problem on my side.
-siebencorgie

SPIR-V doesn't allow booleans in structs with external visibility.
What happens here I think is that the GLSL compiler automatically turns booleans into u32s. Therefore this is beyond my control.

Ah, good to know. So I take the "if not 0" approach.
Thanks!


fix typos

Great article Prashant - I like the step by step explanation with a view of the data at each step, makes it really easy to follow along!
I just saw some small typos that I thought you might want to fix :smiley:

Thanks man for pointing out the errors.


Cluster Stats API,  Fix json tag for nodes.count

Small fix.

@tutuming Oops. Thanks. Will be part of the next release.

Will be fixed later this evening when I release a new version. Thanks for reporting and fixing.


Zoneminder  component failure on start

**Home Assistant release with the issue: **
0.88.2

Last working Home Assistant release (if known):
HA 0.79, ZM 1.30
**Operating environment (Hass.io/Docker/Windows/etc.): **
Raspberry PI 3, Ubuntu 16.04,  venv pip

**Component/platform: **
Zoneminder
https://www.home-assistant.io/components/zoneminder/

Description of problem:
Zoneminder component fails at the initialization phase
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
zoneminder:
  host: <IP_ADDRESS>
  username: ""
  password: ""
  ssl: false
  verify_ssl: false
  path: '/zm/'

**Traceback (if applicable):
zm_error.log
ZM is accessible from internal subnet without user/password login.

**Additional information: worked for zm 1.30 and ha 0.79
After upgrading zm from 1.30 to 1.32 Zoneminder component won't start. Zoneminder itself works Ok. Full reboot both ZM and HA servers hasn't resolve the issue.

It looks like the issue ZM API, not HA


I updated my graphics driver

My present driver is GeForce Game Ready 536.67, release date 07/18/2023, after the update, it'll only output a 0-second .flac file after inference.

I restored my system to the time before I updated my driver and the problem isn't solved. So apparently it's not the driver's problem


Make imports work for nested addons and engines

This is a due to the discussion here : https://github.com/ember-cli/ember-cli/issues/3718

Wow. That's quite the discussion.

This is available as 0.3.8 on npm

note i may release 0.3.9 with updated deps on bower; just need to do a quick test first


Errors should be written to stderr and info to stdout.

Added a macro that makes it easy to write to stderr.  Modified main to use this to write parsing errors.


Journal notes front matter title breaks if you change value of journal:dateFormat

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[ ] Views.  Dendron Preview, Tree View, Side Panels in the UI
[X] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[X] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features

Describe the bug
In dendron.yml, the default setting for journal:dateFormat is y.MM.dd
If you change this, when a journal note is created it reverts to giving the note a front matter title of whatever is after the last . in the hierarchy. This is probably not what was intended.
For example:
I wanted to append the day of the week to the file name for a daily note as in my use case it was useful to me when navigating a list of daily note files. I changed journal:dateFormat to y.MM.dd.ccc which gives a file name of e.g. daily.journal.2022.04.27.Wed
The problem is, this then gives the note a title of 'Wed' rather than '2022-04-27-Wed'
Looking at the code in dnode.ts starting at:
https://github.com/dendronhq/dendron/blob/110706444ff10bcca1bcc56414dd1faa1859a637/packages/common-all/src/dnode.ts#L679
It seems that the match function only expects y.MM.dd to occur at the end of the line:
https://github.com/dendronhq/dendron/blob/110706444ff10bcca1bcc56414dd1faa1859a637/packages/common-all/src/dnode.ts#L687
So in my case, with 'Wed' on the end of the line the code resorts to issuing a normTitle.
I'm no developer so I don't know the ramifications of implementing the match function to take account of what is set for journal:dateFormat in dendron.yml or even if it is appropriate.
But it would be nice if it did and perhaps a note somewhere that points out that the daily note schema will have to be changed depending on the choice of journal:dateFormat.
To Reproduce
See above
Expected behavior
See above
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)

OS: [e.g. iOS] MacOS
Browser (if with published websites; include version): [e.g. chrome, safari]
Versions (all that apply to bug): Latest (see link to code above in GitHub)

Dendron Extension:
VS Code version:
Dendron CLI:

Additional context
This is the first time I've issued a bug report on GitHub, so if anything is wrong in my submission please let me know.
Dendron Log file
Please attach the output of > Dendron:Dev: Open Logs here

Thank you for the catch. We'll keep track of this and let you know when a fix gets pushed 🙏🏼

Hi @harrijer a possible workaround before the fix comes out could be updating your journal config to:
   journal:
        dailyDomain: ''
        name: daily.journal
        dateFormat: y.MM.dd.ccc
        addBehavior: asOwnDomain

and using Dendron: Create Journal Note (keyboard hotkey: ctrl+shift+j) command.


Datasources are unable to retrieve their values

Hi!
I tried to debug for https://github.com/ilijamt/terraform-provider-awx/issues/117 and ran into the following error on AWX 24.6.1:
│ Error: Unable to read resource for CredentialType on /api/v2/credential_types/?name__exact=HashiCorp%20Vault%20Signed%20SSH
│
│   with data.awx_credential_type.hashicorp-vault-signed-ssh,
│   on main.tf line 57, in data "awx_credential_type" "hashicorp-vault-signed-ssh":
│   57: data "awx_credential_type" "hashicorp-vault-signed-ssh" {
│
│ invalid status code: 401, on
│ /api/v2/credential_types/?name__exact=HashiCorp%20Vault%20Signed%20SSH with
│ {"detail":"Authentication credentials were not provided. To establish a
│ login session, visit /api/login/."}

Resources are working fine, but Datasources are unable to retrieve their current values due to an authentication error. This also happens with the current main.

Any datasources?


Taffybar/Haskell GI packages broken

Nix/NixOS users have been complaining that the taffybar haskell package seems to be broken in the latest versions of nixpkgs. It seems that this breakage is due to the fact that old versions of haskell-gi and packages generated from it are on old versions.
I've written an overlay, that bumps the relevant packages to the versions needed to make everything work here:
https://github.com/taffybar/taffybar/blob/b3ca25b0f6656f2da97c8701247519f9300a28c3/environment.nix#L17
What needs to be done to bump the versions of those packages in haskellPackages. @peti

Nixpkgs follows the version recommendations from LTS Haskell 13.x [1]. Ignoring those recommendations to fix taffybar may have the unintended consequence of breaking (possibly many) other packages that rely on this environment. The list of changes taffybar seems to need looks substantial. I don't think we can realistically update all those packages. IMHO, the best solution would be if taffybar would be a part of the LTS package set -- then it would be pretty much guaranteed that it compiles in Nixpkgs (and many others that rely on LTS). I'm not sure how to go forward with this. I suppose we could add an overrideScope for taffybar specifically that contains those version in a local build scope. It's vetry unpleasant (and brittle) to maintain that kind of override, but it would probably work.
[1] https://www.stackage.org/

@peti How are versions for hackage packages that do not appear in stackage selected?Is the latest version simply always used?
Seems like a good possible short term solution might be to simply use a slightly older version of taffybar (e.g. 3.1.2) which did seem to work with the previous package set.
We would need to do the same with a few broken haskell-gi packages. I imagine that this won't work if there is no way to use older versions of packages that are outside of stackage.

How are versions for hackage packages that do not appear in stackage selected?Is the latest version simply always used?

Yes. The latest version is always included in Nixpkgs, and for non-Stackage packages that is also the default version.

Seems like a good possible short term solution might be to simply use a slightly older version of taffybar (e.g. 3.1.2) which did seem to work with the previous package set.

Yes, that seems like a good idea.

Yes. The latest version is always included in Nixpkgs, and for non-Stackage packages that is also the default version.

Yes, that seems like a good idea.

It's not clear to me from this comment whether it is possible/normal to use an old version of a package (not included in stackage) in nixpkgs because the first comment seems to indicate that the answer is no but the second seems to indicate the answer is yes. Can you clarify?
In any case, I have opened https://github.com/commercialhaskell/stackage/pull/4630 to get taffybar in to stackage, but that will only work once stackage moves their the version of haskell-gi to 0.22.6 in lts which is likely to be a while, I think.
That is obviously the long term fix, but I would like to resolve this before then because this breakage seems to be causing quite a bit of confusion.

I suppose we could add an overrideScope for taffybar specifically that contains those version in a local build scope. It's very unpleasant (and brittle) to maintain that kind of override, but it would probably work.

I am also open to volunteer to help maintain this, though as I understand it all of the haskell stuff goes through you so I might not be able to actually do all that much.
I am already maintaining the an overlay over the current nixpkgs that does work though, so you should be able to lift all the version numbers from there if we do go that route https://github.com/taffybar/taffybar/blob/b3ca25b0f6656f2da97c8701247519f9300a28c3/environment.nix#L17

It's not clear to me from this comment whether it is possible/normal to use an old version of a package (not included in stackage) in nixpkgs because the first comment seems to indicate that the answer is no but the second seems to indicate the answer is yes.

Yes, of course it is possible. Just add the appropriate version spec to https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/haskell-modules/configuration-hackage2nix.yaml#L45.

Closed in #79735

Seems like it's broken again, because gi-pango fails to build (see here - possibly due to harfbuzz updates). Upgrading gi-pango to the version based on haskell-gi-base 0.24 fixes it, but it needs a whole load of other stuff to change too; my overlay:
self: super:
{
  haskellPackages = with self.haskell.lib; super.haskellPackages.extend (hself: hsuper: {
    gi-atk = hself.gi-atk_2_0_22;
    gi-cairo = hself.gi-cairo_1_0_24;
    gi-cairo-render = overrideCabal (hsuper.gi-cairo-render) (drv: {
      src = self.fetchFromGitHub {
        owner = "thestr4ng3r";
        repo = "gi-cairo-render";
        rev = "8727c43cdf91aeedffc9cb4c5575f56660a86399";
        sha256 = "16kqh2ck0dad1l4m6q9xs5jqj9q0vgpqrzb2dc90jk8xwslmmhxd";
      };
      editedCabalFile = null;
      postUnpack = ''
        mv source all
        mv all/gi-cairo-render source
      '';
    });
    gi-dbusmenu = hself.gi-dbusmenu_0_4_8;
    gi-dbusmenugtk3 = hself.gi-dbusmenugtk3_0_4_9;
    gi-gdk = overrideSrc hsuper.gi-gdk {
      src = self.fetchurl {
        url = "https://hackage.haskell.org/package/gi-gdk-3.0.23/gi-gdk-3.0.23.tar.gz";
        sha256 = "18v3kb6kmryymmrz0d88nf25priwyh3yzh7raghc5ph2rv7n4w8m";
      };
      version = "3.0.23";
    };
    gi-gdkpixbuf = hself.gi-gdkpixbuf_2_0_24;
    gi-gdkx11 = overrideSrc hsuper.gi-gdkx11 {
      src = self.fetchurl {
        url = "https://hackage.haskell.org/package/gi-gdkx11-3.0.10/gi-gdkx11-3.0.10.tar.gz";
        sha256 = "0kfn4l5jqhllz514zw5cxf7181ybb5c11r680nwhr99b97yy0q9f";
      };
      version = "3.0.10";
    };
    gi-gio = hself.gi-gio_2_0_27;
    gi-glib = hself.gi-glib_2_0_24;
    gi-gobject = hself.gi-gobject_2_0_24;
    gi-gtk = overrideSrc hsuper.gi-gtk {
      src = self.fetchurl {
        url = "https://hackage.haskell.org/package/gi-gtk-3.0.36/gi-gtk-3.0.36.tar.gz";
        sha256 = "0bzb3xrax5k5r5fd6vv4by6hprmk77qrqr9mqn3dxqm6an8jwjn9";
      };
      version = "3.0.36";
    };
    gi-gtk-hs = hself.gi-gtk-hs_0_3_9;
    gi-pango = hself.gi-pango_1_0_23;
    gi-xlib = hself.gi-xlib_2_0_9;
    haskell-gi = hself.haskell-gi_0_24_3;
    haskell-gi-base = addBuildDepend hself.haskell-gi-base_0_24_2 self.gobject-introspection;
    taffybar = appendPatch hsuper.taffybar (self.fetchpatch {
      url = "https://github.com/taffybar/taffybar/pull/494/commits/a7443324a549617f04d49c6dfeaf53f945dc2b98.patch";
      sha256 = "0prskimfpapgncwc8si51lf0zxkkdghn33y3ysjky9a82dsbhcqi";
    });
  });
}

By the way, both times when I've had to bump haskell package versions, say for a package X from version 0.1.1 to 0.1.2, I end up in a situation where there's nix expression X and X_0_1_2, and X_0_1_2 actually doesn't build because none of its dependencies are up-to-date, and I have to manually go up the dependency tree to bump versions too (like here). It seems to be possible in principle to avoid this when generating hackage-packages.nix.
The expression for gi-cairo-render could probably be made neater with some form of appendPatch/overrideCabal, but overrideCabal complains if you set patchFlags (necessary because the repository https://github.com/taffybar/gi-cairo-render/ contains two packages, and the patch https://github.com/taffybar/gi-cairo-render/pull/1 is relative to this directory) - actually, this patch doesn't apply cleanly to master anyway...

I can confirm this issue. The overlay pasted above solves the problem for me too.

@maralorn merged a PR that gets gi-pango working (along with a bunch of related gi-* packages):
https://github.com/NixOS/nixpkgs/pull/95434/files
It may be easier to get Taffybar working now with this PR merged in.

Also, note that the branch off date for 20.09 is approaching, so if you're interested in Taffybar working in the next release, I'd recommend sending a PR for this over the next week or two:
https://github.com/NixOS/nixpkgs/issues/95535

Well, I profited mainly from the work done in this PR. I guess for taffybar to work there would only be 2 or 3 overrides missing. I only didn’t just include them because they were using source overrides were I would prefer an upstream fix/patch. But for getting it into 20.09 I would encourage a pragmatic solution over no solution.

New overlay in light of recent merges:
self: super:
{
  haskellPackages = with self.haskell.lib; super.haskellPackages.extend (hself: hsuper: {
    gi-cairo-render = overrideCabal (hsuper.gi-cairo-render) (drv: {
      src = self.fetchFromGitHub {
        owner = "thestr4ng3r";
        repo = "gi-cairo-render";
        rev = "8727c43cdf91aeedffc9cb4c5575f56660a86399";
        sha256 = "16kqh2ck0dad1l4m6q9xs5jqj9q0vgpqrzb2dc90jk8xwslmmhxd";
      };
      editedCabalFile = null;
      postUnpack = ''
        mv source all
        mv all/gi-cairo-render source
      '';
    });
    gi-dbusmenu = hself.gi-dbusmenu_0_4_8;
    gi-dbusmenugtk3 = hself.gi-dbusmenugtk3_0_4_9;
    gi-gdk = hself.gi-gdk_3_0_23;
    gi-gdkx11 = overrideSrc hsuper.gi-gdkx11 {
      src = self.fetchurl {
        url = "https://hackage.haskell.org/package/gi-gdkx11-3.0.10/gi-gdkx11-3.0.10.tar.gz";
        sha256 = "0kfn4l5jqhllz514zw5cxf7181ybb5c11r680nwhr99b97yy0q9f";
      };
      version = "3.0.10";
    };
    gi-gtk-hs = hself.gi-gtk-hs_0_3_9;
    gi-xlib = hself.gi-xlib_2_0_9;
    gtk-sni-tray = markUnbroken (hsuper.gtk-sni-tray);
    gtk-strut = markUnbroken (hsuper.gtk-strut);
    taffybar = markUnbroken (appendPatch hsuper.taffybar (self.fetchpatch {
      url = "https://github.com/taffybar/taffybar/pull/494/commits/a7443324a549617f04d49c6dfeaf53f945dc2b98.patch";
      sha256 = "0prskimfpapgncwc8si51lf0zxkkdghn33y3ysjky9a82dsbhcqi";
    }));
  });
}

So what needs to be done for this to make it into 20.09? I pulled some changes from @meck, and am able to build, but am still encountering issues with my xmonad-contrib override, and would love to see this fixed in-tree.
Thanks guys!

@evanjs a new version of gi-cairo-connector is needed

Here's my latest version of the overlay I'm using. It's basically the same as the last one, only a few more things get markUnbroken:
self: super:
{
  haskellPackages = with self.haskell.lib; super.haskellPackages.extend (hself: hsuper: {
    gi-cairo-connector = markUnbroken (hsuper.gi-cairo-connector);
    gi-cairo-render = markUnbroken (overrideCabal (hsuper.gi-cairo-render) (drv: {
      src = self.fetchFromGitHub {
        owner = "thestr4ng3r";
        repo = "gi-cairo-render";
        rev = "8727c43cdf91aeedffc9cb4c5575f56660a86399";
        sha256 = "16kqh2ck0dad1l4m6q9xs5jqj9q0vgpqrzb2dc90jk8xwslmmhxd";
      };
      editedCabalFile = null;
      postUnpack = ''
        mv source all
        mv all/gi-cairo-render source
      '';
    }));
    gi-dbusmenu = markUnbroken (hself.gi-dbusmenu_0_4_8);
    gi-dbusmenugtk3 = markUnbroken (hself.gi-dbusmenugtk3_0_4_9);
    gi-gdk = hself.gi-gdk_3_0_23;
    gi-gdkx11 = markUnbroken (overrideSrc hsuper.gi-gdkx11 {
      src = self.fetchurl {
        url = "https://hackage.haskell.org/package/gi-gdkx11-3.0.10/gi-gdkx11-3.0.10.tar.gz";
        sha256 = "0kfn4l5jqhllz514zw5cxf7181ybb5c11r680nwhr99b97yy0q9f";
      };
      version = "3.0.10";
    });
    gi-gtk-hs = markUnbroken (hself.gi-gtk-hs_0_3_9);
    gi-xlib = markUnbroken (hself.gi-xlib_2_0_9);
    taffybar = markUnbroken (appendPatch hsuper.taffybar (self.fetchpatch {
      url = "https://github.com/taffybar/taffybar/pull/494/commits/a7443324a549617f04d49c6dfeaf53f945dc2b98.patch";
      sha256 = "0prskimfpapgncwc8si51lf0zxkkdghn33y3ysjky9a82dsbhcqi";
    }));
    gtk-sni-tray = markUnbroken (hsuper.gtk-sni-tray);
    gtk-strut = markUnbroken (hsuper.gtk-strut);
  });
}

With respect to fixing this in-tree,  I think https://github.com/taffybar/taffybar/pull/494 and https://github.com/taffybar/gi-cairo-render/pull/1 need to be merged (cc @IvanMalison) - those are the patches that I apply in this overlay

Just wanted to share my config which is basically the same same with the following exceptions:
I'm currently using gi-cairo-render and gi-cairo-connector from the original repo, which was recently updated. I think the upstream https://github.com/cohomology/gi-cairo-render should probably be merged into the (AFAIK) hackage maintained https://github.com/taffybar/gi-cairo-render. Or probably as the upstream seems to be maintained again, use the original repo as hackage source?
Here are the different packages (gi-cairo-render and gi-cairo-connector) compared to @NickHu s config:
let
  gi-cairo-render-src = self.fetchFromGitHub {
    owner = "cohomology";
    repo = "gi-cairo-render";
    rev = "051de28ff092e0be0dc28612c6acb715a8bca846";
    sha256 = "1v9kdycc91hh5s41n2i1dw2x6lxp9s1lnnb3qj6vy107qv8i4p6s";
  };
in
{
  gi-cairo-render = markUnbroken (overrideCabal (hsuper.gi-cairo-render)
    (drv: {
      src = gi-cairo-render-src;
      editedCabalFile = null;
      postUnpack = ''
        mv source all
        mv all/gi-cairo-render source
      '';
    }));
  gi-cairo-connector = markUnbroken
    (overrideCabal (hsuper.gi-cairo-connector) (drv: {
      src = gi-cairo-render-src;
      editedCabalFile = null;
      postUnpack = ''
        mv source all
        mv all/gi-cairo-connector source
      '';
    }));
}

@Philipp-M @cohomology has been given access to the hackage package and has already done what you suggest, I believe

I recently merged a pull request from @thestr4ng3r, which makes gi-cairo-render buildable with haskell-gi >=0.24. The new version 0.1.0 of both gi-cairo-render and gi-cairo-connector are on hackage.

@barryfm

Although stackage lts-16.xx is still on the old haskell-gi setup, the newer nightly builds use haskell-gi-0.24.5

We had to make this change because nixpkgs started packaging a newer pango, so it was the only way to get our haskell-gi packages working again: https://github.com/NixOS/nixpkgs/pull/95434

The `gi-gtkx<IP_ADDRESS>" could be included in place of the gi-gtkx11_4_0_2 version which is dependent on gtk4. Is anyone experimenting with that here?

That sounds like a good idea to me, and it goes along with the similar override for gi-gdkx11.  Please feel free to send a PR implementing this.

btw. lts-16.x.x contains ghc 8.8. I don‘t see what that has to do with ghc-9.x.x.? Although you are right, next lts release will probably happen in the next 3 months.

Taffybar won't builld without a custom overlays in nixos-20.09  ? Is that correct ?
I have had a go with  "https://releases.nixos.org/nixos/20.09/nixos-20.09beta992.7badbf18c45/nixos-minimal-20.09beta992.7badbf18c45-x86_64-linux.iso" and I had the following compilation error:
Preprocessing library for gi-cairo-render-0.0.1..
copying path '/nix/store/2z25awbvfzkqn3bslvrnjsfjplmrkl4a-dbus-hslogger-<IP_ADDRESS>' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/p3iq7w4m9yxpq9972vwvrbflhbhnmrmr-gi-atk-2.0.22-doc' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/nr4dv8nl2hp6p7x2jc2yly3iq4g5nsvb-gi-gio-2.0.27-doc' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/yk1zy8d56gzyr6b9ar7qphn7qc3y2wng-gi-harfbuzz-0.0.3-doc' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/8wgy3nrfhrik4xfggmbixrv2b331a4cp-status-notifier-item-<IP_ADDRESS>-doc' from 'https://repository.irisnet.be/artifactory/nix'...
Building library for gi-cairo-render-0.0.1..
copying path '/nix/store/4b0x1p2qhr89x0m6z0lpg358mixjlhqw-gi-pango-1.0.23-doc' from 'https://repository.irisnet.be/artifactory/nix'...
[ 1 of 18] Compiling GI.Cairo.Render.Matrix ( dist/build/GI/Cairo/Render/Matrix.hs, dist/build/GI/Cairo/Render/Matrix.o )
copying path '/nix/store/c4sk82czg9q2f6xhs6pgg5883pz8nvgp-status-notifier-item-<IP_ADDRESS>' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/l7niw1xc59y478ry1hbj02z63i3bsimj-xmonad-extras-0.15.2' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/8dgg1iap35pwmmjl036296jny5r3azrh-gi-cairo-1.0.24' from 'https://repository.irisnet.be/artifactory/nix'...
copying path '/nix/store/dczg9i0mvg0m38r6ia8zynbnsdja83hv-gi-glib-2.0.24' from 'https://repository.irisnet.be/artifactory/nix'...
building '/nix/store/bpbalfcxggr82jds87rn3apygljl58zq-gi-xlib-2.0.8.drv'...
copying path '/nix/store/bhsx4a7p65380478g0rlxb1zv0424871-gi-gdkpixbuf-2.0.24-doc' from 'https://repository.irisnet.be/artifactory/nix'...
[ 2 of 18] Compiling GI.Cairo.Render.Types ( dist/build/GI/Cairo/Render/Types.hs, dist/build/GI/Cairo/Render/Types.o )

GI/Cairo/Render/Types.chs:68:34: error:
    Module ‘Data.GI.Base’ does not export ‘BoxedObject(..)’
   |
68 | import Data.GI.Base (ManagedPtr, BoxedObject(..), GType(..))
   |                                  ^^^^^^^^^^^^^^^

I guess this is a known issue but a quick confirmation would be appreciated.

Yes, Taffybar is marked as broken on 20.09.
Although since this seems to affect quite a lot of users, I would be highly in favor of someone upstreaming their overlay.
It wouldn‘t need to be pretty. The stable branch has a lot less moving parts so we can get away with a lot more workarounds.
Also you get a PR for your Hacktoberfest count!

I fixed the release-20.09 version in #103898 (hi @PierreR) but actually am quite keen on getting a working taffybar in nixos-unstable. I'm not quite sure what it needs to be fixed. Do we need to wait for a new stackage LTS or GHC version?

@rvl This PR needs to get through stackage:
https://github.com/commercialhaskell/stackage/pull/5653
This will require some changes to taffybar itself, where the version of some gi packages need to be bumped, and some small code changes need to be made. If you make the relevant code changes I can definitely merge and release a new version of taffybar quickly.

@IvanMalison isn't https://github.com/taffybar/taffybar/pull/494 the only code change to taffybar required? I haven't exactly been keeping up but my overlay from https://github.com/NixOS/nixpkgs/issues/63500#issuecomment-692207172 is still working for me

@rvl We just this friday decided to switch from stackage-lts to stackage-nightly. That should mean that getting taffybar to run should be easier now, because we won‘t have old gi-packages from stackage holding us back. (Of course this is only true after the initial ironing out of new build failures we got because of the switch, but trying getting taffybar to work would help with that, too.)
If one or two patches from upstream are required and upstream is slow to merge them, we can apply them in nixpkgs.

What I want to stress: Don‘t try to fix this against master, you should work with a very recent haskell-updates branch.

Thanks for the info - don't stress - I didn't have the appetite to attempt fixing this on master anyway. But I did find that @NickHu's overlay works for me (for the time being).

@rvl Thanks so much for the fix in 20.09 stable. I will give it a go soonish.

taffybar is now being maintained by @rvl, so hopefully it will stay unbroken in the future!


[meta] Use the vscode filesystem API for all filesystem operations.

With version , VS Code added a new filesystem API, to provide a consistent and reliable experience on different platforms and execution environments (including remote).  The extension should use it as much as possible.
The API
vscode.workspace.fs.*
  copy(source: Uri, target: Uri, options?: {overwrite: boolean}): Thenable<void>
  createDirectory(uri: Uri): Thenable<void>
  delete(uri: Uri, options?: {recursive: boolean, useTrash: boolean}): Thenable<void>
  readDirectory(uri: Uri): Thenable<[string, FileType][]>
  readFile(uri: Uri): Thenable<Uint8Array>
  rename(source: Uri, target: Uri, options?: {overwrite: boolean}): Thenable<void>
  stat(uri: Uri): Thenable<FileStat>
  writeFile(uri: Uri, content: Uint8Array): Thenable<void>

vscode.FileStat
vscode.FileType

For reference:

https://nodejs.org/api/fs.html
https://github.com/jprichardson/node-fs-extra#methods

How to Switch?
PRs:

#7915 (for #6911)
#8307 (for #6911)

Tasks:

[ ] identify all current filesystem usage (see #8801)
[ ] consolidate all filesystem usage into IFileSystem (see #8801)
[ ] ensure we keep using only our wrapper in the future (see #8801)
[ ] improve testability (see #8801)
use the vscode.workspace.fs API as a replacement:

node's "fs" module is completely subsumed by "fs-extra"
"fs-extra" module

[ ] (missing) chmod() -> ???

covered by microsoft/vscode#73122 and microsoft/vscode#48659

[x] (#6911) readFile() -> readFile()
[x] (#6911) writeFile() -> writeFile()
[x] (#6911) unlink() -> delete()
[x] (#6911) stat() -> stat()
[ ] (missing) lstat() -> ???

covered by microsoft/vscode#71204
maybe use stat() instead?

[x] (#6911) mkdirp() -> createDirectory()
[x] (#6911) rmdir() -> delete()
[x] (#6911) readdir() -> `readDirectory()
[x] (#6911) remove() -> delete()

this is a recursive delete (i.e. rmtree())

[ ] (TODO) statSync() -> ???

per microsoft/vscode#84518, not going to happen
switch from sync to async?

[ ] (TODO) readFileSync() -> ???

per microsoft/vscode#84518, not going to happen
switch from sync to async?

[x] (#6911) createReadStream() - goes away once we use copy()
[x] (#6911) stop using createWriteStream() for copy()
[ ] (missing) createWriteStream() -> ???

requested: microsoft/vscode#84515

"tmp" module

[ ] (missing) file() -> ???

requested microsoft/vscode#84517

"glob" module

[ ] (TODO) glob() -> vscode.workspace.findFiles()

see microsoft/vscode#84175

...

drop workarounds

[ ] (TODO) drop tree traversal code (per microsoft/vscode#84516)
[ ] (blocked) FileStat.ctime == 0

reported: ~microsoft/vscode#84525~
drop: ...

[ ] (blocked) unexpected successes

reported: microsoft/vscode#84177
drop: ...

[ ] (blocked) sockets as FileType.File

reported: ~microsoft/vscode#84524~
drop: ...

FWIW, I'm not sure this is totally done (would have to check), but it's probably better closed for now.  We can revive it or dupe it later if that turns out to matter.


extract out logic from load CLI

This is how I'm thinking about moving logic out of the CLI
It could be much improved but it's moving in the direction of "easier to test" so I think it's a good thing :)
related to #3

Hmm.. this worked locally for me :confused:
<Result ServerSelectionTimeoutError('localhost:27017: [Errno 111] Connection refused',)>.exit_code

Any idea?

Would it be any point in just restarting the build on travis? (only you can do this :))

Nej failar fortfarande

aha, but all the builds are failing (also master branch)
https://travis-ci.org/moonso/loqusdb/builds
I'll modify the travis setup file to install mongodb :8ball:

Yipeeee :cake:

Nooo!

I'll figure out another way!

but it works... and you need mongo to run the tests - it's already installed on travis so just need to activate it

:+1:


🧪 Update Tests to follow naming convention

All tests should be renamed as per the recommended convention - https://www.ssw.com.au/rules/follow-naming-conventions-for-tests-and-test-projects/

Fixed by #212


SyntaxError after Centos 7 installation

Hi guys,
i get following error on Centos 7.  Could you please tell my why?
Traceback (most recent call last):
  File "/home/xxxxxx/.local/bin/termtosvg", line 11, in <module>
    load_entry_point('termtosvg==0.4.0', 'console_scripts', 'termtosvg')()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 479, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2703, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2321, in load
    return self.resolve()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2327, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/home/xxxxxx/.local/lib/python2.7/site-packages/termtosvg/__main__.py", line 143
    print(record.to_json_line(), file=cast_file)
                                     ^
SyntaxError: invalid syntax

THANKS
Greets
Harry

I think this is because you're using Python 2.7, the readme says termtosvg requires Python >= 3.5.

I think this is because you're using Python 2.7, the readme says termtosvg requires Python >= 3.5.
Exactly!

Ah, sorry guys and thank you for the hint.


allow passing in predefined variables

Coverage decreased (-0.03%) to 67.774% when pulling 8f6ef3bd75de37955db01e79849a81ada5a9a1b4 on predefined-variables into d944ec460eec550a8abd1401c0391560aae593f1 on master.


Globbing for filename

We tend to have a hash generated with filename, thus:
main-SOME_RANDOM_HASH.js

Hey, bundlesize already supports that 😄
Just added that to the README: https://github.com/siddharthkp/bundlesize/blob/master/README.md#configuration

Closing this issue. Feel free to reply back if this doesn't solve your problem.

Baller! Thanks a bunch :)

What about master size comparisons? Using generated bundle names results each file not having an older version to compare

@siddharthkp echoing @pun4drunk question - in my project (and usually) we have bundles generated with a hash suffix, so every build generates a new filename - when this awesome tool compares to the previous build, it is always (-null)

May be it is supported already... can't figure out how to use :(

Same here^


Loading old squid files not working

I tried loading some old, 2019, .squid files and had two outcomes. (1) the file wouldn't open, but with no warning message, as for LMT titanite.squid,
or (2) a different .squid file kept loading. The .squid file I tried to load after (1) occurred was, Kara18.squid, which is 5MB in size, and the one that loaded is magcheck.squid, which is 1.8MB. I have attached the files. I have noticed that when this occurs the title at the top of the window is Squid 3 (Project File: NONE)
LMT titanite.squid.zip
magcheck.squid.zip
Kara18.squid.zip

Fixed in v1.10.3.  This was a missed backward compatibility issue having to do with reporting.  Good catch.


Should be an ulitmate fix for request timeout issue

See https://github.com/louislam/uptime-kuma/pull/3961#issuecomment-1804149144 for more details

I think a better description of the bug in #2142 is that there is missing a migration that sets a default timeout value for monitors created before 1.23. Fixing the data in database might be better, but handling this in runtime is also okay, and might be ultimately necessary.

Yes, I think fixing the data should be done in 2.0.0's knex migration. Runtime patch is good enough for both 1.23.X and 2.0 at this moment.

I think the problem is still there
I updated to 1.23.4.

One reason is unreasonable timeout (0.8x check interval). If I have some status checks every 30 minute, then axios timeout is 24 minutes. I have now manually set timeouts to lower, will see if it will help.

If the monitor is running, but the status is stuck at pending (pending number of times > your defined retry count), then it's not related to this issue.


intel_adsp_cavs25: multiple tests under tests/boards/intel_adsp/smoke are failing

Describe the bug
boards.intel_adsp.host_ipc
boards.intel_adsp.clock_calibrate
Above 2 tests are failing due to a assertion failure.
boards.intel_adsp.ipm_cavs_host doesn't run until the twister timeout.
To Reproduce
Steps to reproduce the behavior:

twister -W -p intel_adsp_cavs25 --device-testing --device-serial-pty=$HOME/zephyrproject/zephyr/soc/xtensa/intel_adsp/tools/cavstwist.sh --west-flash=$HOME/zephyrproject/zephyr/soc/xtensa/intel_adsp/tools/cavstwist.sh -T tests/boards/intel_adsp/smoke/ -vvv
see error

Logs and console output
INFO:cavs-fw:Mapped PCI bar 0 of length 16384 bytes.
INFO:cavs-fw:Selected output stream 7 (GCAP = 0x1009701)
INFO:cavs-fw:Mapped PCI bar 4 of length 1048576 bytes.
INFO:cavs-fw:Detected cAVS 1.8+ hardware
INFO:cavs-fw:Trimming 16 bytes of extended manifest
INFO:cavs-fw:Resetting HDA device
INFO:cavs-fw:Powering down DSP cores
INFO:cavs-fw:Configuring HDA stream 7 to transfer firmware image
INFO:cavs-fw:Mapped 2M huge page at 0x155200000 to contain 106496 bytes of firmware
INFO:cavs-fw:Filled the buffer descriptor list (BDL) for DMA.
INFO:cavs-fw:Starting DSP, ADSPCS = 0xf0f
INFO:cavs-fw:Wait for ROM startup
INFO:cavs-fw:Sending IPC command, HIPIDR = 0x81004000
INFO:cavs-fw:Starting DMA, FW_STATUS = 0x5000001
INFO:cavs-fw:Waiting for firmware handoff, FW_STATUS = 0x5000001
INFO:cavs-fw:cAVS firmware load complete
--
Running test suite intel_adsp
===================================================================
START - test_smp_boot_delay
Launch cpu1
Launch cpu2
Launch cpu3
PASS - test_smp_boot_delay in 0.61 seconds
===================================================================
START - test_cpu_halt
halt/restart core 1...
halt/restart core 2...
halt/restart core 3...
PASS - test_cpu_halt in 0.452 seconds
===================================================================
START - test_post_boot_ipi
PASS - test_post_boot_ipi in 0.1 seconds
===================================================================
START - test_cpu_behavior
Per-CPU smoke test 0...
Cache behavior check
CCOUNT/WALCLK ratio 10.406
CPI = 2.506
Per-CPU smoke test 1...
Cache behavior check
CCOUNT/WALCLK ratio 10.396
CPI = 2.502
Per-CPU smoke test 2...
Cache behavior check
CCOUNT/WALCLK ratio 10.425
CPI = 2.502
Per-CPU smoke test 3...
Cache behavior check
CCOUNT/WALCLK ratio 10.409
CPI = 2.502
PASS - test_cpu_behavior in 0.2 seconds
===================================================================
START - test_host_ipc
Simple message send...
Return message request...
Return message request 2...
Return message request, async...
Assertion failed at WEST_TOPDIR/zephyr/tests/boards/intel_adsp/smoke/src/hostipc.c:83: test_host_ipc: (i < 10000 is false)
timeout waiting for msg_flag
FAIL - test_host_ipc in 0.589 seconds
===================================================================
START - test_clock_calibrate
Assertion failed at WEST_TOPDIR/zephyr/tests/boards/intel_adsp/smoke/src/hostipc.c:28: ipc_done: (done_flag is true)
done called unexpectedly
FAIL - test_clock_calibrate in 0.8 seconds
===================================================================
START - test_ipm_cavs_host

Environment (please complete the following information):

OS: Fedora
Toolchain (e.g Zephyr SDK, ...): SDK13.2
Commit SHA: e65e26162199

This is a random failure, and found the cAVS IPC Message Handler Callback function was not invoked as expected.

@andyross Hi, could you help to look at this issue?

Also find that test_ipm_cavs_host failed on intel_adsp_cavs18 occasionally, we can add retry-failed option when running tests to avoid this unstable issue.

Just getting to this for triage.  This definitely seems reliable on my hardware (the Asus chromebook and a Up Xtreme).  What kind of failure rates are you seeing?  Does this happen if you do it via a manual build or only in a twister run, etc...?

Ping?  Any update on the failure rate, etc...?

(more details)
There are 2 test sets:

Test Set 1

boards.intel_adsp : boards.intel_adsp.host_ipc
boards.intel_adsp : boards.intel_adsp.clock_calibrate
boards.intel_adsp : boards.intel_adsp.ipm_cavs_host

Test Set 2

drivers.dma.chan_blen_transfer.dma_m2m_chan1_burst8
drivers.sensor.generic.sensor_unit_conversion
drivers.can.utilities.can_filter_to_zcan_filter
drivers.dma.chan_blen_transfer.dma_m2m_chan0_burst8
drivers.hwinfo.api.clear_reset_cause
drivers.can.utilities.can_frame_to_zcan_frame
drivers.dma.chan_blen_transfer.dma_m2m_chan0_burst16
drivers.dma.scatter_gather.dma_m2m_sg
drivers.can.utilities.zcan_frame_to_can_frame
drivers.sensor.generic.fpu.sensor_unit_conversion
drivers.sensor.generic.sensor_handle_triggers
drivers.hwinfo.api.device_id_get
drivers.hwinfo.api.get_reset_cause
boards.intel_adsp.ipm_cavs_host
drivers.dma.chan_blen_transfer.dma_m2m_chan1_burst16
drivers.can.utilities.can_bytes_to_dlc
drivers.can.utilities.can_dlc_to_bytes
drivers.sensor.generic.fpu.sensor_handle_triggers
drivers.can.utilities.zcan_filter_to_can_filter
drivers.sensor.generic.fpu.sensor_get_channels
drivers.hwinfo.api.get_supported_reset_cause
drivers.dma.loop_transfer.dma_m2m_loop
drivers.sensor.generic.sensor_get_channels
drivers.dma.loop_transfer.dma_m2m_loop_suspend_resume
boards.intel_adsp.mm.adsp_mem_map_array
boards.intel_adsp.mm.adsp_mem_map_region

For cavs25,
Scenario 1:
If test set 1 failed completely with below screenshot (i.e. without "PROJECT EXECUTION FAILED"), it will cause test set 2 to end in error state with only delay boot banner shown.

Scenario 2:
If test set 1 failed with below screenshot (i.e. with "PROJECT EXECUTION FAILED"), it will not jeopardize test set 2.

It seems random for scenario 1 and 2 to happen.
But if we remove the CONFIG_MP_NUM_CPUS=4 added in commit https://github.com/zephyrproject-rtos/zephyr/commit/b433813f5fb5655ee18133dfac176c9e8dfe9a45, test set 2 will not be affected by test 1 even in scenario 1.
So a limited conclusion so far is:
Test set 1 and CONFIG_MP_NUM_CPUS=4 seem to cause the board enter some incorrect state and block the test set 2 which runs afterwards.

(more details)
There are 2 test sets:
Test Set 1
Test Set 2
For cavs25,
Scenario 1: If test set 1 failed completely with below screenshot (i.e. without "PROJECT EXECUTION FAILED"), it will cause test set 2 to end in error state with only delay boot banner shown.
Scenario 2: If test set 1 failed with below screenshot (i.e. with "PROJECT EXECUTION FAILED"), it will not jeopardize test set 2.
It is quite often for test set 1 to fail on all cavs 15/18/25 platforms. But it seems random for which scenario to happen.
And if we remove the CONFIG_MP_NUM_CPUS=4 added in commit b433813, test set 2 will not be affected by test 1 even in scenario 1.
So a limited conclusion so far is:
Test set 1 and CONFIG_MP_NUM_CPUS=4 seem to cause the board enter some incorrect state and block the test set 2 which runs afterwards.

The Test Set 1 is failing for all cavs15/18/25 platforms now.

Amber poked me to come look at this one.  Indeed, I see this reliably now (though checking the dates, it's likely that there is another problem on the CI hardware).
But for the existing failure: this bisects to this patch which merged a few weeks back:
commit 5416abfe5f70 ("util: convert wait_for macro to uppercase")
A simple revert of that works, but as it involves other subsystems I can't submit that and need to spend a bit of time untangling.
As far as the changes in that patch: It doesn't simply rename a macro, it replaces the original cpu-local spinning in the WAIT_FOR() macro with a sleep.  That's... probably not obviously wrong in all cases, but it's not the design intent either (most of these conditions are trying to catch microsecond-scale replies from the host, as reported by interrupts potentially received on another core: we really do want to be spinning).  I suspect there's an edge case in there tripping things up.
Will untangle the deltas and submit a partial reversion when I get a chance.


[.NET 8] Warning: "Found version-specific or distribution-specific runtime identifiers"

Describe the bug
Including the Microsoft.CognitiveServices.Speech NuGet package yields a build warning.
C:\Program Files\dotnet\sdk\8.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(284,5):
  warning NETSDK1206: Found version-specific or distribution-specific runtime identifier(s):
  centos7-x64, win10-arm, win10-arm64. Affected libraries: Microsoft.CognitiveServices.Speech.
  In .NET 8.0 and higher, assets for version-specific and distribution-specific runtime identifiers
  will not be found by default. See https://aka.ms/dotnet/rid-usage for details.

To Reproduce

Create an empty .NET 8 Console App.
Install the Microsoft.CognitiveServices.Speech NuGet package.
Build the solution.

Expected behavior
No warnings!
Version of the Cognitive Services Speech SDK
Microsoft.CognitiveServices.Speech v1.33.0.
Platform, Operating System, and Programming Language

OS: Windows
Hardware: x64
Programming language: C#
Visual Studio 2022, .NET 8

I hope I'm posting this to the right place.  Thanks for your time!

Hi @ladenedge , this is Darren from the Speech SDK team. Thank you for opening this issue. I will look into this and report back here shortly.

@ladenedge we have an internal work item to switch to portable RIDs (per NTESDK1206). Meanwhile, your application should work fine other than seeing this warning. If you like, you can suppress this warning by adding this to your .csproj file:
<ItemGroup>
  <RuntimeHostConfigurationOption Include="System.Runtime.Loader.UseRidGraph" Value="true" />
</ItemGroup>

(Internal work task number 6023463)

Thank you.  Looking forward to the new version!

@ladenedge The upcoming release (due out next week, version 1.34) will include a fix for this. Thank you again for reporting this issue!

@dargilco not fixed in 1.34.1

The warning is still there, but the content is a bit different.  Now instead of showing many RIDs, I only see centos7-x64:
C:\Program Files\dotnet\sdk\8.0.100\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.targets(284,5):
   warning NETSDK1206: Found version-specific or distribution-specific runtime identifier(s): centos7-x64.
   Affected libraries: Microsoft.CognitiveServices.Speech. In .NET 8.0 and higher, assets for version-specific
   and distribution-specific runtime identifiers will not be found by default. See https://aka.ms/dotnet/rid-usage for details.

Just to confirm, I have the following in my build log showing the version number:
C:\Users\laden\.nuget\packages\microsoft.cognitiveservices.speech\1.34.1\lib\netstandard2.0

I went ahead and opened a new ticket: #2244.  (Please feel free to close that one and re-open this one if that's the preferred way to handle this sort of thing.)
Thank you!


add ledvance<PHONE_NUMBER>339 (SMART+ ZB FLEX 3P RGB + TW)

Device information
LED Strip, sold with 3 segments under this article number:<PHONE_NUMBER>339.
This profile is for the full length with 3 segments, as it's sold as one unit. While it could be extended with additional sections, but I don't have them. So I could only provide measurements with 1 or two sections, too. But I doubt many people would throw away a section and use just two or something like that.
Product page
Z2M Device Page
Zigbee model name sounds unique this time (hopefully), so I've added it as alias.
Home Assistant Device information
Flex 3P multicolor<PHONE_NUMBER>339)
by LEDVANCE

Zigbee Info:
Zigbee Model: FLEX RGBW Z3
Zigbee Manufacturer: LEDVANCE
Description: Flex 3P multicolor
Firmware build date: Feb 16 2022
Firmware version: 01066400

Checklist

[x] I have created a single PR per device. When you have multiple submissions please create separate PR's.
[x] For lights - I have only included the gzipped files (*.gz), not the raw CSV files.
[x] For lights - I have provided a CSV file per supported color mode. Look that up in Developer Tools -> States

Additional info

In case you're wondering about the wide spread of the CT mode: This strip has a cold white LED and mixes the warm colors in with an RGB LED, that's why its power consumption is so vastly different for different white tones.

Thank you. everything seems fine by me. Let's merge.


Updating the README

This PR is aimed to provide the users (old & new) with a more comprehensive description of many concepts, like:

What this library is
How they can contribute
What they should when facing issues

Aside from that, I think the first step towards a more in-depth PR to the docs is to provide the links @matthamil had separately here in the README to give who start at least some extra resources "right away".
Moreover, the FAQ section aims to address some recurring issues with the goal of augmenting the transparency from us maintainers to the users.
Yes, this would mean a "longer" README but since it's usually the place many devs look into to "understand" a library I feel it's worth the tradeoff.
Obviously completely open to any feedback.

there are some 3-rd party packages for react-navigation that might be worth mentioning: I know of react-navigation-addons and [ehm, shameless plug] react-navigation-props-mapper

Hey @vonovak thanks for your feedback, yeah a section with "extra libs" can be a good section. I'll add it tomorrow.
@matthamil already provided me some feedback, still waiting on @spencercarli and/or @GantMan to let me know if it's fine for them.

Ok update with the expo link for @GantMan and the libs for @vonovak ;)
I think now it's solid 💯 thanks for the feedback.


libhevc: tidy up android bp

sort listings in alphabetical order
Test: Build
Change-Id: Iddc937c72cebed88aad3d14f222f61dac904938b

is incomplete.


Watchers, tips for beginners: Mention options immediate and deep

Hey,
I'd like to offer to prepare a PR with a few lines to the guide to address beginners questions regarding watchers.
When I started, sometimes I wondered: "Why doesn't my watcher seem to run?"
In addition to the API docs, my understanding is that the guide provides a different angle/approach, especially for beginners, although I also go to the API docs to learn more.
I'd ask for quick feedback if you'd like the guide to expand that far, or maybe it has intentionally been left out.

Hi @michapietsch! Thanks for your offer to update the watcher section. At this time, we're currently focused on efforts for the v3 docs. As a result, happy to mark this as post-3.0 for us to discuss once the team has more bandwidth to update the v2 docs.
If you have any other questions, please let me know!


Add ability to update posts' syndication URLs if a link is returned

Bridgy and IndieNews return a url property after syndication that is the post's syndicated URL.
We should provide some sort of middleware (for want of a better word?) that can perform this for us.
I.e. via https://brid.gy/about#response:
HTTP/1.1 201 Created
Content-Type: application/json
Location: https://twitter.com/me/status/456789

{
  "url": "https://twitter.com/me/status/456789",
  "type": "post",
  "id": "456789"
}

(The url property should be used, not the Location header)

Can you explain what you think the middleware should do? If you're writing a new syndication as src/events/process-post/syndicate/[service].js you should return the URL you want to use. For the Twitter syndicator I get the tweetUrl and return that to the index.js.

Sorry yeah! So what I've currently got on my site is if Bridgy/IndieNews return a $.url in the response of the post, it then performs a Micropub update to replace the syndication URL with the following request:
{
  "action": "update",
  "url": "https://www.jvt.me/mf2/2021/11/tefuk/",
  "add": {
    "syndication": ["https://twitter.com/JamieTanna/status/1459195307368108040"]
  }
}

There's some behind-the-scenes logic that removes the exisitng syndication link, with the resulting change being: https://gitlab.com/jamietanna/jvt.me/-/commit/f6114a8b40b56c7e004494d46a8f5e0d8e0dbaa1

I don't think a Micropub update would be needed if you keep the URL that's returned. With the Twitter syndication I use the tweet URL that's returned is appended to the post.properties.syndication array and stored.
I think if you're using the special brid.gy syndication URL you'll want to remove that from the array before it's persisted.

Even better! 👏🏽


Merge branch release-4.9.20 into 4.9.x

Purpose
$subject

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: sahandilshan:white_check_mark: madurangasiriwardena:x: wso2-jenkins-botYou have signed the CLA already but the status is still pending? Let us recheck it.


Not able to use ion-datetime-picker twice in single view

I am trying to take start and end time. Given below is sample html.  After submitting form, it is giving same value for both start and end time. Please advise.

					{{start_event_time| date: "h:mm a"}}

					{{end_event_time | date: "h:mm a"}}

Hi,
I can't see any problem in your code. Please make a codepen or similar demonstrating your problem.


Update CHANGELOG.rst

Description

Related Issue(s)

Breaking Change?

Checklist

[ ] I have made corresponding changes to the documentation (if required)
[ ] I have added tests that prove my fix is effective or that my feature works

comment


Enhance the accessibility of ColorPickercomponent

Description
This issue aims to address accessibility deficiencies in our slider component in accordance with W3C guidelines. The component currently does not meet the accessibility standards outlined in the W3C documentation.
The goal is to ensure the component is accessible to all users, including those using assistive technologies. All unchecked items in the checklist below should be addressed.

role

[ ] The input tag in the ColorPicker component should have the combobox role.

aria-controls

[ ] An element with the combobox role must have the aria-controls attribute containing the ID of the corresponding popup element.

Are you willing to participate in fixing this issue and create a pull request with the fix?
None
Additional Information
The following issue may be referenced:
https://github.com/yamada-ui/yamada-ui/issues/1731

I will try it!!!

@taku10101
Thank you for comment!
I've assigned to you!

@taku10101
Hi, Thanks for the working on this issue!
We will return this issue assignment to initial state.
If you are working on this issue and would like to be reassigned, please contact us.


Place inside a ScrollView

In the CustomAndStaticToolbar example there's a component above the RTE, but when the content from the RTE does not fit on the screen, the top view remains static.
What's the best approach for have the top component & RTE scroll together?

This is an interesting issue, you could make the editor have a dynamic height, but this breaks other things that were previously handled within the webview itself, like keeping the selection above keyboard and it also messes with ordinary keyboard avoiding view. https://github.com/10play/10tap-editor/pull/89
https://github.com/10play/10tap-editor/assets/36531255/24a7406b-ff8f-4441-b36d-62788c8501c2
Depending on your app, I'd either just go with having the content scrollable, or create a custom "advanced" editor and have the static header inside the editors webview
@GuySerfaty thoughts?

Yeah @17Amir17 the poc looks good to me.. for fixing the issue with the focus on the cursor when it goes behind the keyboard we can try modifying https://10play.github.io/10tap-editor/docs/api/EditorBridge#updatescrollthresholdandmargin
@gituser8796 email us on<EMAIL_ADDRESS>if you need some specific help


Adding 0 ttl on harvester migration

When harvester credentials are migrated, this now adds a 0 ttl for tokens which were not found, rather than simply skipping those tokens.
Issue:

Problem

Solution

Testing

We’d like to have @jakefhyde review the change, as he was the one who implemented the feature :)

Validation Template
Root Cause
On upgrade, Rancher will attempt to update harvester cloud credentials with a  rancher.io/expiration-timestamp annotation which specifies when the cloud credential will expire. For cloud credentials which had a token which was deleted, this annotation would not be updated. In these cases, the UI would not show a renewal button (Since no expiration timestamp was on the secret).
What was fixed, or what change have occurred
Now, on migration, if the token does not exist, the annotation is set to 0 on the secret (rather than omitted from teh secret).
Areas or cases that should be tested

Upgrade from 2.9.2.

On rancher 2.9.2, create a cloud credential for harvester.
Create a second could credential for harvester.
Create a cloud credential for another cloud provider (e.x. digitalocean/aws).
Delete the token associated with the first harvester cloud credential.
Upgrade Rancher to the new version.
Verify that the UI allows users to renew the two harvester cloud credentials, but not the AWS/digitalocean cloud credential.
Verify that the first cloud credential (the one the token was deleted for) has the rancher.io/expiration-timestamp annotation set to 0.
Verify that the second cloud credential (the one with the valid token) has the rancher.io/expiration-timestamp annotation set to the expected value (i.e. non-0).

What areas could experience regressions

The calculation of the expiration timestamp annotation for harvester/non-harvester cloud credentials.
The presence of the renew button for non-harvester cloud credentials.

Are the repro steps accurate/minimal?
Repro Steps:

Run Rancher 2.9.2.
Create a harvester cloud credential.
Delete the kubeconfig token associated with the cloud credential made in step 2.
Upgrade to 2.9.3-alpha8.
Note that the cloud credential does not have a renew button or an expiry timestamp, and there's no indication that the cloud credential expired. (After the fix, the renew button will be present and the expiry timestamp will be set to 0, but there will still not be a notification that the token has expired).


new check: streaming_delay

measuring how much a slave server is lagging behind its master.
This one is a bit similar to the existing streaming_delta check, except the delta check is supposed to be run from the master, and it measures the data delta in bytes, not the time delta in seconds.  In some settings one would probably like to get a quick alert if the slave is significantly lagged compared to the master, even if the data delta size is small.
(requested by a customer of ours)

Hi,
I just looked at this PR.  Actually, we didn't implement it previously because the underlying function is not really helpful.  It unfortunately doesn't return the replication lag, but the time since some data has been received and replayed.  So if there's no write activity on the primary server, this service will probably trigger some false errors.  If we were to accept this check, it'd have to be renamed to something like "received_activity_from_primary" or something that makes clear what's it's actually checking.
About the code:

there's no pg_last_wal_replay_timestamp function in postgres, pg_last_xact_replay_timestamp has never been renamed AFAIK
you document that UNKNOWN is returned if used on primary (and stand-alone server, but I'm not sure of what it means), but that's not the case.  You should probably check for pg_is_in_recovery()

Hi,
So this PR has been softly rejected since 5 years already. Let's close it for good.
However, this feature request will be supported through some other means using *_lag fields that appeared in pg_stat_replication in v10. See #361 and future PR about it.
Cheers,

Oh ... this one went under my radar.  I don't have responsibility for any primary-slave postgresql setups at the moment, so this is no priority for me, but I still think it may be useful for primary-slave environments where continuous write activity is expected.  If the slave is lagging behind, then something is most likely wrong.  I could blow the dust of this one and rename it eventually - but if nobody finds it useful, then let it be :-)

Any reason why you want the service on the secondary rather than the primary?  Are the write_lag and replay_lag from pg_stat_replication enough?

Long time since I was playnig with this, but on the primary server you can only check that there exists a slave that is up-to-date.  Theoretically things may be set up wrongly so that there is another slave connected to the master, so I think it's nice to check from the slave point of view that it's connected, too.  I believe I was playing around with disaster recovery situations where a slave was switched to master, new slaves were taken up or taken down, etc.

Hi,

but on the primary server you can only check that there exists a slave that is up-to-date

No, from pg_stat_replication on the primary you can check that :

the specified secondaries are connected
how much data each of them are lagging behind (write_lsn,flush_lsn,replay_lsn, we use them)
how long they are lagging behing(write_lag,flush_lag,replay_lag, we don't use them... yet)

so the idea is to use the *_lag fields, report them in perfdata and allow to set thresholds on them.

Theoretically things may be set up wrongly so that there is another slave connected to the master

Yes, but you can setup check_pga to explicitly check the streaming to some specific standbies using their application_name + remote IP address, using eg: --slave 'thisstandbyname <IP_ADDRESS>' --slave 'thisanotherstandbyname <IP_ADDRESS>'

I still feel it would be simpler and easier being able to check from a specific slave if it's connected to the master than to do it from the master, but I won't waste time arguing at that - and for the foreseeable future I'm not going to monitor any postgresql slave servers anyway :-)

I still feel it would be simpler and easier being able to check from a specific slave if it's connected to the master than to do it from the master

Sure, it would be possible, why not. However, you can not check the lag from the standby point of view.

and for the foreseeable future I'm not going to monitor any postgresql slave servers anyway :-)

Thank you very much for your past discussions and contributions Tobias!
Cheers,


Disable file watcher in run_build() for the sake of qemu on arm64

While slatedocs/slate native linux/arm64 Docker image is available, running linux/amd64 image on ARM64 (Apple silicon) triggers the infamous Failed to initialize inotify (Errno::ENOSYS) error. It is particularly annoying when one attempts to use Slate's linux/amd64 image on ARM (e.g. as part of multi-arch build).
There appears to be no reason not to disable the watcher in run_build() function in slate.sh, since it's used as one time call.

Alternatively, instead of disabling file watcher entirely --watcher-force-polling could be added to the run_build() bash function, in case I'm not seeing why file watcher might be needed there.


Generate baseline data script for operator with single input

This PR includes

generate baseline data script
baseline data for softsign and gelu operators.

@huningxin @fdwr PTAL, thanks.

Just noticed this is still open. Is it obviated by other changes?

Is this applicable still @BruceDai ?

Is this applicable still @BruceDai ?

Apologize to forget update this PR and missed your previous reminder.
I'm working it , will submit a new commit ASAP.

@fdwr I updated commit to fix your comments, please take another review, thanks!


Update to new bokeh version

Currently we pin to bokeh===0.12.15, it would be nice to update to the latest, 2.2.2.
However, 2.2.2 does not support Python 3.5. The previous version, which does support 3.5, is 1.4.0. Unfortunately, between 1.4.0 and 2.2.2 there is a deprecation that affects this JN: "Importing from_networkx from bokeh.models.graphs is deprecated. Import from bokeh.plotting instead."
So better to wait till after 3.5 is no longer supported.
See https://github.com/dwavesystems/dwave-ocean-sdk/issues/91
I have the code change here for when we do: https://github.com/JoelPasvolsky/factoring-notebook/tree/bokeh

I don't see why would this would be a blocker.
Just unpin bokeh in your requirements, so that the latest version available for the current python is installed.
And then do a conditional import by replacing line 27 on your branch with:
try:
    from bokeh.plotting import from_networkx
except ImportError:
    # handle bokeh<=1.4.0 (py35 and before)
    from bokeh.models.graphs import from_networkx


its not a issue, its ask

what is obfuscate it is? i will deobfuscate everything

it is not obfuscator, it is compiler...


Rules dont work Nmap version 7.93

This out:
$ nmap <IP_ADDRESS>
Starting Nmap 7.93 ( https://nmap.org ) at 2024-09-05 17:08 -03
Nmap scan report for <IP_ADDRESS>
Host is up (0.024s latency).
Not shown: 996 filtered tcp ports (no-response)
PORT     STATE SERVICE
22/tcp   open  ssh
53/tcp   open  domain
80/tcp   open  http
1198/tcp open  cajo-discovery

Nmap done: 1 IP address (1 host up) scanned in 4.80 seconds

Logs:
09/05/2024-17:11:34.995490  [Drop] [**] [1:3400020:2] POSSBL SCAN SHELL M-SPLOIT TCP [**] [Classification: A Network Trojan was detected] [Priority: 1] {TCP} <IP_ADDRESS>:42088 -> <IP_ADDRESS>:4444
09/05/2024-17:11:35.255068  [Drop] [**] [1:3400020:2] POSSBL SCAN SHELL M-SPLOIT TCP [**] [Classification: A Network Trojan was detected] [Priority: 1] {TCP} <IP_ADDRESS>:42090 -> <IP_ADDRESS>:4444

I'm running test in with suricata -T and dont show errors, but the rule dont recongize nmap scan.
Obs.: I test with -sS, etc

Hi, thanks for your post.
That is very interesting. I did a test after reading your post using the latest NMAP 7.94 with a standard scan like yours, and also as a SYN scan -sS, and the rules seemed to work perfectly here, as illustrated below in the logs.
It might help to check the Suricata logs (and OPNsense's too if one is used there) for more details of possible errors or conflicts somewhere. Or if there are perhaps some other devices or software in the way between the NMAP end and your Suricata, which could already catch such massive fast port floods when they happen, but still let more "normal speeded" traffic pass. Doing a raw packet capture from Suricata's end might also prove either way if the whole NMAP flood is actually really reaching the Suricata's end. The interesting bit there - and some positive at least - is that one of the detection rules is catching stuff, which is clear from that Suricata log indicating the usage of port 4444. So, the rules file is loaded and in use, so it kind of works, but for some reason the other detection rules did not fire to your NMAP scan. Without more information at hand right now, it's somewhat hard to determine the root cause, although I really would like to, but I hope you understand.
Here below are my results from the test I just did now to check it myself. It blew up my Suricata log file as was expected. :-) I tested on a dedicated OPNsense computer, running Suricata, and using the installation method following the readme. All software used were with the latest updates at the time of writing.
All the best,

Aleksi

Starting Nmap 7.94SVN ( https://nmap.org ) at 2024-09-06 01:28 ****
Nmap scan report for ..*** (.*..)
Host is up (0.0039s latency).
 :-)

I am testing Suricata on pfSense (FreeBSD), and the ruleset is designed according to Suricata's patterns. I wrote a rule to detect segmented and unsuccessful TCP/SYN requests, and it worked.
Is there something specific in OPNsense that makes the rules work? We haven't tested it on other firewalls or directly on a Suricata system yet, right? I might be mistaken in trying to use the rules on pfSense or natively.


Fixed damage so it's static and doesn't grow, and added icons instead…

… of text names to items (with alt="imageName" for each)

@bmackenty check... files changed... before you merge?
The entirety of archive has been deleted...


add support for DuckDB

adding database support for duckdb would be graet
https://duckdb.org/

It was added in DBeaver 21.0.4.
Duplicate of #12068


Release

hello, where I can download freshest compiled release? :)
thank a lot

I actually wasn't planning to put out a new build before the domain name was changed to my new host, but I have put it up at http://www.stiandrobak.com/CustomBuilds/Simple_Comic.php now.

thank you!


question btn hidden on mobile

Made the "Questions" button hide in mobile. This is because too many buttons in the UI sometimes overflow the width on the screen.
In my phone which has a small screen I could see the screen overflowing.
With the btn:

Without the btn:

Is it useless on mobile? Should we consider moving it somewhere instead of hiding?

Is it useless on mobile? Should we consider moving it somewhere instead of hiding?

It just scrolls down to the FAQ for you. It doesn't really redirect you somewhere.
On mobile you will still be able to manually scroll down and go to the faq.


Optimize: Services

Description
Remove unneeded lines of code by:

Switching to ?? where possible
No is_object checks for nullable typehints
Use Elvis operator where possible
et al.

I have a failing test for router though I didn't touch that before:
$routes  = $routes ?? static::routes();

// this line is missing in the original, causing the passed request object to be actually <null>,
// causing 'Undefined getMethod() on null' on CodeIgniter\Router\Router line 149.
// for fix, I added this line. but I don't know why Travis is not erring in here
$request = $request ?? static::request();

return new Router($routes, $request);

Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPdocs
[x] Unit testing, with >80% coverage
[ ] User guide updated
[x] Conforms to style guide

Personally, I prefer to use the more specific config class name as typehint instead of the generic BaseConfig. This way we can be sure that no one passes an instance of Config\Images for the Parser, for example. And I think no one ever did that.

Fair point, I think we can go with a specific class.

I think we should also consider the case of #3475 for services.

Okay, it seems we all agree on the stricter types for $config.
@paulbalandan I looked at the Services file and we use BaseConfig as type in several places. Could you please review all services and fix types for $config?

I dont get how my changes affect Database Live tests.

We're supposed to use the currently loaded instance of the config file. We should use config('Validation') instead of new ValidationConfig.
I'm also wondering shouldn't we use an explicit declaration for the config types, like \Config\Validation in the method declaration instead of ValidationConfig? Not because currently proposed version is wrong but I wonder if this won't raise questions among users who may not know what class this is? But maybe I'm exaggerating.

We're supposed to use the currently loaded instance of the config file. We should use config('Validation') instead of new ValidationConfig.

Oh. I'll look into this.

I'm also wondering shouldn't we use an explicit declaration for the config types, like \Config\Validation in the method declaration instead of ValidationConfig? Not because currently proposed version is wrong but I wonder if this won't raise questions among users who may not know what class this is? But maybe I'm exaggerating.

I don't know but shouldn't this be already known if you're using PHP OOP? For me, I don't prefer using FQCN in typehints.

For me, I don't prefer using FQCN in typehints

I think this is probably a matter of opinion. Personally unless there is some compelling reason otherwise I will put use statements at the top of my file for every class int he file (including type hints) and then use the short name. This makes it easy to change classes later via aliasing and it acts as a reference for each file as to which classes are in use there.

This is looking good, and very close! Thanks you two.

I don't know what the phpstan error means. @samsonasik ?

@paulbalandan you can remove // @phpstan-ignore-line in system/Config/Services.php line 358.


Install error for Ubuntu16.04

I run "python setup.py install", but it can not work.

Please read what's written in the error message and the linked documentation.

sudo python setup.py install

Throwing sudo at a permission problem is generally a bad idea. Maybe for this user a virtualenv is better, or maybe passing setup.py a writable install directory, or building in-place. It's hard to tell without any context which is the most suitable approach.

Thanks a lot. It works.


NSLock: fix warnings on macOS

In https://github.com/apple/swift-corelibs-foundation/commit/6476c4fdae88e00688d743af5130179a5b2329d8 changes were made for compatibility with SE-0184.
A function in NSLock was missed though, probably because it is only compiled when building the project in Xcode on macOS.
Fix these warnings too.

@swift-ci please test

Is it necessary to call deinitalize on theses two types? I think they are opaque and am not sure it is necessary (happy to be corrected though)

Pass, I'm just cleaning up the warnings at the moment :)

No worries, LGTM

@swift-ci please test and merge


Roll Flutter Engine from 62e0b5f9c340 to ee1884c88383 (6 revisions)

https://github.com/flutter/engine/compare/62e0b5f9c340...ee1884c88383
2024-06-25<EMAIL_ADDRESS>fix: web canvaskit fragment shaders were not using updated uniform values (flutter/engine#53246)
2024-06-25<EMAIL_ADDRESS>Roll Dart SDK from b5fc85cfcf1b to 65ab2f2cf0d3 (1 revision) (flutter/engine#53565)
2024-06-25<EMAIL_ADDRESS>Roll Skia from e4e4feb97a54 to da1ea4eb0270 (4 revisions) (flutter/engine#53563)
2024-06-25<EMAIL_ADDRESS>[DisplayList] Switch to recording DrawVertices objects by reference (flutter/engine#53548)
2024-06-25<EMAIL_ADDRESS>Roll Skia from 5f21260470cf to e4e4feb97a54 (1 revision) (flutter/engine#53559)
2024-06-25<EMAIL_ADDRESS>[impeller] Cleanup blur (flutter/engine#53543)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC jimgraham@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Use from/into instead of as, to ensure type conversions are not lossy

There are quite a lot of places in the codebase (easy to see if you run cargo clippy) where, e.g. val as u32 is done, instead of u32::from(val).
Clippy lint: https://rust-lang-nursery.github.io/rust-clippy/v0.0.212/index.html#cast_lossless

I'm currently working on this. I'll submit a PR soon.


Enhance ApifyTool with additional methods

This commit enhances the ApifyTool by adding the following methods:

get_dataset: Get the dataset associated with a given actor run
get_dataset_items: Get all items from a given dataset
get_key_value_store: Get the key-value store associated with a given actor run
download_file: Download a file from the key-value store of a given actor run
store_dataset: Store data in an Apify dataset

These additional methods provide more functionality for interacting with Apify services, such as fetching datasets, accessing key-value stores, downloading files, and storing data in datasets.
The README.md file has also been updated to reflect these changes and provide usage examples for the new methods.

Hi, can I get some feedback on this pull request?

Pretty interesting, but I think we might want to break some of those function into individual tools so we can be specific around attributes as well


Git Repository using Atom

Prerequisites

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

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

Description

I can't create a repository using Atom. when i try to create one it says loading ... can somebody tell me if its my fault or error.
Steps to Reproduce

Expected behavior:

Actual behavior:

Reproduces how often:

Versions

Additional Information

Hey @VijayBhaskar-G did you try login into github from atom? If yes did you paste the token generated into the github package in atom?
Which version of atom are you using?

Hey @VijayBhaskar-G did you try loging into github from atom? If yes did you paste the token generated into the github package in atom?
Which version of atom are you using?

Thanks for Responding.. I can't see any Token Generated while creating A Repository . Can you briefly explain me please .. I can't find relevant Info in YouTube too ..

Hey @VijayBhaskar-G did you try loging into github from atom? If yes did you paste the token generated into the github package in atom?
Which version of atom are you using?

Thanks for responding . I didn't logged into it. Now working fine...


Remove etas code

Closes #1209

You want also to remove: https://github.com/pulibrary/bibdata/blob/main/spec/fixtures/marc_to_solr/overlap_20200316_compacted_sorted_final.tsv https://github.com/pulibrary/bibdata/blob/main/spec/fixtures/files/overlap_20200429_columbia_abbreviated.tsv https://github.com/pulibrary/bibdata/blob/main/spec/fixtures/overlap_20200429_princeton.tsv

Thanks - done


Range utils

(Formerly https://github.com/envoyproxy/envoy/pull/17872)
Commit Message: Move range logic into range utils and remove range-specific statuses from CacheEntryStatus
Risk Level: Low (refactor)
Testing: Existing

mklein attempted to reopen #17872, but Github said no. Here's a new PR with the same content and commit history.

Oh...I guess the source of this PR was reviewed by @RyanTheOptimist -- I think he can actually finish the review then?

@penguingao would probably be the next choice after me for cache team review.

This LGTM.


python3Packages.pydantic-core: init at 2.3.0

As suggested by @SuperSandro2000, I'm targeting staging due to the dependency
on a fix to the maturinBuildHook which triggers a mass rebuild of ~1800+ packages.
Old PR to master: https://github.com/NixOS/nixpkgs/pull/242543
Description of changes
This package provides the core functionality for pydantic V2 validation and serialization.
Pydantic-core is currently around 17x faster than pydantic V1.
When this package is reviewed, attested and merged, we can start considering to bump pydantic to V2.
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

Please undraft when the other PR is merged

@ofborg build python310Packages.pydantic-core


error: No such file or directory

error: No such file or directory (os error 2) will retry

Megi is moving this functionality into the kernel, and at the same time messing around with all the sysfs files I used. Please just use his kernel driver from now on.


Add Kepler Helm Chart to ArtifactHub

Now that we are hosting and indexing the helm chart for this repo on GitHub Pages from the work done in https://github.com/sustainable-computing-io/kepler-helm-chart/issues/7 we can now create an entry in ArtifactHub that will point people to this and show the versions including default latest version.
This is important for the adoption of Kepler, as ArtifactHub is the go-to for when folks want to search for new projects and they like ArtifactHub as it can help them to try charts faster without the hassle of forking repos then manually installing charts etc.
The following tasks are required for us to 'host' on ArtifactHub:
✅ Tasks

[x] Add New Org on ArtifactHub for sustainable-computing-io
[x] Add new repo on ArtifactHub for Kepler under the new org
[x] Associate new repo with new Org
[x] Add README.md to helm charts adding possible values for the chart
[x] Add meta data to this repo for artifact keywords etc
[x] Get the link for the URL of the Kepler logo that won't be deleted for ArtifactHub
[x] Add a badge to this repo for a link to ArtifactHub
[ ] Add signed, verified, and official badge to ArtifactHub for repo
[ ] Reference chart on Kepler docs repo
[ ] Add Maintainer's emails/names as owners to this org
[ ] Write blog

I have created an issue that depends on this being finished which relates to adding secrets in the repo so I can sign the helm chart.  Signing the helm chart does not change how users use it today it just gives them the additional option of verifying the signature is good and the package hasn't been altered. https://github.com/sustainable-computing-io/kepler-helm-chart/issues/23

We are now signed, verified, and official on ArtifactHub. I have also made a small blog and hopefully will be published in the next eBPF newsletter by Bill Mulligan

@bradmccoydev Thanks for the great work!


Upgrade xstream to 1.4.20.

Related to  https://github.com/spring-cloud/spring-cloud-netflix/issues/4277.

Thanks @OlgaMaciaszek !


How to use two filter_box to control two slice, and not to be interfered on the same dashboard?(divide and rule)

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
0.22
How to use two filter_box to control two slice, and not to be interfered on the same dashboard?(divide and rule)
explain:
slice_A can be controlled by filter_box_A
slice_B can be controlled by filter_box_B
slice_A can't be controlled by filter_box_B
slice_B can't be controlled by filter_box_A

http://superset.apache.org/faq.html#how-to-add-dynamic-filters-to-a-dashboard
There's work taking place with a much better dashboard app allowing for a notion of "scoped filters".


Document.onmousewheel event was removed from typescript

TypeScript Version:  3.4.0-dev.201xxxxx

Search Terms:
Code
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.

Expected behavior:
document.onmousewheel should be existed.
Actual behavior:
Intellisense & on build getting an error: Property 'onmousewheel' does not exist on type 'Document'.
Playground Link:
Related Issues:
I've noticed that this event was removed on the following commit from lib.dom.d.ts:
https://github.com/Microsoft/TypeScript/commit/79e5e79ef7724066889fbce97e9e6d6db4e746b5#diff-46fd87925e4552c166ec188712741c3f
I was wondering if it's a mistake or if there was a reason for the removal.

It was transferred to the Window, my bad :)

Any work on this? It just creates useless/wrong errors:


Radio button inside cell selects button in other cells

Hi, i'm trying to put my radio button inside a prototype cell, my problem is that when i pressed a radio button for example in cell 1, the radio button in cell 9 also gets selected. how do i solve this issue?

As long as each radio button in the cell is a separate instance. The problem should be resolved.

how do you make it into a separate instance? I'm creating a set of radio buttons inside a prototype cell. So those buttons will be dequeued and used again. I think that is what's happening.

One option is having an array of sets of radio buttons. You can fetch corresponded set of buttons by using cell index.


Refactor tiling tests

All inline tiles are moved to the tests/expected_tiles directory. This
separation brings the following benefits:

visual debug and comparison can be performed on images
test case is not polluted with png content

An helper method named `assertIsExpectedTile' is provided in the
RasterTestCase and is used to check result tiling against the expected
one.

Nice contrib, thanks.  Even works graphically inside github.  Certainly beats "reading" image code.


GOSA16 - Make User registration in firebase

Connect user registration UI to firebase and also add registration through google sign in.

assign me

assign me plz

@singhtaran1005 work on this

@singhtaran1005 Thank you for the contribution. You have recieved 10 points for the contribution. Your pull request is merged successfully


Implement connection timeout for Android

When a listening port is opened, a peer needs to connect to it within 3 seconds. Otherwise, the port must be closed.

Note that we have a test for this in testThaliMobileNative called 'Connect port dies if not connected to in in time' that should now be de-activated for Android but we need to re-activate when we fix this bug.

I'm not even sure this is a feature.