Publish HTML version of the book using GH Pages

@happi This is now done. The only missing part is enabling Pages for this repo.

Pages should now use gh-pages as source.

This seems to work correctly now. See:
https://happi.github.io/theBeamBook/


API doesn't work?

I get links, but they return the 403 error.

I get links, but they return the 403 error.

Have you added cookies to the request?


feat: update mock response for user profile

Added user_id and meta fields to user profile mock response.

Closing this, we can move this to https://github.com/zerodha/kiteconnect-mocks
Please open a PR in that repo, will pull it here and update the tests.


Environments with different platforms fail to solve in the same solve group

Checks

[x] I have checked that this issue has not already been reported.

[x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
[project]
channels = ["conda-forge"]
name = "pixitest"
platforms = ["linux-64", "osx-arm64", "win-64"]

[dependencies]
numpy = "*"

[feature.feat1]
platforms = ["linux-64", "osx-arm64"]
[feature.feat1.dependencies]
kubernetes-kind = "*"

[environments]
env1 = { solve-group = "prod" }
env2 = { features = ["feat1"], solve-group = "prod" }

Issue description
When trying to run a solve where

There are >=2 environments with the same solve group AND
A strict subset of the environments reference a feature whose platforms is a strict subset of the project's platforms AND
At least one dependency in this feature is not available for all of the project's platforms

the solve fails. For the MWE above, it fails with the following message:
  × failed to solve the conda requirements of 'prod' 'win-64'
  ╰─▶ Cannot solve the request because of: No candidates were found for kubernetes-kind *.

Expected behavior
The solve should be successful with:

env1 containing numpy for linux-64, osx-arm64 and win-64
env2 containing numpy and kubernetes-kind for linux-64 and osx-arm64

NOTE: The solve is successful when first removing the solve group and running pixi install, then re-running pixi install after re-introducing the solve group :eyes:

Great issue report!
This sounds like a reasonable extension of the solve-group feature. I would like to figure out where in the design this logic gets called, as I would also have expected it to skip the solve-group logic for the win-64 platform on env2.


Does it support server-side rendering?

I'm trying to use storyblok in my Nuxt.js project. But it shows window is not defined.
Is there any plan to support server-side render or I just missed something ?

Hey @Knovour server-side rendering can definitely be achieved since Storyblok only provides JSON via an API. I guess we can add a simple check for window to allow this plugin to be used with serverside rendering as well. This plugin actually only helps you to easily add the HTML comments (which are shipped in the draft JSON) in combination with the JavaScript bridge to be used as reference
to allow that editing.
I'll do some tests and release a new version if everything works as expected, btw. currently working on a Demo & Blogpost for Nuxt.js which should be ready next week!

Thank you
Is there a way to let Vue to call content from express or koa and still editable?

Absolutely - the editing doesn’t happen directly in your website it only happens in the sidebar in Storyblok.
I‘ve just finished a demo with jekyll & metalsmith - next to go is nuxtjs!

Hey @Knovour you can now have a look at https://github.com/storyblok/nuxtjs for SSR with Vue & Nuxt.

Thank you, I will try it on my project these days.
And hope the storyblok-vue will support it too.

The Directive is directly included in the project itself - so this directive won't be used in the NuxtJs example, but you will still be able to use v-editable="blok"!
https://github.com/storyblok/nuxtjs/blob/master/plugins/storyblok_bridge.js

This directive does not work with SSR. To work with SSR it needs a custom SSR-specific implementation.
More info here: https://github.com/nuxt/nuxt.js/issues/898


License discrepancy: MIT vs. Apache

The setup.py in the repo says the code is under the MIT license:

"License :: OSI Approved :: MIT License",

while the LICENSE file contains the Apache 2.0 license, which is confusing.
Could you please clarify which license this repo is under and fix one or the other file to ensure consistency?
Thanks!

Thanks for catching this!


[BUG] weather model bounds too small for larger grid sizes

for a user input cube_spacing_in_m of 50000, the interpolators (weather model locations) do not fully cover the study area.
For the config file below,  buffer has to be increased in the far range
For HRRR, both the near range and far range (and possible y direction) need to be increased.
Note this should not affect GUNW workflow which uses a smaller (weather model dependent) cube_spacing_in_m
aoi_group:
  bounding_box:
  - 33
  - 34
  - -118.25
  - -117.25
cube_spacing_in_m: '50000.0'
date_group:
  date_list: '20200130'
download_only: false
height_group:
  height_levels:
  - -500
  - 0
  - 500
  - 1000
look_dir: right
los_group:
  orbit_file: ./S1B_OPER_AUX_POEORB_OPOD_20210317T025713_V20200129T225942_20200131T005942.EOF
  ray_trace: true
time_group:
  interpolate_time: false
  time: '13:52:45'
weather_model: ERA-5

Download the orbit file with sentineleof eof -d 20210317 -m S1B

@bbuzz31 few thoughts:
The bbox is provided already and as long as the spacing is constructing a grid within the BBOX then you should be ok.
So I assume that the grid is changing the bbox to be bigger than the provided BBox. If that is the case then that new bbox extent is what should be get fed into the buffer code.
Separately we make it at least a weather model node bigger so we can translate the model cube to the user defined cube.
I also suspect this issue should not be model specific, but more a function of more apparent issue depending on high model resolution.


fix: improve UI for deletion of Sessions & Knowledge

Closes #29

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


Front page lacks date

It isn't clear if I'm looking at news from today, last week, last month...
or 5 years ago — well, I guess I can see it says "2023" on the conference dates

@SethTisue My original thought was what you see in the homepage won't need a date as that is what is current and latest edition.
When a new edition comes out, the previous edition moves to the sidebar with an archive date added.
What do you think is that good or shall I add a date to the current edition too?
Thanks.

@SethTisue now that I published the new edition, take a look to see what I mean (archive section):
https://www.scalanews.net/

that certainly helps, but I would still suggest showing the current date as well. it's still useful to know whether what I'm looking it is 0 days old or 6 days old. also the dates off to the side are there if I really look, but are easy to miss.
nearly ever blog and blog platform shows the date on the top post; Scala Times shows the date prominently; This Week in Scala shows the date prominently; it's what people expect

@SethTisue thanks for feedback. Will make that change.


A changed property in the context file does not get picked up immediately

See we have a class like this:
export class Context {
  a = "original";
  b = "original";

}

Then in the REPL we do:
context.a = "updated in REPL";
context.b = "updated in REPL";

Then we change it to this while the server is running.
export class Context {
  a = "original";
  b = "updated in code";
}

What should the values of a and b be at this point?
Expected:
a = "updated in REPL"
b = "updated in code"

Actual:
a = "updated in REPL"
b = "updated in REPL"

It works the way it does now because in the early stages when I was prototyping, I didn't want to go to the trouble of figuring out that b was updated in the code and a was not. As we're on the precipice of 1.0, it's time to fix that.

To make this work, I think we can keep a cache of the state of each context when it was last loaded using structuredClone(). Then when the context file is loaded again, we can check each property. If a property is different from the last time the file was loaded then we update the property. Otherwise we leave the property alone (because it might have been changed at runtime.)


Disable clear table

A few things before I can merge this pull request:

[ ] Fix the build error.
[ ] Squash your commits into one.
[ ] Add a commit message (that starts with "Fixes #188").
[ ] Give enableDataTable a better name that conveys its purpose/function.

Looks good otherwise.


ATV-55 | Use Red Hat base image for Python

Description :sparkles:
This PR changes the Dockerfile base image to Red Hat UBI for Python.

Security updates for images are handled by Red Hat
Images have been tested for usage in OpenShift

Issues :bug:
Closes :no_good_woman:
ATV-55: Change Dockerfile to use a Red Hat base image

It does work, locally the container always waits for the DB (in docker-entrypoint.sh) before continuing. In the entrypoint script we use the default postgres port if it hasn't been configured as an environment variable. On OpenShift environments the DB check is actually currently skipped (but I guess it should work there already).

Codecov Report

Merging #37 (2505f72) into main (1829e96) will increase coverage by 0.35%.
The diff coverage is n/a.

:exclamation: Current head 2505f72 differs from pull request most recent head eb96f2e. Consider uploading reports for the commit eb96f2e to get more accurate results

@@            Coverage Diff             @@
##             main      #37      +/-   ##
==========================================
+ Coverage   85.18%   85.54%   +0.35%
==========================================
  Files          48       47       -1
  Lines        1134     1093      -41
  Branches      108      103       -5
==========================================
- Hits          966      935      -31
+ Misses        126      119       -7
+ Partials       42       39       -3

Impacted Files
Coverage Δ

services/utils.py
84.37% <0.00%> (-0.48%)
:arrow_down:

documents/api/docs.py
100.00% <0.00%> (ø)

documents/api/querysets.py

documents/api/viewsets.py
90.07% <0.00%> (+1.10%)
:arrow_up:

atv/exceptions.py
92.50% <0.00%> (+6.78%)
:arrow_up:

Continue to review full report at Codecov.

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


Resolving of absolute paths with leading res:// and without result in different final paths

Operating system or device:
Windows 10 64 bit, in the editor.
Issue description (what happened, and what was expected):
const MyScript = preload("res://path/to/MyScript.gd")
const MyScript2 = preload("/path/to/MyScript.gd")

# later

print(MyScript.get_path())
print(MyScript2.get_path())
print(MyScript == MyScript2)

Expected output:
res://path/to/MyScript.gd
res://path/to/MyScript.gd
True

Actual output:
res://path/to/MyScript.gd
res:///path/to/MyScript.gd
False

If using preload("/path/to/MyScript.gd") style path is not recommended / not supported then there should be a warning as suggested in https://github.com/godotengine/godot/issues/3106

@Faless Fixed by #6702?

@Faless Fixed by #6702?

@akien-mga  Yes, it actually throws an error instead of just a warning, so users don't get confused. You can close this and also close #3106


Bug for multiple skycuts in dev branch?

Hi Pierre, Guido and all,
We've been looking at fitting multiple redshifts/skycuts using pybird and think we've identified a potentially important bug in the montepython class file, although it's not clear which branches this may be in, or if we've missed/modified something in our fork.
In correlator.compute, the redshifts are reordered such that the model is computed only for the middle bin and then rescaled by the growth factor appropriately for all other redshift bins. However, it looks the linear power spectrum from class is computed for the first redshift in the unordered list of redshifts specified in self.config (zfid in likelihood_class.__set_cosmo. If the middle redshift is different from the first redshift, this causes a mismatch between the linear power spectrum and growth factors.

Hi Cullan,
Yes it is possible that this is the dev branch that has seen multiple commits... I've checked that on the current commit the linear power spectrum is correctly computed for the middle redshift, see l. 847 in pybird_dev/pybird.py.
We'll make it clean when merging with master, meanwhile I am sorry I know the dev branch is a bit messy with frequent commits...


Warnings when running yarn dev

Not sure what they mean but they seemed odd to me.
⠂ source and transform nodesWarning: No slug found for "home/examples/a-component-using-external-plugins.md". Falling back to default "/home/examples/a-component-using-external-plugins.html".
Warning: No slug found for "home/examples/a-simple-component.md". Falling back to default "/home/examples/a-simple-component.html".
Warning: No slug found for "home/examples/a-stateful-component.md". Falling back to default "/home/examples/a-stateful-component.html".
Warning: No slug found for "home/examples/an-application.md". Falling back to default "/home/examples/an-application.html".
Warning: No slug found for "home/marketing/component-based.md". Falling back to default "/home/marketing/component-based.html".
Warning: No slug found for "home/marketing/declarative.md". Falling back to default "/home/marketing/declarative.html".
Warning: No slug found for "home/marketing/learn-once-write-anywhere.md". Falling back to default "/home/marketing/learn-once-write-anywhere.html".

Ah, yes. This warning means that there are markdown files in the content folder that have no associated [`template](https://github.com/reactjs/reactjs.org/tree/master/src/templates). This is probably not common for a Gatsby app, but in our case it's because we split the homepage up from what used to be the a single markdown file into multiple ones, pieced together by a "page" because of the unique layout constraints. (We left the text in the `content` folder though so it could be easily translated via the Crowdin effort.) I left a comment about it inline but I realize that's not super discoverable.
Anyway, just a bit of backstory. I should probably just remove the warning since it probably causes more confusion than it helps. :smile:

Removed this unhelpful log via 27293d63b


Caching of hdwallet provider failing and causing "replacement transaction underpriced" errors

Due to this issue, using a wrapper function that returns an hdwallet-provider in truffle-config fails. To fix that, we had implemented a hack that consisted in evaluating that function to obtain a single instance, and set it as a global provider.
Based on reports from users on zos 2.1.0, truffle 5.0.2, and hdwallet-provider 1.0.2, that is no longer working. Using the wrapper function causes "replacement transaction underpriced" errors, while removing it fixes the issue.
We need to check whether the difference is in zos, truffle, or hdwallet-provider, and re-enable caching the single instance of the provider, since the issue has been open on the provider for over 4 months and there are no signs of fixing.

Do we have more info about this issue? I've tested it with zos versions 2.1.0, 2.1.2 and 2.2.0 but I can't reproduce it neither on testnets (rinkeby, ropsten at least) nor on mainnet :disappointed:.

Reproduced using this truffle config, and pushing a project with 5 contracts:
    "rinkeby-infura": {
      provider: () => new HDWalletProvider(mnemonic, "https://rinkeby.infura.io/v3/KEY"),
      network_id: 3
    }

Failed to reproduce in 2.2.0. Closing the issue as it seems now fixed.

I am still experiencing this issue with zos version 2.2.1and truffle-hdwallet-providerversion 1.0.5. @spalladino Any ideas how to resolve this?

@spalladino FYI, after updating truffle from version 4.1.14 to version 5.0.6 the issue doesn't occure anymore.


Decorators like props.string do not works as expected. Attribute is not reflected to property.

Bug report

Skate version: 5.1.3
Affected browsers (and versions): any

Current behaviour
Please look at:

When properties are described by usage of static get props everything is works fine.
But for the same scenario and almost same code where property is described as @props.string name: string; the value from attribute is not reflected as property.
Expected behaviour
There should not be any differences between usage of decorators and static props property.

Seems that:

here propertyDefinition is undefinied because
property definition is only reflected in _propsNormalised and never in props constructor property

Probably the simplest solution for this problem will be to take the property Definition from _propsNormalised instead of props
P.S.
I tried to create PR but I used Windows and Ubuntu, on both I was not able install deps (npm which downloads 300MB/33K files (!sic) fails on post install) and the tests in master branch fails (some 6 tests fails).

Interesting. I wonder what is causing that to fail on your end. If you want to push a blind PR I'm happy to take it from there.


__del__ behavior on interpreter shutdown

When finishing program execution, python does not guarantee the order in which objects are destroyed.
Calls inside a __del__ method calling other objects or modules are not guaranteed to be correctly executed.
https://github.com/cupy/cupy/blob/master/cupy/cuda/stream.pyx#L185
It is known to fail because runtime module is already unloaded when __del__ is called.
https://docs.python.org/3/reference/datamodel.html#object.__del__
This can affect behavior on RAII pattern.

Maybe atexit module can be used?
https://docs.python.org/3/library/atexit.html

I think I tried registering the stream’s destructor with atexit and it didn’t work, but I don’t remember how exactly I did it, and I could do it wrong.
I think I also tried letting each stream instance hold a reference to the runtime module and it failed too. It seems the shutdown procedure doesn’t care about reference counting...

As pointed out at https://github.com/cupy/cupy/issues/2658#issue-525424530, the problem does not seem explained by Python's expected behavior?

I don't think I've seen this error before. Looks like runtime is set to None when stream.__del__() is invoked, but this is unexpected because, according to PEP 442, starting at Python 3.4 the modules unloaded during interpreter shutdown are no longer set to None, and I'm on Python 3.6.7.

Maybe is because of Cython?

Probably not Cython itself (as I tested several older and latest versions and the problem persists), but its bad interplay with Python. I also wonderEd if this could be a bug in Anaconda/conda-forge’s Python packaging, which I always use in production. Finally, it could just be a coincidence, but both bug reports (#2658, #2777) used CUDA 10.0.

I use CUDA 10.0 too.

We just found that if we install python with pyenv, then it breaks just with python -c 'import cupy; stream = cupy.cuda.Stream()'
Credit goes to @niboshi

Your pyenv is provided by the Linux distribution (apt-get, etc)?

Installed manually
Conda flags
-I$CONDA_PREFIX/include/python3.7m -I$CONDA_PREFIX/include/python3.7m  -Wno-unused-result -Wsign-compare -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O3 -ffunction-sections -pipe  -fdebug-prefix-map=/tmp/build/80754af9/python_1553721932202/work=/usr/local/src/conda/python-3.7.3 -fdebug-prefix-map=$CONDA_PREFIX=/usr/local/src/conda-prefix -fuse-linker-plugin -ffat-lto-objects -flto-partition=none -flto -DNDEBUG -fwrapv -O3 -Wall

Pyenv python 3.7.3 flags (python3-config --cflags)
-I$HOME/.pyenv/versions/3.7.3/include/python3.7m -I$HOME/.pyenv/versions/3.7.3/include/python3.7m  -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall


Rich push notification image apns payload in foreground

It is a very small issue: If an image is attached in the payload and the app is in foreground, the image doesn't show.
:)

When the app is in the foreground, by default a system notification is not displayed when a push notification arrives. This plugin adds support for foreground notifications by displaying a local notification when the FCM notification message arrives. As such, any additions to this local notification - e.g. an image in the payload - are a feature request rather than a bug.

It should be possible to add support for this by extracting the image URL from the APNS payload and inserting it into the local notification as a UNNotificationAttachment as outlined here

When the app is in the foreground, by default a system notification is not displayed when a push notification arrives. This plugin adds support for foreground notifications by displaying a local notification when the FCM notification message arrives. As such, any additions to this local notification - e.g. an image in the payload - are a feature request rather than a bug.

I receive push notifications with maximun priority level even when the app is in foreground, but if the app is in background and payloads have an image attached, the image is shown perfectly (but not in foreground)
I have android 9 One UI 1.1

It should be possible to add support for this by extracting the image URL from the APNS payload and inserting it into the local notification as a UNNotificationAttachment as outlined here

Request feature is for Android not IOS, was my mistake. Title updated


Duplicate non-aggregate type declarations, Opcode: TypeAccelerationStructureNV

A lot of shaders written for DXR/VK_NV_ray_tracing produces the following validation error.
Even though the shader works, we are probably declaring TypeAccelerationStructureNV twice in SPIR-V.
SPIR-V module not valid: Duplicate non-aggregate type declarations are not allowed.
Opcode: TypeAccelerationStructureNV id: 10734
  %10734 = OpTypeAccelerationStructureNV

This is probably a glslang issue, given that our output GLSL only declares things once. We’ll need to investigate and contribute a fix upstream.

This should have been fixed by https://github.com/KhronosGroup/glslang/pull/1645

Thanks @jeffbolznv. We will be updating the version of glslang that we depend on soon, so we should pick up the fix as part of that.
Hopefully once we have a new Slang release that incorporates the fix @Nimanf can confirm that the issue he's seeing is addressed and we can close this out.

I can confirm that this issue has been addressed with the latest glslang changes incorporated into #940. Closing this issue out.


Azure ML bundle artifact

Tested locally using art-def server. This is the current state of the artifact file for ML bundle:
resource "massdriver_artifact" "machine_learning_workspace" {
  field                = "machine_learning_workspace"
  provider_resource_id = azurerm_machine_learning_workspace.main.id
  name                 = "Machine Learning Workspace config file"
  artifact = jsonencode(
    {
      data = {
        infrastructure = {
          ari           = azurerm_machine_learning_workspace.main.id
          discovery_url = azurerm_machine_learning_workspace.main.discovery_url
        }
        security = {
          iam = {
            "ml_read_write" = {
              role  = "AzureML Data Scientist"
              scope = azurerm_machine_learning_workspace.main.id
            }
          }
        }
        specs = {
          azure = {
            region = azurerm_resource_group.main.location
          }
        }
      }
    }
  )
}

subscription_id, resource_group, and resource_name are used by the python SDK to auth to the ML workspace.
discovery_url outputs to https://westus.api.azureml.ms/discovery, which returns a JSON file that looks like:

{
  "api": "https://westus.api.azureml.ms",
  "catalog": "https://catalog.cortanaanalytics.com",
  "experimentation": "https://westus.experiments.azureml.net",
  "gallery": "https://gallery.cortanaintelligence.com/project",
  "history": "https://westus.experiments.azureml.net",
  "hyperdrive": "https://westus.experiments.azureml.net",
  "labeling": "https://westus.experiments.azureml.net",
  "modelmanagement": "https://westus.modelmanagement.azureml.net",
  "pipelines": "https://westus.aether.ms",
  "studio": "https://ml.azure.com"
}

Seems like this contains every URL a dev would need depending on how they are building their ML app. If it makes more sense to expose each URL manually to the user within the artifact file, I can definitely do that instead.

@chrisghill simplified the artifact by removing the extra fields, and moved the URL to infrastructure

After researching more about how a dev will be using the ML bundle, it boils down to 1 of 2 ways:

GUI ML Studio
Local dev using python SDK

Local dev w/ python SDK benefits from a config.json that contains the subscription ID, resource name, and resource group name. Even with the config.json file, the user still gets a prompt to authenticate using their Azure AD account. So even with the config.json file, it can't be used by a bad actor w/o Azure AD creds.


Install Issues off New Document

@howderek working from:
https://github.com/OSSHealth/ghdata/blob/master/devloperstartup.md
I'm still here with nothing below growth indicators:

The trace is here:

Try entering an owner and repo and pressing submit, if still nothing works send the log

Right on! Fully working. I was expecting something from FB Folly.

For sure! That was a placeholder when I was writing my CSS. I'll remove it!

Great.
On Wed, Apr 12, 2017 at 10:12 AM, Derek Howard<EMAIL_ADDRESS>wrote:

For sure! That was a placeholder when I was writing my CSS. I'll remove it!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/OSSHealth/ghdata/issues/39#issuecomment-293609480,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAoDUJbUheTS2klcgtOczz2gMoibAVN9ks5rvOncgaJpZM4M6hkw
.

--
Mutual of Omaha Associate Professor
Information Systems
College of Information Science & Technology
University of Nebraska Omaha
http://faculty.ist.unomaha.edu/mgermonprez/cv.txt


Refer to instances of ApplicationFunction as appFn

Stop using the names 'plugin' and 'app' to refer to instances of
ApplicationFunction.
This renames all variable names, but leaves the plugins folder in place,
to be renamed later

Partial fix for #632

Both stats and sentry are functions that match the signature of ApplicationFunction, and get passed into Application.load() along with any apps provided by the user on the command line and/or in the package.json. They're listed in an array named defaultApps.
From the code's perspective stats and sentry are identical in concept to a probot user's index.js (e.g the hello world app).
Saying it's an "app" when probot's user does it, but a "plugin" when it happens within probot's codebase is exactly the kind of mulitple-names-for-the-same-concept confusion I'd like to avoid.


Don't require all build script output to be utf-8

Build scripts often stream output of native build systems like cmake/make and
those aren't always guaranteed to produce utf-8 output. For example  German
MSVC cmake build has been reported to print non-utf-8 umlauts.
This commit instead only attempts to interpret each line as utf-8 rather than
the entire build script output. All non-utf-8 output is ignored.
Closes #2556

r? @brson

r? @huonw
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit 020db0d has been approved by brson

:hourglass: Testing commit 020db0d with merge 1c9a1ef...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64

Random comment on an old PR, but I hit this same issue with my sccache2 tool that wraps compiler execution. For the MSVC case, what you really want to do is convert from the system codepage, which works fine. (In general the problem is sort of unsolvable unless you want to just take the bytes from the program's stdout and write them using WriteConsoleA.) The code I used is here:
https://github.com/luser/sccache2/blob/ece0aee662dfd095093ef20d884461db22de0614/src/compiler/msvc.rs#L40

@luser just to clarify, did you hit this assertion or see any bad behavior because of this? I was hoping that this would cause Cargo to avoid all non-utf8 output and only look at lines which are utf-8, which in theory all cargo:foo=bar lines should be.

No, sorry, I mean "my project had the same problem dealing with non-UTF-8 output from MSVC".

Ah ok, thanks for the clarification! Also, thanks for the link!


JQuery Versioning

Hi Team,
I am using this widget in one of my application and this widget is using Jquery version 1.11.2 which is vulnerable to XSS scripting. So, I request you to update the Jquery version in this widget and Version should be greater than 1.12.0.
Waiting for your response..

I am working on updating a couple of widgets in terms of jQuery versions, starting with CKEditor. I will create an update for TooltipLink this week.

Hi,
Is this update done?

Hi Team,
Could anyone please tell me if jQuery update is done for this widget?

Hi Sowmya,
Unfortunately Jelte has not been able to finish his update for this widget.
From our previous conversation outside this issue thread I understand that you want to go ahead and create a pull request. (https://github.com/mendix/TooltipLink/pulls)
Is that correct?

Hi Salij,
Yes as its taking some more time for Jelte to do this update, if you provide me access to create branch and commit changes I will do this update from my side and let you know so that you can upload this to Mendix AppStore.
Thanks
Sowmya
From: Roeland Salij<EMAIL_ADDRESS>Sent: Wednesday, September 5, 2018 5:36 PM
To: mendix/TooltipLink<EMAIL_ADDRESS>Cc: Sowmya, Repala<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [mendix/TooltipLink] JQuery Versioning (#3)
EXTERNAL EMAIL   This email originates from outside Genpact. Be vigilant before responding, clicking on links or opening attachments.

Hi Sowmya,
Unfortunately Jelte has not been able to finish his update for this widget.
From our previous conversation outside this issue thread I understand that you want to go ahead and create a pull request. (https://github.com/mendix/TooltipLink/pulls)
Is that correct?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/mendix/TooltipLink/issues/3#issuecomment-418706181, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AoqlAAI_xdiINlKmKbRbZKqmJy1s45P7ks5uX74qgaJpZM4VQ2zs.

This e-mail (and any attachments), is confidential and may be privileged. It may be read, copied and used only by intended recipients. Unauthorized access to this e-mail (or attachments) and disclosure or copying of its contents or any action taken in reliance on it is unlawful. Unintended recipients must notify the sender immediately by e-mail/phone & delete it from their system without making any copies or disclosing it to a third person.

You can create a fork if you want, there are multiple tutorials on that.
When it comes to this XSS vulnerability, it is not applicable in Mendix. This only applies to AJAX requests made from jQuery, which is not done here. More information can be found here.
I am moving this issue to a lower prio as I have other projects I am working on

Well, this is embarrassing. TooltipLink does not use jQuery. Are you sure you are looking at the same widget? I am closing this issue.


Ssh.do: How to run pure computations on remote?

Pure computations always run on the local worker with the current Ssh.do implementation. How to compute whole data flow on remote?
For instance, let's think about the following code:
basedir = "/etc"
dirs <- Ssh.do { user: "user", host: "example.com" } (
    files <- File.listStatus basedir,
    dirs = (file <- files, [file.name | file.isDirectory]),
    Task.of dirs
)

At first glance, it seems that files are listed up and directries of them are selected on the remote server, and then the directories are returned to local, like the following shell script line:
echo /etc | ssh<EMAIL_ADDRESS>'xargs -L1 ls -lA | grep ^d | sed -E "s/([^ ]+ +){8}//"'

Actually it doesn't work so. Only actions are sent to and run on remote. Pure computations and the pipeline run on local like:
echo /etc | ssh<EMAIL_ADDRESS>'xargs -L1 ls -lA' | grep ^d | sed -E "s/([^ ]+ +){8}//"

Indeed. I see two approaches here:

Bring the data to the program (TopShell, second Bash example)
Bring the program to the data (first Bash example, and also MapReduce).

Shell scripts have a primitive but effective way to transmit and run a program remotely: Pack it into a string and ship it off to the target machine in the hope that it has the same flavor of shell preinstalled.
Doing the same thing for TopShell wouldn't be hard, but requiring the target machine to have TopShell preinstalled is rather inconvenient.
Another thing that counts against this approach is that you'd probably want to ship closures rather than just program strings.
A different approach
One thing I've considered is this:
basedir = "/etc"
dirs <- Ssh.doRemotely { user: "user", host: "example.com" } #(
    files <- File.listStatus basedir,
    dirs = (file <- files, [file.name | file.isDirectory]),
    Task.of dirs
)

Where #e is syntax for serializing the e expression to something that can be serialized, transmitted, deserialized and then executed on the target machine. Combined with a typing rule like if e : t then #e : Program t, some kind of mechanism to check that e can be serialized at all, and last but not least a way to actually run the resulting program on the target machine in the absence of a preinstalled TopShell.
Of course, this is still just a vague idea and would require a non-trivial amount of work to implement.
What's your thoughts on this? Do you have a different solution in mind?

If expressions themselves are serializable, like C#'s expression trees of lambda expressions, the special quasi-quoting syntax #e might not be needed. Moreover, it might let Program be a monad: giving ShellScriptProgram.of and ShellScriptProgram.flatMap, implementations of shell script builders, and then the binding syntax x <- e1, e2 would be available.
Other code builder implementations like JavaScriptProgram or SqlProgram are also able to introcude.


Enhancing visibility of commands on certain cards

Is your feature request related to a problem? Please describe
Commands on plot cards (as an example) tend to have bad visibility (usual use case: switch plot type):

Describe the solution you'd like
Some better visible UI element than the current kebab menu.

would it be an idea to be able to choose an icon for commands, like maybe from common menu ones: https://www.behance.net/gallery/89736895/Know-Your-Menu-?

would it be an idea to be able to choose an icon for commands, like maybe from common menu ones:

@Far0n is this just a cosmetic request or would this solve some UX problem? Just asking because we might consider it if it's the latter, otherwise one needs to live with the Wave's opinionated nature.

@Far0n is this just a cosmetic request or would this solve some UX problem? Just asking because we might consider it if it's the latter, otherwise one needs to live with the Wave's opinionated nature.

I had visibility in mind, because the kebab one seems difficult to spot sometimes.

Makes sense. I think this should be resolved with the fixed colors though. We could theoretically go for a hamburger, but that IMO usually means a big side menu is about to open. In fact, we use it for this exact scenario in the header IIRC. The kebab one is more subtle, but that's on purpose. It's just to add a small contextual menu after all so no need for high prominence.


[MM-36030] Allow for duplicate servers with different names to behave normally

Summary
When adding a server with a different name but the same URL, the app would crash due to differences between what the config was reporting as the server list, and what views actually exists. Now the config will filter on both the server name and URL, effectively allowing users to access the same server with multiple different names,
NOTE: You can still add the same server (ie. same name and URL) twice, it just won't cause a crash. We should be adding some validation on server creation to remedy this in a future ticket.
Ticket Link
https://mattermost.atlassian.net/browse/MM-36030
Release Note
NONE

NOTE: You can still add the same server (ie. same name and URL) twice, it just won't cause a crash. We should be adding some validation on server creation to remedy this in a future ticket.

Once we move the servers from the settings to its own dropdown we can probably add this, as there will be only one place to add/modify servers

@devinbinnie @Willyfrog Can this be cherry-picked, or is this fix risky?

I think it would be good to cherry-pick this, but I know we're getting closer to releasing 4.7. @jgilliam17 What are your thoughts?

@devinbinnie Please help cherry-pick ^

cherry-picked directly


Fix timeToLive type from DateTime to TimeSpan.

Description

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as a link to the swagger spec, used to generate the code.
[x] The project.json and AssemblyInfo.cs files have been updated with the new version of the SDK.

@pinwang81 I also do not see any tests for this breaking change? Could add at least a regression test for this change.

From DateTime to TimeSpan isn't a breaking change.  RP always only accept TimeSpan.  Having DateTime in the SDK was a bug that we are trying to fix.

RE: nit: Id instead of ID
This is auto-generated from swagger, which is checked in.  I do not want to make manual update to it.  We can update the swagger file next time around to make it Id instead of ID.

@pinwang81  Please include a link to the accompanying swagger specs pull request, per the checkbox you checked in the checklist above


[BUG] When trying to update, version 1.3.75 shows "Current"

Describe the bug
When clicking the update button in FVTT's module page, it doesn't update and tells me that v1.3.75 is current.
I know this is probably something unique as I haven't seen this reported by others. Just wondering if you may have any idea of what to try? I know I can export calendar, uninstall/reinstall, just trying to avoid if possible.
To Reproduce
I think the description above satisfies this section.
Screenshots

Foundry Information

Browser (please complete the following information):

OS: Windows 10 x64
Browser: Chrome
Browser Version: 101.0.4951.54

Hmm I have no idea why foundry would be saying 1.3.75 is newer than 2.0.1. I will look into why and see if I can fix it
In the mean time uninstalling and reinstalling will work just fine. Uninstalling doesn't remove any settings for the module so they will all be there still when you reinstall. That said making a backup of the world is always a good idea if you are worried about data loss 😁

Yeah I thought it was pretty odd also.  And yes, I backup religiously! haha

Please read these release nots about why this is happening https://github.com/vigoren/foundryvtt-simple-calendar/releases/tag/v2.0.4
The fix is to uninstall and reinstall Simple Calendar to get at least version 2.0.4 installed. After that this issue should not happen again.
Uninstalling and reinstalling the module will not remove any of your saved settings so there will be no data loss in doing so.
A quick explanation:
This has to do with the older versions of Simple Calendar having a v in front of the version number (eg v1.3.75) and the newer version not having that v (eg 2.0.4).
When doing the comparison of the first digits of the version, Foundry always treats one that starts with v as the newest version. Sadly there is nothing I can do now to fix this other than instruct people to Uninstall and Reinstall the module to get the latest version.

So this is happening to everyone then? I'm honestly surprised no one had mentioned it. There were at least a few issues from people on the new version but I guess everyone just grabbed the zip.
No worries about the uninstall/re-install. I figured that's would be the route I'd have to go anyway but I'm glad I brought it up now since it isn't just a unique issue.
I was going to close but I can imagine others may try to update through FVTT and come straight to issues (and possibly not check for closed issues) and therefore not see the release notes.  I'll leave it up to you to close or not.
Thanks for the help Vigoren!


NBT command needs NBT tag removal

Need to be able to remove an nbt value with the command.

Determined to be lack of meta after code inspection. My mistake.


The preview images before April are all displayed the same.(2023年4月之前的图片预览图展示全部一样)

Describe the bug
The preview images before April are all displayed the same
Steps to reproduce
You can view the pictures before April.
Screenshots or additional context
No response

Because the UUID was only added on April 3rd, the UUID values before this date are the same, resulting in the same preview image being parsed.
https://github.com/usememos/memos/commit/1cab30f32f737844090240434defdd834b01ea74

Execute the following SQL into your database or wait next release.
UPDATE
  resource
SET
  public_id = printf (
    '%s-%s-%s-%s-%s',
    lower(hex(randomblob(4))),
    lower(hex(randomblob(2))),
    lower(hex(randomblob(2))),
    lower(hex(randomblob(2))),
    lower(hex(randomblob(6)))
  );


customers: Check OFAC service with metadata

Issue: https://github.com/moov-io/paygate/issues/51

Codecov Report

Merging #54 into master will decrease coverage by 1.32%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #54      +/-   ##
==========================================
- Coverage    43.9%   42.58%   -1.33%
==========================================
  Files          15       16       +1
  Lines        1961     2022      +61
==========================================
  Hits          861      861
- Misses        909      970      +61
  Partials      191      191

Impacted Files
Coverage Δ

customers.go
27.73% <0%> (-1.84%)
:arrow_down:

ofac.go
0% <0%> (ø)

main.go
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[UT] make s3 ut more robust

Why I'm doing:
What I'm doing:
Fixes #issue
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[X] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[X] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto-backported to the target branch

[X] 3.2
[X] 3.1
[X] 3.0
[ ] 2.5

@mergifyio backport branch-3.2

@mergifyio backport branch-3.1

@mergifyio backport branch-3.0


UDP for FreeRDP

First i like freeRDP project, help me study windows programming
Is your feature request related to a problem? Please describe.
when i use freerdp connect windows server or win10
i use wireshark capture packet, free rdp always via tcp transport data
when i use windows application mstsc
the Application Data transport via RDUDP protocol
i found some about UDP for FreeRDP  https://www.hardening-consulting.com/en/posts/20230109-udp-support-2.html
and i found some about RDPUDP protocol code in freeRDP source code, but i don't know how it works
Describe the solution you'd like
want freeRDP support udp transport application data.
Describe alternatives you've considered
Additional context
freerdp connect win10

mstsc connect win10

thank you read the all, my english so sad. sorry

@marcellowy follow instructions at https://github.com/awakecoding/wireshark-rdp and you'll see all the traffic in clear in wireshark including RDPUDP (at least if it's MS-RDPUDP2)

@marcellowy follow instructions at https://github.com/awakecoding/wireshark-rdp and you'll see all the traffic in clear in wireshark including RDPUDP (at least if it's MS-RDPUDP2)

thank you for reply, i will do it and feedback results

@hardening thank you for reply again
I observed freeRDP use RDP protocol over TCP,  not over UDP, like this:

when use mstsc the RDPUDP2 protocol over UDP, like this:

i didn't find freeRDP client send data paket via UDP  to RDP server
or my compilation parameters are incorrect and udp is not enabled ?
i see mstsc client  actively send the first UDP packet, didn't see it at freeRDP

@marcellowy there's currently no UDP support in FreeRDP master, so no surprise here. But I have experimented a little the subject, more in private messages (you've already cited my blog posts).
Regarding mstsc captures, I've not implement various compressions at the "RDP level" (channels) in wireshark, so if you want better captures run mstsc with a .rdp where you have desactivated compression. Also if you have configured everything correctly you shall see egfx traffic and other dynamic channels within the RDPUDP packets.

@marcellowy as @hardening states there is currently no UDP support.  We have the long open issue #4978 for tracking. closing this as duplicated.


istio: ad_identifier proxyv2 discovers istio-proxy and istio-init

Additional environment details (Operating System, Cloud provider, etc):
Kubernetes 1.17.x(AWS EKS)
datadog-agent (image: datadog/agent:7) as DaemonSet
Steps to reproduce the issue:

In auto_conf.yaml, add proxyv2 to ad_identifiers
datadog-agent (re)start

i just followed this example:
https://github.com/DataDog/integrations-core/blob/master/istio/datadog_checks/istio/data/auto_conf.yaml
Describe the results you received:
Since istio-proxy and istio-init have the same container_name proxyv2, auto-discovery will discover both.
the result of agent configcheck is as follows:
=== istio check ===
Configuration provider: file
Configuration source: file:/etc/datadog-agent/conf.d/istio.d/auto_conf.yaml
Instance ID: istio:1b7ba935617675a0
istio_mesh_endpoint: http://<IP_ADDRESS>:15090/stats/prometheus
send_distribution_buckets: true
send_monotonic_counter: true
tags:
- image_name:istio/proxyv2
- kube_service.istio.io/canonical-revision:latest
- kube_deployment:sample-app
- short_image:proxyv2
- image_tag:1.7.2
- kube_container_name:istio-init
- kube_security.istio.io/tlsMode:istio
- kube_service.istio.io/canonical-name:sample-app
- docker_image:istio/proxyv2:1.7.2
- kube_env:dev
- kube_pod-template-hash:5d8786b6c4
- kube_istio.io/rev:default
- kube_namespace:default
- kube_app:sample-app
- pod_phase:running
~
Auto-discovery IDs:
* proxyv2
===
=== istio check ===
Configuration provider: file
Configuration source: file:/etc/datadog-agent/conf.d/istio.d/auto_conf.yaml
Instance ID: istio:9e09fd6a2c0d025d
istio_mesh_endpoint: http://<IP_ADDRESS>:15090/stats/prometheus
send_distribution_buckets: true
send_monotonic_counter: true
tags:
- kube_istio.io/rev:default
- kube_namespace:default
- kube_service:sample-app
- kube_pod-template-hash:5d8786b6c4
- kube_container_name:istio-proxy
- short_image:proxyv2
- kube_service.istio.io/canonical-revision:latest
- docker_image:istio/proxyv2:1.7.2
- kube_env:dev
- pod_phase:running
- kube_deployment:sample-app
- kube_service:sample-app
- image_name:istio/proxyv2
- image_tag:1.7.2
- image_name:docker.io/istio/proxyv2
- kube_service.istio.io/canonical-name:sample-app
- kube_security.istio.io/tlsMode:istio
- kube_app:sample-app
~
Auto-discovery IDs:
* proxyv2
===

so there is two checks which have same host and different container.
this would cause the result to be double the number when aggregated by, for example, sum function.
Describe the results you expected:
can I get metrics only via the istio-proxy container?
i guess collecting the metrics via the istio-init container is unnecessary.

i found a workaround, patch datadog-agent's env and set 'name: istio-init' to 'DD_CONTAINER_EXCLUDE'

Hi @kazukousen ,
Thanks for bringing up this issue! The Datadog autodiscovery uses the container short image name to identify containers. Since they are the same for istio-proxy and istio-init, it's a little harder to differentiate. Another alternative would be to use custom autodiscovery container identifiers: https://docs.datadoghq.com/agent/guide/ad_identifiers/#custom-autodiscovery-container-identifiers

thanks @ChristineTChen
Using custom auto-discovery container identifiers is going to be solving this issue.
but, i think this problem occurs in today's example.
I felt that the current example, which allows the ad_identifier to be set to proxy_v2, was confusing to users and could be improved.
thanks


Privacy and Policy must be aligned

Privacy and Policy must be aligned to provide better visuals, it is overlapping,

@dhairyagothi , please assign me under Gssoc'24 and Hacktoberfest.

I really like your application and want to work on your project ,please assign this issue to me under gssoc-ext 2024

I really like your application and want to work on your project ,please assign this issue to me under gssoc-ext 2024

Make PR asap


Support OpenRouter.ai

Many people avoid having an abundance of subscriptions by purchasing tokens from https://openrouter.ai/ instead.
Would be great to be able to just supply an OPENROUTER_TOKEN instead of openai and anthropic.

Open AI compatible Support would be greate for use free GIT Hub Models Like Open AI 4o / Mini.
Also Mistral and Gemini API  Support would be greate

Yes please! Openrouter here will be a perfect fit.

pls

agreed 👍

The problem is that OpenAI is used for its embeddings.
OpenRouter also provides the LLM of OpenAI, but NOT its embeddings!
😞


write script to take list of blocked email address' from auth0 and delete user accounts from db

Hey @ascott have you run the script yet? hopefully you can run it again...
i have just spent the last hour going through the auth0 users list and blocked probably 300 more users, and counting... im only on 2 months back so far in my sweep, and it appears to have started over 9 months ago. some of the spam addresses are effoby, nedoz, protonmail, etc there are about 10 that I can tell right away are spam. however, there are also probably hundreds more that should be deleted but I can't verify that they're spam for sure because I cant check their profile pages - they look like suspicious accounts, but its super hard to tell for sure since many are gmail and outlook accounts but with odd names that sort of look like they could be legit.
I think this script is a good first step, but Is there any way to beef up spam blocking before they are allowed to create profile pages in the first place? i would say add a captcha or something but we're not sure if we're dealing with people or bots. perhaps we do need that dashboard / admin page we discussed to provide a way for an admin to find a user profile by searching for an email address on the site, if there's no way to stop these people/bots from creating accounts.
anyway, long story short, ill keep going through this sweep and let you know when ive gone through the entire list and deleted the obvious ones. we can chat more on our call tomorrow.

Hey @ascott have you run the script yet? hopefully you can run it again...
i have just spent the last hour going through the auth0 users list and blocked probably 300 more users, and counting... im only on 2 months back so far in my sweep, and it appears to have started over 9 months ago. some of the spam addresses are effoby, nedoz, protonmail, etc there are about 10 that I can tell right away are spam. however, there are also probably hundreds more that should be deleted but I can't verify that they're spam for sure because I cant check their profile pages - they look like suspicious accounts, but its super hard to tell for sure since many are gmail and outlook accounts but with odd names that sort of look like they could be legit.
I think this script is a good first step, but Is there any way to beef up spam blocking before they are allowed to create profile pages in the first place? i would say add a captcha or something but we're not sure if we're dealing with people or bots. perhaps we do need that dashboard / admin page we discussed to provide a way for an admin to find a user profile by searching for an email address on the site, if there's no way to stop these people/bots from creating accounts.
anyway, long story short, ill keep going through this sweep and let you know when ive gone through the entire list and deleted the obvious ones. we can chat more on our call tomorrow.

@jesicarson the script is done and on prod, but i have not run it yet.i was planning on running it tomorrow morning, and it can be run again in the future, as more users are blocked via auth0.
about protonmail users, I don't know that all prontonmail email address' are spam. it is a legit encrypted mail provider: https://protonmail.com/, and some spammy users may be using it but i don't think that means all protonmail users are spam.
discussing a better process/handling of spam on our call is a good idea. 👍

@jesicarson the script is done and on prod, but i have not run it yet.i was planning on running it tomorrow morning, and it can be run again in the future, as more users are blocked via auth0.
about protonmail users, I don't know that all prontonmail email address' are spam. it is a legit encrypted mail provider: https://protonmail.com/, and some spammy users may be using it but i don't think that means all protonmail users are spam.
discussing a better process/handling of spam on our call is a good idea. 👍


Add support for jiva csi volume upgrades

Upgrade support for jiva csi volumes on a release basis.

Currently the jiva-operator creates the controller and replica workloads(deploy/sts/svc) without the version labels. The same is the case with the operator and csi yamls in jiva-operator. We need to update those first and then move on to this issue.


How to create new Function ID signatures

Hey,
Last question, I've read all the docs and can't find any references to buliding new function ID signatures, I wanted to build fID sigs for core c functions like strcpy as currently it doesn't correctly name the variables, and for some reason won't keep the names I give it.
How would I go about building a new FID set?
I'd also like to make some for the WDK
As an example, the types and naming for a known function is messed up:

and if I copy the declaration from the msdn docs: https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/strncpy-strncpy-l-wcsncpy-wcsncpy-l-mbsncpy-mbsncpy-l?view=vs-2017
Ghidra can't understand const char, how would I go about correctly filling this in? I don't want to make a new issue as I'm sure it's just me being dumb.

%Ghidra%/Features/FunctionID
The file common_symbols_win32.txt contains the symbols that were considered common when generating the
.fidb files for Windows 32-bit system code.
The main entry point for building adding libraries to a .fidb file is the dialog
Tools -> Function ID -> "Populate FidDb from programs ...".
This takes on optional file parameter called "Common Symbols File".  The .fidb files currently being
distributed with Ghidra were generated by supplying common_symbols_win32.txt here.
After a library is built, starting from this dialog, a final window provides a list of the most
common symbols encountered for that particular library.  For Windows system code, the top 70 or so symbols from
each list, generated for the libraries listed below, were merged and deduped to produce the final common_symbols_win32.txt.
Visual Studio 1998 Debug
Visual Studio 1998 Release
Visual Studio 2003 Debug
Visual Studio 2003 Release
Visual Studio 2005 Debug
Visual Studio 2005 Release
Visual Studio 2008 Debug
Visual Studio 2008 Release
Visual Studio 2010 Debug
Visual Studio 2010 Release
Visual Studio 2012 Debug
Visual Studio 2012 Release
Visual Studio 2015 Debug
Visual Studio 2015 Release
Each .fidb was generated by supplying common_symbols_win32.txt as the "Common Symbols File" parameter.
After this completed, adjustments were performed by running the RemoveFunctions.java script on the database.
This makes the following modifications:

Auto-fail is set for functions which match a list of full hashes.
Auto-fail is set for functions whose name matches specific regular expressions.
Force-relation is set for functions which match a list of full hashes.
Force-specific is set for functions which match a list of full hashes.
Auto-pass is set for functions which match a list of full hashes.

Auto-fail means a full-hash match will not be returned under any circumstances (even though the function is still in the database)
Force-relation means a full-hash match will only be returned if one of the function's parents or children also matches.
Force-specific means a full-hash match will only be returned if the specific hash matches as well.
Auto-pass means a full-hash match is always returned, even if the function is tiny.
The final .fidb was defragmented using the RepackFid.java script to make the disk image as small as possible.

Can these txt files contain parameter names? How did you generate this initial list, is it just the mangled symbols list?

Also I'm right in saying there's no way to build that text file from within ghidra right? If you've got a library like libc.so loaded, and everything renamed, there's no way to export that into the format for fID?

Additional information in ghidra help, search "Function ID Plug-In", i think it's what you need.

Ah, I didn't have the debug tools enabled. Thank you, it might be worth making an issue for an enchancement to make it easier to hash individual functions


inline images in repro steps from Jira not coming after migration in azure devops

Describe the problem
Inline images in repro steps (in Item Info) from Jira not coming after migration in azure devops (checking in repro steps).
Instead of the image getting this -  !image-2023-11-17-12-09-02-249.png|width=799,height=421!
Very similar to this github issue - https://github.com/solidify/jira-azuredevops-migrator/issues/114
just that I am getting in repro steps the problem
Also tried to use the mapper - MapRendered in the mapping but after that the repro steps got blank in azure
To Reproduce
Steps to reproduce the behavior:

Try importing a bug with repro steps having images in it

Tool version

Version of the jira-azuredevops-migrator tool - 3.0.115 (also tried on 3.0.250 but same behaviour)
Attachments

Please attach the following files:

config.json
jira-export-log.txt
wi-import-log.txt

config-agile.json
jira-export-log-231121-161953.txt
wi-import-log-231121-164942.txt
Screenshots

Usually you will want to migrate the description to ReproSteps, like this:
      {
        "source": "description",
        "target": "Microsoft.VSTS.TCM.ReproSteps",
        "for": "Bug",
        "mapper": "MapRendered"
      },

Or is Repro Steps a custom field in your case? In that case, possibly related to https://github.com/solidify/jira-azuredevops-migrator/issues/602

Yes Repro Steps is a custom field that we are using in which all the screenshots etc we put, in description generally just plain text we put in our case. Is there any way you can suggest to work out images in Repro Steps.
In issue  - https://github.com/solidify/jira-azuredevops-migrator/issues/602 it mentions first revision is migrated but in my case after using MapRendered I am getting completely blank in Repro Steps in ADO.

Gotcha. Most likely it is because the tool is trying to append the string "$Rendered" to the field id, as this is how description and other HTML fields work in Jira. Custom fields do not work this way however, so a fix is required on our part.
I am marking this issue as a bug report.

@shweta22992, can you run the exporter with the setting "log-level": "Debug" in your configuration, and let me know what the output becomes for your ReproSteps field in the log? It should say something about which field it is trying to export and what the transformed value becomes.

@Alexander-Hjelm attaching the export log file.
jira-export-log-231123-103627.txt
' to field 'Microsoft.VSTS.TCM.ReproSteps' is what I could see in the log.
Also if possible can you pls let me know in how much time can we expect a fix for the bug.

I see a lot of these for example:
[D][10:36:50]    Mapped value '*Server: PSP*
*tFDB:  thinkfolio_222nathann*

*User: rfurbear*
*Portfolio(s)/Group(s):  Any*
 * Make sure that this Admin option is set like this

!image-2023-11-17-11-39-01-307.png|width=579,height=389!
 * Set up a CDS trades - click on Open OTC position and select CDS

!image-2023-11-17-12-07-41-345.png|width=538,height=248!

 - make sure to set the deal date a day back . This a key point here .

*!image-2023-11-17-12-09-02-249.png|width=799,height=421!*

*!image-2023-11-17-12-09-29-084.png|width=753,height=392!*
 * Save the trade at Working  and as you can see here the accrued  is positive and this is what the trademarketside will look like at this point.

*!image-2023-11-17-12-11-15-937.png|width=628,height=259!*
 * Run a tE15 – with a specific load source with no data.- run te15 with sloadsource 'nope'

!image-2023-11-17-11-16-25-901.png|width=549,height=283!

*Expected Result: Accrued doesn't change and there is no error*
*Actual Result:* Accrued has become negative change and there is an error in the logs

{*}!image-2023-11-17-12-19-44-651.png|width=649,height=245!{*}{*}{*}{*}{*}

*!image-2023-11-17-12-27-39-073.png|width=1234,height=724!*

{*}Screenshot(s){*}:' to field 'Microsoft.VSTS.TCM.ReproSteps'.

Which should indicate that the value got mapped correctly.
Unfortunately it is hard to give an estimate at the moment, since I'm the only resource from our side who is actively working on this project, and at the moment there are other pressing needs. We always welcome community contributions though. And if you need prority support, contact us at<EMAIL_ADDRESS>to inquire about consulting services.

One point I missed to mention the above log comes when not using MapRendered and when I add this mapper then ReproSteps get miss from the log file. Attaching the log file after MapRendered.
jira-export-log-231124-124033.txt
Will discuss with my team regarding the priority

@shweta22992 what field type is your Repro Steps field in Jira? I tried to reproduce the issue for Jira Cloud, but when creating a new field I cannot seem to find any field type that resembles anything like "Html tect field" or similar.  The closest field type I can find is Text Field (multi-line), but that one does not have support for inline images, etc...

@Alexander-Hjelm it is just like the description field that we have for a bug in JIRA, it has type Wiki Style Renderer.

Ok! It looks like only Custom fields of type "Free Text Field (unlimited text)" or "Text Field" supports the Wiki Style Renderer.
I will try and reproduce this problem as soon as I can,

Issue closed with merge of PR https://github.com/solidify/jira-azuredevops-migrator/pull/918, please reopen the issue and tag me if the problem persists.

@Alexander-Hjelm I tried the latest release but the issue is still there for me. Image doesnt come and if I use MapRendered then it becomes blank.
jira-export-log-231129-110224.txt
wi-import-log-231129-110256.txt

Also not getting the option to reopen, if you can pls reopen at your end . @Alexander-Hjelm

Demoting to support issue.
As I stated in #919, please make sure you have read through the FAQ on mapping and troubleshooting custom fields, I suspect you will find your answer there: https://github.com/solidify/jira-azuredevops-migrator/blob/master/docs/faq.md
I suspect that you have tried to enter the jira field name without using "source-type: "name"` in the configuration :)

Thanks, working now after adding the "source-type: "name" in config. Closing the issue.

Perfect! :)


Complain if expect is passed multiple arguments

Summary
When using unexpected it's common to import it under the name expect. Consider this case:
import expect from 'unexpected';

it('should be unexpected', () => {
  expect(true, 'to be false');
});

If a user by accident forgets to import unexpected, they will not immediately notice, as the builtin expect in jest will ignore any further arguments passed to it. Which will result in a passing test instead of the failure you would expect.
This PR adds a check to the expect method, so that it will throw an error if it is called with more than one argument.
@Munter already discussed a solution to this with @cpojer. The solution I implemented here is a bit different. Instead of using a check on arguments.length I opted to use ...rest and check that it has a length of 0. The expect method was implemented as an arrow function, and arrow functions do not expose arguments, so it was either refactoring it into a normal function or using the ...rest alternative. From my humble benchmarking I didn't observe any significant difference, so I opted for the least invasive change, that also happens to be following the Code Conventions the closest - prefering es6 syntax where possible.
To further enhance the check one could add a check for the case of expect being called with no arguments. It's less likely to cause users to shoot themselves in the feet, so I left it out.
Test plan
The test implemented covers the case that the check is implementing.
All tests in the project is passing. I ran yarn test in the root of the repo to verify that the change had no unintended side effects.

Discussion was in jest-core #general on Aug 9th

Sounds good, and still enables us to allow more arguments in the future if we want to.


dx12: support individual command buffer reset

dx12::RawCommandPool now holds a collection of ID3D12CommandAllocator,
introducing a new one each time a new command buffer is allocated.
dx12::RawCommandPool::reset() now performs a reset() on each allocator in
the collection, mimicking the prior single-allocator behaviour.
dx12::CommandBuffer::reset() now handles the release_resources flag by
reseting its allocator.
Fixes #2140
PR checklist:

[x] make succeeds (on *nix)
[ ] make reftests succeeds*
[x] tested examples with the following backends: dx12
[ ] rustfmt run on changed code*

*make reftests fails here:
Warding DX12:
        Scene 'basic':
thread 'main' panicked at 'assertion failed: `(left != right)`
  left: `0`,
 right: `0`', src\warden\src\gpu.rs:1152:9

I haven't looked too closely into this, but it also fails with the patch reverted. Other than this, there are 15 passing reftests.

*rustfmt --check requests many changes (not limited to things inserted in this patch), but I believe the style of the code added in this patch is consistent with the rest of the file.

TODO: add a test (I'm not sure how easy it will be to simulate an EOM reliably to verify that it doesn't happen with the patch applied, though).

Thank you for the PR!
Let's wait a bit for @msiglreith to have a look at it.
In the meantime, individual command buffer reset is only needed for command pools created with RESET_INDIVIDUAL flag. We aren't currently checking for it. Would we get a simpler code path (in terms of run-time costs mostly, since implementation wise it will only make more code) for those command pools that don't need individual resets?

In the meantime, individual command buffer reset is only needed for command pools created with RESET_INDIVIDUAL flag. We aren't currently checking for it. Would we get a simpler code path (in terms of run-time costs mostly, since implementation wise it will only make more code) for those command pools that don't need individual resets?

so, a few different ways come to mind, what do you prefer? they all seem to make it more complicated than always behaving as though RESET_INDIVIDUAL were specified, though.

store the create flags in RawCommandPool, and always use the first-created allocator for all command lists
allocator is an enum variant of either a raw allocator, or a vector of allocators
create a trait that handles different strategies for the allocators "allocator_for_new_command_list()" and "reset()", I guess --- and store a Box  of the trait object in place of a variant or extra bit flags.
the entire RawCommandPool struct is generic, with implementations for RawCommandPool<ComPtr<d3d12::ID3D12CommandAllocator>> and RawCommandPool<Vec<ComPtr<d3d12::ID3D12CommandAllocator>>>

I like the (2). But let's make this work only if there is a promise of run-time advantage (less work to do) for those pools not supporting individual cmdbuf resets.

Regarding optimization for indiviual resets let's follow the proposal here as we also have to take into account multiple command buffers recorded at the same time.

Regarding optimization for indiviual resets let's follow the proposal here as we also have to take into account multiple command buffers recorded at the same time.

I don't fully understand what the proposal is wanting to do. In this bug, it sounds like we're wanting to only keep multiple allocators if requested --- but it sounds like you want to always support multiple allocators, but only allocate them if needed (if an allocator is being recorded while a new one is being allocated)?

We basically have to take care of two things in D3D12 for emulating the behavior of Vulkan (beside the large memory preallocations..):

Releasing the memory of command allocators to avoid OoM (requires allocator release + recreate)
Supporting to record multiple command buffers at the same time per pool (Vulkan concept)

With respect to the 2nd point we don't really have control over how many allocators we will need. Therefore, I would just store them in a Vec and create new allocators on demand (#allocators >= #command buffers currently recording)
For the 1st aspect we also need one pool per command buffer in case of indiviual command buffer reset. If we only have one allocator we wouldn't be able to tell when we can release the underlying allocator. In this case #allocators must be equal to the number of command buffers allocated from the HAL/Vulkan pool.

What conditions would allow for that safely? allocator.clone().as_unknown().Release() == 1?

As mentioned above for the individual reset case (as it is here) the buffer more or less owns the allocator, so it's always safe to release the pool and recreate one. Note that cloning will increment the internal reference counter so we actually end up with the same internal ref count after the Release call as before the operation.

These are actually more or less optimization, so the PR is also fine without this further changes.
I'm just noticing that it's still quite a bit of work to grasp all the details between Vulkan's and D3D12's approach and implement it.

This still doesn't release any allocators until the CommandPool and all of its CommandBuffers have been dropped (assuming all the addref/release logic is sound)

As mentioned above for the individual reset case (as it is here) the buffer more or less owns the allocator, so it's always safe to release the pool and recreate one. Note that cloning will increment the internal reference counter so we actually end up with the same internal ref count after the Release call as before the operation.

Right, I wrote that thinking this was RawCommandPool doing this.
Still, RawCommandPool and CommandBuffer both hold a reference to the allocator, so dropping it in the CommandBuffer doesn’t really destroy it. Dropping it twice would leave an invalid ComPtr in RawCommandPool, which would break RawCommandPool::reset();
So, like you say, CommandBuffer could reference back to the pool, and ask the Pool to remove that ComPtr from its list, effectively dropping it (but I’m not sure how speedy all this would be, if that matters).

If it doesn't work with ComPtrs let's just fallback to pointers. ComPtr will be replaced anyway once https://github.com/gfx-rs/gfx/pull/2374 lands. (WeakPtr is basically just a pointer which needs to be manually tracked)
I'm not sure what's the best way to handle it, but at some pointer in the future we need to do else the pool will just eat away all out memory :<

So, I understand:

CommandBuffer::reset() can happen on any different threads
CommandBuffer needs to be able to have the Vec drop an allocator

So, we need to rethink this a bit.

hold a reference to RawCommandPool (a RefCell or unsafe pointer?), and synchronize access to the Pool's allocators via a mutex
use a mpsc::Sender to notify the RawCommandPool's owner thread that it needs to drop an allocator from the vector.

ehh - let's look what's the result of https://github.com/KhronosGroup/Vulkan-Docs/issues/802 before we start to fiddle with mutexes or lock-free queues :D
As mentioned we can also postpone it for now, we are also kind of blocked a bit.

Is this PR getting stale? I thought there are no blockers atm. Ping @caitp

Looks fine to me, needs rebasing tho

is there a good reason we have explicit destroy_command_pool methods, instead of just drop() --- and the destroy() methods don't borrow mutably?
I ask because it seems there's no guarantee that the command pool will actually be dropped after destroy_command_pool is called, and it's not possible to clear the allocators vector because destroy_command_pool() doesn't borrow the pool mutably, so it will have an array of dead allocators which would probably crash if destroy_command_pool is called twice, --- or if anything continues to reference one of the allocators.
it seems safer to just implement Drop for everything, and allow users to control the lifetime of these objects with Rc/Arc if they wish to.

WeakPtr is Copy, so we can't implement drop for it,  We could ofc implement it for CommandPool but I'm not sure what would be the advantage as we have explicit Device::destroy_command_pool calls anyway. Feel free to move towards destroy(&mut self) or even self.

WeakPtr is Copy, so we can't implement drop for it, We could ofc implement it for CommandPool but I'm not sure what would be the advantage as we have explicit Device::destroy_command_pool calls anyway. Feel free to move towards destroy(&mut self) or even self.

yes, I specifically was referring to the gfx-rs wrappers around the native bindings, because the explicit destroy calls technically leave open the possibility of accessing invalid memory, but if we used Drop instead, that should be impossible

anyways, rebasing has been done --- we still don't destroy the allocator if release_resources is true, because a dead WeakPtr would still be in the RawCommandPool, and might be dereferenced again via destroy_command_pool().

bors r=msiglreith


Make udp_server_test pass on Mac, which does not have IP_PKTINFO as a meaningful setsockopt

Fixes #8386

Merging with fire since failures unrelated


Segfault in map_coordinates

Hello,
My code produces segfault in the map_coordinates function (when it calls _nd_image.geometric_transform). It seems this segfault is linked to the values/size of coordinates array.
numpy.__version__ = 1.7.1
scipy.__version__ = 0.12.1
test on 64bits linux (kernel 3.10)

To reproduce:
im = np.random.random((48000, 5984))
gr = (np.random.random((255492992,2)) * 50000).astype('f')
map_coordinates(im,gr.T,order=3,mode='constant',cval=np.nan,output=np.float64)

Is it really a segfault? On my machine, it fails with a MemoryError on the second line. Which is as graceful as it can get, I'd say.

Yes, it is. You need at least 4,5Gb just for im and gr plus few Gb for map_coordinates which generates some arrays.
I don't have access to my work machine until may, 9th but I checked my original data with scipy-current and the segfault is still present. Unfortunately I cannot reproduce it with random matrixes on current.
I'll check this bug in depth next week with gdb on scipy-current.

I debugged my code with gdb on scipy-0.12, the segfault is in the NI_GeometricTransform function. The value of idxs[hh] seems to be too big.
Catchpoint 2 (signal SIGSEGV), 0x00007fffea717294 in NI_GeometricTransform (input=<optimized out>, map=<optimized out>, map_data=<optimized out>, matrix_ar=<optimized out>,
    shift_ar=<optimized out>, coordinates=<optimized out>, output=0x729a060, order=3, mode=4, cval=<optimized out>) at scipy/ndimage/src/ni_interpolation.c:592
592                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Float64);
(gdb) l
587                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Int8);
588                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Int16);
589                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Int32);
590                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Int64);
591                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Float32);
592                         CASE_INTERP_COEFF(coeff, pi, idxs[hh], Float64);
593                     default:
594                         PyErr_SetString(PyExc_RuntimeError,
595                                                         "data type not supported");
596                         goto exit;

#define CASE_INTERP_COEFF(_coeff, _pi, _idx, _type) \
case t ## _type:                                    \
    _coeff = *(_type*)(_pi + _idx);                   \
    break;

I tried to reproduce it with scipy-0.17 and current but the bug has been corrected on those versions.

Thanks for checking. By now scipy 0.12 is really recommended to upgrade from.


Improved status sharing between ERT and SUMO

Number of realizations.

Today SUMO assumes number of realizations based on max. real number found in uploaded data.
ERT can easily add a new environment variable stating number of realizations, and expose this in the same pre-ensemble workflow that fmu-dataio is using today for registering an interation/enmseble.
One complication is that sometimes apparently an ensemble is started/splitted between different users (to better utilize cluster resources, which are currently allocated per user). I.e. might need to ensure that the different runs for the different users (which formally is part of the same ensemble).

Status

Post-simulation workflow - poll ERT storage and update SUMO realization metadata.

I also learned this yesterday. I guess it would be relatively easy to implement expected realizations into the case object in the metadata, e.g.
fmu:
  case:
    name: MyCase
    uuid: <uuid4>
    expected_realizations: 39

Not thought through, so don't implement this directly 😬. But as a concept, I think it should work.

Relevant? https://github.com/equinor/ert/issues/2359


incorrect sizing

hi there, just wondering if anyone else has run into any problems with scrollbars being incorrectly sized. I can't figure out if it's just me or if it's the plugin. I am using the plugin inside of an app that i'm building using backbone marionette. I only init the plugin after inside of onAttach functions, or after the element has been put into the dom, but with the dynamic content i'm loading in asyncly the scrollbars I'm getting are not quite reflective of the amount of content there is. Well, I should say that I'm not sure if it's because of the padding i have on the wrapper inside of the div i'm calling the plugin on, or if it's the content that's being brought in. Has anyone else gotten this problem?

I can help if you provide simple example with incorrect behavior. This problem does not look simple - maybe problem is with initialization or destroying previously initialized scrollbar, maybe problem with re-creating scrollable DOM element when all events are lost. There can be several reasons and I need simple example to say what exactly is wrong

so this is what i use to init each element. Basically, i pass an element into a global module that takes care of making sure that i have not already inited it, and that it gets set up with the right closure / events so that it triggers some global events on my app object.
var scrollbars = $();
var setupScrollbar = module.setupScrollbar = function (els) {
    return $(els).each(function (idx, el) {
        var lastObj, previous = [0, 0];
        var scrollFinishedDebouncer = _.debounce(function () {
            unmarkScrolling(lastObj.scrollx.scroll);
            unmarkScrolling(lastObj.scrolly.scroll);
        }, 500);
        if (scrollbars.index(el) === -1) {
            scrollbars.push(el);
            $(el).height();
            $(el).scrollbar({
                onUpdate: function () {
                    this.container.css({
                        height: 'auto'
                    });
                },
                onScroll: function (y, x) {
                    if (lastObj) {
                        lastObj = this;
                        if (y.scroll !== previous[1]) {
                            markScrolling(this.scrolly.scroll);
                        }
                        if (x.scroll !== previous[0]) {
                            markScrolling(this.scrollx.scroll);
                        }
                        app.trigger('global:body:scroll');
                        scrollDebouncer();
                        scrollFinishedDebouncer();
                    } else {
                        lastObj = this;
                    }
                }
            });
        }
    });
};

Hi.
I'm sure your code can be rewritten better way. Try next thing: before updating scrollable element/its content, just destroy custom scrollbar and init it again after update - it will make your code clear and short.

if you read the code, you will clearly see that i never init the scrollbar on the same element 2x

I've read your code, but it does not explain what's wrong happens in your environment

why should that matter? isn't the plugin constantly checking the height and width of the element that it is called on?

should it always be up to date if it's checking the dom every n milliseconds?

All the information you provided here is useless. You should check scrollbar behaviour - look at DOM structure after you initialize plugin, then update content as you do it, and re-check DOM structure again. Try to understand if scrollable container was overwritten or not, try to init custom scrollbar on updated container again and see what happen next.

the dom structure is always the same, it clones the dom node that i call the plugin on then inserts it into itself. it never does this more than once. I have checked. If you go back to my original question i state that resizing the browser window corrects it, so there is probably a bug in the check that is happening every 250 ms, that is getting ironed out in the resize event.

is the plugin only checking the last inited dom node? or is it checking all of them on the interval that you have setup?

whoops. i guess i didn't mention that. my bad. well, it corrects itself on resize. usually the height is set to auto

it clones the dom node that i call the plugin on then inserts it into itself
How does it happen? This moment is not clear for me.

is it checking all of them on the interval that you have setup?
Yes

the plugin literally clones the dom node and puts it inside of itself. you will notice that the second picture has a modified dom structure with the ".main-container-content" node (the node that the plugin was called on) recreated inside of itself, causing a deeper structure. This is the moment that the plugin is inited on the dom node. this is literally the only thing that happens, and it happens whether or not i use the module's function that i defined above.

So you were talking about plugin - it does not clone, it wraps element with custom container that is different. But I am more interested in HOW YOU UPDATE your content and what happens next. Didn't you try to init custom scrollbar on your container after content was updated? For example, manually from the browser console, and then look at DOM structure - is it the same, or it was changed.
Also, I see you've changed source code of plugin (at least CSS classes in plugin), haven't you?

Unfortunately I'm going to bed now. Let's continue tomorrow or on monday.

whether or not i am simply appending elements or replacing the innerHTML of a dom node, it should not make a difference, as the plugin should be detecting the amount of content inside of the dom node that was first inited on. Should i be reinitializing the plugin if i add / remove any of the content? let me know

Should i be reinitializing the plugin

No, it should detect content/container size changes automatically. But in your case we have problem. Is there any way for me to look at your environment?


refactor: replace searchAPI with useSearchApi hook to prevent infinit…

Description
Currently eslint flags a warning on the SearchBox component due to useEffect not having onSearch in its dependency array. When you add it to the array, the search finctionality on the website breaks due to an infinite re-render. Potentially this happens because we end up with a circular new objects creation by triggering the filter array method within SearchBox.
In this PR I replaced the searchAPI method with a hook called useSearchApi which doesn't get called in SearchBox but rather in the parent component App. This way the filter doesn't happen in child components, it only depends on changes to searchText and it doesn't get triggered when the demos array changes.
Also, added the newly created hooks directory to eslint config in next.config.js.
Fixes #87
Type of change

[x] Improvement

How Has This Been Tested?
Running build and lint commands locally to confirm there are no errors. Also, ran the application locally to ensure search finctionality still works. Checked a few of the demos to make sure functionality there isn't affected, though it would be best if someone more familiar with the application confirms everything is as expected.
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@rzhekova
Thanks a lot for taking the issue and making the app better. Please feel free to pick up more, contribute more. I wish you a great #Hactoberfest ahead. You will be added to the contribution list right after we merge this PR. Don't forget to share about your contribution publicly and provide your support with a star ⭐.
Great work 🔥 !!!!


bump privacy dashboard to 7.3.1

Task/Issue URL:  https://app.asana.com/0/414730916066338/1209003600291441/f
Description
The assets for the dashboard were removed by mistake, this PR adds them back. Please see the link above for more details.
Steps to test this PR

The dashboard loads correctly

Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

#5419  👈 (View in Graphite)
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

E2E CI green 👍  https://github.com/duckduckgo/Android/actions/runs/12428400598/job/34699933136


Update MG PG for use with GaaS

(This is a placeholder for specific requirements for updating MG PG for use with GaaS)

Closed by PR https://github.com/rapidsai/GaaS/pull/24


uv self update error on Windows: The system cannot move the file to a different disk drive

I am using a Dev Drive on Windows 11, mounted at D:. As recommended by Microsoft docs, I have mapped CARGO_HOME to this drive to improve cache speeds. This seems to cause issues with uv self update however, resulting in the following error:
uv self update
info: Checking for updates...
error: The system cannot move the file to a different disk drive. (os error 17)
[Exit code 2]

The issue was reproduced on uv version 0.2.3, one older than the current version. The issue cannot be reproduced on the latest v0.2.4 as uv self update exits early upon detecting being on the latest version, however I am making the assumption that the issue is still present.

This is likely an issue in https://github.com/axodotdev/axoupdater. Do you mind filing there? Otherwise I can.

Forwarded, thank you for the quick response!

Thanks! We'll keep this open in the interim.

I've opened a PR on Axoupdater that should fix this (https://github.com/axodotdev/axoupdater/pull/121). Due to the US holiday, it'll most likely take us a day or two to test and cut a new release.

Don't mean to unnecessarily bump this issue, but just for the record, I believe the upstream issue was fixed with axoupdater v0.6.5.

Thank you yes! And we updated.


Error when TensorRT is loaded for RemBG

Hi,
I have an error when I try to use "Image Rembg" node :
`2024-06-03 12:26:18.3178859 [E:onnxruntime:Default, provider_bridge_ort.cc:1534 onnxruntime::TryGetProviderInfo_TensorRT] D:\a_work\1\s\onnxruntime\core\session\provider_bridge_ort.cc:1209 onnxruntime::ProviderLibrary::Get [ONNXRuntimeError] : 1 : FAIL : LoadLibrary failed with error 126 "" when trying to load "E:\00_ComfyUI_Fooocus\python_embeded\lib\site-packages\onnxruntime\capi\onnxruntime_providers_tensorrt.dll"
*************** EP Error ***************
EP Error D:\a_work\1\s\onnxruntime\python\onnxruntime_pybind_state.cc:456 onnxruntime::python::RegisterTensorRTPluginsAsCustomOps Please install TensorRT libraries as mentioned in the GPU requirements page, make sure they're in the PATH or LD_LIBRARY_PATH, and that your GPU is supported.
when using ['TensorrtExecutionProvider', 'CUDAExecutionProvider', 'CPUExecutionProvider']
Falling back to ['CUDAExecutionProvider', 'CPUExecutionProvider'] and retrying.
****************************************`
I have two graphics cards. One, my primary, is a GTX 1070 Ti for the display and the second one is an RTX 4070 Super for computation (3D, compositing and AI).
What I need to do to avoid this error and use the RTX 4070 Super TensorRT ? Of course, the node switch back to cuda and compute the node.
Thank you,
Matt

https://github.com/comfyanonymous/ComfyUI/issues/2823
pip uninstall rembg //uninstall rembg
pip uninstall onnxruntime //uninstall onnxruntime
pip install rembg[gpu] onnxruntime-gpu //install rembg with GPU support

Thank you for your answer ;)
Matt

I guess so? I launched CMD in the ..\ComfyUI\venv\Scripts directory and called the activate.bat. Then I entered those lines in order.

Oki, thank you very much ;)

What is your cudnn version?
onnxruntime-gpu does not support cudnn version 9.x yet. Reducing your cudnn version to 8.9.x may solve your problem.

Hi all,
Thx for your answers, the solution of Bobcate solved my problems and another ;)
Thank you again,
Matt


JSON value '50%' of type NSString cannot be converted to NSNumber

Fix bug server return string instead number in borderRadius

Summary
Explain the motivation for making this change: here are some points to help you:

What issues does the pull request solve? Please tag them so that they will get automatically closed once the PR is merged
What is the feature? (if applicable)
How did you implement the solution?
What areas of the library does it impact?

Test Plan
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.
What's required for testing (prerequisites)?
What are the steps to reproduce (after prerequisites)?
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Checklist

[x] I have tested this on a device and a simulator
[ ] I added documentation in README.md
[x] I updated the typed files (typescript)
[ ] I added a test for the API in the __tests__ folder

Hello @huydosgtech,
Could you please explain and provide an example to run a test case, demonstrating how it behaves before and after those changes?
Thank you.


Refactor after migration to Vite

          # To Do After Migration to Vite

Refactor Class Components to Functional Components
Functional components are recommended for better performance and simplicity.

Refactor main.css
Refactor main.css into separate files

Fix Script Execution Issues
Fix problems related to script execution.

Migrate from TreeBeard to MUI Material for Script Tree Generation
TreeBeard is outdated and causing warnings. Switch to MUI Material for generating the script tree due to the following warnings:
TreeBeard2: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.

Warning: Transition2 uses the legacy childContextTypes API, which is no longer supported and will be removed in the next major release. Use React.createContext() instead.

...

Originally posted by @palagdan in https://github.com/kbss-cvut/s-pipes-editor-ui/issues/61#issuecomment-2317935601

Also make sure that s-forms.css is imported and not duplicated in the project.

@palagdan, I added new sub-issues to this issue and prioritized them. We should split this issue into separate issues (it is enough to do it incrementally, i.e. pick only the most important ones at the time and separate them to an issue)


wip(module:steps): refactor steps

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[ ] No

Other information

Coverage remained the same at 98.122% when pulling 20744aaa9f871b8853d4588ca5d292f9d7c46b53 on vthinkxie:0.7.0 into bb7b63d69cfcb23e81585f8ab61b638ef275ed08 on NG-ZORRO:0.7.0.


Project 26 Contribution

I would like to share my Idea with you.  I have enjoyed your teachings and videos over the years.  I am a hobby programmer at best. I am going to work with your code to reverse the walls and vortex's and replace them with landing spots, multiple balls, and a shake motion to free/restart/reset the balls.  Here is an example of what I am talking about.  Maybe you can do it better and use it as an add-on to this project.  Thanks again for all your knowledge and sharing.  It has been a great learning site.

Hello! I love to see folks take these projects and do exciting new things with them, and in particular release their versions of the projects on the App Store. However, I can't really accept those changes back onto the site – each tutorial is designed to teach a handful of things, and if I kept adding more to them it would grow increasingly large. Best of luck building your improvements!


flash: sam0: set write_block_size=1 when EMULATE_BYTE_PAGES is set

The sam0 has a page size of 64 bytes, making it incompatible with
the nvs driver that specifies a maximum write block size of
32 bytes. When CONFIG_SOC_FLASH_SAM0_EMULATE_BYTE_PAGES is set,
it should report a write block size of 1 byte, which is compatible
with nvs.
Signed-off-by: Adam Serbinski<EMAIL_ADDRESS>

Bump for review?

ls there any bug issue registered for this?

Not to my knowledge.


[BD-21] Get rid of the documented_elsewhere annotation

Description: This is nowhere used. If we need to re-introduce it at some point, we'll
discuss it then.
JIRA: BD-21 https://openedx.atlassian.net/wiki/spaces/COMM/pages/1596358943
Reviewers:

[x] @robrap

Merge checklist:

[ ] All reviewers approved
[ ] CI build is green
[x] Version bumped
[x] Changelog record added
[ ] Documentation updated (not only docstrings)
[x] Commits are squashed

Post merge:

[ ] Create a tag
[ ] Check new version is pushed to PyPi after tag-triggered build is
finished.
[ ] Delete working branch (if not needed anymore)

Author concerns: List any concerns about this PR - inelegant
solutions, hacks, quick-and-dirty implementations, concerns about
migrations, etc.

Thanks for the pull request, @regisb! I've created BLENDED-604 to keep track of it in Jira.   More details are on the BD-21 project page.
When this pull request is ready, tag your edX technical lead.


.valign-wrapper issues? Or documentation?

Some unexpected issues come up with .valign-wrapper and .valign.
.center-align seems to interfere with .valign-wrapper.
.col seem to interfere with it, for example: issue #1051
Also the docs show an tutorial using .valign, nested in .valign-wrapper. Is this deprecated?

To understand fully how valign works you may want to take a look at the implementation below, it uses flexbox so it will conflict with .col which has float:left
.valign-wrapper {
@include flexbox();
@include align(center);
.valign {
display: block;
}
}

I had the same issue. Using center-block instead of center fixed the issue:

Blerg!

Had tip to this post for pointing out the solution: http://stackoverflow.com/a/31214741/62694

I found a workaround, at least for vertical centering. I was not actually going for horizontally centered, just vertically Here's what I had:

Another col div in the row was taller than this image one, stretching the height of the row to more than the image, so valign did nothing to fill the empty space and the
" just hung out at the top.
I slapped on a CSS rule of
.card-image {
  height: 100%;
}

, and now it had room to vertically center the image.