ephemeral type respond() issue

Description
When updating the message, the user is changed to 'Bot' and profile image changed to default image . I searched almost everywhere, but I couldn't find anything related to it.
await respond({
      replace_original: true,
      blocks: await createBlock(parseInt(action.value), 5, campusNo),
    });

What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
package version:
node version:
OS version(s):
Steps to reproduce:

use respond()
2.update the message

Expected result:
User name must be the same before or after modification.
Actual result:
What actually happened
Attachments:
before

after

Hey @jho2301!
I need a bit more info about what you are doing here.

Could you share a code snippet? In the first image, it seems like your app is posting as a user. Is this correct? If so, maybe you used a userToken to do so.
Are you listening to any events that you use to trigger the message update?
Are you using new granular bot tokens? What scopes are you using for your app?

I'd also recommend checking out https://api.slack.com/methods/chat.postMessage#authorship.

Could you share a code snippet? In the first image, it seems like your app is posting as a user. Is this correct? If so, maybe you used a userToken to do so.

app.command(COMMAND, async ({ command, ack, body, context, client }) => {
  await ack();

 if (`${command.text}` === "list") await showList(command, body, context, client);
});

async function showList(~~~) {
  const block = await createBlock();
  await app.client.chat.postEphemeral({
    token: process.env.SLACK_BOT_TOKEN,
    channel: command.channel_id,
    user: command.user_id,
    blocks: block,
    text: 'you called  list',
  });
}

async function createBlock(offset, limit, campusNo) {
  const actionBlock = {
    type: 'actions',
    elements: [],
  };
  if (offset - limit >= 0) {
    actionBlock.elements.push({
      type: 'button',
      text: {
        type: 'plain_text',
        emoji: true,
        text: 'Previous',
      },
      action_id: 'paginate_previous',
      value: String(offset - limit),
    });
  }
  if (offset + limit < count) {
    actionBlock.elements.push({
      type: 'button',
      text: {
        type: 'plain_text',
        emoji: true,
        text: 'Next',
      },
      action_id: 'paginate_next',
      value: String(offset + limit),
    });
  )
  return actionBlock;
}

app.action(/paginate.*/, async ({ blah blah }) => {
    await ack();

    await respond({
      replace_original: "true",
      blocks: await createBlock(~),
    });
});

i tried to  describe the logic briefly

Are you listening to any events that you use to trigger the message update?
yes, it listens action app.action(/paginate.*/, ~~)
Are you using new granular bot tokens? What scopes are you using for your app?
in program, bot token is always same.

i use

chat:write
chat:write.public
im:write
mpim:write

the profile image and the profile that comes out when I click the bot user are same as before. However, the displayed bot user's name is changed to 'Bot' when message got updated.

👋 Hi @jho2301 sorry for our very slow response here. If you are still interested in this issue, I'm happy to work with you here.
Thanks for sharing the code snippet but I don't think the code is not representing the scenario. The respond utility (using response_url) is unable to modify messages posted using chat.postEphemeral API method.
If the bot user's icon image can be broken in a specific scenario, I'll escalate the issue to the server-side engineering teams (or client app teams if it's client app specific).

Let me close this issue but please feel free to write in as necessary!


Control crashes on selecting large files

Control wont respond on selection of large files (upto 5GB). I have given the file size limit aslf-filesize="6000MB" lf-totalsize="7000MB"
Is there any fix for this issue or what is the max size control supports?

Any Solution for this? @sangameshb15

It's very long time and I have moved out of it
On Mon, Oct 19, 2020, 3:32 PM AhmedMasoodSiddiqui<EMAIL_ADDRESS>wrote:

Any Solution for this? @sangameshb15 https://github.com/sangameshb15
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shuyu/angular-material-fileinput/issues/42#issuecomment-711967651,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABZO7L4Y253CQP6W3XEWPZ3SLQFDLANCNFSM4CNB5OKQ
.


TAJO-2027: Writing Hive UDF integration document

@hyunsik , it's done. Please check.

+1 the patch looks good to me. I'll commit it soon.

I also updated the documentation. But, I missed 'close' tag in the commit log. Could you close this ticket?

See http://tajo.apache.org/docs/devel/functions/hivefunc.html

Thanks, I close this one.


Tutorial and default install on Ubuntu 14.4 give SQLite DateTime type only accepts Python error when running pipelines

Hello, I instaled Airflow 1.6.1 on Ubuntu 14.4, running Python 2.7. I can start the AirFlow server, visit the web UI, however if I try and "run" any of the example DAGs via the UI I get the following error:
raise TypeError("SQLite DateTime type only accepts Python "
StatementError: (exceptions.TypeError) SQLite DateTime type only accepts Python datetime and date objects as input. [SQL: u'INSERT INTO log (dttm, dag_id, task_id, event, execution_date, owner, extra) VALUES (?, ?, ?, ?, ?, ?, ?)'] [parameters: [{'task_id': u'runme_0', 'extra': "[('origin', u'http://localhost:8080/admin/airflow/graph?root=&dag_id=example_bash_operator'), ('force', u'false'), ('deps', u'false'), ('task_id', u'runme_0'), ('execution_date', u'2015-01-01T00:00:00'), ('dag_id', u'example_bash_operator')]", 'execution_date': u'2015-01-01T00:00:00', 'event': 'run', 'owner': 'anonymous', 'dttm': datetime.datetime(2015, 12, 10, 22, 31, 22, 996435), 'dag_id': u'example_bash_operator'}]]

The error also happened when the scheduler tried to run the tasks.
I can, however, from the terminal run the command airflow backfill tutorial -s 2015-06-01 -e 2015-06-07 and the code executes without errors.

Good catch, looks like a legit bug. Can you please paste the full stacktrace?
Looks like we just need to cast to datetime somewhere in that view.

                          ____/ (  (    )   )  \___
                         /( (  (  )   _    ))  )   )\
                       ((     (   )(    )  )   (   )  )
                     ((/  ( _(   )   (   _) ) (  () )  )
                    ( (  ( (_)   ((    (   )  .((_ ) .  )_
                   ( (  )    (      (  )    )   ) . ) (   )
                  (  (   (  (   ) (  _  ( _) ).  ) . ) ) ( )
                  ( (  (   ) (  )   (  ))     ) _)(   )  )  )
                 ( (  ( \ ) (    (_  ( ) ( )  )   ) )  )) ( )
                  (  (   (  (   (_ ( ) ( _    )  ) (  )  )   )
                 ( (  ( (  (  )     (_  )  ) )  _)   ) _( ( )
                  ((  (   )(    (     _    )   _) _(_ (  (_ )
                   (_((__(_(__(( ( ( |  ) ) ) )_))__))_)___)
                   ((__)        \\||lll|l||///          \_))
                            (   /(/ (  )  ) )\   )
                          (    ( ( ( | | ) ) )\   )
                           (   /(| / ( )) ) ) )) )
                         (     ( ((((_(|)_)))))     )
                          (      ||\(|(|)|/||     )
                        (        |(||(||)||||        )
                          (     //|/l|||)|\\ \     )
                        (/ / //  /|//||||\\  \ \  \ _)
-------------------------------------------------------------------------------
Node: airflow-test
-------------------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask_admin/base.py", line 68, in inner
    return self._run_view(f, *args, **kwargs)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask_admin/base.py", line 359, in _run_view
    return fn(self, *args, **kwargs)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/flask_login.py", line 755, in decorated_view
    return func(*args, **kwargs)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/airflow/www/utils.py", line 95, in wrapper
    session.commit()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 801, in commit
    self.transaction.commit()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 392, in commit
    self._prepare_impl()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 372, in _prepare_impl
    self.session.flush()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 2015, in flush
    self._flush(objects)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 2133, in _flush
    transaction.rollback(_capture_exception=True)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/util/langhelpers.py", line 60, in __exit__
    compat.reraise(exc_type, exc_value, exc_tb)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/session.py", line 2097, in _flush
    flush_context.execute()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 373, in execute
    rec.execute(self)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/unitofwork.py", line 532, in execute
    uow
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 174, in save_obj
    mapper, table, insert)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/persistence.py", line 785, in _emit_insert_statements
    execute(statement, params)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 914, in execute
    return meth(self, multiparams, params)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/sql/elements.py", line 323, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1010, in _execute_clauseelement
    compiled_sql, distilled_params
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1078, in _execute_context
    None, None)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1341, in _handle_dbapi_exception
    exc_info
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 199, in raise_from_cause
    reraise(type(exception), exception, tb=exc_tb)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1073, in _execute_context
    context = constructor(dialect, self, conn, *args)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 582, in _init_compiled
    param.append(processors[key](compiled_params[key]))
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/dialects/sqlite/base.py", line 601, in process
    raise TypeError("SQLite DateTime type only accepts Python "
StatementError: (exceptions.TypeError) SQLite DateTime type only accepts Python datetime and date objects as input. [SQL: u'INSERT INTO log (dttm, dag_id, task_id, event, execution_date, owner, extra) VALUES (?, ?, ?, ?, ?, ?, ?)'] [parameters: [{'task_id': u'print_date', 'extra': "[('origin', u'http://localhost:8080/admin/airflow/graph?dag_id=tutorial'), ('force', u'false'), ('deps', u'false'), ('task_id', u'print_date'), ('execution_date', u'2015-06-07T00:00:00'), ('dag_id', u'tutorial')]", 'execution_date': u'2015-06-07T00:00:00', 'event': 'run', 'owner': 'anonymous', 'dttm': datetime.datetime(2015, 12, 11, 19, 7, 44, 43123), 'dag_id': u'tutorial'}]]```

Looks like this commit fixed the problem: https://github.com/airbnb/airflow/commit/c4d0fe93ed8185114364984e5eafa1b1fc404a0c#diff-6ff6b61554e53188d97c129ed40256cd
However it's not part of the package that pip install picks up (code still lists itself as v. 1.6.1).

I did a pip install -U git+https://github.com/airbnb/airflow@master. Restarted the webserver and the scheduler, but now the scheduler fails with:
[2015-12-11 21:26:25,114] {jobs.py:633} INFO - Done queuing tasks, calling the executor's heartbeat
[2015-12-11 21:26:25,114] {jobs.py:636} INFO - Loop took: 0.136741 seconds
[2015-12-11 21:26:25,182] {models.py:222} INFO - Finding 'running' jobs without a recent heartbeat
[2015-12-11 21:26:25,183] {models.py:228} INFO - Failing jobs without heartbeat after 2015-12-11 21:24:10.183023
[2015-12-11 21:26:25,183] {jobs.py:644} ERROR - Could not find a FROM clause to join from.  Tried joining to <class 'airflow.jobs.LocalTaskJob'>, but got: Can't find any foreign key relationships between 'task_instance' and 'job'.
Traceback (most recent call last):
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/airflow/jobs.py", line 642, in _execute
    dagbag.kill_zombies()
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/airflow/utils.py", line 132, in wrapper
    result = func(*args, **kwargs)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/airflow/models.py", line 232, in kill_zombies
    .join(LJ)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 1942, in join
    from_joinpoint=from_joinpoint)
  File "<string>", line 2, in _join
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/base.py", line 201, in generate
    fn(self, *args[1:], **kw)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2085, in _join
    outerjoin, create_aliases, prop)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2153, in _join_left_to_right
    self._join_to_left(l_info, left, right, onclause, outerjoin)
  File "/home/ubuntu/anaconda2/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2281, in _join_to_left
    "Tried joining to %s, but got: %s" % (right, ae))
InvalidRequestError: Could not find a FROM clause to join from.  Tried joining to <class 'airflow.jobs.LocalTaskJob'>, but got: Can't find any foreign key relationships between 'task_instance' and 'job'.```

Tried airflow resetdb but still get the error above.

Also airflow upgradedb didn't change anything.

Time is probably ripe for 1.6.2

out of the box i'm having the same problem

Same here...


"brew audit --fix --cask" - doesn't check sha256

brew config output
HOMEBREW_VERSION: 3.1.9-68-g990d5f0
ORIGIN: https://github.com/Homebrew/brew
HEAD: 990d5f048fa429b15b2babe7c639104ce11da152
Last commit: 12 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 16c46fe92664bcd3484e4b26381dd3b4b5212a2d
Core tap last commit: 46 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_BAT: set
HOMEBREW_CASK_OPTS: []
HOMEBREW_CLEANUP_PERIODIC_FULL_DAYS: 3
HOMEBREW_CLEANUP_MAX_AGE_DAYS: 3
HOMEBREW_EDITOR: code --goto
HOMEBREW_MAKE_JOBS: 12
HOMEBREW_NO_ANALYTICS: set
HOMEBREW_UPDATE_REPORT_ONLY_INSTALLED: set
HOMEBREW_VERBOSE_USING_DOTS: set
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 12.0.5 build 1205
Git: 2.31.1 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.5-x86_64
CLT: <IP_ADDRESS>.1.1617976050
Xcode: N/A

brew doctor output
Your system is ready to brew.

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
Trying to create a new PR for an existing cask: https://github.com/Homebrew/homebrew-cask-versions/pull/11092
What happened (include all command output)?
brew audit --fix --cask did not report that I had an incorrect sha256. I used to run the cask with an empty string - and the old behavior used to warn about a missing sha, but would continue and then report the expected value. This was a shortcut to copy-paste into the cask file before committing and raising the PR. Now, it didn't download the asset and so didn't complain at all for a random string (only complained about missing/empty, and the length of the random string).
What did you expect to happen?
I expected that the sha would actually be checked after downloading the asset.
Step-by-step reproduction instructions (by running brew commands)
1. Edit a pre-existing cask file (say `Casks/ferdi-beta.rb` in the `homebrew-cask-versions` repo
2. Replace the `sha256` string with another random string of the same length, but not the same as the downloaded file.
3. See the absence of any error.

Try adding --online to brew audit

Thanks @Rylan12 : that works! Maybe I missed the documentation, could that be verified please? Closing the ticket for now.

From brew help audit:
      --online                     Run additional, slower style checks that
                                   require a network connection.

To check the sha256 requires downloading the file and, thus, a network connection. This command (well really it's brew audit --appcast --online I believe) is what's run by our CI.

So, the github issue template (while submitting the PR) doesn't mention --online, nor the --appcast

You could open a PR if you think it should be added. I don't know if there's a reason as to why it isn't already there.


Use maven central to pull down cloud debugger dependency

Instead of bundling the jar.
http://maven-repository.com/artifact/com.google.apis/google-api-services-clouddebugger

Looks like this is related to #463


Android TV support

Reddit user requested Android TV support.
What needs to happen for the APK to be supported on Android TV? My guess is better landscape support to start.

Agreed to this. LBRY is very suited for Android TV.

   The app must work for using a "remote" to navigate etc. and not require a keyboard or touch only.   It must work on AndroidTV, FireTV, and other TV platforms.

I've tested installing LBRY Android App from the AptoideTV App on a Nvidia Shield and it works fine. however the UI is not optimized for remote control usage. It needs a UI rework to be more TV friendly, like video browsing and autoplay in full screen (maybe a new video player interface) when clicking a video.

Resource and guidelines for Android TV apps:
https://developer.android.com/training/tv/start

Google uses https://cobalt.foo/ for it's own YouTube TV app

I'm sad that there's still no App available to replace YouTube for my new Android 10 tv.
I tried odysee.com in the Paraffin browser.
While it works the audio and video track are not in sync and the overall usability isn't great since you have to rely on a cursor instead of jumping to the buttons.
Can this get a bit more priority? There are huge amounts of Android TV devices out there, which also have constant power and internet.
If Android TV allows background services they could help to stabilize the network, since mobile clients have a hard time doing this.

I started a project for Android TV app, any feedback or pull requests are welcome!
https://github.com/linimin/lbry-androidtv

I started a project for Android TV app, any feedback or pull requests are welcome! https://github.com/linimin/lbry-androidtv

Awesome!


docs:  changing the documentation, the installation instructions not right to close #2

Issue
In the documentation, the installation instruction is not right
In the document README.md it shows the instruction to install the library, but it is not published like this in NPM.
npm install -S keycloak-backend-ts
To Reproduce
Steps to reproduce the behavior:

Go to '/README.md'
See installation instruction

What to do?
Just change the package name according to what was published in NPM

Codecov Report

Merging #3 (b7846fd) into main (a14f98e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   85.03%   85.03%
=======================================
  Files           7        7
  Lines         147      147
  Branches       18       18
=======================================
  Hits          125      125
  Misses         11       11
  Partials       11       11

Flag
Coverage Δ

unittests
85.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


extensionPath needs to be escaped or wrapped in quotes

https://github.com/asvetliakov/vscode-neovim/blob/9bf0183ac5c96fc8ee78cbec09e639d475f443c0/src/main_controller.ts#L103
If the extension path is not quoted (or escaped), paths with space in them cause the above to throw the error:
Unable to init vscode-neovim: Command failed:
C:\Windows\system32\wsl.exe wslpath c:\\Users\\My Name\\.vscode\\extensions\\asvetliakov.vscode-neovim-0.0.76
wslpath: Invalid argument

This is due to the space in the path in 'My Name'.
Adding single quotes around ${extensionPath} fixed the issue.

PR welcome

PR welcome


Could not find a configuration file for package, even through the package installed successfully

Describe the bug
Could not find a configuration file for package, even through the package installed successfully
Environment

OS: [Windows10]
Compiler: Visual Studio 16 2019 -A x64

To Reproduce
Steps to reproduce the behavior:

run vcpkg integrate install
install glfw3 by running: vcpkg install glfw3:x64-windows
Calling CMake command with vcpkg toolchain file vcpkg/scripts/buildsystems/vcpkg.cmake
find glfw3 using find_package(glfw3 REQUIRED), then it'll fail

Expected behavior
Found installed glfw3 without error
Failure logs
CMake Error at C:/Users/zhuwa.ADS/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
[cmake]   Could not find a configuration file for package "glfw3" that is compatible
[cmake]   with requested version "".
[cmake]
[cmake]   The following configuration files were considered but not accepted:
[cmake]
[cmake]     C:/Users/zhuwa.ADS/vcpkg/installed/x64-windows/share/glfw3/glfw3Config.cmake, version: 3.3.2 (64bit)
[cmake] -- Configuring incomplete, errors occurred!

Additional context
This bug is not always appeared. Sometimes, it'll be failed, sometimes not.

In general this happens if the architecture does not match i.e. x86 vs x64.
Maybe you are sometimes switching architecture without noticing it?

Yes, it is the reason indeed. Thanks for your answer.


chore(deps): update renovate/renovate docker tag to v37.5.3

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
37.1.3 -> 37.5.3

Release Notes

renovatebot/renovate (renovate/renovate)
v37.5.3
Compare Source
Bug Fixes

add httpsCertificate, httpsPrivateKey and httpsCertificateAuthority into redactedFields (#25013) (4670e3b)

Miscellaneous Chores

deps: update dependency @types/markdown-it to v13.0.2 (#25010) (74d2a48)
deps: update dependency type-fest to v4.3.3 (#25011) (75d828f)

v37.5.2
Compare Source
Build System

deps: update dependency zod to v3.22.3 [security] (#25007) (47c0b78)

v37.5.0
Compare Source
Features

cargo: support private crate (#24704) (3c592a2)

Code Refactoring

remove duplicate dependency names in warning (#24992) (adca94e)

v37.4.1
Compare Source
Bug Fixes

Correct variable interpolation in error message (#24991) (2a548e7)

Documentation

config options: explain prCreation=approval (#24949) (3a19e5e)

v37.3.3
Compare Source
Bug Fixes

package-rules: matchCurrentVersion with null versioning (#24965) (b66df6e)

Miscellaneous Chores

deps: update dependency memfs to v4.5.0 (#24967) (dfcbe08)
deps: update dependency rimraf to v5.0.2 (#24966) (cb67d76)
deps: update dependency rimraf to v5.0.4 (#24969) (87edb30)
deps: update dependency rimraf to v5.0.5 (#24970) (c8fceec)

v37.3.2
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.20.8 (#24962) (be9d896)

Miscellaneous Chores

deps: update dependency @types/semver to v7.5.3 (#24961) (7b025ce)

v37.3.1
Compare Source
Bug Fixes

versionCompatibility: fix compatibility suffix (#24954) (e6fdecd)

Documentation

versionCompatbility: fix suffix example (8a0956d)

Miscellaneous Chores

improve descriptions (#24946) (45ca2cf)

Code Refactoring

types: optional newValue (#24953) (1b70c42)

Continuous Integration

drop actions/stale bot for issues and PRs (#24950) (260c9af)

v37.3.0
Compare Source
Features

versionCompatibility (#24717) (42b3a7c)

Documentation

update references to renovate/renovate to v37 (#24935) (4b9bb12)

Code Refactoring

helm: More idiomatic schema usage (#24934) (d847715)

v37.2.0
Compare Source
Features

schema-utils: Add MultidocYaml helper (#24933) (e324907)

Miscellaneous Chores

deps: update dependency @types/aws4 to v1.11.4 (#24711) (2611b88)

Code Refactoring

npm: Simplify .yarnrc parsing (#24931) (906c982)

v37.1.6
Compare Source
Bug Fixes

deps: update ghcr.io/containerbase/sidecar docker tag to v9.20.7 (#24733) (b9a660a)

Documentation

Fix typo in .pages (#24718) (cb68571)

Miscellaneous Chores

deps: update dependency @types/eslint to v8.44.3 (#24719) (d1fb5b5)
deps: update linters (#24720) (8341845)

v37.1.5
Compare Source
Build System

deps: update dependency simple-git to v3.20.0 (#24715) (19b9a5d)

v37.1.4
Compare Source
Bug Fixes

allow more than 99 PRs/branches per repository (#24705) (666819e)

Miscellaneous Chores

deps: update dependency @types/auth-header to v1.0.3 (#24710) (7c83d59)
deps: update dependency @types/diff to v5.0.5 (#24712) (f8178d7)
deps: update dependency @types/lodash to v4.14.199 (#24713) (5f9dc20)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.2.9 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Technical debt on token issuers

Summary
With the explosion of tokens on the XRPL, there is a lot of people rushing to create tokens to simply grab at the rise in interest. This is great, but now we are facing issues with scaling and debit on the infrastructure in place.
Motivation
The idea is to impose a level of technical debit on the token issuers. As fees associated with issuance seem to be of issue to some.
Solution
Require the running of a node/validator to issue a token.

It help provide infrastructure to the network that is currently abused by free loaders.
It help require some technical skill from the issuers. At the moment anyone can run to a faucet and issue a token.

Idea is to have a pointer from the validator to an account that only then allows an account to issue a token.

I am not convinced that more people running nodes will solve the scalability problems. I think more people using their own nodes for RPC will take the load off of public services like s2 and xrplcluster.com, but there are numerous other load problems that would not be affected by more people running nodes. For instance, nodes are taking a long time to sync. More people running nodes most likely won't improve sync times, as each node still needs to sync fully. Maybe the peer network will have more capacity if more people run nodes, but it also could lose capacity if people run nodes that don't perform that well. Or consider the fee issue. More nodes on the network is not necessarily going to bring down fees.
I should also note the there has been significant work on the public facing services front. Reporting mode exists in rippled today, and allows people to run public facing RPC services in a much more scalable way. Project clio (https://github.com/cjcobb23/clio) is coming soon, and further improves on reporting mode.

I do agree with the notion that we should make issuing a token cost more to the issuer. What if we just charge higher fees, or a higher reserve, or even burn the reserve?

Do not confuse the issue of trustset transaction SPAM, that is another issue. This is around only the issuance of a new token.
The wider ecosystem using and running trustset transactions can be handled by fees, that is relatively straight forward. This issue is around tokens like BumcrackXRP raising the technical "debit" level these issuers need to cross filters out a lot of this rubbish.

I do agree that issuing tokens should with some sort of commitment/cost to the issuer that ultimately benefits the network.
At the very least I think large issuers should connect to their own nodes rather than leeching off the public clusters. How to go about that is the challenging part.

I've had a few conversations about nodes and it is safe to say that if we implement such thing:

Require the running of a node/validator to issue a token.

Is not appropriate to force users of the XRP Ledger to run their own rippled servers since we need node maintainers that know what they're doing, it takes a considerable amount of time to understand the basics of linux CL, hardware, distros, the XRP Ledger, rippled and not only that, if the network shits itself, we need node maintainers that can understand the crisis and try fixing their own nodes without needing support from rippled maintainers.
I'm also not saying that people shouldn't try running their own server(s) since experience is one of the most important building blocks in this industry. It's generally  just not appropriate to force users to participate in the network's consensus to use it's features, it creates an unbalanced network where a good majority of its participants are forced to do so with bad tools and hardware.
Hopefully, once Lite Accounts are deployed, more users migrate there, this creates a situation where users are only allowed to mint tokens via privileged accounts (normal accounts, similar to today's).


Pickle error on using loguru with ray (hashtag706)

Hi. I'm facing this error on running loguru with [ray remote]( I think I'm missing something here. I went through the documentation and I couldn't find anything helpful to solve my specific issue. I noticed from issue hashtag386 that  has mentioned "The logger [is picklable]( as long as the added handlers are picklable too". Is it because of this? Appreicate the help. Thanks for the wonderful library. Loguru has made logging very easy.
hashtaghashtaghashtag Code
from loguru import logger
import ray

logger.add(f'logs/{__name__}', filter=__name__, rotation='1 week')

class StartUp:
    def start(self):
        for i in range(10000):
            logger.info(i)

def run():
    logger.info("started!")
    agents = [StartUp.remote() for i in range(4)]
    result = []
    for count , agent in enumerate(agents):
        logger.info(count)
        result.append(agent.start.remote())
    done_id, _ = ray.wait(result)
    logger.info("complete!")

if __name__ == "__main__":
    run()

hashtaghashtaghashtag Dependencies
[tool.poetry.dependencies]
python = "3.8.13"
ray = {extras = ["default"], version = "1.13.0"}
loguru = "0.6.0"

hashtaghashtaghashtag Error
Traceback (most recent call last):
  File "test.py", line 23, in <module>
    run()
  File "test.py", line 13, in run
    agents = [StartUp.remote() for i in range(4)]
  File "test.py", line 13, in <listcomp>
    agents = [StartUp.remote() for i in range(4)]
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/actor.py", line 529, in remote
    return self._remote(args=args, kwargs=kwargs, **self._default_options)
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/util/tracing/tracing_helper.py", line 387, in _invocation_actor_class_remote_span
    return method(self, args, kwargs, *_args, **_kwargs)
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/actor.py", line 844, in _remote
    worker.function_actor_manager.export_actor_class(
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/_private/function_manager.py", line 461, in export_actor_class
    serialized_actor_class = pickle.dumps(Class)
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/cloudpickle/cloudpickle_fast.py", line 73, in dumps
    cp.dump(obj)
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/cloudpickle/cloudpickle_fast.py", line 620, in dump
    return Pickler.dump(self, obj)
  File "/home/blue/.cache/pypoetry/virtualenvs/loguru-ray-test-l4hNMfu6-py3.8/lib/python3.8/site-packages/ray/cloudpickle/cloudpickle_fast.py", line 320, in _file_reduce
    raise pickle.PicklingError(
_pickle.PicklingError: Cannot pickle files that are not opened for reading: a

Hi.
I don't know how ray is implemented under the hood, but if it spawn sub-processes and try to pickle all local objects, then it can indeed cause the PicklingError you're facing.
You'll need to find a way to make the child process "inherit" the logger object using ray API, possibly involving enqueue=True. This part of the documentation may give you some insights: [Compatibility with multiprocessing using enqueue argument](

I think I have some idea now and I'm able to successfully run the code with these changes.
from loguru import logger

import ray

logger.add(f'logs/{__name__}__run.log', filter=__name__ , rotation='1 week')

class StartUp:
    def __init__(self, log):
        self.log = log
        self.log.add(f'logs/{__name__}.log', filter=__name__, rotation='1 week')

    def start(self):
        for i in range(10):
            self.log.info(i)

def run():
    logger.info("started!")
    logger.remove()
    agents = [StartUp.remote(logger) for i in range(4)]
    result = []
    logger.add(f'logs/{__name__}__run.log', filter=__name__, rotation='1 week')
    for count , agent in enumerate(agents):
        logger.info(count)
        result.append(agent.start.remote())
    done_id, _ = ray.wait(result)
    logger.info("complete!")

if __name__ == "__main__":
    run()


[$250] Chat - Cursor moves several characters when deleting markdowns on multiline message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.48-0
Reproducible in staging?: Y
Issue reported by: Applause Internal Team
Action Performed:

Open the staging.new.expensify.com website.
Open any chat.
Write a multiline message with at least five line breaks and three markdowns and send it.
Long tap over the sent message.
Tap on "Edit Message"
Delete the markdowns at the end of the message.
Verify the cursor moves only one character everytime a markdown is deleted.

Expected Result:
The cursor should move only one character at the time while deleting markdowns at the end of a message.
Actual Result:
When deleting the markdowns at the end of a multiline message while editing, the cursor moves several characters at the time.
Workaround:
Unknown
Platforms:

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/1648cb08-1348-4926-a0a0-a03fc2650018

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021847007161571207373
Upwork Job ID:<PHONE_NUMBER>571207373
Last Price Increase: 2024-11-21

Issue OwnerCurrent Issue Owner: @thesahindia

We think that this bug might be related to #wave-collect - Release 1

@OfstadC  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
Chat - Cursor moves several characters when deleting markdowns on multiline message
What is the root cause of that problem?
The problem comes from react-native-live-markdown package.
The package has custom cursor management logic  and those works well. The issue occurs because the custom cursor management logic runs faster than React’s native text update. As a result, the cursor is repositioned too early. When React completes its slower text update, it overwrites the manually set cursor position, causing it to be incorrect. This timing mismatch leads to the cursor jumping to the wrong place.
What changes do you think we should make in order to solve the problem?
Wrapping this code in InteractionManager will solve the problem
InteractionManager.runAfterInteractions(() => {
  switch (inputType) {
    case 'historyUndo':
      newInputUpdate = undo(divRef.current);
      break;
    case 'historyRedo':
      newInputUpdate = redo(divRef.current);
      break;
    default:
      console.log(111111111)
      newInputUpdate = parseText(divRef.current, parsedText, processedMarkdownStyle, newCursorPosition, true, !inputType, inputType === 'pasteText');
  }
})

What alternative solutions did you explore? (Optional)

I did not experience this. I also think this is kind of an odd scenario that is unlikely to occur for a user (must have 5 line breaks and 3 markdowns seems like an odd equation ) - So going to close this out

@OfstadC The bug is actual now, and it happens with even with 1 or 2 line breaks. I am Sorry but I think you should retest

Hi @thesahindia. Did you notice my proposal above ?

@thesahindia could you please review the available proposal by EOD? Thank you 😃

@thesahindia It is reproducible in last main
https://github.com/user-attachments/assets/b3cb9521-b377-4082-a397-59a1a9b64ae8

I still can't repro it. @OfstadC, could you please look into it?

Have you tested android mWeb

I was able to repro it on mWeb. @shahinyan11, could you repro it on native or is it just a mWeb issue?

I could repro only on mWeb

Proposal
Updated Since the package was updated, the previous solution stopped working and I updated the proposal.

Any update @thesahindia 😃

Bump @shahinyan11 Please update by EOD tomorrow 😃 Thanks!

Bump @shahinyan11 Please update by EOD tomorrow 😃 ThankS!

Hi @OfstadC . I think you have mentioned me by mistake an it should be addressed to @thesahindia . If not, please clarify what update you mean.

Proposal
Please re-state the problem that we are trying to solve in this issue.
The issue with the react-native-live-markdown package stems from its custom cursor management logic. While this logic operates smoothly, it moves faster than React’s native text update process. Consequently, the cursor gets repositioned prematurely. When React’s slower text update completes, it overrides the manually set cursor position, resulting in an incorrect cursor placement. This timing discrepancy causes the cursor to jump to an unintended spot.
What is the root cause of that problem?
Enclosing this code within InteractionManager can effectively address the timing issue. By using InteractionManager, the custom cursor management logic can wait until React’s text update process is complete, helping ensure the cursor position is correctly maintained and preventing the cursor from jumping to the wrong spot.
What changes do you think we should make in order to solve the problem?

What alternative solutions did you explore? (Optional)
InteractionManager.runAfterInteractions(()=> {
if (shouldForceDOMUpdate || targetElement.innerHTML !== dom.innerHTML) {
const animationTimes = getAnimationCurrentTimes(targetElement);
targetElement.innerHTML = '';
targetElement.innerText = '';
targetElement.innerHTML = dom.innerHTML;
updateAnimationsTime(targetElement, animationTimes);
}
updateTreeElementRefs(tree, targetElement);
targetElement.tree = tree;
moveCursor(isFocused, alwaysMoveCursorToTheEnd, cursorPosition, targetElement, shouldScrollIntoView);
})

Proposal
Please re-state the problem that we are trying to solve in this issue.
The issue with the react-native-live-markdown package stems from its custom cursor management logic. While this logic operates smoothly, it moves faster than React’s native text update process. Consequently, the cursor gets repositioned prematurely. When React’s slower text update completes, it overrides the manually set cursor position, resulting in an incorrect cursor placement. This timing discrepancy causes the cursor to jump to an unintended spot.
What is the root cause of that problem?
Enclosing this code within InteractionManager can effectively address the timing issue. By using InteractionManager, the custom cursor management logic can wait until React’s text update process is complete, helping ensure the cursor position is correctly maintained and preventing the cursor from jumping to the wrong spot.
What changes do you think we should make in order to solve the problem?
InteractionManager.runAfterInteractions(()=> {
  if (shouldForceDOMUpdate || targetElement.innerHTML !== dom.innerHTML) {
    const animationTimes = getAnimationCurrentTimes(targetElement);
    targetElement.innerHTML = '';
    targetElement.innerText = '';
    targetElement.innerHTML = dom.innerHTML;
    updateAnimationsTime(targetElement, animationTimes);
  }
  updateTreeElementRefs(tree, targetElement);
  targetElement.tree = tree;

  moveCursor(isFocused, alwaysMoveCursorToTheEnd, cursorPosition, targetElement, shouldScrollIntoView);
})

What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
Chat - Cursor moves several characters when deleting markdowns on multiline message
What is the root cause of that problem?
The issue with the react-native-live-markdown package stems from its custom cursor management logic. While this logic operates smoothly, it moves faster than React’s native text update process. Consequently, the cursor gets repositioned prematurely. When React’s slower text update completes, it overrides the manually set cursor position, resulting in an incorrect cursor placement. This timing discrepancy causes the cursor to jump to an unintended spot.
What changes do you think we should make in order to solve the problem?
Enclosing this code within InteractionManager can effectively address the timing issue. By using InteractionManager, the custom cursor management logic can wait until React’s text update process is complete, helping ensure the cursor position is correctly maintained and preventing the cursor from jumping to the wrong spot.
InteractionManager.runAfterInteractions(()=> {
  if (shouldForceDOMUpdate || targetElement.innerHTML !== dom.innerHTML) {
    const animationTimes = getAnimationCurrentTimes(targetElement);
    targetElement.innerHTML = '';
    targetElement.innerText = '';
    targetElement.innerHTML = dom.innerHTML;
    updateAnimationsTime(targetElement, animationTimes);
  }
  updateTreeElementRefs(tree, targetElement);
  targetElement.tree = tree;

  moveCursor(isFocused, alwaysMoveCursorToTheEnd, cursorPosition, targetElement, shouldScrollIntoView);
})

What alternative solutions did you explore? (Optional)

@thesahindia Looks like we have a new proposal to review 😃

Bump @thesahindia

Sorry for the confusion here! Looks like this is waiting for some more proposals 😃

Proposal
Note I noticed that another member had previously posted a proposal here, but since there are currently no proposals, I decided to post a new proposal whose proposed and it may be similar to the proposal that was there previously.
Please re-state the problem that we are trying to solve in this issue.
Chat - Cursor moves several characters when deleting markdowns on multiline message
What is the root cause of that problem?
The problem with the react-native-live-markdown package lies in how it handles cursor management. The custom logic for the cursor works effectively but operates at a quicker pace compared to React’s default text updating mechanism. As a result, the cursor gets repositioned too early. When the slower React text update concludes, it overwrites the cursor position that was set manually. This mismatch in timing leads to the cursor appearing in an incorrect location, causing it to unexpectedly jump to a different point in the text.
What changes do you think we should make in order to solve the problem?
Move this  code in callback of  InteractionManager.runAfterInteractions
InteractionManager.runAfterInteractions(()=> {
  if (shouldForceDOMUpdate || targetElement.innerHTML !== dom.innerHTML) {
    const animationTimes = getAnimationCurrentTimes(targetElement);
    targetElement.innerHTML = '';
    targetElement.innerText = '';
    targetElement.innerHTML = dom.innerHTML;
    updateAnimationsTime(targetElement, animationTimes);
  }
  updateTreeElementRefs(tree, targetElement);
  targetElement.tree = tree;

  moveCursor(isFocused, alwaysMoveCursorToTheEnd, cursorPosition, targetElement, shouldScrollIntoView);
})

What alternative solutions did you explore? (Optional)

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~0183b679e4e9629baa

Issue not reproducible during KI retests. (First week)

Waiting on proposals

Issue not reproducible during KI retests. (Second week)

Issue not reproducible during KI retests. (Third week)


Enable dovecot antispam

Add dovecot-antispam package (and fix yaml error but that is addressed by PR #3 so approve that first?)
Change antispam backend from pipe to mailtrain (since we are using the forked version)
Add documentation on how to enable it (ansible will not enable it by default as this can be considered optional functionality)

I also got some information off this: https://kaworu.ch/blog/2014/03/25/dovecot-antispam-with-rspamd/
Gives more background to the backend and config.


Serializer fails because of old nilportugues/php-serializer dependency

Hi,
while trying to serialize an object I ran into an issue that was fixed already here:
https://github.com/nilportugues/php-serializer/commit/8489eabb7c67a2ef8507f8af22238c135ee9bf3c
This is because symfony-jsonapi relies on
"nilportugues/json-api": "^2.4"
which relies on
"nilportugues/api-transformer": "^3.0.0"
which relies on
"nilportugues/serializer": "~1.1"
I installed the package about 2 days ago. According to https://getcomposer.org/doc/articles/versions.md#tilde version 1.2 of serializer should have been installed, but it wasn't. Instead I have this in my composer.lock file (excerpt):
snip snip
{
            "name": "nilportugues/serializer",
            "version": "1.1.5",
            "source": {
                "type": "git",
                "url": "https://github.com/nilportugues/serializer.git",
                "reference": "82ede04c687336aaec5f1c58f3ec986626b05810"
            },
},
{
            "name": "nilportugues/api-transformer",
            "version": "3.0.0",
            "source": {
                "type": "git",
                "url": "https://github.com/nilportugues/php-api-transformer.git",
                "reference": "4e2743527b7deb7af5b4ef55f2ca33146e9fab65"
            },
},
{
            "name": "nilportugues/json-api",
            "version": "2.4.4",
            "source": {
                "type": "git",
                "url": "https://github.com/nilportugues/php-json-api.git",
                "reference": "87d5898dee49670df8c67c81014db3c31cf94202"
            },
},
{
            "name": "nilportugues/jsonapi-bundle",
            "version": "1.5.2",
            "source": {
                "type": "git",
                "url": "https://github.com/nilportugues/symfony-jsonapi.git",
                "reference": "c4bbdfec0bb0b402aa0057fd32d1225447988460"
            },
}

Any idea what's wrong with the dependencies?

I'm using your bundle together with Symfony 3. The problem was related to the platform requirements. I added the current serializer version explicitly to my composer.json and got the following error:
 Problem 1
    - Installation request for nilportugues/serializer ^1.2 -> satisfiable by nilportugues/serializer[1.2.0].
    - nilportugues/serializer 1.2.0 requires php >=5.6.0 -> your PHP version (7.1.1) overridden by "config.platform.php" version (5.5.9) does not satisfy that requirement.

In my particular use case it's ok to run composer with --ignore-platform-reqs, it works correctly then.

I will dig into it, I don't want people using the --ignore-platform-reqs

Fixed on the underlying library


slaExtension hitting default "safety" case when Actively Exploited CVEs is true

I think I've found a situation where the slaExtension value is hitting the default of 90 days. When simulating the Nudge prompt for different, older OS versions, macOS 14.4 is showing a deadline of 74 days from today.
14.5 and 14.6 seem to be calculating the correct deadline dates of 12 and 21 days from today, respectively. (I'd be kind of surprised if someone went to the effort to update their Mac from 14.5 to 14.6 and not all the way to 14.6.1, and they would probably be Nudged to update to 14.6.1  anyway so seems like it's all good for our use case.)
The only difference that I've been able to see in all of the Nudge screens for the test cases is that 14.4 has Actively Exploited CVEs: true whereas all the others (14.4.1, 14.5, 14.6) have Actively Exploited CVEs: false
I thought I'd post here given the code says:
https://github.com/macadmins/nudge/blob/9014f1df0464263a32786956964393d29c3b8d78/Nudge/UI/Main.swift#L273-L274
It's also possible that I've completely mis-identified the cause of this. Regardless, I think that macOS 14.4 having 74 days to update to a more recent OS version is incorrect.

Nudge version: <IP_ADDRESS>783
macOS host version: 14.6.1 (23G93)
Nudge config deployed using the latest Jamf schema, I've updated it today to ensure it's the latest.
Customised values:

optionalFeatures

acceptableCameraUsage: true
acceptableUpdatePreparingUsage: true
acceptableScreenSharingUsage: true
utilizeSOFAFeed: true (I know this is likely redundant, but including it to make it clear to anyone who looks at the config in Jamf)

osVersionRequirements

osVersionRequirement1
minorVersionRecalculationThreshold: 1
requiredMinimumOSVersion: latest-minor

userExperience

nudgeMinorUpdateEventLaunchDelay: 3

userInterface

Some of the values (logo, header text) have been customised but I don't think they're relevant to this.

14.6
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -disable-random-delay -simulate-os-version "14.6"

Days remaining to update: 21
2024-08-14 10:30:21.107061+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:30:21.107209+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:preferences-json] osVersionRequirements key is empty - json
2024-08-14 10:30:21.179191+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:preferences-json] userExperience key is empty - json
2024-08-14 10:30:21.179633+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:preferences-json] optionalFeatures key is empty - json
2024-08-14 10:30:21.179647+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Utilizing previously cached SOFA json
2024-08-14 10:30:21.182367+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:30:21.182983+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for active exploits: ["14.6", "14.6.1"]
2024-08-14 10:30:21.183022+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:30:21.183030+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] Device requireMajorUpgrade: false
2024-08-14 10:30:21.183036+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] SOFA Actively Exploited CVEs: false
2024-08-14 10:30:21.183124+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for recalculation: ["14.6.1"]
2024-08-14 10:30:21.183132+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] minorVersionRecalculationThreshold is set to 1 - Current Version: 14.6 - Targeting version 14.6.1 requiredInstallationDate via SOFA
2024-08-14 10:30:21.183304+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Found target macOS version 14.6.1 - releaseDate is 2024-08-07 00:00:00 +0000, slaExtension is 28 days, 0 hours, 0 minutes, 0 seconds
2024-08-14 10:30:21.183319+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Setting requiredInstallationDate via SOFA to 2024-09-04 00:00:00 +0000
2024-08-14 10:30:21.183325+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] SOFA Matched OS Version: 14.6.1
2024-08-14 10:30:21.183353+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] SOFA Assets: ["J132AP", "J137AP", "J140AAP", "J140KAP", "J152FAP", "J160AP", "J174AP", "J180dAP", "J185AP", "J185FAP", "J213AP", "J214KAP", "J215AP", "J223AP", "J230KAP", "J274AP", "J293AP", "J313AP", "J314cAP", "J314sAP", "J316cAP", "J316sAP", "J375cAP", "J375dAP", "J413AP", "J414cAP", "J414sAP", "J415AP", "J416cAP", "J416sAP", "J433AP", "J434AP", "J456AP", "J457AP", "J473AP", "J474sAP", "J475cAP", "J475dAP", "J493AP", "J504AP", "J514cAP", "J514mAP", "J514sAP", "J516cAP", "J516mAP", "J516sAP", "J613AP", "J615AP", "J680AP", "J780AP", "Mac-1E7E29AD0135F9BC", "Mac-63001698E7A34814", "Mac-937A206F2EE63C01", "Mac-AA95B1DDAB278B95", "VMA2MACOSAP", "VMM-x86_64"]
2024-08-14 10:30:21.183360+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] SOFA CVEs: [:]
2024-08-14 10:30:21.247277+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:softwareupdate-device] Error assessing DeviceID: remotectl: Unable to find device "localbridge".
2024-08-14 10:30:21.247453+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Assessed Model IDs: ["Unknown", "", "J514sAP", "J514sAP"]
2024-08-14 10:30:21.247473+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:sofa] Assessed Model ID found in SOFA Entry: true
2024-08-14 10:30:21.247788+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:30:21.247798+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:30:21.247811+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] Device outside nudgeMinorUpdateEventLaunchDelay
2024-08-14 10:30:21.247886+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:30:21.247896+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:30:21.247896+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:softwareupdate-download] enforceMinorUpdates: true
2024-08-14 10:30:21.247920+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:30:21.247930+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:30:21.275193+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:30:21.279708+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:30:21.279725+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:preferences-json] updateElements key is empty - json
2024-08-14 10:30:21.284787+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] Device allow1HourDeferralButton: true
2024-08-14 10:30:21.285001+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] Device allow24HourDeferralButton: true
2024-08-14 10:30:21.285200+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] Device allowCustomDeferralButton: true
2024-08-14 10:30:21.308814+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] Device requireDualQuitButtons: false
2024-08-14 10:30:21.309048+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] nudgeRefreshCycle: 60
2024-08-14 10:30:21.317659+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Device pastRequiredInstallationDate: false
2024-08-14 10:30:21.317711+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:30:21.351849+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:user-interface] net.kovidgoyal.kitty is currently the frontmostApplication
2024-08-14 10:30:21.352094+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Activating Nudge
2024-08-14 10:30:21.366298+1000  localhost Nudge[53335]: [com.github.macadmins.Nudge:utilities] Activating Nudge

14.5
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -disable-random-delay -simulate-os-version "14.5"

Days remaining to update: 12
2024-08-14 10:29:50.097042+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:50.097192+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:preferences-json] osVersionRequirements key is empty - json
2024-08-14 10:29:50.161077+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:preferences-json] userExperience key is empty - json
2024-08-14 10:29:50.161599+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:preferences-json] optionalFeatures key is empty - json
2024-08-14 10:29:50.161615+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Utilizing previously cached SOFA json
2024-08-14 10:29:50.164360+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:50.164957+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for active exploits: ["14.5", "14.6", "14.6.1"]
2024-08-14 10:29:50.164995+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:50.165003+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] Device requireMajorUpgrade: false
2024-08-14 10:29:50.165014+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] SOFA Actively Exploited CVEs: false
2024-08-14 10:29:50.165115+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for recalculation: ["14.6", "14.6.1"]
2024-08-14 10:29:50.165123+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] minorVersionRecalculationThreshold is set to 1 - Current Version: 14.5 - Targeting version 14.6 requiredInstallationDate via SOFA
2024-08-14 10:29:50.165313+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Found target macOS version 14.6 - releaseDate is 2024-07-29 00:00:00 +0000, slaExtension is 28 days, 0 hours, 0 minutes, 0 seconds
2024-08-14 10:29:50.165327+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Setting requiredInstallationDate via SOFA to 2024-08-26 00:00:00 +0000
2024-08-14 10:29:50.165333+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] SOFA Matched OS Version: 14.6.1
2024-08-14 10:29:50.165364+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] SOFA Assets: ["J132AP", "J137AP", "J140AAP", "J140KAP", "J152FAP", "J160AP", "J174AP", "J180dAP", "J185AP", "J185FAP", "J213AP", "J214KAP", "J215AP", "J223AP", "J230KAP", "J274AP", "J293AP", "J313AP", "J314cAP", "J314sAP", "J316cAP", "J316sAP", "J375cAP", "J375dAP", "J413AP", "J414cAP", "J414sAP", "J415AP", "J416cAP", "J416sAP", "J433AP", "J434AP", "J456AP", "J457AP", "J473AP", "J474sAP", "J475cAP", "J475dAP", "J493AP", "J504AP", "J514cAP", "J514mAP", "J514sAP", "J516cAP", "J516mAP", "J516sAP", "J613AP", "J615AP", "J680AP", "J780AP", "Mac-1E7E29AD0135F9BC", "Mac-63001698E7A34814", "Mac-937A206F2EE63C01", "Mac-AA95B1DDAB278B95", "VMA2MACOSAP", "VMM-x86_64"]
2024-08-14 10:29:50.165372+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] SOFA CVEs: [:]
2024-08-14 10:29:50.228858+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:softwareupdate-device] Error assessing DeviceID: remotectl: Unable to find device "localbridge".
2024-08-14 10:29:50.229008+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Assessed Model IDs: ["Unknown", "", "J514sAP", "J514sAP"]
2024-08-14 10:29:50.229029+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:sofa] Assessed Model ID found in SOFA Entry: true
2024-08-14 10:29:50.229355+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:50.229366+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:50.229379+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] Device outside nudgeMinorUpdateEventLaunchDelay
2024-08-14 10:29:50.229454+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:50.229462+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:50.229465+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:softwareupdate-download] enforceMinorUpdates: true
2024-08-14 10:29:50.229487+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:50.229498+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:50.257906+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:29:50.262124+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:29:50.262138+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:preferences-json] updateElements key is empty - json
2024-08-14 10:29:50.266928+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] Device allow1HourDeferralButton: true
2024-08-14 10:29:50.267145+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] Device allow24HourDeferralButton: true
2024-08-14 10:29:50.267342+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] Device allowCustomDeferralButton: true
2024-08-14 10:29:50.290643+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] Device requireDualQuitButtons: false
2024-08-14 10:29:50.290864+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] nudgeRefreshCycle: 60
2024-08-14 10:29:50.299023+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Device pastRequiredInstallationDate: false
2024-08-14 10:29:50.299074+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:50.331272+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:user-interface] net.kovidgoyal.kitty is currently the frontmostApplication
2024-08-14 10:29:50.331522+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Activating Nudge
2024-08-14 10:29:50.359289+1000  localhost Nudge[53292]: [com.github.macadmins.Nudge:utilities] Activating Nudge

14.4.1
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -disable-random-delay -simulate-os-version "14.4.1"

Days remaining to update: 12
2024-08-14 10:28:03.142743+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:28:03.142918+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:preferences-json] osVersionRequirements key is empty - json
2024-08-14 10:28:03.203276+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:preferences-json] userExperience key is empty - json
2024-08-14 10:28:03.203787+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:preferences-json] optionalFeatures key is empty - json
2024-08-14 10:28:03.203802+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Utilizing previously cached SOFA json
2024-08-14 10:28:03.206642+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:28:03.207256+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for active exploits: ["14.4.1", "14.5", "14.6", "14.6.1"]
2024-08-14 10:28:03.207298+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:28:03.207306+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] Device requireMajorUpgrade: false
2024-08-14 10:28:03.207313+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] SOFA Actively Exploited CVEs: false
2024-08-14 10:28:03.207403+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for recalculation: ["14.5", "14.6", "14.6.1"]
2024-08-14 10:28:03.207414+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] minorVersionRecalculationThreshold is set to 1 - Current Version: 14.4.1 - Targeting version 14.6 requiredInstallationDate via SOFA
2024-08-14 10:28:03.207608+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Found target macOS version 14.6 - releaseDate is 2024-07-29 00:00:00 +0000, slaExtension is 28 days, 0 hours, 0 minutes, 0 seconds
2024-08-14 10:28:03.207623+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Setting requiredInstallationDate via SOFA to 2024-08-26 00:00:00 +0000
2024-08-14 10:28:03.207630+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] SOFA Matched OS Version: 14.6.1
2024-08-14 10:28:03.207658+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] SOFA Assets: ["J132AP", "J137AP", "J140AAP", "J140KAP", "J152FAP", "J160AP", "J174AP", "J180dAP", "J185AP", "J185FAP", "J213AP", "J214KAP", "J215AP", "J223AP", "J230KAP", "J274AP", "J293AP", "J313AP", "J314cAP", "J314sAP", "J316cAP", "J316sAP", "J375cAP", "J375dAP", "J413AP", "J414cAP", "J414sAP", "J415AP", "J416cAP", "J416sAP", "J433AP", "J434AP", "J456AP", "J457AP", "J473AP", "J474sAP", "J475cAP", "J475dAP", "J493AP", "J504AP", "J514cAP", "J514mAP", "J514sAP", "J516cAP", "J516mAP", "J516sAP", "J613AP", "J615AP", "J680AP", "J780AP", "Mac-1E7E29AD0135F9BC", "Mac-63001698E7A34814", "Mac-937A206F2EE63C01", "Mac-AA95B1DDAB278B95", "VMA2MACOSAP", "VMM-x86_64"]
2024-08-14 10:28:03.207665+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] SOFA CVEs: [:]
2024-08-14 10:28:03.272195+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:softwareupdate-device] Error assessing DeviceID: remotectl: Unable to find device "localbridge".
2024-08-14 10:28:03.272449+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Assessed Model IDs: ["Unknown", "", "J514sAP", "J514sAP"]
2024-08-14 10:28:03.272473+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:sofa] Assessed Model ID found in SOFA Entry: true
2024-08-14 10:28:03.272868+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:28:03.272883+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:28:03.272902+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] Device outside nudgeMinorUpdateEventLaunchDelay
2024-08-14 10:28:03.272987+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:28:03.272998+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:28:03.272999+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:softwareupdate-download] enforceMinorUpdates: true
2024-08-14 10:28:03.273022+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:28:03.273034+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:28:03.302767+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:28:03.307723+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:28:03.307743+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:preferences-json] updateElements key is empty - json
2024-08-14 10:28:03.313666+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] Device allow1HourDeferralButton: true
2024-08-14 10:28:03.313875+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] Device allow24HourDeferralButton: true
2024-08-14 10:28:03.314071+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] Device allowCustomDeferralButton: true
2024-08-14 10:28:03.339147+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] Device requireDualQuitButtons: false
2024-08-14 10:28:03.339384+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] nudgeRefreshCycle: 60
2024-08-14 10:28:03.348843+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Device pastRequiredInstallationDate: false
2024-08-14 10:28:03.348915+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:28:03.382037+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:user-interface] net.kovidgoyal.kitty is currently the frontmostApplication
2024-08-14 10:28:03.382316+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Activating Nudge
2024-08-14 10:28:03.400362+1000  localhost Nudge[53204]: [com.github.macadmins.Nudge:utilities] Activating Nudge

14.4
/Applications/Utilities/Nudge.app/Contents/MacOS/Nudge -disable-random-delay -simulate-os-version "14.4"

Days remaining to update: 74
2024-08-14 10:29:17.525074+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:17.525259+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:preferences-json] osVersionRequirements key is empty - json
2024-08-14 10:29:17.599454+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:preferences-json] userExperience key is empty - json
2024-08-14 10:29:17.600516+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:preferences-json] optionalFeatures key is empty - json
2024-08-14 10:29:17.600533+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Utilizing previously cached SOFA json
2024-08-14 10:29:17.603835+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:17.604464+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for active exploits: ["14.4", "14.4.1", "14.5", "14.6", "14.6.1"]
2024-08-14 10:29:17.604499+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:17.604508+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] Device requireMajorUpgrade: false
2024-08-14 10:29:17.604515+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] SOFA Actively Exploited CVEs: true
2024-08-14 10:29:17.604601+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Assessing macOS version range for recalculation: ["14.4.1", "14.5", "14.6", "14.6.1"]
2024-08-14 10:29:17.604612+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] minorVersionRecalculationThreshold is set to 1 - Current Version: 14.4 - Targeting version 14.6 requiredInstallationDate via SOFA
2024-08-14 10:29:17.604791+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Found target macOS version 14.6 - releaseDate is 2024-07-29 00:00:00 +0000, slaExtension is 90 days, 0 hours, 0 minutes, 0 seconds
2024-08-14 10:29:17.604805+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Setting requiredInstallationDate via SOFA to 2024-10-27 00:00:00 +0000
2024-08-14 10:29:17.604811+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] SOFA Matched OS Version: 14.6.1
2024-08-14 10:29:17.604839+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] SOFA Assets: ["J132AP", "J137AP", "J140AAP", "J140KAP", "J152FAP", "J160AP", "J174AP", "J180dAP", "J185AP", "J185FAP", "J213AP", "J214KAP", "J215AP", "J223AP", "J230KAP", "J274AP", "J293AP", "J313AP", "J314cAP", "J314sAP", "J316cAP", "J316sAP", "J375cAP", "J375dAP", "J413AP", "J414cAP", "J414sAP", "J415AP", "J416cAP", "J416sAP", "J433AP", "J434AP", "J456AP", "J457AP", "J473AP", "J474sAP", "J475cAP", "J475dAP", "J493AP", "J504AP", "J514cAP", "J514mAP", "J514sAP", "J516cAP", "J516mAP", "J516sAP", "J613AP", "J615AP", "J680AP", "J780AP", "Mac-1E7E29AD0135F9BC", "Mac-63001698E7A34814", "Mac-937A206F2EE63C01", "Mac-AA95B1DDAB278B95", "VMA2MACOSAP", "VMM-x86_64"]
2024-08-14 10:29:17.604846+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] SOFA CVEs: [:]
2024-08-14 10:29:17.669460+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:softwareupdate-device] Error assessing DeviceID: remotectl: Unable to find device "localbridge".
2024-08-14 10:29:17.669638+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Assessed Model IDs: ["Unknown", "", "J514sAP", "J514sAP"]
2024-08-14 10:29:17.669657+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:sofa] Assessed Model ID found in SOFA Entry: true
2024-08-14 10:29:17.669979+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:17.669988+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:17.670000+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] Device outside nudgeMinorUpdateEventLaunchDelay
2024-08-14 10:29:17.670068+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:17.670077+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:17.670080+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:softwareupdate-download] enforceMinorUpdates: true
2024-08-14 10:29:17.670103+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:17.670112+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] OS Version: 14
2024-08-14 10:29:17.703315+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:29:17.709138+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:preferences-json] userInterface key is empty - json
2024-08-14 10:29:17.709156+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:preferences-json] updateElements key is empty - json
2024-08-14 10:29:17.715475+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] Device allow1HourDeferralButton: true
2024-08-14 10:29:17.715690+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] Device allow24HourDeferralButton: true
2024-08-14 10:29:17.715875+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] Device allowCustomDeferralButton: true
2024-08-14 10:29:17.740574+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] Device requireDualQuitButtons: false
2024-08-14 10:29:17.740826+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] nudgeRefreshCycle: 60
2024-08-14 10:29:17.750775+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Device pastRequiredInstallationDate: false
2024-08-14 10:29:17.750822+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Major required OS version: 14
2024-08-14 10:29:17.785891+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:user-interface] net.kovidgoyal.kitty is currently the frontmostApplication
2024-08-14 10:29:17.786276+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Activating Nudge
2024-08-14 10:29:17.818349+1000  localhost Nudge[53254]: [com.github.macadmins.Nudge:utilities] Activating Nudge

It's because you have minorVersionRecalculationThreshold but it's set to 1. Make it 99 and the issue will fix itself.

That's fixed it! Thanks for your quick help and all the awesome work you do for Nudge, @erikng 🙇


Fix status command for helm 3

fixes same as https://github.com/roboll/helmfile/issues/1050 , but for helmfile status command.

@rinrailin @mumoshu i think this should be reopened
https://sweetops.slack.com/archives/CE5NGCB9Q/p1582088381195000


Export connectors

Pull request
Description
export missing connectors
update rust
Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance

blocked on https://github.com/fede1024/rust-rdkafka/issues/681


Question: How do I import a urdf model?

I'm trying to use your plugin, but I can't seem to find any examples or any documentation for how to use the urdf import capability to import a urdf model into Unreal.
Any help would be appreciated.

Thanks for your question.
Currently we are not supporting spawning robot from URDF yet. we have a plan to support it and working on it.

Hi @yuokamoto , thank you all for the great work to build this plugin.
About the URDF importer, I saw you have implemented URDF parser in the codebase. Can we know what are the remaining work and an estimated timeline to have the importer work? Thanks ahead

Currently we are working on creating skeletal mesh from parsed URDF info.
Targeting to complete MVP in this year but not 100% confidence.
cc @Tadinu

@yuokamoto
Any progress on this feature?

Unfortunately not major progress since key contributer left this project...
I may make current very beginning prototype public later...


add fd_manager runtime module

Problem
We run out of file descriptors because things like TCP sockets consume them: #556
Solution
Introduce a new runtime module: fd_manager. It is pretty simple: it just tracks the number allowed fds. Runtime modules that consume fds must notify fd_manager when they open or close an fd. Then, if the total amount of fds passes some threshold, fd_manager sends out a Request to all runtime modules with open fds to Cull their old fds with a suggested fraction to cull. Runtime modules that consume fds must, therefore, also implement logic to respond to a Cull.
Testing
TODO
Docs Update
TODO
Notes
TODO list:

[x] Write fd_manager skeleton
[x] Write fd_manager helper send_fd_manager_open(number_opened: u64)
[x] Write fd_manager helper send_fd_manager_close(number_closed: u64)
[x] Update vfs to talk to fd_manager
[ ] Update sqlite to talk to fd_manager
[ ] Update kv to talk to fd_manager
[x] Update net to talk to fd_manager
[ ] Look for any other consumers of fds and update them to talk to fd_manager
[ ] Test

When booting a pre-existing indirect node with this binary I got a segfault. Not obvious to me where in the net code there is a hanging peer, but that's what this looks like to me:
Tue 09:51 net: connection lost with aficionad.os
Tue 09:51 net:distro:sys closed 1 of 20
diligence.os > m our@fd_manager:distro:sys "GetState"
Tue 09:52 process diligence.os@12665670855602396235:terminal:sys returned without error
Tue 09:52 process<PHONE_NUMBER>5602396235:terminal:sys has OnExit behavior None
Tue 09:52 kernel: killing process<PHONE_NUMBER>5602396235:terminal:sys
Tue 09:52 hq:uncentered.os: error: Internal sync failed: Failed to generate embeddings: Timeout
Tue 09:53 net: attempting to connect to aficionad.os directly
Tue 09:53 net: connected to aficionad.os directly
diligence.os > thread 'tokio-runtime-worker' panicked at kinode/src/net/connect.rs:11:30:
                                                                                net: peer sender was dropped: SendError { .. }
                                    note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
              Cleaning up "/home/nick/kinode-homes/diligence.os"...
Done cleaning up "/home/nick/kinode-homes/diligence.os".

Will look more into this this afternoon

Pretty sure I got it; confirming then fix coming here.

Fixed in aca7985. Unrelated fixes in a2fa276

By my count, the kernel / runtime itself uses about 20 file descriptors in the base case. I suggest that instead of configuring kernel, sqlite, kv, and terminal to use fd_manager, we simply add a fixed buffer that reserves the runtime FDs. Only vfs and net dynamically use a bunch of FDs / have the potential to overwhelm a limit at the moment.
Currently fd_manger uses a constant to give cushion from what the system gives:
const DEFAULT_FDS_AS_FRACTION_OF_ULIMIT_PERCENTAGE: u64 = 60;

I suggest that this gets bumped up to 90 and we tack on 30 as a fixed value that gets subtracted from whatever system ulimit we are given. If we are given less than 40 from system (which would give 9 as the final amount available to vfs/net.. not much to work with..) we crash with a descriptive error.

I suggest that instead of configuring kernel, sqlite, kv, and terminal to use fd_manager, we simply add a fixed buffer that reserves the runtime FDs. Only vfs and net dynamically use a bunch of FDs / have the potential to overwhelm a limit at the moment.

This doesn't necessarily have to be in 0.9.5 yet, but kv and sqlite FDs can definitely use a bunch of FDs (loop open 500 sqlite dbs will error), if users have many apps installed that use them, should be quite simple to cull them given most open actions are already OpenOrCreate.

kv and sqlite FDs can definitely use a bunch of FDs

Wait really? I thought that both of these used one "db" and parceled userspace requests into separate tables and such.. if a new file descriptor is acquired we should def track

I see now that multiple DBs get opened. I'll wire these up to fd_manager.

@bitful-pannul need to you check my work here on refactor to kv. sqlite coming next

Sqlite work added.


HDDS-4950. Provide example k8s files to run full HA Ozone

What changes were proposed in this pull request?
With the help of @bshashikant I tested how SCM-HA works in K8s environement. It worked well and here I publish the required k8s yaml files for any tests.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4950
How was this patch tested?
The easiest way to test is using k3s.
As the final definition is optimized for real, multi-node environment with persistence, testing is easier with transforming the files:
flekszible generate \
    -t mount:hostPath=/home/elek/projects/ozone/hadoop-ozone/dist/target/ozone-1.1.0-SNAPSHOT,path=/opt/hadoop \
    -t image:image=apache/ozone-runner:20200420-1 \
    -t ozone/onenode

Where the first host path is the location of your Ozone build.

Please hold on the merge util we finish merging master back to 2823. Thanks!

@elek , can you rebase and retrigger the tests now?

@elek , can you rebase and retrigger the tests now?

Sure, just rebased the branch and pushed...


Add docs about asset management

The auto importing topic is covered in one part of the docs, but it would be nice to have a dedicated section.   A bit of stuff:
// fuse config

dependencies.include = "path/to/resource/folder/"

Using a literal import
import ref from "./image.png"

document.body.innerHTML += `<img src="${ref}">`;

Should consider resource field too.

Hey.  I'm trying to use an image in fuse-box 4.0 and can't figure it out.
If I do:
import ref from "./image.png"

It gives "./abc123.png" when it should give "./resources/abc123.png".  Also, it renames it which I don't want it to do.
I've tried adding this to my cofig:
dependencies: {
    include: ['tslib', "./assets"],
  },

But it's not copying my assets folder over.
I can't figure out how to display an image right now.  :/

For now I'm just manually copy pasting into dist.

Add link configuration, There is a bug where it prioritizes it's local config over the global one

I still haven't figured out how to work around this problem in fuse-box.
It seems there should be some very, very simple way to copy files from one folder to another inside dist.
Right now I'm trying to use chokidar to achieve this because I can not figure out how to make it happen in fuse-box.

For this config:
https://github.com/fuse-box/fuse-box/blob/0c30c7b1131de2ba8b3289892c199d50539fcc5a/src/config/IDependencies.ts#L14-L19
What would it take to make the following config option possible:
interface IDependecyIncludeConfig {
  target: string;             // path or glob to files that should be included in dist
  distPath: string;         // path from dist root for where files should be copied
}

The result being something like so:
cosnt bundler = fusebox({
  // ... omitted
  dependencies: {
    include: [
      {
        target: "../assets/img/**/*",
        distPath: "./img"
      }
    ]
  }
});

I remember this type of stuff was really easy with sparky, but I don't think Sparky is around anymore (Is it?).  So maybe this kind of behavior could become part of standard fuse-box.

The following code does not work:
class Context {
  isProduction;
  runServer;
}
const { task, src } = sparky<Context>(Context);

// src("./assets/**/*")
//   .dest("./dist", "")
//   .exec();

task("default", async () => {
  await src("./assets/**/**.**")
    .dest("./dist/", ".")
    .exec();
});

I can't find a single usage of sparky().src() anywhere in the entire codebase:  https://github.com/fuse-box/fuse-box/search?p=5&q=sparky+src(

Found the issue:
https://github.com/fuse-box/fuse-box/blob/fe10bf4693cef1a9d0c5faaec1b63b8578bf2a57/src/sparky/sparky_chain.ts#L46-L53
For some reason all files that have a newLocation and newBase (which is true whenever sparky().dest()) are put into folders of their filetype.
It seems like maybe some logic that belongs in the resources use case got put into sparky proper.
In any case, it no longer appears to be possible to use sparky to simply copy files from one place to another.


Updated blast config labels

Type

[ ] Bug fix
[ ] New feature
[x] Improvement to existing feature

Related JIRA Issue(s)
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1487
Description
Updated blast labels after review by AndreaW
Deployment URL
http://updated-blast-labels.review.ensembl.org/
Views affected
Blast
Other effects
NA

[ ] I have checked any requirements for Google Analytics
[ ] I have created any required tests
[ ] The PR has as its final commit a WASM/JS update commit if any Rust files were updated.

@jyothishnt the review URL isn't working for me. Its giving this error:
default backend - 404
can you check if it works for you.

Labels correspond to the ticket. The label "statistical accuracy" instead of "composition-based statistics" or "composition-based adjustments" makes no sense to me (I've checked the articles referenced in the docs), but there is nothing I can do about it. I wish someone like @andrewyatz could review these labels 😞

I noticed that there is a description field in the json, maybe we can used this with a help icon next to each field. Its just a suggestion, lets see what comes out of the user testing.

Probably not related to this PR but i have noticed that HSPs has only one value (100), is that correct? looking at uniprot, the HSPs dropdown has a few options. sorry if it has already been discussed but it feels wrong to have a dropdown with just one value.

Probably not related to this PR but i have noticed that HSPs has only one value (100), is that correct

This is the only (default) value provided by the jDispatcher

sorry if it has already been discussed but it feels wrong to have a dropdown with just one value

Yes, it is wrong. We'll need to come up with our own list of values; jDispatcher won't give it to us. A similar situation is with the word size, where we are getting three suggested defaults from jDispatcher, but should extend the list with our own values.

I noticed that there is a description field in the json, maybe we can used this with a help icon next to each field.

Yes. But Andrea didn't want question marks next to each field.

sorry if it has already been discussed but it feels wrong to have a dropdown with just one value

Yes, it is wrong. We'll need to come up with our own list of values; jDispatcher won't give it to us. A similar situation is with the word size, where we are getting three suggested defaults from jDispatcher, but should extend the list with our own values.

Indeed just noticed there is a jira for this task in the next sprint:
https://www.ebi.ac.uk/panda/jira/browse/ENSWBSITES-1498

@jyothishnt the review URL isn't working for me. Its giving this error:
default backend - 404
can you check if it works for you.

The link to the deployment is wrong. Should be update-blast-labels, not updated. Same as the name of the branch.


Testing Workspace

This is an issue for managing the conversation around the testing workspace use case, providing a place to discuss and document the evolution of the workspace.

Should we have other types of testing? End to End? Integration?

I have updated this to use the new space-themed APIs, rebranding to be about PM Corp enterprise APIs.


Why do we need to enable implicit flow for the app?

Note: This repo is only for questions related to its samples. If you have questions about how to use office.js or the Office developer platform, please post your question on https://stackoverflow.com. Tag your question with office-js or outlook-web-addins

Question
The instructions for app registration are suggesting that we create an implicit grant flow (Point 6).

But the code does not seem to rely anywhere on implicit flow

There are suggestions that implicit grant flow is no longer suitable.

Can you please help us understand if the implicit flow is mandatory or recommended for addins?

@kapilash Thanks for your question.
@davidchesnut Can you take a look?
Thanks.

Thanks @kapilash! I'll look into this sample.

FWIW, the code comment "Gets IdToken from implicit flow and sends it to main add-in window." does not accurately describe the method it is on. That method is using the AuthCode flow.

Thanks @Rick-Kirkham, I'm adding a link here to the code comment so I don't forget to update it: https://github.com/OfficeDev/Office-Add-in-samples/blob/39a7105582287bc82ffde7844167d53381a1867b/Samples/auth/Outlook-Add-in-SSO/AttachmentDemoWeb/Controllers/AzureADAuthController.cs#L46

thanks @davidchesnut!


Remove react as a dependency

Having react as a dependency can cause multiple versions of react to be installed. Instead, it should just be a peerDependency.
This is what cloudflare-ui does: https://github.com/cloudflare/cf-ui/blob/master/packages/cf-builder-table/package.json#L20
Update this code:
https://github.com/cerner/generator-terra-module/blob/master/generators/app/templates/package.json#L33

This change was made here in https://github.com/cerner/generator-terra-module/pull/40


[Snyk] Security upgrade org.apache.camel.springboot:camel-spring-boot-starter from 3.20.6 to 4.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `maven` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

src/app-edge/pom.xml

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

589/1000  Why? Has a fix available, CVSS 7.5
Denial of Service (DoS) SNYK-JAVA-ORGYAML-2806360
org.apache.camel.springboot:camel-spring-boot-starter:  3.20.6 -> 4.0.0
Yes
No Known Exploit

506/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 3.7
Stack-based Buffer Overflow SNYK-JAVA-ORGYAML-3016888
org.apache.camel.springboot:camel-spring-boot-starter:  3.20.6 -> 4.0.0
Yes
Proof of Concept

399/1000  Why? Has a fix available, CVSS 3.7
Stack-based Buffer Overflow SNYK-JAVA-ORGYAML-3016889
org.apache.camel.springboot:camel-spring-boot-starter:  3.20.6 -> 4.0.0
Yes
No Known Exploit

536/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 4.3
Stack-based Buffer Overflow SNYK-JAVA-ORGYAML-3016891
org.apache.camel.springboot:camel-spring-boot-starter:  3.20.6 -> 4.0.0
Yes
Proof of Concept

399/1000  Why? Has a fix available, CVSS 3.7
Stack-based Buffer Overflow SNYK-JAVA-ORGYAML-3113851
org.apache.camel.springboot:camel-spring-boot-starter:  3.20.6 -> 4.0.0
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Rejected because major version changed


re-send tracks permissions after reconnected.

According to @lukasIO , I think we need to send it for normal connect also ? (set permission before connection)

Responding since Lukas is on vacation this week. He's saying that the client could buffer up permission updates, which makes it easier for clients to use. Right now the clients have to wait until the connection is complete before setting permission


Remove duplicate data loading in rl_training.py

We load dataset twice, but in line 149 (new), we do  ds = train_dataset.map anyway

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


trained Weight not applied to Sample process of ScreenerNet ?

In the example of ScreenerNet, the resample process of train process seemed should apply with
trained weight of sample, But it seemed like the train loader simply retrieve trained samples in  ordinarily
pytorch dataloader manner in the file sent.py in ScreenerNet dir ?
So the only effect of ScreenerNet is the grads update of Main NetWork ?
And I have not see the PrioritizedExperience Replay(PER) Process in the code (adjust the weight for sampling)
I am Confused with this, it may related with my misunderstanding, Please give me an explaination.
@TobeyQin

Hi, there,
I'm also interested in ScreenerNet, maybe we can discuss it together. Actually, I've tried to use ResNet to replace the basenet here, and the results are not satisfying, it seems that screenernet does not give a  better convergence or much slower than the baseline.


🛠 FIX : Fuzz Testing in PRBMath.t.sol

🛠 [FIX]
Description:
PRBMath functions are not fuzz tested.
Objective:
Write fuzz tests for functions implemented in src/ComplexHuff/PRBMath.huff

@0xpanicError can I work on this issue?

Yes ofc. There is another PR working on fuzz testing so ensure the functions you work on don't overlap with that.
https://github.com/BlocSoc-iitr/HorseRiders/pull/30


comments included

instead of functions for text widgets can you use ternary operators

instead of functions for text widgets can you use ternary operators

okayy


service-catalog does not pass the operation to last_operation

The OpenServiceBroker spec specifically states Query-string field vs Request Field:
Parameters
The request provides these query string parameters as useful hints for brokers.

Query-String Field
Type
Description

service_id
string
ID of the service from the catalog.

plan_id
string
ID of the plan from the catalog.

operation
string
A broker-provided identifier for the operation. When a value for operation is included with asynchronous responses for Provision, Update, and Deprovision requests, the broker client should provide the same value using this query parameter as a URL-encoded string.

But if you look at the url string the operation is not appended to the url:
pollingFormatString                    = "%s/v2/service_instances/%s/last_operation"
We send in the operation in the request body for a GET call. But never append it to the url as a query parameter.
func (c *openServiceBrokerClient) pollBroker(ID string, operation string) error {
	pollReq := brokerapi.LastOperationRequest{}
	if operation != "" {
		pollReq.Operation = operation
	}

	pollingURL := fmt.Sprintf(pollingFormatString, c.url, ID)
	for i := 0; i < pollingAmountLimit; i++ {
		glog.V(3).Infof("Polling broker %v at %s attempt %v", c.name, pollingURL, i+1)
		pollResp, err := sendOSBRequest(c, http.MethodGet, pollingURL, pollReq)

Lines 302-311

It's interesting the example doesn't show the query parameters at all. service_id and plan_id are explicitly mentioned as optional, but operation is not.
I can read that section as "if the broker provides it in a response, the client should echo it back on the next request".  None of that sounds required to me.
I'd say this is more of a bug in the spec definition than our implementation until the spec is clarified.

@vaikas-google can you handle this in #717 ?

@MHBauer that's part of the problem. It is being returned by the broker but the catalog is not echoing it back as a query parameter.

Actually properly addressed by a follow up in #757