Assessment presentation

Some comments from me (overall looks great!):

it might be worth (for future beamer builds - NOT this year) to separate out the SRG response questions to the appropriate presentations.  Most do relate to the assessment, but others might be better suited in other presentations (e.g., the ovary histological one and sampling protocol one and catch data extraction deadline one seem to fit well with the data presentation).
first 'changes' slide second bullet: maybe just 'remove zero-sum recruitment deviation constraint ('simple' approach)' - not sure people will know what 'simple' means but I see we use it with figures so good to keep too but when in text throughout use quotes, i.e., 'simple'
first 'changes' slide third bullet: technically we updated pre-2019 survey data too (a couple changes to CVs were made) - may not even be worth bringing it up, but just so aware
-second to last 'changes' slide fourth bullet: only one parameter, the survey theta, was stuck on the bound, so not 'these'
it might be worth considering adding the prior figure that Ian sent us in issue 595 (https://github.com/pacific-hake/hake-assessment/issues/595#issue-550480621) just after talking about the prior (just after slide 13)
-second slide 'estimated quantities' last bullet: not sure what you mean by 'quite certainly'?  Do you mean the MLE and MCMC match up well?
-'estimates of 2014 and 2016 cohorts': the big change with the addition of the 2019 survey comps is the estimate of the 2017 year class (lower) relative to last years assessment (but not sure there is room on here for another comparison
'summary key cohorts': question will be what makes up the other 35% of biomass, so may want to include 2017 cohort , even if just in relation to the final three bullets about cohort % of population
one key summary point might be one of caution:  we have the three highest catches in the last three years and the 2010 and 2014 large cohorts are now ageing (mortality outweighing growth) such that biomass is trending downwards (which will continue without either a reduction in catch/fishing mortality or another big recruitment and no evidence that recent recruitments will be a boomer.  I'll get into this a bit more in the management talk, but seems like a summary of the assessment results in terms of current status. (sure we are trending toward the 'target' but we don't want to overshoot!)

@aaronmberger-nwfsc Thanks for taking a look. I agree with emphasizing the current state of high catch and no large incoming recruitments, so I'll add that to the summary. I'll also add Ian's figures for the DM stuff (I had forgotten about that figure).
For the % biomass by cohort I may make a whole slide which has them all for reference. Then there's no question what's going on.
I'll work on this today and possibly into tomorrow.

Thanks Chris and sorry for the late comments!  Please wait until tomorrow to work on any changes as none are crucial and the presentation is great even if you didn't get to any of them.  :)

Nice job, this is a long one. I really like how you put the document figure reference at the top of the slide. Also, feel free to ignore the following comments as they are trivial.

Could add last year's weight-at-age figure before slide 8 to allow people to flip between them
Switch slides 10 and 11
Slide 13, I believe it was just the survey weighting parameter that was hitting the bound not both
Slide 35 - remove "So "
Slide 60 the passive voice is quite strong here and I had to re-read "have been dropping since" a few times to get it, sorry my brain is slow :(

Given the high interest in cohort strength on the JMC call (and the subsequent Canadian JMC call) I added a slide which gives an overview of the cohort biomass estimates with uncertainty for the terminal year. The table is sorted by cohort strength.
It used the posteriors in base.model$extra.mcmc$natselwt.prop
Does this seem like a good addition? If so, I want to make sure I understand the values in that output. My interpretation is that they are proportions of biomass with selectivity applied, which is why they only sum to 96.1%. Is that right? (@aaronmberger-nwfsc, @kellijohnson-NOAA)

Thx

I like the plot, not so sure if you need the plot and the table, though as @andrew-edwards mentioned it is better to present information in multiple ways. Regarding the values not adding to 100%, I am almost certain that is because there is no constraint that the median for each age will come from the same row, where all rows will sum to one.

Yes, that makes sense to me and I like the plot.  I think we get the same thing with selectivity (or any sum to one set of proportions for that matter) when summarizing values from posterior draws.  I was a bit surprised that it was that far off ~4%, but shape of posterior and summarizing metric (median, mean, etc.) would influence this I would think.  I wouldn't even mention that they don't sum to one, but have that explanation ready in case someone asks.


CSV reader/writer

Do you think a CSV reader would be worthwhile?
ogr2ogr supports it: https://gdal.org/drivers/vector/csv.html
For example I have a dataset like this:
Address,Type,Datetime,Latitude,Longitude,Report Location,Incident Number
904 7th Av,Car Fire,05/22/2019 12:55:00 PM,47.6069,-122.329051,POINT (-122.329051 47.6069),F190051945
9610 53rd Av S,Aid Response,05/22/2019 12:55:00 PM,47.515984,-122.266529,POINT (-122.266529 47.515984),F190051946

There are multiple ways that the csv might contain geometry data in the wild, some some thought about configuration is due. Two popular ones I've seen are:

If it's a table of points, lat and lon columns are specified.
wkt column

My real world example above actually has both!

I use the OGR CSV driver regularly, so yes, it would be worthwile.


maven-metadata.xml has incorrect latest

Describe the bug
https://nexus.frankframework.org/repository/frank-flow/org/ibissource/frank-flow/maven-metadata.xml has <latest>2.27.1-20240410.190322</latest> and <version>2.27.1-20240501.205713</version>.
Latest should also contain 2.27.1-20240501.205713

https://nexus.frankframework.org/repository/frank-flow/org/frankframework/frank-flow/maven-metadata.xml is now available and used by the Frank!Runner


Gurobi Optimizer

hi
is it possible to run this code without installing the Gurobi Optimizer?

hi
I installed nlopt library so I can use it instead of the gurobi optimizer. I also changed the CMakeLists.txt accordingly.
Then, I tried to complied and got an error message: OctopusSearch::run requires 5 arguments but given only 3 in solver_nlopt.cpp


[WIP]Add NULS support

[x] Implement functionality in C++. Put it in a subfolder of src/.

[x] Address (if necessary)
[x] Transaction (if necessary)
[x] Signer

[x] Write unit tests. Put them in a subfolder of tests/.
[x] Mnemonic phrase - > Address derivation test. Put this test in the CoinTests.cpp file
[x] Add relevant constants in TWCoinType, TWP2SHPrefix, TWEthereymChainID, TWHRP, etc., as necessary.
[x] Return correct curve and purpose in src/Coin.cpp.
[x] Implement address validation and derivation in src/Coin.cpp.
[x] Implement coin configuration src/include/TWCoinTypeConfiguration.cpp.
[x] Write interface header in include/TrustWalletCore and implement the interface in src/interface.

[x] Address interface (if necessary).
[x] Signing interface.

[ ] Validate generated code in Android an iOS projects. Write integration tests for each.

encode64LE(val & 0xffffffffffff, data) will write 8 byte data to buffer.
So we use encode48LE to write 6 byte number.

Thanks for the new pull request, could you please add a Kotlin or Swift transaction signing test case?

Hi, can you fix CI?

You might need to add a test case in CoinType+Address.swift to fix the iOS CI

@hewigovens max amount transfer plan support. check tests/NULS/TransactionPlanTest.cpp


Enforce unique tags

Is your feature request related to a problem? Please describe.
Currently, tags are not unique:

Since we intend to provide the ability to filter flags by tag labels for #430, we need clearer UX for setting tags in the Flagsmith UI.
Describe the solution you'd like

Enforce a unique label constraint in the Django model.
Add a data migration to merge existing duplicate tags.

Describe alternatives you've considered
Filtering by tag ID in SDK would require UI changes to communicate the tag IDs to user and overcomplicate the user experience.

A quick query on the production database shows that there are only 5 instances where we have non-unique labels in a project. 3 of which are clearly test data.


Update port info

Actually we still use :5044 in the product. I thought we had switched to :443, but obviously not yet. We should make this change, but we cannot merge this PR until the product uses 443

https://mulesoft.slack.com/archives/C02HGAD2E/p1595289839422300


using a wrench on a huge diesel sometimes crashes the game

I used the create wrench on the create diesel generators huge diesel engine to make the pipe connect to it (the pipe was already in position to connect), and it sometimes crashed my game. I believe no progress was lost, and the connection went through (it was there when I relaunched). I don't know what causes it, but it happened twice on the same block (I undid the connection and redid it).
Now I've wrenched diesel engines on the other side of the pipe and there was no crash, so it might have something to do with the pipes getting updated and not liking it.
edit: putting in a shaft into the diesel about to run crashed the game.

I'm not able to reproduce it on new version


riak_kv_put_fsm:execute_remote doesn't include schedule_timeout Raw [JIRA: RIAK-2896]

Finding the following in the console log when cluster nodes are slow:
2016-09-23 02:00:59.599 [warning] <0.7703.3186>@riak_repl_util:wait_for_response:189 Timed out after 1 minute doing put on replicated object
2016-09-23 02:01:59.600 [warning] <0.7703.3186>@riak_repl_util:do_repl_put:160 put fsm did not exit on schedule

(https://github.com/basho/riak_repl/blob/develop/src/riak_repl_util.erl#L180-L190)
Shows that we're erroring out during the wait_for_response call in do_repl_put.  Tracing back to (https://github.com/basho/riak_repl/blob/develop/src/riak_repl_util.erl#L146-L148)
riak_kv_put_fsm:start_link() converges to riak_kv_put_fsm:start().  From riak_kv_put_fsm:init path flow ends up in the riak_kv_put_fsm:execute() code block: (https://github.com/basho/riak_kv/blob/develop/src/riak_kv_put_fsm.erl#L514-L528)
Since repl puts are not coordinated execute_remote is called: (https://github.com/basho/riak_kv/blob/develop/src/riak_kv_put_fsm.erl#L514-L528)
From the code flow:
(https://github.com/basho/riak_kv/blob/develop/src/riak_kv_put_fsm.erl#L609-L616)
If the node is slow, the riak_kv_node_put call (https://github.com/basho/riak_kv/blob/develop/src/riak_kv_put_fsm.erl#L609) does not respond within the 60 second timeout set in the riak_repl_util:wait_for_response as there is no TRef/monitoring call setup and the reference object is passed in asis with no Timeout set.
Even if the riak_kv_node_put returns after 60 seconds, the riak_repl_util:do_repl_put has moved on to waiting for the FSM to exit:
(https://github.com/basho/riak_repl/blob/develop/src/riak_repl_util.erl#L155-L162)
This then can potentially leave an orphaned FSM while also placing additional work load on the cluster as the repl put operation is retried possibly multiple times.

Fixed by #1511 - merged into develop-2.2


not support jdk17？

Exception in thread "main" java.lang.ExceptionInInitializerError
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not "opens java.lang" to unnamed module @396f6598
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:354)
	at java.base/java.lang.reflect.AccessibleObject.checkCanSetAccessible(AccessibleObject.java:297)
	at java.base/java.lang.reflect.Method.checkCanSetAccessible(Method.java:199)
	at java.base/java.lang.reflect.Method.setAccessible(Method.java:193)
	at ma.glasnost.orika.converter.builtin.CloneableConverter.<init>(CloneableConverter.java:64)
	at ma.glasnost.orika.converter.builtin.CloneableConverter$Builtin.<init>(CloneableConverter.java:221)
	at ma.glasnost.orika.converter.builtin.BuiltinConverters.register(BuiltinConverters.java:135)
	at ma.glasnost.orika.impl.DefaultMapperFactory.build(DefaultMapperFactory.java:1278)
	at ma.glasnost.orika.impl.DefaultMapperFactory.getMapperFacade(DefaultMapperFactory.java:881)

Process finished with exit code 1

Hi @a364176773  , Sadly same issue was open in 2021 and Orika hasn't response for that
u can see there is workaround in that discussion , #377

@a364176773 There is a work around:

Just add this jvm args, here is the code if you are using gradle
bootRun {   jvmArgs = ["--add-opens=java.base/java.lang=ALL-UNNAMED"] }

Sorry, I think this method is only a temporary solution, not a real support for jdk17

I agree @a364176773!
Looks like the authors gave up Orika, unfortunately.
Looking to replacements already, no new projects with Orika from now on.

@thiagolvlsantos we managed to replace Orika with https://mapstruct.org/ successfully. It was straight forward but that depends on the complexity of your mappings.

duplicate of https://github.com/orika-mapper/orika/issues/377

@Chr3is mapstruct is too cumbersome and requires defining conversion classes for each pair of POJOs

When using .parallelStream(),  the orika maper is not working
ma.glasnost.orika.MappingException: ma.glasnost.orika.MappingException: While attempting the following mapping:
Error occurred: java.lang.ClassCastException:

@thiagolvlsantos we managed to replace Orika with https://mapstruct.org/ successfully. It was straight forward but that depends on the complexity of your mappings.

MapStruct always requires the writing of mappers.


Contributions to "New to RSE"

New content
Are you requesting or providing new content? (replace [ ] with [x] to check the relevant box in the list below)

[ ] Content request: You would like to see new content covering a specific topic added to the resource
[x] Providing content: You are providing some new content for the RSEToolkit (conent to be provided via a pull request)
[ ] Other new content-related query: You have some other query related to content not currently present in the resource (e.g. a question about whether some specific material might be useful/relevant)

New content information
Hi! I'm interested in adding the following new/updated content:

I'm wondering where open source can fit into these docs? E.g., reading about the different flavors of RSEs the scope is limited to basically provided as a service by a university group vs. embedded in a lab. What about representation for people that provide services via company (e.g., Million Concepts by Chase Million or Dreaming Spires) or RSEng that aren't in a lab or university group but heavily involved in open source development? I'd also want to add to this page something about how students or more traditional roles can be acting as RSEng, and that a graduate degree is common but not required.

I can start here and extend! I think it would be cool if each major org had a link to their "story" - e.g., the UK group already has their link, but US-RSE now has one too :) https://us-rse.org/2022-02-06-a-brief-history-of-usrse/

Also just occurred to me - there might be some overlap between here and https://cosden.github.io/intersect-web/? How could we work together on that? ping @cosden

Also just occurred to me - there might be some overlap between here and https://cosden.github.io/intersect-web/? How could we work together on that? ping @cosden

Thanks @vsoch - I'd be curious how we can collaborate as well. The current project site for INTERSECT (RSE training development and delivery) is here https://intersect-training.github.io/.

Awesome! Please use me as a worker bee if needed, I'm here to help.

Thanks for these suggestions @vsoch. Definitely happy to include material that recognises other RSE routes/roles/activities. The current "What is an RSE" material that you linked to feels like it could perhaps be made a bit clearer and more structured.
While I suppose there are many differently structured RSE roles in place and it's difficult to cover everything, maybe we can have an "Types of RSE role" section or something along these lines that lists various different models including those that you highlight? Perhaps including:

University-based - central team
University-based - embedded within research group/lab
National lab (non-university)
Commercial research / R&D-based RSE team
Open source research software developers in industry
...?

Not sure how well this fits in with what you had in mind - just a few thoughts but if you're happy to add something along the lines of what you were thinking, that would be fantastic - I'm happy to contribute too.
Linked to this, I'd like to add something along the lines of "The RSE Continuum" (tagging @SimonHettrick since we're currently thinking about this) which presents the scale of RSE roles ranging from those at one end that look very similar to industry developers to those at the other end that look very similar to traditional university research roles.
Re @cosden's follow-up, definitely interested to look at opportunities to collaborate - thanks for the link to INTERSECT.

Yes I like that! In my talk I gave recently I talked about "flavors" and they were more akin to the list you provided. Once we hear from @SimonHettrick I can take a shot at updating that page with a listing or continuum of what we decide. Perhaps within each of those groups there is a continuum, or more generally the continuum can be applied to any kind of RSE flavor?

I think we decided when thinking about this that there are indeed many "continua" in RSE although in a slightly different context to the level of the different RSE flavours....this could end up getting somewhat complex! 🙂


Error when upgrade from 0.13.1 to latest version

What happened?
After upgrade, all my nodes return this error :
2023-01-20 10:15:50,010 ERROR: create_config_service failed
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/patroni/dcs/kubernetes.py", line 890, in _create_config_service
    if not self._api.create_namespaced_service(self._namespace, body):
  File "/usr/lib/python3/dist-packages/patroni/dcs/kubernetes.py", line 468, in wrapper
    return getattr(self._core_v1_api, func)(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/patroni/dcs/kubernetes.py", line 404, in wrapper
    return self._api_client.call_api(method, path, headers, body, **kwargs)
  File "/usr/lib/python3/dist-packages/patroni/dcs/kubernetes.py", line 373, in call_api
    return self._handle_server_response(response, _preload_content)
  File "/usr/lib/python3/dist-packages/patroni/dcs/kubernetes.py", line 203, in _handle_server_response
    raise k8s_client.rest.ApiException(http_resp=response)
patroni.dcs.kubernetes.K8sClient.rest.ApiException: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'e47d519f-f244-47a4-ad9f-201cbe928c4a', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f182df09-64d8-40dd-8faa-445be223320d', 'Date': 'Fri, 20 Jan 2023 10:15:50 GMT', 'Content-Length': '300'})
HTTP response body: b'{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"services is forbidden: User \\"system:serviceaccount:opennms:timescaledb\\" cannot create resource \\"services\\" in API group \\"\\" in the namespace \\"stage\\"","reason":"Forbidden","details":{"kind":"services"},"code":403}\n'

Did you expect to see something different?
Yes, no error in my timescaledb nodes
How to reproduce it (as minimally and precisely as possible):

Use this timescaledb-ha image : pg12.13-ts2.9.1-latest
Install the chart timescaledb-single in version 0.13.0
try to upgrade to latest or others 0.1X.X
And voilà ! You have same error in nodes

Environment

Which helm chart and what version are you using?

TimescaleDB-single in 0.13.1 at start and I try to upgrade to 0.30.0

What is in your values.yaml ?

affinity: {}
backup:
  enabled: true
  env: null
  envFrom: null
  jobs:
    - name: full-weekly
      schedule: 12 02 * * 0
      type: full
    - name: incremental-daily
      schedule: 12 02 * * 1-6
      type: incr
  pgBackRest:
    compress-type: lz4
    process-max: 4
    repo1-cipher-type: none
    repo1-retention-diff: 2
    repo1-retention-full: 2
    repo1-s3-endpoint: s3.amazonaws.com
    repo1-s3-region: eu-west-1
    repo1-type: s3
    start-fast: 'y'
  pgBackRest:archive-get: {}
  pgBackRest:archive-push: {}
  resources: {}
bootstrapFromBackup:
  enabled: false
  repo1-path: null
  secretName: pgbackrest-bootstrap
callbacks:
  configMap: null
clusterName: stage
debug:
  execStartPre: null
env:
  - name: TIMESCALEDB_TELEMETRY
    value: 'off'
envFrom: null
fullnameOverride: '{{ .Release.Name }}'
image:
  pullPolicy: Always
  repository: timescale/timescaledb-ha
  tag: pg12.13-ts2.9.1-latest
networkPolicy:
  enabled: false
  ingress: null
  prometheusApp: prometheus
nodeSelector: {}
patroni:
  bootstrap:
    dcs:
      loop_wait: 10
      maximum_lag_on_failover: 33554432
      postgresql:
        parameters:
          archive_command: /etc/timescaledb/scripts/pgbackrest_archive.sh %p
          archive_mode: 'on'
          archive_timeout: 1800s
          autovacuum_analyze_scale_factor: 0.02
          autovacuum_max_workers: 10
          autovacuum_naptime: 5s
          autovacuum_vacuum_cost_limit: 500
          autovacuum_vacuum_scale_factor: 0.05
          hot_standby: 'on'
          log_autovacuum_min_duration: 1min
          log_checkpoints: 'on'
          log_connections: 'on'
          log_disconnections: 'on'
          log_line_prefix: '%t [%p]: [%c-%l] %u@%d,app=%a [%e] '
          log_lock_waits: 'on'
          log_min_duration_statement: 1s
          log_statement: ddl
          max_connections: 100
          max_prepared_transactions: 150
          shared_preload_libraries: timescaledb,pg_stat_statements
          ssl: 'on'
          ssl_cert_file: /etc/certificate/tls.crt
          ssl_key_file: /etc/certificate/tls.key
          tcp_keepalives_idle: 900
          tcp_keepalives_interval: 100
          temp_file_limit: 1GB
          timescaledb.passfile: ../.pgpass
          unix_socket_directories: /var/run/postgresql
          unix_socket_permissions: '0750'
          wal_level: hot_standby
          wal_log_hints: 'on'
          max_locks_per_transaction: 2200
          max_parallel_workers: 14
          max_worker_processes: 32
          timescaledb.max_background_workers: 16
        use_pg_rewind: true
        use_slots: true
      retry_timeout: 10
      ttl: 30
    method: restore_or_initdb
    post_init: /etc/timescaledb/scripts/post_init.sh
    restore_or_initdb:
      command: >
        /etc/timescaledb/scripts/restore_or_initdb.sh --encoding=UTF8
        --locale=C.UTF-8
      keep_existing_recovery_conf: true
  kubernetes:
    role_label: role
    scope_label: cluster-name
    use_endpoints: true
  log:
    level: WARNING
  postgresql:
    authentication:
      replication:
        username: standby
      superuser:
        username: postgres
    basebackup:
      - waldir: /var/lib/postgresql/wal/pg_wal
    callbacks:
      on_reload: /etc/timescaledb/scripts/patroni_callback.sh
      on_restart: /etc/timescaledb/scripts/patroni_callback.sh
      on_role_change: /etc/timescaledb/scripts/patroni_callback.sh
      on_start: /etc/timescaledb/scripts/patroni_callback.sh
      on_stop: /etc/timescaledb/scripts/patroni_callback.sh
    create_replica_methods:
      - pgbackrest
      - basebackup
    listen: <IP_ADDRESS>:5432
    pg_hba:
      - local     all             postgres                              peer
      - local     all             all                                   md5
      - hostssl   all             all                <IP_ADDRESS>/32       md5
      - hostssl   all             all                ::1/128            md5
      - hostssl   replication     standby            all                md5
      - hostssl   all             all                all                md5
      - host      all             all                all                md5
    pgbackrest:
      command: /etc/timescaledb/scripts/pgbackrest_restore.sh
      keep_data: true
      no_master: true
      no_params: true
    recovery_conf:
      restore_command: /etc/timescaledb/scripts/pgbackrest_archive_get.sh %f "%p"
    use_unix_socket: true
  restapi:
    listen: <IP_ADDRESS>:8008
persistentVolumes:
  data:
    accessModes:
      - ReadWriteOnce
    annotations: {}
    enabled: true
    mountPath: /var/lib/postgresql
    size: 25Gi
    subPath: ''
  wal:
    accessModes:
      - ReadWriteOnce
    annotations: {}
    enabled: true
    mountPath: /var/lib/postgresql/wal
    size: 5Gi
    storageClass: null
    subPath: ''
pgBouncer:
  config:
    default_pool_size: 12
    max_client_conn: 500
    pool_mode: transaction
    server_reset_query: DISCARD ALL
    client_tls_sslmode: prefer
    ignore_startup_parameters: extra_float_digits
  enabled: true
  pg_hba:
    - local     all postgres                   peer
    - host      all postgres,standby <IP_ADDRESS>/0 reject
    - host      all postgres,standby ::0/0     reject
    - hostssl   all all              <IP_ADDRESS>/0 md5
    - hostssl   all all              ::0/0     md5
    - host      all all              <IP_ADDRESS>/0 md5
    - host      all all              ::0/0     md5
  port: 6432
  userListSecretName: null
podAnnotations: {}
podLabels: {}
podManagementPolicy: OrderedReady
podMonitor:
  enabled: false
  interval: 10s
  path: /metrics
postInit:
  - configMap:
      name: custom-init-scripts
      optional: true
  - secret:
      name: custom-secret-scripts
      optional: true
prometheus:
  args: []
  enabled: false
  env: null
  image:
    pullPolicy: Always
    repository: quay.io/prometheuscommunity/postgres-exporter
    tag: v0.11.1
  volumeMounts: null
  volumes: null
rbac:
  create: true
readinessProbe:
  enabled: true
  failureThreshold: 6
  initialDelaySeconds: 5
  periodSeconds: 30
  successThreshold: 1
  timeoutSeconds: 5
replicaCount: 3
resources: {}
secrets:
  certificate:
    tls.crt: ''
    tls.key: ''
  certificateSecretName: certificate
  credentials:
    PATRONI_REPLICATION_PASSWORD: ''
    PATRONI_SUPERUSER_PASSWORD: ''
    PATRONI_admin_PASSWORD: ''
  credentialsSecretName: credentials
  pgbackrest:
    PGBACKREST_REPO1_S3_BUCKET: ''
    PGBACKREST_REPO1_S3_ENDPOINT: s3.amazonaws.com
    PGBACKREST_REPO1_S3_KEY: ''
    PGBACKREST_REPO1_S3_KEY_SECRET: ''
    PGBACKREST_REPO1_S3_REGION: ''
  pgbackrestSecretName: pgbackrest
service:
  primary:
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: '4000'
      service.beta.kubernetes.io/aws-load-balancer-internal: 'true'
      service.beta.kubernetes.io/aws-load-balancer-type: nlb
    labels: {}
    nodePort: null
    port: 5432
    spec: {}
    type: LoadBalancer
  replica:
    annotations:
      service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: '4000'
      service.beta.kubernetes.io/aws-load-balancer-internal: 'true'
      service.beta.kubernetes.io/aws-load-balancer-type: nlb
    labels: {}
    nodePort: null
    port: 5432
    spec: {}
    type: LoadBalancer
serviceAccount:
  annotations: {}
  create: true
  name: null
sharedMemory:
  useMount: true
timescaledbTune:
  args: {}
  enabled: true
tolerations: []
topologySpreadConstraints: []
version: null
global:
  cattle:
    systemProjectId: p-rg64l
loadBalancer:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-internal: 'true'
    service.beta.kubernetes.io/aws-load-balancer-type: nlb
  enabled: false
replicaLoadBalancer:
  annotations:
    service.beta.kubernetes.io/aws-load-balancer-internal: 'true'
    service.beta.kubernetes.io/aws-load-balancer-type: nlb

Kubernetes version information:
kubectl version
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.8", GitCommit:"4a3b558c52eb6995b3c5c1db5e54111bd0645a64", GitTreeState:"clean", BuildDate:"2021-12-15T14:52:11Z", GoVersion:"go1.16.12", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22+", GitVersion:"v1.22.15-eks-fb459a0", GitCommit:"be82fa628e60d024275efaa239bfe53a9119c2d9", GitTreeState:"clean", BuildDate:"2022-10-24T20:33:23Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:
insert how you created your cluster: Rancher

Anything else we need to know?: I saw the same error here : https://github.com/timescale/helm-charts/issues/405 But the thread is marked as resolved. But no real solution is proposed to resolve this thread.
I saw the problem is with patroni but I don't Know if timescaledb-ha images using only postgres 12 version are patched

This error is a Patroni error that is fixed here.  That Patroni fix was merged into the timescaledb-ha image version timescale/timescaledb-ha:pg13.9-ts2.9.2-p0.  You will need to update your timescaledb-ha image for that message to go away.

@nhudson thanks I test that. This image have the postgres 12 version on it ? (settings the correct parameter in the value.yaml)

The same error here (with the newest version of the chart (0.33.1). I did not want to use other image, so I had to create Role and RoleBinding with these values:
cat <<EOF | kubectl apply --context <your_context> -f -
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  namespace: <your_namespace>
  name: timescaledb-patch-to-remove
rules:
- apiGroups: [""] # "" indicates the core API group
  resources: ["services"]
  verbs: ["create"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: timescaledb-patch-binding
  namespace: <your_namespace>
subjects:
- kind: ServiceAccount
  name: <your_name>
  namespace: <your_namespace>
roleRef:
  kind: Role
  name: timescaledb-patch-to-remove
  apiGroup: rbac.authorization.k8s.io
EOF

@nhudson It's not normal to use a specific image with a patch not deployed in all new timescaledb-ha tags. Do we have a date or something for when and if this will be rolled out to all future timescaledb-ha tags?

Same error with pg14.6-ts2.9.2-p0 and pg14.6-ts2.9.1-patroni-static-primary-p2. Any image on pg14.6 fixing this problem?

Any news about the publication of patroni patch in all new timescaledb-ha images without apply patch or use very specific timescaledb-ha image ? @nhudson

Same error with timescaledb-ha:pg12.14-ts2.9.3-latest published 4 days ago 😢

@tomislater patch fix the problem. But it's not a solution : normally, with a helm chart, we do not to do this patches.
It's possible to add this directly in the chart to fix the problem in next version ? @feikesteenbergen

@throrin19 looks like we are waiting on the Patroni images to become available in the Debian repo.  https://github.com/timescale/timescaledb-docker-ha/pull/343

Is there an update date of patroni in the image timescaledb-ha since a month?
This problem seems to be blocking for most of the current and future users of this chart but no solution seems to arrive quickly (except the role tweak which is to be done in manual but not available on the chart itself).

I tried with the latest image that is currently available (pg14.6-ts2.9.3-patroni-dcs-failsafe-p0) and the problem is resolved!

@GeorgFleig : It's not a final image, it is a specific tag with the fix. Ok it resolves the problem but it's not the solution, the solution is : with default tags used in this charts, patroni works fine without patch in kubernetes

Still getting this error in the timescaledb pod logs.
Any news on when the container images that have the patroni fix will be referenced in the helm chart?

@pfrydids You can forgot about this, the project seems not maintained...

@throrin19 oh no! A real shame as it seems to be working quite well otherwise

@pfrydids I use it in my organisation, but nobody have response to their issues like 6 months.

Well that's a shame. I was integrating this into my cluster and saw this issue occurring but if the project is dead I'll have to look for some alternative. :(

@DreamwareDevelopment you can fix that with the patch of roles and rolebindings published by @tomislater https://github.com/timescale/helm-charts/issues/554#issuecomment-1406256190


drivers: usb_dc_rpi_pico: don't call usb_dc_ep_start_read() on transf…

…er-managed endpoints during setup and properly reset next_pid.
The previous behaviour led to an issue where we already expected data1 on the first transfer instead of data0. The DesignWare USB DC actually implements the same behaviour. Also, the next_pid flag has to be reset on setting up the endpoint.
Fixes: #66283

Is there still anything missing from my side or what's the status on this PR?


Revert "[must-gather] Drop our custom log collection in favor of must-gather"

Reverts openstack-k8s-operators/ci-framework#857
This revert is just for testing purpose.

/hold

@lewisdenny is this ready for review ? I guess not based on the description above but ci bot assigned me for review and it showed up in my notifications.
can you please set to draft ? Or, do we really want to revert and if so why?

recheck

@lewisdenny is this still needed for your tests? Or can we close it? :)


Adding Optional Text Preprocessing Steps

Adding extra text pre-processing options might come in handy for different use cases and might improve our model performances on some datasets. These options can be implemented:

Removal of Emojis,
Removal of URLs,
Removal of HTML Tags,
Removal of Digits

Since these steps applied on raw strings before tokenization comes with another question, where shall we implement them? bblock.util.py maybe?

Can you send the snippet used for each. I believe they can be added as tokenizer exception rules

Emoji Removal:
import re
def remove_emoji(string):
    emoji_pattern = re.compile("["
                           u"\U0001F600-\U0001F64F"  # emoticons
                           u"\U0001F300-\U0001F5FF"  # symbols & pictographs
                           u"\U0001F680-\U0001F6FF"  # transport & map symbols
                           u"\U0001F1E0-\U0001F1FF"  # flags (iOS)
                           u"\U00002702-\U000027B0"
                           u"\U000024C2-\U0001F251"
                           "]+", flags=re.UNICODE)
    return emoji_pattern.sub(r'', string)

Text:
remove_emoji("bugün forvetler 🔥🔥")
Output:
bugün forvetler
Text:
remove_emoji("Komedi😂")
Output:
Komedi
URL Removal:
import re
def remove_urls(string):
    url_pattern = re.compile(r'https?://\S+|www\.\S+')
    return url_pattern.sub(r'', string)

Text:
remove_urls('Şu adresten bulabilirsin: https://www.imdb.com/title/tt0050083/')
Output:
Şu adresten bulabilirsin:
HTML Tags Removal:
import re

def remove_html(string):
    html_pattern = re.compile('<.*?>')
    return html_pattern.sub(r'', string)

text = """                </span>
            </div>
        </div>
    </div>
      </div>
  <script>
    if ('csm' in window) {
      csm.measure('csm_TitleReviewsAndPopularityWidget_finished');
    }
  </script>
    </div>"""

remove_html(text)
Output:

    if ('csm' in window) {
      csm.measure('csm_TitleReviewsAndPopularityWidget_finished');
    }

Digit Removal:
import re

def remove_digit(string):
    return re.sub(r'\d+', '', string)

Text:
remove_digit('20 kişi saat 12 gibi geldi')
Output:
 kişi saat  gibi geldi

Note to self: Should be done in a general way, allowing users to add their own custom preprocessing steps if necessary.


fix #69 (pt 1)

Changes Unknown when pulling c2d7af64f2000bc8e06ac1ed1bc8af1944e50fca on subscribable-params into ** on master**.


AWS S3 Connector and Authentication Module

Thanks @gauravkrshah
I just need to add the links to the Marketplace, once they are released, and then I can publish.
Please let me know when you are ready to go.
Mark

Component IDs have been assigned. Publishing.

Component IDs have been assigned. Publishing.


Sgroup

What does this implement/fix? Explain your changes.
Adds SubstanceGroup to the SWIG wrappers so we can work with V3000 mol blocks
Any other comments?
Also added overloads for QueryAtom::setQuery

We should add java and c# tests here as well.

@bp-kelley I can add a Java test easily enough, but there are currently no tests for the C# wrappers in RDKit.   Before adding any C# tests I think you'd at least need to update the C# compiler from mono to dotnet and put in place xunit testing.  That's quite a bit of CMake work and is probably best to do in another PR.  I can remove SubstanceGroup.i from the C# wrappers if not having a test is a problem.

I can remove SubstanceGroup.i from the C# wrappers if not having a test is a problem.

My two cents: it's not a problem given that we don't have convincing C# tests for anything else
It'd be great to put C# tests in place for everything (and to improve the java tests), but that's clearly not for this PR

There are some c# tests, I’ve been meaning to add more.  This might be a good time to start.

I've added a Java test.  It was worth it as I caught a "free(): invalid pointer error" from SubstanceGroup#getAtoms()- the SWIG vector wrapper was freeing the returned reference.
@bp-kelley I don't really want to add any C# tests to the PR as the work is being done for Schrodinger and that's not something they need.  I put in the change to the C# wrapper as it was trivial.  I understand if you're not comfortable with the lack of testing, but, if so, I should just revert the change to the C# wrapper and do the tests in another PR.
I don't see any C# tests, just the main methods in test.cs and RDKitCSharpTest/Program.cs.  Am I missing something?

@jones-gareth  I can hold off on the C# test I haven't added them for my own stuff anyway!


Resource Management

SRM Issue: See in SRM
SRM Status: New
Detection Method: Static Analysis
First seen on 09.02.2024
Location: package.json:14
Tool: GitHub Advanced Security
Tool Code: Resource Management
CWE: CWE 399 - Resource Management Errors (MITRE: https://cwe.mitre.org/data/definitions/399.html)
Severity: Critical
Training link: See training
Description:
N/A
Evidences
Tool: GitHub Advanced Security
Tool Code: BDSA-2020-0604: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Intelligent/BDSA-2020-0604: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityToolVersion: 0.1.8
githubSecurityCreateDate: 2023-08-22T07:08:41Z
Descriptor: BDSA-2020-0604: js-bson
Contextual Description:
View in GitHub
BDSA BDSA-2020-0604 Score 7.9/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Technical Description
The serializeInto function in lib/bson/parser/serializer.js allows objects which have an unknown _bsontype value to be serialized as a document instead of the intended BSON type. An attacker could exploit this vulnerability by sending a specially crafted object that will be serialized in an unintended way and result in unexpected behavior such as data disclosure.
Multiple CVEs have been assigned for this vulnerability.
View BDSA record | View CVE record
Base Score Metrics (CVSS v3.x Metrics)

Attack vector
NETWORK
Availability
NONE

Attack complexity
LOW
Confidentiality
HIGH

Integrity
HIGH
Scope
UNCHANGED

Privileges required
NONE
User interaction
NONE

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:U/RL:O/RC:C
Published on April 01, 2020
Last Modified April 01, 2020
Disclosure March 24, 2020
Exploit Available -
Vulnerability Age 1351 Days.
Solution
Fixed in version 1.1.4 by this commit.
Fixed in version 4.0.2 by this commit.
Workaround
No Workaround
Policy violations
Policy name:	Medium Vulnerability Count more than 0 for lejouni/sampleapp
Policy description:	-
Policy severity:	MAJOR
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: BDSA-2020-4750: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Intelligent/BDSA-2020-4750: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityToolVersion: 0.1.8
githubSecurityCreateDate: 2023-08-22T07:08:41Z
Descriptor: BDSA-2020-4750: js-bson
Contextual Description:
View in GitHub
BDSA BDSA-2020-4750 Score 4.3/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Technical Description
The vulnerability arises when an objects _bsontype  contains an invalid data type and the object is serialized. This will lead to the object being serialized as a document rather than of BSON type.
View BDSA record | View CVE record
Base Score Metrics (CVSS v3.x Metrics)

Attack vector
NETWORK
Availability
NONE

Attack complexity
HIGH
Confidentiality
LOW

Integrity
LOW
Scope
UNCHANGED

Privileges required
NONE
User interaction
NONE

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N/E:P/RL:O/RC:C
Published on March 01, 2022
Last Modified July 04, 2023
Disclosure March 24, 2020
Exploit Available March 24, 2020
Vulnerability Age 652 Days.
Solution
Fixed in version 1.1.4 by this commit.
The latest stable releases can be found here.
Workaround
No Workaround
Policy violations
Policy name:	Medium Vulnerability Count more than 0 for lejouni/sampleapp
Policy description:	-
Policy severity:	MAJOR
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: CVE-2020-7610: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Intelligent/CVE-2020-7610: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityToolVersion: 0.1.10
githubSecurityCreateDate: 2023-06-09T08:19:23Z
Descriptor: CVE-2020-7610: js-bson
Contextual Description:
View in GitHub
NVD CVE-2020-7610 (BDSA-2020-0604) Score 9.8/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Description
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended BSON type.
View BDSA record | View CVE record
Base Score Metrics (CVSS v3.x Metrics)

Attack vector
NETWORK
Availability
HIGH

Attack complexity
LOW
Confidentiality
HIGH

Integrity
HIGH
Scope
UNCHANGED

Privileges required
NONE
User interaction
NONE

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published on March 30, 2020
Last Modified April 01, 2020
Disclosure -
Exploit Available -
Vulnerability Age 1165 Days.
Solution
No Solution
Workaround
No Workaround
Policy violations
Policy name:	New policy
Policy description:	-
Policy severity:	CRITICAL
Policy name:	AF Medium Vulns Rapid
Policy description:	-
Policy severity:	BLOCKER
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: CVE-2019-2391: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Intelligent/CVE-2019-2391: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityToolVersion: 0.1.10
githubSecurityCreateDate: 2023-06-09T08:19:23Z
Descriptor: CVE-2019-2391: js-bson
Contextual Description:
View in GitHub
NVD CVE-2019-2391 (BDSA-2020-4750) Score 5.4/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Description
Incorrect parsing of certain JSON input may result in js-bson not correctly serializing BSON. This may cause unexpected application behaviour including data disclosure. This issue affects: MongoDB Inc. js-bson library version 1.1.3 and prior to.
View BDSA record | View CVE record
Base Score Metrics (CVSS v3.x Metrics)

Attack vector
NETWORK
Availability
NONE

Attack complexity
LOW
Confidentiality
LOW

Integrity
LOW
Scope
UNCHANGED

Privileges required
LOW
User interaction
NONE

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Published on March 31, 2020
Last Modified September 29, 2020
Disclosure -
Exploit Available -
Vulnerability Age 1164 Days.
Solution
No Solution
Workaround
No Workaround
Policy violations
Policy name:	New policy
Policy description:	-
Policy severity:	CRITICAL
Policy name:	AF Medium Vulns Rapid
Policy description:	-
Policy severity:	BLOCKER
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: CVE-2020-7610: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Intelligent/CVE-2020-7610: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityCreateDate: 2023-06-08T09:29:57Z
githubSecurityToolVersion: 0.1.10
Descriptor: CVE-2020-7610: js-bson
Contextual Description:
View in GitHub
NVD CVE-2020-7610 (BDSA-2020-0604) Score 9.8/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Description
All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended BSON type.
View BDSA record | View CVE record
Base Score Metrics (CVSS v3.x Metrics)

Attack vector
NETWORK
Availability
HIGH

Attack complexity
LOW
Confidentiality
HIGH

Integrity
HIGH
Scope
UNCHANGED

Privileges required
NONE
User interaction
NONE

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published on March 30, 2020
Last Modified April 01, 2020
Disclosure -
Exploit Available -
Vulnerability Age 1164 Days.
Solution
No Solution
Workaround
No Workaround
Policy violations
Policy name:	New policy
Policy description:	-
Policy severity:	CRITICAL
Policy name:	AF Medium Vulns Rapid
Policy description:	-
Policy severity:	BLOCKER
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: CVE-2019-2391: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Intelligent/CVE-2019-2391: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityCreateDate: 2023-06-08T09:29:57Z
githubSecurityToolVersion: 0.1.10
Descriptor: CVE-2019-2391: js-bson
Contextual Description:
View in GitHub
NVD CVE-2019-2391 (BDSA-2020-4750) Score 5.4/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Description
Incorrect parsing of certain JSON input may result in js-bson not correctly serializing BSON. This may cause unexpected application behaviour including data disclosure. This issue affects: MongoDB Inc. js-bson library version 1.1.3 and prior to.
View BDSA record | View CVE record
Base Score Metrics (CVSS v3.x Metrics)

Attack vector
NETWORK
Availability
NONE

Attack complexity
LOW
Confidentiality
LOW

Integrity
LOW
Scope
UNCHANGED

Privileges required
LOW
User interaction
NONE

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Published on March 31, 2020
Last Modified September 29, 2020
Disclosure -
Exploit Available -
Vulnerability Age 1163 Days.
Solution
No Solution
Workaround
No Workaround
Policy violations
Policy name:	New policy
Policy description:	-
Policy severity:	CRITICAL
Policy name:	AF Medium Vulns Rapid
Policy description:	-
Policy severity:	BLOCKER
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: BDSA-2020-0604: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Rapid/BDSA-2020-0604: js-bson
Metadata:
githubSecurityStatus: open
githubSecurityToolVersion: 0.1.0
githubSecurityCreateDate: 2023-04-26T08:30:17Z
Descriptor: BDSA-2020-0604: js-bson
Contextual Description:
View in GitHub
BDSA BDSA-2020-0604 (CVE-2020-7610) Score 7.9/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Description
Bson contains a deserialization of untrusted data vulnerability due to improper handling of user input. An attacker could exploit this vulnerability through specially crafted input which could lead to the application treating the input in a way it was not intended, such as data disclosure.
View BDSA record | View CVE record
Published on April 01, 2020
Vendor Fix November 18, 2019
Vulnerability Age 1140 Days.
Solution
Fixed in version 1.1.4 by this commit.
Fixed in version 4.0.2 by this commit.
Workaround
No Workaround
Upgrade guidance
Recommended short term upgrade to version:	1.1.6
Recommended long term upgrade to version:	5.3.0
Policy violations
Policy name:	No High Vulnerabilities
Policy description:	-
Policy severity:	BLOCKER
References

Common Weakness Enumeration: CWE-502

Tool: GitHub Advanced Security
Tool Code: CVE-2019-2391: js-bson
Tool Category: GitHub Advanced Security/Synopsys Black Duck Rapid/CVE-2019-2391: js-bson
Metadata:
githubSecurityStatus: fixed
githubSecurityToolVersion: 0.1.0
githubSecurityCreateDate: 2023-04-26T08:30:17Z
Descriptor: CVE-2019-2391: js-bson
Contextual Description:
View in GitHub
NVD CVE-2019-2391 Score 5.4/10
Dependency tree

sampleapp/0.0.1-SNAPSHOT/-npm

mongodb/3.1.0

mongodb-core/3.1.0

bson/1.0.9

Description
Incorrect parsing of certain JSON input may result in js-bson not correctly serializing BSON. This may cause unexpected application behaviour including data disclosure. This issue affects: MongoDB Inc. js-bson library version 1.1.3 and prior to.
View BDSA record | View CVE record
Published on March 31, 2020
Vendor Fix -
Vulnerability Age 1121 Days.
Solution
No Solution
Workaround
No Workaround
Upgrade guidance
Recommended short term upgrade to version:	1.1.6
Recommended long term upgrade to version:	5.2.0
Policy violations
Policy name:	Vulnerability Score Greater Than Or Equal to 0
Policy description:	Shows all rapid scan components and vulnerabilities
Policy severity:	UNSPECIFIED
Policy name:	No High Security Risk
Policy description:	-
Policy severity:	UNSPECIFIED
References

Common Weakness Enumeration: CWE-502

Source snippet:
N/A

This is false positive

In some reason we cannot do the upgrade.


No reference to PowerShellProcessInstance class

This module lacks support for PowerShellProcessInstance

yes, this is correct. The V1 pipeline APIs were explicitly excluded from PowerShell Standard

Thanks for pointing this out. Does this mean that the use of this class is discouraged/deprecated? What would be the power shell standard way to run ps out of process?

@leonardder It is discussed in https://github.com/PowerShell/PowerShell/issues/11674


Cocoon pre-submit checks fail to get updated even though luci build has finished.

This issue happens in https://github.com/flutter/cocoon/pull/845
cocoon build shows success: https://ci.chromium.org/p/flutter/builders/try/Cocoon/1030
But the checks on PR is not updated:

The problem is we used to have two different version of the pub/sub subscription one for staging and one for prod. This morning I deleted the staging one as we were hitting the API quotas and all checks api messages were being processed by the current prod version of flutter-dashboard that do not understand checks API yet.

Closing this as after updating the pub/sub we haven't gotten this error anymore.


Ingress: support ALB

Add basic support for using AWS's LoadBalancer as Ingress on EKS.
This was split from https://github.com/buildbuddy-io/buildbuddy-helm/pull/40
Add support for ALB Ingress using AWS LoadBalancer Controller(1) on EKS.
(1): https://github.com/kubernetes-sigs/aws-load-balancer-controller/

In #40 we discussed moving the source of truth into the monorepo.
But before that, I want to get my change in so it would unblock the terraform effort that is/could be going on in parallel.

Moved ALB portion into a separate file.


Mj social

@LiamRiddell I extended the console app a little bit and called it tools now.
What you can do for a new component:

Create a new file, e.g. SocialElementComponent.cs
Copy everything from allowedAttributes to defaultAttributes to the file.

e.g.
static allowedAttributes = {
    align: 'enum(left,center,right)',
  }

  static defaultAttributes = {
    align: 'left',
  }

Run the tools

It will convert the file and create the props struct for you.

Create a new file, e.g. SocialElementComponent.cs

This is really cool. Thanks for updating me. I'll return to the mj-section tonight.

I have found a bug in mjml, so I had to tweak my tests a little bit, becuase our implementation works correctly.
https://github.com/mjmlio/mjml/issues/2448


set/get macros should works with already defined components values

Currently you can't use defined components inside set/get macros:
let component: T = T { value: ... };
set !(world, storage_key, (component));

The current fix is to only create the component inside the macro:
set !(world, storage_key, (T { value: ... }));

This is not convenient for some scenario, for example:
let component: T = T { value: ... };
set !(world, storage_key, (component));

// use component value for other things ...

Resolved in #675


Functional compose

What the program do ?
Implementation of the functional compose utility to compose multiple functions together and return a composed function.

In what programming language it is written?
Javascript

This pull request contains conflicts. Please fix it and reopen


ValidateScript error

Hello
I use the 3.5.0 development version. It appears in ValidateScript. 3.4 Previous bug, prompt me ${NGRINDER_HOME}/ script/admin/TestRunner.groovy: 46: unexpected token: & @ line 46, column 22.
Test = new GTest (1, & quot; www.baidu.com")
Good luck
Thank you

@keny16888
Refer to this https://github.com/naver/ngrinder/issues/389#issuecomment-501570407

refer to #389


Assign multiple personnel to a ticket

Expected Behavior
The user should be able to add/remove personnel to a ticket such that more than one person can be associated with a ticket (think pair programming or shift work).
Actual Behavior
The user can select one person against a ticket
Steps to Reproduce
N/A

I want to try this! But i can't find config file for mongogb, where i can change 'assigned' field.


Feedback Tool

Data and the model are coming into the user interface
Need to able to go through the paragraph and remove the inaccuracies and add the correct parts.
Data is in a hierarchical format
Devesh will design how this gets pulled in

Amy should also be on this

I'll improve our prototype and we can think about ways forward.


Making my fan work which uses the tuya legacy fan API

These changes make my fan work that uses the legacy API, so the changes are tested using a real device.
I've seen the pull request from @vookimedlo after finishing coding and tested it, but that code doesn't work for me, it looks like the API is reporting wrong values for the legacy API - the API and the documentation are conflicting, see my comments in my changes.

@tbratfisch I will get back to you during the weekend. I am busy right now. I have some comments to your implementation, but I would say we can find a working solution together.

Meanwhile, 1.4.0 changed the implementation of Fan speed - it has broken the Air Purifier support as I described here #228. I closed my original PR #154  because it is no more relevant.

@tbratfisch @vookimedlo @mouth4war
We managed to get my fan speeds working in https://github.com/tuya/tuya-home-assistant/pull/490 (at the time I'm writing this there is one change missing in the pr itself but mentioned in the comments).
Now my fan uses another way of setting speeds but this new code should support all 3 speed types
That pr (just fan.py) should also work for your fans, could you test?


How to build new operators?

Hi, I need to compile the operators in https://github.com/deepinsight/insightface/tree/master/3rdparty/operator. I tried to copy files in that folder to incubator-mxnet/src/operator and compile the source codes using incubator-mxnet/docs/install/install_mxnet_ubuntu_python.sh. Then I install these operators using incubator-mxnet/python/setup.py. However, I still cannot run these operators? Any suggestions. Thanks in advance!

Did you receive any kind of error when you tried to compile mxnet? Also, the new operator FAQ might be able to help you https://mxnet.incubator.apache.org/versions/master/faq/new_op.html?

Thanks for your reply. There was no error in compiling. I also refered
https://github.com/reminisce/mxnet/blob/900a6997ded8f7124fc6323aa66408cb70e8253f/docs/how_to/add_op_in_backend.md
On Tue, Sep 17, 2019 at 7:10 AM Zach Kimberg<EMAIL_ADDRESS>wrote:

Did you receive any kind of error when you tried to compile mxnet? Also,
the new operator FAQ might be able to help you
https://mxnet.incubator.apache.org/versions/master/faq/new_op.html?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-mxnet/issues/16174?email_source=notifications&email_token=AH2DOTUZSFCRY32CRWVWA4TQKAG7DA5CNFSM4IWZQEEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD62Y6TY#issuecomment-531992399,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH2DOTVKSTJCLHW4OQS5PW3QKAG7DANCNFSM4IWZQEEA
.

With today's new updated website launch - https://mxnet.incubator.apache.org/api/faq/new_op should be the link @zachgk

I copy pasted the files into src/operator/. directory. Rebuilt it.
Tried the following
>>> import mxnet as mx
>>> mx.nd.AmSoftmax(data=mx.nd.arange(0,12).reshape(3,4),weight=mx.nd.arange(0,4).reshape(1,4),label=mx.nd.array([0,0,1]),num_hidden=1)

[[14.]
 [38.]
 [62.]]
<NDArray 3x1 @cpu(0)>

This didn't give me any error
For more details about using the function, help() might be helpful
>>> help(mx.nd.AmSoftmax)

@mxnet-label-bot add [Pending Requester Info]
@zachgk Is this good to close since I think we've answered this question and the author hasn't responded for a while.


feat: connect linear issues

Problem
When I write unit tests without the right context, they can end up inaccurate or incomplete. Missing key details from issues or tickets  means the tests might not cover important parts of the feature. This leads to gaps in coverage, increasing the risk of bugs making it into production.
Feature
To solve this, I added a feature that connects with Linear. Users can link their Linear accounts, search for related issues directly in the app, and add them as context when generating unit tests. This extra context makes the tests more accurate and relevant, ensuring they reflect the feature requirements.
Scope Limitations
This version is a proof of concept, focusing on Linear integration to validate its effectiveness and see if it helps other developers. If it proves useful, expanding to include other tools like Jira and adding more integrations will be the next steps.
Demo
https://github.com/user-attachments/assets/94d9c7f4-9dcb-4abf-bb7e-9c105caf14a2

I think the code should be self-explanatory to writing the tests.

I'm open to a github issue integration perhaps, or feeding in the PR description, but not Linear / Notion as I think those tools shouldn't contain "specs" outside of GitHub and limits the usage.
We can discuss on the call tmmrw tho!

Link in discussions! Will also be recorded


Create  GASDocumentation_Chinese

The Chinese version of the document I translated.

Wow, that's great! Unfortunately I won't be merging it. I don't know Chinese and there's no way that I can keep that up to date with every change that I make to the English version. Instead, I can link to your repository in the Other Resources section.

Wow, that's great! Unfortunately I won't be merging it. I don't know Chinese and there's no way that I can keep that up to date with every change that I make to the English version. Instead, I can link to your repository in the Other Resources section.

Thank you for writing this document, which is very useful to me.
I have shown the translated document to my colleagues and friends. They think it is very useful. You know, there are not many tutorials about GAS in Chinese. Thank you. I'm just the disseminator of your ideas. This is my GitHub repository of the Chinese version of the document.
Thank you again.

I would like to thank you as well! This document has been invaluable on my indie game project. Thanks to this document, I managed to make a FPS game with RPG-like damage system with network prediction and stuff.


Error code 301 - Date of birth falls after the year ended.

Error information
Error code
301
Description to display
Date of birth falls after the year ended.
DfE Long-form description of error
Child's date of birth must fall on or before 31 March of the current data collection year.  Check date of birth and amend record accordingly, if the date of birth is correct, this record should be deleted from this year's submission.
DfE suggested coding
<DOB> must be <= <COLLECTION_END_DATE>`
For further info, refer to the DfE validation document here

@DMC63 are you working on this?


"Linked Network cannot be found" message appears even if the terminal clearly works

I know when and why this happens, I just don't have a good fix for it

Hi, I'm not sure if this is related but I will present it here in case it helps, I combined all three terminals into the Universal Terminal. Now, if I am in Nether the terminal works till 45-47% after that it gives the same message Linked Network cannot be found. I then have to go in rage of the wireless transmitter for it to work again.

I'm getting the same message, as you can see I can access the network just fine. Using Wireless Universal Terminal with Pattern Encoding and Crafting.

This issue also occurs for Prominence II [FORGE] (v1.7.0) modpack.
Using AE2WTLib 15.1.4.

Same issue here!

will be fixed in the next release

I have this issue in present day (atm9)

I have this issue in present day (atm9)

which ae2wtlib version are you using? it should be fixed in 15.2.2 and 15.2.3 (and any later versions)

I have this issue in present day (atm9)

which ae2wtlib version are you using? it should be fixed in 15.2.2 and 15.2.3 (and any later versions)

First off apologies for opening a new issue! I figured that was the correct way to do things but now i see you replied here. Should i delete the issue i opened?
Second, I'm using 15.2.3

First off apologies for opening a new issue! I figured that was the correct way to do things but now i see you replied here.

I replied here because when I was writing the reply, you hadn't opened the other issue yet.
also I wasn't sure if you had the same issue or a slightly different one (which is the case since you are using a version that is supposed to be fixed)

Should i delete the issue i opened?

no

1.20.1 is not supported anymore, and won't receive further updates.


Root widget built twice, again.

I think #33566 should be reopen.

Hi @roeniss
Please refer to https://github.com/flutter/flutter/issues/57353#issuecomment-629569076.


docs: Document meaning of ETags in developer docs

As @butonic correctly states in https://github.com/owncloud/ocis/issues/3988#issuecomment-1167681224 we need to document the concept of the ETags (and possibly CTags in the future) in the developer documention.
References:

#3988
#3782
https://github.com/cernbox/smashbox/blob/master/protocol/protocol.md#restrictions-and-limitations
And a classic of the ownCloud literature: https://dragotin.wordpress.com/2015/03/13/owncloud-etags-and-fileids/

etags now mentioned in devdocs. closing.


Remove superfluous newline

The file "test" had two trailing newlines, which is unnecessary many, so I just removed one of them.

That was definetly necessary :rofl:

But it is a critical fix!


How to use "whereHas" along with "search()"

I need to use search with "search()" and also validate a condition for "whereHas", but I'm not being able to use both together when I use "search()" it returns that the method "whereHas" does not exist.
Any ideas?

Hi, i need the same thing. I wish I could filter first based on my relations and then search for the text.

also interested in how you can use whereHas

also interested in how you can use whereHas


Snap 730

Changes proposed in this pull request
align min cached batch size if cached batch size is less than minimum.
Patch testing
N/a
ReleaseNotes changes
N/a
Other PRs
https://github.com/SnappyDataInc/snappydata/compare/SNAP-730

Looks good to me.


Document environment glow restrictions in the Compatibility rendering method

This closes https://github.com/godotengine/godot/issues/89054.

Note: Not cherry-pickable as glow in Compatibility is only implemented in 4.3.

I'll add, maybe glow_blend_mode should mention what is it equivalent to?

I'll add, maybe glow_blend_mode should mention what is it equivalent to?

I believe glow is always using the Add blend mode in Compatibility, but I'm not 100% sure. cc @BastiaanOlij

Thanks!


[UI Feature] Privacy progress page could show more information.

This page :

It used to display every UTXO in the circle, Now there's only 2 section, Semi-private and Private.
Seems like a step backward, I suggest adding a link to whatever pop-ups when typing CTRL-CD. (Coin control)

It is because you have more than 100 coins. This limit was added to avoid rendering problems

I think it's still a good place to link to UTXO list.

From https://mempool.space/address/bc1qh2puhz50s2lf7c0s062g8w2c4j5jjautcuv06l


Image filtering depends on zoom

Hello!
 :-)
I stumbled across a small issue: image filtering appears to depend on the zoom level.
The viewer seems to alternate between bilinear and point filtering.
Additionally, it would be nice to have a setting which specifies the filtering behavior - typically, you want resampling, but sometimes it's nice to be able to look at "raw" pixels.
Cheers!

Compare to Bug https://github.com/darbyjohnston/DJV/issues/148

Hi, I've added settings so that you can choose which filter you want to use for minification (sp?) and magnification, this will be available in the next version.


Typescript no longer auto importing suggestions

When picking a suggestion from another module, TS no longer auto imports that suggestion. I have to trigger suggest once again, accept the only change and then it gets imported.

Can you please check the TypeScript Server trace:

Set "typescript.tsserver.trace": "verbose"
Reproduce the problem
Open the output panel and view the TypeScript section

Are there any errors or stack traces printed near the end?

https://gist.githubusercontent.com/joaomoreno/76d1e08bfded241499dafcba7241bf4c/raw/6da60ff7304145ab459018296ef419c1c69e1624/ts.log

Can confirm this behavior. I never get auto import suggestions unless I trigger the auto-complete hints a second time.

I too need to trigger the intellisense twice, in order to see the import path in the hint, and then trigger the auto-import.

Same here, I have to trigger it two or three times in order for the auto-import to show up. This is on Typescript 3.2.0-rc

With vscode 1.29.1
TS 3.0.3 works
npm install<EMAIL_ADDRESS>in your local project or
sudo npm install -g<EMAIL_ADDRESS>to install globally for all projects.

Same here

There are two cases to try for this:

Type quickly to trigger suggest but do not hit enter. In this case, the suggest list item does not contain any details (indicating that auto imports have not been resolved properly). Scrolling through the list or waiting does not help; the details are never resolved

Type quickly to trigger suggest and then press enter quickly. Auto imports are also not resolved here.

@jrieken The root cause seems to be our internal handling of cancelation while resolving completion items. The sequence of events:

Trigger suggest
The suggestWidget starts trying to resolve a suggestion item in a promise. We cache the promise value here.
Before this can complete, type some more but make sure that the same suggestion item will still be active. This cancels the ongoing resolution.
We then try to resolve the same suggestion item again. This just gets the cached promise result so we never properly resolve the suggestion item

There are a few potential things that need fixing:

Why are we trying to re-resolve the same item in the first place? We should just continue on with the current resolution. The cancellation that seems to cause this is https://github.com/Microsoft/vscode/blob/86052e38f3a25f365e57590cbe2175bb24b84939/src/vs/editor/contrib/suggest/suggestWidget.ts#L714
We should never cache canceled requests (but we should likely cache other failures).

@jrieken I submitted a PR that fixes case 1: https://github.com/Microsoft/vscode/pull/64093
Case 2 is still broken. I think we need to make sure that the completion item is resolved when we call _onDidSelectItem in SuggestController

Is there a workaround for this? It's killing productivity

Can't use TS 3.2.1 now cause of this, sticking to 3.0.3

Is there a workaround for this? It's killing productivity

Can't use TS 3.2.1 now cause of this, sticking to 3.0.3.

Sweet that worked. Thanks k-knyazev.

Case 2 is still broken. I think we need to make sure that the completion item is resolved when we call _onDidSelectItem in SuggestController

Thanks. I will push a change that ensures we always that we always call resolve. This will help all different insertions, like insert on trigger character.

We should just continue on with the current resolution. The cancellation that seems to cause this is [...]

The problem is that resolving details also updates the UI and that pending, but outdated, detail-calls would reveal the wrong items. See https://github.com/Microsoft/vscode/issues/60753 for more details.

@mjbvz I merged the PR and I made a tweak on top of it - the IPC layer might reject a promise with a cancellation error if it's canceled before dispatched.
What wonders me is why this only happens with certain version of TypeScript? Was the extra edit not a detail before or what has changed so that these issues are now exposed?

Thanks @jrieken! I believe this started happening after the resolve call in the TS extension went from being a single async operation to two. Previously, if cancellation occurred after the single operation had been dispatched but before resolve returned, we'd still return the fully resolved completion item. After the change in TS, on cancellation we bail early and return the unresolved completion item.
Closing this as the causes of this specific issue have been addressed

I am also having this issue.
VS Code details:
Version: 1.29.1 (user setup)
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:13:36.375Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Due to legacy code reasons, I am stuck on TypeScript 2.5.3
Any idea when this fix will be available?

Thanks @jrieken! I believe this started happening after the resolve call in the TS extension went from being a single async operation to two. Previously, if cancellation occurred after the single operation had been dispatched but before resolve returned, we'd still return the fully resolved completion item. After the change in TS, on cancellation we bail early and return the unresolved completion item.
Closing this as the causes of this specific issue have been addressed

"allowSyntheticDefaultImports: true" breaks auto import, finally tracked the cause of this in my particular case.
Issue do not exist from TS 3.0.3 and still present even till TS@next. Must I open a new issue? Is this TS problem more than vscode?


Sort download archive by versions

Sort releases by order from newest to oldest major.minor version.

@leecow are you ok with my change? Should I move ".NET Core Tools for Visual Studio 2015" to the bottom? (I don't think it needs Current vs. LTS attribution)


how to access my own gitlab source when running job

I have some problem to connect to gitlab to clone the code, so I want to test to clone code from our company's gitlab. But I can only clone code with SSH, how to do it in the job?

I am not sure I understand your question. Do you mean you cannot access gitlab from within the job container? Can you access other site in the container? Maybe you should check the CNI deployment in the k8s.

because of the GFW... clone code from github could be slow or failed, and for security, I want to clone code from company's private gitlab, but I can not clone from it without SSH security key, how could I do this?

Hi @HaoLiuHust. Before clone code, you need to add your private key to ssh-agent.
Please refer https://docs.github.com/en/github/authenticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#adding-your-ssh-key-to-the-ssh-agent
For the private key, you can put it into secret field.
And refer the secret field in the command.
Please make sure your container has ssh tools
example:
protocolVersion: 2
name: job
type: job
jobRetryCount: 0
prerequisites:
  - type: dockerimage
    uri: 'openpai/standard:python_3.6-pytorch_1.2.0-gpu'
    name: docker_image_0
secrets:
  ssh-key: |
    -----BEGIN RSA PRIVATE KEY-----
   <your key>
    -----END RSA PRIVATE KEY-----
taskRoles:
  taskrole:
    instances: 1
    completion:
      minFailedInstances: 1
    taskRetryCount: 0
    dockerImage: docker_image_0
    resourcePerInstance:
      gpu: 1
      cpu: 5
      memoryMB: 51200
    commands:
      - echo  "<% $ssh-ke.ssh-key %>" > key-file
      - ssh-add ./key-file
      - git clone ....

Thanks, helps a lot...


Adding of audio captcha and captcha history that will help to genarate new captcha's in captcha generator project.

Made some changes according to the above topic. please assign this issue @Sulagna-Dutta-Roy ma'am

Kindly spare some time to assign. Before raising any pull requests.

Kindly raise the issue using feature request

Kindly raise the issue using feature request

Already raised issue #217 and also provided solution. Please refer.#217

Kindly spare some time to assign. Before raising any pull requests.

OK ma'am. This shall be not happen next time. Extremely sorry.

You can check other people's issues. How the template is provided.
Kindly do not open blank issues. Also you've opened a new issue, that one I closed because of duplicates.
Some points to Improve:

Feel free to explore closed Issues. How other people have added as per the guidelines

Also explore closed PRs, if possible. Kindly give me some time to assign all the issues. Because there are no mentors here.

Thank you for your contributions @vyanky1227

Thank you so much ma'am for you support and guidance.


RGBW help

Firstly - this is such a great library and is already looking very cool as it is on my RGBW strip. Thank you so much!
I was hoping you might be able to point me in the right direction to adapt this for an rgbw Neopixels strip. I'm obviously getting some quite weird colour results as I need that extra 'W' value. This may also be why not all my pixels are lighting up (I've changed the numbers in the config and that hasn't done the job).
Any pointers you can give would be massively appreciated!!

Glad you have it working! Thanks for the kind words.
This project uses the WS2812x library which in turn uses the Adafruit_Neopixel library. I took a look at their documentation and it does look like that RGBW is supported. I don't have any RGBW strips to test with but if you want to give it a go, it might be fun. I think the only two places you need to make changes is visualization.py and led.py.
In visualization.py there's this line:
p = np.tile(1.0, (3, config.N_PIXELS // 2))

I think If you change the value from 3 to 4, it'll add a "W' tile. You'll also have to look at the different visualizations and add the 'w' - for example in visualize_scroll there's this:
p[0, 0] = r
p[1, 0] = g
p[2, 0] = b

I think adding a p[3,0] = w will add that channel.
There are also a lot of places where you need to add the 'w' code. And you need to make changes to led.py for the leds to update properly.
This is a very rough look at this process. Without the led strip (and time needed), I won't be able to provide any specific update to the repo. Maybe one day I'll get myself an RGBW NeoPixel strip and give it a go.
Hope this helps a little, good luck!

This is super helpful - thanks so much for the quick response!
I was trying to do something along the lines of what you've outlined here last night but thought I'd check in and see if you'd done it previously or had some tips. I've also just noticed there's a closed issue where someone else seems to have got rgbw working so will drop him a message if needs be!
Hopefully will work it out and let you know!


Publish Docker container to Docker hub using python:3.9.1-buster as base image

Currently Schemathesis is published using Alpine as base image.
Is your feature request related to a problem? Please describe.
Running MSAL authentication on Alpine is not supported out of the box. On the other hand MSAL works quite well using Buster.
Describe the solution you'd like
Publish another (besides alpine) docker image using python:3.9.1-buster as base image
Describe alternatives you've considered
Currently we use Buster Linux image and then doing pip install of Schemathesis
Additional context
This request to improve integration with RAFT

Hi @stishkin !
Thank you for bringing this up! I will take a look at it this week :)

Hi @stishkin !
Thank you for bringing this up! I will take a look at it this week :)

Hej @stishkin !
The following Buster-based images are available now on Dockerhub:

schemathesis/schemathesis:latest-buster
schemathesis/schemathesis:stable-buster
schemathesis/schemathesis:v3.0.7-buster

Let me know if it doesn't work for you :)

Hej @stishkin !
The following Buster-based images are available now on Dockerhub:

schemathesis/schemathesis:latest-buster
schemathesis/schemathesis:stable-buster
schemathesis/schemathesis:v3.0.7-buster

Let me know if it doesn't work for you :)


restarting onboarding needs to re-execute the model

https://github.com/KittyCAD/modeling-app/assets/1445228/029ca791-948d-4dca-bb54-0c8cbce81eb3

https://github.com/KittyCAD/modeling-app/assets/29681384/4ddc740b-4ed0-44e1-aef9-4dc7ac47f129
https://github.com/KittyCAD/modeling-app/assets/29681384/8170f27a-7441-44cd-8a15-b471db741970
We mostly got this for free in #897, but I did find a bug when checking this, so fixed that up too.


TypeScript custom marchers declaration snippet

A small note in expect.extend() documentation for TypeScript users since it's not obvious how to declare  types for custom marchers.
Thanks, keep it up!

@thymikee hey, nice catch, but I'm seeing the commits, and I don't think is the same thing.
If I understand correctly, the PR is about adding jest built-in matchers types.
But my scenario is about a TypeScript user defining a new custom matcher using jest.extend().
In that case the user will need to declare its custom matcher signature somehow, in order to have type checking.
Declaring a mixing or extending an ambient module is not trivial in TypeScript IMO that's why I'm suggesting that small tip in the doc .
But perhaps I'm missing something about the PR ?
Thanks!

That is true for @types/jest, it won't necessarily be true when Jest comes with its own types. We could land this in the meantime, of course

@cancerberoSgx can you specify in the docs that this is only true for @types/jest and not Jest itself? Jest will provide its own global typings soon:tm:, but I don't want to tie us to what's currently in @types/jest

@SimenB :

That is true for @types/jest, it won't necessarily be true when Jest comes with its own types. We could land this in the meantime, of course

So, this IS true both for @types/jest and jest (now). Also, I consider myself very capable with TypeScript declarations/types and I doubt you will be able to accomplish this in the near future. I think the only way right now of augmenting an existing type is with a declaration and you can't declare anything in within a type declaration, dynamically . Will do what you asked, but I needed to comment this. Regards,

So, this IS true both for @types/jest and jest (now).

This is not true jest as jest does not expose any types in the global namespace. Semantics, but the point is that if you remove @types/jest (an external package, totally separate from Jest itself) from your project, that snippet will be wrong. It should at the very least mention the fact this is for @types/jest, and that it's subject to change whenever Jest comes with its own typings. And Jest will not necessarily make that change in a major (although we probably will to avoid the churn)

Also, I consider myself very capable with TypeScript declarations/types and I doubt you will be able to accomplish this in the near future. I think the only way right now of augmenting an existing type is with a declaration and you can't declare anything in within a type declaration, dynamically

Sure, but I won't commit to e.g. calling it Matchers when it's dumped into the global namespace

Thanks!


A/B Test LLMs?

Hi @Fluder-Paradyne @Tarraann @jedan2506
In production, we don't know if Llama2 is going to provide:

good results
quickly

Would it be helpful to provide a way to easily A/B test between new models in production?
Context - I'm working on LiteLLM and we recently released a way to a/b test straight from the completion endpoint:
Tutorial: https://docs.litellm.ai/docs/tutorials/ab_test_llms

Thank you for your valuation feedback. We will surely look into the information you provided and have a detailed discussion on it.


Reland "Update FocusManager platform check to include iOS"

It looks like removing kIsWeb from the FocusManager._appLifecycleListener platform check is causing memory leaks and test failures.
This pull request fixes #148475 and prevents the test failures shown in #148978.

I think FocusManager.listenToApplicationLifecycleChangesIfSupported should also be updated to reflect this new platform check.

@Renzo-Olivares I hadn't noticed that the listenToApplicationLifecycleChangesIfSupported method was added, thank you!

When will this land in stable? It has been baking in master for over a month now.

Hi @techouse, I appreciate your concern! Unfortunately, a comment like this one contravenes our issue hygiene guidelines.
But to answer your question: it will land in stable once someone makes a cherry-pick pull request, and that PR is approved. I was planning to manually create a PR within the next day or two!


⚠ ESPN has degraded performance

In 2146529, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 13234 ms

Resolved: ESPN performance has improved in c30885c.


VWMA calculation is werid

I think VWMA calculation is werid, since it does not take the weighted by recent value into consideration.
It uses
pv = close * volume
vwma = sma(close=pv, length=length) / sma(close=volume, length=length)

for wma calculation check out this, it should use the same with adding volume as an additional parameter
WMA = (P1 * 5) + (P2 * 4) + (P3 * 3) + (P4 * 2) + (P5 * 1) / (5 + 4+ 3 + 2 + 1)
VWMA = ?

right? what do you think?
TradingView is using the same as the current calculation https://www.tradingview.com/pine-script-reference/v3/#fun_vwma
Maybe:
WMA is weighted by recent value
VWMA is weighted by volume without of recent value
if that is the case. then please feel free to close this

I think:
WMA is weighted based on recent
VWMA is weighted based on volume instead of recent
if that is the case. then please feel free to close this

@twopirllc
Thank you so much. I really appreciate it.


Fix fuzzy search lookup issues

PR includes a couple of modifications to the fuzzy search:

Fixes #2380 (81d37a0)
Improves the results returned by the fuzzy search library (93d20d2)

@juliusv this fixes the issue you filed. Can you give it a spin?

@fabxc Thanks for the reminder!
@lightpriest Sorry for the delay. It seems to work nicely for me, thanks a lot!


⚠ Processors has degraded performance

In eb08b8a, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 1349 ms

Resolved: Processors performance has improved in f9de737.


HTTP request failed:  malformed after a while solomining

[2019-06-10 14:28:26] HTTP request failed:  malformed
[2019-06-10 14:28:26] HTTP request failed:  malformed
[2019-06-10 14:28:26] submit_upstream_work_mtp json_rpc_call failed
after a while (in the last case about 3 hourse) I get the above errors from cpuminer

shutting down and restarting the wallet temporarily fixes it.    I'm on v<IP_ADDRESS>-8b7d49e-unk but it was a problem on earlier versions as well.

Ran it for another hour and now I am getting
HTTP request failed: Operation timed out after 30001 milliseconds with 0 bytes received
json_rpc_call failed, retry after 10 seconds

@chileminer Is it still actual?

Hi, are you solo mining with cpuminer ?

While I appreciate your reaching out to me, it's a bit late.   After Sebastian made false accusations against me and told me to stay off of testnet, I lost interest and haven't been on testnet much since.
Chile
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, July 23, 2019 9:15 AM, djm34<EMAIL_ADDRESS>wrote:

Hi, are you solo mining with cpuminer ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@reubenyap @djm34  Should we close this? Or maybe continue investigation?

I don't have time to look into it again.   Do what you think is best.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, August 13, 2019 8:57 AM, MJ<EMAIL_ADDRESS>wrote:

@reubenyap @djm34 Should we close this? Or maybe continue investigation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Debug API Not working - Cannot read properties of undefined

Does this occur consistently?
Repro steps:

Trying to Debug the API

APIM Details:
Developer Tier
Platform Version: stv2
Region: EAST US 2
Network: Internal VNET
apiVersionConstraint.minApiVersion : 2019-12-01
Action: azureApiManagement.debugPolicy
Error type: TypeError
Error Message: Cannot read properties of undefined (reading 'primaryKey')
Version: 1.0.6
OS: darwin
OS Release: 22.5.0
Product: Visual Studio Code
Product Version: 1.80.1
Language: en

Call Stack
extension.bundle.js:479:71081
OperationConsole.<anonymous> extension.bundle.js:479:71044
fulfilled extension.bundle.js:479:68637

any update on this issue?

After some investigation, it seems this issue is happening only if the management api is 2019-12-01 . If i change this to null the issue is not happening. But the problem of this workaround will be security reason from ms
Microsoft recommends to make this to value not null and keep it 2019-12-01 or higher The reason for this would be
To prevent service secrets from being shared with read-only users, the minimum API version should be set to 2019-12-01 or higher.
So i think we should not start practising the workaround by making the api version to null and fix the extension code to support this version

@DeagleGross / @malincrist / @quanterion  thanks for fixing the issue. Is this part of any new release ? Is there a place we can check the changelog or release doc ?

Hello @jayendranarumugam , the fix will come with a new release. You can track GitHub releases or the changelog from the VSCode extension.


Error when trying to edit a server.

When i try to see a server it gives this error and if i restart the pufferpanel service it give's the same error.
Error: { "message": "Request failed with status code 403", "name": "Error", "stack": "Error: Request failed with status code 403\n at t.exports (http://:8080/js/chunk-vendors.25ec2db5.js:7:79339)\n at t.exports (http://:8080/js/chunk-vendors.25ec2db5.js:20:57976)\n at XMLHttpRequest.p.onreadystatechange (http://:8080/js/chunk-vendors.25ec2db5.js:37:44703)", "config": { "url": "/api/servers", "method": "get", "params": { "page": 1, "limit": 10 }, "headers": { "Accept": "application/json, text/plain, /", "Authorization": "Bearer eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJzZXNzaW9uIiwiZXhwIjoxNjA0NTEyNTM5LCJpYXQiOjE2MDQ1MDg5MzksInN1YiI6IjIiLCJwdWZmZXJwYW5lbCI6e319.oZdsygw9oMu2EEFBs8uwj9nEMmEx6slitZ2HY4KB2aHzA2vyxvvHtXW0pCTHuTphxMfkIcnYlJ1fN5_Xk4ia8w" }, "transformRequest": [ null ], "transformResponse": [ null ], "timeout": 0, "xsrfCookieName": "XSRF-TOKEN", "xsrfHeaderName": "X-XSRF-TOKEN", "maxContentLength": -1 } }.

status code 403 means your user does not have permission, I'd assume you probably fell for #925 and assumed that that permission should not be granted, but despite the label it actually only allows a user to see the servers they have been given access to and should therefore be granted in most cases

but i'm logged in with admin account..

I fixxed the problem, i modified a normal user account but it overwrited my admin account so with ssh i created a new admin account so i  edited my admin normal account and it worked just fine. but i noticed that modifing the normal user account (previous) he overwrited all account with deleting all informations of 3 account. is that normal??


Remove dependency on Syntex

We depend on Syntex for three things:

parsing
quasi
aster

I wrote a Rust parser https://github.com/dtolnay/syn and quasi-quoter https://github.com/dtolnay/quote which together build in 8.1 seconds (including all their dependencies). Syntex (including quasi and aster and dependencies) builds in 65 seconds so it is a decent improvement.
I am going to start porting serde_codegen over to these. For now serde_codegen will still need Syntex as a shim but serde_derive can disable it with a feature flag and use the new approach directly.
This will eliminate the biggest advantage of serde_macros over serde_derive - compile time. Once serde_derive is off of Syntex I propose that we stop supporting serde_macros.

To clarify the "for now": serde_codegen will need Syntex until either of the following happens:

Macros 1.1 is stabilized and we no longer need to parse all of Rust in a build script https://github.com/rust-lang/rust/issues/35900
We can parse all of Rust in a build script without Syntex https://github.com/dtolnay/item/issues/4

Until one of these things happens, serde_derive can depend on serde_codegen but flag off the Syntex dependency.

In progress in #548, though there is a lot of work left.

Fixed in #548 for serde_derive.
Closing because I don't currently plan to do this for serde_codegen, but we can reopen if plans change.


typeguard dependency change

The following error occurs from a recent version bump for the package typeguard https://pypi.org/project/typeguard/#history:
omni_obj = get_omni_object_from_yaml('src/config.yaml')
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/tmp/ipykernel_1540/2003880732.py in <module>
----> 1 omni_obj = get_omni_object_from_yaml('src/config.yaml')

/opt/conda/lib/python3.9/site-packages/omnibenchmark/utils/build_omni_object.py in get_omni_object_from_yaml(yaml_file)
    349     with open(yaml_file) as f:
    350         config = yaml.load(f, Loader=yaml.FullLoader)
--> 351     check_type("config", config, ConfigDict)
    352     return build_omni_object_from_config(config)

TypeError: check_type() takes 2 positional arguments but 3 were given

An intermediate work-around is to down-grade typeguard with pip install typeguard==2.13.3

Thanks for this, should be fixed from version 0.0.42


Streaming output support

Is your feature request related to a problem? Please describe.
Text generation will require supporting modules that return DataStream[T] to stream output.
This will need to be hooked up to a unary-stream RPC.
Describe the solution you'd like
Tasks can specify DataStream[T] as output type
Service generation code adds output streaming flag in py-to-proto
Servicer implementation returns something like...
stream = model.run
return iter(stream.map(stream_class.to_proto()))

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context about the feature request here.

Some decisions from caikit architecture club:

A task that will require streams will be a separate task

A default stream block implementation could batch a non-stream block's responses. This can be task implementation specific.

This will mainly affect the module.run functions
We will remove the module.stream function.
We will be keeping module.run_batch at this time


Narrow it down to specific Stacks?

Is it possible to narrow the tool down to specific Stacks rather than all?

Thank you for suggesting this feature @wolf-allywilson
To make sure I fully understand, would a new optional parameter like --stackName be what you are looking for?
When that is specified, then rather than printing all the stacks in the specified account/region, this will only print any graphs that the specified stack is part of.
I think this might be doable.

I think --stackName or --stackNames stack1,stack2,stack3,etc would work, yep.
Thanks for considering this.

Was looking into generating a graph of a particular stack, this is a very valuable feature I would also like to echo.


Added "system" agent state type

*Issue #908 *
Description of changes:
Added "system" to the AgentStateType enum.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Also added the "error" state type.

Fixed it as a part of another pull request, thank you for your contribution.


Space travelers team project

Below is the direct link to the project:
Project Link
The project will be developed by two students.

STATUS: APPROVED!!!  🎉 🎉 🎉 :champagne: :champagne: :champagne:
Hi Team,
Good job !!!
To Highlight! :clap:  :green_circle:
:heavy_check_mark:  Good job with issue summary
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉 🎉 🎉 :champagne: :champagne: :champagne:

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
N/A
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear or you can get to me on slack  using this handle @mihndim.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Thank you for the kind review


Can't stop recording (and save) on Android 8

On Android 8, it is impossible to click on the red button to stop recording and save.
The Android drop down menu takes the focus, somehow disabling the button.
The application is otherwise a wonder, nice job!

Duplicate of #149.


Adding themes and vent to gitignore

can this be merged and closed? @tautrimas

@trylika, yes it can. Had to rename the commit.


When I try BARF on my own sequence， some error(s) occurred in Test while loading state_dict for NeRF

Hi Chenhsuan!
Thank you for sharing the code! When I try BARF on my own sequence，
tran script：python train.py --group='barf' --model=barf --yaml=barf_iphone --name='iphone' --data.scene='cats' --arch.posenc!
test script：python evaluate.py --group='barf' --model=barf --yaml=barf_iphone --name='iphone' --data.scene='cats' --resume
some error(s) occurred in test while loading state_dict for NeRF. Have you encountered this problem before? Thank you
Errors：
restoring nerf...
Traceback (most recent call last):
File "evaluate.py", line 34, in
main()
File "evaluate.py", line 28, in main
m.restore_checkpoint(opt)
File "/data1/lvxinbi/barf/model/base.py", line 53, in restore_checkpoint
epoch_start,iter_start = util.restore_checkpoint(opt,self,resume=opt.resume)
File "/data1/lvxinbi/barf/util.py", line 131, in restore_checkpoint
child.load_state_dict(child_state_dict)
File "/home/hotel_ai/anaconda3/envs/torch1.7/lib/python3.7/site-packages/torch/nn/modules/module.py", line 1407, in load_state_dict
self.class.name, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for NeRF:
size mismatch for mlp_feat.0.weight: copying a param with shape torch.Size([256, 3]) from checkpoint, the shape in current model is torch.Size([256, 63]).
size mismatch for mlp_feat.4.weight: copying a param with shape torch.Size([256, 259]) from checkpoint, the shape in current model is torch.Size([256, 319]).
size mismatch for mlp_rgb.0.weight: copying a param with shape torch.Size([128, 259]) from checkpoint, the shape in current model is torch.Size([128, 283]).

Hi @lancerste, you would also need to pass --arch.posenc! into your evaluation command, or there will be a shape mismatch in the model weights you're loading from your checkpoint.


[Do not merge] Remove authorities file

This removes the authorities.json file and its dependencies from Frontend, having moved the file to MapIt (https://github.com/alphagov/mapit/pull/20). We take the time to refactor some code to make it easier to understand its intention.
Note: Relies on https://github.com/alphagov/gds-api-adapters/pull/515, will need to wait until that PR is merged and the new version is used in this PR before the tests will pass.
Note: LocalLinksManager will also have to be updated before this gets merged as it currently imports the authorities.json file to attach slugs to LocalAuthorities
WIP - Needs a refactor to use MapIt routes for code/govuk_slug/

Closed in favour of https://github.com/alphagov/frontend/pull/970