How to stop multiple rows in logging error

Hello Team,
I'm new to NLog. I'm working on v4.7 to implement logging through file target. Based on various levels provided, I had noticed below while logging

For "Debug" level, for each message, only one line of text is added to file
For "Info" level, for each message, two lines of text is added to file
For "Error" level, for each message, three lines of text is added to file

I think, irrespective of level, the text added to log file should be single line., for this I added attribute concurrentWrites="false" for file target. But this didn't worked.
Is this a bug ? or should I need to add something?
Thanks in advance

Yes it's probably a bug in your <rules> ;)
Please note, all the  <rules>  are used for top to bottom. If one match, it still goes on to the next (unless you say so it should not)

Hi @304NotModified
Per you suggestion "Please note, all the  are used for top to bottom. If one match, it still goes on to the next", I kept only those rules which I wanted, and it worked as expected.
So does this mean, we can't continue to use more than one level of rule at a time?
And if used, multiple lines are logged ?

So does this mean, we can't continue to use more than one level of rule at a time?
And if used, multiple lines are logged ?

Sure you can, but please share your config, current and expected result. It's a bit of guessing now


Question: How can I use a custom glass definition

I am trying to model lens design from patents. With regards to the glass type, I only have the refractive index and abbe number for d-line. For example, 1.79668 and 45.5. As this is a Nikon patent I tried to see if there was any glass in the Hikari catalog matching this, but there isn't.
Is there a way to add my own glass type just using these two attributes?

If you want to use Opticspy, you can try to change the glass index folder.
Add some customized glass.
Dibyendu Majumdar<EMAIL_ADDRESS>于2019年9月29日周日 上午2:27写道：

I am trying to model lens design from patents. With regards to the glass
type, I only have the refractive index and abbe number for d-line. For
example, 1.79668 and 45.5. As this is a Nikon patent I tried to see if
there was any glass in the Hikari catalog matching this, but there isn't.
Is there a way to add my own glass type just using these two attributes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Sterncat/opticspy/issues/34?email_source=notifications&email_token=AAUIRBI7Y2ZNW2P24T5YAYLQMBYIJA5CNFSM4I3RUQZKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HOLWFTQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUIRBJWNIVY7W24JIPS2T3QMBYIJANCNFSM4I3RUQZA
.

Okay thank you for the information.


permit dynamic value for appended whitespace

i encountered a use case where it was useful to be able to change the appended whitespace while the page had already loaded. previously, this value was only updated on directive link.

@monospaced please review

Hi @monospaced can you review this PR?


Correction for raw affiliation AGAP, INRAE, CIRAD, Montpellier SupAgro, Univ Montpellier, San Giuliano, France; CBGP, INRAE, CIRAD, IRD, Montpellier SupAgro, Univ Montpellier, Montpellier, France

Correction needed for raw affiliation AGAP, INRAE, CIRAD, Montpellier SupAgro, Univ Montpellier, San Giuliano, France; CBGP, INRAE, CIRAD, IRD, Montpellier SupAgro, Univ Montpellier, Montpellier, France
raw_affiliation_name: AGAP, INRAE, CIRAD, Montpellier SupAgro, Univ Montpellier, San Giuliano, France; CBGP, INRAE, CIRAD, IRD, Montpellier SupAgro, Univ Montpellier, Montpellier, France
new_rors: 03rnk6m14;05kpkpg04;05q3vnk25;051escj72;003vg9w96;05h7ddb14
previous_rors: 03rnk6m14;05kpkpg04;05q3vnk25;051escj72;003vg9w96
works_examples: W4234160146;W4237749085;W4251293994
contact: 2f03094b59e90a41f838ae9672741f43:6fa568f116bbdbc48256b6a5de658fe29a72 @ inrae.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-18. The new affiliations should be visible within the next 7 days.


Install Packer binaries in the Rover container

Requesting to add the Packer binaries in the Rover container as there are requirements to create Custom Images.
Instructions to be included :
sudo yum-config-manager --add-repo https://rpm.releases.hashicorp.com/RHEL/hashicorp.repo
sudo yum -y install packer-${versionPacker}
cd /usr/bin
sudo mv packer packer.io   #CentOS has an existing package by the same name; so Packer has to be renamed.
ref : https://learn.hashicorp.com/tutorials/packer/getting-started-install?in=packer/getting-started
Thank you.

@LaurentLesle The Packer version to be specified is 1.6.4 (packer-1.6.4)

I think its just as safe to just drop an alias in the .bashrc as thats specific to the user space wheras "the other packer" is used by the system.
At any rate, I noticed this as well and ultimately just made a custom container for the company that adds the missing pieces .  The entire dockerfile could look like this:
ARG versionRover

FROM ${versionRover} as base

# note these MUST be unique from existing ENV in base
# or they will be ignored
ARG versionPacker

###
# Install Packer
###
RUN echo "Installing packer ${versionPacker}..."

Add to it with nomad or other tools you want included, and just call the rover version you want with the leading arg.

Thanks Justin. I have created an alpha version of the rover aztfmod/roveralpha:2010.140651
I put packer in the /usr/local/bin so it is picked-up without having to specify the alias in the .bashrc
We should have a vnext later this week

Thank you @LaurentLesle . It's working.


XML configuration file format

I was looking at an XML configuration file:
<!--Automatically generated Configuration file.-->
<configuration>
	<graphics screenwidth="1000" screenheight="700" bitdepth="60" fullscreen="false" vsync="false" />
	<audio mixrate="22050" channels="2" sfxvolume="128" musicvolume="128" bufferlength="1024" mixer="SDL" />
	<options>
		<option name="maximized" value="false" />
		<option name="skip-splash" value="true" />
	</options>
</configuration>

I noticed the <options> section doesn't follow the same format as the other section. If it did, it might end up looking more like:
<options maximized="false" skip-splash="true" />

Was there a particular reason for the change in format? I was thinking about writing more generic parsing code. Having a more consistent format could make that easier.
On the other hand, a clearer description of why the difference was chosen might also be helpful.
It might come down to simply being "because the programmer or file format said so". In which case, the kind of parsing needed could be decided at a higher level, and there could be two types of parsers, depending on which section you are trying to parse.

Ultimately, it seems configuration data is stored in sections, where each section consists of key/value pairs. We could potentially represent parsed data as key/value string pairs using a std::map.
Granted, the choice of strings for the value is largely due to the text file format, where all data must be serialized to/from string format. Some of those values actually represent integers or booleans, so there needs to be a bit of support for converting between such basic types and the storage format. The interface the game actually cares about is with the proper data types.

We could just drop XML entirely and use raw key-value pairs for config files:
#Automatically generated Configuration file.

#Graphics Options
screenwidth=1000
screenheight=700
refreshRate=60
fullscreen=false
vsync=false
maximizedwindow=false

#Audio options
audiomixrate=22050
audiochannels=2
sfxvolume=128
musicvolume=128
bufferlength=1024
mixer=SDL

#Game options
skipsplash=true

Yes, our needs for the configuration data are simple enough that an .ini file would suffice.
The Sprite data I believe is more involved, and probably wouldn't work so well with a flat format like .ini. We likely need either XML or JSON for that.
For now though, I want to avoid large format changes. I want to work on the API used to read configuration data, and only once that is abstracted enough do I want to worry about changing the internal format.
Which I suppose answers my own question. If current configuration files are written this way, and exist in that format on end user systems, we should probably stick with that format for now. Changing the config file format could break things for people who are currently testing the game. The config file is outside the scope of release packages, so wouldn't be overwritten by a new install. That may mean careful consideration to what happens in the Configuration class if an old configuration file format is found.
For the sake of end users, if we're going to change the format a little, maybe we should wait until we're ready to change it all the way, and perhaps convert to .ini files.

The Sprite data I believe is more involved, and probably wouldn't work so well with a flat format like .ini. We likely need either XML or JSON for that.

Yes. Absolutely. I should have been more clear, I was only referring to the config files and nothing else.

From an external discussion, it seems the difference in format was originally chosen to support unknown parameter names. Hence the parameter name ended up being a value accessed through the known name attribute.
Given the structure of the XML code, this distinction is not strictly necessary. The XML code allows reading arbitrary attribute names, and provides them in string form. As such, the original format could still be used for unknown parameter names.

Given the above, it seems we could reasonably change the file format to make things consistent. However, we might also consider that configuration files in the existing format are already out in the wild, so it may be wise to keep some support for them, at least for reading, so it doesn't negatively impact player experience.
What could be done is to write code to parse both formats, while perhaps only writing a single format, causing existing files to be updated to a newer consistent format.

Given the nature of the format is better understood now, I'm going to close this discussion.


Failures on [cfe] Include null check in shorting

There are new test failures on [cfe] Include null check in shorting.
The tests
co19_2/Utils/tests/Expect/identical_A01_t01 RuntimeError (expected Pass)
language/null_aware/null_shortening_test RuntimeError (expected Pass)
language/null_aware/null_shortening_test RuntimeError (expected Pass)

are failing on configurations
dart2js-hostasserts-strong-linux-x64-d8
dart2js-hostasserts-weak-linux-x64-d8
dart2js-linux-firefox
dartdevk-strong-linux-release-chrome
dartdevk-weak-linux-release-chrome
dartk-strong-linux-debug-x64
dartk-weak-asserts-linux-debug-x64
dartkp-strong-linux-release-x64
dartkp-weak-asserts-linux-release-x64

co19_2/Utils/tests/Expect/identical_A01_t01 was not caused by this commit.


fetchFromGitHub sha256 checksum error

I'm using Nix on OSX 10.10, with nixpkgs from GitHub. I can't get fetchFromGitHub to accept the sha256 checksum I supply to it for a repository. For example:
# default.nix
with import <nixpkgs> {};

stdenv.mkDerivation {
  name = "github-test";
  src = fetchFromGitHub {
    owner = "octocat";
    repo = "Spoon-Knife";
    rev = "d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9";
    sha256 = "71529cd6998a14f6482a78f078e1e868570f37b946ea4ba04820879479e3aa2c";
  };
  builder = ./builder.sh;
}

When I run nix-shell, I get the following error:
unpacking source archive /private/var/folders/nr/77qh9x2j1nbfc_gmy9v5smz40000gn/T/nix-build-Spoon-Knife-d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9-src.drv-0/d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9.tar.gz
output path ‘/nix/store/rqyyzn38i2vnp6hjp17synq3jyph0d7x-Spoon-Knife-d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9-src’ should have r:sha256 hash ‘1jzxn58pjxrnis7ca37rgsxflsx8578w4iyn3bzkdfn51d5k0l5c’, instead has ‘1imvnn0k59yban4drm8x3lsdhs8rvm1j854zghigd2pfhqk70ipn’
error: build of ‘/nix/store/wbjsg7cc9777yy8sbbsdsj6kf2gvcljv-Spoon-Knife-d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9-src.drv’ failed

These are the commands I used to generate the checksum of the repository:
$ curl -OL https://github.com/octocat/Spoon-Knife/archive/d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9.tar.gz
$ shasum -a 256 d0dd1f61b33d64e29d8bc1372a94ef6a2fee76a9.tar.gz

I also double-checked that the archive downloaded in the commands above indeed result in the correct archived repository. I also noticed that the sha256 checksum for the file changed at least once upon newly downloading the same archive from GitHub. Is there some nondeterministic behavior in downloading archives from GitHub in this way?

Use nix-prefetch-git to figure out the sha256 to use in your expression (or just look at the error message; that's what I do). It uses fetchzip to hash the contents of the tarball as opposed to the tarball itself, which as you noted will vary between downloads.

That fixes it! Can this perhaps be done in a more user-friendly way, or at least document this behavior at the definition of the fetchFromGitHub function?

What would be friendlier?
On Wednesday, March 11, 2015, Luis G. Torres<EMAIL_ADDRESS>wrote:

That fixes it! Can this perhaps be done in a more user-friendly way, or at
least document this behavior at the definition of the fetchFromGitHub
function?
—
Reply to this email directly or view it on GitHub
https://github.com/NixOS/nixpkgs/issues/6750#issuecomment-78260834.

I think it would be useful if a comment at the fetchFromGitHub definition in all-packages.nix briefly explained how to determine the sha256 field used when calling fetchFromGitHub.

I think it's just using the standard nix recursive directory hasher. Not sure how to invoke that manually, but maybe someone else is.

See man nix-hash - that should be the same hashes (with proper options passed).


Attached Model version shown as unknown

Describe the bug
In a project for labeling task, (Text classification in my case) with a model attached to the project, the model version is shown as unknown as shown in the provided screenshot.
Expected behavior
Either the correct model version is shown or the version label should not be shown at all, if the version is not available.
Screenshots

Environment (please complete the following information):

OS: Windows
Label Studio Version v1.01

@nawabhussain did you setup the model version in your /setup ML backend api call?

I was following the tutorial, It didn't seem to mention anything about /setup API call

Same problem here, I opened an issue on https://github.com/heartexlabs/label-studio-ml-backend/issues/121#issue-1263399401


Feature: adding a Candid-Rust binding crate

Overview
Why do we need this feature? What are we trying to accomplish?
Requirements
What requirements are necessary to consider this problem solved?
Considered Solutions
What solutions were considered?
Recommended Solution
What solution are you recommending? Why?
Considerations
What impact will this change have on security, performance, users (e.g. breaking changes) or the team (e.g. maintenance costs)?

@chenyan-dfinity PTAL.


[aurgerctl] Support for the json format as output

part of https://github.com/etcd-io/auger/issues/3

/cc @jmhbnz
/cc @siyuanfoundation

Done


The location of the sensor

Hello,
I have a quick question. Do you know where the acc sesor is attached? say chest or wrist
Best regards and many thanks!

Hello SteinPanyu,
I attached my 3D-Acceleration sensor on the chest around the sternum. I hope that helps you.
Greetings.

Thanks!


Fixing issue 1262: AWSTraceHeader is now propagated

:loudspeaker: Type of change

[x] Bugfix
[ ] New feature
[ ] Enhancement
[ ] Refactoring

:scroll: Description
The fix propagates correctly the tracing header (AWSTraceHeader) as SQS message system attribute, when available among Spring Message headers
:bulb: Motivation and Context
This PR is for fixing https://github.com/awspring/spring-cloud-aws/issues/1262
:green_heart: How did you test it?
Added two tests: on SqsTemplateTests and SqsHeaderMapperTests involving the methods that have been changed
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[ ] I updated reference documentation to reflect the change
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Looks good to me. @tomazfernandes what do you think?
Only worried .name() to toString() could be breaking change

Hi @MatejNedic,
that is actually the fix to the problem related to the issue https://github.com/awspring/spring-cloud-aws/issues/1262


Set default data type for notify to tts

As proposed by #1738, this PR sets the default data value of the notify service type to tts.
Closes #1738

Thanks!


upgrade eksctl-anywhere   question

eksctl 0.76.0
eksctl-anywhere v0.7.2
os:ubuntu
I tried upgrading eksctl-anywhere to v0.15.3 from v0.7.2  i understand that this is not possible and have to upgrade to next release ....
I what to get to latest with minimum no. of upgrades also have constraint of being in air-gaped environment.is it possible?
also i tried upgrading to v0.8.2 but can't download the ubuntu.ova accessed denied is there a archive where version can be download if i have to upgrade 8,9,10 ?

Hi @danielem37. We require users to upgrade incrementally so you can't skip straight to 0.15. With respect to Ubuntu, we stopped vending the images some time ago so you'll need to build and host them (see https://anywhere.eks.amazonaws.com/docs/reference/artifacts/#building-node-images).
I'm closing the issue but feel free to continue asking questions.

I know you stop vending images and from v0.11 start using image builder
I have built images  but I can not upgrade using them
So want you saying is all images from 8-10 are not available even in
archives?
On Thu, 11 May 2023 at 14:44 Chris Doherty @.***> wrote:

Hi @danielem37 https://github.com/danielem37. We require users to
upgrade incrementally so you can't skip straight to 0.15. With respect to
Ubuntu, we stopped vending the images some time ago so you'll need to build
and host them (see
https://anywhere.eks.amazonaws.com/docs/reference/artifacts/#building-node-images
).
I'm closing the issue but feel free to continue asking questions.
—
Reply to this email directly, view it on GitHub
https://github.com/aws/eks-anywhere/issues/5844#issuecomment-1543846002,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGTZ54AAT5CEO2PIJFWDBRDXFTGLDANCNFSM6AAAAAAX5WN4PY
.
You are receiving this because you were mentioned.Message ID:
@.***>


Bugfix/fix frontend application tests

NO NEED APPROVAL AND MERGE!!!!
It's just for testing purpose.
I don't know now how to run tests without pull request
EPMLABSBRN-XX
Description:

@koylubaevnt to run tests locally start application:
cd frontend
yarn remote:prod
visit http://localhost:4200/tests
or
cd frontned
yarn test
to run tests in headless mode

It's duplicate PR!
original: https://github.com/Brain-up/brn/pull/1996


WWW-Authenticate resource parameter fails challenge verification even with custom hostname + SSL

Is your feature request related to a problem? Please describe.
I'm exploring the use of the Lowkey Vault at work, where we have an abstraction over the Key Vault client. The Lowkey Vault is great ( thank you ❤ ) but it would be strongly preferable not to need the  disableChallengeResourceVerification parameter in Node.js.
I don't think it's possible to fix the challenge verificiation for normal use when running on localhost, but it could be possible to fix it when running in Docker with custom hostnames.
Currently, the WWW-Authenticate header returned by Lowkey uses the current request URI as the value of the resource parameter - e.g. with the default behaviour running on localhost:8443:
$ docker run -p 8443:8443 nagyesta/lowkey-vault:2.4.141

$ curl --silent -k -v https://localhost:8443/secrets/lorem 2>&1 | grep WWW
< WWW-Authenticate: Bearer resource="https://localhost:8443", authorization_uri="https://localhost:8443/secrets/lorem"

This would fail the challenge anyway, since the Guidance for applications using the Key Vault libraries says the "[...] host domain must match one of the known domain names [...]"
If we try it in Docker with a custom hostname:
$ docker network create --driver bridge lowkey-test
$ docker run --net=lowkey-test --hostname lowkey.vault.azure.net -p 8443:8443 nagyesta/lowkey-vault:2.4.141

$ docker run --net=lowkey-test --rm -it node:latest bash
> curl --silent -k -v https://lowkey.vault.azure.net:8443/secrets/lorem 2>&1 | grep WWW
< WWW-Authenticate: Bearer resource="https://lowkey.vault.azure.net:8443", authorization_uri="https://lowkey.vault.azure.net:8443/secrets/lorem"

We get the "full" hostname returned in the resource parameter. This doesn't match the challenge because the Key Vault client expects the requested URI to be a subdomain of the resource parameter - e.g. we'd have to request myvault.lowkey.vault.azure.net to pass the challenge, but we can't do that, because the resource parameter keeps matching our request URI.
I couldn't find this directly spelled out, it's kind of implied in the linked blog post where it says "[...] prepended with the “.” character to confirm a match [...]" and there's another hint in the Basis-Theory/azure-keyvault-emulator source code
Describe the solution you'd like
Support an additional LOWKEY_* argument (e.g. LOWKEY_AUTH_RESOURCE) to use in the WWW-Authenticate header resource parameter
Describe alternatives you've considered
It does work with disableChallengeResourceVerification: true, but it would reduce the need to add changes, conditionals, or risk by exposing that option to users, if we didn't need to use it in the first place.
Additional context
Rather than ask for a feature request without putting any effort in, I've made an attempt at making this work in a personal fork:
craig0990/lowkey-vault@ae7f1068fffc06a1257e5b4795b81869d05bb36e
I'm not really a Java dev 🥲 I've copied the approach used in the VaultImporterProperties.java class to add @Value usage in the constructor of the CommonAuthHeaderFilter where the header is constructed.
I didn't know how to make the @Value injection keep the current behaviour by default, since the current behaviour is dynamic to the received request hostname. I guess you could default to blank/null and add a conditional in the constructor, if that's an issue? But I'm assuming that if the user isn't running Lowkey with a custom hostname, they're probably going to run with disableChallengeResourceVerification and not particularly care what's in the resource parameter. Maybe that's a poor assumption.
I've attempted test cases, but again, I'm sure they could be improved.
I've also forked the Node.js example repository, to give an example of running the existing Node tests using the new LOWKEY_AUTH_RESOURCE argument:
https://github.com/craig0990/lowkey-vault-example-nodejs
I'll raise a PR after submitting this issue, if only for reference - I can understand if there's a different/better approach to be taken.
Edit: PR at #1150

Hi @craig0990 ,
first of all, thank you! I am not getting feature requests often and especially not with a PR :).
I like your solution and will use it. Added a single commit on top of it and pushed to my fork to allow the pipeline to run successfully (unfortunately there are some secrets which are needed for a green build). As a result the new PR will be #1151 and I will close #1150 without merging since it is no longer needed.
I hope this is not an issue for you!

The release completed, you can use it with v2.5.0.
Thank you again and best of luck!

That's absolutely awesome @nagyesta - that's the last missing piece to help us on our test journey, so thanks for building such a solid local emulator 🙏🏻

Thank you!


🐛 Add an annotation with BMH status when pausing it

What this PR does / why we need it:
In order to properly pivot the BMH, we need to set two annotations
on the BMH, one to pause the reconciliation, the other with the
marshalled status. This commit adds the second annotation as part
of the pausing workflow.

/test-v1a4-integration

/cc @kashifest
/cc @fmuyassarov
/cc @furkatgofurov7
/hold for discussion on BMO

/test-v1a4-integration

This approach looks good. If there is a conflict writing the host here, it will retry and get the new status. If the BMO is reconciling the host at the same time it will get a conflict, try again, and see the pause annotation.
/approve

/hold cancel

/lgtm


Add brunch support (JS Task Runner)

http://blog.toggl.com/2014/03/grunt-vs-gulp-vs-brunch/

@reubano pull request is welcome ;)

Unless more support is expressed or a feature-branch open on this I think it should be closed.


Modify test to cover a previous C++/CLI issue

C++/CLI issue was fixed in https://github.com/cross-language-cpp/djinni-generator/pull/78.

Made obsolete by #86.


Player's heart_core_mat.tres emission_energy_multiplier changes value every time the main scene is saved

Every time the main scene is saved, this value in the heart_core_mat.tres material changes:
diff --git a/Player/model/materials/heart_core_mat.tres b/Player/model/materials/heart_core_mat.tres
index ec92b25..7eb6d28 100644
--- a/Player/model/materials/heart_core_mat.tres
+++ b/Player/model/materials/heart_core_mat.tres
@@ -4,4 +4,4 @@
 albedo_color = Color(0, 0, 0, 1)
 emission_enabled = true
 emission = Color(0, 1, 0.392157, 1)
-emission_energy_multiplier = 0.669953
+emission_energy_multiplier = 1.2208

diff --git a/Player/model/materials/heart_core_mat.tres b/Player/model/materials/heart_core_mat.tres
index 7eb6d28..9d3e649 100644
--- a/Player/model/materials/heart_core_mat.tres
+++ b/Player/model/materials/heart_core_mat.tres
@@ -4,4 +4,4 @@
 albedo_color = Color(0, 0, 0, 1)
 emission_enabled = true
 emission = Color(0, 1, 0.392157, 1)
-emission_energy_multiplier = 1.2208
+emission_energy_multiplier = 2.16216

This messes up the git history but also actually changes the material. Might be a Godot bug, but I'm reporting it here first to debug.
Seen with Godot 4.0.4, and 4.1.1.

This seems to be due to the autoplaying Player/model/custom_animations/default_heartbeat.tres which animates this value. Godot will save whichever value is currently shown by the playing animation.
The default setup should likely be to play the RESET animation so nothing changes, and enable idle animations at runtime.


Mac M1 Failing Bazel Build When Trying to Build cpp_grpc_library

Describe the bug
Bazel build fails when trying to build cpp_grpc_library:
$ bazel build --copt="-Wno-error=deprecated-copy" //networking:pod_cc_proto
INFO: Analyzed target //networking:pod_cc_proto (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /private/var/tmp/_bazel_vulcan/8c1801317d32dd0e271100c0f6118973/external/upb/upbc/BUILD:44:10: Compiling upbc/message_layout.cc [for host] failed: (Aborted): wrapped_clang failed: error executing command external/local_config_cc/wrapped_clang '-D_FORTIFY_SOURCE=1' -fstack-protector -fcolor-diagnostics -Wall -Wthread-safety -Wself-assign -fno-omit-frame-pointer -g0 -O2 -DNDEBUG '-DNS_BLOCK_ASSERTIONS=1' ... (remaining 55 argument(s) skipped)

Use --sandbox_debug to see verbose messages from the sandbox
In file included from external/upb/upbc/message_layout.cc:26:
In file included from external/upb/upbc/message_layout.h:32:
In file included from external/com_google_absl/absl/container/flat_hash_map.h:40:
In file included from external/com_google_absl/absl/container/internal/hash_function_defaults.h:56:
In file included from external/com_google_absl/absl/strings/cord.h:78:
external/com_google_absl/absl/functional/function_ref.h:124:16: error: definition of implicit copy constructor for 'FunctionRef<void (absl::string_view)>' is deprecated because it has a user-declared copy assignment operator [-Werror,-Wdeprecated-copy]
  FunctionRef& operator=(const FunctionRef& rhs) = delete;
               ^
external/com_google_absl/absl/strings/cord.h:1325:33: note: in implicit copy constructor for 'absl::FunctionRef<void (absl::string_view)>' first required here
    return ForEachChunkAux(rep, callback);
                                ^
1 error generated.
Error in child process '/usr/bin/xcrun'. 1
Target //networking:pod_cc_proto failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1.426s, Critical Path: 1.27s
INFO: 13 processes: 9 internal, 4 darwin-sandbox.
FAILED: Build did NOT complete successfully

Steps to reproduce the bug
You can find all the code for the project here.
The BUILD target in question that causes the issue is here.
What version of Abseil are you using?
Not sure -- seems like its being imported from the grpc rules
What operating system and version are you using
Mac OS Monterrey
Version 12.2.1
Apple M1
What compiler and version are you using?
Apple clang version 13.1.6 (clang-13<IP_ADDRESS>)
Target: arm64-apple-darwin21.3.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

What build system are you using?
bazel 4.2.1-homebrew

Additional context
Most relevant issue I could find was #948 -- but adding --copt="-Wno-error=deprecated-copy" to bazel build did not seem to change anything. Would greatly appreciate any set of eyes on this issue!

What version of Abseil are you using?
Not sure -- seems like its being imported from the grpc rules

Can you please try to reproduce this with the latest version?

What version of Abseil are you using?
Not sure -- seems like its being imported from the grpc rules

Can you please try to reproduce this with the latest version?

I am using the (latest gRPC version)[https://rules-proto-grpc.com/en/latest/index.html], so I can only presume that I am using the latest version? I am not sure how to verify that -- I tried graphing the bazel dependency tree as well as searching. absl in the gRPC repository to find a version, but no luck. I am not sure how I would even change it if I was able to find it.

Same issue here. For me it started after I update to Monterey 12.3 and had to re-install Xcode

$> xcodebuild -version
Xcode 13.3
Build version 13E113

It seems that the errors are for a different version since the lines in the error messages do not match the code in the repo. For example, the line cord.h:1325 in the error message is line 1499. Similar for function_ref.h:124. The code there is the same but this indicates that we are using an older version.

Thanks @tzovas! That worked! For anyone else, just remember to delete the failed cached build. Closing this issue since it is fixed now!

I had the same issue with an Intel Mac and reverting back to Xcode 13.2.1 also solved the issue for me. However I would consider this to be more of a temporary fix as we cannot stay on this specific version of Xcode forever. Can we reopen the issue?

I had the same issue with an Intel Mac and reverting back to Xcode 13.2.1 also solved the issue for me. However I would consider this to be more of a temporary fix as we cannot stay on this specific version of Xcode forever. Can we reopen the issue?

That is a fair point. Reopening to see if we can get some more eyes on this

This should be fixed, but downstream projects haven't updated to the lastest version. We can't do anything about that.
I also have no idea why --copt="-Wno-error=deprecated-copy" is not suppressing the error.

I can confirm for macOS Monterey Intel. The same error as below happens.  PWD=/proc/self/cwd
external/local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE -fstack-protector -Wall -Wthread-safety -Wself-assign -Wunused-but-set-parameter -Wno-free-nonheap-object -fcolor-diagnostics -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/host/bin/external/upb/upbc/objs/protoc-gen-upb/protoc-gen-upb.d '-frandom-seed=bazel-out/host/bin/external/upb/upbc/objs/protoc-gen-upb/protoc-gen-upb.o' -iquote external/upb -iquote bazel-out/host/bin/external/upb -iquote external/com_google_protobuf -iquote bazel-out/host/bin/external/com_google_protobuf -iquote external/zlib -iquote bazel-out/host/bin/external/zlib -iquote external/com_google_absl -iquote bazel-out/host/bin/external/com_google_absl -iquote external/bazel_tools -iquote bazel-out/host/bin/external/bazel_tools -isystem external/com_google_protobuf/src -isystem bazel-out/host/bin/external/com_google_protobuf/src -isystem external/zlib/zlib/include -isystem bazel-out/host/bin/external/zlib/zlib/include -g0 -g0 -Wextra -Werror -Wno-long-long -no-canonical-prefixes -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP__="redacted"' '-D__TIME__="redacted"' -c external/upb/upbc/protoc-gen-upb.cc -o bazel-out/host/bin/external/upb/upbc/_objs/protoc-gen-upb/protoc-gen-upb.o)
Execution platform: @local_config_platform//:host
Use --sandbox_debug to see verbose messages from the sandbox
In file included from external/upb/upbc/protoc-gen-upb.cc:28:
In file included from external/com_google_absl/absl/container/flat_hash_map.h:40:
In file included from external/com_google_absl/absl/container/internal/hash_function_defaults.h:56:
In file included from external/com_google_absl/absl/strings/cord.h:78:
external/com_google_absl/absl/functional/function_ref.h:124:16: error: definition of implicit copy constructor for 'FunctionRef<void (absl::string_view)>' is deprecated because it has a user-declared copy assignment operator [-Werror,-Wdeprecated-copy]
FunctionRef& operator=(const FunctionRef& rhs) = delete;
^
external/com_google_absl/absl/strings/cord.h:1325:33: note: in implicit copy constructor for 'absl::FunctionRef<void (absl::string_view)>' first required here
return ForEachChunkAux(rep, callback);
^
1 error generated.
(17:09:31) INFO: Elapsed time: 198.929s, Critical Path: 29.76s
(17:09:31) INFO: 2195 processes: 767 remote cache hit, 670 internal, 741 darwin-sandbox, 17 worker.
(17:09:31) FAILED: Build did NOT complete successfully

Same issue here. On an intel x86-64 mac, with Mac OS 12.4


DateHistogramValuesSourceBuilder - offset support

Is your feature request related to a problem? Please describe.
Can't specify "offset" parameter for date_histogram with OpenSearch java client.
Current offset parameter is used differently (rounding).
Describe the solution you'd like
A way to specify offset.
Describe alternatives you've considered
Replace current offset function usage or create new. - "dateHistogramOffset()"
Additional context
Add any other context or screenshots about the feature request here.
In request json body, no way to set "offset" with java client.
{
    "date_histogram":
    {
        "field": "timestamp",
        "calendar_interval": "1w",
        "offset": "-1d",
    }
}

@muzehyun This looks to be java client related functionality gap. Can you create the issue in this repo please ?

I'm still using "rest-high-level" client here in this repo. No major update on rest-high-level-client? Should I move to new Java client?

@muzehyun Yes you should. Moving this issue into opensearch-java.


NavBar

The navbar should take the entire width of the screen

.

This issue is not properly explained.

Hey @roshanchatei, thanks for logging these issues! I have a couple of links here which have some tips for creating a really good github issue - please do take a read through!

https://medium.com/nyc-planning-digital/writing-a-proper-github-issue-97427d62a20f
https://hackernoon.com/45-github-issues-dos-and-donts-dfec9ab4b612

In particular, in this case: How does one reproduce the bug you've reported? It would be great to know:

what browser you're using, and if it occurs in other browsers.
what you'd expect to happen.
what actually happens.
How I (as an issue reader) can reproduce the bug if I want to try to fix it or revew the bug myself.


Need to block access to kernel files systems in /proc and /sys

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

LGTM

Same questions as from https://github.com/projectatomic/libpod/pull/61/files, if that's all hip, then LGTM.

@rh-atomic-bot r=TomSweeneyRedHat

Yes if they are missing it is ok.  We should ask about the sysrq one on CRI-O or in docker, if it is also readonly there?


Feat: Cloud Gateways Documentation

Cloud Gateways:
https://konghq.atlassian.net/browse/DOCU-3686
Preview
Ready for review
Overview Page
Networking and Peering information
Supported regions
Transit Gateways
How to upgrade data planes
Custom Domains
Coming in the next day or so
How to use CGW
Diagrams
API Spec

[x] Overview Page + change log
[x] Terminology updates
[x] Networking and Peering Information
[x] New Supported AWS regions
[x] Transit gateways
[x] Updates to getting started docs
[x] How to upgrade data plane nodes
[ ] CGW Operations
[x] Custom DNS
[ ] Diagrams
[ ] API Spec

Preview Link: https://deploy-preview-7097--kongdocs.netlify.app/konnect/

[ ] The image in the Overview page is oversized.
[ ] In the regions we should also add the geographical name
[ ] In transit gateway we should add an example and perhaps a short 60 seconds video that shows how to do it.
[ ] In how to upgrade we should have an image that shows where to click.
[ ] In networking and peering we need architectural diagrams that explain the setup like:

Thanks team for pulling this together! I know it came in hot and without nearly enough detail 😅
Feel free to merge in the morning before 9am ET / 6am PT.


addon-a11y not working on latest next

Describe the bug
@storybook/addon-a11y not reporting a11y test results on next branch . It shows 0 passes and 0 violations on any story regardless of decorator being set or not.
To Reproduce

Checkout next branch
Start the official-storybook kitchen sink app or install/register add-on to any other app.
Open any of the a11y stories with decorator set.
Go to Accessibility panel.
See 0 results on both passes/violations.

Expected behavior
Should display amount of test passes or violations respectively in each tab.
Screenshots

Code
It's related to the runA11yCheck function on the addon's declaration and the DOM being selected to run the aXe tests on:
const runA11yCheck = () => {
  const channel = addons.getChannel();
  const infoWrapper = document.getElementById('story-root').children;
  const wrapper = document.getElementById('root');

  axe.reset();
  axe.configure(axeOptions);
  axe
    .run(infoWrapper || wrapper)
    .then(results => channel.emit(CHECK_EVENT_ID, results), logger.error);
};

System:

Browser: any
Framework: all
Addons: a11y
Version: 4.0.9

Additional context
Tried this on some of the other kitchen sink apps with same result.

Are all your other storybook deps up to date?

Yes this is happening on a fresh clone of latest, 4.1.0-alpha.9.

Hi, I met the same issue. This is a reproduction repo: https://github.com/Bobgy/reproduction-storybook-a11y-bug
It's simply made from a new create-react-app and installing storybook@next

The addon-a11y plugin also appears to be broken in the 4.1.1 release now - displaying 0 passes and 0 violations on all stories.

This is also an issue on the official Storybook example page
I'm guessing this is related to #4704 - Adding a <div id="root-story"> around all my stories, causes aXe to throw a selector warning, but it does run all the tests correctly afterwards. It still scrolls to the bottom of the page.
I'm not sure why the root-story is only added to the Info addon? Scrolling to the bottom of a story is a general issue, that's not just related to pages with the Info addon. The readme addon has the same issue, and in my project i have multiple stories that either render entire pages or components that just take up more than the screen.
index.js:19 Error: Expect axe._selectorData to be set up
    at generateSelector (axe.js:3953)
    at Object.createUniqueSelector [as getSelector] (axe.js:4009)
    at DqElement.get selector [as selector] (axe.js:3400)
    at axe.js:2393
    at Array.map (<anonymous>)
    at axe.js:2386
    at Array.map (<anonymous>)
    at axe.js:2383
    at Array.forEach (<anonymous>)
    at Object.push../node_modules/axe-core/axe.js.helpers.processAggregate (axe.js:2375)

Having the same issue using Angular


unit testing for grouping unification

          The practical effect of this unification is only in `drawio`  - the fixes originated in Haim's request. Its more natural to test it there. I can only test, or try to test, cumbersome side effects of the unification, and not sure the test can be decoupled from the actual impl (and as such problematic).

Perhaps we can open an issue for this and see what it the best way to test it.
Originally posted by @ShiriMoran in https://github.com/np-guard/vpc-network-config-analyzer/pull/423#discussion_r1506260364
The unification process is so that in the drawio presentation each semantic group is presented only once; this includes groups that are both src in a line and dst in another line in the single vpc context or e.g. the same external IP groups in the multi VPC context.
Not sure what is the best way to smoothly test this in unit test. Better avoid messy pointer comparison.

I think it may be sufficient to add mechanism to identify cache hits, and then have two examples in unit tests that demonstrate the caching and verify those cache hits. The examples are required for both flows - one for grouping  for multi-vpc level, and one for grouping after self-loop grouping runs, within single vpc context.


LoggingFactory: Make logger() used cached loggers by default

Actually, it probably would make even more sense to turn the extention function into an extension property instead. Something like
val Any.logger: KotlinLogger
    inline get() = cachedLoggerOf(this::class.java)

What do you think @rocketraman?

I kind of like that idea. I'm not super familiar with API compatibility with Kotlin (besides looking up how default argument values are translated to Java; turns out that adding more named parameters is indeed an ABI change as you might expect despite the API staying source-compatible).

Ok, now that I've loaded the code back up again (and after using Kotlin myself a lot more lately), I see where you're going with this. If we leave the function in place as always constructing a KotlinLogger, then a property can use a cached logger which seems intuitive. For example:
inline fun <reified T> T.logger(): KotlinLogger = loggerOf(T::class.java)

inline val <reified T> T.logger: KotlinLogger
  get() = cachedLoggerOf(T::class.java)

The docs for the T::logger function explicitly states that it's for logger instantiation. Adding a property for the cached logger seems like an interesting API alternative to extending the Logging mixin. Kotlin is all about flexibility here, so let's go for it!

I've added the extension property in #29.


Project Setup

Hello
I am facing the below issue while setup the flex-project template, if anyone have solution please help me on the same.

Error Msg :- E:Twilio-flexplugin-flex-ts-template-v2 directory is not a flex plugin directory. You must either run a plugin inside a directory or use the --name flag

It looks like you might have missed the npm install step of the local setup instructions. Try running that step and then npm start should work!

Closing due to inactivity, feel free to re-open if you still need assistance!


Ability to add pre_remove_hook in the derive macro

I'd like to add a hook that checks the expiry of the rest of the records (I have a chrono field that describes expiry) and deletes them. Essentially it's cleanup during every delete - since I'm rarely deleting stuff it makes sense

Hum, that would make sense, what do you have in mind for the derive syntax ? Providing the name of a free function that would take an instance of the entity as an argument?

oh damn I forgot about infinite recursion!
I'd expect something in the sense of pre_remove_hook = "my_awesome_remove_hook", like serde does
btw why do you use https://docs.rs/reindeer/latest/reindeer/trait.Entity.html#method.use_pre_remove_hook and not inline the pre_remove_hook { Ok(()) }?

Hmm, yes you're probably right. It's been a while, the use_pre_remove_hook might indeed not be useful at all. The pre-remove hook's default implementation is already what you suggested, btw.
For the macro itself, I'm moving houses at the moment and have a ton of way-overdue work so I hope you're not in a hurry; in the meantime you can implement the Entity trait the hard way, it should work!

I'm not in a hurry at all - my project is "finished" in terms of features, I'm just discussing what would be nice. I like it very much when people interact with my projects (issues/ideas/etc.) so it's some kind of a weird "thank you" :P
take your time and I wish you the best


Use Lodash for utility functions

Lodash is a widely used, highly tested and performance optimized library. This PR removes the custom utility functions and uses their Lodash equivalent.

:shipit:


Fix parsing body array

Allow for parsing of body returned as array
The content schemas allow for body content to return as a string or
as an array for multiple content types [1] but we had only assumed the
case for strings. This caused issues when we tried to call string
methods on an array.
This was sending a lot of error messages in our logs.
[1]
https://github.com/alphagov/govuk-content-schemas/blob/master/formats/shared/definitions/publishing_api_base.jsonnet#L125
and
https://github.com/alphagov/govuk-content-schemas/blob/master/formats/shared/definitions/publishing_api_base.jsonnet#L129

 BUG: fix `undefined method `delete!' for Array`

I agree with @pmanrubia. Have addressed @MatMoore's comment meanwhile.

Thank you @chao-xian
Superseded by https://github.com/alphagov/content-performance-manager/pull/756, which is a continuation of this work.
cc://  @MatMoore


Reset password fails  - "invalid request: both auth code and code verifier should be non-empty"

I try to explore the "reset the password" after deployment, unfortunately it doesn't work.
Detail: I did get the reset password email, then clicked the link, yet the update_password page seemed crashing.
Took a look at the log, the error is in the /auth/reset_password
⨯ eG [AuthApiError]: invalid request: both auth code and code verifier should be non-empty
    at e5 (/var/task/.next/server/chunks/286.js:1:69374)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ae (/var/task/.next/server/chunks/286.js:1:70373)
    at async e7 (/var/task/.next/server/chunks/286.js:1:70029)
    at async ag._exchangeCodeForSession (/var/task/.next/server/chunks/286.js:1:84836)
    at async /var/task/.next/server/chunks/286.js:1:90526 {
  __isAuthError: true,
  status: 400,
  code: 'validation_failed'
}

Any suggestion? Thanks

I might figure out the issue.  In the SignIn component, it tries to get the user with supabase.auth.getUser();. But since the user forgot its password and not sign in, this is always null, so always redicts to '/signin'.
  const {
    data: { user }
  } = await supabase.auth.getUser();

  if (user && viewProp !== 'update_password') {
    return redirect('/');
  } else if (!user && viewProp === 'update_password') {
    return redirect('/signin');
  }

I figured it out. During the vercel deployment there are multiple URLs.  I used one to click the "forgot password", yet the reset email site url points to another one, so resulting the mis-match..


Bugfix for delegate VirtualService with analysis enabled

Bugfix for delegate VirtualService with analysis enabled

@Nerja I think it's best to remove skipAnalysis: true from e2e-istio-tests-delegate.sh I missed this when reviewing #715 sorry

Sounds good @stefanprodan, removed the new e2e test and adapted the old one.


Contract unit tests

contracts: Emit missing PoolDeployed event
contracts: Fix and configure solhint
contracts: Add YieldGate testing setup
contracts: Fix unstake: supporter amount must be non-zero
contracts: Add stake and unstake test
ci: Add contract tests to CI

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@af3f090). Click here to learn what that means.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             develop       #52   +/-   ##
===========================================
  Coverage           ?   100.00%
===========================================
  Files              ?         1
  Lines              ?        62
  Branches           ?         7
===========================================
  Hits               ?        62
  Misses             ?         0
  Partials           ?         0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Removed Coveralls again. We can try later, recorded here https://github.com/yieldgate/yieldgate/issues/55


[folding] CTRL+A doesn't select last folded line in python

VSCode Version: Code 1.19.2 (490ef761b76b3f3b3832eff7a588aac891e5fe80, 2018-01-10T15:55:03.538Z)
OS Version: Windows_NT x64 10.0.16299
Extensions:

Extension
Author (truncated)
Version

jupyter
don
1.1.4

file-icons
fil
1.0.7

code-runner
for
0.8.7

python
ms-
0.9.1

vscode-todo-highlight
way
0.5.11

(1 theme extensions excluded)

Steps to Reproduce:

Reproduces without extensions: Yes/No

I also hit this problem.

IMo the problem is with convertModelRangeToViewRange:
https://github.com/microsoft/vscode/blob/4ec6717139357f3e96c51ddd8d5ef601af31f737/src/vs/editor/common/viewModel/splitLinesCollection.ts#L765.
When converting a range both start and end positions are converted to the last visible line.


Does face need aligned in predict.py?

I found that in predict.py only the croped face are put into net  to predict the attributes,  the face is not  aligned, is it right?

yes, you're right. because no align in training.  you man consider using align during training.


Further fixing the IAM User auditor to work with the new IAM User format.

Further fixing the IAM User auditor to work with the new IAM User format.

Coverage remained the same at 51.941% when pulling<PHONE_NUMBER>cfed225475275b1486de007cb4b218 on iamuser_auditor_fixes into 31de86f9cf1a82a77eb98f6c54fa67a1f53cdf5b on develop.


Map Jenkins Authentication Otel Log attributes to Elastic ECS

What feature do you want to see added?
Map Jenkins Authentication Otel Log attributes to Elastic ECS when ingesting Jenkins Otel logs in Elastic to better integrate with Elastic SIEM.

Jenkins OTel Log Attribute
Standard OTel Semantic Convention
Elastic ECS Field

enduser.id=hudson.model.User.getId()
yes
TBD user.id ("Unique identifier of the user") or user.name ("Short name or login of the user")

net.peer.ip=request.getRemoteAddr()
yes

event.action='user_login'
no
event.action

event.category='authentication'
no
event.category

event.outcome='success' or 'failure'
no
event.outcome

❓ Pending questions:

Should Elastic map Jenkins Otel Logs attributes if they are not part of the official Otel Semantic Conventions? Should Elastic map any Otel attribute that match an equivalent official ECS field? For example should Elastic automatically map the an OpenTelemetry attribute event.action to Elastic event.action or should it map it to labels.event.action? Currently it's the latter.

Elastic SIEM detections:

Elastic Security / Detect Unusual Login Activity
Auditbeat System Login Dataset

Example Successful Authentication Log Message
{
  "_index": ".ds-logs-apm.app-default-2022.03.07-000002",
  "_id": "ajqBq38B8sassxURpvo6",
  "_version": 1,
  "_score": 1,
  "_source": {
    "container": {
      "id": "559d4b8ac80f638fbc37f1804394a24d1a5f3fadd567054995b586a226055253"
    },
    "agent": {
      "name": "opentelemetry/java",
      "version": "1.12.0"
    },
    "data_stream.namespace": "default",
    "message": "Successful login of user 'admin' from <IP_ADDRESS>",
    "processor": {
      "name": "log",
      "event": "log"
    },
    "data_stream.type": "logs",
    "labels": {
      "process_runtime_description": "Eclipse Adoptium OpenJDK 64-Bit Server VM 11.0.14+9",
      "event_action": "user_login",
      "jenkins_url": "https://jenkins.<IP_ADDRESS>.ip.es.io/",
      "enduser_id": "admin",
      "event_outcome": "success",
      "jenkins_version": "2.319.3",
      "net_peer_ip": "<IP_ADDRESS>",
      "service_namespace": "jenkins",
      "jenkins_opentelemetry_plugin_version": "2.3.0-rc1",
      "event_category": "authentication"
    },
    "observer": {
      "hostname": "8bacbea9c748",
      "id": "8ed90c13-d060-42db-a432-ad699ad6bb20",
      "ephemeral_id": "cfcf472e-eaf4-4670-9406-e904441836c1",
      "type": "apm-server",
      "version": "8.1.0",
      "version_major": 8
    },
    "@timestamp": "2022-03-21T08:04:33.856Z",
    "ecs": {
      "version": "1.12.0"
    },
    "service": {
      "node": {
        "name": "559d4b8ac80f638fbc37f1804394a24d1a5f3fadd567054995b586a226055253"
      },
      "name": "jenkins",
      "runtime": {
        "name": "OpenJDK Runtime Environment",
        "version": "11.0.14+9"
      },
      "language": {
        "name": "java"
      },
      "version": "2.319.3"
    },
    "data_stream.dataset": "apm.app",
    "host": {
      "hostname": "jenkins-0",
      "os": {
        "type": "linux",
        "platform": "linux",
        "full": "Linux 5.4.170+"
      },
      "name": "jenkins-0",
      "architecture": "amd64"
    },
    "event": {
      "severity": 9,
      "agent_id_status": "missing",
      "ingested": "2022-03-21T08:04:35Z"
    }
  },
  "fields": {
    "labels.jenkins_version": [
      "2.319.3"
    ],
    "labels.net_peer_ip": [
      "<IP_ADDRESS>"
    ],
    "labels.process_runtime_description": [
      "Eclipse Adoptium OpenJDK 64-Bit Server VM 11.0.14+9"
    ],
    "host.os.full": [
      "Linux 5.4.170+"
    ],
    "labels.enduser_id": [
      "admin"
    ],
    "labels.event_action": [
      "user_login"
    ],
    "labels.jenkins_url": [
      "https://jenkins.<IP_ADDRESS>.ip.es.io/"
    ],
    "service.node.name": [
      "559d4b8ac80f638fbc37f1804394a24d1a5f3fadd567054995b586a226055253"
    ],
    "host.hostname": [
      "jenkins-0"
    ],
    "service.language.name": [
      "java"
    ],
    "container.id": [
      "559d4b8ac80f638fbc37f1804394a24d1a5f3fadd567054995b586a226055253"
    ],
    "processor.event": [
      "log"
    ],
    "agent.name": [
      "opentelemetry/java"
    ],
    "host.name": [
      "jenkins-0"
    ],
    "event.agent_id_status": [
      "missing"
    ],
    "labels.event_outcome": [
      "success"
    ],
    "event.severity": [
      9
    ],
    "service.name": [
      "jenkins"
    ],
    "host.os.type": [
      "linux"
    ],
    "data_stream.namespace": [
      "default"
    ],
    "processor.name": [
      "log"
    ],
    "service.runtime.name": [
      "OpenJDK Runtime Environment"
    ],
    "service.runtime.version": [
      "11.0.14+9"
    ],
    "observer.version_major": [
      8
    ],
    "message": [
      "Successful login of user 'admin' from <IP_ADDRESS>"
    ],
    "observer.hostname": [
      "8bacbea9c748"
    ],
    "data_stream.type": [
      "logs"
    ],
    "labels.jenkins_opentelemetry_plugin_version": [
      "2.3.0-rc1"
    ],
    "host.architecture": [
      "amd64"
    ],
    "event.ingested": [
      "2022-03-21T08:04:35.000Z"
    ],
    "observer.id": [
      "8ed90c13-d060-42db-a432-ad699ad6bb20"
    ],
    "@timestamp": [
      "2022-03-21T08:04:33.856Z"
    ],
    "service.version": [
      "2.319.3"
    ],
    "observer.ephemeral_id": [
      "cfcf472e-eaf4-4670-9406-e904441836c1"
    ],
    "observer.version": [
      "8.1.0"
    ],
    "host.os.platform": [
      "linux"
    ],
    "observer.type": [
      "apm-server"
    ],
    "ecs.version": [
      "1.12.0"
    ],
    "data_stream.dataset": [
      "apm.app"
    ],
    "agent.version": [
      "1.12.0"
    ],
    "labels.event_category": [
      "authentication"
    ],
    "labels.service_namespace": [
      "jenkins"
    ]
  }
}

Upstream changes
No response

Hi @cyrille-leclerc, please let me offer a couple of suggestions:

Should Elastic map Jenkins Otel Logs attributes if they are not part of the official Otel Semantic Conventions? Should Elastic map any Otel attribute that match an equivalent official ECS field?

If, as the initial comment suggests, the goal is to "Map Jenkins Authentication Otel Log attributes to Elastic ECS when ingesting Jenkins Otel logs in Elastic to better integrate with Elastic SIEM.", then yes, an optimal approach would be to attempt to map all fields from the Jenkins Otel Logs to ECS, not limiting mapping to just those fields for which Standard OTel Semantic Convention exists.

For example should Elastic automatically map the an OpenTelemetry attribute event.action to Elastic event.action or should it map it to labels.event.action? Currently it's the latter.

When using ECS, optimal analyst experiences (single click filtering, aggregations, single-click-pivoting) become available when the ECS fields are present in their specified hierarchy within the ECS namespace.  Which means that event.* fields such as event.category, event.outcome, and event.action should be present at the root of the event document's namespace, and NOT nested under labels.*


example basic-compute-shader  fails on Apple M1 Silicon

System Config

Version of vulkano: 0.26
OS: macOS 11.6
GPU (the selected PhysicalDevice): Apple M1 (type: IntegratedGpu)
GPU Driver: Vulkan version  1.2.189 (based on MoltenVK)
Minimal complete main.rs file that demonstrates the issue: the example is taken from the example basic-compute-shader taken unchanged from the github repository

Issue
I am able to build everything, but the test fails on a MacBook Pro (13-inch, M1, 2020) with the following messages:
./target/debug/basic-compute-shader

Using device: Apple M1 (type: IntegratedGpu)
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ExtensionRestrictionNotMet(ExtensionRestrictionError { extension: "khr_portability_subset", restriction: RequiresInstanceExtension("khr_get_physical_device_properties2") })', examples/src/bin/basic-compute-shader.rs:70:6
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

@phelluy I merged a Pull Request from @Rua with the fix, but I wan't able to test it, I don't have Mac. Can you test it please and let us know if it work? And please reopen the Issue if the bug persisted on the latest master.

Actually, I think this issue may have been closed in error (my mistake). It is true that the PR should fix the problem that khr_get_physical_device_properties2 is required even on Vulkan 1.1 and above. However, if you are using a Vulkan 1.0 instance, then this extension will be required and the examples will still fail. So the examples need to be adjusted so that they enable this extension on Vulkan 1.0 if it's available.

Now the basic-compute-shader compiles and run in debug. But in release I cannot compile:
cargo build --release
Compiling examples v0.1.0 (/Users/helluy/vulkano/examples)
error[E0428]: the name Data is defined multiple times
--> examples/src/bin/shader-types-sharing.rs:83:9
|
83 |         vulkano_shaders::shader! {
|         ^^^^^^^^^^^^^^^^^^^^^^^^
|         |
|         Data redefined here
|         previous definition of the type Data here

I can reproduce that issue for the shader-types-sharing example on Linux, so it's not related to Mac or your original issue. I'll open a new one.

@phelluy, @Rua I believe this issue is now fixed(in #1765). Can you confirm, please?

I confirm that now everything compile also in release mode. And the above tests and examples pass.
thanks !


Create de.json

for german keyboard-hits
Please don't send pull-requests for translation. Use the Crowdin project instead.

Hi Mathew,
thanks a lot for your great tool. This is my first pull request... I hope I did everything right. I tested the json file extensively with my German keyboard.
Best Regards
Olli

Looks good to me! Thank you for your contribution.
I'm happy to let you know that it's the first community contribution towards keymaps.
Merging 👍


Question only?

Hey I was trying to understand how the webpack auto reload is working.
I know your using a webpack-dev-server, but what part of your code is forcing the reload to happen when you edit a component?
Thanks in advance. Any resources is much appreciated.

@brianbier The parsed jsx is served using WebPackDevServer here. This means that the server is able to both have access to your filesystem (listen for file changes), and refresh the browser.
If you want to read more about that "refresh the browser" part above, take a look at the WebPack Docs Explanation

thanks for the answer @dawsonbotsford, I recommend reading Webpack Docs and Dan's blog post on approaches to hot reloading in React.


[ffigen] Fix global_test flake (finally!)

global_test and global_native_test are exactly the same, except that one uses ordinary bindings, and the other uses @Native style bindings. When both tests are run in the same suite, occasionally they will both fail. It's always the case that both fail or both pass.
The flake appears to be in the build, not the test. If I change the workflow to build once and run the tests 10 times (and count the failures instead of stopping on failure), then it's always the case that there are either 0 or 10 failures: https://github.com/dart-lang/native/actions/runs/11471378290/job/31980751070?pr=1674
I hit a bit of a wall at this point, because I'm not sure how to get the bad build artifacts from github. So I've just changed these two tests to share the same native code. They still have their own ffigen bindings, but the underlying so file only has one copy of the global variables. Just have to make sure to reset the test state after each test, so they don't interfere with each other.
This seems to have fixed the flake, because there's no longer a conflict between the tests native artifacts. To verify the fix I changed the workflow to run the build/test 10 times, and there were no flakes: https://github.com/dart-lang/native/actions/runs/12386195112/job/34573726773
Fixes https://github.com/dart-lang/native/issues/1435

coverage: 87.958%. remained the same
when pulling fdc7c0a37223a974f9effa5b1e473463579aae47 on more_global_flake
into f2a0e28dca61bb37fac6b352db9ade98f45deb6b on main.

Of course, as soon as I put this PR out for review, it starts flaking again 😩


if cutoffs=[], convert_transfo_xl_checkpoint_to_pytorch.py has a bug

🐛 Bug

Model I am using (Bert, XLNet....): transformer_xl
Language I am using the model on (English, Chinese....): I train xl model base on own dataset

Environment

OS: centos 7.3
Python version: python3.6
PyTorch version: torch1.1
PyTorch Transformers version (or branch): 1.0.0
Using GPU: yes
Distributed of parallel setup ? no
Any other relevant information: no

detail context

AttributeError: 'ProjectedAdaptiveLogSoftmax' object has no attribute  'cluster_weight'
I see 'ProjectedAdaptiveLogSoftmax' code, if len(cutoffs) - 1 > 0,  will have attribute  'cluster_weight'

Hi!
Yes, you should indeed specify cutoffs in your TransfoXLConfig or the adaptive softmax won't be able to create its clusters. We should probably put a more explicit error.

Hello, @LysandreJik
The checkpoint of https://github.com/kimiyoung/transformer-xl doesn't have cutoff_N when adaptive softmax is not used. Does PyTorch-Transformers support TransfoXLConfig.adaptive = False? If supported, should it read checkpoint without explicit error? The content of checkpoint is like this without adaptive softmax.
transformer/adaptive_embed/lookup_table (DT_FLOAT) [32768,512]
transformer/adaptive_embed/lookup_table/Adam (DT_FLOAT) [32768,512]
transformer/adaptive_embed/lookup_table/Adam_1 (DT_FLOAT) [32768,512]
transformer/adaptive_softmax/bias (DT_FLOAT) [32768]
transformer/adaptive_softmax/bias/Adam (DT_FLOAT) [32768]
transformer/adaptive_softmax/bias/Adam_1 (DT_FLOAT) [32768]
transformer/layer_0/ff/LayerNorm/beta (DT_FLOAT) [512]


Hide RxJava from ClassLoader for StorIOContentResolver

Closes #144
@nikitin-da PTAL

well done! Can you update, please?

Updated!

:+1:


If the last room throws an error, don't ask about proceeding onto next room

If the last room in the list has an error when updating, the user is asked "Do you want to continue to the next Room? [y/n]:" when there is no next room to proceed and a "yes" response isn't followed up by any further action.

It would require an overhaul to the error handling mechanism as the code at the continue point has no concept of other rooms to be done.


Mast: Watch techymau.games

Mast requests the watch of the watch_keyword techymau\.games. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

techymau\.games has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Automated cherry pick of #5021: fix: 避免因大小写导致linux未注入默认用户

Cherry pick of #5021 on release/3.1.
#5021: fix: 避免因大小写导致linux未注入默认用户

/lgtm

/approve


[WIP]Required vs options

This will close out #260 by splitting up the required vs optional output in the usage output.

This change introduces two new variables requiredKeys and optionalKeys. It moves useage printing into its own function, and calls it for each type of key.
Todo

[x] Implement fix
[ ] Fix unit tests
[ ] Add any additional tests

@ammeep  closing this in favor of https://github.com/bcoe/yargs/issues/274, which I think is a great generic solution -- let's us support your behavior and other category names :)
I encourage you and @nexdrew to sync up on this feature, so that we make sure everyone's needs are addressed.

Sounds good :+1:


add gencode reference

two new references added to the S3 bucket:

human genome gencode v30 + ERCC + ChrM
the one above + HAV_18F virus

You can test this using the --branch option for evros:
evros --branch aopisco-add-HAV18-homoERCC92 alignment.run_start_and_htseq ...
If the corresponding files are in the right place (index tgz in czbiohub-reference/STAR/ and gtf in czbiohub-reference/velocyto/)  it should work fine...

@jamestwebber the branch seems to be working but the jobs are not able to succeed. there is a problem with the genome that I can't understand: https://us-west-2.console.aws.amazon.com/cloudwatch/home?region=us-west-2#logEventViewer:group=/aws/batch/job;stream=aegea_util_aws_batch_jd_27f7c94e/default/17d12cfd-099d-4dfd-bfbb-7404762bdc51

testing completed

@jamestwebber what are the steps to make the new human ref available for 10X/cell ranger as well?

That requires making a separate cellranger reference (cellranger mkref) and modifying the corresponding scripts.


gRPC with TLS is not working for me

Hello everybody,
I followed the tutorial for TLS termination.
It is perfectly working for non-gRPC deployments.
The issue is when i try to use TLS with gRPC. The gRPC server is started with some credentials
tlsCreds, err := credentials.NewServerTLSFromFile("certs/fullchain.pem", "certs/privkey.pem")

I deploy this just like it is said in the documentation:
---
apiVersion: v1
kind: Service
metadata:
  labels:
    service: helloworld-tls
  name: helloworld-tls
  annotations:
    getambassador.io/config: |
      ---
      apiVersion: ambassador/v0
      kind: Mapping
      name: grpc_mapping_helloworld_tls
      grpc: true
      prefix: /helloworld.Greeter/
      rewrite: /helloworld.Greeter/
      service: helloworld-tls.ms-dev
      ambassador_id: ambassador-tls
spec:
  type: ClusterIP
  ports:
  - port: 80
    name: helloworld-tls
    targetPort: grpc-api
  selector:
    service: helloworld-tls
---
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: helloworld-tls
spec:
  replicas: 1
  template:
    metadata:
      labels:
        service: helloworld-tls
    spec:
      containers:
      - name: helloworld-tls
        image: [MY_IMAGE]
        ports:
        - name: grpc-api
          containerPort: 50151
        resources:
          limits:
            cpu: "0.5"
            memory: 500Mi
      restartPolicy: Always

When i try to ping Ambassador with a client using TLS and the same certs (used for my domain name on top of the external IP of the ambassador svc), i got the given issue:
upstream connect error or disconnect/reset before headers

I can read the logs of Ambassador's pods, and I can see that the ambassador is routing to the right service, but the server seems to be closing the communication:

The TLS communication is fine in my computer, even when I forward the port of the pods of the deploy on my machine.
Do you have an idea?
Thanks,
Maxime

@maximematheron I hope this has been resolved elsewhere but do you have alpn_protocols: h2 set in the TLS module?


Downloading and Installing Libraries in the Package Manager

Summary
We need to implement the logic for downloading a specific library version.
Value

Libraries can be downloaded from the repository.

Specification

[ ] A helper that updates the available editions - download the list of editions and download any missing edition files.

[ ] A setting file that specifies sources for the editions, initially only our main repo, but custom repos could be added here.

[ ] Parser for library manifest and metadata files.
[ ] Download the manifest file for the library.
[ ] Recursively install all dependencies first.
[ ] Download the required packages.
[ ] Create a directory in the library path for the library and extract the packages there.
[ ] Ensure that there are no conflicts when multiple instances are installing libraries.

Possibly include a lock for 'adding a library' and per-library locks.
An alternative simpler solution is to allow only one installation at a given time, but that is a bit limitting.

Acceptance Criteria & Test Cases

The above specification has been completed.
[ ] The functionality has been tested to a reasonable extent.

I'm very much on the fence here with estimation - in a good scenario it should take about 4 days to do it but the locking mechanisms are often problematic so maybe 5 will be safer to account some buffer for unexpected troubles.


Allow conditional uniforms.

If I have multiple shaders where some of them have one uniform and some don't, there is no easy way to describe this with glium.
If uniform is included which is missing in the shader there is error message.
If I copy ther uniform! call for all the different uniform sets and try to use branches to select one it fails because the uniform is encoded in the type system and different branches have different types.

uniform! is not the only way to pass uniforms. All you need is an object that implements the Uniforms trait.
You could create an enum or something similar that implements the trait.


added custom options in config for residual plots

This allows the user to set the style of the error bars in the residual plots via the config. Aids when there are many data sets or just one.

Codecov Report

Merging #181 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #181      +/-   ##
==========================================
+ Coverage   74.21%   74.21%   +<.01%
==========================================
  Files         117      117
  Lines       11963    11964       +1
==========================================
+ Hits         8878     8879       +1
  Misses       3085     3085

Continue to review full report at Codecov.

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


fix(dataset): normalize tokenizer config and change hash from tokenizer class to tokenizer path

Fix hash across tokenizers. We should not base on tokenizer class name as they could have different vocabs.

Description

Motivation and Context

How has this been tested?

Screenshots (if appropriate)
Types of changes

Social Handles (Optional)

Test failing due to not normalizing config, I believe.


Over heating in buildings should be acknowledged

also, the infiltration rate should be adjust accordingly

#16 I belive this should be solve there.

Idea:
(1) According to DIN EN ISO 13792

This issue will also be attacked in #16

Closed for now. Continuing work in #256 and others.


added c calculator  , js login , py random reddit post

:D
A C calculator was added , a js login with google thingy and obtaining a random post

oopsie
i'll close this


Combat mode action isn't predicted

The popups match now (great) but now it's not predicted (not great).

Actually if I recall there was a lag where the icon updated but not combatmode itself so I need to double-check this.


Add a new config object for compactConfig

Fixes #5242.

This change is

@jihoonson, doesn't this patch add a new endpoint: /druid/coordinator/v1/config/compaction and remove the compaction config from the dynamic config (where it used to be)? I meant reflecting those changes in the docs.

@gianm actually the API endpoint is not changed. I only added a new config object for compaction config. Do you think the API endpoint should be changed as well?

Sorry, I was being really dumb. I didn't realize the endpoint already existed through a different code path.

@gianm oh, sorry. I finally got your point. Fixed docs according to the changed APIs.

@gianm thanks. Fixed.


Fix method name in getting started

elementFromXMLFilename doesn't  exists or was renamed to fileExtension
See: https://github.com/ZaBlanc/RaptureXML/blob/master/RaptureXML/RXMLElement.h#L53

3 years without any comment I'm going to close it


tcp keep alive error when running Mongod on Windows Bash

Hello - I am trying to install mongodb (3.0) on the latest preview build (14393) of Windows Bash (I am on the fast ring and updated windows Bash today with the lxrun command).
I have a couple of issues:

When we install Mongodb and run it from the command line, I see an error

2016-07-27T15:42:09.861-0400 E NETWORK  [initandlisten] can't get TCP_KEEPIDLE: errno:22 Invalid argument
2016-07-27T15:42:09.861-0400 E NETWORK  [initandlisten] can't get TCP_KEEPINTVL: errno:22 Invalid argument

When I looked up this error, it relates to not finding the keepalive interval for TCP packets over mongo.
I checked the /proc/sys/net folders and found nothing there.  Is that an intentional left out or is it something i need to install.  I'm not a guru at Ubuntu, but know my way around fairly well.  This is an area I do not know so well so pointers would be helpful.
My other question is can I run mongod as a service (i.e. service mongod start).  I don't know if that is something that the team intentionally left out or if I am doing something wrong during the installation.
I'm assuming also that mongo is something I should be able to run on Windows Bash.  right?
Here's some doc on mongo and how it uses keepalive.  https://docs.mongodb.com/v2.6/faq/diagnostics/
Thanks

#645 dup.

@alanosman You didn't do anything wrong during installation. Any files in the /proc directory are "ProcFs" files and are implemented by our driver.  The /proc/sys/net is currently not implemented but it is on our backlog.
The TCP_KEEPIDLE and TCP_KEEPINTVL socket options are currently stubbed and it looks like getsockopt will return a failure.  We have a lot of networking work on our plate post Windows 10 Anniversary Update and this definitely falls into that bucket.

@benhillis That is awesome to hear.  Shall I close this?

I'm fine leaving the issue open, it might be useful for other people hitting the same unimplemented surface area.

@benhillis awesome - I'll keep an eye out for the changes when they hit. You guys are doing rock solid work and it's very much appreciated by folks like me who are Windows based, but also need Liniux.  This will make development a heck of a lot smoother.  Thanks!

@alanosman - Thanks for reporting the issue and trying out WSL. We are glad to know that it is helping streamline your dev process. As @benhillis has indicated, we are looking into implementing these socket options. Please continue the feedback coming.

@alanosman

My other question is can I run mongod as a service (i.e. service mongod start)

I recently created a issue with similar problem here https://github.com/Microsoft/BashOnWindows/issues/796 and get answer https://github.com/Microsoft/BashOnWindows/issues/796#issuecomment-238048520
You can just first install mongodb with sudo apt-get install mongodb (in this case you can run mongodb with sudo service mongodb start) then without remove of this version install latest version with instructions from official website for Ubuntu 14.04
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv EA312927
echo "deb http://repo.mongodb.org/apt/ubuntu trusty/mongodb-org/3.2 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-3.2.list
sudo apt-get update
sudo apt-get install -y mongodb-org

Now you can again run MongoDB with sudo service mongodb start and see that your version of mongodb (latest at this moment) 3.2.8

Hi @Zx-EvM and all, I tried following the steps listed here and on #796 and it's still failing to run the service. Unfortunately I'm not super knowledgeable about windows services or how WSL is ideally supposed to run Mongo, but I was able to get it installed and have version 2.4.9. I ran the apt-get command above and the output looks like everything succeeded, but when I try to sudo service mongodb start it gives the following:
`root@blakes-PC:/etc# sudo service mongodb start
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused

Starting database mongodb                                                                                [ OK ]
root@blakes-PC:/etc#`

Interestingly, I have a file named mongodb in etc/init.d/. Not sure if that's relevant but @Zx-EvM mentioned not having that on the other thread.
Any help would be appreciated - apologies if I'm missing something or my question doesn't make sense. Thanks!

Hi @bschwartz757 -- for what it's worth, I believe the upstart error is a red herring; it doesn't prevent mongodb from starting.  Could you confirm that mongodb didn't start anyway?  Assuming that it didn't start, could you look around a little to see if there are error logs anywhere?
Keep in mind that, if you start a background process this way, it will be terminated when you close all WSL terminals.

Thanks for the response, guys! I'll have to get back to you on that
unfortunately. Assuming mongodb is in fact running, would I just be able to
run mongod from a new terminal window? I'm embarrassed to say I didn't
think to try that... just assumed it would start in the current window.
I'll give it a shot when I'm back at my home machine and let you know.

Blake Schwartz

On Tue, Sep 20, 2016 at 8:52 AM, Adam Seering<EMAIL_ADDRESS>wrote:

Hi @bschwartz757 https://github.com/bschwartz757 -- for what it's
worth, I believe the upstart error is a red herring; it doesn't prevent
mongodb from starting. Could you confirm that mongodb didn't start anyway?
Assuming that it didn't start, could you look around a little to see if
there are error logs anywhere?
Keep in mind that, if you start a background process this way, it will be
terminated when you close all WSL terminals.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BashOnWindows/issues/695#issuecomment-248344418,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHK9nAHjk4QgxYPMik_3F5sp0HeMEOC4ks5qsAEugaJpZM4JWjxM
.

@aseering Hmm, this looks promising - I was in fact able to get the server running (it looks like) although I had to feed it a dbpath and port - it didn't recognize the existing data/db/ folders on my Windows installation that I've been using with Git Bash. If anyone else has the same problem, this worked for me:
mongod --dbpath /mnt/c/data/db/ --port 29019
although it seems to re-assign the process to a different port (30019 in my case.)
I'm able to connect from the mongo shell, but unfortunately it looks like it's still using version 2.4.9:
MongoDB shell version: 2.4.9
connecting to: test
Tue Sep 20 19:57:18.518 ERROR: can't get TCP_KEEPIDLE: errno:22 Invalid argument
Tue Sep 20 19:57:18.518 ERROR: can't get TCP_KEEPINTVL: errno:22 Invalid argument
> db.version()
2.4.9
>```
I tried re-running the apt-get command @Zx-EvM referenced above for version 3.2, and it seems to succeed, but I'm still only getting access to the older version.

Any ideas?

This should be fixed in the latest insider build 14971. Closing it out. If the issue persists, please let us know and we can reopen it.


Device mismatch in PGD PyTorch

Describe the bug
When running on the GPU, PGD (PyTorch) complains about operands being on different devices:
'# Apply mask
if mask is not None:
grad = torch.where(mask == 0.0, torch.tensor(0.0), grad)
Looks like torch.tensor(0.0) should be mapped to self.estimator.device (since mask and grad are).
https://github.com/Trusted-AI/adversarial-robustness-toolbox/blob/1.6.1/art/attacks/evasion/projected_gradient_descent/projected_gradient_descent_pytorch.py

Hi @manishbcd
Thank you very much for reporting this issue! We'll fix it with 1.6.2.


[MOI] add support for MOI.Interval{Float64}

This has been added 6 weeks ago in Ipopt.jl.
Supporting MOI.Interval{Float64} leads to consistent results with ExaModels, as otherwise the interval constraints are rewritten as one constraint with a lower-bound and another constraint with a upper-bound.

Codecov Report
Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (7cb834f) 69.35% compared to head (76a1ef0) 69.68%.

Files
Patch %
Lines

src/Interfaces/utils.jl
50.00%
6 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
+ Coverage   69.35%   69.68%   +0.33%
==========================================
  Files          39       40       +1
  Lines        4542     4566      +24
==========================================
+ Hits         3150     3182      +32
+ Misses       1392     1384       -8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Temporary fix of leapp.stdlib

Now the __write_raw (and run) function should be working with Py2
and Py3 as well, but it is temporary solution as the leapp.stdlib.call
is still in bad shape.
Fixes: #487
Related issue #488

Can one of the admins verify this patch?


webhook build only on merged PR

remove ghRepo config var
use config vars "directly"
listen for pull_request event
only run config.ghPushCommand if data.pull_request.merged is truthy

@kwrl thoughts?

adding: the reason for this is to avoid circular builds when pushing to the same repo (eg gh-pages branch).


Remove the need to use opaque return types.

Having an associatedtype on TensorOperation requires makeOp to be defined with opaque return types as follows:
ExecutionContext.makeOp() -> some TFTensorOperation
However, opaque return types are not available everywhere yet. Removing the associatedtype requirements for the time-being so that makeOp can be defined as follows:
ExecutionContext.makeOp() -> TFTensorOperation
This also merges the declaration of protocol TensorOperation into TFTensorOperation.swift.

@rxwei @dan-zheng are you OK with this PR?

Confirmed that this PR builds on macOS.


Update README with notes for using f90nml

Added notes and an example for using the f90nml CLI to insert multiple input filenames into the namelist at once

Thanks both! I've incorporated your changes, also linking f90nml to its readsthedocs page


updated readme accordingly to the existing tasks.

🚀 Description
Current Readme doesn't expose the current situation of the repository.
📄 Motivation and Context
I had troubles to see what grade task I should be executing.
🧪 How Has This Been Tested?
It's purely based on IntelIJ Tasks and what I could get from there.
📦 Types of changes

[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)

✅ Checklist

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.

👍


Fix io_setup EAGAIN errorno

The io_setup could occasionally be interrupted and return EAGAIN, so using retry to fix.

/kind improvement

/lgtm
/approve


release 3.0

Hello,
We're using Rails 5.0.x.
Draper 3.0.0pre1 supports version 5.0.x of rails. That is what we've been using since August 10, 2016.
Is there a road map to finally releasing draper 3.0? So rails 5.0 developers can point to a non-pre gem?
Thanks

@seanlinsley is looking for new maintainers, anyone?  Everyone else appears to have moved on, ActiveAdmin is the only dependent project I know of.  @owen2345 at Camaleon CMS?

I'm waiting for new version!! Is anyone working for new version release?

@varyonic I don't know if I can commit to maintaining full time; however, I'd like to do what I can to help get 3.0.0 released and then go from there.  I'd hate to see such a useful gem die because we failed to provide support for Rails 5.
We have been running 3.0.0.pre1 in production with Rails 5 for several months now without issue. When attempting an upgrade to Rails 5.1, I had to point draper to master to get it to work. So it appears that master is compatible with Rails 5 and 5.1 to some extent.
@seanlinsley Are there specific issues you were hoping to get fixed before releasing version 3.0.0? If not, I propose we cut a release for 3.0.0 and fix reported issues from there. That way draper isn't a roadblock for upgrading Rails and people aren't tempted to just remove it from their project.

I want to help as I can 😄

Pull request open: https://github.com/drapergem/draper/pull/780

This release has been merged and push to RubyGems. Please report any issues you may come across.

Thank you for the great work! We were really looking forward to this release :)
Would you like to create 'a release' for 3.0.0 on GitHub as well? If so, this link might be useful as a reference: https://help.github.com/articles/creating-releases/

A release on GitHub is automatically created if a version tag is created.

@kenta-s Sorry about that. I have created the corresponding Github release.


Delegate Marshalling

Initital support for delegate marshalling.

Enabled only in full runtime
Doesn't work in non-windows platforms
Only supports open static delegates

@sergiy-k @MichalStrehovsky  @jkotas

You can move these a couple of lines above into the existing #ifdef USE_PORTABLE_HELPERS instead of having to declare another one

Refers to: src/Native/Runtime/portable.cpp:456 in b17dcdc. [](commit_id = b17dcdc25cf3637991c6bcff0a0cc4b8efbde673, deletion_comment = False)

@shrah Can you get someone from the interop team have a look at the changes in PInvokeILEmitter.cs and Marshaller.cs? I'm not looking at any of those.

@tijoytom  @yizhang82  PTAL at the Marshaller.cs and PInvokeILEmitter.cs

LGTM


Setup markdown lint check to avoid 403 error

GitHub returns a 403 response when we check links. You have to accept compressed formats in the response.

The check "Test / integration-test-with ..." is failing because of this.


chore: merge updated release version to dev

Codecov Report

Merging #264 (78a0656) into dev (c016d21) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #264   +/-   ##
=======================================
  Coverage   53.57%   53.57%
=======================================
  Files          84       84
  Lines        6087     6087
=======================================
  Hits         3261     3261
  Misses       2826     2826

Continue to review full report at Codecov.

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


[BUG] ChunkReader.php Linea: 55 Mensaje: Undefined array key

1⃣ Is the bug applicable and reproducable to the latest version of the package and hasn't it been reported before? (Currently 3.1.x)
Yes, in fact the bug is in the "maatwebsite/excel": "^3.1" version.
2⃣ What version of the package, Laravel and PHP do you use? Please provide the FULL version number.
"PHP 8.0.5 (cli) (built: May  3 2021 11:58:58) ",
"laravel/framework": "^8.0",
3⃣ Describe your issue. Please be short, but concise.
At implementing "WithChunkReading", I receive this message:
/home/user/project/api/vendor/maatwebsite/excel/src/ChunkReader.php Linea: 55 Mensaje: Undefined array key "SpreadSheet1""
Where: SpreadSheet1 is the name of the SpreadSheet in my File: Totals.xlsx
4⃣ How can the issue be reproduced? Please provide easy-to-reproduce steps (repository, simple code example, failing unit test).
Use the same code that the example in:
https://docs.laravel-excel.com/3.1/imports/chunk-reading.html#using-it-together-with-batch-inserts
And use it with a file with one single SpreadSheet and 10898 rows
5⃣ What should be the expected behaviour?
The insert of the rows and no error message.
6⃣ Have you filled in the entire issue template? If not, your issue will be closed. Thanks for using the package! 🙌
Thank you, i hope it will be solved

Please provide the FULL version number of the package too
"name": "maatwebsite/excel",
"version": "3.1.27",

I have the same problem with laravel 8. Is there any guide to solve this problem?

Please update to latest version of this package.

It works! But now the import function doesn't return to the controller execution.I guess that's something else. Any Ideas?

No idea what you mean with "doesn't return"

No idea what you mean with "doesn't return"

Ok, this is my code:
public function upload(Request $request){
try{
$file = $request->file('filexlsx');
$datetim = date("d").date("m").date("Y").date("H").date("i").date("s");
$renameFile = 'MyFile'.$datetim;
$upload_success = $request->file('file')->move(storage_path(),$renameFile.'.xlsx');
        $url = strval(storage_path().'/'.$renameFile.'.xlsx');
        Excel::import(new UsersImport, $url);

        $return['info']['message'] = 'Data has been loaded corrrectly';
        return response()->json($return,200);
    }
    catch (\Throwable $th) {
        return response()->json($th->getCode(),400);
    }
}

And i'm testing with PostMan and it hangs out, but if I check the database, all data is inserted, the only problem is that the controller returns nothing! I wonder what have I missed?

Try and debug it: dd() or xdebug and see where it hangs.

New version is released with updated phpspreadsheet to 1.18


Correct bundle show deprecation

What was the end-user problem that led to this PR?
The problem was bundle show deprecation messages are incorrect:
$ bundle show yard
[DEPRECATED FOR 2.0] use `bundle list` instead of `bundle show`
Resolving dependencies...
/home/deivid/Code/activeadmin/.bundle/ruby/2.5.0/gems/yard-0.9.16
$ bundle list yard
ERROR: "bundle list" was called with arguments ["yard"]
Usage: "bundle list"

What was your diagnosis of the problem?
My diagnosis was that deprecation messages only mention bundle list, but in some cases, the replacement is bundle info.
What is your fix for the problem, implemented in this PR?
My fix is to replace "show" in the original command with the appropriate alternative in each case.
Why did you choose this fix out of the possible options?
I chose this fix because it was the most user friendly message, since it prints the exact command the user needs to type to get rid of the warning.

@bundlerbot r+


fix: allow notifying of marker tap event (after #331)

PR #331 changed the mapViewDidTapMarker method where this return prevents the InfoWindow from showing.

@dapriett ok like this then (works for me locally indeed)

Thanks for the PR @abhayastudios! 👏


Program Opens then Immedietly Closes

Traceback (most recent call last):
  File "__main__.py", line 3, in <module>
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "PyInstaller\loader\pyimod02_importers.py", line 385, in exec_module
  File "start.py", line 13, in <module>
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "PyInstaller\loader\pyimod02_importers.py", line 385, in exec_module
  File "commands\scraper.py", line 35, in <module>
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "PyInstaller\loader\pyimod02_importers.py", line 385, in exec_module
  File "utils\download.py", line 73, in <module>
  File "utils\config.py", line 42, in read_config
  File "utils\config.py", line 84, in get_current_config_schema
  File "utils\config.py", line 294, in get_threads
ValueError: invalid literal for int() with base 10: ''
[4824] Failed to execute script '__main__' due to unhandled exception!

Fixed


Error: DelayedStream#maxDataSize of 2097152 bytes exceeded.

Getting this error when trying to upload a 10mb file....
Is there a quick fix??
events.js:141
throw er; // Unhandled 'error' event
^
Error: DelayedStream#maxDataSize of 2097152 bytes exceeded.
at FormData.CombinedStream._checkDataSize (C:\Apps\workspace\betty.acdb.ui\node_modules\form-data\node_modules\combined-stream\lib\combined_stream.js:165:19)
at emitOne (events.js:77:13)
at PassThrough.emit (events.js:169:7)
at PassThrough.source.emit (C:\Apps\workspace\betty.acdb.ui\node_modules\form-data\node_modules\combined-stream\node_modules\delayed-stream\lib\delayed_stream.js:30:21)
at readableAddChunk (_stream_readable.js:146:16)
at PassThrough.Readable.push (_stream_readable.js:110:10)
at PassThrough.Transform.push (_stream_transform.js:128:32)
at afterTransform (_stream_transform.js:76:12)
at TransformState.afterTransform (_stream_transform.js:54:12)
at PassThrough._transform (_stream_passthrough.js:21:3)

Do you mind to provide code sample? Thank you.

Will share the required details in some time. Here's the info I can provide right now:
I am using node-multiparty to parse the form req and when the form emits part, I append it to the form-data.
This error  is originating @ combined-stream.
The default maxDataSize in combined stream is 2MB.
Here is the code snippet of combined stream:
CombinedStream.prototype._checkDataSize = function() {
this._updateDataSize();
if (this.dataSize <= this.maxDataSize) {
return;
}
var message =
'DelayedStream#maxDataSize of ' + this.maxDataSize + ' bytes exceeded.';
this._emitError(new Error(message));
};
Can you pls use this info and see what might be causing this issue? Maybe there should be an option to override maxDataSize of combined-stream.
Ps. I really need a quick fix. Thanks!

Here is the code sample:
let form = new multiparty.Form();
var payload = new FormData();
payload.append('auth', conf.documents.auth);
form.on('error', function(err) {
tLogger.info('Error parsing form: ' + err.stack);
callback(null);
});
form.on('field', function(name, value) {
tLogger.info('got field ' + name + ' == ' + value);
keywords.push(value);
});
// Parts are emitted when parsing the form
form.on('part', function(part) {
// filename is defined when this is a file
if (part.filename) {
  //append the part to the payload which will be sent
   payload.append(part.filename, part, { filename:part.filename});//this is were the error comes
   part.resume();
}
part.on('error', function(err) {
  tLogger.error('Error is processing stream' + err);
});

});
form.on('close', function(){
I make POST request here.....
})

We are also facing same issue, did anyone found a solution or workaround for this issue?
Error: DelayedStream#maxDataSize of 2097152 bytes exceeded.

I took a code and made some changes to it. Here's the copy, do a require for this and use it the way you'd use form-data until a permanent fix is pushed:
form-data.zip

Do we have proper fix for this issue?

@maxcc0 Thanks for the fix. Do you mind to create a pull request to this repo? So we can see the nature of the change?
Also, based on the error log, it seems like the issue comes from https://github.com/felixge/node-delayed-stream package, which already set to Infinity here: https://github.com/felixge/node-combined-stream/blob/master/lib/combined_stream.js#L44
PS. And beware of downloading random zip files from internet :)

I see, combined-stream has it's own maxDataSize – https://github.com/felixge/node-combined-stream/blob/master/lib/combined_stream.js#L10
So what you can try here:
var payload = new FormData();
payload.maxDataSize = Infinity;
payload.append('auth', conf.documents.auth);

And we'd look into ways of allowing custom options at creation time, similar to what combined-stream does. What do you think @DylanPiercey?

@alexindigo good idea for custom options. And I remember I just removed the maxsize condition from one of the files somewhere (it's working good in production for a year now 😃). I can check that tomorrow and share it here.

@alexindigo what are your thoughts on doing something like:
FormData.MAX_FILE_SIZE = Infinity

I personally like this because it doesn't do anything in the browser.

It's a singleton, so it will affect all instances in your node process, which might be beyond desirable. :)

@maxcc0 It's a luxury when you can modify files in production :)

@alexindigo yeah I suppose. What about just setting it on the instance? Or do you have something else in mind?

Yep, there are couple ways of doing it on the instance.
Less obvious, supposedly works "out of the box":
var payload = new FormData();
payload.maxDataSize = Infinity;

"Classical" approach, doesn't work at the moment:
var payload = new FormData({
  maxDataSize: Infinity
});

Surprisingly
var payload = new FormData({
  maxDataSize: Infinity
});

Works in the browser, so I'm not against it. Although it's probably worth checking that no browsers error out with this.

It works-works? Or just being ignored? :)

Just being ignored, but that's fine IMO. Another alternative though is just setting the maxDataSize to infinity and pushing that part of the api on the user to check manually?

👍  Like overloading checkDataSize with custom implementation – I like the idea :)

This way we aren't tied to combined-stream either.