Instructions for stash-scm-collector

Are there any instructions available for stash-scm-collector ??
I am assuming that it would need application.properties file to run but what exactly are the tokens in that property file that this collector would be looking for ??
Thanks

Default server configuration
debug=true
spring.jpa.show-sql: true
Default server configuration values
server.contextPath=/api
server.port=${PORT:0}
#server.port=${PORT:0}
dashboard.properties
#dbhost= xxxxxxxxxx
dbhost= localhost
dbport= 27017
dbname=
dbusername=
dbpassword=
#Collector schedule (required)
git.cron=0 0/1 * * * *
#mandatory
git.host = https://xxxx.xxxxxx.com/
#mandatory
git.api=/rest/api/1.0/
#Maximum number of days to go back in time when fetching commits
git.commitThresholdDays=15
#Credentials should be enter in the UI. Is not necessary.
#git.user=
#git.password=

Keyur,
For the property, git.api.
/rest/api/1.0/, Is this an api exposed by stash ??
Shall i simply replace this as a value for this property
Source code of hygieia has /!api/2.0/repositories/ as value for this property.
Will either work ??
Thanks

You need to make code change to read these properties inside the client code in collector
Sent from my iPhone
On Apr 11, 2016, at 2:59 PM, aryasunny <notifications<EMAIL_ADDRESS>wrote:
Keyur,
For the property, git.api.
/rest/api/1.0/, Is this an api exposed by stash ??
Shall i simply replace this as a value for this property
Source code of hygieia has /!api/2.0/repositories/ as value for this property.
Will either work ??
Thanks
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/496#issuecomment-208530797

I thought these properties are already being read and that is why we need to furnish these properties values to make the code work.
What is this git api being used for ??
source code has host as bitbucket.org and git.api as /!api/2.0/repositories/
So what i believe is that there is an api being exposed here --> bitbucket.org/!api/2.0/repositories/ which is being used inside the code.
so I i replace the value of host property from bitbucket.org to my internal bitbucket server then this URL --> MyinternalBitBucket/!api/2.0/repositories/ will not make any sense. then do i have to write an api that would do the same work as this api --> /!api/2.0/repositories/

This is what I am doing
I am giving the repository URL for my internal bitbucket server and a corresponding branch name.
I am getting connection timeout on that URL. Now this URL when I am trying to access through my browser it asks me for an username and password.But inside the code I am not giving any username or password. So will we get a connection timeout in this case because username and password was not provided.
And I really don't see this git.host and git.api being used anywhere.
Thanks

@softwareklinic will you have time to provide some help here

Yes I will send out changes tonight - I may not have time to PR - but will upload the code and send you the link - which you can test / merge / PR
Sent from my iPhone
On Apr 11, 2016, at 8:10 PM, aryasunny <notifications<EMAIL_ADDRESS>wrote:
@softwareklinichttps://github.com/softwareklinic will you have time to provide some help here
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/496#issuecomment-208652250

thanks keyur, I understand that you are writing some code for support for authentication.
But can you spare 2 minutes to answer this question of mine, it will help me understand the flow of the code. I will really appreciate that.
What is this git api being used for ??
source code has host as bitbucket.org and git.api as /!api/2.0/repositories/
So what i believe is that there is an api being exposed here --> bitbucket.org/!api/2.0/repositories/ which is being used inside the code.
so I i replace the value of host property from bitbucket.org to my internal bitbucket server then this URL --> MyinternalBitBucket/!api/2.0/repositories/ will not make any sense.
then do i have to write an api that would do the same work as this api --> /!api/2.0/repositories/

@softwareklinic @tabladrum - Need your help
I was looking into the code and found that there is a Rest service call being made to this URL --> https:////reponame
So is this a REST api provided by bitbucket to give the stats of the repository provided in reponame ??
And so I can assume that my internal bitbucket server also will have this API exposed ??

I am not familiar with bitbucket api. I would google it up unless @softwareklinic knows it for sure.

thanks for replying. If this is not an api exposed by bitbucket, then how are we gathering stats of the repository to show on dashboard.
Sorry for asking so many questions

it does actually
https://developer.atlassian.com/static/rest/bitbucket-server/4.0.0/bitbucket-build-rest.html

@softwareklinic @tabladrum  - any suggestions/answer for the question
If this is not an api exposed by bitbucket, then how are we gathering stats of the repository to show on dashboard.

@softwareklinic @tabladrum - any insights into --> how are we gathering stats of the bitbucket repository to show on dashboard. What is the service that is giving us the stats for dashboard.
I created a repository on bitbucket, but when i use the below URL, I get "404 not found"
https://bitbucket.org/rest/api/1.0/aryasunny/renewal/commits?sha=feature/develop&since=2016-0
4-12T21:08Z

Give me few - will get back
Sent from my iPhone
On Apr 12, 2016, at 9:33 PM, aryasunny <notifications<EMAIL_ADDRESS>wrote:
@softwareklinichttps://github.com/softwareklinic @tabladrumhttps://github.com/tabladrum - any insights into --> how are we gathering stats of the bitbucket repository to show on dashboard. What is the service that is giving us the stats for dashboard.
I created a repository on bitbucket, but when i use the below URL, I get "404 not found"
https://bitbucket.org/rest/api/1.0/aryasunny/renewal/commits?sha=feature/develop&since=2016-0
4-12T21:08Z
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/496#issuecomment-209199513

Was able to make the bitbucket collector work
This has to be the properties in properties file
#mandatory
git.host=api.bitbucket.org
#mandatory
git.api=/2.0/repositories/
And had to made one change in the clientcode for bitbucket collector.

Sounds like we should have a separate bit bucket collector? Or should stash collector be able to handle it via properties configuration?

I will check it out at our end.
From: tabladrum<EMAIL_ADDRESS>Sent: Wednesday, April 13, 2016 9:27 AM
To: capitalone/Hygieia
Cc: Shah, Keyur
Subject: [E] Re: [capitalone/Hygieia] Instructions for stash-scm-collector (#496)
Sounds like we should have a separate bit bucket collector? Or should stash collector be able to handle it via properties configuration?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/496#issuecomment-209473670

Most likely it is just properties… not a whole lot – since – it’s a natural progression of stash --> bitbucket
From: tabladrum<EMAIL_ADDRESS>Sent: Wednesday, April 13, 2016 9:27 AM
To: capitalone/Hygieia
Cc: Shah, Keyur
Subject: [E] Re: [capitalone/Hygieia] Instructions for stash-scm-collector (#496)
Sounds like we should have a separate bit bucket collector? Or should stash collector be able to handle it via properties configuration?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHubhttps://github.com/capitalone/Hygieia/issues/496#issuecomment-209473670

@tabladrum @softwareklinic
for me, the stash-scm collector itself worked. We have client code for both stash and bit-bucket both in stash collector module itself
When working with stash I had to place @component annotation in class DefaultStashClient.java
When working with bit-bucket then, I had to place @component annotation in class DefaultBitbucketClient.java
and had to make small code change in both of these client files.
But it would be a good idea to have separate collector for bit-bucket. Will make things bit clear.

@aryasunny Can you do a PR for a new BitBucketCollector? Unless there is a smart way to handle the annotation? @softwareklinic - thoughts?

@tabladrum  I am too new for this thing. I would need some time before I can get a good handle on this to do a PR. Will keep you posted.

closing this issue. Will work on getting the code ready for PR


[2/n permissions] feat: add permission hooks

(For the entire PR stack)
Permission hooks are hooks associated with a validation function. The proposed model of permissions is:

A validation function, global or associated with a selector
A set of pre validation functions associated with the validation function that will all run, and must all pass (AND logic)
A set of permission hooks (pre and post execution) that applies to the validation. If the permission hook requires the UO context, the top level execution call must be made to executeUserOp, and the full PackedUserOp struct would be passed to the hook

Changelog in this PR:

Add a boolean requireUOContext to ExecutionHook for plugins to signal that the hook needs PackedUserOperation
Add execution hooks associated with a validator
Add getters in the loupe for these hooks
Add string[] to PluginMetadata for permission plugins to declare ERC-7715 permission strings
Use a variable uint8 requireUOHookCount to track the number of permission hooks to allow a cheap check during validation

2 issues that will be addressed in future PRs:

As part of the change, plugins can specify permission hooks to install in the manifest, associated with any validation function. Long term, permission configuration should be user-defined on install time as opposed to plugin-defined on plugin compile time. This change would be done in a separate PR, in the 6900 plugin install configs revamp.
Pre execution/permission hooks now pass in abi.encodePacked(msg.sender, msg.value, msg.data) or abi.encode(PackedUserOperation). As we'll likely transition to composable validation with "entity ids", the final shape of execution hooks relies on that. At the same time, instead of passing in msg.value, we should consider passing in an int256 "outgoing value minus incoming value"

addresses: https://github.com/erc6900/resources/issues/50


Missing Export.h

Compiling the sources fails, because Value.h contains:
#include "Export.h"
But this file is not found.

This file should have been generated from the cmake build process.
Though, I see that if it is not installed, the Export.h is found in the build directory, and not with the include files.
Here's a sample compilation I just did:
~/.../jsonbox/test ⃲ git clone git@github.com:anhero/JsonBox.git
Cloning into 'JsonBox'...
remote: Counting objects: 1183, done.
remote: Total 1183 (delta 0), reused 0 (delta 0), pack-reused 1183
Receiving objects: 100% (1183/1183), 620.78 KiB | 0 bytes/s, done.
Resolving deltas: 100% (699/699), done.
Checking connectivity... done.

~/.../jsonbox/test ⃲ mkdir build

~/.../jsonbox/test ⃲ cd build/

~/.../test/build ⃲ cmake ../JsonBox/
-- The C compiler identification is GNU 5.2.0
-- The CXX compiler identification is GNU 5.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_VISIBILITY - Success
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY
-- Performing Test COMPILER_HAS_HIDDEN_INLINE_VISIBILITY - Success
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR
-- Performing Test COMPILER_HAS_DEPRECATED_ATTR - Success
-- Configuring done
CMake Warning (dev) at CMakeLists.txt:36 (add_library):
  Policy CMP0063 is not set: Honor visibility properties for all target
  types.  Run "cmake --help-policy CMP0063" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Target "JsonBox" of type "STATIC_LIBRARY" has the following visibility
  properties set for CXX:

    CXX_VISIBILITY_PRESET
    VISIBILITY_INLINES_HIDDEN

  For compatibility CMake is not honoring them for this target.
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at CMakeLists.txt:82 (add_executable):
  Policy CMP0063 is not set: Honor visibility properties for all target
  types.  Run "cmake --help-policy CMP0063" for policy details.  Use the
  cmake_policy command to set the policy and suppress this warning.

  Target "example1" of type "EXECUTABLE" has the following visibility
  properties set for CXX:

    CXX_VISIBILITY_PRESET
    VISIBILITY_INLINES_HIDDEN

  For compatibility CMake is not honoring them for this target.
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done
-- Build files have been written to: /Users/samuel/Projects/jsonbox/test/build

~/.../test/build ⃲ make
Scanning dependencies of target JsonBox
[  9%] Building CXX object CMakeFiles/JsonBox.dir/src/JsonWritingError.cpp.o
[ 18%] Building CXX object CMakeFiles/JsonBox.dir/src/Value.cpp.o
[ 27%] Building CXX object CMakeFiles/JsonBox.dir/src/SolidusEscaper.cpp.o
[ 36%] Building CXX object CMakeFiles/JsonBox.dir/src/Escaper.cpp.o
[ 45%] Building CXX object CMakeFiles/JsonBox.dir/src/Indenter.cpp.o
[ 54%] Building CXX object CMakeFiles/JsonBox.dir/src/IndentCanceller.cpp.o
[ 63%] Building CXX object CMakeFiles/JsonBox.dir/src/JsonParsingError.cpp.o
[ 72%] Building CXX object CMakeFiles/JsonBox.dir/src/Convert.cpp.o
[ 81%] Linking CXX static library libJsonBox.a
[ 81%] Built target JsonBox
Scanning dependencies of target example1
[ 90%] Building CXX object CMakeFiles/example1.dir/examples/main.cpp.o
[100%] Linking CXX executable example1
[100%] Built target example1

~/.../test/build ⃲ ls
CMakeCache.txt       example1             libJsonBox.a
CMakeFiles/          Export.h             Makefile
cmake_install.cmake  JsonBoxConfig.cmake

~/.../test/build ⃲ make install DESTDIR=.
[ 81%] Built target JsonBox
[100%] Built target example1
Install the project...
-- Install configuration: ""
-- Installing: ./usr/local/lib/libJsonBox.a
-- Installing: ./usr/local/include/JsonBox/Convert.h
-- Installing: ./usr/local/include/JsonBox/Escaper.h
-- Installing: ./usr/local/include/JsonBox/Grammar.h
-- Installing: ./usr/local/include/JsonBox/IndentCanceller.h
-- Installing: ./usr/local/include/JsonBox/Indenter.h
-- Installing: ./usr/local/include/JsonBox/JsonParsingError.h
-- Installing: ./usr/local/include/JsonBox/JsonWritingError.h
-- Installing: ./usr/local/include/JsonBox/OutputFilter.h
-- Installing: ./usr/local/include/JsonBox/SolidusEscaper.h
-- Installing: ./usr/local/include/JsonBox/Value.h
-- Installing: ./usr/local/include/JsonBox.h
-- Installing: ./usr/local/include/JsonBox/Export.h
-- Installing: ./usr/local/lib/cmake/JsonBoxConfig.cmake
-- Installing: ./usr/local/lib/cmake/JsonBoxConfig-noconfig.cmake

~/.../test/build ⃲

You might want to set those cmake options instead if using DESTDIR:
CMAKE_PREFIX_PATH
CMAKE_INSTALL_PREFIX

See cmake --help-variable <var> for more informations about their use.

I was always simply including the sources into my project and not building the library. Thanks.


Update version

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Fixes issue where certain Windows installations get the wrong home path

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender


[WIP] mongo-authmechanism

Please do not merge yet!
Add authmechanism to MongoClient call (and functions which call _get_collection).

 Deploy Handle Service 2


restic as importable module with exported main function

What does this PR change? What problem does it solve?
This PR turns the codebase into an importable Go package that exports restic's main function. The binary is a single source file that imports the package and calls the exported main function.
So why do I want this? I have a backup program (mostly for personal use) that's using restic internally. I've tried to come up with a way to distribute this program as a single binary that bundles restic. I gave up on bundling the binary and extracting it at runtime because of all the problems. However, with this change:

I can build restic into a static library
I can link that static library into my own program's binary
in my own main function, I can decide to run restic's main function based on a flag of my choice

There's no user-visible changes here and I have no intention of adding an actual library API. This is just a modification to support this particular build
(I guess the Go convention would be to move the code to pkg/. I have no strong opinion on this matter; but to begin with, I opted for a layout that didn't require me to move every source file.)
Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

This looks like a bad idea. Restic wasn't designed for this use case at all and will do things like close install signal handlers, call os.Exit on errors, etc. that mess with the state of the process calling restic.Main.

This looks like a bad idea. Restic wasn't designed for this use case at all and will do things like close install signal handlers, call os.Exit on errors, etc. that mess with the state of the process calling restic.Main.

Yes, absolutely. The only sensible way to use this is by calling restic.Main in a new process and accept that restic owns that process now and may do whatever with it.
If you're saying that this will be easy to misuse and invite people to use it incorrectly, i.e. thinking it's some kind of library API: I can't necessarily argue against that. :slightly_smiling_face: It's certainly a niche change with situational utility, but it would allow me to do my linking trick without maintaining a patch so I'm in favour of having it.

I have to agree with @greatroar this is bound to cause all sorts of strange problems.
We currently do not intend to support embedding restic into another binary. See also #404 and #1089 for previous discussions. So, I'm closing this PR, sorry.

Fair enough, I suppose, and I'm not currently invested enough in the idea to protest. 😄


Update CDN failover documentation

This documentation is out of date for two reasons:

Our DNS config has moved from alphagov/govuk-dns-config to alphagov/govuk-dns-tf, and is now deployed using Terraform Cloud
We have a new CloudFront failover distribution, which supports more functionality than the previous one

I've also raised a sister PR alphagov/govuk-dns-tf#69 (based on alphagov/govuk-dns-config#714), which can just sit in a draft state waiting to be merged if we ever need to perform a failover.
Couple of open questions before we can merge:

I’ve removed the recommendation to wait for a grace period before performing the failover, because the new distribution doesn’t carry the same degraded performance as the old one. I’m not sure if we need approval for this first (it’s quite a big change in policy).
I’m not sure what the rationale is for manually performing the failover from the AWS and GCP consoles, and then merging a PR in govuk-dns-tf (formerly govuk-dns-config) to do the same thing in an automated way(?) - should I remove the manual failover section?

Trello card
This PR is based on the documented Cloudfront failover test procedure

I’m not sure what the rationale is for manually performing the failover from the AWS and GCP consoles, and then merging a PR in govuk-dns-tf (formerly govuk-dns-config) to do the same thing in an automated way(?) - should I remove the manual failover section?

It's a funny story actually. The only time we've had to do this failover in anger, we tried to do it with Terraform. Can you guess which CDN Terraform uses to host the AWS / GCP terraform providers?
tl;dr - we found that terraform doesn't work reliably if Fastly is having a major incident. This might be fixed now that we're using Terraform Cloud (e.g. if it caches terraform providers more reliably than Jenkins did), but it's very hard to say for sure.

Thanks @ChrisBAshton!

One last thing: the test steps had a note about reducing the DNS TTL to 30 seconds, to make it quicker to switch back to Fastly. I'll defer to an SRE or Tech Architect on this one, but that sounds like a sensible addition to make to the draft govuk-dns-tf PR while we're here 👍

Good shout! I've gone with 5 minutes though, last time Fastly went down it took several hours to recover and we don't want people hammering our DNS too hard in the meantime.

It's a funny story actually. The only time we've had to do this failover in anger, we tried to do it with Terraform. Can you guess which CDN Terraform uses to host the AWS / GCP terraform providers?
tl;dr - we found that terraform doesn't work reliably if Fastly is having a major incident. This might be fixed now that we're using Terraform Cloud (e.g. if it caches terraform providers more reliably than Jenkins did), but it's very hard to say for sure.

Oh no 🙈
Thanks, this is useful context that I should add to this document. I think it probably makes sense to leave the manual failover steps there rather than splitting them out to a separate section too.

@ChrisBAshton Requesting a re-review as I think I've addressed all the feedback (n.b. I will raise a separate PR for the drill)


GIF Tracking pixel

Problem
For some environments (such as email) JS SDK will not work. We need to fallbackt to old-school GIF tracking pixel
Solution
End-point /api/v1/p.gif (GET). Parameters: data= or path.to.json.node.
Processing pipeline generally consists from two steps: 1) restore payload JSON 2) inject additional data based on headers.
Restoring JSON

If data parameter is present - treat the value as base64 encoded JSON object, otherwise start with empty {} object
For each parameter (except data), treat it as path to json node with value. E.g. /api/v1/p.gif?context.a.b=1&context.b=x will be decoded to {context: {a: {b: 1}, b: "x"}}
If compat field is present in JSON, enable compatibility mode

Injecting additional data
Unless the field is present, the following values should be added

/url (/eventn_ctx/url in compat mode) — take from referer header
/doc_host (/eventn_ctx/doc_host in compat mode), /doc_path (/eventn_ctx/doc_path in compat mode), /doc_search (/eventn_ctx/doc_search in compat mode) parse url
/user/anonymous_id (/eventn_ctx/user/anonymous_id in compat mode) — identify user based on cookie. Cookie domain should be taken from Host header, unless cookie_domain node is present in JSON.
/user_agent (/eventn_ctx/user_agent in compat mode) take from the header
/utc_time (/eventn_ctx/utc_time in compat mode) - current time in UTC as ISO string
/src - 'jitsu_gif'

As a response empty transparent GIF should be served

Keep in mind that some mail clients (at least Gmail web client) load images in s2s manner


Add deployment mode "WhatIf"

It would be great, if you could add a what-if deployment mode to understand changes that will be made before merging the changes into main. Please let me know, if you have more questions about the feature request.
For more details: https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deploy-what-if?tabs=azure-powershell

Hi @marvinbuss
Can you please explain what use case this mode will solve? We looked into it and it made more sense while being used in a CLI where you see changes and confirm whether we want to go ahead with deployment or not.
Also how urgent is this feature?

Hi @t-dedah,
The idea is to use this in a PR to check what changes will be made once the PR gets merged back into the main branch. I don't need this feature tomorrow, but it would be nice to get this implemented.

Thanks @marvinbuss for the insight.

I agree with @marvinbuss 's use case.  A similar use case would be in a CICD deployment scenario using approval workflows, where you would 'pause' after the what-if action ran so that an operator could say Yes/No to proceeding with the deployment.
Conceptually, this would be very similar to how Terraform does their plan / apply workflow.

@t-dedah Any updates?

Hi @marvinbuss I will be picking this up in next sprint, hope that wont be an issue.

Next sprint should be fine. Once this is included, I will add this to our CI/CD pipelines and test the feature.

Hi @t-dedah,
Any updates on this? Thanks!

Hi @marvinbuss its WIP, will be raising PR soon.

/not-stale

#not-stale

#not-stale

@larryclaman @marvinbuss @johndowns We have released a new version with support for additional additionalArguments.
All the extra parameters can be passed as string using additionalArguments.
additionalArguments: "--what-if --what-if-exclude-change-types Create Ignore"

Hi @t-dedah,
What do I need to do to specify a what-if deployment. This is failing:
https://github.com/Azure/data-product-streaming/blob/01b8b3c72e2d3d2fb8c3d1402ecf035f518f9062/.github/workflows/dataProductDeployment.yml#L63-L75
Thanks for your help!

I don't really understand why it is modelled as additional parameter, since it is is actually a deployment mode within Azure CLI.
But there is no what-if branch in the deployment options here: https://github.com/Azure/arm-deploy/blob/main/src/deploy/scope_resourcegroup.ts

Hi @marvinbuss
As what-if is already a parameter in az group create, we decided to use that in order to reuse the current code. All the functionalities are still same but now with addition of additionalArguments there will be no further need of enhancements through separate input for each of new request.
https://docs.microsoft.com/en-us/cli/azure/deployment/group?view=azure-cli-latest#az_deployment_group_create

Thanks for the prompt response @t-dedah! 🚀
I have tested the new feature and it works as expected. Thanks for this!
Here is the yaml: https://github.com/Azure/data-product-streaming/blob/b10ff6bd2ab9112f7605305a54b52917dec058d8/.github/workflows/dataProductDeployment.yml#L62-L75
And here is a successful run of the workflow: https://github.com/Azure/data-product-streaming/runs/4309573044?check_suite_focus=true

@t-dedah The output could be improved. There are some warnings that should be removed:

Agree about cleaning up the output.  I don't want to see errors like that when doing a "what-if" deployment.

We have removed the additionalArguments while validation step. This should resolve the warnings and other related issues.

Please reopen the issue if needed.

I'm seeing an issue now where my additional arguments are getting added to my template filename:
Error: ERROR: [Errno 2] No such file or directory: 'test.bicep--what-if'

@t-dedah Please reopen this issue. I am running into the same error.

@marvinbuss @nnellans We have released a new version with the fix for this bug.

As what-if is already a parameter in az group create, we decided to use that in order to reuse the current code. All the functionalities are still same but now with addition of additionalArguments there will be no further need of enhancements through separate input for each of new request.

@t-dedah , would it be possible to update the main README to mention that what-if can be passed via additionalArguments?  I'm finding that users are not aware of this feature.

Hi @larryclaman sorry for the delay. Will this be enough or should we add more details?
PR - https://github.com/Azure/arm-deploy/pull/102


Fix typo: s/kwrags/kwargs

Codecov Report

Merging #73 into master will not change coverage.
The diff coverage is 100%.

@@         Coverage Diff          @@
##           master   #73   +/-   ##
====================================
  Coverage      96%   96%
====================================
  Files          21    21
  Lines         450   450
====================================
  Hits          432   432
  Misses         18    18

Impacted Files
Coverage Δ

django_fsm_log/backends.py
70% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


New package: StateSpaceAnalysis v0.1.0

Registering package: StateSpaceAnalysis
Repository: https://github.com/harrisonritz/StateSpaceAnalysis.jl
Created by: @harrisonritz
Version: v0.1.0
Commit: 136c0b99e98025884132039a9ff2ff8fa4a682d7
Reviewed by: @harrisonritz
Reference: https://github.com/harrisonritz/StateSpaceAnalysis.jl/issues/2#issuecomment-2518728177
Description: Alpha version of StateSpaceAnalysis.jl

Hi @harrisonritz, congrats on the new package! Can I ask why the existing options in Julia were not sufficient for your purposes? I know of several projects with similar scopes

Hi @harrisonritz, congrats on the new package! Can I ask why the existing options in Julia were not sufficient for your purposes? I know of several projects with similar scopes

Hi @gdalle! The goal of StateSpaceAnalysis.jl is to create a method thats optimized for neuroimaging analysis. While there are some good general-purpose packages (e.g., ControlSystemsAnalysis.jl or StateSpace.jl), my package is tailored for a couple of key needs for the neuroimaging community:

event-related structure of Neuroimaging data. EEG/MEG often has batched sequences (e.g., states x timesteps x trials). We are custom-built for that case by (A) including spline bases for inputs and (B) re-using the filtered/smoothed covariance across batches to massive reduce compute time.

high-dimensional systems. We are designed around scaling through efficient memory allocation, robust covariance handling (via PDMats.jl), and regularization. This has allowed this packaged to work well for high-dimensional state space models (e.g., factor dim > observation dim).

lack of domain knowledge. Because using SSMs for task-based neuroimaging is relatively new, it is difficult to provide good initializations for state space models. My packages includes modified SSID functions from ControlSystemsAnalysis.jl (appropriately credited and consistent with their license -- incredibly grateful!). By use SSID, we get really good initializations, which are critical for high-dimensional SSMs.

To further improve the ability for this package to benefit the neuroimaging community, my roadmap includes building out support for:

interfacing with a popular neuroimaging package via PyMNE.jl, which in the short term will allow easier importing of standard neuroimaging formats
building out methods for source reconstruction (localizing activity in the brain using SSMs).

This is my first Julia package, so I'm eager for suggestions & PRs. It accompanies a recent paper that uses this method in EEG. I have several research groups interested in utilizing this method for their own reserach. Since Julia is new to many in the neuroimaging community, I'm hoping that a tailored package will encourage uptake & Julia adoption.
Right now, I have to fix the compat to resubmit, and I'm going to tidy up the readme a bit.

Hi @gdalle, I have revised the readme to better reflect the targeted use-case of this package.

[noblock] My uneducated 2 cents: If this is tailored for neuroimaging, wouldn't you want "NeuroImaging" in the name?

[noblock] hi @briochemc -- thats a good question!
I considered NeuralStateSpace at some point (NeSS; smash bros mascot), but I didn't want to cast it too narrow either, as psychology/neuroscience is a big tent. For example, the features that make it useful for neuroscience would also be helpful in other domains, such as physiological modeling (e.g., eye-tracking, skin response, pupil dilation, facial reactions) or behavioral modeling (e.g., body movement, emotional changes, etc). In my field, some people can also be touchy about calling things 'neural' when you're getting indirect measurements from EEG/MEG/fMRI (🙄).

[noblock]
Sounds good to me! But next time be sure to register your Julia package (and thus get this kind of community feedback) before you mention its name in a paper 😉

[noblock] ha! Yes, fair enough. Assumed I'd just host a repo before I started reading into the package development process.


Add support for a hosted mode deployment

This syncs the upstream PR:
https://github.com/open-cluster-management-io/governance-policy-addon-controller/pull/15
Relates:
https://github.com/stolostron/backlog/issues/24362
Closes:
#70

@mprahl are you planning to address the changes for the cert and iam controllers in a separate PR? I wouldn't mind if they got added here, but if you prefer to keep things clean and separate that's fine too

@mprahl are you planning to address the changes for the cert and iam controllers in a separate PR? I wouldn't mind if they got added here, but if you prefer to keep things clean and separate that's fine too

As part of the epic scoping, we decided that the Cert and IAM controllers wouldn't be supported in hosted mode for now.


Draft to add Codemeta terms

See namespace considerations in #275 before merging.

Not sure if we should add this for 1.2 when we don't have a corresponding section explaining when to use embargoEndDate etc.  Suggest to delay this for 2.0.

@dgarijo  to double-check the PIDs

I added a few comments @stain. In Codemeta we resolved the resolution and content negotiation of w3id.org/codemeta, but at this time, the id is still  https://codemeta.github.io/terms/. I followed with another comment to see if we can push forward changing the id of the vocabulary. That may lead to incompatibility changes, so I am not sure how reluctant will people be.
I suggest using for now the current Codemeta id, even if it's not machine readable

It's OK, better remain compatible for now and use codemeta.github.io namespace.
I can add the machine readable definitions to our core Profile Crate for 1.2-DRAFT, but we would need to add also human-readable text to explain also why these URLs are 404 Not Found.

As shown in https://github.com/codemeta/codemeta/discussions/360 my proposal is to move it to https://w3id.org/codemeta/terms/
It would be great if you drop a +1 to show your support to this change

Hopefully by June 20th we'll get it solved. But community standards are slow sometimes.

I've added machine readable version in https://github.com/ResearchObject/ro-crate/blob/codemeta/docs/1.2-DRAFT/ro-crate-metadata.json#L736 , which you are free to adapt/correct. Unsure about if domainIncludes should always be SoftwareApplication

I will review when time allows. Thanks!

Ideally from https://www.researchobject.org/ro-crate/specification/1.2-DRAFT/appendix/jsonld.html#extending-ro-crate we should have a sameAs link for these term so that RO-Crate previewer has something to link to instead of the 404 Not Found pages https://codemeta.github.io/terms/developmentStatus
However, while each term is defined on https://codemeta.github.io/terms/ textually, there are no HTML anchors there, so https://codemeta.github.io/terms/#developmentStatus for instance would not help much and would still have that dangerous github.io in its non-persistent URL:.
And we can't have multiple DefinedTerm entities  with the same "sameAs": "https://codemeta.github.io/terms/"  as that would semantically link them all together to the same term.
@dgarijo  Could we use the https://w3id.org/codemeta# prefix in sameAs?
   {
    "@id": "https://codemeta.github.io/terms/developmentStatus",
    "@type": ["DefinedTerm", "rdf:Property"],
    "name": "developmentStatus",
    "termCode": "developmentStatus",
    "description": "Description of development status, e.g. Active, inactive, suspended. See repostatus.org",
    "domainIncludes": {"@id": "http://schema.org/SoftwareSourceCode"},
    "rangeIncludes": {"@id": "http://schema.org/Text"}
    "sameAs": "https://w3id.org/codemeta#developmentStatus"
    }

While https://w3id.org/codemeta#developmentStatus does resolve to a HTML page you still have to scroll down and look for "developmentStatus" but at least it's a persistent URL for each term, and also in the promised namespace-to-come.
Related question is if sameAs should rather be as an object reference  to match with schema.org JSON-LD mapping as an object property:
"sameAs": { "@id": "https://w3id.org/codemeta#developmentStatus" }

@dgarijo  could you also check if I got the domainIncludes and rangeIncludes correct? https://github.com/ResearchObject/ro-crate/pull/276/files#diff-391353380a9c2b594e12f6735db992305846175ab2c59389fc314ee9c5aafa37R767

I got it wrong above, I see https://github.com/codemeta/codemeta/discussions/360#discussioncomment-9519453 suggests https://w3id.org/codemeta/terms/ as namespace, so I've added that, e.g.
{
    "@id": "https://codemeta.github.io/terms/buildInstructions",
    "@type": ["DefinedTerm", "rdf:Property"],
    "sameAs": "https://w3id.org/codemeta/terms/buildInstructions"
}

@dgarijo Can you confirm I got this right now..?

Will complete a review by the end of the week.


Historical Elo Endpoint

Resolves #371 :rocket:

Looking for some input (am I even on the right track??)

Fixed!

Need new review after making changes per @j-mao request :rocket:


vscode.authentication.onDidChangeSessions does not fire for new sessions (1.80 regression?)

Type: Bug
(Note: this could be an API misunderstanding, but then if this is working as expected I'm not sure how to achieve the results I want)
I have a waitForSignIn method that looks something like:
public async waitForSignIn(): Promise<void> {
    if (await this.isSignedIn()) {
        return Promise.resolve();
    }

    return new Promise<void>((resolve) => {
        const disposable = vscode.authentication.onDidChangeSessions(async (event) => {
            if (event.provider.id === 'microsoft' && await this.isSignedIn()) {
                disposable.dispose();
                resolve();
            }
        });
    });
}

After calling waitForSignIn when not signed in, I would expect this method to resolve after, well, signing in.
However, after signing in, what actually happens is...nothing. I have a breakpoint set on the if (event.provider.id === 'microsoft') { line and it never gets hit.
Elsewhere in the codebase, there's another onDidChangeSessions listener, and as far as I can tell, it only gets called when I completely log out of a provider (at which point the listener is called twice as many times as the number of extensions that were using the provider).

Here's my test extension:
import * as vscode from 'vscode';
async function isSignedIn() {
	return !!(await vscode.authentication.getSession('microsoft', ['Mail.ReadWrite']));
}

async function waitForSignIn(): Promise<void> {
	if (await isSignedIn()) {
		return Promise.resolve();
	}

	return new Promise<void>((resolve) => {
		const disposable = vscode.authentication.onDidChangeSessions(async (event) => {
			if (event.provider.id === 'microsoft' && await isSignedIn()) {
				disposable.dispose();
				resolve();
			}
		});
	});
}
export async function activate(context: vscode.ExtensionContext) {
	context.subscriptions.push(vscode.commands.registerCommand('open.helloWorld', async () => {
		await waitForSignIn();
	}));
}

With this, I was not able to reproduce the issue. Can you provide a minimum repro for me?

Hmm, you're right. I'll need to investigate this more and see why I'm seeing something different in our extension.

I'll go ahead and close this for now, but feel free to open a new issue (or reopen) if you get to the bottom of it and it's my fault 😅

@TylerLeonhardt here's a recording that repros the bug using the exact same code you are, on a remote SSH session.
The event callback only fires after I switch windows back to the host.
https://github.com/microsoft/vscode/assets/2766036/3338ca11-6a60-4152-83f5-7850c968882e

@50Wliu this may be silly, but can you try again in today's insiders? I fixed something that could be related...

I'll get back to you after https://github.com/microsoft/vscode-remote-release/issues/8708 😋

@TylerLeonhardt Hi. We experienced the same problem with our company's plugin:
vscode.authentication.onDidChangeSessions() was not triggered after login/logout.
It seems to be solved in the insider version.
Do you plan to release an update for the fix? Thanks!

@eran-swimm we just released 1.80.1. Can you try that stable version and see if it's fixed there?

@eran-swimm we just released 1.80.1. Can you try that stable version and see if it's fixed there?

@TylerLeonhardt Fixed. Thanks!

Cool! I'll close this then

Darn, I was just writing up a comment about how this wasn't fixed :(. Let me verify again to be extra-sure, but I still seem to be hitting this on
Version: 1.81.0-insider (user setup)
Commit: 4390ebc406732e5b4eed22a1d7aa4fc0ef4a9460
Date: 2023-07-18T05:36:41.526Z
Electron: 22.3.14
ElectronBuildId: 21893604
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.25907

@50Wliu much like that other issue of yours, I'm curious if:

this works for you on another machine
this works if you're not using a Remote SSH connection

This will be good info to go off of

This issue does repro for me on other machines. But bizarrely, I do need to be in a remote SSH session (or at least, it works locally).
Version: 1.81.0-insider (user setup)
Commit: 9800cf6dd6bf4634889d60720ef46a400f3a7298
Date: 2023-07-28T12:08:04.472Z
Electron: 22.3.18
ElectronBuildId: 22689846
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.25918

Ok I just tried this in a dev container and can repro the issue! Thanks! Let me see what's going on here...


Improve portability of application development using containers

This needs to be defined better. A couple distinct use cases come to mind:

Developer environments.
Containerization of microservices and CI/CD.


Zero byte files being downloaded and back of scans missing since early February

I'm on a macOS Sierra 10.12.4 machine running Java 1.8.0_131, and as of early February, I'm seeing lots of zero byte files across two of my mailboxes.

All but one of the zero byte files ends in -3. And the IDs that are zero bytes are also missing the -2 files (the back of the envelope). When I run BulkScanDownloader, I get this in the logs.
18:41:47.692 [main] INFO - Starting BulkScanDownloader
18:41:47.952 [main] INFO - Starting fetch iteration.
18:41:50.683 [main] INFO - File processing started: /path/to/XXXXXXXXXXXX-0.JPG
18:41:51.098 [main] ERROR - Unable save item to disk:
18:41:51.099 [main] ERROR - Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index (Guid: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)

I'm not seeing any more zero-byte files, so the issue seems to have been resolved itself.


npx @backstage/create-app doesn't work for node 17+

When running  npx @backstage/create-app
then the process terminates with an error.
  executing     yarn install ◝ error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "14 || 16". Got "17.3.0"

Feature Suggestion
Ideally this should support the latest stable version of node. In my case my node version is as below.
 -> % npx node --version
v17.3.0

So we don't support 17, we support LTS versions which is 16 and 14. You can however proceed with 17 if you wish by using --ignore-engines as an yarn install command after, but we'd recommend using one of the LTS versions instead as there could be dragons with 17.


Remove climate setting schedules from fake-seam-connect

Need to get the fake API closer to the current API. We don't need to implement any new thermostat APIs here yet, but we should remove any that no longer match the Seam API.

We should also remove

https://github.com/seamapi/fake-seam-connect/blob/main/src/pages/api/thermostats/update.ts
https://github.com/seamapi/fake-seam-connect/blob/main/src/pages/api/thermostats/get.ts


'OStorageException: File with id 155 does not exist' during Index rebuilding

Creating this issue as per the comment by @laa in https://groups.google.com/forum/#!topic/orient-database/NqijZy-IUz0
OrientDB version : 2.0-M3
Our application was killed (kill -9) due to OutOfMemory. When we start next time, index rebuilding started. After some time, this Exception has come....
Will it impact in 'not creating the index'???
i.e., the application will be able to retrieve the data from the index.... right?????
Pls clarify
`
2014-12-12 17:40:27:756 INFO  Index POR_MSP1_1.key was successfully created and rebuild is going to be started. [OIndexManagerShared$RecreateIndexesTask]
2014-12-12 17:40:27:767 INFO  - Rebuilding index rcainv.POR_MSP1_1.key (estimated 539210 items)... [OIndexRebuildOutputListener]
2014-12-12 17:40:37:768 INFO  --> 56.75% progress, 306,014 indexed so far (30,601 items/sec) [OIndexRebuildOutputListener]
2014-12-12 17:40:46:355 INFO  --> OK, indexed 539,210 items in 18,588 ms [OIndexRebuildOutputListener]
2014-12-12 17:40:46:985 INFO  Rebuild of POR_MSP1_1.key index was successfully finished. [OIndexManagerShared$RecreateIndexesTask]
2014-12-12 17:40:46:986 INFO  Start creation of index CIRCUIT.key [OIndexManagerShared$RecreateIndexesTask]Error during addition of index {type:UNIQUE_HASH_INDEX,name:CIRCUIT.key,indexDefi
nition:{className:CIRCUIT,field:key,keyType:STRING,collate:default,nullValuesIgnored:true},indexDefinitionClass:com.orientechnologies.orient.core.index.OPropertyIndexDefinition,clusters:[1
],mapRid:#1:35,algorithm:SBTREE,valueContainerAlgorithm:NONE}
com.orientechnologies.orient.core.exception.OStorageException: File with id 155 does not exist.
at com.orientechnologies.orient.core.index.hashindex.local.cache.OWOWCache.openFile(OWOWCache.java:313)
at com.orientechnologies.orient.core.index.hashindex.local.cache.OReadWriteDiskCache.openFile(OReadWriteDiskCache.java:164)
at com.orientechnologies.orient.core.index.hashindex.local.OLocalHashTable.deleteWithoutLoad(OLocalHashTable.java:720)
at com.orientechnologies.orient.core.index.engine.OHashTableIndexEngine.deleteWithoutLoad(OHashTableIndexEngine.java:115)
at com.orientechnologies.orient.core.index.OIndexAbstract.deleteWithoutIndexLoad(OIndexAbstract.java:495)
at com.orientechnologies.orient.core.index.OIndexManagerShared$RecreateIndexesTask.createAutomaticIndex(OIndexManagerShared.java:500)
at com.orientechnologies.orient.core.index.OIndexManagerShared$RecreateIndexesTask.recreateIndex(OIndexManagerShared.java:486)
at com.orientechnologies.orient.core.index.OIndexManagerShared$RecreateIndexesTask.recreateIndexes(OIndexManagerShared.java:460)
at com.orientechnologies.orient.core.index.OIndexManagerShared$RecreateIndexesTask.run(OIndexManagerShared.java:449)
at java.lang.Thread.run(Thread.java:745)
2014-12-12 17:40:47:001 INFO  Start creation of index POR_TLWITHCTP.key [OIndexManagerShared$RecreateIndexesTask]
2014-12-12 17:40:47:413 INFO  Index POR_TLWITHCTP.key was successfully created and rebuild is going to be started. [OIndexManagerShared$RecreateIndexesTask]
`

Close it because it is not reporducable, but feel free to reopen it.


Create a "Base distribution" for an out-of-the-box CLAW

I think this was the idea all along, (and maybe this is redundant because there's an other issue?) but to have a set of "stuff" (modules? features? Maybe a Drupal installation profile?) that can let CLAW function out of the box, possibly including:

commonly used content types (images, audio, video, book, pdf...)
common RDF-mapped metadata fields ("forms" including the basic metadata fields that have been present in existing forms)
a set of derivatives that let us build a web-friendly display and navigation (thumbnails and display proxies)
viewers for those display proxies
a nice theme for presenting objects and their metadata, and navigation (collection?)
a default setup of solr so that search is snazzy

Whereas the "functionality" to have these is going to be built into CLAW core, there was always an intention to keep core lean. Would these types of 'defaults' be better in a set of 'starter modules' or features, rather than having the defaults (which are totally editable if you don't want to use them) baked into core?
Please discuss!

I was exploring setting up Apache Solr search and facets.  I've complied some notes here: https://github.com/Natkeeran/Notes/blob/master/Configuring Apache Solr Search and Facets in CLAW.md

@Natkeeran++ just looking that at that, thanks. Any problems/missing things?

@DiegoPino
The current default Apache core (CLAW) does not seem to have the needed configurations.  I've copied the configurations provided in the Solr Search module.
Both of the modules are not covered by drupal security advisory policy. Not sure how big of an issue that would be!  We are in the early stages of prototyping, thus have not explored the indexing and facets in detail.  Overall, seems to be a workable solution.

The original issues in the ticket are somewhat completed, and there remain new issues related to default builds for Islandora. Every method has different things. Coming up with a standard default remains an issue. We need to rewrite this use case.

I did a brain dump, and above are the use cases I've encountered.
Anyone want to discuss these?

Added the first one to the working spreadsheet of use cases - thanks @rosiel !


🚧 lint on commit

ht @kkukelka screenshot
PR type

[x] Bugfix

What's new?

[x] remove json file from lint rules

Related #1861


Rendering bug on app start in zen mode

VSCode Version: 1.32-1.33
OS Version: macOS 10.14.4

Steps to Reproduce:

Set app to restore to zen mode if it was exited in zen mode
Open file explore and/or terminal
Reload vscode
Observe previously opened file explore and/or terminal are not rendered but empty panels are shown instead.

Does this issue occur when all extensions are disabled?: Yes

Does this issue occur in latest insiders build?: Yes

@ivanvoznyakovsky great find and nice steps.
I first thought this is a candidate issue, however the previous stable we already shipped with this and nodoby noticed. So it seems like zenmode.restore is not such a popular option.
I have pushed a fix, so if you are reallying on this behavior please start using insiders. Thanks!

great. thnx for a quick fix 👍

@isidorn On reload/restart file explorer is not retrieved? Is it expected?

No, that is an issue. I filled it here -> https://github.com/microsoft/vscode/issues/73408


Error Parsing Erlang Version

The returned value using Erlang is shown below, perhaps the result has changed with newer Erlang version

Also might be good to surround the third commands (get version, halt) with single quotes.

Fixed with new release v1.5.0 of this project


Add Gitlab Release tagging and badge to Gitlab Java template

Can likely do something like the below.
gitlab_release_traceability_job:
  stage: deploy
  image: registry.gitlab.com/gitlab-org/release-cli:latest
  rules:
    - if: $CI_COMMIT_TAG                 # Run this job when a tag is created
  script:
    - echo "running release_job"
  release:                               # See https://docs.gitlab.com/ee/ci/yaml/#release for available properties
    tag_name: '$CI_COMMIT_TAG'
    description: '$CI_COMMIT_TAG'


Add @ExtensionPoint and @PublicApi annotations.

This is an attempt to clarify questions about what is and is not a public API (see https://github.com/druid-io/druid/pull/4131#discussion_r108780846, https://github.com/druid-io/druid/pull/4394#discussion_r123125180, https://github.com/druid-io/druid/pull/4254#discussion_r121013256). It adds two new annotations: @ExtensionPoint which signifies something you can subclass, and @PublicApi which signifies something you're not meant to subclass, but that you can use for implementation. The idea is that if an extension author sticks to public APIs then their extension will keep working for at least an entire major Druid line.
Extension authors are of course free to use non-public APIs, but their extensions might break randomly.
Feedback on the specific list of annotated and non-annotated items is welcome.
Some notes:

The list of public apis is somewhat subjective, but I did my best guess based on the current contents of http://druid.io/docs/latest/development/modules.html and based on recent discussions about what is and isn't public. In general I erred on the side of annotating fewer rather than more entities, since I figured that annotating too many entities would make too much friction for dev of core Druid.
Speaking of subjectivity: relating to the last comment in the list above (https://github.com/druid-io/druid/pull/4254#discussion_r121013256) I actually think CSVParseSpec shouldn't be considered a public api, since it's not really useful for extensions. So, I didn't annotate it. Tranquility does use it, but Tranquility really blatantly uses a ton of private Druid APIs. It should really have no expectation of being able to run with any Druid release other than the one it was built with.
Nothing in java-util is annotated since the annotations are in druid-api, and java-util doesn't depend on druid-api. We could deal with this by either saying "everything in java-util is public", or alternatively, creating a new package druid-annotations that java-util and druid-api both depend on.
I'm not sure I got the annotations for the query metrics stuff right (see #3954). @leventov could you double check if I captured your intent? What I did was annotate GenericQueryMetricsFactory as public (since AFAIK any extension query would need to call methods on it) but nothing else in the query metrics world.

Is druid-api module still needed?

Maybe not. The purpose was to put everything that was a public API in one package, but it turns out that there are public APIs in other packages too.

I cleaned up the wording a bit, to clarify that PublicApis can have new non-default methods added to an interface and this is not considered a breakage (because they are not meant to be subclassed).

👍

Pushed a new commit to resolve conflicts and address https://github.com/druid-io/druid/pull/4433#discussion_r125367680.

Thanks for your reviews @fjy and @leventov. I'd like to get a few more eyes on this just to see what other people think. Let's keep it open for a bit and bring it up in a dev sync too.

@gianm I have heard from @cheddar before that the json is the api spec rather than the java code itself per-se. Since there is a mix of things which feed into jackson and things which don't feed into jackson that have the same annotation, would it make sense to have a special annotation for things which are part of the JSON api, rather than the Java api?

@drcrallen,

@gianm I have heard from @cheddar before that the json is the api spec rather than the java code itself per-se. Since there is a mix of things which feed into jackson and things which don't feed into jackson that have the same annotation, would it make sense to have a special annotation for things which are part of the JSON api, rather than the Java api?

For this I think the attitude has been (and can continue to be) that a JSON API is stable if, and only if, it is documented. So I don't think an annotation is necessary.

It was brought up on the dev sync that it would be desirable to merge java-util into druid-common, which would solve the problem of "java-util can't see the annotations". That would be a big patch though and I think I'd like to do this patch first, for everything other than java-util. And then do another one for merging in java-util to druid-common.

@gianm is Task interface not marked as extension point consciously or just missed ? I know at least one user who have written their own task.
We should also mark LookupExtractorFactory and LookupExtractor as extension points. I know of multiple QTL extensions which extend those.

@gianm ServletFilterHolder too should be extension point.

@gianm is Task interface not marked as extension point consciously or just missed ? I know at least one user who have written their own task.

I consciously didn't add Task because it's not listed on http://druid.io/docs/latest/development/modules.html. And with this PR, I was more trying to encode existing policy in annotations, rather than change the policy. That being said, I would +1 a proposal to make Task an extension point.

We should also mark LookupExtractorFactory and LookupExtractor as extension points. I know of multiple QTL extensions which extend those.

Similar to Task, I left it out since it's not on http://druid.io/docs/latest/development/modules.html. In addition, Lookup APIs are explicitly described as "experimental" in the docs, so I think they shouldn't be annotated as stable. As long as they're experimental, users should be free to make extensions for lookups, but they shouldn't be guaranteed to keep working across upgrades.

@gianm ServletFilterHolder and PasswordProvider too should be extension points.

Hmm, ServletFilterHolder is kind of borderline (it's not on http://druid.io/docs/latest/development/modules.html) but it's close enough to "Jersey resources" (which is) that I guess it makes sense to add. I'll do that.
PasswordProvider isn't on http://druid.io/docs/latest/development/modules.html but maybe it should be. I'll leave the annotation out for now.

What do people think about adding these as extension points?

Task
PasswordProvider

They make sense to me but since they aren't currently on the modules.md list I wanted to check for opinions. If we generally think they make sense then I can add them to modules.md and annotate them.

@gianm @himanshug it makes sense to me.

@gianm PasswordProvider should definitely be an extension point, that was the primary reason for introducing it so that users can integrate Druid with their own internal secrets management systems effectively.
I don't feel so strongly about Task though, haven't seen a general need to extend it beyond one use case.

@gianm PasswordProvider should definitely be an extension point, that was the primary reason for introducing it so that users can integrate Druid with their own internal secrets management systems effectively.

I'll make PasswordProvider an extension point too.

I don't feel so strongly about Task though, haven't seen a general need to extend it beyond one use case.

I'll leave Task as "internal" for now, but if there is some consensus that it's a good idea to make it a formal extension point, then I'm ok with changing it.

@himanshug @jihoonson @leventov I made the adjustments discussed, and also updated the modules.md doc to reflect what has been annotated (as well as provided some more "hints" for implementors).

:+1:

There have been 3 approvals here, it should be good to go after conflicts are resolved.

Resolved conflicts.

@gianm feel free to merge whenever you want. it has enough approvals.

Ok, I'll merge it after CI is done.


redisContextConnectTcp is blocked in the poll

HI,
I am trying to redisClusterAsyncConnect  to connect to cluster. But looks like cluster context flags are ignored when we create redisContext and which leads to blocking connect. If route to destination exist then connect gets blocked forever.
cluster_update_route_by_addr
{
<>
if(cc->timeout){
c = redisConnectWithTimeout(ip, port, *cc->timeout);
}else{
c = redisConnect(ip, port);  <<< this is always blockig even if cc has blocking flag  reset.
}
<>
}

Please show your code about hiredis-vip.


[VS Code] Unable to connect to the remote server

Error:
Unable to connect to the remote server

Version Data

extensionName
VSLS

extensionVersion
0.2.405

protocolVersion
2.1

applicationName
VSCode

applicationVersion
1.22.2

platformName
Windows

platformVersion
6.1.7601

@marcorag Thanks for reporting the issue!  We could use a little more info to help you.
A few questions:

When did you get this error?  Joining a collaboration session?  Sharing?
Are you behind a proxy?
Could you send us your logs? You can get them by running "Live Share: Export Logs" and then either drag-and-dropping the zip here or emailing them to<EMAIL_ADDRESS>

@marcorag We were hitting some service issues earlier in the day. These issue should now be resolved (#235). I'd be interested to know if you are still hitting the issue you are reporting here now that it appears to be fixed. If you're still hitting issues, I'd love to see your logs.

thanks for quick reply. it's was a  problem of proxy now LiveShare work great

Great!!  Glad to hear it.  Looking forward to hearing any other feedback you have.


A confusion about mm_grounding_dino configuration file

In the mm_grounding_dino refcoco finetuning config file, I find an item:
'absolute_pos_embed': dict(decay_mult=0.)

But I don't find the model parameters related to the item. I don't know if the item is working. Can I delete it in the config file?

@jiangtann You can disregard it, as it was copied from Dino.


feat: support ESM file extension

fix https://github.com/themesberg/flowbite-vue/issues/86

Thanks


QKC/OP Devs Meeting #29 Agenda

Meeting Info

Dec 14, 2024, 10:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress

Goal:

SWC Testnet

Updates:

Devnet supports dac server https://github.com/ethstorage/optimism/pull/124
Discuss on scalar https://github.com/ethstorage/optimism/issues/93
Go through devnet and run a simple airdrop test based on web3.py

TODO:

https://github.com/ethstorage/pm/issues/149

Goal:

Prepare WSC L2 testnet launch

Updates:

https://github.com/ethstorage/optimism/pull/121
https://github.com/ethstorage/optimism/pull/122
https://github.com/ethstorage/optimism/pull/123
https://github.com/ethstorage/optimism/pull/116
https://github.com/ethstorage/optimism/pull/117
review:

https://github.com/ethstorage/optimism/pull/124
https://github.com/ethstorage/optimism/pull/119
https://github.com/ethstorage/optimism/pull/125

TODO:

https://github.com/ethstorage/optimism/issues/103
Prepare a tool to handle scalar: https://github.com/ethstorage/optimism/issues/93

Goal:

EthStorage Mainnet Ready

Updates:

CircleCI: Filled a ticket for the permission issue
Filled the EthStorage OP grant
EigenDA investigation: https://docs.google.com/presentation/d/1e2xeE7YdU58K28vSspdiFyBJbJEkrvxB65Z_kZgVdXo/edit?usp=sharing
Code reviews

TODO:

Follow up EigenDA's discussion
https://github.com/ethstorage/pm/issues/149

Goal:

SWC Testnet

Updates:

go through Devnet setup
address SWT e2e test issue

TODO:

https://github.com/ethstorage/optimism/issues/113

Goal:

circleci tests

Updates:

Fix https://github.com/ethstorage/optimism/issues/111

op-e2e-HTTP-tests: TestSoulGasToken/sgt_as_msg.value
op-e2e-fuzz, cannon-fuzz
op-e2e-fault-proof-tests, op-e2e-action-tests

Fix https://github.com/ethstorage/optimism/issues/112

gas-snapshot-check
lint
snapshots-check-no-build

TODO:

https://github.com/ethstorage/optimism/issues/112

check-generated-mocks-op-node
check-generated-mocks-op-service
cannon-go-lint-and-test
cannon-build-test-vectors
todo-issues
shellcheck/check


download from GitHub instead of TuxFamily

was recommended here: https://twitter.com/YuriSizov/status/1711097703323603242
would be nice to have this — i wonder if the download urls would be more normalized than the ones in tuxfamily, which would make it possible to add support for godot 3...will require further investigation

Good suggestion! I'm happy to take on this work.


page.waitFor can hold onto the process even when the browser closes/crashes

Tell us about your environment:
macOS 10.14.5

Puppeteer version: 1.20.0
Platform / OS version: Darwin
URLs (if applicable): N/A
Node.js version: 10.x

What steps will reproduce the problem?
If a browser (or the underlying socket) closes, any prior-invoked page.waitFor's continue to hang onto the process. Since these are using timers under-the-hood, Node won't exit and the process "hangs." Ideally, if the browser (or socket) closes then the entire process should probably close with it.
Here's how to repro:
const puppeteer = require('puppeteer');

(async () => {
    const host = await puppeteer.launch();
    const browserWSEndpoint = host.wsEndpoint();
    const client = await puppeteer.connect({ browserWSEndpoint });
    // Process wont return for 30 seconds
    (await client.newPage()).waitFor(30000);

    await host.process().kill('SIGKILL');
    console.log(`I should probably exit but don't!`);
})();

What is the expected result?
The process should exit, as it does with other page-level actions (goto and so on).
What happens instead?
Timers are still running, so the process hangs, which isn't ideal.

Unfortunately I think the only solution is to keep these timer ID's and clear them when the browser closes, which probably isn't a fun fix to implement.


SalesForce integration: is it possible to retrieve the details about the clicked phone number's Object (i.e. Opportunity) from the Widget?

Title has the question. I tried accessing the URL, but the focus changes to the Widget and the URL is different. I'm trying to log the call directly to the object that the number is attached to (i.e. Opportunity) Wondering if there are any workarounds for the scenario I'm trying to enable. Thanks.

Hi, @rederekt Now the Widget doesn't support to retrieve the Object data.
But I think you can flag the phone number with the Object in salesforce onClickToDial event opencti.onClickToDial in VisualForce page scripts. And when you get call log event from the widget, use phone number from the call info and the flag to retrieve Object.
Following show how to use salesfore ClickToDial with the Widget.


Generate line number information in class files

In stack traces, any code generated by Eta has (Unkown Source) listed as the line number since Eta doesn't generate any info right now. The information is available at the STG level via StgTick. This information should be used to generate the appropriate class file attributes that can be used to make debugging a whole lot easier.

I've outlined the steps to get this implemented below. This is what I feel is the most immediate approach to getting this feature in. There may be alternatives that you can choose to pursue based on your style of programming.

Add functionality in codec-jvm for generating the LineNumberAttribute attribute.
a. In Codec.JVM.Attr, a new constructor for the Attr type should be added, probably something along the lines of ALineNumber [(Offset, LineNumber)] where LineNumber can be a newtype or a type synonym.
b. Update attrName to handle the new case.
c. Update putAttrBody to handle the new case.

Add functionality in codec-jvm for generating the SourceFileAttribute attribute.
a. In Codec.JVM.Attr, a new constructor for the Attr type should be added, probably something along the lines of ASourceFile Text.
b. Update attrName to handle the new case.
c. Update putAttrBody to handle the new case.
d. Update unpackAttr to handle the new case.
i. This is required since SourceFile references a constant in the constant pool for the name.

In codec-jvm, provide APIs to add attributes for methods.
a. Update Codec.JVM.ASM.MethodDef to store attributes.
b. Update Codec.JVM.ASM.mkMethodDef to handle the change in (a).
c. Add a new function addAttrsToMethodDef which will allow you to update an existing MethodDef and add new attributes to it.
d. Update Codec.JVM.Method.MethodInfo to store attributes.
e. Update Codec.JVM.ASM.mkClassFile to convert between MethodDef and MethodInfo properly handling the new attributes-storing fields in each type.

In Codec.JVM.ASM.Code.Instr, add the facility to record line number info.
a. Augment InstrState with a field for storing line number information.
b. Add a new function getBCSL that is similar to getBCS which returns the line number information from (a).
c. Similarly, add a new function instrBCSL that uses the new function in (b).

In Codec.JVM.Attr, handle custom attributes in the binary serialization functions.
a. In toAttrs, use the new function from 4 (c) and make sure that the LineNumberAttribute attribute is placed in the list of attributes to generate for the method, not for the Code attribute.

In Codec.JVM.ASM.Code, add combinators for modifying the state of the Instr monad.
a. Define emitLineInfo :: LineNumber -> Code.

Familiarize yourself with the data types involved in this feature.
a. The basic abstract syntax tree (AST) for STG code in ETA.StgSyn.StgSyn defined via the GenStgExpr data type, with special attention to StgTick.
b. The Tickish type defined in ETA.Core.CoreSyn, with special attention to SourceNote.
c. The RealSrcSpan data type in ETA.BasicTypes.SrcLoc.

Update the CodeGen monad in ETA.CodeGen.Monad to store relevant information needed for generating the attributes above.
a. The information for the SourceFile can be obtained from the ETA.BasicTypes.Module.Module datatype which can be retrieved from the ETA.Main.DynFlags.DynFlags data type.
b. Update withMethod to modify the methodDef before returning by reading the CgEnv or CgState and generating attribute information from it.
i. Make sure to add on the SourceFile attribute using the function from 3 (c).
ii. The module remains constant for a single invocation of the code generator so the SourceFile information will remain the same across calls to withMethod.

Deal with the StgTick case in ETA.CodeGen.Expr.cgExpr.
a. Get a feel for how StgTick is generated by sending the -g -ddump-stg -ddump-cg-trace -ddump-to-file flag to the eta compiler (which turns on creating StgTicks for SourceNotes). Can be done with an etlas project by adding eta-options: -g -ddump-stg -ddump-cg-trace -ddump-to-file.
i. Inspect the generated *.dump-stg and *.dump-cg-trace files and look for the StgTick debug outputs to see how and when they're generating. Compare with the original source file.
ii. Determine whether -g should be turned on by default.
b. Process the Tickish component and only deal with the SourceNote case which provides information.
i. The RealSrcSpan you can extract from a SourceNote should give you a line number which you can add to the line number info using emit $ emitLineInfo ....

@rahulmutt I think that needs to be LineNumberTable attribute, instead of LineNumber attribute.

@puffnfresh Updated, thanks!

Hi. I'll try to implement this feature based on the description above.

Just wanted to point out that @Abhiroop and I implemented #3 in the outline above just yesterday in the process of implementing #298.

@ywata #298 is now merged into master and the required updates have been pushed to codec-jvm. Feel free to update your progress on this issue and let us know about anything that's blocking you.

@ywata @rahulmutt hi, i am trying to implement this one. I already have a inittial implementation of 1 and 2

@jneira Great start! I think 3 should already be implemented so you can proceed to 4 and beyond.

I have pushed what I have been able to do so far: https://github.com/jneira/codec-jvm/commit/0c236aea36814e8e4f80442e647f4a654643f3ad
I will not be able to continue it until after a few weeks

Awesome! Feel free to submit a PR to codec-jvm.

@jneira Will you be tackling the rest of this as well?

Hi @rahulmutt, sure i'll try to do it. BTW i have to do steps 5 and 6 fot finishing the codec-jvm part, started with this pr

Sure send another PR for that.

Hi @rahulmutt, i think the LineNumberAttribute shoud be generated for the Code Attribute. I tested to compile a java class with javac and with javap -v the LineNumberTable seems to be under Code and no under Method definition
Moreover, the spec  states:

The attributes defined by this specification as appearing in the attributes table of a method_info structure are the Code (§4.7.3), Exceptions (§4.7.5), Synthetic (§4.7.8), Signature (§4.7.9), Deprecated (§4.7.15), RuntimeVisibleAnnotations (§4.7.16), RuntimeInvisibleAnnotations (§4.7.17), RuntimeVisibleParameterAnnotations (§4.7.18), RuntimeInvisibleParameterAnnotations (§4.7.19), and AnnotationDefault (§4.7.20) attributes.

and

The only attributes defined by this specification as appearing in the attributes table of a Code attribute are the LineNumberTable (§4.7.12), LocalVariableTable (§4.7.13), LocalVariableTypeTable (§4.7.14), and StackMapTable (§4.7.4) attributes.

So unless you tell me otherwise i'll try to do it in this way

@jneira Apologise for that, you're right. Go ahead.

nvm, it could not been done (by me) it in a reasonable time without your detailed guide lines
now i'll try to do the really hard part in eta

It's not as hard as you think :) You're very close actually.
So as you debug, I strongly encourage you to run the ./tests/verify/verify.sh script after you do ./cleaninstall.sh with your changes. It will let you now whether the generated classfile is valid.
I took a look at this last week some time, here are some observations that might help:
Doing -g -ddump-stg -ddump-cg-trace -ddump-to-file in ghc-options: in the base.cabal file can give you some examples to look at. The files will be in dist/build/*. I'm taking a look at GHC/List.dump-cg-trace, I find this:
creating new closure...sat_sNKN
StgTick src<GHC/List.hs:986:38-56>
StgTick src<GHC/List.hs:986:47>
StgTick src<GHC/List.hs:986:52-53>
StgTick src<GHC/List.hs:986:55-56>
StgApp zipWith3 [z_sNK9, as_sNKF, bs_sNKI, cs_sNKL]

Notice that before any code is even reached in the STG AST, you encounter 4 consecutive StgTicks, all with different line number information. Those ticks give you information about the original functions before inlining which is useful for even better debugging information later, but for now you need to make a decision on which of those line numbers to choose. The first entry will be the outer most call and the last entry will be the innermost call. It'll probably help you to open up GHC.List source file and really follow the sequence above and you'll find out which line number will be the most relevant to the user upon an exception or space leak.
As far as I see it, you main work will be:

Extending the state in ETA.CodeGen.Monad to include some data structure to track consecutive StgTicks.
Extending the StgTick case in cgExpr to use the state in (1) to collect all consecutive StgTicks and just after the last consecutive tick, emit the line number into the bytecode - checkout the emit function in the CodeGen monad.

Hope this helps! You're almost there.

I complete the changes in codec-jvm with a method to add attributes when making a ClassFile, so we can add the sourceFile attribute in eta Codegen monad
https://github.com/rahulmutt/codec-jvm/pull/13

Maybe we could close this one, taking in account #494

Yes, we can - thanks for the reminder!


fix(recap.email): handle okeb short_description parsing

Related to #912

handle okeb short description parsing
add 2 test cases for okeb

Thanks!


General code quality fix-1

This pull request is focused on resolving occurrences of Sonar rules
squid:S2184 - Math operands should be cast before assignment.
squid:S1066 - Collapsible "if" statements should be merged.
You can find more information about the issue here:
https://dev.eclipse.org/sonar/rules/show/squid:S2184
https://dev.eclipse.org/sonar/rules/show/squid:S1066
Please let me know if you have any questions.
Faisal Hameed

Conflicts with the previous PR. Do you think you could fix this? Thanks!

@jastice Conflicts resolved.

Thanks!


Client Allocation Request for: 上海辰盟信息科技有限公司

Client Allocation Questions
Core Information

Name: 上海辰盟信息科技有限公司
Website / Social Media: https://www.chenmob.com/index.html
Region: Greater China
DataCap Requested: 5TiB
Addresses to be Notarized: f1fayarvpqi73lbbvxtgck53w5j346chk4kwz2jdq
Notary Requested: ozhtdong

Thanks for your application. I want to know more basic information of you and your company. Please answer following question:
1.What's your name? What's your position? Can you introduce yourself?
2.What's your company's business? Any other social media link? Please introduce your company.
3.Could you show me your company's business license?

Hi,ozhtdong
1.What's your name? What's your position? Can you introduce yourself?
Hello, I’m Li Xiao as the CEO of Shanghai Chenmeng Information Technology Co., Ltd.
2.What's your company's business? Any other social media link? Please introduce your company.
Chenmeng Technology, founded in 2018, has helped many well-known companies achieve digital transformation and upgrading, including e-commerce business, new retail business, big data, social e-commerce business, etc.It  helps enterprises save the investment in IT R&D in the early stage of the business, and realize the start of informatization from "0 to 1".
3.Could you show me your company's business license?

Thanks for your quick reply and detailed information.
I have further more questions about data and storing.
1.What kind of data do you want to store and how much? Could you please send me some demos of your data?
2.Have you/your company ever used cloud? Which platform do you use? What's your usage volume and frequency?

Hi
1、What kind of data do you want to store and how much? Could you please send me some demos of your data?
Market analysis Data mainly,15TiB would be best,I will email to you later
2、Have you/your company ever used cloud? Which platform do you use? What's your usage volume and frequency?
Yes,Baidu cloud、 Tencent cloud、 Ali cloud ……,About 10 TiB/Month.

Hello this is ours Data Demos
在 2021-03-18 11:03:31，"ozhtdong" @.***> 写道：
Thanks for your quick reply and detailed information.
I have further more questions about data and storing.
1.What kind of data do you want to store and how much? Could you please send me some demos of your data?
2.Have you/your company ever used cloud? Which platform do you use? What's your usage volume and frequency?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
从网易126邮箱发来的超大附件
001 - 电商创新 [1 - 1].mp4 (42.32M, 2021年4月2日 13:05 到期)
在线预览 | 下载

Hi.
I also want to know more about your allocation strategy.
1.How many miners do you want to store your data to? How much data for each miner?
2. Will you record your allocation decision in public? Which platform will you use?
3. What method/tool will you use to inspect miners? Which aspect of miners will you inspect?
4. Have you ever allocated before? If yes, how did you do when you were questioned?

1.How many miners do you want to store your data to? How much data for each miner?
We're going to pick five miners,20% for each.
2.Will you record your allocation decision in public? Which platform will you use?
Yes,We'll post the results on Github.
3.What method/tool will you use to inspect miners? Which aspect of miners will you inspect?
We choose miners we know,They are closer to our data center.
4 .Have you ever allocated before? If yes, how did you do when you were questioned?
None.


Create GitHub action to automate CodeFlare operator release

Fixes https://github.com/project-codeflare/codeflare-operator/issues/137
Requires GH_TOKEN secret containing GitHub token with access to repo and workflow, to be able to push changes back to the community-operators-prod repository.

Once https://github.com/project-codeflare/codeflare-operator/pull/118 gets merged I will update the readme and mark this PR as ready.

@anishasthana thinking whether I should use CodeFlare bot directly in this PR or rather open a separate PR once this is merged, WDYT?


DEV: Pass on logging level from config to services' env

Scaler will pass on the logging level set in config.core.logging.log_level as an environment variable for services to read to set for their logger.
Related PR: https://github.com/CybercentreCanada/assemblyline-v4-service/pull/19

Should probably include the same changes in updater.


Add NacosConfigReceivedEvent log

What is the purpose of the change
When NacosConfigReceivedEvent occurs, the application logs nothing at all.
Brief changelog
Add NacosConfigReceivedEvent log

这个日志不是在nacos原生sdk的日志中已经有类似的了吗？


demo run error

2021-01-06 18:07:10.801 ERROR 19760 --- [enderExecutor_1] c.a.c.s.b.r.i.RocketMQMessageHandler     : RocketMQ Message hasn't been sent. Caused by No route info of this topic, test-topic
See http://rocketmq.apache.org/docs/faq/ for further details.
2021-01-06 18:07:10.803 ERROR 19760 --- [enderExecutor_2] c.a.c.s.b.r.i.RocketMQMessageHandler     : RocketMQ Message hasn't been sent. Caused by No route info of this topic, test-topic
See http://rocketmq.apache.org/docs/faq/ for further details.
2021-01-06 18:07:10.805 ERROR 19760 --- [enderExecutor_5] c.a.c.s.b.r.i.RocketMQMessageHandler     : RocketMQ Message hasn't been sent. Caused by No route info of this topic, test-topic
See http://rocketmq.apache.org/docs/faq/ for further details.
2021-01-06 18:07:10.805 ERROR 19760 --- [enderExecutor_4] c.a.c.s.b.r.i.RocketMQMessageHandler     : RocketMQ Message hasn't been sent. Caused by No route info of this topic, test-topic
See http://rocketmq.apache.org/docs/faq/ for further details.
2021-01-06 18:07:10.805 ERROR 19760 --- [enderExecutor_3] c.a.c.s.b.r.i.RocketMQMessageHandler     : RocketMQ Message hasn't been sent. Caused by No route info of this topic, test-topic
See http://rocketmq.apache.org/docs/faq/ for further details.

rocketmq-binder-send-receive-demo   运行不了

rocketmq-binder-send-receive-demo   运行不了

是不是阿里云买的rocketMQ 不能用这个demo？

是不是阿里云买的rocketMQ 不能用这个demo？


Unable to create ticket without setting all values of a ticket

You are not able to create a ticket without setting all (not all, but at least very much) values of the Ticket object.
E.g. you have to set the PriorityId, StateId, CreateArticleTypeId, CreateArticleSenderId, UpdatedById and CreatedById because the don't support null-values.
Same for the TicketArticle with the values SenderId, UpdatedById and CreatedById.
Please support Nullables for these values.

Do not the values really have to be set?

I have tested this. you are right!


fix: adjust training defaults for laptop

effective batch size should be 64 for knowledge on a laptop which is what we focus on primarily
max batch len is too high for most laptops to work with. 5000 is a realistic max batch len for 64 GB of RAM following full SDG

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Functional tests have been added, if necessary.
[ ] E2E Workflow tests have been added, if necessary.

@Mergifyio backport release-v0.19


Problem

Hello,
When I run the script, I get this error:

Do you have any ideas to help me ? I have the Eaton Network Card-M2.
Have a nice day :)

Seems that your web-interface has a different setup than the one that I used before.
I can't really help you with your problem, as you have to figure out yourself what the differences are.
It seems that you don't have the attribute realtime in the inputs['measures'].
You could try to remove the lines from the code that are causing issues and move on from there.

It's been almost a year and no further questions have been asked to keep this issue open, so I will close it now

I stumbled upon this today, I have 3 of the same UPS's with all the same network card.
2x of my UPS's are on Network Card Firmware 1.7.5 with one of them on 2.0.5 somehow, this error appears on my UPS with the 2.0.5 Firmware, suggesting Eaton changed something somewhat recently with the way input measures are called upon.
Unfortunately I'm not well versed enough to figure out what causes the issue, although it may be possible to upgrade your firmware to 2.0.5 and figure it out for yourself.
For anyone reading this, do not upgrade your Firmware if you wish to keep using this amazing exporter (:

I stumbled upon this today, I have 3 of the same UPS's with all the same network card.
2x of my UPS's are on Network Card Firmware 1.7.5 with one of them on 2.0.5 somehow, this error appears on my UPS with the 2.0.5 Firmware, suggesting Eaton changed something somewhat recently with the way input measures are called upon.
Unfortunately I'm not well versed enough to figure out what causes the issue, although it may be possible to upgrade your firmware to 2.0.5 and figure it out for yourself. There is also a 3.0 version firmware, seems they really did support this product decently!
For anyone reading this, do not upgrade your Firmware if you wish to keep using this amazing exporter, thanks for making it! (:

I have moved this to a new issue (#23)


merge ts-trace-viewer extension (WIP)

Still a work in progress as I can only get it to build without rollup, but I wanted you to get a preview of what's coming

Got it working with rollup

closing, in favor of soon to come nuxt version


update logic to wait for proxy connection to be established before ma…

updating sample pipeline to include OPSMAN_PRIVATE_KEY for backing up director.  In addition, updating "export-director-metadata" to have a 5 sec delay before executing a bbr command through the proxy. It was discovered that not having the delay can result in a connection refused error.

Thank you @sapient007


PHOENIX-4940 Add tenantId parameter to index tool

PhoenixMapReduceUtil.setTenantId(tenantId)

We pass the configuration (with tenantId set) to the jobs. This one sets MAPREDUCE_TenantID and when it is set, it overrides the configuration's tenantid with this value. I think we don't need to set it with this but to be safe, I will do it.

@gokceni - Looks like there needs to be a separate patch for the 4.x branches of Phoenix, which compile against HBase 1.2, 1.3 and 1.4.
There's a compilation failure with use of the Admin class in IndexToolIT. Could you please post an additional patch? (no need for separate review, can just post as an attachment on the original JIRA)


atan2 printed out without its arguments when using xpdf

Dear all,
I seem to have come across a printing issue.
The command xpdf generates a .tex file that does not entail the printing of the arguments of the inverse trig function atan2. When you cast an eye on the bit at fault in the .tex file, you can observe that the “\end{equation*}” arrives too soon, see zip file attached.
However, this phenomenon does not occur when using jupyter.
Look forward to hearing from you.
kind regards,
FB
atan2_issue.zip

The relevant tex snippet:
\pmb{\mbox{atan2 is printed out without its arguments!}}
\begin{equation*} atan2(u,v) = atan_{2} \end{equation*}
\begin{equation*} atan(u/v) = \arctan{\left (\frac{u}{v} \right )} \end{equation*}
\end{document}

What's also weird is the subscript for 2, probably this is a lead.
I've checked the code to specifically handle atan and atan2, they seem harmless.


Customizable tipsy

#6
Customizable Tipsy
Allow passing React element to be rendered by React Tipsy library. This solve the issue of implementing Custom styled react-tipsy using CSS modules instead of global CSS

In Mavenlink case we change the arrow based on context. Tispy-arrow can
be at any direction and can face up down left right.
On Thu, Oct 12, 2017, 4:57 PM Andrew<EMAIL_ADDRESS>wrote:

@ahuth commented on this pull request.
In src/Tipsy.js
https://github.com/dennisduong/react-tipsy/pull/7#discussion_r144430550:

@@ -11,6 +10,27 @@ import PropTypes from 'prop-types';

Like bootstrap's tooltip plugin, Tipsy does not rely on images.
*/

+class Container extends PureComponent {

render() {
return (

 <div className={`Tipsy in ${this.props.placement}`} role="tooltip" >

{this.props.children}

Are there cases where changing the content of the tipsy wouldn't be
enough? Unless I'm reading it wrong, it seems like we could use arbitrarily
complicated content there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dennisduong/react-tipsy/pull/7#discussion_r144430550,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAi4KUwCgOU5MqJp37mln6PHjoCd7rEOks5srplUgaJpZM4NSOgH
.


pitest PR actions take a long time

Summary
Pitest is executed to verify PR, the CI / pitest (pull_request)  pitest task seems to take forever, it's not clear if it's in the Receive or PR Update workflow.
Example
https://github.com/assertj/assertj-core/pull/2083/checks?check_run_id=2700985331 has started 14h 52m 7s ago and has not finished (at the time of this writing).
A pitest artefact  containing the pitest execution report is produced and is available at https://github.com/assertj/assertj-core/suites/2863716540/artifacts/63970905.

@hcoles can you help on this one?
I made 2 changes on https://github.com/assertj/assertj-core/blob/main/.github/workflows/pitest-updated-pr.yml from https://github.com/GroupCDG-Labs/pitest-github-demo/blob/main/.github/workflows/update-pr.yml:

use of pitest profile (-Ppitest)
bumped version of com.groupcdg:pitest-github-maven-plugin to 0.0.8 to be in sync with the pitest version used in the pom (https://github.com/assertj/assertj-core/blob/main/pom.xml#L37)

It's a bit confusing to investigate as I can't pinpoint which exact github action jobs/step is performed.
The Receive workflow job is completed as far as I can tell from https://github.com/assertj/assertj-core/pull/2083/checks?check_run_id=2700972002 but I fail to identify which step is taking so much time, I assume it's in pitest-update-pr even though there is no log showing pitest-update-pr has started.

A bit more insight, when comparing with https://github.com/GroupCDG-Labs/pitest-github-demo/ PRs, I see that the pitest phase that takes forever in assertj-core takes almost no time, ex: https://github.com/GroupCDG-Labs/pitest-github-demo/pull/7/checks?check_run_id=2546195806.
It shows the Pitest mutation testing feedback results whereas the one in assertj-core are stuck there.
https://github.com/GroupCDG-Labs/pitest-github-demo/pull/7/checks?check_run_id=2546195806

Hi Joel,
What I think is happening is that mutation testing is running successfully, but the job defined in https://github.com/assertj/assertj-core/blob/main/.github/workflows/pitest-updated-pr.yml is failing to complete.
This job is starting, creating a new checkrun called 'pitest', but is then unable to update its status so it appears to have been running for hours.
This is a known bug caused by a change to the github apis last week and these two issues
https://github.com/hub4j/github-api/issues/1156
https://github.com/hub4j/github-api/issues/1157
I'm hoping there will be a release of hub4j soon to fix this.
What I don't understand is why no error log is visible. I assume this is a peculiarity of the actions workflow_run trigger.

Thanks @hcoles for the explanation.

@joel-costigliola There is now a 0.0.9 release that should fix the issue if you update the pom and the version in the github workflow, sorry for the delay.

thanks @hcoles, I'll try it on the week end.

version bumped, let's see how it goes.

Looks good now: https://github.com/assertj/assertj-core/pull/2246#issuecomment-855236608
thanks again @hcoles


Flatten auto/config into auto

Follow up to https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/982#discussion_r1735402520
By moving the auto/config package into auto, all the non-user related types are unexported and removed from the public API.

+1 to @RonFed's comments around the duplication+complexity. I would also prefer to organize the external-facing code into packages than having it all at the root.
I don't personally think the separation between internal/external is a high priority at this stage of the project, but I do think that addressing it is something we need to do. These changes make that line a little unclear to me too.
Wydt about taking the time to inventory our code and map out what makes sense to be public vs private in the ideal long term?

I'm focused on ensuring that the user experience is prioritized here. Having an external API with unreachable types and functions or one that is bloated with unnecessary things is going to be a bad design with poor user experience. I'm also extremely hesitant to just add things to the API without justification and thought.
While we are at an early stage, with adoption, these APIs become de facto "stable".
I'm on-board for re-evaluating our approach. However, if we plan to do that we need to revert https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/982 and https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/1010 so we are doing so from a clean slate. Both of those PRs have added to the exported API and included elements mentioned above.

@MrAlias I think we want the same things, but it's not clear to me what that looks like. So, I can't tell if this PR works toward that or not (I'm not saying it doesn't, I mean that I can't objectively say based on a specific goal)
I think we can reevaluate the approach without reverting everything. I would just like to know what the ideal end state of the user facing API is. So, just a step back that could include moving forward with this change too.
I am totally for treating the APIs as de facto stable, because even ignoring the user experience it builds good code practices to do so. That said, the user experience can still suffer if the public frontend is difficult to maintain.
So I'm not disagreeing with you, and you've got a good example of a function that shouldn't be public. I'm saying let's look at every function and type, decide what they do, and design an API before we move forward trying to fix it. Do you think that's reasonable, or should we prioritize this patch right now?

Yeah, I agree we are both striving for the same thing. I see this as an incremental positive change, and one we can build from. It addresses the two main issues mentioned above:

Functionally related types and functions are unified into the same package.

The Sampler type used by the Instrumentation is in the same package
The ConfigProvider type used by the Instrumentation is in the same package

It removes functions exposing internal types.

I'm happy to keep iterating here. I have thoughts about how these types could be refactored as well.
However, I do not think the current state of the project can just be left as is. It is not in a state that should be considered for release:

https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/982 was merged with the expressed qualification that this type of refactor would be required afterwards: https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/982#discussion_r1742400937, https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/982#pullrequestreview-2283861134
https://github.com/open-telemetry/opentelemetry-go-instrumentation/pull/1010 was merged with a single approval from the same company as the PR author

Both of these changes introduced modifications to our public API without the communities buy-in to the change. If we want to not move forward iterating on these issues we need to roll them back and address their inclusion from a clean slate.

I think we agree that we need a longer term vision, but I also think we can unstick the current state to address the promises made in those PRs that we'd fix this.
So my two main concerns with this change are that 1) it seems somewhat over-flattened and 2) I don't understand why the duplication in internal/pkg/instrumentation/config.go and provider.go
For 1) I don't mind this being flattened, but if you're intending for that to be part of the long term design then I'd like to block and discuss it. Otherwise, that's totally fine with me to get things shaped up for now.
For 2), I could just be missing something so it would help if you can please explain that duplication
And just to get on the same page, do you mean for this PR to be part of the long term design or are you open to changes here as we work that out?

So my two main concerns with this change are that 1) it seems somewhat over-flattened [...]
For 1) I don't mind this being flattened, but if you're intending for that to be part of the long term design then I'd like to block and discuss it. Otherwise, that's totally fine with me to get things shaped up for now.

Can you expand on this? I don't see a case where a user would ever import go.opentelemetry.io/auto/config without importing go.opentelemetry.io/auto first. The go.opentelemetry.io/auto/config package is not a logically distinct collection of code. It is a part of go.opentelemetry.io/auto that seems to be broken off to support underlying developer complexity reduction.
FWIW, I am not opposed to adding additional package to go.opentelemetry.io/auto/. If there are logical distinct units and reusable code that will be used in multiple places it would make sense to add that code as its own package. This config package is demonstrably not that though.

I don't understand why the duplication in internal/pkg/instrumentation/config.go and provider.go

[...]
For 2), I could just be missing something so it would help if you can please explain that duplication

There is duplication because of the alternate representation of a Sampler externally vs internally. The internal provide uses the internal definition of a sampling.Config, where the external declaration uses the external auto.Sampler.
This is an area I think we could iterate on. Especially since we are going to need an way to allow users to pass custom Samplers and support the remote samplers (i.e. Jaeger, AWS).
This forcing function will likely result in the Sampler definition to be updated into something used in both places and will likely result in a new auto/sampling package. But this is very speculative and I haven't done more than thought about it.

I would like to merge this PR or revert the prior two. I see the current state of the repository in limbo without doing either.
I do not feel comfortable releasing what we have on main currently, which means we are blocked releasing all the existing changes we have merged.
I'm also not 100% sure I would want to release with this merged either. However, I see incremental changes that can be made on top of this that could get us to a release-able place.