Request for revision of support requirements for MDE on Linux

[Enter feedback here]
Hello Team,
Could you please modify and update the supporting requirements for MDE on Linux?

CentOS Stream is included in the supported OS.
A statement confirming that CentOS 6.x and 8 are not supported.
EOS OS does not support MDE on Linux.

Best Regards,
Kazuya

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

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

@Dansimp Please help us in resolving this issue. Thanks

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Heart Rate Recorder : how to download the data?

How can the files generated by Heart Rate Recorder be downloaded?
Thanks!

Using the IDE ( https://www.espruino.com/ide/ ) you can read file from the device (the Database icon on the middle bar)
You can also write a script using Puck.js

You can click on an arrow pointing down in the app loader as well.
https://banglejs.com/apps/#

As @Purple-Tentacle  says:


suite: config_yaml should contain yaml content instead of path/to/yaml

Route /suite has <config_yaml> in request schema. It takes path to the yaml config file in the data body, for example:
{
        "--ceph": "main",
        "--ceph-repo": "https://github.com/ceph/ceph-ci.git",
        "--machine-type": "testnode",
        "--num": "1",
        "--priority": "70",
        "--suite": "teuthology:no-ceph",
        "--suite-branch": "main",
        "--suite-repo": "https://github.com/ceph/ceph-ci.git",
        "--teuthology-branch": "main",
        "--verbose": "1",
        "--user": "example",
        "<config_yaml>": ["/path/to/yaml"]
     }

https://github.com/ceph/teuthology-api/blob/9af7fb0d39501feedac82f030c7060eb4b7e8a03/src/teuthology_api/schemas/suite.py#L44
This would mean that the config file should already exist on t-api's server. For more practical use-case, we can accept a string with the yaml config content. After receiving a request, teuthology-api can save this yaml content in a temporary file and then pass path to that file to teuthology.suite.main function.

I'd like to work on this issue. So basically instead of the YAML file path the request would contain the contents of the file, and we need to save it as a temporary file (something like <username>_<timestamp>.yaml) and pass that to the teuthology function?

Understood, I'll take a look at this library and start working on it!

I looked at the tempfile module and this is what I was able to gather. Once the with block is over, the temporary file will be deleted automatically and until then it will show as a temporary file on the system.

after writing the YAML content to this tmp, we can pass it on to the teuthology.main function, and can put the user's name as suffix if required

Yes, that sounds good! Like in our docker setup, we use this yaml config while scheduling: https://github.com/ceph/teuthology/blob/main/docs/docker-compose/teuthology/containerized_node.yaml
Also it's possible to get multiple configs which is why "<config_yaml>" param is a list in /suite schema. So you'll probably want to create a new file for every config and then send path of each temp file to teuthology.main.

So after creating temporary files for all configs, I should replace the <config_yaml> key with the list of names of those temporary files?

can i work on this? @VallariAg

So after creating temporary files for all configs, I should replace the <config_yaml> key with the list of names of those temporary files?

@Devansh3712 sorry for late reply! And yes, you pass the path of all the temporary config files like: {"<config_yaml>": ["path/to/config.yaml"] ....}. I think that should work!
@octonawish-akcodes please check with Devansh if he's still working on this issue.

understood, and yes i'm working on this issue


For macOS, set java.library.path when launching GUI from NetBeans

We can make CMake add run.args.extra=<opensim-core-lib-dir> to Gui/opensim/nbproject/private/platform-private.properties.

Verified.


Remove assumptions that caused a thread panic

minimal sane fix

Should something explicit happen in the Err case?

No, there are cases where the tx will not be found in the wallet so we should not error here


Add bump2version configuration

This adds a new workflow for creating releases, with a VERSION file that acts as a single source of truth for the project version number.
Helps: https://github.com/endlessm/endless-key-flatpak/issues/69

Note that the version scheme here treats the patch component as optional, so a release can be 0.5 or 0.5.1. I don't super like that scheme, but it's consistent with the releases we've created so far and seems silly to mess with it.

It would be nice if we could integrate bump2version with our appstream metadata somehow. I think my favourite workflow for that would be we update the release notes for the next release as we go.  Then when we do bump2version it'll find that release in the XML (and error out if there isn't one), set the date, set type from "development" to "stable", and set the correct version.


attempt to fix permissions for semver-check action

First and last commits of #3003. The last one which changes perms I recreated rather than cherry-picking to convince Github that it was really me who authored it.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

2 of 7 (28.57%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 83.081%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

io/src/error.rs
2
7
28.57%

Files with Coverage Reduction
New Missed Lines
%

io/src/error.rs
1
22.95%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
19588

Relevant Lines:
23577

💛  - Coveralls

Tried changing on:pull_request: to on:pull_request_target: as per https://github.com/actions/labeler/issues/136#issuecomment-1357839196

That did seem to work. But I can't make heads or tails of the stuff in the linked blog post https://securitylab.github.com/research/github-actions-preventing-pwn-requests/
What are "repository secrets" and why would I care if CI can access them? How could npm install possibly do damage to a CI box and why does it matter what permissions the workflow has, when CI workflows are always able to access the Internet and write to disk? What does "runs in the context of the target repository of the PR, rather than in the merge commit"? Why is the error we see so opaque and none of this documented except in a random comment by the maintainer of a specific action?

Gerrit looks interesting, although it has a 1970's feel to the GUI, probably because it's 14 years old now which is practically 1/2 a decade worth of changes in the real world.

Yeah, I feel you...

Tried changing on:pull_request: to on:pull_request_target: as per actions/labeler#136 (comment)

Seeing the README of the actions/labeler you have:

When submitting an initial pull request to a repository using the pull_request_target event, the labeler workflow will not run on that pull request because the pull_request_target execution runs off the base branch instead of the pull request's branch. Unfortunately this means the introduction of the labeler can not be verified during that pull request and it needs to be committed blindly.

This is already circumvented by the neat hack where we force to switch to the PR branch even if the event is pull_request_target.
https://github.com/rust-bitcoin/rust-bitcoin/blob/beab1dd7248eb4175c74ecb8124b8d81ba871aae/.github/workflows/manage-pr.yml#L1-L20
Since we are doing that anyways already for every PR, doing this for #3003 does not increase our threat model.
Now, this is my opinion, but do we really need the comment? Because if labeling is enough, then we don't need to add an extra action (that is also community-driven, non-official) thollander/actions-comment-pull-request. This does not increase the surface attack of a rogue action, since the threat model stays the same with only giving write access to the official actions/labeler (official GH).
Is this a viable approach?

Change the on: pull_request to on: pull_request_target
Add the same hack as the manage-pr.yml job to switch to current PR branch
Change from actions-ecosystem/action-add-labels (which is community-driven) to the official actions/labeler (official GH)
Remove the actions-comment-pull-request step.

I think the label is probably sufficient and the comment isn't needed.
But I still don't understand how any of these things can be a threat model. Because they can open PRs and issues and labels on Github? Lol. Obviously we are not depending on the Github UX being a source of truth, and even if we were, we wouldn't pay attention to bot-like actions.
Nothing can push directly to master and even if they could, they can't sign commits and can't push to crates.io.
I don't understand why none of these "threat modeling" docs ever describe what bad things CI actions are supposed to be able to do..

I don't understand why none of these "threat modeling" docs ever describe what bad things CI actions are supposed to be able to do..

Yes, but not everyone has the same safeguards as rust-bitcoin.
I will start modifying #3003 accordingly.

I will start modifying https://github.com/rust-bitcoin/rust-bitcoin/pull/3003 accordingly.

Does that modification include switching us to Gerrit :)

What does "runs in the context of the target repository of the PR, rather than in the merge commit"?

I happen to know what this means. "context of target repository" basically means that actions will read the yaml and scripts the in master branch not the one in the PR. By default, the action is taken from the yaml in the PR branch to allow easy testing of CI updates before merging but if the action is working with secrets it'd be trivial to get them to leak: just open a PR that modifies an action to print them into logs or send to a server.

I think we can close this.
Thanks for the debugging...


how to get metadata of output image?

the current example only get input image metadata, not output, if the input image's size is 1200x1200, we get  {width: 1200, height: 1200, ...} not {width: 400, height: ?, ...}
      const sharpInstance = sharp(buf).resize(400);
      const resizedBuf = await sharpInstance.toBuffer();
      const metadata = await sharpInstance.metadata();

Hello, I think you're looking for the metadata of the processed image, which would be:
const metadata = await sharp(resizedBuf).metadata();

From v0.17.3+, you could also use:
const { data, info } = await sharpInstance.toBuffer({ resolveWithObject: true });

thanks

Can this be achieved without calling toBuffer? It seems like a common use-case that somebody would need to know the metadata of the transformed file.

@ajhool Please can you provide a code sample demonstrating how you think this might be improved.

@lovell
Eg, I want to convert an unknown sized image to 200100 with { fit: inside }. after resize call, the size of processed image is unknown, I need to calculate paddings and call extend to extend the image to 200100.
I don't know if it is a bug. After
img..resize(200,100,{fit:sharp.fit.inside})

I got an 100*100 image when input is square.


Refactor: VoteHandler.accept_vote returns Option

Checklist

[ ] Updated guide with pertinent info (may not always apply).
[x] Squash down commits to one or two logical commits which clearly describe the work you've done.
[x] Unittest is a friend:)

This change is

@mergify update

Manually merged in: 5593b96dea30979a1bdc924abbfe3fc8d2463ecd


[Frontend] Chat-based Embeddings API

This PR extends the existing Embeddings API to accept chat conversations similar to Chat Completions API. This enables multi-modal conversations to be passed to the embedding model.
To reduce code duplication, I've also factored out the common code for handling completion and chat-based inputs into the base OpenAIServing class.
FIX #8967
FIX https://github.com/vllm-project/vllm/pull/9303#issuecomment-2437569903

Sorry for the commit spam, I'm done refining the docs now.

Entrypoints tests pass now.

@simon-mo @njhill do you have time to take a look at this?


Add Selenium for Python

Add webdrivers for Python selenium

This adds the executable drivers to be ignored

@ignatiusmb given that Selenium can be used in other environments to Python, do you think this might be worth maintaining as it's own Selenium.gitignore template?

@shiftkey right, I was thinking that it only uses multiple webdrivers that could be added to each environment. But now that you mention it, I realize it also has its own IDE that could be used with a lot of other APIs and frameworks.
I think creating its own Selenium.gitignore is probably the right step, considering it's one of the most popular browser automation tool. Personally, I only use it with Python so I can't really say much about it maintaining it.


Addition of folder security to mock framework

Hmmm, this one feels like another going-too-far issue.  Since your implementation probably doesn't match NTFS or FAT directory security checking.

Given the age of the PR, and I'm not totally sold on value-add here, I'm going to close this.


[SPARK-46567][CORE] Remove ThreadLocal for ReadAheadInputStream

What changes were proposed in this pull request?
This PR propose to remove ThreadLocal for ReadAheadInputStream.
Why are the changes needed?
ReadAheadInputStream has a field oneByte declared as TheadLocal.
In fact, oneByte only used in read.
We can remove it by the way that the closure of local variables in instance methods can provide thread safety guarantees.
On the other hand, the TheadLocal occupies a certain amount of space in the heap and there are allocation and GC costs.
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
Exists test cases.
Was this patch authored or co-authored using generative AI tooling?
'No'.

ping @dongjoon-hyun @srowen cc @sitalkedia

The GA failure is unrelated.

I agree with this change, I would be surprised if it's even an optimization

Merged to master.

Thank you, @beliefer and all.


Transfer Policy

New CR:Transfer Policy

[ ] Remove transfer policy from wallet creation flow. This was relevant in the old app architecture. Leave it in the wallet settings only. @Raheel1258 Find design link in comment

[ ] @pratyakxx If no vaults avaiable app crash on Transfer policy UAI

[ ] @pratyakxx There is no default TP for wallets unless set and so it should not be triggered or even checked for at any time when not set. -- This one will be moved to Transfer policy changes

[ ] When user sets it from settings, they should also be able to choose which vault it needs to transfer to.

https://xd.adobe.com/view/bbecc076-09ba-46dd-963f-531197a31224-eebf/

Still I can see Trasfer policy in wallet creation

The point pending was completed


t_Co=256 by default

I use to use git mergetool(vim). One thing I annoyed is highlight. Because of it some text was not displayed(turns out it had the same color as foreground). As a workaround I found solution in internet that "disabled" all highlighting making my text white(bold sometimes) and foreground black. Some time ago browsing vim github issues(if I remember right) I saw t_Co=256 in vimrc(maybe) that borned idea in my head that it could solve git mergetool highlighting. Today I tried :set t_Co=256 and it did the trick. That's cool and I can make some explanation why it don't work by default(minimal as possible) but if it would be turned on by default will it hurt old terminals? At least for me I am angry. Because this finding was miracle and I don't want the others to struggle with git mergetool
and also I would be quite happier to not type it everytime I do rebase...
@brammool can you explain why this option is not by default?

I use to use git mergetool(vim). One thing I annoyed is highlight.
Because of it some text was not displayed(turns out it had the same
color as foreground). As a workaround I found solution in internet that
"disabled" all highlighting making my text white(bold sometimes) and
foreground black.

That should be a problem with the colorscheme.  I have no idea why this
would happen with mergetool, perhaps it depends on how Vim is started
then.  I also wonder how you disable all highlighting.

Some time ago browsing vim github issues(if I remember
right) I saw t_Co=256 in vimrc(maybe) that borned idea in my head that
it could solve git mergetool highlighting. Today I tried :set t_Co=256
and it did the trick. That's cool and I can make some explanation why it
don't work by default(minimal as possible) but if it would be turned on
by default will it hurt old terminals? At least for me I am angry.
Because this finding was miracle and I don't want the others to struggle
with git mergetool
and also I would be quite happier to not type it everytime I do rebase...
@brammool can you explain why this option is not by default?

I very much doubt the value "256" matters.  Have you tried setting it to
"16"?  Changing the value may trigger reloading the colors and it's very
well possible that fixes the problem you experience.  You could also try
using a :colorscheme command.
--
hundred-and-one symptoms of being an internet addict:
144. You eagerly await the update of the "Cool Site of the Day."
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


import cupy 9.0.0a2 doesn't work on Windows 10

Thank you for using and contributing to CuPy!
If your issue is a request for support in using CuPy, please post it on Stack Overflow or Google Groups (en / ja).
Developer team members are monitoring questions on these channels.
If it is a bug report, please include the following information:

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')

CuPy version 9.0.0a2
OS/Platform: Windows 10
CUDA version: 10.2
cuDNN/NCCL version (if applicable)

Code to reproduce

>>> import cupy

Error messages, stack traces, or logs

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\Amin\anaconda3\envs\py38\lib\site-packages\cupy\__init__.py", line 57, in <module>
    from cupy import fft  # NOQA
  File "C:\Users\Amin\anaconda3\envs\py38\lib\site-packages\cupy\fft\__init__.py", line 1, in <module>
    from cupy.fft._fft import fft  # NOQA
  File "C:\Users\Amin\anaconda3\envs\py38\lib\site-packages\cupy\fft\_fft.py", line 9, in <module>
    from cupy.fft import config
  File "C:\Users\Amin\anaconda3\envs\py38\lib\site-packages\cupy\fft\config.py", line 13, in <module>
    from cupy.fft._callback import get_current_callback_manager  # NOQA
  File "cupy\fft\_callback.pyx", line 35, in init cupy.fft._callback
AttributeError: 'NoneType' object has no attribute 'split'

Hi @ma-sadeghi Thanks for reporting! This is surprising, could you help me debug it? I need to know the output of the following snippet on Windows:
import sysconfig
sysconfig.get_config_var('CXX')

No worries, it doesn't return anything for me.

Thanks! Right, this callback module is new, so it's not included in the v8 releases. I will push a fix.

btw forgot to say, though this is irrelevant to my planned fix (as the callback doesn't work on Windows anyway): Any chance you know the path to an MSVC compiler installed on your system? I couldn't make sense of the output you reported.

I don't think I have MSVC compiler installed

Thank you for the feedback, we'll soon make a release including this fix as v9.0.0a3.

I don't think I have MSVC compiler installed

Hi @ma-sadeghi I know nothing about CUDA + Windows, so I took a quick look at the Installation Guide and found that MSVC needs to be installed before installing CUDA Toolkit. Looks like you're using a conda environment, but given that we haven't built Windows packages yet (https://github.com/conda-forge/cupy-feedstock/issues/62), I assume that you already have a CUDA Toolkit installed locally, and then install CuPy by wheel (pip install cupy-cuda102)? But this means you should have MSVC somewhere, or NVCC would not work. I am wondering how to make Python discover where your MSVC is...

@leofang You're right, I have Cuda Toolkit installed on conda (from https://anaconda.org/anaconda/cudatoolkit), and then I installed cupy using pip in my conda environment.
When I run nvcc --version in cmd or conda prompt, I get a valid output:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Oct_12_20:54:10_Pacific_Daylight_Time_2020
Cuda compilation tools, release 11.1, V11.1.105
Build cuda_11.1.relgpu_drvr455TC455_06.29190527_0

I'm not really familiar with C++ build tools, but I just installed the C++ build tools from Microsoft, and still I get no output when running:
import sysconfig
sysconfig.get_config_var('CXX')

we'll soon make a release including this fix as v9.0.0a3.

Unfortunately, as many test failures are observed in #4362, we decided not to release v9.0.0a3 this time and will work on fixing the Windows issues towards v9.0.0b1 planned next month. We are going to take down v9.0.0a2 Windows wheels. We're sorry for the inconvenience.

This is everything I could obtain via sysconfig module in my test environment:
C:\Users\chainer\cupy>python -m sysconfig
Platform: "win-amd64"
Python version: "3.7"
Current installation scheme: "nt"

Paths:
        data = "C:\Development\Python\Python37"
        include = "C:\Development\Python\Python37\Include"
        platinclude = "C:\Development\Python\Python37\Include"
        platlib = "C:\Development\Python\Python37\Lib\site-packages"
        platstdlib = "C:\Development\Python\Python37\Lib"
        purelib = "C:\Development\Python\Python37\Lib\site-packages"
        scripts = "C:\Development\Python\Python37\Scripts"
        stdlib = "C:\Development\Python\Python37\Lib"

Variables:
        BINDIR = "C:\Development\Python\Python37"
        BINLIBDEST = "C:\Development\Python\Python37\Lib"
        EXE = ".exe"
        EXT_SUFFIX = ".pyd"
        INCLUDEPY = "C:\Development\Python\Python37\Include"
        LIBDEST = "C:\Development\Python\Python37\Lib"
        SO = ".pyd"
        VERSION = "37"
        abiflags = ""
        base = "C:\Development\Python\Python37"
        exec_prefix = "C:\Development\Python\Python37"
        installed_base = "C:\Development\Python\Python37"
        installed_platbase = "C:\Development\Python\Python37"
        platbase = "C:\Development\Python\Python37"
        prefix = "C:\Development\Python\Python37"
        projectbase = "C:\Development\Python\Python37"
        py_version = "3.7.2"
        py_version_nodot = "37"
        py_version_short = "3.7"
        srcdir = "C:\Development\Python\Python37"
        userbase = "C:\Users\chainer\AppData\Roaming\Python"


Another day, another deadlock...

Stack trace.
Main thread is locked waiting for one of the background queues to stop doing image loading, and image loader queues are locked trying to update icons...

Pastie is 410 gone :(
Closing this due to inactivity. If you're still facing an issue with the latest version of Quicksilver, please create a new issue.
Thanks!


Lost tracing & beforeSend hook stopped working after upgrading to latest version

Versions + Platform

[ ] SDK version - ^3.0.7
[ ] Electron version - 13
[ ] Platform - macOS

Description
I've just upgraded this package to latest version (3.0.7 from 2.5.1), and noticed all the console logs, warns and errors are being reported from instrument.js as a result I can't keep trace from which file log, and warns are coming.
Is there any way to disable this behavior? As I want to report exceptions manually using  Sentry.capureException.
  var consoleError = console.error
  console.error = function() {
    var args = Array.prototype.slice.call(arguments)
    const error = reduceConsoleArgs(args)
        Sentry.captureException(error, { level: 'error' })
    return consoleError.apply(console, args)
  }

  -----------------------------------------------------

  const logWarn = log.warn
  log.warn = function() {
    var args = Array.prototype.slice.call(arguments)
    Sentry.addBreadcrumb({ category, ...translateArgs(args), timestamp: Date.now(), level: Sentry.Severity.warn })
    return logWarn.apply(log, args)
  }

Also beforeSend in renderer is not working anymore.
const Sentry = require('@sentry/electron/')
const sentryIssues = [] // global session array

function getConfig(version) {
return {
  dsn<EMAIL_ADDRESS>  release: 'Repeato-' + version + '-' + process.platform,
  integrations: [],
  // debug: true,
  beforeSend(event, hint) {
    console.log('CheckSentryMessage', hint, hint.originalException?.message)
    return null // do not report the error
  }
}
}
module.exports = { getConfig, sentryIssues, Sentry }

I've just upgraded this package to latest version (3.0.7 from 2.5.1), and noticed all the console logs, warns and errors are being reported from instrument.js as a result I can't keep trace from which file log, and warns are coming.
Is there any way to disable this behavior? As I want to report exceptions manually using Sentry.capureException.

You can disable console breadcrumbs in the renderer via the Breadcrumbs integrations:
import { init, Integrations } from '@sentry/electron/renderer';

init({
  dsn: '__DSN__',
  integrations: [new Integrations.Breadcrumbs({ console: false })]
})

Also beforeSend in renderer is not working anymore.

Events are not sent directly from the renderer so beforeSend is not called. You should use beforeSend in the main process.

I'm going to close this as there aren't any actions left to take. Feel free to open new issues if you come across anything else!


fetches.EachTopic empty .Records() and varying size

Note: I am only consuming a single topic:
Im not sure this acutally an issue, but more of an issue with my understanding of the differences between.
When using this code i see some varying prints, where in some cases ft.Records() is all 5k messages from PollRecords and in some other cases there I will see 3 prints of varying size combining to be 5k messages.
And then in some cases I see a couple of fetches coming in with len(ft.Records()) == 0
func (s *Service) poll() {
	for {
		fetches := s.kafkaClient.PollRecords(context.Background(), 5000)
		if fetches.IsClientClosed() {
			zap.L().Info("shutting down: KafkaClient closed")
			return
		}
		fetches.EachError(func(_ string, _ int32, err error) {
			panic(err)
		})
		fetches.EachTopic(func(ft kgo.FetchTopic) {
			fmt.Println(len(ft.Records()))
		})
	}
}

On the other hand using fetches.Records() as below i see 5k messages consistently(Until the consumer group is caught up to the kafka offset)
func (s *Service) poll() {
	for {
		fetches := s.kafkaClient.PollRecords(context.Background(), 5000)
		if fetches.IsClientClosed() {
			zap.L().Info("shutting down: KafkaClient closed")
			return
		}
		fetches.EachError(func(_ string, _ int32, err error) {
			panic(err)
		})
                fmt.Println(fetches.Records())
	}
}

Any clarification on this behaviour would be greatly appreciated.

When using Poll functions, the client waits until there is at least something to return (you're not going to see no records and no errors). PollRecords is upper bounding the return to 5k, but it's possible you'll see fewer records if there are fewer records buffered in the client that are ready to be returned. Seeing a consistent 5k to me signals that either you're consuming that has a lot of records in the broker; eventually you should reach the end and see fewer than 5k.
When the client buffers records to be returned, it buffers them per fetch if a fetch has any records. If I fetch foo partition 1 and 2, and 2 has records while 1 doesn't, the client actually buffers the metadata that was returned for partition 1 as well. This metadata is the FetchPartition, which contains the high watermark, log start offset, and last stable offset.
So, the difference between your cases is that in the first case, you're seeing these empty partitions (or topics, if you fetched a topic that has no records while another topic did), and in the latter case, you're just seeing all records.

Let me know if the above isn't clear or doesn't answer the issue fully; I'll go ahead and close this for now.


fix VGG error in benchmark_score

Signed-off-by: Andrey Parfenov<EMAIL_ADDRESS>Description
example/image-classification/benchmark_score.py fails for VGG net with ""Invalide num_layers {}. Possible choices are 11,13,16,19.".format(num_layers)" caused by #7556 this PR fix that
Checklist
Essentials

[x] Passed code style checking (make lint)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] For user-facing API changes, API doc string has been updated. For new C++ functions in header files, their functionalities and arguments are well-documented.
[x] To my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Could you rebase?

done


Redundancy of privateRegistryScanSecretsNames

If image scans are made from the same cluster where they are running, then they already exist on the nodes. Is it possible not to request them again from public/private registries, but to take them from the cluster nodes? What disadvantages do you see in this approach?

@Ais8Ooz8 in that case the scan-job will have to run on the same node of the image ?


Configure django plugin

Currently the django plugin is not working correctly. The reason for this is that dependabot updates have been merged without updating django configuration according to the version.
From django's plugin usage documenation:

Usage
Ensure pylint-django is installed and on your path. In order to access some
of the internal Django features to improve pylint inspections, you should also
provide a Django settings module appropriate to your project. This can be done
either with an environment variable::
DJANGO_SETTINGS_MODULE=your.app.settings pylint --load-plugins pylint_django [..other options..] <path_to_your_sources>

Alternatively, this can be passed in as a commandline flag::
pylint --load-plugins pylint_django --django-settings-module=your.app.settings [..other options..] <path_to_your_sources>

If you do not configure Django, default settings will be used but this will not include, for
example, which applications to include in INSTALLED_APPS and so the linting and type inference
will be less accurate. It is recommended to specify a settings module.

Since our use case consists for running the plugin in different projects the second configuration options seems like a better fit.

@caiofbpa Hi !, can you please take a look at this one when you have some time. Regards.

Perhaps we should expose the --django-settings-module as an engine option so our users can define it based on their projects?

@caiofbpa

Perhaps we should expose the --django-settings-module as an engine option so our users can define it based on their projects?

It won't work since the application code is always mounted at /code. Makes sense ?

It won't work since the application code is always mounted at /code. I already tried that. Makes sense ?

But the settings module could not be at the root project, for instance it could be inside an app module, so the --django-settings-module should be set to code.app.settings. The point is that we cannot predict where the settings module of every project will be.
Or am I missing something?

But the settings module could not be at the root project

I wasn't aware of the following:

But the settings module could not be at the root project, for instance it could be inside an app module, so the --django-settings-module should be set to code.app.settings.

Looks good to me. You can edit this PR and once done I can merge it. Thanks for your contribution!

@caiofbpa thank you for looking into this.
How do you see it now ?

Nice work, just a couple of minor tweaks and we'll be ready to merge

@caiofbpa thank for reviewing, updated.

This looks very good, thanks again for the contribution! Merging now...


Add documentation on internationalization to users manual.

We have some obsolete documentation on internationalization at http://visitusers.org/index.php?title=Internationalization. We should update and move it to the Developer Manual section of the User Manual.

Related to #5867


fix: adapt konflux-demo for konflux-ci

Description
TBD
Issue ticket number and link
KONFLUX-3683
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
TBD
Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/retest

/retest

/retest

/retest

/retest


Fix SonarCloud

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.

#77  👈
main

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

Join @JackPlowman and the rest of your teammates on  Graphite

Merge activity

Oct 10, 10:52 AM EDT: A user merged this pull request with Graphite.


Auto escaped methods

Hi,
Is it possible to add a function in a static class to the auto escaped functions list? I can escape any function from the class but not the function specifically. ie: classname::function_name

No, that isn't supported. The feature could be added though.

Related: #473

Are there any news on this?
Additionally, I need to add non-static class functions (e.g. $class->function_name) and functions inside a namespace (e.g. NamespaceName\function_name)

Even though this was the earlier issue, another issue was opened since and has a lot more discussion on it, including implementation ideas, so I'm going to close this issue in favour of the more recent issue #1176.


Implementing turbo prune command for pnpm workspaces

What version of Turborepo are you using?
1.0.24
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Linux
Describe the Bug
I was running the command turbo prune --scope=web for a pnpm workspace using turborepo
And it returns this error message:
 ERROR  this command is not yet implemented for nodejs-pnpm

Expected Behavior
It should have trimmed the workspace with relation to the scope declared which would make it easier for me to build the container image for that particular app.
To Reproduce
You can create a simple turborepo that uses pnpm as the package manager like the pnpm example https://github.com/vercel/turborepo/tree/main/examples/with-pnpm
and try to run the command:
turbo prune --scope=web

I am running the pnpm version 6.24.4 node version v17.3.0 turbo version 1.0.24

can be based on this solution
https://www.npmjs.com/package/pnpm-isolate-workspace

Thanks @AlonMiz and @ivoilic for your contributions.

Can't wait to have this feature.

@jaredpalmer can you please put this issue at a higher priority? It would make working with pnpm and turbo very easy.

DISCLAIMER: This might be terrible advice.
In the meantime while we wait for pnpm-based turbo prune, you can use pnpm locally for blazing fast package management at dev-time while still using turbo prune for docker builds, if that is something you're interested in doing. Steps I'm taking to achieve this:

Fork your root package.json file. Maybe something like package.docker-build.json.
Update your "packageManager" property in package.json to target your<EMAIL_ADDRESS>(eg 6.32.4).
Create a pnpm-workspace.yaml as explained in the pnpm documentation.
Update your .dockerignore, ymmv. Make sure you add package.json and package.docker-build.json, because the next step 👇 .
In your Dockerfile, COPY package.docker-build.json package.json at the proper moment in your context transfer.

Potential Drawbacks:
the cost of synchronizing a top level yarn.lock file, depending on how you're building your project, may make this all more hassle than it is really worth. But the nice thing about workspaces is that the two top-level package.jsons are isolated from dependency changes in subworkspaces.

This is something that is on our list however we have not prioritized doing this work at this time. The existing implementation is narrowly focused on an individual Yarn use case and is not easily generalizable, so it's not a trivial task.

Is there a way around in the meantime? :)

@Manubi I haven't explicitly tested it, but in general the thing proposed here should work: https://github.com/vercel/turborepo/issues/534#issuecomment-1101144057
(Use Yarn to generate docker images, and whatever package manager you want for general use.)

@ivoilic can you maybe post the full docker file? :)
I just recently started with turbo pnpm and docker... would be appreciated!
thanks

can be based on this solution https://www.npmjs.com/package/pnpm-isolate-workspace

this doesn't appear to currently work due to various type errors neither on linux or windows

I need this so bad 👍

I am using with great succes: https://pnpm.io/cli/deploy

Hey @weyert, is there any example repo ?

my solution for nextjs, hope can help someone:
this is just a temp solution, need wait for turbo prune --scope=web --docker support at pnpm
your apps/web Dockerfile
# 1. Generate a sparse/partial monorepo with a pruned lockfile for a target workspace. https://turborepo.org/docs/reference/command-line-reference#turbo-prune---scopetarget

# Refer to this original https://github.com/vercel/turborepo/blob/main/examples/with-docker/apps/web/Dockerfile

FROM node:alpine AS deps
# Check https://github.com/nodejs/docker-node/tree/b4117f9333da4138b03a546ec926ef50a31506c3#nodealpine to understand why libc6-compat might be needed.
RUN apk add --no-cache libc6-compat

# Set working directory
WORKDIR /app

# pnpm cannot support turbo prune yet. so need manual create isolated folder https://github.com/vercel/turborepo/issues/534
# RUN pnpm global add turbo
# COPY . .
# RUN turbo prune --scope=web --docker

# Need to change to correct app folder name for each flow [ deps, builder, runner ]
# set your APP_NAME
ENV APP_NAME=web

# Create apps folder
RUN mkdir -p apps

# Copy related packages and apps, warning: this solution can't copy package that only needed for the build.
COPY ./packages /app/packages
COPY ./apps/$APP_NAME /app/apps/$APP_NAME

# Copy nextjs env, comment out if you don't have .env
COPY ./apps/$APP_NAME/.env.staging.sample /app/apps/$APP_NAME/.env.production

# Copy clean root files to root folder
COPY ./turbo.json /app/turbo.json
COPY ./.gitignore /app/.gitignore
COPY ./.npmrc /app/.npmrc
# Add lockfile and package.json's of isolated subworkspace
COPY ./package.json /app/package.json
COPY ./pnpm-lock.yaml /app/pnpm-lock.yaml
COPY ./pnpm-workspace.yaml /app/pnpm-workspace.yaml

# 2. Rebuild the source code only when needed
FROM node:alpine AS builder
WORKDIR /app

# Build the project and its dependencies
ENV NEXT_TELEMETRY_DISABLED 1

# set your APP_NAME
ENV APP_NAME=web

COPY --from=deps /app/ .
RUN corepack enable
RUN pnpm install
RUN pnpm turbo run build --filter=$APP_NAME...

# 3. Production image, copy all the files and run next
FROM node:alpine AS runner

WORKDIR /app

ENV NEXT_TELEMETRY_DISABLED 1
ENV NODE_ENV=production

# set your APP_NAME
ENV APP_NAME=web

RUN addgroup -g 1001 -S nodejs
RUN adduser -S nextjs -u 1001

# comment out below if you don't have public folder
COPY --from=builder /app/apps/$APP_NAME/public public

COPY --from=builder --chown=nextjs:nodejs /app/apps/$APP_NAME/.next/standalone ./
COPY --from=builder --chown=nextjs:nodejs /app/apps/$APP_NAME/.next/static ./.next/static

USER nextjs

EXPOSE 3000

ENV PORT 3000

CMD node apps/$APP_NAME/server.js

remember enable standalone and set root path at next.config.js
const withTM = require('next-transpile-modules')(['ui'])
const path = require('path')

module.exports = withTM({
  reactStrictMode: true,
  output: 'standalone',
  experimental: {
    outputFileTracingRoot: path.join(__dirname, '../../'),
  },
})

With #1819 prune is now supported for repos using pnpm

@chris-olszewski you forget to update the docs

Will update the docs when it is released. 🎉￼

Looks like it is :-) Can you update doc ? ahah

Getting this error during next build: error TS5083: Cannot read file '/app/tsconfig.json'.
Same issue eithern when building with @zigang93's proposed Dockerfile and with the one below:
RUN apk add --no-cache libc6-compat
RUN apk update
# Set working directory
WORKDIR /app
RUN yarn global add turbo
COPY . .
RUN turbo prune --scope=@acme/web --docker

# Add lockfile and package.json's of isolated subworkspace
FROM --platform=linux/amd64  node:alpine AS installer
RUN apk add --no-cache libc6-compat
RUN apk update
WORKDIR /app

# First install the dependencies (as they change less often)
COPY .gitignore .gitignore
COPY --from=builder /app/out/json/ .
COPY --from=builder /app/out/pnpm-lock.yaml ./pnpm-lock.yaml
COPY --from=builder /app/out/pnpm-workspace.yaml ./pnpm-workspace.yaml

RUN yarn global add pnpm
RUN pnpm install

# Build the project
COPY --from=builder /app/out/full/ .
COPY turbo.json turbo.json
COPY .npmrc .npmrc

# COPY tsconfig.json tsconfig.json

ENV SKIP_ENV_VALIDATION=true

RUN pnpm turbo run build<EMAIL_ADDRESS>
FROM --platform=linux/amd64 node:alpine AS runner
WORKDIR /app

ARG DATABASE_URL
ARG NEXTAUTH_URL
ARG NEXTAUTH_SECRET

# Don't run production as root
RUN addgroup --system --gid 1001 nodejs
RUN adduser --system --uid 1001 nextjs
USER nextjs

COPY --from=installer /app/apps/web/next.config.js .
COPY --from=installer /app/apps/web/package.json .

# Automatically leverage output traces to reduce image size
# https://nextjs.org/docs/advanced-features/output-file-tracing
COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/standalone ./
COPY --from=installer --chown=nextjs:nodejs /app/apps/web/.next/static ./apps/web/.next/static

CMD node apps/web/server.js

Anybody know why?

@nathanhammond Have the docs been updated for pnpm examples?
I have been trying to get turbo prune working with pnpm in a docker container for the better part of a day, but I have no change of getting it working.
Would really appreciate it if there were more examples & docs for using turbo with pnpm.

@trm217 There is basically no material difference between each of the package managers. Remove the lockfile, create pnpm-workspace.yml, change * to workspace:*, and then do a global s/yarn/pnpm/g.
If you have particular problems open a new issue including details of the error message that you're encountering.

@nathanhammond

Remove the lockfile

this sounds like a bad advice since (I assume) it means that the packages that I expect to be installed on my machine are not guaranteed to be the packages installed in docker.
I've mentioned it in a different issue, but it seems bizarre that the official docs for turborepo recommend using pnpm

but provide examples of using yarn with docker (and no example with pnpm).

If you have particular problems open a new issue including details of the error message that you're encountering.
As someone who just started writing Dockerfiles, it's hard to pinpoint the exact issues I have. Since I basically took the yarn Dockerfile and started going line by line and (with the help of ChatGPT and dive) updating it to pnpm.
But now I'm in the position where I have to deeply understand how pnpm and docker works just to make it work for me.

I think the correct solution is either:

Don't recommend pnpm in the official docs (I would've used npm I guess)
Provide an example of using pnpm

I think my previous message sounded too demanding, so I made a PR in the hopes that we solve the issue using the second option (Provide an example of using pnpm)
https://github.com/vercel/turbo/pull/5536

In case someone's use case is not covered by @nicu-chiciuc's example, or you just want to look at more examples, you can get pretty specific with sourcegraph's search.


ENH: Better indexed inputs and output support in itk::TransformixFilter

Improvements to help with functional Python interface.
GetOutput has indexed interface.
"MovingImage" is the required, second indexed input
("TransformParameterObject") is the first.

Improvements to help with functional Python interface.
GetOutput has indexed interface.
"MovingImage" is the required, second indexed input
("TransformParameterObject") is the first.

This is the other way around right?

This is the other way around right?

Correct! I will update the PR description.


Remove unused jobs. Fix URL in PR check job.

Removing jobs that are not used anymore and all credentials and templates related with them.
Fixing URL of archived artifacts used in PR check of rh-che.

[test]


好像不支持MVVM模式

Look at here

→ Did you read the doc carefully
→ Did you add annotation above target activity
→ Did you add annotation processor dependence
→ Receive only bugs and suggestions

误会，是环境问题，可以支持。


Will this handle conditional fields?

@serialbandicoot  Will this handle conditional Fields?
Will it also handle Sub-forms
And will it also handle User based specific actions?

Will this handle conditional Fields? Server or/and Client...

At the server end, form validation should return as normal.
At the client end, I'm not sure - suggest you write a test.

If you create a new rspec test (client_validation_spec.rb) and what happens?
e.g. it "should handle max field length"

Sub-Forms? I'm not quite sure what you mean? Can you describe this in HTML

User based specific actions? Can you also describe this further, an html example would be useful.

This is a good start for client validation:
https://www.w3schools.com/tags/att_input_maxlength.asp

@Mossington Any follow ups on this one? Happy to close if your done.


Drag component have wrong coordinates if layout is changed

mrp: My Project.zip

Thanks for the feedback! Found the issue and will update soon


Bump StateDB to v0.3 with range-funcs

This bumps StateDB to v0.3.0 which brings in the iter.Seq2 based API: https://github.com/cilium/statedb/pull/40.
Before:
  iter := tbl.All(db.ReadTxn())
  for obj, _, ok := iter.Next(); ok; obj, _, ok = iter.Next() {
    ...
  }

Now:
  for obj := range tbl.All(db.ReadTxn()) {
    ...
  }

/ci-integration

/test

/test

/test


fix: fix name verifying

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?
Fix allowing the creation of a table/database with an invalid name bug.
Checklist

[ ]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.

Refer to a related PR or issue link (optional)

Do we need to verify column names?

Column name seems to encode with base64. cc @waynexia


Update explainer/spec to specify what coordinates are being used in updatelayout call

Specify what coordinates are being used screen vs logical coordinates

May be a question about logical vs. screen coordinates...

We came to a conclusion that web authors should be using client coordinates while providing the bounds in the updatelayout call. The conversion to screen coordinates is done internally in the platform. We also decided that we should be applying zoom and device scaling factor to the supplied EditContext bounds if the user decides to zoom/pan or the monitor that is being used is high dpi.


[21.11] alejandra: init at 0.5.0, add vscode extension

Motivation for this change
Also useful to people living on stable.
Things done
Backported expressions from current unstable.

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Closing as the Versions in this PR are outdated and mapping in from master works fine.
e.g. using sth. like:
extensions = with pkgs.vscode-extensions; [
      channels.unstable.vscode-extensions.kamadorueda.alejandra  # available in stable channel from 22.05 onwards
];


Fix vertex-to-element case in Mesh::FindPoints [fix-findpoints]

This fixes the case where we actually found a point but don't break the for loop.

I updated the implementation of the FindPoints methods in Mesh and ParMesh as part of #313. Can you please take a look at that?
One think I changed is to remove the elimination of points based on the bounding box - the computation of the bounding box is not guaranteed to give you a box that strictly contains all elements, e.g. due to convex curved boundaries.

I would need to test that for our "special mesh" but if the algorithm works better than before i don't see a problem.

@juan42 were you able to test on your mesh? We'd like to merge #313 as part of the mfem-3.3.2 release this week.

Works fine for me!

Fixed in #313.


[grafana] use dashboard provider to load dashboards from local file

Signed-off-by: Ziqi Zhao<EMAIL_ADDRESS>Fixes for  https://cloud-native.slack.com/archives/C03B4CWV4DA/p1665417709142739
Use grafana dashboard provider to provision dashboards

This is already fixed in #515


community[patch]: fix data.usage error because Moonshot sometimes does not return

Moonshot does not return data.usage when stream is true. So we need to add a default value to avoid errors.

Thank you!


Does not work anymore

i think part of the reason it doesn't work anymore is that valve changed the domain used for websockets and that
from *.cm.steampowered.com to *.steamserver.net

I removed the dep to the missing json_viewer, fixed the url and made a new wildcard for that url.
Iam still unable to capture wss traffic.

I removed the dep to the missing json_viewer, fixed the url and made a new wildcard for that url. Iam still unable to capture wss traffic.

It got broken another way


Haskell Package beam-core is broken

Describe the bug
[cody@nixos:~$ nix-shell -p '(haskellPackages.ghcWithPackages (p: [p.beam-core]))'
these derivations will be built:
  /nix/store/fcqfjnbf695rqv1k6q870cmcnckvh2pp-beam-core-<IP_ADDRESS>.drv
  /nix/store/hlj38hvvmzll9787lgdnr9rw99zpwcj1-ghc-8.8.3-with-packages.drv
building '/nix/store/fcqfjnbf695rqv1k6q870cmcnckvh2pp-beam-core-<IP_ADDRESS>.drv'...
setupCompilerEnvironmentPhase
Build with /nix/store/jd57710zy096m0b1g3rd41wj10ajw7c5-ghc-8.8.3.
unpacking sources
unpacking source archive /nix/store/mm1v409lvbpf3mr1nb453k08pwm4f796-beam-core-<IP_ADDRESS>.tar.gz
source root is beam-core-<IP_ADDRESS>
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file beam-core-<IP_ADDRESS>/Database/Beam/Backend/SQL/Row.hs
patching sources
compileBuildDriverPhase
setupCompileFlags: -package-db=/build/setup-package.conf.d -j4 -threaded
[1 of 1] Compiling Main             ( Setup.hs, /build/Main.o )
Linking Setup ...
configuring
configureFlags: --verbose --prefix=/nix/store/x7s1j53k5ik1hb4hrbc1n9myv8sz3qd5-beam-core-<IP_ADDRESS> --libdir=$prefix/lib/$compiler --libsubdir=$abi/$libname --docdir=/nix/store/lzwf61jq1lwgfvbdwzia2xwxk9h3phmi-beam-core-<IP_ADDRESS>-doc/share/doc/beam-core-<IP_ADDRESS> --with-gcc=gcc --package-db=/build/package.conf.d --ghc-option=-j4 --disable-split-objs --enable-library-profiling --profiling-detail=exported-functions --disable-profiling --enable-shared --disable-coverage --enable-static --disable-executable-dynamic --enable-tests --disable-benchmarks --enable-library-vanilla --disable-library-for-ghci --ghc-option=-split-sections --extra-lib-dirs=/nix/store/49x12wk4l8c0lh97crvwhjbzfxrq1fa2-ncurses-6.2/lib --extra-lib-dirs=/nix/store/hfs34n1yww7ba1m8gbrwrwh6v1y269m6-libffi-3.3/lib --extra-lib-dirs=/nix/store/l9nfr0znv7qibrapym32qj7dxmynfh84-gmp-6.2.0/lib
Using Parsec parser
Configuring beam-core-<IP_ADDRESS>...
CallStack (from HasCallStack):
  die', called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:1022:20 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configureFinalizedPackage, called at libraries/Cabal/Cabal/Distribution/Simple/Configure.hs:475:12 in Cabal-<IP_ADDRESS>:Distribution.Simple.Configure
  configure, called at libraries/Cabal/Cabal/Distribution/Simple.hs:625:20 in Cabal-<IP_ADDRESS>:Distribution.Simple
  confHook, called at libraries/Cabal/Cabal/Distribution/Simple/UserHooks.hs:65:5 in Cabal-<IP_ADDRESS>:Distribution.Simple.UserHooks
  configureAction, called at libraries/Cabal/Cabal/Distribution/Simple.hs:180:19 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMainHelper, called at libraries/Cabal/Cabal/Distribution/Simple.hs:116:27 in Cabal-<IP_ADDRESS>:Distribution.Simple
  defaultMain, called at Setup.hs:2:8 in main:Main
Setup: Encountered missing or private dependencies:
hashable >=1.1 && <1.3, vector-sized >=0.5 && <1.3

builder for '/nix/store/fcqfjnbf695rqv1k6q870cmcnckvh2pp-beam-core-<IP_ADDRESS>.drv' failed with exit code 1
cannot build derivation '/nix/store/hlj38hvvmzll9787lgdnr9rw99zpwcj1-ghc-8.8.3-with-packages.drv': 1 dependencies couldn't be built
error: build of '/nix/store/hlj38hvvmzll9787lgdnr9rw99zpwcj1-ghc-8.8.3-with-packages.drv' failed

To Reproduce
Steps to reproduce the behavior:
nix-shell -p '(haskellPackages.ghcWithPackages (p: [p.beam-core]))'

Expected behavior
Landing in a nix shell after successfully building beam-core.
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 5.5.9, NixOS, 20.09pre217537.d96bd3394b7 (Nightingale)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.3
channels(root): "nixos-20.09pre217537.d96bd3394b7"
channels(cody): "home-manager"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Please feel free to send a PR fixing this.

It looks like no one ended up working on this, so I am going to go ahead and close it.  Please feel free to re-open (or send a PR) if you're still interested in this.


Is it possible to update Clusterize but keep the previous elements visible?

Assuming I have N rows and I use the search method (from the example), would it be possible to somehow set the irrelevant rows as visible but to start from the 1st active row? e.g
[
 { value: 1, active: true, visible: true },
 { value: 2, active: true, visible: true },
 { value: 3, active: true, visible: true },
 { value: 4, active: true, visible: true },
 { value: 5, active: true, visible: true },
 { value: 6, active: true, visible: true },
 { value: 7, active: true, visible: true }
]
search(4)
[
 { value: 1, active: false, visible: true },
 { value: 2, active: false, visible: true },
 { value: 3, active: false, visible: true },
 { value: 4, active: true, visible: true },
 { value: 5, active: true, visible: true },
 { value: 6, active: true, visible: true },
 { value: 7, active: true, visible: true }
]

Basically I would like to create a way to scroll back after searching.
Thanks,
Shaked

I struggled with the same issue on a UL list I wanted to bind a click event on a LI and add class 'active' to it, once scrolling and clusterize renewed the list and going back, the selected LI lost is active state. I found a solution for this, maybe this can help you. Here is my codepen test.
https://codepen.io/PlippiePlop/pen/vegozV
The one issue I did not get around was when selecting the item and going to another page and coming back to the page with the list, getting/scroll back to the  selected event in the large list.

Your codepen test is not there anymore, can you provide what you did?

updated the link...


Added Tower of Hanoi Implementation with Stack

Excellent work @abhpd  Thanks a lot for making this PR.

Thanks for Merging @amitsaini4556 it is always a pleasure to contribute.


close browser before opening another one

When running the following test, you will see two browser windows. One of them wont be closed after the test.
$this->visit('/createSomething')
     ->submitForm('Save', ['name' => 'Jonny'])
     ->visit('/overview')
     ->see('Jonny');

Why do you open a new page? The user should be redirected to a page right? Why don't you check for that instead of visiting a new page?
->seePageIs('/overview')

The user should be redirected to a page right?

no

Why do you open a new page?

I wrote some tests for an old project. I create a customer first and then I want to check if the customer is listed on the customer-overview. There is no redirect and no link that I can follow.

In that case it would be easier to check if the user exists in the database instead of visiting another page


Add repo to drone rancher pr/publish

https://github.com/rancherlabs/eio/issues/491

Request Granted, closing issue


Add "query params" support

Hello, clayallsopp.
I just add "query params" support to Router. Url like /users/4?name=router will add a "name" param with value "router" in Intent's extras or callback's params.
I am realy sorry there is many changes of your code, but I swear to god, I just change some codes between line 364 to line 407, "private RouterParams paramsForUrl(String url)", and add two method Map<String, String> parseQueryParams(String queryPart) and Map<String, String> mergeMaps(Map<String, String> map1, Map<String, String> map2).
It's because of the IDE "Android Studio", it automatically reformat the code, please be aware.

Thanks for contributing this! I've merged #13, which is a slightly different way but solves the same problem. Give that a shot and let me know what you think!

Great!


⚠ Bofrost.es has degraded performance

In 85be6ab, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1383 ms

Resolved: Bofrost.es performance has improved in 866d884 after 3 hours, 58 minutes.


Add test with nullable field to demonstrate Fletchgen issue

This reproduces the issue encountered by Mengfei when using nullable fields. It breaks the sum example when modified to have a nullable field.
This PR should not be merged but can be used to reproduce the issue.

Elaborating simtop_tc...
Running simtop_tc...
/usr/local/bin/ghdl:error: bound check failure at /home/vsts/work/1/s/examples/nullable-sum/hardware/vhdl/Sum_ExampleBatch.gen.vhd:99
  from: work.sum_examplebatch(implementation).DEFAULT_CNFIG.arrayreader at Sum_ExampleBatch.gen.vhd:106
/usr/local/bin/ghdl:error: error during elaboration

This is due to the config string generating an extra bit for validity bitmaps that are not present on the command stream to array readers.
There is a test for the data channel widths vs. config string generated widths but not for the command channel widths vs. config string generated widths.
A fix would need to add this test and add the extra bits for any nullable types (potentially nested) as vhdmmio control field and properly connect it at the nucleus level. At the nucleus level, to merge vhdmmio's output (buffer addresses) and the kernel's command stream output (first and last index) a vhdl component is used called ArrayCmdCtrlMerger. This would need to be extended to allow for these bit to be merged onto the command stream coming from the mmio.
A work-around would be to correct the size of this channel and start implementing from the nucleus rather than the kernel level of abstraction.


Using SSL with client libraries and Flight in Windows (tls certs, errors, workarounds)

Here is how we solved it within the new client library:

import influxdb_client_3 as InfluxDBClient3
import pandas as pd
import numpy as np
from influxdb_client_3 import flight_client_options
import certifi

fh = open(certifi.where(), "r")
cert = fh.read()
fh.close()

client = InfluxDBClient3.InfluxDBClient3(
    token="",
    host="b0c7cce5-8dbc-428e-98c6-7f996fb96467.a.influxdb.io",
    org="6a841c0c08328fb1",
    database="flightdemo",
    flight_client_options=flight_client_options(
        tls_root_certs=cert))

table = client.query(
    query="SELECT * FROM flight WHERE time > now() - 4h",
    language="influxql")

print(table.to_pandas())

Its not perfect as you have to rely on the certifi library to provide the root certificate. Hopefully it gets solved upstream i believe it might be a grpc issue

https://influxdata.slack.com/archives/C04768675QD/p1690559401432409?thread_ts=1690558637.363649&cid=C04768675QD

Start with Python. Add other examples using https://grpc.io/docs/guides/auth/#using-client-side-ssltls


Update to 2.0

Started update to newer SmartSim and TF Agents versions.

[x] Use  new Python TOML package builder
[ ] Update README.md with new Marenostrum5 installation instructions
[ ] Update RL scripts for TF Agents 0.19.0
[ ] Update SmartSim scripts for 0.7.0

This is actually going to be implemented in https://github.com/b-fg/SmartSOD2D/pull/2.


Including patches fixing Ant and Maven build of MCF source code releases

The latest version of ManifoldCF source code package includes some issues related to build these connectors: Solr, CSV and Nuxeo connector.
The SDK can manage this adding some string replacement strategies and make easier for everyone to implement custom extensions and connectors for ManifoldCF.

Included in the 0.0.2-SNAPSHOT tag


beets: version from command is 2.1.0, while the source is obtained from a GitHub release titled 2.2.0

Describe the bug
$ result/bin/beet --version
beets version 1.6.1
Python version 3.12.7
plugins: chroma

Steps To Reproduce
Steps to reproduce the behavior:

nix build .#beets
result/bin/beet --version

Expected behavior
Expected the version of the package, 2.0.0.
Screenshots

Additional context

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 6.11.10-300.fc41.x86_64, Fedora Linux, 41.20241205.0 (Sway Atomic), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Lix, like Nix) 2.91.1
System type: x86_64-linux
Additional system types: aarch64-linux
Features: gc, signed-caches
System configuration file: /etc/nix/nix.conf
User configuration files: /home/jordan/.config/nix/nix.conf:/etc/xdg/nix/nix.conf
Store directory: /nix/store
State directory: /nix/var/nix
Data directory: /nix/store/lknx1arna0x37dg61ixsjbdlwcy9dvld-lix-2.91.1/share`
 - nixpkgs: `/nix/store/w66xaybnxjf5zhxapxs3pd3zp7gxk9dw-source`

Notify maintainers

@aszlig @doronbehar @lovesegfault @pjones

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

This is an upstream issue. I installed beets 2.0.0 on openSUSE and got the following output:
$ beet --version
beets version 1.6.1
Python version 3.11.10
no plugins loaded

It would be great if we could patch it. It's blocking me from packaging beets-audible which requires beets 2.0.0.

Unless I'm mistaken I think this issue upstream may deal with it? If so proposed fix is in there.
https://github.com/beetbox/beets/issues/5539

Looks like it should be fixed in #358086

Fixed by #358086. Thanks for pinging this issue.

With #358086 I get:
./result/bin/beet --version
beets version 2.1.0
Python version 3.12.7
no plugins loaded

Yes, the upstream issue is still present:

https://github.com/beetbox/beets/issues/5539

I've updated this issue's title to match the current state of things, but I'll keep the issue closed.

I am to blame for this hiccup, apologies! It's addressed in this PR and should hopefully not happen again.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/cannot-get-beets-package-to-update/57499/4


Feature Request: an option to disable mandatory md5 checksum on boot

Hi,
It would be wonderful to have an option to disable the mandatory md5 checksum on boot letting only one line in the md5sum.txt file.
BR,
Ib

Hi, thank you for your feature request. I have implemented it with the new -c option.


add pilot end-to-end test for routing rules to outboud traffic

What this PR does / why we need it:
add pilot end-to-end test for routing rules to outboud traffic defined by egress rules
Special notes for your reviewer:
This PR adds the first test of routing rules to egress rules:
fault injection to httpbin.org
more tests to follow...
Release note:

NONE

Hi @ronenschafferibm. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

/ok-to-test

@nmittler since you have gained some good familiarity with the test pieces (in addition to others), would you like to shepherd this through?

@rshriram sure I'll take a look

This LGTM.
@ZackButcher do you want to take a peek for go-isms, etc?

/test cla/google

/lgtm by https://github.com/istio/istio/pull/2016#issuecomment-350051851

/lgtm

/test all

I signed it!


npmignore: Do not publish yarn.lock file

... as discussed on Slack
see also https://twitter.com/kentcdodds/status/786704147248807936

yeah, was just thinking the same thing...

package-lock.json might not be necessary though

One key detail about package-lock.json is that it cannot be published

from https://docs.npmjs.com/files/package-lock.json


Calling config.get() within a config() function.

The goal is to set the unique_key just once and reuse it across.
Example 1:
{% set unique_key='borrower_address_id' %}
{{ config(materialized='incremental', unique_key=unique_key) }}
{{ config(post_hook="CREATE UNIQUE INDEX IF NOT EXISTS {{ this.table }}_idx ON {{ this }} ({{ unique_key }})")}}

OR (even better):
{{ config(materialized='incremental', unique_key='borrower_address_id') }}
{{ config(post_hook="CREATE UNIQUE INDEX IF NOT EXISTS {{ this.table }}_idx ON {{ this }} ( config.get('unique_key')")}}

The latter code is preferred as it does not mix JINJA with non-JINJA contexts. And, above all, the call to config.get() should just work, right?

Thanks for the report @rpammeraal! The first example would be pretty tricky to implement, as the hook config specifically is evaluated in a different context than the rest of the jinja code shown here!
I think it's totally doable and a very good idea for us to support the second example you've shown above:
{{ config(materialized='incremental', unique_key='borrower_address_id') }}
{{ config(post_hook="CREATE UNIQUE INDEX IF NOT EXISTS {{ this.table }}_idx ON {{ this }} ( config.get('unique_key')")}}

These context questions are sometimes intertwined in ways that aren't obvious at first-blush. If this is straightforward to implement, we should do it!
If you're in a pinch though, I did want to suggest a potential workaround:
{% set unique_key='borrower_address_id' %}
{{ config(materialized='incremental', unique_key=unique_key) }}
{{ config(post_hook="CREATE UNIQUE INDEX IF NOT EXISTS {{ this.table }}_idx ON {{ this }} (" ~ unique_key ~ ")") }}

This "hoists" the interpolation of the unique_key out of the hook config and into the wrapping config call where it will be in scope!

Let's use this as an opportunity to rationalize the SourceConfig module in dbt. It might be a lot, a lot more work than fixing this acute issue, but it will fundamentally make parsing and configuring objects simpler and more consistent in dbt.


Connecting to couchbase?

I am attempting to use a Couchbase memcached to test some code in development, but I can't seem to connect to it. I keep getting the same error
server=<IP_ADDRESS>:11211, tokens=[11211, <IP_ADDRESS>], messages=[unauthorized, null bucket], failures=5, totalFailures=0

Is there some specific way I have to configure this to connect to the memcached bucket?

You're probably better off using https://www.npmjs.com/package/couchbase

@ronkorving The issue with that is that we are actually using memcached in real environments, I just wanted to get something simple up and running on my local machine so I could test something out.

I've used this module (memcached) successfully to connect to Couchbase in the past, but it's been ages tbh.

Yeah, I've seen other mentions in the issues about other people who have used it, but I don't see any examples at all about how to configure it (and clearly based on the errors I'm getting, something's not set up right).

In the basics it should work, but for me the last time using it is a while ago too. The only thing I can think of and that seems to match with the error message is authentication. Did you enable authentication on the bucket? Because you cannot do that on membase buckets.


Update sdk to 6.5.0

Bump version of maven-archetypes to 2.4.0
Add org.hibernate.validator:hibernate-validator:6.2.0.CR1 provided scope
org.apache.maven.plugins:maven-compiler-plugin  upgraded to 3.8.1
source + target changed to 11
Kotlin version updated to 1.5.10 (artifactId:kotlin-stdlib-jdk8)

Thanks for taking the time @jarryDk !


embed_bqm should handle dimod.AdjArrayBQM

Since dimod.AdjArrayBQM is not "shapeable", it doesn't support methods like add_variables_from, and embed_bqm fails if the source BQM was of AdjArrayBQM type. A fix in 5af1c10c72bfbd8130e943260103a5f70f11a9a8 makes target bqm inherit from source bqm's type.
Sampling traceback, for example:
  ...
    sampleset = sampler.sample(bqm, return_embedding=True, **self.params)
  File "/home/radomir/work/dwave-inspector/env/lib/python3.7/site-packages/dwave/system/composites/embedding.py", line 476, in sample
    return super(LazyFixedEmbeddingComposite, self).sample(bqm, **parameters)
  File "/home/radomir/work/dwave-inspector/env/lib/python3.7/site-packages/dwave/system/composites/embedding.py", line 243, in sample
    smear_vartype=dimod.SPIN)
  File "/home/radomir/work/dwave-inspector/env/lib/python3.7/site-packages/dwave/embedding/transforms.py", line 125, in embed_bqm
    target_bqm.add_variables_from({u: b for u in chain})
AttributeError: 'AdjArrayBQM' object has no attribute 'add_variables_from'

Proposed fixes: either use a shapeable target, or explicitly fail when source is non-shapeable.

I am leaning towards it always creating an AdjDictBQM, since at the scale that we're embedding the flexibility is probably more important than anything else. However, it does seem a bit surprising for the function to change BQM type.

Closed by #310 , which defaults to AdjVector when the BQM is not shapeable.


Add support for [FromServices] attribute

ASP.NET Core supports method injection in its MVC controllers through the use of the FromServices attribute. Simple Injector does not support this, and there is currently no intention in supporting this. This issue is merely a description on what it takes to add support for this in the ASP.NET Core integration package.
Things to take into consideration:

The default ASP.NET Core MVC implementation is strongly coupled to the built-in DI Container. This means that a [FromServices]-marked method argument, will always be resolved from the ASP.NET Core configuration system; not from Simple Injector.
When this feature gets implemented, it should be integrated into the Diagnostic subsystem. In other words, the container should be told that an [FromServices]-marked method argument is a KnownDependency of the specific controller. This allows object graphs to be visualized that include those services and analysis to be performed based on the relationship of the method-injected dependency with its consuming controller.
Due to the nature of how MVC works (with its model binder providers) and how method injection works, it seems hard to apply context-based injection on such dependency, e.g. An Index([FromServices]ILogger logger) method on an HomeController, whould ideally get an Logger<HomeController> injected in case the user uses Simple Injector's .AddLogging() extension method. This might not be possible, but further investigation is required.
The Potential Single Responsibility Violation message would likely be generated when a user starts using the [FromServices] attribute. A decision needs to be made whether counting of dependencies should be limited to constructors or not. If so, a change to the core library is required, separating dependency types (e.g. constructor, property, method, other).
When a [FromServices] dependency is not registered, verification should fail.

ASP.NET Core will, by default, resolve a [FromServices] dependency from the built-in configuration system—not from Simple Injector. These calls can be intercepted by replacing ASP.NET Core's Microsoft.AspNetCore.Mvc.ModelBinding.Binders.ServicesModelBinderProvider. A possible implementation might look as follows:
public class SimpleInjectorServicesModelBinderProvider : IModelBinderProvider
{
    private readonly SimpleInjectorServicesModelBinder modelBinder;

    public SimpleInjectorServicesModelBinderProvider(Container container)
    {
        this.modelBinder = new SimpleInjectorServicesModelBinder(container);
    }

    public IModelBinder GetBinder(ModelBinderProviderContext context)
    {
        if (context == null)
        {
            throw new ArgumentNullException(nameof(context));
        }

        if (context.BindingInfo.BindingSource != null &&
            context.BindingInfo.BindingSource.CanAcceptDataFrom(BindingSource.Services))
        {
            return modelBinder;
        }

        return null;
    }

    private sealed class SimpleInjectorServicesModelBinder : IModelBinder
    {
        private readonly Container container;

        public SimpleInjectorServicesModelBinder(Container container)
        {
            this.container = container;
        }

        /// <inheritdoc />
        public Task BindModelAsync(ModelBindingContext bindingContext)
        {
            if (bindingContext == null)
            {
                throw new ArgumentNullException(nameof(bindingContext));
            }

            var model = this.container.GetInstance(bindingContext.ModelType);

            bindingContext.ValidationState.Add(
                model, new ValidationStateEntry() { SuppressValidation = true });

            bindingContext.Result = ModelBindingResult.Success(model);
            return Task.CompletedTask;
        }
    }
}

This custom binder provider can replace the built-in one:
mvcOptions.ModelBinderProviders.RemoveType<ServicesModelBinderProvider>();
mvcOptions.ModelBinderProviders.Add(new SimpleInjectorServicesModelBinderProvider(container));

Limitations of this implementation:

No contextual injection; method-injected dependencies are considered to be root types.

This is part of the solution. What's still missing here is the integration with the diagnostics subsystem. This is likely something that should be done inside the AddControllerActivation() extension method. This likely involves the registration of a ExpressionBuilding or ExpressionBuilt event,  because this is the interception point that allows informing Simple Injector about known dependencies.
Resources:

Current documentation page on FromServices

What are your thoughts about supporting "minimal api" service injection with SimpleInjector?
Minimal api routig will probably get a commonly used alternative to controllers. And the [FromServices] attribute isnt even required anymore because internally the framework checks if arguments are registered services by using the IServiceProviderIsService interface (Docs).
It is still possible to use FromServices to make the binding decisions explicit, but its optional.
See parameter binding docs.
So does this issue also cover minimal apis and are minimal api endpoints without FromServices attribute a dead-end for SimpleInjector?

I've been reading through the MS docs on minimal APIs to understand what it is. I'm not sure I fully support the idea, but that's besides the point.
Unfortunately, as far as I can see by looking at the .NET 6 code base, any interception point that allows resolving any service argument from Simple Injector is missing. The docs contain the following example:
app.MapGet("/{id}", (int id, int page, Service service) => { });

This allows Service to be resolved in case it is registered in MS.DI. But this is hard-wired to the built-in container. As Simple Injector is a 'non-conforming' container, the framework must have a hook that would allow Simple Injector to intercept the call to resolve Service. But after inspecting the source code of EndpointRouteBuilderExtensions and RequestDelegateFactory, I have to conclude any required hooks are missing. This disallows a method such as the above where Simple Injector-registered services are added to the mapped delegate definition.
A model, however, that I've been promoting for a number of years now has many similarities to the new .NET 6 minimal API model. This model is described in the SOLID Services POC on GitHub. In SOLID services, instead of relying on manually defined mappings using app.MapGet(...) (as the above code snippet shows), the API is defined by the specified query and command objects. Using reflection, a similar mapping is made that maps an incoming request to an underlying handler. This solution uses Simple Injector to demonstrate the concept.
From a Minimal API perspective, the SOLID Services 'map' requests similar to what would be the following with Minimal API:
app.MapGet("/api/queries/GetOrderById/{OrderId}", (int OrderId) => (OrderInfo)null);
app.MapGet("/api/queries/GetUnshippedOrdersForCurrentCustomer", (GetUnshippedOrdersForCurrentCustomerQuery query) => (Paged<OrderInfo>)null);
app.MapPost("/api/commands/CreateOrder", (CreateOrderCommand command) => { });
app.MapPost("/api/commands/ShipOrder", (ShipOrderCommand command) => { });

The SOLID Services project contains an ASP.NET Core example, although it uses an ASP.NET Core 3.1. It might be useful to add an example project that plugs in into the new Minimal API structure, because it likely gives many advantages (such as generation of API documentation, which the current 3.1 project doesn't support).

@davidroth,
Even better, the SOLID Services now contains an example project that uses ASP.NET Core 6 Minimal API, which actually drastically simplifies the amount of code needed to wire this up.
Without the optional Swagger configuration, the Program file is not much more than this:
var builder = WebApplication.CreateBuilder(args);
var services = builder.Services;
var container = new Container();

services.AddSimpleInjector(container, options =>
{
    options.AddAspNetCore();
});

Bootstrapper.Bootstrap(container);

var app = builder.Build();

app.MapCommands("/api/commands/{0}", container, Bootstrapper.GetKnownCommandTypes());
app.MapQueries("/api/queries/{0}", container, Bootstrapper.GetKnownQueryTypes());

app.Run();

Here MapCommands and MapQueries are custom extension methods that iterate the list of known command and query types and do the appropriate app.MapPost(...) calls.
This model ties completely into the ASP.NET Core pipeline, but with all the advantages that the ICommandHandler<T> and IQueryHandler<TQuery,  TResult> bring to the table.

Thanks for your thoughts steven! The Solid services example is nice. Unfortunately the query string issue a real blocker for many scenarios.
Beside from that, it would still be nice to have the option to use lambdas and SimpleInjector without the dynamic command dispatch helpers. But I see the problem when RequestDelegateFactory is once again hard coded against ServiceProvider :-/

Unfortunately the query string issue is a real blocker in many scenarios.

I accept pull requests ;-)

Last week I tried to implement a more 'REST-full' method making use of the new .NET 6 Map API, but this proved to be extremely difficult. That new API analyzes the structure (input and return parameters) of the supplied delegate and uses this to construct a route and build an explorable API.
Because I'd like messages to be 'batch-registered' in the API, those delegates need to be auto-generated. Supplying a compiled expression, unfortunately, breaks the Map API, because compiled expressions lack parameter names and don't allow retrieving their custom attributes. An alternative is using LCG to generate classes with methods dynamically, but this is an awful lot of work, and was a path I stopped pursuing.
Two alternative remain: implementing this through source generators or providing Microsoft with a feature and pull request in the hope that a future version of Minimal API gives more flexibility.


Update transitive dependencies

There is a high-severity security vulnerability in lodash which is one of our transitive dependencies. Run an npm update to bump all locked dependencies to their latest versions, including lodash.
This is a development dependency (and our only one at this point), so there is no need for security advisories for our users.

Oh those dependencies!


upgrading requests to urllib3 makes propagates fail with IncompleteRead

as part of #389, i tried upgrading tweepy to 3.3 (snarfed/oauth_dropins@68e6ea944f3e4fd22bbde54fb285aa052c1222a1), which included upgrading python-requests to 2.6.2 which uses urllib3 instead of httplib2. that made propagate tasks start failing with IncompleteReads, probably due to a mismatch in handling for chunked requests (Transfer-Encoding: chunked). not sure how to fix this quite yet.
example log:
Starting Response repost tag:twitter.com,2013:592796217396076546 https://twitter.com/svaroschi/status/592796217396076546
Webmention from https://brid-gy.appspot.com/repost/twitter/mathewi/592795567140536323/592796217396076546 to http://www.mathewingram.com/work/2015/04/27/eu-publishers-sign-deal-with-google-but-are-they-focusing-on-the-right-enemy/
Sending...
Starting new HTTP connection (1): www.mathewingram.com
"GET /work/2015/04/27/eu-publishers-sign-deal-with-google-but-are-they-focusing-on-the-right-enemy/ HTTP/1.1" 200 None

Traceback (most recent call last):
  File "/base/data/home/apps/s~brid-gy/3.383902397363262415/tasks.py", line 478, in do_send_webmentions
    if not mention.send(timeout=999, headers=util.USER_AGENT_HEADER):
  File "/base/data/home/apps/s~brid-gy/3.383902397363262415/webmention-tools/webmentiontools/send.py", line 24, in send
    self._discoverEndpoint()
  File "/base/data/home/apps/s~brid-gy/3.383902397363262415/webmention-tools/webmentiontools/send.py", line 30, in _discoverEndpoint
    r = requests.get(self.target_url, verify=False, **self.requests_kwargs)
...
  File "/base/data/home/apps/s~brid-gy/3.383902397363262415/activitystreams/oauth_dropins/requests_module/requests/packages/urllib3/response.py", line 304, in stream
    for line in self.read_chunked(amt):
  File "/base/data/home/apps/s~brid-gy/3.383902397363262415/activitystreams/oauth_dropins/requests_module/requests/packages/urllib3/response.py", line 411, in read_chunked
    raise httplib.IncompleteRead(''.join(line))
IncompleteRead: IncompleteRead(16 bytes read)
Error sending to endpoint: {'code': 'EXCEPTION'}

Keep an eye on https://github.com/shazow/urllib3/issues/618

Looking....

tried the latest version of requests (2.8.1) just now, but no luck, at least in dev_appserver. traceback below.
2.8.1 was released after those commits, but they're evidently not merged into requests, and it's unclear if they will be. (i also tried installing the latest urllib3 (1.12) manually, but i expect requests still used the version it bundles.)
ah well. i'll try again in a while!
Traceback (most recent call last):
...
  File "/Users/ryan/src/bridgy/twitter.py", line 134, in post
    return self.start_oauth_flow(util.get_required_param(self, 'feature'))
  File "/Users/ryan/src/bridgy/twitter.py", line 106, in start_oauth_flow
    return handler.post()
  File "/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/oauth_dropins/handlers.py", line 101, in post
    url = self.redirect_url(state=self.request.get('state'))
  File "/Users/ryan/src/bridgy/util.py", line 512, in redirect_url
    self.construct_state_param_for_add(state, **kwargs))
  File "/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/oauth_dropins/twitter.py", line 145, in redirect_url
    signin_with_twitter=not self.access_type, access_type=self.access_type)
  File "/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/tweepy/auth.py", line 85, in get_authorization_url
    self.request_token = self._get_request_token(access_type=access_type)
  File "/Users/ryan/src/bridgy/local/lib/python2.7/site-packages/tweepy/auth.py", line 68, in _get_request_token
    raise TweepError(e)
TweepError: ('Connection aborted.', error(13, 'Permission denied'))

http://stackoverflow.com/a/35944044/186123 told me requests 2.10.0 + requests-toolbelt works...and it does! yay!

reopening until we figure out sigmavirus24/requests-toolbelt#141.

yay, done!


[FEATURE]: Open Container is mapped to DPAD-UP on gamepad

What happened?
Currently, open container / take one / take all are hardcoded to the favorites key / activate / ready weapon, respectively. However on gamepad, the favorites key is by default tied to DPAD Up, which is needed to navigate the QuickLootIE menu.
One way to alleviate this issue would be to add an option to change keybindings, or to move away from using favorites as the key.
Version
2.0.0
What Skyrim version are you using?
1.6.1170
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Duplicate of #51, closing this. I don't want multiple issues tracking similar things.


Save errors as list when performing bulk ticker downloads

I'd like to be able to save the tickers that fail to download as a list so that I can update my list of tickers for stocks daily rather than having to copy the console output of the data function and clean the data - is there a way to include this functionality in yfinance? Attempting to download all ASX listed stocks produces this list but fails to remove them from 'data'. Is there a way to automatically remove the failed downloads from data or to have it as a variable say data.errors()?
[100%**]  2189 of 2189 completed
178 Failed downloads:

EMD.AX: No data found, symbol may be delisted
CST.AX: No data found for this date range, symbol may be delisted
PPZ.AX: No data found, symbol may be delisted
XPD.AX: No data found, symbol may be delisted
LI1.AX: No data found, symbol may be delisted
RT2.AX: No data found, symbol may be delisted
TT9.AX: No data found, symbol may be delisted
IMG.AX: No data found, symbol may be delisted
MBL.AX: No data found for this date range, symbol may be delisted
MEQ.AX: No data found for this date range, symbol may be delisted
SUM.AX: No data found, symbol may be delisted
MBJ.AX: No data found, symbol may be delisted
AO2.AX: No data found, symbol may be delisted
TT7.AX: No data found, symbol may be delisted
FM2.AX: No data found, symbol may be delisted
SCA.AX: No data found, symbol may be delisted
SS7.AX: No data found, symbol may be delisted
INH.AX: No data found, symbol may be delisted
WEJ.AX: No data found, symbol may be delisted
VPC.AX: No data found, symbol may be delisted
SAC.AX: No data found, symbol may be delisted
CU2.AX: No data found, symbol may be delisted
RTD.AX: No data found for this date range, symbol may be delisted
PUK.AX: No data found, symbol may be delisted
LLP.AX: No data found, symbol may be delisted
MPZ.AX: No data found, symbol may be delisted
SBK.AX: No data found, symbol may be delisted
NRO.AX: No data found, symbol may be delisted
RFE.AX: No data found for this date range, symbol may be delisted
TIH.AX: No data found, symbol may be delisted
AR1.AX: No data found for this date range, symbol may be delisted
TDY.AX: No data found, symbol may be delisted
MZ2.AX: No data found, symbol may be delisted
AYU.AX: No data found, symbol may be delisted
DXA.AX: No data found, symbol may be delisted
TNF.AX: No data found, symbol may be delisted
PUS.AX: No data found, symbol may be delisted
VPG.AX: No data found for this date range, symbol may be delisted
HVM.AX: No data found, symbol may be delisted
DAE.AX: No data found, symbol may be delisted
TOZ.AX: No data found, symbol may be delisted
NFN.AX: No data found, symbol may be delisted
NRM.AX: No data found for this date range, symbol may be delisted
INN.AX: No data found, symbol may be delisted
DMG.AX: No data found, symbol may be delisted
ANV.AX: No data found, symbol may be delisted
LTF.AX: No data found, symbol may be delisted
NAO.AX: No data found, symbol may be delisted
XCL.AX: No data found, symbol may be delisted
EMI.AX: No data found for this date range, symbol may be delisted
DAZ.AX: No data found, symbol may be delisted
AOR.AX: No data found for this date range, symbol may be delisted
DAM.AX: No data found, symbol may be delisted
SIX.AX: No data found, symbol may be delisted
WSO.AX: No data found, symbol may be delisted
PEU.AX: No data found, symbol may be delisted
PUB.AX: No data found, symbol may be delisted
SFV.AX: No data found, symbol may be delisted
RE1.AX: No data found, symbol may be delisted
MZT.AX: No data found, symbol may be delisted
KIG.AX: No data found, symbol may be delisted
SGL.AX: No data found for this date range, symbol may be delisted
LT1.AX: No data found, symbol may be delisted
WE1.AX: No data found, symbol may be delisted
LO1.AX: No data found, symbol may be delisted
MVT.AX: No data found, symbol may be delisted
WSN.AX: No data found, symbol may be delisted
SSF.AX: No data found, symbol may be delisted
AOJ.AX: No data found, symbol may be delisted
QNB.AX: No data found, symbol may be delisted
IDJ.AX: No data found, symbol may be delisted
WEF.AX: No data found, symbol may be delisted
IMQ.AX: No data found, symbol may be delisted
NFI.AX: No data found, symbol may be delisted
WSZ.AX: No data found, symbol may be delisted
WSQ.AX: No data found, symbol may be delisted
TNJ.AX: No data found, symbol may be delisted
DA1.AX: No data found, symbol may be delisted
WSH.AX: No data found, symbol may be delisted
PUJ.AX: No data found, symbol may be delisted
WEH.AX: No data found, symbol may be delisted
SM9.AX: No data found, symbol may be delisted
NIB.AX: No data found, symbol may be delisted
REK.AX: No data found, symbol may be delisted
SCD.AX: No data found for this date range, symbol may be delisted
SAZ.AX: No data found, symbol may be delisted
PUV.AX: No data found, symbol may be delisted
AO3.AX: No data found, symbol may be delisted
ATB.AX: No data found, symbol may be delisted
POV.AX: No data found, symbol may be delisted
LCN.AX: No data found, symbol may be delisted
RFC.AX: No data found, symbol may be delisted
WSD.AX: No data found, symbol may be delisted
IMO.AX: No data found, symbol may be delisted
KFW.AX: No data found, symbol may be delisted
EMT.AX: No data found, symbol may be delisted
POX.AX: No data found, symbol may be delisted
PUQ.AX: No data found, symbol may be delisted
MDZ.AX: No data found, symbol may be delisted
AVQ.AX: No data found, symbol may be delisted
PER.AX: No data found, symbol may be delisted
CBE.AX: No data found, symbol may be delisted
KEB.AX: No data found, symbol may be delisted
NAF.AX: No data found, symbol may be delisted
LT3.AX: No data found, symbol may be delisted
MZF.AX: No data found, symbol may be delisted
LI6.AX: No data found, symbol may be delisted
PU1.AX: No data found, symbol may be delisted
KOP.AX: No data found, symbol may be delisted
COS.AX: No data found for this date range, symbol may be delisted
NXR.AX: No data found for this date range, symbol may be delisted
CHJ.AX: No data found, symbol may be delisted
RDA.AX: No data found, symbol may be delisted
NAJ.AX: No data found, symbol may be delisted
MZC.AX: No data found, symbol may be delisted
XQL.AX: No data found, symbol may be delisted
HTB.AX: No data found, symbol may be delisted
MED.AX: No data found, symbol may be delisted
WLC.AX: No data found, symbol may be delisted
LI4.AX: No data found, symbol may be delisted
CU1.AX: No data found, symbol may be delisted
ICB.AX: No data found, symbol may be delisted
CM1.AX: No data found, symbol may be delisted
CCB.AX: No data found, symbol may be delisted
SHZ.AX: No data found, symbol may be delisted
PES.AX: No data found, symbol may be delisted
TTZ.AX: No data found, symbol may be delisted
MZ1.AX: No data found, symbol may be delisted
KI1.AX: No data found, symbol may be delisted
LGP.AX: No data found, symbol may be delisted
AOL.AX: No data found, symbol may be delisted
PUZ.AX: No data found, symbol may be delisted
IMK.AX: No data found, symbol may be delisted
INB.AX: No data found, symbol may be delisted
IFX.AX: No data found, symbol may be delisted
WEK.AX: No data found, symbol may be delisted
WSJ.AX: No data found, symbol may be delisted
MZA.AX: No data found, symbol may be delisted
TES.AX: No data found for this date range, symbol may be delisted
ELE.AX: No data found, symbol may be delisted
PUO.AX: No data found, symbol may be delisted
PSL.AX: No data found, symbol may be delisted
LI5.AX: No data found, symbol may be delisted
RFB.AX: No data found, symbol may be delisted
SCW.AX: No data found, symbol may be delisted
TNA.AX: No data found, symbol may be delisted
SPW.AX: No data found, symbol may be delisted
DGF.AX: No data found, symbol may be delisted
QBC.AX: No data found, symbol may be delisted
WEN.AX: No data found, symbol may be delisted
VCD.AX: No data found, symbol may be delisted
CHU.AX: No data found, symbol may be delisted
HCS.AX: No data found, symbol may be delisted
MHK.AX: No data found, symbol may be delisted
CSK.AX: No data found, symbol may be delisted
RTC.AX: No data found, symbol may be delisted
RT1.AX: No data found, symbol may be delisted
RT9.AX: No data found, symbol may be delisted
ZOR.AX: No data found, symbol may be delisted
TT1.AX: No data found, symbol may be delisted
IMN.AX: No data found, symbol may be delisted
NAH.AX: No data found, symbol may be delisted
PUU.AX: No data found, symbol may be delisted
TNB.AX: No data found, symbol may be delisted
LC1.AX: No data found, symbol may be delisted
WPG.AX: No data found, symbol may be delisted
XVG.AX: No data found, symbol may be delisted
TNH.AX: No data found, symbol may be delisted
KAU.AX: No data found, symbol may be delisted
PEP.AX: No data found for this date range, symbol may be delisted
SS6.AX: No data found, symbol may be delisted
IMX.AX: No data found, symbol may be delisted
IDH.AX: No data found, symbol may be delisted
POT.AX: No data found, symbol may be delisted
LT4.AX: No data found, symbol may be delisted
LI2.AX: No data found, symbol may be delisted
SXB.AX: No data found, symbol may be delisted
DAS.AX: No data found, symbol may be delisted

I'm accessing the failed tickers as in the example below.
Not sure if this resolves your issue?
import yfinance as yf
data = yf.download(tickers, start_date)
missing = list(yf.shared._ERRORS.keys())

I also have such a issues.
`data = yf.download(
tickers = tickerlist,
period = '1d',
interval = '1d',
group_by = 'ticker',
auto_adjust = False,
prepost = False,
threads = True,
proxy = None
)
data = data.T
values = []
for company in companylist:

    tickdata = data.loc[(company['tick'].upper(),),].T
    result = tickdata.reset_index().to_json(None, orient='records', date_format='iso')
    resultjson = json.loads(result)

    if len(resultjson) == 0:
        continue

    if (resultjson[0]['Open']) is None:
        continue`

I also have like that issues.
data = yf.download(
tickers = tickerlist,
period = '1d',
interval = '1d',
group_by = 'ticker',
auto_adjust = False,
prepost = False,
threads = True,
proxy = None
)
data = data.T
values = []
for company in companylist:

    tickdata = data.loc[(company['tick'].upper(),),].T
    result = tickdata.reset_index().to_json(None, orient='records', date_format='iso')
    resultjson = json.loads(result)

    if len(resultjson) == 0:
        continue

    if (resultjson[0]['Open']) is None:
        continue

Help me