Update to 9.5 as well as the new secrets for .6/.7 to work.

@jmccann I've upped the version to 9.5 for terraform as well as changed the secrets to be terraform_secrets because secrets is now used to decide what secrets get injected to the container and thus wouldn't work with the new versions of drone. It should still work with .5 as well if secrets is changed to terraform_secrets in the same way. Let me know if you need to to change anything or you see anything wrong

Is there a need for terraform plugin specific secrets? Why not use the standard drone's secrets management?

I need to investigate if this is still needed in Drone 0.6+.
In 0.5 plugins were hardcoded to specific secret names, so this was a way to be able to use different sets of secrets to multiple calls to same plugin in a single pipeline.
With Drone 0.6 and ability to specify secret target I'm not sure all this is still needed.

Yeah but that will limit how many secrets you can inject in, or you would need some kind of naming convention.

@josmo You're right, I forgot.  I think I still want to investigate dealing with secrets but will review this again tomorrow and probably merge.

@jmccann If you have a better way I'd love to know about it for other plugins I'm writing.  I was thinking about asking Brad if it would make sense to expose some kind of secrets_list as well as injecting the env variables for this kind of purpose, then you wouldn't need a dedicated terraform_secrets mapping type thing.

Sorry for stepping in again, but why current secrets management in 0.6 limit[s] how many secrets you can inject in? I'm just curious if there is something I don't know about those secrets in 0.6

It doesn't limit the number, but forces you to know the envs  keys ahead of time. Which is why theres still a need to map the values in a plugin like this. I haven't spent a ton of time thinking about it so there might be a simpler solution.

There isn't many env keys to use with terraform outside of the providers you're using or variables you want to pass to your tf configs. And those you should be familiar with if you're using them. AWS access keys, GCP key json, password, etc that terraforms picks up from the env?
That's why I'm a bit confused about special handling of secrets in the plugin itself, especially now that drone exports them to env exactly as they are named (without PLUGIN_ prefix). Plus, gives you an option to rename them on the fly. I'm always asking for a concrete use case before something gets worked on.
I'm not against this PR, I just want to understand if there is something I don't know about since we're trying to use drone with this plugin a lot more in the future.

@msuterski Brings up good points.
With ability to do https://www.terraform.io/docs/configuration/variables.html#environment-variables to have vars take in values from envvars and providers also looking for secrets from envvars (e.g. https://www.terraform.io/docs/providers/openstack/#configuration-reference can read from OS_USERNAME, OS_PASSWORD, etc) there isn't really a need to pass secrets to terraform cli via -var with secrets/terraform_secrets from what I can tell.
@josmo thoughts?

@edwinavalos Thoughts on above?

Again I could totally be confused :) but I'm thinking about when I need to pass a secret to a variable to set something like user data info with a template file. I'm not sure how else you would set the var the correct secret.

@josmo Maybe we posted at same time ... have you seen https://www.terraform.io/docs/configuration/variables.html#environment-variables for reading var values from envvars?

Oh actually didn't know you could do that. Sounds good to me :)

Yep posted at the same time, want me to update the pr?

@josmo Maybe create a new PR for the 0.9.5 update you want.  Thanks!

OS_USERNAME, OS_PASSWORD

I believe I ran into some wonkiness trying to get the secrets to work when I just had them defined as the ENV variables they should have been provided as, like the plugin just didn't see them at all. I could try and recreate if I get some time again.

I'll double check when I make the new PR but I think it's because the plugin uses the secret key word

@jmccann ok so an issue with this :/ if we're using the TF_VAR_input it looks like terraform cares about case. so when setting the target to be TF_VAR_input drone sends it in as TF_VAR_INPUT and then terraform doesn't see it. I get you could set all variables in tf to be uppercase but seems like having the ability to inject TF_VAR via secrets and the terraform secrets mapping both might be desirable in this case so people can have lower case variables. Let me know your thoughts

@josmo You should still be able to inject secrets via vars such as:
0.5:
pipeline:
  terraform:
    image: jmccann/drone-terraform:1
    plan: false
    vars:
      app_name: my-project
+     secret_var: ${MY_SECRET}

I think (not sure as I haven't used secrets yet in 0.6) you can do the following for 0.6+:
pipeline:
  terraform:
    image: jmccann/drone-terraform:1
    plan: false
    secrets: [ my_secret ]
    vars:
      app_name: my-project
+     secret_var: ${MY_SECRET}

I think in 0.6 secrets get injected as an envvar with their name.  I also think that 0.6 hijacks secrets key from drone-terraform so even though there are conflicts it should work?  Or at least if we remove secrets from plugin as discussed it should work?
I'm also considering adding code to plugin to search for all envvar that match TF_VAR_* and "copy" them to lowercase equiv (e.g. TF_VAR_SECRET -> TF_VAR_secret).
I'm still working on finishing my 0.6 env to start playing around with things in.  So let me know if I'm wrong on anything.

Secrets are no longer interpellated so the second option doesn't work.  Removing the terraform secrets does work :) the only caveat is the casing issue :/  with the current price you can select camel case, upper, lower and have it work. Again I'm down with whatever, it does seem to add a bit of complexity just for casing but I also know how much certain organizations have conniptions about it :)

Closing this in favor of #46


Sending a test event fails with ** (FunctionClauseError) no function clause matching in :proplists.get_value/3

Environment
What version are you running? 10.7.1
Steps to Reproduce

Configure prod
run MIX_ENV=prod mix sentry.send_test_event

Expected Result
Test event is sent.
Actual Result
An error is raised in the console.
Client configuration:
server: REDACTED/envelope/
public_key: REDACTED
secret_key:
current environment_name: "prod"
hackney_opts: [pool: :sentry_pool]

Sending test event...
** (FunctionClauseError) no function clause matching in :proplists.get_value/3

    The following arguments were given to :proplists.get_value/3:

        # 1
        "X-Sentry-Error"

        # 2
        %ArgumentError{message: "unknown registry: Req.Finch"}

        # 3
        nil

    (stdlib 6.0.1) proplists.erl:214: :proplists.get_value/3
    (sentry 10.7.1) lib/sentry/client.ex:386: Sentry.Client.maybe_log_send_result/2
    (sentry 10.7.1) lib/sentry/client.ex:251: Sentry.Client.encode_and_send/4
    (sentry 10.7.1) lib/sentry/client.ex:137: Sentry.Client.send_event/2
    (sentry 10.7.1) lib/mix/tasks/sentry.send_test_event.ex:88: Mix.Tasks.Sentry.SendTestEvent.send_event/1
    (mix 1.17.2) lib/mix/task.ex:495: anonymous fn/3 in Mix.Task.run_task/5
    (mix 1.17.2) lib/mix/cli.ex:96: Mix.CLI.run_task/2
    /Users/rlopez/.asdf/installs/elixir/1.17.2-otp-27/bin/mix:2: (file)

My config:
config :sentry,
  client: Gru.Sentry.HttpClient,
  release: System.get_env("APP_VERSION", "0.0.1"),
  dsn: "REDACTED",
  environment_name: config_env(),
  enable_source_code_context: true,
  root_source_code_paths: [File.cwd!()],
  report_deps: false,
  integrations: [
    oban: [
      # Capture errors:
      capture_errors: true,
      # Monitor cron jobs:
      cron: [enabled: true]
    ]
  ]

My HTTP client:
defmodule App.Sentry.HttpClient do
  @moduledoc """
  Sentry HTTPClient using Req
  """
  @behaviour Sentry.HTTPClient

  @impl Sentry.HTTPClient
  def post(url, request_headers, request_body) do
    request_headers = Map.new(request_headers)

    case Req.post(url, headers: request_headers, body: request_body) do
      {:ok, %Req.Response{status: status, headers: headers, body: body}} ->
        {:ok, status, headers, body}

      {:error, error} ->
        {:error, error}
    end
  end
end

@savhappy can you take a look at this?

@savhappy yeah I think we should prevent this kind of deep-within-the-lib errors when possible. In this case, I think we should not assume that we have well-formed headers in Sentry.Client.maybe_log_send_result/2 and instead check for that. Let's make sure to add a test for this regression too 🙃

Okay, so what's actually happening here is that an error exception is being returned. Which is great because it tells us exactly what's wrong (Req is returning a struct so the body isn't encoded, thus the Jason.decode fails). However, I only noticed this after I commented out the :proplists.get_value() function and let the entire error fall through.
I think we should allow this error exception through on the Sentry.Client.maybe_log_send_result/2 like it is in Sentry.Client.send_event/2.  This is in PR #789
%Sentry.ClientError{reason: :server_error, http_response: {:error, :badarg, [{:erlang, :iolist_to_binary, [%{"id" => "49fd6554bb7f491e8956324a8071802e"}], [error_info: %{module: :erl_erts_errors}]}, {Jason, :decode, 2, [file: ~c"lib/jason.ex", line: 69]}, {Sentry.Transport, :request, 4, [file: ~c"lib/sentry/transport.ex", line: 62]}, {Sentry.Transport, :post_envelope_with_retries, 5, [file: ~c"lib/sentry/transport.ex", line: 34]}, {Sentry.Client, :encode_and_send, 4, [file: ~c"lib/sentry/client.ex", line: 249]}, {Sentry.Client, :send_event, 2, [file: ~c"lib/sentry/client.ex", line: 137]}, {Mix.Tasks.Sentry.SendTestEvent, :send_event, 1, [file: ~c"lib/mix/tasks/sentry.send_test_event.ex", line: 88]}, {Mix.Task, :"-run_task/5-fun-3-", 3, [file: ~c"lib/mix/task.ex", line: 495]}]}}

@whatyouhide I'm making another PR to handle header validation because this issue might arise again for Req users.

This has been fixed in #794.


support react 0.14

reflux not support react 0.14

+1

+1

+1

React v.0.14 was announced two days ago: https://facebook.github.io/react/blog/2015/10/07/react-v0.14.html
So, this feature request is critical now. Has anyone tried to fork refluxjs and enable react v.0.14?

+1
It seems like refluxjs has not been updated for 2 months.

I think the main problem was the "new" path Facebook takes by embracing pure ES6 class. It breaks anything based on mixins, and reflux still has some feature based on mixins. However, I'm using reflux since a few weeks, and all my react code views are pure ES6 classes, I didn't see any blocking point so far.
Still, it's a big move, the doc should be changed, maybe some features are ONLY accessible via mixins etc

2 months no update basically means it's deserted. Will the maintainer add more maintainers, maybe?

+1
It's a blocking issue.

+10086

+1

+1


Add endpoint / field to inform about the locked wallet

On startup when auto-unlock is not enabled, the Lightning wallet is locked.
I would like to have an extra endpoint or a field in ln_info_lite to see if the wallet is locked.

I don't really want to add a field to ln_info_lite because you only can get this info when the wallet is unlocked.
Proposal:
All endpoints, while locked, will return http status 409 Conflict. Additionally, when establishing the SSE connection, clients will receive a new event type called wallet_status with one boolean field locked. This way there is no additional endpoint needed, just to see whether the wallet is locked or not.

The SSE event sounds awesome!
I'm not sure if the 409 conflict though. How about 423 Locked :)
& a question: What endpoints won't work when the wallet is locked? Am I able to receive on-chain transactions etc.?

See #34 for progress on this.


performance on mid-size projects

atom-typescript works like a charm when I start a new ts project. However, as soon as the number of files grows, performance issues start to creep in. Mainly:

autocompletion stops working
error reporting freezes (with visual cues pointing to what has already been corrected)
native atom snippets stop working too!!

Today I noticed that the notification at the bottom for "Pending Requests" can reach 1500+ at certain points. If I leave Atom for a few minutes and the "Pending requests" reach zero, the same issues persist.
I've always noticed this behaviour when working with ts files in Atom. I've just been trying to debug possible causes but with no success.
Is there anything I should be configuring in a different way?
Is this a limitation with atom and/or typescript?

"filesGlob": [
        "!node_modules/**"
    ],

This can help A BIT. Unfortunately, even though it reduced lag for me a lot, it still is not very useable on large projects. My project consist of around 270 .ts files and for a simple autocompletion after placing a dot I must wait like 2-3 seconds. It may seem not much, but today I've tried Visual Studio Code as alternative and it is so blazing fast (stil using same html technology)...

We're using atom-typescript on a fairly large project too and the performance is good, unless we ask it to autocomplete a module import. Then the pending requests shoot up in the low hundreds.
Can you describe your directory structure and paste your tsconfig.json files?

I've tried the glob that @nullptr128 suggests and I haven't noticed any difference. However, I've also followed his suggestion of using Visual Studio and I'm amazed about how fast typescript features are! Thanks for that!
At first, I thought that this was something to do with the limitations of using Electron, but Visual Studio Code is also an Electron app, so it must be something else.
I've counted all the ts files in the project and actually it's not that many. 160 (without counting node_modules). 2956 if I count node_modules too.
My folder structure is nothing out of the ordinary:
project_dir
   src
      app
      assets
      vendor
   ...
   tsconfig.json
   ...

My tsconfif file:
{
  "compilerOptions": {
    "target": "es5",
    "module": "es2015",
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "noFallthroughCasesInSwitch": true,
    "noImplicitAny": true,
    "suppressImplicitAnyIndexErrors": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "strictNullChecks": false,
    "removeComments": true,
    "sourceMap": true
  },
  "awesomeTypescriptLoaderOptions": {
    "forkChecker": true,
    "useBabel": false,
    "useWebpackText": true
  },
  "compileOnSave": false,
  "buildOnSave": false,
  "atom": {
    "rewriteTsconfig": true
  },
  "files": [
    "src/app/app.module.ts",
    "src/main.ts"
  ]
}


Does this reset the map to the center?

As the title says, does is this supposed to reset the map to the center as well as the zoom level?
From the example in the README, this is specified
center: [51.505, -0.09],

When pressing the world button, it doesn't appear to recenter on that point. Instead it zooms back out based on the current center point. Is this the expected behavior?

Yes, that's the expected behaviour.

Just append an ; on line 39: this._map.setZoom(this._map.getMinZoom())
And add a new line 40 with : this._map.panTo(new L.LatLng(55, 0)); //Or whatever center point, not sure how to get center point from the map object


Fix Organization List HTML Update After Delete

This PR implements a quick fix to ensure that the HTML updates after an organization is deleted on the organization admin page.
Major Changes

Added a line in the subscription to deleteOrganization() to filter out the organization from the component's organizations array.

Testing
All changes were tested on the local server after running honcho start.
Developer Notes
This is a temporary fix (modeled after how the admin roles list is updated). This will be changed if the code is refactored to use RXJS objects throughout the application.

Hey @jadekeegan may need to change base branch!


typo add doris complex type for flink-doris-connector

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Notebook: Trusted should be set if all cells are run

Jupyter behavior is that on running all cells (either 1 at a time or using "Run All Cells") the notebook becomes trusted. We lost this logic somewhere along the line, such that there's no handling / notification of this. We should look to fix.

@chlafreniere When I try executing cells in jupyter the notebook stays Not Trusted. In my testing, the notebook only became trusted when clicking the Trusted button or through saving the notebook. Should we still proceed with this one?

Yes, please proceed. We had some design discussions around this quite a while back and would like to re-enable this functionality.


Any SQL errors in a transaction are masked

Any errors that happen during a transaction, are masked by the current transaction is aborted, commands ignored until end of transaction block error, due to the call made to await super.query('reset rls.actor_id; reset rls.tenant_id;');despite there being an error and the call being transactional.
I believe the solution to this issue would be to check if this.isTransactionActive is true and if there is an error, do not attempt to run the reset rls.actor_id; reset rls.tenant_id; query.

Thank you @karvapallo for your contribution. This is now released as version 2.0.4.
I would like to back-port this to version 1 of rls. Do you want to add the same changes but into branch 1.x ? Otherwise I can do it as well, but it would be nice to have your name as contributor on the PR.

@stelescuraul thanks! You can go ahead and make that changes to version 1.x. Thanks again.


AttributeError: module 'dojo.pipeline' has no attribute 'modify_permissions'

Bug description
I upgraded from version 2.12.0 to version 2.13.0 and when trying to login with Azure AD an error occurs AttributeError: module 'dojo.pipeline' has no attribute 'modify_permissions'.
I verified that version 2.13.0 actually removed the modify_permissions method. Link
I don't know if it would have an impact, but the method remains in the file dojo/settings/settings.dist.py. Link
Steps to reproduce

Go to login page
Click on 'login with Azure AD'
See error

Deployment method

[ ] Docker Compose
[X] Kubernetes
[ ] GoDojo

Environment information

Operating System: Kubernetes
DefectDojo version (see footer) or commit message: [2022-08-02 12:08:45 -0500] d54ea5279: Merge pull request #6643 from DefectDojo/release/2.13.0 [ (HEAD, tag: 2.13.0, origin/master, origin/HEAD, master)]

Logs
[04/Aug/2022 18:38:02] ERROR [django.request:224] Internal Server Error: /complete/azuread-tenant-oauth2/
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/usr/local/lib/python3.8/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/local/lib/python3.8/site-packages/django/views/decorators/cache.py", line 44, in _wrapped_view_func
    response = view_func(request, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/django/views/decorators/csrf.py", line 54, in wrapped_view
    return view_func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_django/utils.py", line 46, in wrapper
    return func(request, backend, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_django/views.py", line 31, in complete
    return do_complete(request.backend, _do_login, user=request.user,
  File "/usr/local/lib/python3.8/site-packages/social_core/actions.py", line 45, in do_complete
    user = backend.complete(user=user, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_core/backends/base.py", line 40, in complete
    return self.auth_complete(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_core/utils.py", line 247, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_core/backends/oauth.py", line 401, in auth_complete
    return self.do_auth(response['access_token'], response=response,
  File "/usr/local/lib/python3.8/site-packages/social_core/utils.py", line 247, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_core/backends/oauth.py", line 413, in do_auth
    return self.strategy.authenticate(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_django/strategy.py", line 105, in authenticate
    return authenticate(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/django/views/decorators/debug.py", line 42, in sensitive_variables_wrapper
    return func(*func_args, **func_kwargs)
  File "/usr/local/lib/python3.8/site-packages/django/contrib/auth/__init__.py", line 76, in authenticate
    user = backend.authenticate(request, **credentials)
  File "/usr/local/lib/python3.8/site-packages/social_core/backends/base.py", line 80, in authenticate
    return self.pipeline(pipeline, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_core/backends/base.py", line 83, in pipeline
    out = self.run_pipeline(pipeline, pipeline_index, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/social_core/backends/base.py", line 112, in run_pipeline
    func = module_member(name)
  File "/usr/local/lib/python3.8/site-packages/social_core/utils.py", line 59, in module_member
    return getattr(module, member)
AttributeError: module 'dojo.pipeline' has no attribute 'modify_permissions'

Screenshots

Additional context (optional)
I'm using an external PostgreSQL database.

Same here.
Assuming block of code was unintentionally removed with:
https://github.com/DefectDojo/django-DefectDojo/commit/12f49e0adcd25cdffcb246c6655aef320356494f

Is there any patching possible for 2.13.0 ? Just upgraded on my instance...

@StefanFl FYI

I asked the other maintainers about a hotfix release.

Release has been made -> https://github.com/DefectDojo/django-DefectDojo/releases/tag/2.13.1

Login with Azure AD ok, thanks!


Appstudio update mvp-test-component

Pipelines as Code configuration proposal

Pipelines as Code CI/mvp-test-component-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
7 seconds
init

✅ Succeeded
15 seconds
clone-repository

✅ Succeeded
1 minute
build-container

✅ Succeeded
12 seconds
sanity-inspect-image

✅ Succeeded
27 seconds
deprecated-base-image-check

✅ Succeeded
16 seconds
clair-scan

✅ Succeeded
56 seconds
clamav-scan

✅ Succeeded
11 seconds
sbom-json-check

✅ Succeeded
8 seconds
sanity-optional-label-check

✅ Succeeded
7 seconds
sanity-label-check

✅ Succeeded
5 seconds
show-summary


nginx-quiche: many error logs: epoll_ctl(1, 12) failed (17: File exists)

Hi, there
client:  quiche-0.9.0
server: nginx-quiche-0.10.0 release
there are many error logs in nginx, but the request is successful
2021/10/26 09:55:32 [alert] 114582#0: *22873 epoll_ctl(1, 12) failed (17: File exists), client: <IP_ADDRESS>, server: oquic-test.wanyol.com, request: "GET /test/get/case/1k HTTP/3", subrequest: "/mirror/test/get/case", host: "oquic-test.wanyol.com:8443" 2021/10/26 09:55:32 [alert] 114582#0: *22873 epoll_ctl(1, 12) failed (17: File exists), client: <IP_ADDRESS>, server: oquic-test.wanyol.com, request: "GET /test/get/case/20k HTTP/3", subrequest: "/mirror/test/get/case", host: "oquic-test.wanyol.com:8443" 2021/10/26 09:55:33 [alert] 114582#0: *22873 epoll_ctl(1, 12) failed (17: File exists), client: <IP_ADDRESS>, server: oquic-test.wanyol.com, request: "GET /test/get/case/10k HTTP/3", subrequest: "/mirror/test/get/case", host: "oquic-test.wanyol.com:8443"

You might want to retry with 0.18 and see if this is better.


await fix for 3.5 skip support (client side eval)

See https://github.com/aspnet/EntityFramework/issues/2445
In the meantime, as NotSupportedExcepton is thrown

Just throwing "NotSupportedExecption" like in EF6 is fine


Topics: Messages filtering by seek type is broken within Topic profile

Describe the bug (Actual behavior)
Messages filtering by seek type (Offset, Timestamp) is broken within Topic profile
Expected behavior
Should be possible to filter messages by Offset/Timestamp
Set up
https://www.kafka-ui.provectus.io/
Steps to Reproduce

Login to kafka-ui
Navigate to Topics
Select the Topic
Turn to Messages tab
Add new messages
Select seek type (Offset/Timestamp)
Press Submit

Screenshots
https://user-images.githubusercontent.com/104780608/217451012-2888e38d-0346-49fc-82cc-b89d43ed12cb.mov

Filtering by offset still unavailable
https://user-images.githubusercontent.com/104780608/228433188-be5f19f6-9057-42a1-a84a-0c594c0f1f73.mov


Animate the adding of new values

On a line graph, it could be nice to have the impression that the values are added continuously even if it's not really the case. This would be made possible if the values where sliding continuously from the right to the left, and the last value is displayed after the duration of the slide.
This means that the graph will not be real time anymore, but the visualisation could be smoother and nicer to look. Any thoughts on this?

@almet You'd have to look at the Rickshaw.Graph.Axis.Time.js file, and check out the render function, as far as I can tell.


Expose Case Annotations in varfish API

Currently an endpoint for retrieving annotations for an individual case is already exposed in the following endpoint:
https://github.com/bihealth/varfish-server/blob/1e956c92aabfc7fee9caaefaec60f0034f5e2cc9/cases/views_api.py#L363
This endpoint currently has no permission_classes set and is not reachable.
Expected behavior:
Using an varfish API Token, access to the endpoint should be possible.
Current behavior:
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://varfish.bihealth.org/cases/api/case-gene-annotation/list/<CASE_UUID>

@stolpeo Do you perhaps know how the new endpoints can be added to the token based API? This might also be needed for some other additional endpoints, where I would like to perform some automated filters.

@holtgrewe I can add a PR, but do you currently have the capacity to review PRs regarding these issues? Otherwise I can find alternative solutions, that do not require changing the Varfish API

@xiamaz yes, we will review PRs.

Currently, the following endpoints will need to be exposed in order to export all information necessary in exported variants:
    smallvar_flags_url = "https://varfish.bihealth.org/variants/api/small-variant-flags/list-create/{varfish_uuid}"
    smallvar_annos_url = "https://varfish.bihealth.org/variants/ajax/smallvariant/user-annotated-case/{varfish_uuid}"
    svs_flags_url = "https://varfish.bihealth.org/svs/ajax/structural-variant-flags/list-create/{varfish_uuid}"
    svs_details_url = "https://varfish.bihealth.org/svs/sv-query-result-row/retrieve/{sv_uuid}"

We require the following information for both structural and small variants:

chromosomal position
transcript cDNA, protein consequence, preferably NM MANE
for structural variants, involved genes, exons
Zygosity per member in FAM
all flags in Varfish with their status
ACMG annotations
preferably also comments


[v0.11.2] Release Tracker

This is a main issue to track which PRs should be cherry-picked for the 0.11.2 release, and follows PyTorch's criteria https://github.com/pytorch/pytorch/issues/58518.
Cherry-Pick Criteria
Only low-risk changes may be cherry-picked from main:

Fixes to regressions against the most recent minor release (e.g. 1.8 for 1.9 release; see module: regression issue list)
Critical fixes for: silent correctness, backwards compatibility, crashes, deadlocks, (large) memory leaks
Fixes to new features introduced in the most recent minor release (e.g. 1.8.1 for 1.9 release)
Test/CI fixes
Documentation improvements
Compilation fixes or ifdefs required for different versions of the compilers or third-party libraries
Release branch specific changes (e.g. change version identifiers)

Cherry-Pick Process
Ensure your PR has landed in main. This does not apply for release-branch specific changes (see Cherry-Pick criteria).
Create a PR against the release branch.
Have the PoC of the release review and merge the cherry pick.
Once it is merged, add a change log entry with the following format:

Link to merged main PR (if applicable):
Link to release branch PR:
Criteria Category:

cc @seemethere @malfet

Link to merged main PR: https://github.com/pytorch/vision/pull/4931
Link to release branch PR: https://github.com/pytorch/vision/pull/5061
Criteria Category: Test/CI fixes

Link to merged main PR: https://github.com/pytorch/vision/pull/4926
Link to release branch PR: https://github.com/pytorch/vision/pull/5062
Criteria Category: Test/CI fixes

Link to merged main PR: https://github.com/pytorch/vision/pull/4987
Link to release branch PR: https://github.com/pytorch/vision/pull/5065
Criteria Category: Test/CI fixes

Link to merged main PR: https://github.com/pytorch/vision/pull/4966
Link to release branch PR: https://github.com/pytorch/vision/pull/5066
Criteria Category: Critical fixes

Link to merged main PR: https://github.com/pytorch/vision/pull/4806
Link to release branch PR: https://github.com/pytorch/vision/pull/5067
Criteria Category: Critical fixes

Link to merged main PR: https://github.com/pytorch/vision/pull/4649
Link to release branch PR: https://github.com/pytorch/vision/pull/5068
Criteria Category: Critical fixes

Link to merged main PR: https://github.com/pytorch/vision/pull/4893
Link to release branch PR: https://github.com/pytorch/vision/pull/5094
Criteria Category: Regressions from previous release


Boomer Desktop Application

[ ] Vision Based Exercise Partner
[ ] Vision Based Games
[ ] GUI Based Application
[ ] REMINDERS and DATABASES
[ ] Movements Integration

For implementation of UI, Right?

For implementation of UI, Right?
Exactly.


Get neighbors error

Configuration:

RDKit Version: '2019.09.1'
Operating system: Windows
Python version (if relevant): 3.7
Are you using conda? Yes
If you are using conda, which channel did you install the rdkit from? https://anaconda.org/rdkit/rdkit
If you are not using conda: how did you install the RDKit?

Description:

I am trying to be able to read all of the bonds in the molecule Furan. When using [x.GetAtomicNum() for x in atom.GetNeighbors()] it is returning [1, 6, 8] when it reads oxygen which tells me it thinks oxygen is bonded to H and C but it really is only bonded two carbons. My understanding is that vector is that the first elements are bonds, and the last element is the atomic number of the atom you are reading. My guess would be it should return [6,6,8]. Am I missing something?

https://gist.github.com/bdaves12/b3861a73b1d3ae855d127b19317e3f3d
Your code sample here
for atom in m.GetAtoms():
    print(atom.GetAtomicNum())
    n = n+1
for x in range(0, n):
    symbol = m.GetAtomWithIdx(x).GetSymbol()
    print(symbol, x)
    if symbol == 'O':
        print(f'symbol = {symbol}')
        atom2 = m.GetAtomWithIdx(x)
        bonds2 = [x.GetAtomicNum() for x in atom.GetNeighbors()]
        bonds2.sort()
        bond_oxygen.append(bonds2)
        print(f'bond_oxygen = {bonds2}')
    if symbol == 'C':
        print(f'symbol = {symbol}')
        atom = m.GetAtomWithIdx(x)
    # print([x.GetAtomicNum() for x in atom.GetNeighbors()])
        bonds = [x.GetAtomicNum() for x in atom.GetNeighbors()]
        bond_structure.append(bonds)
        print(f'bonds = {bonds}')

Any help would be appreciated thank you.

Could you please attach the SDF molblock of your molecule?
You can obtain it with
print Chem.MolToMolBlock(m)

Thanks.

9  9  0  0  0  0  0  0  0  0999 V2000
1.2760   -0.0000    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
0.3943    1.2135    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
-1.0323    0.7500    0.0000 O   0  0  0  0  0  0  0  0  0  0  0  0
-1.0323   -0.7500    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
0.3943   -1.2135    0.0000 C   0  0  0  0  0  0  0  0  0  0  0  0
2.7760    0.0000    0.0000 H   0  0  0  0  0  0  0  0  0  0  0  0
0.8578    2.6401    0.0000 H   0  0  0  0  0  0  0  0  0  0  0  0
-2.2458   -1.6317    0.0000 H   0  0  0  0  0  0  0  0  0  0  0  0
0.8578   -2.6401    0.0000 H   0  0  0  0  0  0  0  0  0  0  0  0
1  2  2  0
2  3  1  0
3  4  1  0
4  5  2  0
5  1  1  0
1  6  1  0
2  7  1  0
4  8  1  0
5  9  1  0
M  END

Can you please paste the molblock between
```
```
otherwise multiple spaces are collapsed to a single space.

I think there is something wrong with our code, here is a simpler version
that looks ok to me:

>>> for atom in m.GetAtoms():

...     print(atom.GetIdx(), atom.GetSymbol(), [(nbr.GetIdx(),
nbr.GetSymbol()) for nbr in atom.GetNeighbors()])

...

atom.  atom neighbors

0 C [(1, 'C'), (4, 'C'), (5, 'H')]

1 C [(0, 'C'), (2, 'O'), (6, 'H')]

2 O [(1, 'C'), (3, 'C')]

3 C [(2, 'O'), (4, 'C'), (7, 'H')]

4 C [(3, 'C'), (0, 'C'), (8, 'H')]

5 H [(0, 'C')]

6 H [(1, 'C')]

7 H [(3, 'C')]

8 H [(4, 'C')]

On Fri, Nov 15, 2019 at 10:15 AM Paolo Tosco<EMAIL_ADDRESS>wrote:

Can you please paste the molblock between

otherwise multiple spaces are collapsed to a single space.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/issues/2789?email_source=notifications&email_token=ACLOFIESR42MEDP6UZ2IZV3QT24KPA5CNFSM4JN3Q5G2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEFXEDQ#issuecomment-554398222,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLOFIEUXUVTE6W4QCGVGRDQT24KPANCNFSM4JN3Q5GQ
.

(Typo, I meant to write a problem with your code not a problem with our code)
And now with markdown!
for atom in m.GetAtoms():
  print(atom.GetIdx(), atom.GetSymbol(), [(nbr.GetIdx(), nbr.GetSymbol())
          for nbr in atom.GetNeighbors()])

atom.  atom neighbors
0 C [(1, 'C'), (4, 'C'), (5, 'H')]
1 C [(0, 'C'), (2, 'O'), (6, 'H')]
2 O [(1, 'C'), (3, 'C')]
3 C [(2, 'O'), (4, 'C'), (7, 'H')]
4 C [(3, 'C'), (0, 'C'), (8, 'H')]
5 H [(0, 'C')]
6 H [(1, 'C')]
7 H [(3, 'C')]
8 H [(4, 'C')]

Okay that's what I figured do you have any idea why the way I formatted the code did not work? Also how exactly are you using that nbr? I apologize for the questions I am new to using this software.

Simplified version of your code that yields the expected result:
for n, atom in enumerate(m.GetAtoms()):
    print(atom.GetAtomicNum())
bond_oxygen = []
bond_structure = []
for x, atom in enumerate(m.GetAtoms()):
    symbol = atom.GetSymbol()
    print(symbol, x)
    if symbol == 'O':
        print(f'symbol = {symbol}')
        bonds2 = [nbr.GetAtomicNum() for nbr in atom.GetNeighbors()]
        bonds2.sort()
        bond_oxygen.append(bonds2)
        print(f'bond_oxygen = {bonds2}')
    if symbol == 'C':
        print(f'symbol = {symbol}')
        bonds = [nbr.GetAtomicNum() for nbr in atom.GetNeighbors()]
        bond_structure.append(bonds)
        print(f'bonds = {bonds}')
6
6
8
6
6
1
1
1
1
C 0
symbol = C
bonds = [6, 6, 1]
C 1
symbol = C
bonds = [6, 8, 1]
O 2
symbol = O
bond_oxygen = [6, 6]
C 3
symbol = C
bonds = [8, 6, 1]
C 4
symbol = C
bonds = [6, 6, 1]
H 5
H 6
H 7
H 8

The reason why your code fails is here:
    if symbol == 'O':
        print(f'symbol = {symbol}')
        atom2 = m.GetAtomWithIdx(x)
        print('*** atom', atom.GetIdx(), atom.GetSymbol())
        bonds2 = [x.GetAtomicNum() for x in atom.GetNeighbors()]

You define atom2, but then access atom in the following line, and atom still has the value that you assigned in the if symbol == 'C' if clause, so it is actually the last carbon that you met while looping through the atoms.

Ahhh I did not even realize that thank you so much this was extremely helpful!

Following up, the 'nbr' is being used in a list comprehension:
[(nbr.GetIdx(), nbr.GetSymbol()) for nbr in atom.GetNeighbors()]

This makes a new list of (atom_idx, atom_symbol) by iterating through atom.GetNeighbors using the temporary variable nbr.
More info here;
https://www.pythonforbeginners.com/basics/list-comprehensions-in-python

I'm closing this because it looks like the question is answered. Please reopen if necessary.


Add ZeroPadding1D and ZeroPadding3D layers

Currently, the support for ZeroPadding1D  and ZeroPadding3D   are missed, and it would be great to add support for these layers. The desired PR addressing this issue should include:

[ ]  Implementation of layer class named as ZeroPadding1D  (you can take inspiration from the implementation of ZeroPadding2D  as reference)
[ ]   Implementation of layer class named as ZeroPadding3D  (you can take inspiration from the implementation of ZeroPadding2D  as reference)
[ ] Common hierarchy of all ZeroPadding layers with abstract class with the common functionality
[ ]  Documentation of layer and all non-private methods
[ ]   JUnit tests in api  module
[ ]   Support for export of layer to JSON (see ModelSaver.kt)
[ ]   Support for import of layer from JSON (see ModelLoader.kt)

Also, if needed, you can take a look at Keras documentation for ZeroPadding1D  and ZeroPadding3D .
NOTE: for the moment, there is no need to add support for "data format" (i.e., channels last vs. channels first) in your PR; you can assume the channels are always in the last dimension.
P.S. If you want to take this ticket, please leave the comment below
P.P.S Read the Contributing Guidelines.

Hey @zaleslaw can i take up on this?

Of course, @therealansh it's yours


Fixed a few sandcastle paths that didn't work with website build

Two sandcastle demos, High Dynamic Range and Export KML, referenced the SampleData path in a weird way that fails on the website. See sandcastle. I changed the paths to the correct style.
old: ../../../../Apps/SampleData/models/DracoCompressed/CesiumMilkTruck.gltf
new: ../../SampleData/models/DracoCompressed/CesiumMilkTruck.gltf

Thanks for the pull request @IanLilleyT!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Thanks @IanLilleyT!


Naming and type constraint fixes in aggregation functions

@OlivierBlanvillain @kanterov @imarios Just a couple of fixes for some inconsistencies in aggregation functions.

Current coverage is 89.80% (diff: 85.71%)

Merging #81 into master will increase coverage by 0.08%

@@             master        #81   diff @@
==========================================
  Files            25         25
  Lines           467        471     +4
  Methods         460        464     +4
  Messages          0          0
  Branches          7          7
==========================================
+ Hits            419        423     +4
  Misses           48         48
  Partials          0          0

Powered by Codecov. Last update 0f60a57...ad4215e

@OlivierBlanvillain took your comments into account ^^ Thanks !

Many thanks, merging! :+1:


added the GitHub contribution badges to display the contributors of repository in README file.

issue #48

@Sanket1308 please add the labels


The While function in render.py

Hi kwea123, I don't understand why there is a while function in your render_test function, the MAX_SAMPLES is 1024, the parameter N_samples is 1 or 4, and the loop is conducted for 1024 or 1024/4=256 times. Could you please tell me where is the key of this while loop? Thanks!

Oh I understand, no need to answer me, Sorry to border hhh~


Solution link for App Insights

I understand from my last issue here that this doc is due for updates, but I specifically just noticed that the link under Web Sites is pretty much obsolete.
One of these two links might be more appropriate now?
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-overview
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-azure-web-apps

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

ID: 7acb7625-7cb0-8884-b184-7c0ca8741699
Version Independent ID: 1d500cc4-0c28-64b1-763e-c0223f9c2c03
Content: Collect Azure service logs and metrics for Log Analytics
Content Source: articles/log-analytics/log-analytics-azure-storage.md
Service: log-analytics
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@dcbrown16 - Thanks for bringing this to our attention.  I'll bug this and we will determine the best way to address this since we are in the planning process to re-write content from Log Analytics regarding data collection.  In the meantime, I can determine which link to App Insights to reference in the existing article.  #please-close


example of for loop with range

see https://kie.zulipchat.com/#narrow/stream/232676-kogito/topic/In.20FEEL.2C.20how.20to.20map.20a.20function.20over.20a.20list.3F/near/362175124

An iteration context may either be an expression that returns a list of elements, or two expressions that return integers connected by “..”.

from <IP_ADDRESS> For loop expression

green on CI, proceeding to merge.


MP3 player not working with Firefox (14.0.1)

This can be seen at www.jazzooatlanta.org.
I'm using this to autoplay an MP3 file for a website. The player works perfectly fine with Chrome and Safari, and even on mobile, but when I view the site with Firefox the player pops up for a brief moment and then disappears (as opposed to the gray box issue I've seen others mention). That is to say, disappears as in the element removes itself from the page and the other elements shift up to fill the space, not just that it becomes invisible.
Any idea what would cause this, and how to fix it?
Note: I've seen some possibly-related fixes suggest using an AddType function in the .htaccess file, but unfortunately this particular site is hosted on Yahoo Small Business, and they do not allow the upload/edit of .htaccess. Other ideas?
Thanks!

@thisisnottravis Is this still an issue? If not can you close it please?


Extend overall NEET rate chart to pre-pandemic

YFF would like to see this data going back further. Exact date TBC

Pre-requisites:

[ ] Email Andrea, Zach & Chris to confirm a) exact starting date and b) whether it should be a rolling period of time or static start time. Probably makes sense to do this as part of #74

Asked about this as part of another email I sent - but we can follow up as part of #74 as well if there is no response.


FALCON-1852. Actual optional=true validation for inputs.  pushing the…

…se changes for inmobi 0.9 branch

Code has reviewed and merged to apache/falcon. As there are no merge conflicts merging the request.


Allow pinning internal actions

New issue?

[X] I have reviewed the Known Issues and confirm this is not a known issue.

TL;DR
For internal/private repos, pinning actions would be nice
✗ ratchet pin .github/workflows/snip.yml
failed to pin refs: 1 error occurred:
	* failed to resolve<EMAIL_ADDRESS>failed to get commit sha: GET https://api.github.com/repos/org/repo/commits/snip-v1.0.1: 404 Not Found []

A workaround for myself is to use mheap/pin-github-action. I'd like to use ratchet since that's what I currently use for open source actions.
export GH_ADMIN_TOKEN=$(gh config get -h github.com oauth_token)
pin-github-action .github/workflows/snip.yml

Detailed design
See above

Additional information
See above

Hi @nitrocode what do you mean by "internal" action? Is this on a private GitHub Enterprise Server (behind the firewall), or is this a private repo on GitHub.com?
You should be able to do the same with ratchet:
export ACTIONS_TOKEN=$(gh config get -h github.com oauth_token)
ratchet ./

Oh I meant private repo on github.com.
I did not know I could use that env var. Thank you!


Console command to make new Razor Page project is incorrect

Currently states you should run the command dotnet new webapp -o RazorPagesMovie when instead it should be dotnet new razor -o RazorPagesMovie

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

ID: cafe31d3-11f1-d679-1937-915690ac7360
Version Independent ID: e6b12009-be25-33e0-c5a8-8a1bd686b387
Content: Get started with ASP.NET Core Razor Pages in Visual Studio Code
Content Source: aspnetcore/tutorials/razor-pages-vsc/razor-pages-start.md
Product: aspnet-core
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@RyanTaite Thanks for commenting. They introduced an alias for razor ... webapp. Do you have the 2.1 SDK installed? ... The alias works with 2.1. Otherwise for 2.0, you're correct, it would be razor. If you flip the doc to "2.0" (upper-left of the page), it should flip the command back to using razor.

Looks I don't have 2.1 installed, and only 2.0! Totally my mistake then. Thank you!


My first issue

Removed redundancies in test code by creating _check method to be implemented

I’m afraid some wires got crossed somewhere along the way. The Extension is my project but I’m a fashion designer, not a coder. I’m only working on an iPhone right now and have never, I sweat, made a pull request because I don’t know how to do that.

Hey @Schiaparelli778, it’s all good. This is just a practice project. I’m not sure exactly what brought you here, but there’s nothing to worry about!


erro smali

Failed to locate smali file to hook ?

see the run.log file

I get the same problem last week your apk android:name atribut dont exisit in the manifest you have to find it manualy and replace $android_class by $total_pakage/$android_name . Where android name shall be Main or .Main or MainActivty

Failed to locate smali file to hook ?

I get the same problem last week your apk android:name atribut dont exisit in the manifest you have to find it manualy and replace $android_class by $total_pakage/$android_name . Where android name shall be Main or .Main or MainActivty

#191 Some improvements are being implemented.


Front-End - donate button & logo

[ ] add donate icon
[ ] replace react logo on browser with s/s logo

done


Mention Android in repository description

There are many projects named "Restler" on GitHub. But not all for Android. It would be good to mention OS platform this app is created for. So, anybody hwo searches "android test api" can find this project. For example: "Restler is a beautiful and powerful Android app for testing REST API anywhere and anytime. http://restler.tiagohm.xyz"

Thanks for feedback. I edited the description.


Make storagecluster version dynamic

Version is currently hardcoded into the instance examples.  If the version is not included in the object ODF will dynamically set the version based on the operator version.

Less is more!  LGTM


hangs while opening HTML file

VSCode Version:0.10.11
OS Version:Win7

While opening HTML file, toast message appears:

[Info] HTML CSS Class Completion: Fetching CSS rules from CSS files, please wait.

then windows popup titled Visual Studio Code:

The window is no longer responding
You can reopen or close the window or keep waiting.

Steps to Reproduce:

open an HTML file

@alfalabs Do you have any extensions installed that could cause that? In the built-in HTML support we don't do any fetching of CSS.

@aeschli
Yes, I installed VScode yesterday and a bunch of extensions before running it.
I would expect that a third party extension should never cause VScode to hang.
This issue should be reopened as to protect VScode from bad extensions.

@alfalabs reopening, but now please provide detailled information about your setup:

which extensions do you have installed
attach the html file that caused the hang

@aeschli @egamma
In my original post, the offensive extension is mentioned in message: " HTML CSS Class Completion"
Here is the link: https://github.com/Zignd/HTML-CSS-Class-Completion
Attached is the index.html file
index.zip

// CC @alexandrudima

It is happening to me as well. I'm also using HTML Class Completion extension.

I've same issue.
![image](https://cloud.githubusercontent.com/assets/1710431/17260683/718ce54a-55da-11e6-9413-
20a276e7a02f.png)

@levka9, please, update the image.

It is still reproducible with the latest version: 1.4.0
This extension (https://github.com/Zignd/HTML-CSS-Class-Completion) is causing VSCode to freeze and even the dialog that pops-up (Wait, Reopen, Close) does not handle it.
I am able to reproduce it when I open html file in a fairly big project. It is not reproducible with smaller projects. It may be related to specific CSS loading or something and not to the project size itself.

Resolved by uninstall HTML Class Completion extension in one click with restart vs code.

I've had this problem also, and in the previous version even major crashes.
Removed the extension.

I have tried to reproduce with the HTML contents of index.zip and failed to do so.
I can continue to investigate @ventsislav-georgiev @davidrensh @KioriSun -- is it perhaps something about the folders you open? Does this extension traverse all the files in a folder, possibly unbounded?

Faced same issue problem. Thank you.
Resolved by uninstall HTML Class Completion extension

@alexandrudima my folder had thousands of files(and css's with thousands of lines), and I always had some .php files pre opened, but even if not, after a certain point it got stuck on the whole "CSS Class Completion: Fetching CSS rules from CSS files, please wait."
I guess it was just way too many files for the extension to handle. It's weird also because it didn't happen when i installed it right away, but rather after a few open and closes of the program.
Try using this with a really big project and see how it goes.

The workaround so far is everyone is recommending to uninstall the extension. I suggest we implement a registry of known "slow" extensions and show this in vs code next to the extension. i.e. "This extension is known to cause performance problems". We cannot protect against high CPU code, we are not an OS.

At this point everyone is in agreement that this is an issue with the extension, therefore nothing actionable for me.


Allow mysql v7 cookbook

Relax mysql version constraint for allow recent versions of the cookbook.
Fix https://github.com/sinfomicien/mysql2_chef_gem/issues/9

@Maks3w: thanks for submitting this. We merged #10, which included some additional testing changes.


Updates liquibase-sdk-maven-plugin to latest (DAT-11807)

this dependency is already updated to 10.19


Set DATABASE_URL for all login shell sessions

Right now DATABASE_URL is only set in the entrypoint script.
This means that when you shell into a container to use the rails console you need to manually set the env variable to access anything.
We should move this to somewhere where it can be sourced from both situations.

However this gets fixed I need to replicate to the other microservices.

Fixed by https://github.com/ManageIQ/topological_inventory-api/pull/71 and https://github.com/ManageIQ/topological_inventory-deploy/pull/22


Making android min sdk configurable per auto-instrumentation subproject

Closes #138
This should allow to set the minimum Android SDK supported by a specific auto-instrumentation subproject like so:
// library build.gradle.kts file

plugins {
    id("otel.java-library-conventions")
    //...
}

otelAndroid.minSdk = 26

This will prevent animal sniffer from complaining about code references used by the auto-instrumentation project that aren't available neither in the Android SDK 21 (the current core lib min SDK supported) nor in the desugar lib.
The README of the auto-instrumentation subproject that changes this value should mention what's the minimum supported Android API level for the auto-instrumentation to work properly, this is because some auto-instrumentations might target code found on versions above 21 while still providing some functionality and being safe to run on devices with API level 21 (since the code from higher SDK versions would just be ignored as it wouldn't be found in devices with SDK version 21). In some other cases, the auto-instrumentation could cause issues when running on devices with the SDK version 21, so that's why it should be specified in the README what's the minimum version supported.

Thanks @LikeTheSalad! I also tried it out in httpurlconnection module, it works perfectly!
Just had a question about what we should call out in readme -
The "otelAndroid.minSdk = 24" we specify in the build file is what's used to compile the module. And as you also pointed out, and I tested it before - a module compiled with higher sdk version can RUN on all prior versions (android offers this backward compatibility). So, If I were to mention min sdk compatible to be run on, it would be API level 1. We can perhaps skip that? But we will definitely make sure we test our module runs perfectly on one of the prior versions to the compile sdk version we mention in build script.

Just had a question about what we should call out in readme - The "otelAndroid.minSdk = 24" we specify in the build file is what's used to compile the module. And as you also pointed out, and I tested it before - a module compiled with higher sdk version can RUN on all prior versions (android offers this backward compatibility). So, If I were to mention min sdk compatible to be run on, it would be API level 1 (or whatever Android provides backward compatibility upto if that's different). We can perhaps skip that? But we will definitely make sure we test our module runs perfectly on one of the prior versions to the compile sdk version we mention in build script.

It's probably the case that it works back to API 1 as you mentioned, however, I think it might be a little confusing to use that value since this tool relies on the OTel Java lib which has min API 21. So I would mention something like "The minimum supported Android SDK version is 21, though it will also instrument tools added in the Android SDK version 24 when running on devices with API level 24 and above". There's probably a better way to phrase it, but generally speaking, that would be my approach.

It's probably the case that it works back to API 1 as you mentioned, however, I think it might be a little confusing to use that value since this tool relies on the OTel Java lib which has min API 21. So I would mention something like "The minimum supported Android SDK version is 21, though it will also instrument tools added in the Android SDK version 24 when running on devices with API level 24 and above". There's probably a better way to phrase it, but generally speaking, that would be my approach.

Oh, I see. That makes more sense! Will add that in the readme :)

It's probably the case that it works back to API 1 as you mentioned, however, I think it might be a little confusing to use that value since this tool relies on the OTel Java lib which has min API 21. So I would mention something like "The minimum supported Android SDK version is 21, though it will also instrument tools added in the Android SDK version 24 when running on devices with API level 24 and above". There's probably a better way to phrase it, but generally speaking, that would be my approach.

Oh, I see. That makes sense! Will add that in the readme :)

Another option is to throw an exception with this message when setting minSdk < 21, so it's not failing at runtime in case it compiles somehow.

This is cool. I am not expecting to see a huge number of wildly differing instrumentations in the short term, but I do think about end-user ergonomics, and I wonder if having different minSdk versions for different components could cause user confusion (or at least burden).
Not a showstopper, but wanted to be thinking about it for later.

Yeah, ideally, and most likely, we wouldn't have to create too many of these add-ons with higher SDK version compatibility, especially because that should only happen when addressing Android OS's classes and I'm guessing third-party libs would be more often the targets of instrumentation. However, I cannot say we will never encounter a situation where we need to instrument OS's classes-related code added in newer API levels, for those cases, I think we should make sure that their READMEs explain this quite well to avoid confusion. The burden is still there though, but since these tools are optional, I think it's better to have that burden rather than enforcing our core lib api limitations on end-user's projects.
This case is kinda like a hybrid one since it doesn't break the min SDK compatibility for 21 as @surbhiia explained, but it still supports code added past that version.


Error when submitting new attribute

When submitting a domain indicator with a new attribute, I received the following error:
'domain.com' does not appear to be an IPv4 or IPv6 address.
I confirmed that the the indicator for which I was trying to submit was a domain/host (www[.]yahoo[.]4pu[.]com), and not an IPv4/6. So, weird that it thought I was trying to submit an IP. Also tried submitting without 'www' and got the same error.

Hmm. Making edits in the comments field also results in the same error.

So the error pops up, but when canceling, and then returning to the indicator from the Indicator page, it looks like the attributes ARE actually getting submitted. So I'm using "Cancel" as the work around right now.

Very weird. I can't seem to replicate this on my end. I submitted a new indicator with the same name, and chose domain type. Then I tried to submit a new attribute and that seemed to work as well. I also added comments to the same indicator, and got no errors. Can you try to replicate this bug and document the exact steps?

This might be caused by a trailing space when the domain was first added. Try deleting the indicator and adding it.

Should be fixed in latest update with fix #30


All macros and scripts that need a token selected must check if one is selected

The GM or a player can put a macro in the bottom bar even if the macro is marked as a token macro. If they do so, and invoke the macro from the bottom bar, a token may not be selected. Handle this scenario.

Note:
Macros that have roll queries in them cannot be conditionally run because of the chat command processing order. See #56. This means that the following macros cannot check for selected in advance of their roll queries from triggering.

Set Token-Defaults
Set-Token-Light
Set-Token-vision

These will be investigated further in #56.


Grpc Java client block forever while filer server responsed with http1 400 - root cause lies in cmux matcher for grpc

Greetings,
I am seeing an issue while utilizing grpc java client versus filer server, the java client will block forever... while actually server responsed with an http 1.1 400 bad request.
I have reproduced the issue with grpc helloworld example under grpc-helloworld
Is it possible to change the matcher in filer.go to be
m.MatchWithWriters(cmux.HTTP2MatchHeaderFieldSendSettings("content-type", "application/grpc")
as per note from cmux?
At your convinience, please take a look, thanks in advance!
Note from cmux limitation
Java gRPC Clients: Java gRPC client blocks until it receives a SETTINGS frame from the server. If you are using the Java client to connect to a cmux'ed gRPC server please match with writers:
grpcl := m.MatchWithWriters(cmux.HTTP2MatchHeaderFieldSendSettings("content-type", "application/grpc")

Thanks for debugging and reporting this!
We may need to have a separate port for gRPC because of this and TLS limitations.
Btw: are you just trying to migrate to filer2?

np, i see others made same decision and change,  dgraph-io issue .
Not yet tried filer2, i am doing some experiments on this.

fixed in https://github.com/chrislusf/seaweedfs/commit/299312c8057c5b96f67a8ac825ee026fe01dd8fc


Transport Razor.Utilities.Shared and its dependencies

Related: https://github.com/dotnet/sdk/pull/31508, https://github.com/dotnet/sdk/pull/31510

Verified locally that this should fix the errors in SDK:

Run Microsoft.NET.Sdk.Razor.Tests - seeing the errors.
Packaged Razor: .\eng\common\build.ps1 -restore -build -pack
Added <add key="local" value="C:\razor\artifacts\packages\Debug\NonShipping" /> to SDK's NuGet.config.
Changed the Razor transport package versions to 7.0.0-dev in SDK's eng\Versions.props.
Rebuild the SDK and re-run the tests - no errors.


Runtime error using scPoli - Tensors must have same number of dimensions: got 1 and 2

Hi,
I am trying to follow this tutorial: https://github.com/theislab/scarches/blob/master/notebooks/scpoli_surgery_pipeline.ipynb.
matplotlib==3.8.2 numpy==1.24.4 pandas==1.5.3 scArches==0.5.10 scanpy==1.9.6 scikit-learn==1.3.2 seaborn==0.13.1 torch==2.1.2
When I try to train the model I run into this error:
Traceback (most recent call last):
File "/home/lifesci/data/scPoli_test.py", line 103, in
scpoli_query.train(
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/models/scpoli/scpoli_model.py", line 307, in train
self.trainer.train(n_epochs, lr, eps)
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/trainers/scpoli/trainer.py", line 298, in train
self.on_epoch_begin(lr, eps)
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/trainers/scpoli/trainer.py", line 515, in on_epoch_begin
self.initialize_prototypes()
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/trainers/scpoli/trainer.py", line 395, in initialize_prototypes
latent = self.get_latent_train()
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/trainers/scpoli/trainer.py", line 382, in get_latent_train
latent = self.model.get_latent(
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/models/scpoli/scpoli.py", line 354, in get_latent
z_mean, z_log_var = self.encoder(x_, embed_c)
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/lifesci/miniconda3/envs/scarches_new/lib/python3.9/site-packages/scarches/models/scpoli/scpoli.py", line 459, in forward
x = torch.cat((x, batch), dim=-1)
RuntimeError: Tensors must have same number of dimensions: got 1 and 2
Has anyone run into this error and been able to fix it?

Hm, can't reproduce this. Do you just run the tutorial with the same data etc? Could you try with the latest version of scarches?

Thanks, When I try with the latest version of scarches, the problem can be solved.


Span passed to IScopeManager.Activate is not == the underlying tracer span type

Consider
// ...
IScopeManager.Activate(ISpan span, bool finishSpanOnClose) {
  var myTypedSpan = span as MySpan; // The OpenTracing spec people told me to do this :( I told them it was finicky, as we now see
  // Do stuff
}
// ...

Currently, when ScopeBuilderDecorator.StartActive calls ScopeManagerDecorator.Activate it does so with the result of SpanBuilderDecorator.Start() which is of type SpanDecorator.
ScopeManagerDecorator.Activate then passes this to this._scopeManager.Activate directly

Right but I don't see why it'll be an issue ?
You really need a span implementation of your own ?
The problem is i'm very glad not to have any IScope overriding to do. And for that I need to give my own Span to the underlying Tracer/Scope

It's been a long time, but the reason we had to do the casting was one of two things

We had a strongly typed SpanId struct that could be parsed from a string, but that was wasteful to do on every SetTag/Log/Finish operation, so we tried to save it as a property. I think now I'd end up doing this via baggage though
There was some problem with IScope not exposing it's finishSpanOnClose that prevented another similar wrapping implementation from properly being able to handle IScopeManager.Active, since it couldn't tell if the underlyingManager.Active's scope had been set like that. I suggested that IScope expose finishSpanOnClose since it has to be constructed with one so it makes sense for wrapping, but I know at that time I was told to save it to a property myself and cast the span when it is read.

I think, until I hit whatever case it was that caused me issues again, we can ignore this issue. Especially since, really, if you do need to cast to the concrete type and you're not doing something crazy (like just trying to wrap) then maybe with more people involved it'll be easier to get OT to make a change to that API to expose that property :)


Cannot call kubectl port-forward on a running waSCC instance

If I run the demo in #152, I cannot appear to forward a port over to the instance:
><> k create -f demos/wascc/hello-world-assemblyscript/k8s.yaml
pod/hello-world-wascc-assemblyscript created
><> k get po
NAME                               READY   STATUS    RESTARTS   AGE
hello-world-wascc-assemblyscript   1/1     Running   0          23s
><> kubectl port-forward hello-world-wascc-assemblyscript 8000:80
error: error upgrading connection: unable to upgrade connection: Not Found

If I enable verbose logging:
><> k port-forward hello-world-wascc-assemblyscript 8000:80 -v 10
I0402 15:45:34.240660   26648 loader.go:375] Config loaded from file:  /Users/bacongobbler/.kube/config
I0402 15:45:34.242008   26648 cert_rotation.go:137] Starting client certificate rotation controller
I0402 15:45:34.242333   26648 cached_discovery.go:114] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/servergroups.json
I0402 15:45:34.243187   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/discovery.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243208   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authentication.k8s.io/v1/serverresources.json
I0402 15:45:34.243222   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authorization.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243401   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/autoscaling/v1/serverresources.json
I0402 15:45:34.243403   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/events.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243424   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiregistration.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243403   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/storage.k8s.io/v1/serverresources.json
I0402 15:45:34.243418   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authorization.k8s.io/v1/serverresources.json
I0402 15:45:34.243475   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/v1/serverresources.json
I0402 15:45:34.243523   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiregistration.k8s.io/v1/serverresources.json
I0402 15:45:34.243531   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/extensions/v1beta1/serverresources.json
I0402 15:45:34.243573   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/scheduling.k8s.io/v1/serverresources.json
I0402 15:45:34.243573   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/autoscaling/v2beta2/serverresources.json
I0402 15:45:34.243583   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiextensions.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243665   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/admissionregistration.k8s.io/v1/serverresources.json
I0402 15:45:34.243684   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authentication.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243707   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/storage.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243711   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/scheduling.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243811   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/admissionregistration.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243815   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/policy/v1beta1/serverresources.json
I0402 15:45:34.243835   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/coordination.k8s.io/v1/serverresources.json
I0402 15:45:34.243829   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/rbac.authorization.k8s.io/v1/serverresources.json
I0402 15:45:34.243864   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apps/v1/serverresources.json
I0402 15:45:34.243876   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/batch/v1/serverresources.json
I0402 15:45:34.243942   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/node.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243956   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/networking.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243981   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/networking.k8s.io/v1/serverresources.json
I0402 15:45:34.243975   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/certificates.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.243996   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/autoscaling/v2beta1/serverresources.json
I0402 15:45:34.244026   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/rbac.authorization.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.244035   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiextensions.k8s.io/v1/serverresources.json
I0402 15:45:34.244047   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/coordination.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.244075   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/batch/v1beta1/serverresources.json
I0402 15:45:34.262859   26648 cached_discovery.go:114] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/servergroups.json
I0402 15:45:34.263476   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apps/v1/serverresources.json
I0402 15:45:34.263644   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/rbac.authorization.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.263812   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiextensions.k8s.io/v1/serverresources.json
I0402 15:45:34.263863   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/storage.k8s.io/v1/serverresources.json
I0402 15:45:34.263977   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiextensions.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264010   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/v1/serverresources.json
I0402 15:45:34.264038   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/storage.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264118   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/scheduling.k8s.io/v1/serverresources.json
I0402 15:45:34.264175   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/admissionregistration.k8s.io/v1/serverresources.json
I0402 15:45:34.264257   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/scheduling.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264310   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/rbac.authorization.k8s.io/v1/serverresources.json
I0402 15:45:34.265096   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/networking.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264383   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/coordination.k8s.io/v1/serverresources.json
I0402 15:45:34.264379   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/batch/v1/serverresources.json
I0402 15:45:34.264473   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/discovery.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264524   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/coordination.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264537   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/admissionregistration.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.264850   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/networking.k8s.io/v1/serverresources.json
I0402 15:45:34.264878   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/policy/v1beta1/serverresources.json
I0402 15:45:34.264913   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/node.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.265002   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authentication.k8s.io/v1/serverresources.json
I0402 15:45:34.265016   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/certificates.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.265049   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/events.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.265132   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authentication.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.265132   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/batch/v1beta1/serverresources.json
I0402 15:45:34.265263   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiregistration.k8s.io/v1/serverresources.json
I0402 15:45:34.265279   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authorization.k8s.io/v1/serverresources.json
I0402 15:45:34.265299   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/autoscaling/v1/serverresources.json
I0402 15:45:34.265411   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/apiregistration.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.265434   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/autoscaling/v2beta1/serverresources.json
I0402 15:45:34.265443   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/authorization.k8s.io/v1beta1/serverresources.json
I0402 15:45:34.265473   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/extensions/v1beta1/serverresources.json
I0402 15:45:34.265618   26648 cached_discovery.go:71] returning cached discovery info from /Users/bacongobbler/.kube/cache/discovery/<IP_ADDRESS>_8443/autoscaling/v2beta2/serverresources.json
I0402 15:45:34.281710   26648 round_trippers.go:423] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.18.0 (darwin/amd64) kubernetes/9e99141" 'https://<IP_ADDRESS>:8443/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript'
I0402 15:45:34.299712   26648 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript 200 OK in 17 milliseconds
I0402 15:45:34.299737   26648 round_trippers.go:449] Response Headers:
I0402 15:45:34.299742   26648 round_trippers.go:452]     Date: Thu, 02 Apr 2020 22:45:34 GMT
I0402 15:45:34.299747   26648 round_trippers.go:452]     Content-Type: application/json
I0402 15:45:34.299751   26648 round_trippers.go:452]     Content-Length: 2660
I0402 15:45:34.299796   26648 request.go:1068] Response Body: {"kind":"Pod","apiVersion":"v1","metadata":{"name":"hello-world-wascc-assemblyscript","namespace":"default","selfLink":"/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript","uid":"b7123e72-0285-4f48-b69e-9b6d15827f02","resourceVersion":"762","creationTimestamp":"2020-04-02T22:43:50Z","annotations":{"deislabs.io/wascc-action-key":"MA6DECXXYRIRPWYJAIKQT7ZBPUCJ7HRBLK3ZSDTGE7WWIJ6VU52PZOCI"},"managedFields":[{"manager":"kubectl","operation":"Update","apiVersion":"v1","time":"2020-04-02T22:43:50Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:deislabs.io/wascc-action-key":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"hello-world-wascc-assemblyscript\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:nodeSelector":{".":{},"f:beta.kubernetes.io/arch":{}},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}},{"manager":"unknown","operation":"Update","apiVersion":"v1","time":"2020-04-02T22:43:52Z","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:containerStatuses":{},"f:phase":{}}}}]},"spec":{"volumes":[{"name":"default-token-f9d8r","secret":{"secretName":"default-token-f9d8r","defaultMode":420}}],"containers":[{"name":"hello-world-wascc-assemblyscript","image":"webassembly.azurecr.io/hello-world-wascc-assemblyscript:v0.1.0","resources":{},"volumeMounts":[{"name":"default-token-f9d8r","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","nodeSelector":{"beta.kubernetes.io/arch":"wasm32-wascc"},"serviceAccountName":"default","serviceAccount":"default","nodeName":"krustlet-wascc","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceLinks":true},"status":{"phase":"Running","conditions":[{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2020-04-02T22:43:50Z"}],"containerStatuses":[{"name":"hello-world-wascc-assemblyscript","state":{"running":{"startedAt":"2020-04-02T22:43:52Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"","imageID":"","started":true}],"qosClass":"BestEffort"}}
I0402 15:45:34.330709   26648 round_trippers.go:423] curl -k -v -XGET  -H "Accept: application/json, */*" -H "User-Agent: kubectl/v1.18.0 (darwin/amd64) kubernetes/9e99141" 'https://<IP_ADDRESS>:8443/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript'
I0402 15:45:34.333617   26648 round_trippers.go:443] GET https://<IP_ADDRESS>:8443/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript 200 OK in 2 milliseconds
I0402 15:45:34.333637   26648 round_trippers.go:449] Response Headers:
I0402 15:45:34.333642   26648 round_trippers.go:452]     Date: Thu, 02 Apr 2020 22:45:34 GMT
I0402 15:45:34.333646   26648 round_trippers.go:452]     Content-Type: application/json
I0402 15:45:34.333649   26648 round_trippers.go:452]     Content-Length: 2660
I0402 15:45:34.333679   26648 request.go:1068] Response Body: {"kind":"Pod","apiVersion":"v1","metadata":{"name":"hello-world-wascc-assemblyscript","namespace":"default","selfLink":"/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript","uid":"b7123e72-0285-4f48-b69e-9b6d15827f02","resourceVersion":"762","creationTimestamp":"2020-04-02T22:43:50Z","annotations":{"deislabs.io/wascc-action-key":"MA6DECXXYRIRPWYJAIKQT7ZBPUCJ7HRBLK3ZSDTGE7WWIJ6VU52PZOCI"},"managedFields":[{"manager":"kubectl","operation":"Update","apiVersion":"v1","time":"2020-04-02T22:43:50Z","fieldsType":"FieldsV1","fieldsV1":{"f:metadata":{"f:annotations":{".":{},"f:deislabs.io/wascc-action-key":{}}},"f:spec":{"f:containers":{"k:{\"name\":\"hello-world-wascc-assemblyscript\"}":{".":{},"f:image":{},"f:imagePullPolicy":{},"f:name":{},"f:resources":{},"f:terminationMessagePath":{},"f:terminationMessagePolicy":{}}},"f:dnsPolicy":{},"f:enableServiceLinks":{},"f:nodeSelector":{".":{},"f:beta.kubernetes.io/arch":{}},"f:restartPolicy":{},"f:schedulerName":{},"f:securityContext":{},"f:terminationGracePeriodSeconds":{}}}},{"manager":"unknown","operation":"Update","apiVersion":"v1","time":"2020-04-02T22:43:52Z","fieldsType":"FieldsV1","fieldsV1":{"f:status":{"f:containerStatuses":{},"f:phase":{}}}}]},"spec":{"volumes":[{"name":"default-token-f9d8r","secret":{"secretName":"default-token-f9d8r","defaultMode":420}}],"containers":[{"name":"hello-world-wascc-assemblyscript","image":"webassembly.azurecr.io/hello-world-wascc-assemblyscript:v0.1.0","resources":{},"volumeMounts":[{"name":"default-token-f9d8r","readOnly":true,"mountPath":"/var/run/secrets/kubernetes.io/serviceaccount"}],"terminationMessagePath":"/dev/termination-log","terminationMessagePolicy":"File","imagePullPolicy":"IfNotPresent"}],"restartPolicy":"Always","terminationGracePeriodSeconds":30,"dnsPolicy":"ClusterFirst","nodeSelector":{"beta.kubernetes.io/arch":"wasm32-wascc"},"serviceAccountName":"default","serviceAccount":"default","nodeName":"krustlet-wascc","securityContext":{},"schedulerName":"default-scheduler","tolerations":[{"key":"node.kubernetes.io/not-ready","operator":"Exists","effect":"NoExecute","tolerationSeconds":300},{"key":"node.kubernetes.io/unreachable","operator":"Exists","effect":"NoExecute","tolerationSeconds":300}],"priority":0,"enableServiceLinks":true},"status":{"phase":"Running","conditions":[{"type":"PodScheduled","status":"True","lastProbeTime":null,"lastTransitionTime":"2020-04-02T22:43:50Z"}],"containerStatuses":[{"name":"hello-world-wascc-assemblyscript","state":{"running":{"startedAt":"2020-04-02T22:43:52Z"}},"lastState":{},"ready":true,"restartCount":0,"image":"","imageID":"","started":true}],"qosClass":"BestEffort"}}
I0402 15:45:34.352477   26648 round_trippers.go:423] curl -k -v -XPOST  -H "X-Stream-Protocol-Version: portforward.k8s.io" -H "User-Agent: kubectl/v1.18.0 (darwin/amd64) kubernetes/9e99141" 'https://<IP_ADDRESS>:8443/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript/portforward'
I0402 15:45:34.388145   26648 round_trippers.go:443] POST https://<IP_ADDRESS>:8443/api/v1/namespaces/default/pods/hello-world-wascc-assemblyscript/portforward 404 Not Found in 35 milliseconds
I0402 15:45:34.388176   26648 round_trippers.go:449] Response Headers:
I0402 15:45:34.388185   26648 round_trippers.go:452]     Content-Length: 9
I0402 15:45:34.388191   26648 round_trippers.go:452]     Date: Thu, 02 Apr 2020 22:45:34 GMT
F0402 15:45:34.388736   26648 helpers.go:115] error: error upgrading connection: unable to upgrade connection: Not Found

Is there an endpoint that Krustlet needs to provide in order for the port-forward API to work?

There are some theories suggesting that kubectl port-forward may only work if the kubelet is on a linux node. I was testing this on macOS with minikube. Will test with Ubuntu tomorrow and see if results differ

I can confirm this is not working on macOS with Docker Desktop either.

same on WSL2

I'm running Krustlet on a Linux instance and same-same.

closing as the krustlet-wasmcloud provider has been moved to its own project: https://github.com/wasmCloud/krustlet-wasmcloud-provider
Please open tickets related to the wasmcloud provider there. Thanks.


Fix for LLVM 18 compatibility and CI

Changes for compatibility with LLVM 18 and LLVM 17
Cleanup cmake files
CI for LLVM 18 through rocm 6.2.1

Note: The CI tests on tioga will be failing for 6.2.1 and this is expected


tmp file

hi guys,
In talon step, a talon_tmp dir was created. But many pybedtools.*.tmp files were generated in my root /tmp dir. How to fix it?
Thx.
Y

Hi,
I'm not sure I understand your question. Is this the same problem as https://github.com/mortazavilab/TALON/issues/74?

Hi fairliereese,
Thanks for response.
I am not familiar with python scripts, but I think there may be an issue with pybedtools. It generates  pybedtools..tmp files in /tmp/ file by default. I see that in  https://daler.github.io/pybedtools/topical-design-principles.html. And the /tmp/* files were not deleted when transcriptclean finished.
I add a line in transcriptclean.py:
pybedtools.set_tempdir('/mypath/tmp')
And manually remove this tmp dir after runing.
Y

Ah I see. That definitely does seem weird, but perhaps maybe something that could be solved in TranscriptClean as opposed to TALON.


Rename ImageManager::delete to ImageManager::remove to be more consistent

...with the Docker API.
Fixes #85

@ubermuda Good to merge?

Yes!

Thanks!

Nice..thanks!


Fix Barbican templating

The existing template removes the newline after {% endraw%}, so the two config options get stacked onto the same line, breaking Barbican

Should it go to yoga first?

@MoteHue Suggested that it could be to do with the config merging in Antelope. If you think it would affect yoga as well, then I'll rebase

Should it go to yoga first?

@MoteHue Suggested that it could be to do with the config merging in Antelope. If you think it would affect yoga as well, then I'll rebase

This isn't due to the config merging, it's just how {% raw %} tags work. The similar "bug" I've seen is that defining an option within an environment and a base config file will cause the lines to be duplicated.
Personally, I'd change this to the following because it's not immediately obvious that we'd need to keep that newline hanging around.
{% raw %}
ssl_ca_crt_file = {{ openstack_cacert }}
{% endraw %}

I've Yoga'd it and moved around the tags


Change Toast to snackbars in app.

Summary:
Snack bars look better than toast and disappear when activity is destroyed.
https://stackoverflow.com/questions/34432339/android-snackbar-vs-toast-usage-and-difference
Steps to reproduce:
Add a utils function in Utils.java

public static void showSnackbar(View view, String message) {
    Snackbar.make(view, message, Snackbar.LENGTH_SHORT).show();
}

Commons app version:
2.6.7-Debug
Screen-shots:

Would you like to work on the issue
Yes

@ujjwalagrawal17 Seems easy though, but you will need to take care of edge cases. Eg. As of now, the app shows a toast for each image which it could not cache (error in caching image), leading to number of toasts equal to the number of images failed to cache. You should figure out how to get past this issue, since showing 20 or merely 6 toasts continuously will definitely not a good UX.


Fix milestone evidence missing and Link Credit Transactions

#969 #973 #974 #975 #976
Did some minor layout cleanup, and restricted the credit transactions shown in Link Credit Transactions to related credit transactions only
Changelog:

Fixed milestone becoming overwritten after it's been received
Link Credit Transactions now only show records that involved the fuel supplier
Updated layout for consistency
Moved Link Credit Transactions table into a modal window to provide more context to the user
Code cleanup

 SFS | Restrict linking credit transactions list based on fuel supplier organization |3|

 SFS | Marking submission as received removes milestone description from title for P3A Milestone Evidence type |1|

 SFS | Adjust label when linking credit transaction |1|


Meta: Where can I find the actual Block Wave wallpaper?

Hi @drewswaycool , what do you mean by actual?

I think I didn't read deep enough into what this tool is/does. It appears that you can generate a background based off of theme colors etc..?

No worries. Yes, that's correct. You give it a set of colors (or use a built-in set), and it will generate themes for your tools as well as a matching background.


[Error] subscribe: topic name is not a non-empty string

I am running the default installation of ros indigo and when walking through the default [ROS tutorials](http://wiki.ros.org/ROS/Tuto
I installed the rosbridge_suite from: http://wiki.ros.org/rosbridge_suite/Tutorials/RunningRosbridge
When running the turtlesim example and the rosbridge server I end up with the following running nodes:
$ rosnode list
/my_turtle
/rosapi
/rosbridge_websocket
/rosout
/turtlesim

However, when I try to connect the ROS Control Center to localhost (which seems to work though), I end up with:

The terminal output for the rosbridge_suite reads:
[INFO] [WallTime:<PHONE_NUMBER>.687831] Client connected.  1 clients total.
[INFO] [WallTime:<PHONE_NUMBER>.912490] [Client 0] Subscribed to /rosout
[ERROR] [WallTime:<PHONE_NUMBER>.917653] [Client 0] [id: subscribe::6] subscribe: topic name is not a non-empty string

It seems like the ros nodes are not correctly retrieved and shown in the ROS Control Center, am I correct in assuming this currently encountered behaviour is incorrect?

I had the same issue. One thing to note is that the topic names must start with a capital letter in order to be displayed. For instance I had to change my imu message from imu_bosch/data to IMU/Data in order for it to display IMU on the side bar and Data as a sub category.

@pantor Enabling the advanced view doesn't seem to do anything for me either. Clicking the Enable Advanced View button gives no reaction and checking the Advanced View box under Settings doesn't do anything either.
Worse, if I set up a node called Tester that publishes a string to a topic /Test_group/Test_topic, I don't see any output under the control tab (regardless of Advanced View). This is also true if I publish anything to /battery.
I'm confused because rosbridge_suite shows me that a new client subscribes to /rosout whenever I refresh the browser page, but I only see the "There is nothing to show here..." alert, nor do I see any subscriptions to /battery or /Test_group/Test_topic.
Anything I can give you for debugging information?

Actually, it looks like this was a completely unrelated problem: https://github.com/RobotWebTools/roslibjs/issues/219
I changed bson from my pip installed version to the apt-get installed version. This fixed the problems I was experiencing above (including the advanced view one).


[3.1.0-RC2] Has been displayed unknown bootstrap's alert. affected by GroupACL?

Environment
Host

item
version

OS
unknown

GROWI
3.1.0-RC2

node.js
(snip use docker image)

npm
(snip use docker image)

Using Docker
yes

Using growi-docker-compose
yes

(Accessing https://{GROWI_HOST}/admin helps you to fill in above versions)
Client

item
version

OS
Windows 10

browser
Google Chrome 66.0.3359.181

How to reproduce? (再現手順)

login
enable GroupACL in admin page.
create page in personal space ( /user//memo/YYYY/MM/dd )

Page setting

[GroupACL] set public

What happens? (症状)

has been displayed unknown bootstrap's alert.

What is the expected result? (期待される動作)

not to display it, if there is nothing.

Note

same issue: #432

@kouki-o This would be resolved at v3.1.0 and I can't reproduce.
Please write the procedure to reproduce 100%.

OK, now I confirmed to reproduce, but not 100%...

This might be reproduced only when using Group ACL.
This doesn't occured when 'Public' grant.


Get and Send Ticket

When there are no agent available. M trying to get and send ticket using the below Code
visitorSDK
.getTicketForm()
.then(data => {
console.log('Ticket form data', data)
})
.catch(error => {
console.log('error')
})
But the above method is failing with response as below
reason: "Request failed"
type: "connection"
And If i try to send the ticket using below method
visitorSDK
.sendTicketForm({
name: 'John',
email<EMAIL_ADDRESS>subject: 'App support',
message: 'I have a problem with your app',
})
.then(() => {
console.log('Ticket sent')
})
.catch(error => {
console.log('error')
})
app is crashing with below error message
uncaught at gh
at e
at Gd
at N
at wd
at dp
at lp
TypeError: Cannot read property 'hide_trademark' of undefined
at fp (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:459428:61)
at blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:459535:26
at tryCatch (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:27973:19)
at Generator.invoke [as _invoke] (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:28146:24)
at Generator.prototype.(anonymous function) [as next] (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:28016:23)
at y (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:454536:17)
at Ue (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:454524:54)
at F (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:454707:9)
at blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:454653:59
at L (blob:http://localhost:8081/06b4645a-661b-4e35-a30b-cf85c7873a54:454654:10)
Kindly help me where am going wrong

Hi,
sadly sending tickets works only on web right now. This problem is related to fact that this library uses VisitorSdk that was created for web only. We manage to make it work on mobile by changing a code a little, but still most of functionalities won't work :(

Is there any workaround for this scenario.

Yes,
you can create your own backend service for creating tickets using our Rest Api.
You can find more information here: https://developers.livechatinc.com/docs/rest-api/#create-a-ticket
In case of any problems or questions, ask right away :)


Refactoring secret encryption

Overriding attributes can cause problems when working in the rails console. I'm closing this one then.