feat: implement ErrorSnapshotter for error context capture

This commit introduces the ErrorSnapshotter class to the crawlee package, providing functionality to capture screenshots and HTML snapshots when an error occurs during web crawling.
Closes #2280

Hey @B4nan,
I have completed the pull request that resolves the issue with saving Save screenshot/HTML on first occurrence of error in error statistics.
However, I encountered a few problems during the testing phase. I was only able to test the functionality using the debugger and a temporary test file created with Cheerio and the browser and it seems to be working fine.
Normal tests ran fine, but seems there are errors but I don't believe they are related to my changes.
Unfortunately, I was unable to run the e2e tests or build it due to some errors in the terminal, and I wasn't able to figure out what caused them.
I'm using node v18.17.1 and yarn v4.0.2
yarn test Error:
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > browser should launch with rotated custom proxy
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > browser should launch with rotated custom proxy
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > browser should launch with rotated custom proxy
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > browser should launch with rotated custom proxy
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation on error respects maxSessionRotations, calls failedRequestHandler
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation on error respects maxSessionRotations, calls failedRequestHandler
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation on error respects maxSessionRotations, calls failedRequestHandler
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation on error respects maxSessionRotations, calls failedRequestHandler
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation logs the original proxy error
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation logs the original proxy error
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation logs the original proxy error
 FAIL  test/core/crawlers/browser_crawler.test.ts > BrowserCrawler > proxy > proxy rotation logs the original proxy error
TargetCloseError: Protocol error (Runtime.callFunctionOn): Session closed. Most likely the page has been closed.
 ❯ CdpCDPSession.send node_modules/puppeteer-core/src/cdp/CDPSession.ts:106:6
 ❯ ExecutionContext.#evaluate node_modules/puppeteer-core/src/cdp/ExecutionContext.ts:292:6
 ❯ ExecutionContext.evaluate node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:124:36
    125|      * @example
    126|      *
    127|      * ```ts
       |      ^
    128|      * const context = await page.mainFrame().executionContext();
    129|      * const handle: JSHandle<typeof globalThis> = await context.evaluateHandle(
 ❯ IsolatedWorld.evaluate node_modules/puppeteer-core/src/cdp/IsolatedWorld.ts:153:14
 ❯ CdpFrame.evaluate node_modules/puppeteer-core/src/api/Frame.ts:513:30
 ❯ CdpFrame.<anonymous> node_modules/puppeteer-core/src/util/decorators.ts:64:2
 ❯ CdpFrame.content node_modules/puppeteer-core/src/api/Frame.ts:788:10
 ❯ CdpFrame.<anonymous> node_modules/puppeteer-core/src/util/decorators.ts:64:2
 ❯ CdpPage.content node_modules/puppeteer-core/lib/esm/puppeteer/api/Page.js:516:43
 ❯ ErrorSnapshotter.captureSnapshot packages/utils/src/internals/error_snapshotter.ts:38:38

yarn build Error:
@crawlee/utils#build: command (/Users/hamza/Desktop/apify/crawlee/packages/utils) /private/var/folders/4z/qgr81fxx5695006fwrzq6k7r0000gn/T/xfs-504fbf48/yarn run build exited (2)

 Tasks:    3 successful, 5 total
Cached:    3 cached, 5 total
  Time:    3.881s
Failed:    @crawlee/utils#build

 ERROR  run failed: command  exited (2)

yarn test:e2e Error:
node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/hamza/Desktop/apify/crawlee/packages/utils/dist/index.mjs' imported from /Users/hamza/Desktop/apify/crawlee/test/e2e/tools.mjs
    at new NodeError (node:internal/errors:405:5)
    at finalizeResolution (node:internal/modules/esm/resolve:324:11)
    at moduleResolve (node:internal/modules/esm/resolve:943:10)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40)
    at link (node:internal/modules/esm/module_job:76:36) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v18.17.1

Can you send the full build log you have from the build command? There should be more information 👀

@vladfrangu

Can you send the full build log you have from the build command? There should be more information 👀

Full build log:
yarn build
╭───────────────────────────────────────────────────────────────────────╮
│                                                                       │
│                  Update available v1.11.3 ≫ v1.12.3                   │
│    Changelog: https://github.com/vercel/turbo/releases/tag/v1.12.3    │
│           Run "npx @turbo/codemod@latest update" to update            │
│                                                                       │
│        Follow @turborepo for updates: https://x.com/turborepo         │
╰───────────────────────────────────────────────────────────────────────╯
• Packages in scope: @crawlee/basic, @crawlee/browser, @crawlee/browser-pool, @crawlee/cheerio, @crawlee/cli, @crawlee/core, @crawlee/http, @crawlee/jsdom, @crawlee/linkedom, @crawlee/memory-storage, @crawlee/playwright, @crawlee/puppeteer, @crawlee/templates, @crawlee/types, @crawlee/utils, crawlee
• Running build in 16 packages
• Remote caching disabled
@crawlee/types:build: cache hit (outputs already on disk), replaying logs d5696cf6c1be5593
@crawlee/templates:build: cache hit (outputs already on disk), replaying logs 5de49aba4a4af3e3
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Validating 8 templates
@crawlee/templates:build: Validating template getting-started-ts
@crawlee/templates:build: Finished validating getting-started-ts
@crawlee/templates:build: Validating template getting-started-js
@crawlee/templates:build: Finished validating getting-started-js
@crawlee/templates:build: Validating template cheerio-ts
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Debugger attached.
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/types:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Finished validating cheerio-ts
@crawlee/templates:build: Validating template playwright-ts
@crawlee/templates:build: Finished validating playwright-ts
@crawlee/templates:build: Validating template puppeteer-ts
@crawlee/templates:build: Finished validating puppeteer-ts
@crawlee/templates:build: Validating template cheerio-js
@crawlee/templates:build: Finished validating cheerio-js
@crawlee/templates:build: Validating template playwright-js
@crawlee/templates:build: Finished validating playwright-js
@crawlee/templates:build: Validating template puppeteer-js
@crawlee/templates:build: Finished validating puppeteer-js
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Debugger attached.
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/templates:build: Waiting for the debugger to disconnect...
@crawlee/utils:build: cache miss, executing 4ba9529396006646
@crawlee/cli:build: cache hit (outputs already on disk), replaying logs 05dc6b290eb9c6bb
@crawlee/memory-storage:build: cache miss, executing a3934740eaa87094
@crawlee/utils:build: error TS2209: The project root is ambiguous, but is required to resolve export map entry '.' in file '/Users/hamza/Desktop/apify/crawlee/packages/utils/package.json'. Supply the `rootDir` compiler option to disambiguate.
@crawlee/utils:build:
@crawlee/utils:build:
@crawlee/utils:build: Found 1 error.
@crawlee/utils:build:
@crawlee/utils:build: ERROR: command finished with error: command (/Users/hamza/Desktop/apify/crawlee/packages/utils) /private/var/folders/4z/qgr81fxx5695006fwrzq6k7r0000gn/T/xfs-fada239d/yarn run build exited (2)
@crawlee/utils#build: command (/Users/hamza/Desktop/apify/crawlee/packages/utils) /private/var/folders/4z/qgr81fxx5695006fwrzq6k7r0000gn/T/xfs-fada239d/yarn run build exited (2)

 Tasks:    4 successful, 5 total
Cached:    3 cached, 5 total
  Time:    5.055s
Failed:    @crawlee/utils#build

 ERROR  run failed: command  exited (2)

Just checked CI logs too, and yeah.. probably updating imports with what I sent might fix it

Just checked CI logs too, and yeah.. probably updating imports with what I sent might fix it

Yes, it's fixed now.

A couple of things:
1- I need to handle saving the local file path to the screenshot and HTML, currently, I only save the Apify path which will not work locally.
2- Please verify the naming or the path of the screenshot and HTML properties, and the method that generates the file names.
3- Not sure if the way I handled saving the error is the correct way, as we have errorTracker and errorTrackerRetry.
4- Regarding this:

Some errors happen before any page is created or opened, before navigation happens, or after the page is already closed (maybe then a response object is still available to store HTML?)

It's not possible to save the HTML or take a screenshot if an error happens before navigation, and I have not yet looked at the case for post-navigation

Please add some tests for the new functionality.
Also, note that what you did (making the add method async) is in fact breaking change, but I guess we can afford to do that here as the class is rather internal (but it's not marked as such and is publically documented). Maybe it would be better to add another method, e.g. addAsync.

@metalwarrior665 ,
Here is an example, clicking on the (path + cmd) opens the file:
"retryErrors": {
    "file:///Users/hamza/Desktop/playwright-test/main.js:18:19": {
      "missing error code": {
        "Error": {
          "This is an error": {
            "count": 3,
            "firstErrorScreenshot": "file:///Users/hamza/Desktop/playwright-test/storage/key_value_stores/default/SNAPSHOT_de2cd33186d663537f2b441be5c372_This-is-an-error.jpeg",
            "firstErrorHtml": "file:///Users/hamza/Desktop/playwright-test/storage/key_value_stores/default/SNAPSHOT_de2cd33186d663537f2b441be5c372_This-is-an-error.html"
          }
        }
      }
    }
  }

@HamzaAlwan When adding tests, let's add a few real-world errors so we can properly trim very long error messages. I wonder if the 30 chars error length could be longer but let's see how the real world errors will look like. Thanks.

Everything is done, please look it over and provide any feedback.
What is left is this:

We should be able to capture snapshots of e.g. pages that navigated but then were rejected as blocked by status code. Those should already have a body and perhaps the page object

This code works for browsers because we can access the page in the context. However, it throws an error without returning the response ref1 and ref2. I'm unsure if we want to change the code's behavior, as doing so could cause further issues, and it may also be another breaking change.

@B4nan @vladfrangu @barjin  Hey guys, let's get this merged pls. It is really useful for us and we believe for the community as well. We are ready to refactor it if needed. Thanks

@HamzaAlwan Please look at @B4nan 's remarks. Let's prioritize this so we can finish it finally. cc @AndreyBykov

Great that you addressed the comments just now @HamzaAlwan, we want to ship v3.10 in the afternoon most probably, so let's try to squeeze this in. Don't forget to rebase and resolve the conflicts.

@HamzaAlwan please try to work on this asap if you want to see this in v3.10.0

I might be late to the party, but why ErrorSnapshotter and not ErrorScreenshotter or something? "Snapshot" is pretty ambiguous.

it does not store just screenshots, but also html snapshots, right?

We use the term snapshot as "store representation of the page" like screenshot, HTML (potentially HAR , JS etc. if we would want that). I agree the term is confusing but we didn't find better one. We already have https://crawlee.dev/api/3.7/playwright-crawler/namespace/playwrightUtils#saveSnapshot


Tests: Reduce number of threads spawned if -PtestForks is used

Should help reducing context-switching and system overload, making the
tests overall a bit faster.

Not really - due to the randomization in the test-suite the run duration varies a lot anyway. I've had the impression that it overall helps a bit, but I don't have numbers to proof it.
Happy to revert it in case we've reason to believe it slows things down.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4673

Questions ?
Please refer to the Backport tool documentation


Pytestifying

Work in progress in replacing nose with pytest. (On top of some previous unmerged PR.)
Putting this up early in case there is some comment.
Todo

[x] Add basic test() function in top-level scipy package.
[x] Fix up things in runtest.py.
[x] Convert tests dir to subpackages and fix imports.
[x] Fix up minor things so that test collection passes and it runs.
[x] dec.knownfailureif
[x] dec.skipif
[x] dec.slow (custom marker)
[x] SCIPY_XSLOW (custom marker)
[x] Fix sparse:test_base.py:_TestCommon (a bit ugly; but the yield tests that necessitate this would be on way out anyway)
[x] Replace test() in all subpackages.
[x] Make travis pass
[x] Make circleci pass

Fixing up all the yield tests, which is a bit of more work, can be done later.
We can stick with Pytest 3.x for that.

Now that the first two test janitoring PRs have been merged, could you rebase?

Everything seems to pass on Travis now.
The big remaining thing would be conversion of all yield tests to pytest.mark.parametrize, plain for loops (pytest can print local variables), or some other approach --- the refactoring in some cases may need some thought on how to do it. This in principle can be done later piecewise, as they're still supported in current pytest. (Although, if you forget to say --disable-warnings or pipe the output to uniq, pytest will print the "yield tests are deprecated" message 15652 times to make sure you got it :)
There are also some more minor cleanups that could be done.

The big remaining thing would be conversion of all yield tests to pytest.mark.parametrize, plain for loops (pytest can print local variables), or some other approach --- the refactoring in some cases may need some thought on how to do it.

I'd be happy to see the yield-based tests go in some cases. For example the ARPACK or 64-bit sparse tests; when something is wrong you often get 20-100 test errors instead of one or two, which gives the impression that something is horribly broken (bad for users) or you just have to scroll forever in a terminal (bad for devs).
So if a for-loop approach can be made to work, that sounds good to me.

Note that I was thinking of leaving fixing the yield tests to be done
later in separate PRs. They are still supported in pytest, and
refactoring them is a bit more complicated as it's not just a
search-and-replace operation.

Note that I was thinking of leaving fixing the yield tests to be done later in separate PRs.

So this is good to merge as is (after a rebase)? Still has WIP in the PR title

Yes, I think this is no longer WIP, as I think I won't be adding more
stuff here.

Looks like  pytest.ini needs to be added to MANIFEST.in.
This looks good from a browse. Would like to test in a bit of detail

Question: with the removal of run_module_suite, is there still a way to run one file?

The same way you would do it with nose:
.
python -c "scipy.test(tests=['scipy.fftpack.tests.test_basic'])"
python runtests.py -t scipy/fftpack/tests/test_basic.py
cd scipy/fftpack/tests; python -mpytest test_something.py  (not sure if
making the tests packages breaks this)
.
We may also want to add --disable-warnings to pytest.ini to avoid
getting the tens of thousands of "yield tests are deprecated" messages.

Hmm, first test drive:
$ python -c "import scipy as s; s.test()"
========================================= test session starts ==========================================
platform linux2 -- Python 2.7.6, pytest-2.8.2, py-1.4.30, pluggy-0.3.1
rootdir: /home/rgommers/Code/tmp, inifile:
plugins: xdist-1.13.1, timeout-0.5, capturelog-0.7
collected 23164 items / 3 errors
 .....................EEEEEEEEEEx..EEE
 <etc>
INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/home/rgommers/.local/lib/python2.7/site-packages/_pytest/main.py", line 90, in wrap_session
INTERNALERROR>     session.exitstatus = doit(config, session) or 0
INTERNALERROR>   File "/home/rgommers/.local/lib/python2.7/site-packages/_pytest/main.py", line 121, in _main
INTERNALERROR>     config.hook.pytest_runtestloop(session=session)
INTERNALERROR>   File "/home/rgommers/.local/lib/python2.7/site-packages/_pytest/vendored_packages/pluggy.py", line 724, in __call__
<etc>
=============================== 460 tests deselected by "-m 'not slow'" ================================
 1 failed, 17263 passed, 1798 skipped, 460 deselected, 74 xfailed, 1 xpassed, 3 pytest-warnings, 1863 error in 448.68 seconds

After upgrading to latest pytest (3.1.3) it looks much better. Guess needs a check for minimum supported version somewhere.

  Please remove the prefix and use the @pytest.fixture decorator instead.
  pytest_funcarg__capturelog: declaring fixtures using "pytest_funcarg__" prefix is deprecated and scheduled to be removed in pytest 4.0.  Please remove the prefix and use the @pytest.fixture decorator instead.

/home/rgommers/Code/scipy/scipy/_lib/tests/test_ccallback.py
  yield tests are deprecated, and scheduled to be removed in pytest 4.0
  <infinite amounts of warnings to follow>

Question: with the removal of run_module_suite, is there still a way to run one file?

Fixing run_module_suite was the easy part in numpy. Fixing runtests and friends, as here, looks more difficult (to me.  I'll probably steal some of this ...

@charris: how did you fix run_module_suite? Transforming test/ to
packages + adding conftest.py seems to throw cranks in the gears?

@rgommers: looks a bit like another warning suppression
indeterminancy... not sure if the test order is fully deterministic.
Maybe this is fixed by gh-7583 (needs to be merged before this).
.
The semi-infinite "yield tests are deprecated" spam will hopefully be
fixed in the next pytest version.

@pv Like so. The plugin isn't needed, I've just been fooling around with them to see how they work.
    import pytest
    from .noseclasses import NpyPlugin

    if file_to_run is None:
        f = sys._getframe(1)
        file_to_run = f.f_locals.get('__file__', None)
        if file_to_run is None:
            raise AssertionError

    if argv is None:
        argv = sys.argv[1:] + [file_to_run]
    else:
        argv = argv + [file_to_run]

    pytest.main(argv, plugins=[NpyPlugin()])

That fails because of conftest.py and init.py under tests/.
Either of those is enough to make it not to work, although the former
can be avoided by --noconftests, but that makes tests behave in a
different way which not desirable.

Works fine for me on NumPy, I've been using it for several days. There must be something different about SciPy.
charris@fc [numpy.git (add-pytest-support)]$ NPY_PYTEST=1 python numpy/core/tests/test_umath_complex.py --disable-pytest-warnings -q
...................s.........................................s...............
75 passed, 2 skipped, 67 warnings in 0.06 seconds

The difference is having a conftest.py, and init.py in test directories.

The conftest.py files could probably be gotten rid of by using a class plugin instead. The __init__.py are something else, what problem do they cause ?

I would not want to go with custom test runners and plugins, to keep
things simple and to retain similarity between pytest --pyargs scipy
and scipy.test.
.
I think dropping run_module_suite and sticking close to the pytest
recommended setup is a simpler alternative.

I think dropping run_module_suite and sticking close to the pytest recommended setup is a simpler alternative.

Sounds OK to me

OSX10.12.5
platform darwin -- Python 3.6.1, pytest-3.1.2, py-1.4.34, pluggy-0.4.0
Getting weird errors thinking I'm on Linux for some reason.

        Returns a dict of items in /proc/meminfo
        """
        info = {}
>       with open('/proc/meminfo', 'r') as f:
E       FileNotFoundError: [Errno 2] No such file or directory: '/proc/meminfo'

info       = {}

scipy/sparse/tests/test_sparsetools.py:323: FileNotFoundError

Further information, the errors I reported are seen using import scipy;scipy.test() as well. None of the test suite runs because those errors are seen during test collection.

@andyfaff: thanks, those tests were supposed to skipped on non-linux. Should be fixed now (another yield test + mark issue).

The tests run this time. There is still a test failure, #7590, log at this gist. Is there anyway we can get a CI working on a true OSX install?

The tests run this time. There is still a test failure, #7590, log at this gist. Reinforces the need to OSX CI

That test failure is already present in master, not introduced by this PR. So nothing stopping this PR from getting merged I think.

Okay went through this again, LGTM. Needs another rebase, when it's green it can be merged I think.

Finally, is there a way to get ccache enabled also on the osx side for clang.
If it's enabled, it will greatly speed up the build due to the various c++ modules...

Rebased.

Merged, thanks a lot @pv !

@rgommers @v You can do
charris@fc [scipy.git (master)]$ pytest --pyarg scipy/stats/tests/test_multivariate
================================= test session starts ==================================
platform linux2 -- Python 2.7.13, pytest-3.1.2, py-1.4.34, pluggy-0.4.0
rootdir: /home/charris/Workspace/scipy.git, inifile: pytest.ini
collected 69 items

. .....................................................................

============================== 69 passed in 0.74 seconds ===============================

I suspect that can be made into a run_module_suite pytest fixup.

@charris: note that it seems to run the installed version of the file, not the file under $PWD/scipy/stats/tests/test_multivariate which may be confusing --- it seems to be the same as pytest --pyargs scipy.stats.tests.test_multivariate.

Ah, indeed, that seems to be the case. I was looking for a substitute for nose.runmodule, but apparently this isn't it.


[TextServer] Silently skip invalid system fallback fonts.

See https://github.com/godotengine/godot/issues/96101

Probably also fixes https://github.com/godotengine/godot/issues/97536

Thanks!


Add an identity check to resource unregistration from cache

This is needed because resources loaded with CACHE_MODE_IGNORE still have path_cache set. (See #88664, this is a fixup of.)
CC @KoBeWi because we had discussed about the implications of always having a cache path set.
Fixes #91811.

Thanks!


Make the (lint-fmt) phase depend on the minimal commit to avoid issues when projects fail because they require a newer dune version

Issue encountered in https://ci.ocamllabs.io/github/ocaml/merlin/commit/122369c769636890ca6b094f4d0595d2522b546b/variant/(lint-fmt)

Thanks!


Investigate impacts of popo in language context system

Description
Flagged instances of definition dictionary logic that appears in the language context system
Linked Items:
Closes #712
Added
Flags on calls to definition logic
Checklist:

[ ] I updated project documentation to reflect my changes.
[ ] My changes generate no new warnings.
[ ] I updated new and existing unit tests to account for my changes.
[ ] I linked the associated item(s) to be closed.
[ ] I bumped the version.
[ ] I added the labels corresponding to my changes.

Make sure to bump the version in the root __init__.py of src/aac since this is merging to main.

Need to check your pipeline results, have a handful of flake8 gripes about the style of comment. The linter prefers a single # at the start of comments and no trailing for in lines like we've implemented.

Make sure to bump the version in the root __init__.py of src/aac since this is merging to main.

Team decided to not bump versions for the comment flagging tasks.


Geopoint prompt type ignoring required column

Marking the required column of the xlsx file to true does not prevent empty responses for geopoint question types.

This issue actually affects all complex data type prompts (Barcodes, Multimedia, etc), not just Geopoints

Fixed in:
opendatakit/app-designer@8259e63


Possible Bug with createSWRInfiniteProxy

When using two separate instances of createSWRInfiniteProxy in a single view without specifying a custom key in the request configuration, there seems to be an issue with key assignment. Both instances appear to share the same key internally, leading to cache-related problems.
E.g:
const { data: medicationsData, size: medicationsSize, isLoading: isLoadingMedications, setSize: setMedicationsSize } = infinite.medications.find.use(
  (index) => ({ page: index }),
  { revalidateOnFocus: false },
);

const { data: usersData, size: usersSize, isLoading: isLoadingUsers, setSize: setUsersSize } = infinite.users.find.use(
  (index) => ({ page: index }),
  { revalidateOnFocus: false },
);

The userData is the same as medicationsData
Client
import { httpBatchLink } from '@trpc/client';
import { createSWRProxyHooks } from '@trpc-swr/client';
import { createSWRInfiniteProxy } from '@trpc-swr/infinite';
import type { AppRouter } from '.........';

import { client } from '@utils/auth';

// Initialize TRPC client
export const trpc = createSWRProxyHooks<AppRouter>({
  links: [
    httpBatchLink({
      url:
        import.meta.env.VITE_GATEWAY_BASE_URL || 'http://localhost:8001/trpc',
      maxURLLength: 500,
    }),
  ],
});

// Initialize SWR infinite
export const infinite = createSWRInfiniteProxy(trpc);

When print swr cache the result is:
{key: undefined}

Code to print:
<button
          onClick={() => {
            void mutate(
              (key) => {
                console.log({ key });
                return Array.isArray(key) && key[0].startsWith('medications.');
              },
              undefined,
              { revalidate: true },
            );
          }}
        >
          toggle
        </button>

another print where the cache is saved well but without using inifinite
{key: ["medications.doses.dates"]}
{key: ["events.dates"]}
{key: ["physicians.filters"]}
{key: ["topics.find"]}
{key: ["learn.find", {page: 0}]}

Packages versions
 "@trpc-swr/client": "^2.0.1",
    "@trpc-swr/infinite": "^2.0.1",
    "@trpc/client": "^10.44.1",
    "@trpc/server": "^10.44.1",

Thank you very much for your help

Looking into this now

@sannajammeh Do you have any updates on this?

@sannajammeh any news on this? thanks


[SP-6154] [PDI-19502] Database Lookup step throws an exception when t…

…able date field is null

:white_check_mark: Build finished in 17m 27s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:exclamation: No tests found!
:information_source:  This is an automatic message


Change Request: Sub-client naming (get vs. create) in light of Event Hubs

At the JS guideline review last week, we re-committed ourselves to a get prefix for methods which vend sub-clients, e.g. getBlockBlobClient() lives on ContainerClient. The rationale, as I understand it, is that create is confusing and users might think they're creating a remote resource of some kind.
Event Hubs, in at least JS and Java, presently use create for things like createConsumer() and createProducer() which are not creating entities on the remote service per se, but @ramya-rao-a pointed out that these actually do create entities at the protocol level that users may have to pay for on an individual basis (or at least watch their caps).
I want to confirm if we would prefer getConsumer() vs. createConsumer() for EventHubs. Presumably all languages would want to change at the same time?
/cc @johanste @KrzysztofCwalina @JonathanGiles

This has been in the back of my mind recently too. To me, I feel that the Event Hubs consumer / producer are different than clients, and I therefore assuaged myself of concerns around lack of consistency. I am ok with 'create' here.

Pick your poison; get implies to me that you get the same instance back and create can imply that a resource is created. I personally believe that the existence of both create_<child> and create_<child>_client on the parent client should clear up any confusion.

@johanste agree that get vs. create from first principles isn't super clear, but we decided on get for empirical reasons so I feel a bit bad ultimately making the call with "handwaving".
I think I agree with your last point, but given that the create operation may not make sense every time we have a sub-client for something (EventHubs being a notable example, I suppose), your solution doesn't generalize so I'm a bit reluctant.

BOARD DISCUSSION:

There are actually three options: get_NOUN, create_NOUN, NOUN.
NOUN is not idiomatic in .NET.  .NET would want to reserve create for service operation.
NOUN "feels right" in JS (Cosmos); Java feels it is also a good thing
Python uses NOUN for non-validating, get_NOUN for validating
We should be careful about removing the verb to avoid readability issues
For JS/Java/Python, it is a stylistic opinion - can be different on different clients

BOARD DECISION:

MUST NOT use create_ unless it creates a resource on the service
Language guidelines should add no prefix vs. get so client libraries are consistent within the language.


Add dataset metadata to IDataset

Description
For the entire test set (in large dataset scenario), we need the feature ranges and number of rows while creating cohort filters.
Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #2071 (3f099f6) into main (e398f5a) will increase coverage by 2.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2071      +/-   ##
==========================================
+ Coverage   92.35%   94.41%   +2.05%
==========================================
  Files         100       18      -82
  Lines        4973      412    -4561
==========================================
- Hits         4593      389    -4204
+ Misses        380       23     -357

Flag
Coverage Δ

unittests
94.41% <ø> (+2.05%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 82 files with indirect coverage changes


Backend: Sliding histogram of incoming tweets

Story
We want to see the frequency of tweets by language over time. To do so we have to prepare a proper table.
Steps

Create and document  a new Accumulo table called: "TweetFrequency"

row key as String of format --> YYYYMMDDhhmm
family --> the language tag of the tweet (see JSON tag "lang")
qualifier --> [empty]
value --> number of tweets of this language

Extend the stream ingest after the "DateExtraction" using the flink window functionioanlity to create one minute buckets which count the number of tweets per language.
Write the results of the window function to the created accumulo table.

@merando: you want me to write number of tweets of this language per window instead of all time sum don't you?
I understood it this way:
201605051430    en    -     3
now there are 5 new incoming english tweets during the next minute so it'll be:
201605051430    en    -     3
201605051431    en    -     8

sorry, edited my comment.

hey @loewenzahm .
you got it totally right.


Fix an include

Currently rendering funny because of the leading +

@ranieuwe,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@ranieuwe : Thanks for your contribution to the Azure documentation! The author, @naziml, has been notified to review your proposed change.

#sign-off


Fix  Design Inconsistency across App/Client and Landing Page

Align the visual elements, typography, and color schemes of the app/client with the landing page to create a cohesive user experience. This will enhance brand recognition and improve overall aesthetics.
Definition of Completion: The app/client's design matches the landing page's style guide, including fonts, colors, spacing, and layout. All elements appear consistent and visually appealing.

Hello @fishonamos  I'm a frontend d3v and a blockchain dev I would like to work on this issue :) this will be my first time contributing on this project if I'm assigned
Please kindly assign :)

Note: Only applications through the OnlyDust platform will be considered.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a fullstack developer worked with various frontend frameworks over the years as well as backend frameworks. currently transitioning into the web3 space.
How I plan on tackling this issue
I will work wth the current library and framework of landver to deliver this task

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi, I’m Sudipta Paul, a full-stack developer with 1.5 years of experience, specializing in blockchain technology. I’ve worked on several web-based projects where consistency in design across pages was crucial to maintaining a cohesive user experience.
How I plan on tackling this issue
My approach to solve this issue:
Will start by reviewing the design specifications of the landing page, including typography, color palettes, spacing, and layout components. This will be used as the baseline for ensuring consistency.
I will conduct a thorough audit of the current app/client interface, identifying all visual elements that differ from the landing page, such as font styles, color mismatches, button sizes, and padding inconsistencies.
Based on the audit I will update the app/client's Ui components to match the landing page. This will include:
Updating font family, size, weight
Applying consistent color schemes
Aligning the layout and spacing according to the style guide
Ensuring uniform button styles, input fields, and hover effects
I will ensure that the updated design remains responsive across devices and performs consistently across different browsers.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a full-stack developer with experience in QA testing and languages like Python, Cairo, Solidity, React, and JavaScript.
How I plan on tackling this issue
i will Establish a clear brand identity,
Use consistent typography and color schemes,
Define visual elements and layout guidelines,
Test for usability and consistency.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hey! I'm Lau Chaves, Im part of Dojo Coding Costa Rica! I would like to contribute to this issue!
I have over 5 years of experience working with JavaScript, React, and TypeScript, ruby...
My primary role has been as a front-end developer, and I have a keen eye for detail and a strong focus on mobile-first approaches. I ensure the quality of my work through rigorous self- QA processes. I have a solid knowledge of CSS, Sass, and styled-components.
How I plan on tackling this issue
This is the approach Id follow:

I’d review the entire app, looking for inconsistencies in fonts, colors, spacing, and layout compared to the landing page.
I’d adjust the typography in the app to match the styles used on the landing page.
I’d update the color scheme in the app to ensure it aligns with the landing page's colors.
I’d refine the spacing and layout of elements to ensure a consistent look.
I’d test the app on different devices to confirm that the design looks good and responsive.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi, I'm Josué Brenes and I'll be working on issue.
I'm Dojo Coding member.
I estimate this will take 3 day to complete.
How I plan on tackling this issue
Here’s how I would tackle this issue:

Review the landing page’s style guide:

I will analyze the design specifications of the landing page, including the fonts, colors, spacing, and layout. I will ensure that these design elements are consistently used across both the app/client and the landing page.

Update the app/client’s visual elements:

I will identify any discrepancies between the app/client’s design and the landing page. This includes ensuring that the typography (font family, size, weight) matches, along with the correct color schemes and spacing.
I will align the app/client’s UI components (such as buttons, forms, and headings) with the landing page to create a cohesive look and feel.

Test for consistency:

I will manually verify that all visual elements in the app/client are consistent with the landing page’s design. This will include checking font rendering, color accuracy, and spacing in different viewports (responsive design).
I will conduct usability tests to ensure the changes maintain or enhance user experience without any visual inconsistencies.

Completion Criteria:

The issue will be considered resolved when the design of the app/client fully matches the style guide of the landing page, with all elements such as fonts, colors, and spacing appearing visually cohesive and appealing.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Good day, my name is Deon and I’m a Full-Stack web3 developer with a strong passion for creating intuitive and user-friendly interfaces.
I have experience in writing Typescript as well as modern JavaScript and its frameworks and a keen eye for design, which allows me to effectively translate design concepts into functional web applications.
I’m dedicated to enhancing user experiences and continuously learning about best practices in frontend development.
How I plan on tackling this issue
How I Plan To Solve This Issue

I’ll begin by analyzing the existing visual elements in both the app/client and landing page. Then Identify discrepancies in buttons, icons, and other UI components.

I will refer to the existing style guide that includes the visual elements used on the landing page and ensure that all components in the app/client are consistent.

I will check the typography in both the app/client and landing page and note for any differences in font styles, weights, and sizes.

I will then update the app/client to use the same fonts as the landing page and make sure that headings, body text, and other typographic elements are uniform across both platforms.

I will compare and adjust the colors in the app/client to match those specified in the landing page style guide and make sure that the overall color usage enhances brand recognition.

Finally, I'll thoroughly examine the spacing and layout of elements in both the app/client and landing page and look for inconsistencies in margins, padding, and alignment and correct them immediately and make sure that the app/client layout aligns with the landing page’s spacing guidelines

If given the opportunity to contribute to Landver via this issue, I promise to deliver and ensure a seamless, cohesive design experience that aligns with the project’s goals.
My focus will be on maintaining high-quality standard and timely completion to meet the expectations of the team. I'm excited about the opportunity to contribute and can't wait to get started, Do have a great day.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Fix Design Inconsistency across App/Client and Landing Page
Hello LandVer team,
I am Joel Vargas, and I'm a member of Dojo Coding. I also come from OnlyDust.
I would like to request the assignment of this issue. Below is my proposed approach for implementing this issue:
How I plan on tackling this issue
Proposal to Align App/Client Design with Landing Page
Problem
Currently, the visual elements, typography, and color schemes of the app/client do not align with those of the landing page. This inconsistency can lead to a disjointed user experience and may hinder brand recognition. A cohesive design across all platforms is crucial for establishing a strong brand identity and ensuring that users feel a seamless transition between the landing page and the app.
Solution
To address this issue, I propose a comprehensive review and alignment of the app/client’s design with the landing page's style guide. This will involve adjusting typography, color schemes, spacing, and layout to ensure consistency and visual appeal throughout the application.
Key Features

Typography Alignment:

Update font families, sizes, and weights in the app/client to match those used on the landing page.
Ensure that heading and body text styles are consistent, enhancing readability and brand recognition.

Color Scheme Synchronization:

Implement the same color palette used on the landing page across all app/client components.
This includes primary, secondary, and accent colors to maintain visual harmony.

Consistent Spacing and Layout:

Review and adjust margins, padding, and overall layout to ensure it aligns with the landing page design.
Ensure that elements like buttons, forms, and cards have a consistent look and feel.

Visual Element Standardization:

Ensure all icons, buttons, and UI components match the style used on the landing page.
Use Tailwind CSS to maintain consistency in sizing and appearance.

Implementation Details

Style Guide Reference:

Utilize the landing page’s style guide as a reference document for all design updates.
Document the key styles such as typography, color schemes, and spacing in a centralized location.

Tailwind CSS Configuration:

Update the Tailwind CSS configuration file (tailwind.config.js) to include custom colors, font families, and spacing values that match the landing page.
Example configuration:module.exports = {
  theme: {
    extend: {
      colors: {
        primary: '#FF5733', // Example primary color
        secondary: '#C70039', // Example secondary color
      },
      fontFamily: {
        sans: ['Inter', 'sans-serif'], // Example font family
      },
      spacing: {
        '4': '1rem', // Example spacing
        '8': '2rem',
      },
    },
  },
};

Component Review and Update:

Review all existing components and update their styles to match the new design specifications.
For example, update button styles:<button className="bg-primary text-white font-bold py-2 px-4 rounded">
  Click Me
</button>

Testing and Validation:

After implementing the design changes, conduct thorough testing to ensure that all elements display correctly and are visually consistent.
Gather feedback from team members or stakeholders to identify any areas for further improvement.

Definition of Completion
The project will be considered complete when:

The app/client's design fully matches the landing page's style guide, including fonts, colors, spacing, and layout.
All visual elements appear consistent and visually appealing across different devices and screen sizes.
The user experience is cohesive, enhancing overall brand recognition.

Benefits

Enhanced Brand Recognition: A cohesive design will reinforce brand identity, making it more recognizable to users.
Improved User Experience: Consistency in design elements will lead to a more intuitive and visually appealing experience for users.
Streamlined Development: Establishing a unified style guide will simplify future design updates and component creation.

Next Steps

Implement the proposed design updates.
Conduct testing for visual consistency and user experience.
Gather user feedback for potential refinements.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I'm a frontend and smart contract developer and I'd be happy to contribute to this project.
How I plan on tackling this issue
Here is how I intend to tackle this task:

Review both the app/client and the landing page to identify inconsistencies in fonts,

colors, button styles, spacing, and layout.
List all the design elements (headers, footers, buttons, forms, typography, etc.)
that need to be aligned.
3.Implement Design Changes in the App/Client:
Apply the typography settings across the app to ensure consistent use of fonts, headings, paragraphs, and buttons.
Update the color scheme in the app by replacing any mismatched colors with those specified in the landing page's style guide.
Ensure consistent spacing by adjusting margins and padding to match the grid system of the landing page.

Align UI components (e.g., buttons, cards, forms) so they match the visual style of the landing page in terms of shape, shadow, border radius, and hover states.
Cross-platform Consistency:

I will ensure that both the app and landing page look visually cohesive on different devices (desktop, tablet, mobile) by testing responsiveness and adjusting the layout where necessary.
Collaborate with Design.

I will ensure that all elements appear uniform and aligned across the app/client and the landing page.
Get feedback from users and stakeholders to validate the new design’s consistency and visual appeal.

ETA: 2-3 days.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a software developer with 6 years experience building applications
How I plan on tackling this issue
Use the landing page as a guide to align typography, visual elements and color schemes of the app/client to pixel perfect implementation

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a Full Stack Developer specializing in Next.js, TypeScript, Node.js, Cairo and Rust . With over 31 contributions across projects in the OnlyDust ecosystem, I’ve developed strong proficiency in delivering high-quality solutions and resolving complex issues within tight deadlines. My experience spans frontend, backend, smart contracts, and the optimization and maintenance of scalable codebases.
How I plan on tackling this issue
To fix the design inconsistency between the app/client and the landing page, I will review the visual elements, typography, and color schemes of both. The goal is to make them look and feel the same, which will improve brand recognition and the overall look of the app.
I will start by checking the landing page’s style guide for key details like fonts, colors, spacing, and layout. Then, I will apply these styles to the app/client, ensuring that buttons, headings, and icons match. This may involve updating CSS styles and creating reusable design components.
I will also adjust the typography and spacing to align with the landing page’s design. After making these changes, I will thoroughly review the app/client to ensure everything is consistent. The task will be complete when the app/client design matches the landing page’s style guide, making the overall user experience better.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I'm a Full Stack Blockchain Developer with demonstrable expertise across modern web and blockchain technologies. My tech stack centers on Next.js, TypeScript, React, and Node.js for web development, complemented by Three.js for 3D experiences, and Solidity/Rust for blockchain solutions.
What sets me apart is my proven track record on OnlyDust, where I've made 83 significant contributions across 15 different projects since Edition 1. This extensive involvement reflects my ability to deliver quality solutions under tight deadlines while adapting to diverse project requirements.
With my deep experience in hackathon environments, I bring both technical excellence and practical development skills to the table. I'm confident I can contribute meaningfully to pushing the boundaries of what's possible in blockchain development while maintaining a focus on user-centric solutions.
My profile (https://app.onlydust.com/u/Ugo-X) showcases my consistent ability to deliver results across various blockchain challenges. I'm excited to bring this experience and drive for innovation to your team.
How I plan on tackling this issue
Audit the Current Design: I’ll start by performing a comprehensive review of the existing visual elements on both the app/client and the landing page. This involves looking closely at typography, color schemes, spacing, and layout to pinpoint inconsistencies. This step will help me identify the specific areas that require alignment.
Establish a Unified Style Guide: I’ll either create a new style guide or refer to the existing one from the landing page to serve as the basis for the app/client design. This guide will outline the appropriate fonts, color palettes, and spacing to maintain consistency throughout. I’ll also consider breakpoints for responsive design to ensure a uniform experience across all devices.
Update Typography and Color Schemes: I’ll adjust the fonts and colors in the app/client to align with those used on the landing page. Utilizing Tailwind CSS or the current CSS framework, I’ll ensure that the app/client adopts the correct styling, modifying any overrides or custom styles that don’t conform to the guide.
Align Layout and Spacing: I’ll concentrate on the layout structure and spacing, ensuring that margins, padding, and alignment are uniform across both platforms. This may require tweaking the grid systems or flexbox layouts in the app/client to reflect the structure of the landing page.
Review and Test: Once the necessary changes are made, I’ll review the app/client alongside the landing page to ensure that the visual elements are cohesive. I’ll also test the design on various screen sizes and devices to guarantee responsiveness and a good user experience across all platforms.
Feedback and Iteration: After implementing the initial design updates, I’ll seek feedback to ensure that the app/client meets expectations. I’ll make any minor adjustments based on this feedback before the final release.
Expected time of delivery: 3-4 days.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hi, I'm Collins a frontend and blockchain developer, and an active contributor on OnlyDust. You can check out my profile here: https://app.onlydust.com/u/0xdevcollins. This is my first time contributing to this repository, and I’m excited about the opportunity to contribute. Looking forward to collaborating!
How I plan on tackling this issue
I'll ensure the app's design perfectly aligns with the landing page by matching fonts, colors, and layout, creating a seamless, cohesive user experience that strengthens brand recognition and enhances visual appeal across platforms.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have a deep passion for Web3 and I am currently working as a frontend developer intern at a Web2 company, focusing on Next.js. Additionally, I am an active member of Dojo Coding, a prominent Web3 community in LATAM, which has given me great exposure to decentralized technologies.
Recently, I have been working on a project for Base LATAM's Buildathon, where I am gaining hands-on experience in building decentralized applications. I am eager to continue growing and contributing, and see this as a fantastic opportunity to further develop my skills and make a significant impact.
This is my first OD Hack, so I will appreciate it if you give me the chance to contribute to this amazing project.
Some frontend projects that i have:
https://buildmyevent.xyz/
https://peritazgo-website.vercel.app/
How I plan on tackling this issue
To address the design inconsistency across the app/client and landing page, I would take the following steps:
Review the Existing Design Elements: I would start by conducting a thorough review of both the app/client and the landing page to identify all visual elements, including typography, color schemes, buttons, icons, and spacing. This analysis will help pinpoint the specific areas that require alignment.
Establish a Style Guide: Based on the review, I would create or update a comprehensive style guide that outlines the fonts, color palettes, button styles, and spacing rules that should be used consistently across both platforms. This guide will serve as a reference for the development team to ensure all new and existing components adhere to the same design standards.
Implement Consistent Typography: I would align the typography used in the app/client with that of the landing page, ensuring that font families, sizes, weights, and line heights are consistent. This will create a unified look and feel across the entire user interface.
Harmonize Color Schemes: I would adjust the color schemes in the app/client to match the landing page’s colors, ensuring that primary, secondary, and accent colors are used uniformly. This consistency will enhance brand recognition and visual appeal.
Align Spacing and Layout: I would standardize the spacing and layout of elements within the app/client to mirror the landing page’s design. This includes margins, paddings, and alignment of components to create a harmonious visual flow throughout the application.
Conduct User Testing: Once the adjustments have been made, I would perform user testing to gather feedback on the new design. This step ensures that the updates enhance the user experience and meet the needs of the target audience.
Definition of Completion: The task will be considered complete when the app/client's design matches the landing page's style guide, including fonts, colors, spacing, and layout. All elements should appear consistent and visually appealing, providing users with a cohesive and enjoyable experience.
By implementing these steps, I aim to create a unified design language across the app/client and landing page, ultimately enhancing brand recognition and improving the overall aesthetics of the platform.
@fishonamos I hope you give me the opportunity to contribute to this amazing project; I would be very grateful.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a full stack developer with over a year experience in software development which will be leveraged to implement these changes while maintaining a user-friendly experience.
How I plan on tackling this issue
I will approach by extracting components from the design, implementation and working closely with the design.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
Hello, I'm Dprof-in-tech, a seasoned Full Stack Blockchain Developer, and I'm excited to be part of ODHACK 9! I have a strong foundation in technologies such as Next.js, TypeScript, JavaScript, React, Node.js, Rust, and Cairo, I've built extensive experience across the blockchain development landscape.
I first got involved with OnlyDust during Edition 2, and since then, I've made 39 contributions across 11 different projects. Working on the platform has really helped me sharpen my skills, especially when it comes to delivering great solutions under tight deadlines. I love combining technical know-how with a user-focused approach, whether it's building immersive 3D experiences or crafting smart contracts that solve real-world problems.
Throughout, I've consistently demonstrated the ability to adapt and contribute effectively to diverse challenges. I'm confident in my ability to tackle new problems and drive innovation within the blockchain space. As we kick off ODHACK 9, I'm eager to apply my previous experience and technical expertise to push the boundaries of what's possible.
You can view my public profile on OnlyDust here: https://app.onlydust.com/u/Dprof-in-tech
How I plan on tackling this issue
Approach for Issue #91: Fix Design Inconsistency across App/Client and Landing Page
Audit the Current Design: I’ll begin by conducting a thorough review of the existing visual elements on both the app/client and the landing page. This includes examining typography, color schemes, spacing, and layout on each to identify where the inconsistencies lie. This step will allow me to map out the specific areas that need alignment.
Establish a Unified Style Guide: I’ll create or refer to the existing style guide from the landing page and use it as the foundation for the app/client design. This guide will define the correct fonts, color palettes, and spacings to ensure consistency across the board. I'll take into account breakpoints for responsive design to ensure consistent experience on all devices.
Update Typography and Color Schemes: I’ll update the fonts and colors in the app/client to match those used on the landing page. Using Tailwind CSS or the existing CSS framework, I’ll ensure the app/client inherits the correct styling, adjusting any overrides or custom styles that don’t align with the guide.
Align Layout and Spacing: I’ll focus on layout structure and spacing, ensuring that margins, padding, and alignment are consistent across both platforms. This might involve modifying the grid systems or flexbox layouts used in the app/client to ensure it mirrors the landing page’s structure.
Review and Test: After making the necessary changes, I’ll review the app/client alongside the landing page to confirm the visual elements are now cohesive. I’ll also test the design on various screen sizes and devices to maintain responsiveness and user experience across all platforms.
Feedback and Iteration: Once the initial design updates are implemented, I’ll seek feedback to ensure that the app/client aligns with expectations. Any small tweaks or adjustments will be made based on this feedback before the final release.
Expected time of delivery - 3-4 days

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I have over 3 years of experience as a frontend developer, with a strong foundation in design from my early career as a graphic designer. This unique combination of skills allows me to bridge the gap between design and development, ensuring that applications not only function well but also align visually with established design guidelines. My expertise lies in HTML, CSS, JavaScript, and React.js, and I have a deep understanding of typography, color theory, and layout design from my design background.
In this role, my design experience enables me to meticulously align visual elements, typography, and color schemes with the style guide of a landing page or app, ensuring brand consistency and improving aesthetics. I understand the importance of maintaining a cohesive user experience, as it enhances both brand recognition and user satisfaction. My ability to work with style guides to match fonts, colors, spacing, and layout will ensure that the app's interface appears consistent and visually appealing.
How I plan on tackling this issue
First, I would thoroughly review the existing style guide, taking note of the specific fonts, colors, spacing, and layout guidelines. This step is critical in ensuring I understand the brand’s visual identity and the expectations for the design alignment.
Then I would perform a visual audit of both the client and the landing page, identifying areas where inconsistencies exist. This would include checking typography (fonts, sizes, weights), color schemes, spacing between elements, and overall layout structure. I would work closely with the design and product teams to get feedback throughout the process. This collaboration ensures that the implementation stays true to the original design vision.
Once the adjustments are in place, I would perform a final review and test the app on various browsers and devices to ensure all elements are consistent, visually appealing, and adhere to the style guide.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am Santiago Villarreal Arley, a passionate software developer with a growing interest in Web3 technologies. Over the past few months, I've had the opportunity to work on innovative projects, such as BuildMyEvent, an open-source initiative that leverages blockchain and decentralized systems. I thrive on problem-solving and enjoy the challenge of integrating cutting-edge solutions into real-world applications. My goal is to contribute to the Web3 ecosystem by staying ahead of emerging trends, learning continuously, and developing projects that push the boundaries of decentralized technologies.
How I plan on tackling this issue
I’d love to contribute to aligning the visual elements, typography, and color schemes of the app/client with the landing page to create a cohesive user experience. Here's my proposed approach:
Style Guide Review:
I’ll begin by reviewing the landing page’s style guide to identify key design elements like fonts, colors, spacing, and layout patterns. This will form the basis for aligning the app/client design.
Typography Implementation:
I’ll ensure that the fonts and text styles used across the app/client match those of the landing page for headers, body text, and buttons, ensuring a unified and professional look.
Color Scheme Matching:
I’ll apply the exact primary and secondary colors from the landing page throughout the app/client, including backgrounds, buttons, and interactive elements, to enhance brand recognition and consistency.
Layout and Spacing:
I’ll align the spacing, padding, and margins to mirror the landing page, ensuring that the layout feels cohesive and visually appealing across both platforms.
Consistent UI Elements:
I’ll ensure that buttons, form inputs, icons, and other UI components follow the same styling rules as the landing page, including interaction states like hover, focus, and active.
Testing and Final Adjustments:
After implementing the changes, I’ll test the app/client across different devices and screen sizes to make sure tI look forward to contributing and ensuring a consistent user experience across the app and landing page!he visual consistency holds. I’ll also collaborate with the design and QA teams to ensure the final result is pixel-perfect.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am a python dev . A new-comer here, willing and ready to contribute to solve the  issue.

I am applying to this issue via OnlyDust platform.
My background and how it can be leveraged
I am  a fullstack blockchain dev with years of experience , i love this project and would love to contribute
How I plan on tackling this issue
I plan on following the guidelines strictly and implementing as directed
ETA: 48 hours max

@fishonamos , i have fixed the issue here


fix: Handle LlamaIndex Update

PR Dependency

This PR is dependent on the resolution of PR #1

Description
LlamaIndex ChatEngine, ChatMemoryBuffer, BaseMemory relationship.

ChatMemoryBuffer inherits BaseMemory.
ChatEngine has a memory field whose type is BaseMemory.

Before v0.8.57

As ChatEngine such as SimpleChatEngine or ContextChatEngine depends on BaseMemory interface, ChatEngines only used abstract methods (get, put, etc) defined in BaseMemory.

Onward v0.8.57

However, onward v0.8.57, ChatEngines started using methods that are NOT defined in BaseMemory but in ChatMemoryBuffer (It's a bad design violating LSP?).

That's why our SDK introduced errors for llama index integration as we provide a wrapper class for BaseMemory which does not have ChatMemoryBuffer specific methods/attrs.

Proposed Solution

Using dynamic attrs dict, if the memory instance is of ChatMemoryBuffer, the specific methods/attrs are added to the dynamic attrs dict.
When Chatengines reference these such as self._memory.tokenizer_fn, I set __getattr__ to link them.

I'm not sure if it's a good solution since if other concrete BaseMemory classes are added, then a bunch of isinstance will occur.

#1과 동일한 이슈가 있는 것 같습니다. 모두 수정 부탁드려요

@noisrucer main 기준으로 Rebase 해주세요. Diff가 조금 불필요한 내용까지 있는 것 같아요


Main.close() never close active connections

Main class close() method - Close any persistent connections.
  private void close() {
    client.connectionPool().evictAll(); // Close any persistent connections.
  }

ConnectionPool.evictAll() - Close and remove all idle connections in the pool.
  /**
   * Close and remove all idle connections in the pool.
   */
  public void evictAll() {
    List<RealConnection> evictedConnections = new ArrayList<>();
    synchronized (this) {
      for (Iterator<RealConnection> i = connections.iterator(); i.hasNext(); ) {
        RealConnection connection = i.next();
        if (connection.allocations.isEmpty()) {
          connection.noNewStreams = true;
          evictedConnections.add(connection);
          i.remove();
        }
      }
    }

    for (RealConnection connection : evictedConnections) {
      closeQuietly(connection.socket());
    }
  }

Condition connection.allocations.isEmpty() closes the connection only if there are no active streams in this connection
list of revisions:

ConnectionPool Rename evictAll() -> closeIdle()
Mark evictAll() method is Deprecated
ConnectionPool Add method closeAll() - Close any persistent connections.
Main close() method call client.connectionPool().closeAll()
fix OkHttpClient javadoc
fix tests

Correct me if I'm wrong.

@swankjesse If I call the close () method in the Main class, I expect that all connections will be closed, not just those that are inactive.

OkCurl’s close method is not public API.

It seems like we should have some API for closing all connections including active ones, as there are scenarios where callers are somewhat out of our control, and there are shared HTTP/2 connections that have inflight requests at all times.


The "any" definition in the schema does not allow for number

The parameters in a template pipeline have a field, default, defined as "any".
"any" can be seen here:
https://github.com/microsoft/azure-pipelines-vscode/blob/2e9781b705725387964e1931d9f52ae455746ca1/service-schema.json#L30-L46
It does not include numeric types. The following pipeline therefore fails validation:
parameters:
- name: vals
  default: [1, 2]
jobs:
- ${{ each val in parameter.vals }}:
  - job: foo
    steps:
    - bash: echo ${{ val }}

My understanding is that the above is valid, and that these values will be coerced to strings appropriately.

This is once again a problem with the ADO-defined schema, and unfortunately out of the control of this extension :(.
From https://github.com/microsoft/azure-pipelines-vscode/issues/411#issuecomment-890723614 it looks like this behavior might be intentional, which would be very confusing...I need to sit down sometime and figure this all out, then decide who to file bugs on.

Hi @sirosen, this issue isn't retated to this extension. You can submit the same issue to Microsoft developer community. Do you have any additional questions regarding azure-pipelines-vscode extension itself?

You can submit the same issue to Microsoft developer community.

No. This is where I draw the line as a developer of FOSS software who is only working with this schema on personal time. The schema is in this repo.
Judging from @50Wliu's response, the schema is actually provided by some other upstream team.
I should note that the schema is listed in SchemaStore as being available here. That's a community project, but if there's a more accurate location that I and others should be going to get the schema, tell me and I'll put in a PR to update SchemaStore.

@sirosen, the schema in this repository is generated on the Azure DevOps server, the VSCode extension only is just a schema consumer, so to fix this schema - first need to fix the schema on Azure DevOps side. The schema in Azure DevOps is supported by another team, and to fix this problem it would be better to create a ticket on the Microsoft developer community, once the schema will be updated we will be able to update it on the extension side.

@golubev-ivan is right. As for why it appears like we own the schema (and why I assume Schema Store points to this repo as the source location) - the API endpoint to retrieve the schema is organization-specific because organizations can install extensions that add custom tasks. This extension doesn't yet support retrieving the org-specific schemas on-demand, so it provides a baseline by using a dummy ADO organization to copy over the base schema on every extension release (see https://github.com/microsoft/azure-pipelines-vscode/blob/main/RELEASE.md#bumping-service-schema).
The real source of truth is dependent on your ADO organization, and available using https://docs.microsoft.com/en-us/rest/api/azure/devops/distributedtask/yamlschema/get.

it provides a baseline by using a dummy ADO organization to copy over the base schema on every extension release

Is that location publicly available?
Better yet, can you ask the Azure Pipelines developers provide the base schema from a URL where we could GET it and list it in SchemaStore, to cut out the middleman? Not only would this drop the need for the VSCode extension maintainers to keep a dummy org around (unless it's needed for other things too), it would also clarify who owns the schema and where to go to report bugs with it.

I hope you can understand my distaste for mucking around in a support forum when I'm trying to report a bug.
I'm not trying to be belligerent about this, but there's a history of discussion in this repo about issues pertaining to the schema and schema validation. Enough so that there's an accurate-yaml-validation label on this bug report.
For example, looking at past reported issues in that forum, it's easy to find things like this bug report about missing support for template expressions which just refers back to #187 on this repo! I shouldn't think it's at all surprising that the support personnel manning that forum would prefer to push tickets to a more technical space for discussion.
Plus, there are tickets like #411, where there wasn't any runaround about "this isn't the right place for this".
I'll bend in this case, and put in a message in that forum. But I think it should be clear why the decision to boot these tickets out of this repo appears arbitrary.

Is that location publicly available?

Nope (most likely for compliance reasons even if there's nothing stored in it).

Better yet, can you ask the Azure Pipelines developers provide the base schema from a URL where we could GET it and list it in SchemaStore, to cut out the middleman?

This would be great! I'll defer to @golubev-ivan on this.

I hope you can understand my distaste for mucking around in a support forum when I'm trying to report a bug.

I understand, it's not very clear that this repository doesn't own the schema. That's something we can do better at clarifying. What makes it even trickier is that parts of the schema (builtin tasks at https://github.com/microsoft/azure-pipelines-tasks) are controllable.
This is getting into the weeds, but "accurate-yaml-validation" more-or-less covers three areas:

Validation issues with the "core" schema (non-tasks) are out of our control, but the standard has sort of been to keep them open to reduce the number of duplicate issues we get. Moving forward I think the best course of action is still to keep them open, but also to file Developer Community tickets.
Validation issues with tasks are also kept open, and we try to be good at upstreaming PRs to azure-pipelines-tasks to fix those, then closing the issue once they're ingested into the schema endpoint.
Validating correctness beyond the schema, such as template expressions, unique stage names, or only using runtime variables when allowed. And technically those issues belong in azure-pipelines-language-server, but again we're treating this repository as the landing pad because they're so tightly coupled.

Essentially, it boils down to "this repository is an aggregator of validation-related issues for visibility. We can answer questions, but if you're looking for something to be fixed, that ultimately needs to happen elsewhere", elsewhere being Developer Community/azure-pipelines-tasks/azure-pipelines-language-server.

I can't provide the base schema and as far as I know, there is no way to get the base schema that isn't related to the organization now. Right now you can only get a scheme related to the organization, as @50Wliu mentioned.

The real source of truth is dependent on your ADO organization, and available using https://docs.microsoft.com/en-us/rest/api/azure/devops/distributedtask/yamlschema/get.

Predictably, the response from filing this bug report in that forum is less than satisfactory. The same holds for the other bug I took the time to report there.
All I wanted out of this was to somehow get a message to the schema maintainers that their schema has inaccuracies which make it very difficult to use for validation outside of the language-server. If the org decides that's not a problem because it works for the language server, and you want to close this as a wontfix, then please just do that.
This reply made me think that "okay, this will get upstreamed appropriately." But at this point, it's starting to seem that there's no way for me -- a downstream software developer trying to work with this schema -- to report issues directly to the team responsible. I want to report problems with the schema in a place where I'm not going to have to explain myself eight times over, and the repo maintainers don't want to hear about it because the schema is officially not their area of concern. It seems that we're just talking in circles.

I'm very frustrated at this point, but not insensitive to the repo maintainers' concerns. The fact that the schema is publicly visible here is pretty much an accident of software development, not any kind of carefully considered decision.
However, here's where I'd point out an (at least apparent) inconsistency:

Essentially, it boils down to "this repository is an aggregator of validation-related issues for visibility. We can answer questions, but if you're looking for something to be fixed, that ultimately needs to happen elsewhere", elsewhere being Developer Community/azure-pipelines-tasks/azure-pipelines-language-server.

If this is the place where validation issues go, then this is where validation issues go.
There's no more appropriate place for me to report an issue with the schema. The responses on the "Developer Community forum" demonstrate that it is a much less appropriate place to try to describe these problems. The personnel there don't even understand the bugs being reported.
I understand and respect that the team which maintains this repo cannot be expected to fix these issues. But you could just accept the bug reports, rather than asking me to waste time in a "support forum".

Hello @sirosen, I'm closing this ticket, since we can't help you with issues that are related to the schema, our team doesn't support Azure DevOps YAML schema. Extension in fact is the same consumer of ADO schema as you and all the questions related to schema outside our ownership.


New UI for the NAM trainer integrated into the nam

environment
New features:

Select amp capture directory and see list of all .wav files in that directory or any subdirectories
All settings saved and restored automatically
Custom model name, but based on name of selected amp capture
Selectable system theme, ui is 100% ttk widgets

Thanks for the PR! This looks pretty cool!
I'm not really keen on taking on maintaining a second, separate GUI trainer. Here are a few options:

You could keep this trainer as a separate resource (e.g. in its own repo) that builds on top of this repo. The advantage thee is that you can build as you like & to suit your needs, while having a clean interface between your work & this repo.
If you wanted to work in the changes to the existing GUI trainer, let's have a conversation about what the changes would be and how to get there. I'm open to the idea of having this become the official local GUI trainer if it checks the boxes that the existing one does.

But what I want to avoid is taking on the responsibility of maintaining a fourth(!) independent trainer in this repo. (In fact, thinking about it, I think I'm keen to deprecate colab.ipynb to simplify even further and get down to only 2 trainers to maintain! 🙂)

Of the two options above, (1) wouldn't involve a PR like this to the repo, and (2) would probably look quite a bit different, so I think that the right course of action from where we are here and now is to close this PR, and, if you're keen on (2), work out a plan in the Issues to get there.

Hi Steve, so to my knowledge this includes all of the features of the 0.5.1 nam GUI and adds what I described above. What do you feel needs to be changed or added to this version of the GUI in order to make it the official one?


Improve configuration for different vlei test scenarios

They should allow for singlesig/multisig/multi-user and composability across gleif/qvi/le/ecr etc.
@aydarng and I discussed this and perhaps it becomes like a github action yaml file, but that can be run from the test script, etc.

@aydarng will review the scenarios (single sig, multi user, multi sig, etc) and generated data with @HunnySajid and we can provide a demo UI feature to select the scenario to run the ui test.


Drop the oldest version of the docs with the CI job

This is the CI job https://github.com/iasql/iasql-engine/blob/main/.github/workflows/drop.yml


Current project status

Hi, what is the current status of the project? Are you looking for new maintainers?

Hi Daniel, thanks for asking.
Indeed, we have chosen to spend our open-source time on other projects for now (specifically on react-admin, which we use a lot internally).
If you're willing to give us a hand on gremlins.js, we'd love it!

So, any news on this?

We're still on other priorities, but we'll definitely give the Gremlins project some love later this year.

It’s time to give some love to this useful and fun package ! @Pierre and I are the new maintainers of this project.
We already publish a gremlins.js 2.0 and refresh the readme file.


Update using-the-windows-mixed-reality-simulator.md

fixed nested bullets and numbered lists

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/using-the-windows-mixed-reality-simulator.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Unable to Install-Module Intune from PowerShell Gallery on Win10

I'm trying to install the module in my Win 10 client and not in Cloud Shell.
A search for Intune at the PowerShell Gallery doesn't return a module named Intune: http://www.powershellgallery.com/items?q=Intune&x=0&y=0
I would hate to compile and install locally...
Results of attempt below:
PS C:\WINDOWS\system32> install-module Intune
PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'Intune'. Try
Get-PSRepository to see all available registered module repositories.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\<IP_ADDRESS>\PSModule.psm1:1809 char:21
+ ...          $null = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Ex
   ception
    + FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

PS C:\WINDOWS\system32> Get-PSRepository

Name                      InstallationPolicy   SourceLocation
----                      ------------------   --------------
PSGallery                 Untrusted            https://www.powershellgallery.com/api/v2/

Hello, I'm trying to setup the module per the .md. I am getting an error that the PowerShellGraphSDK.dll can not be loaded.
`PS C:\scripts\net471> import-module .\Microsoft.Graph.Intune.psd1
import-module : Could not load file or assembly 'file:///C:\scripts\net471\Microsoft.Intune.PowerShellGraphSDK.dll' or one of its
dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
At line:1 char:1

import-module .\Microsoft.Graph.Intune.psd1

  + CategoryInfo          : NotSpecified: (:) [Import-Module], FileLoadException
  + FullyQualifiedErrorId : System.IO.FileLoadException,Microsoft.PowerShell.Commands.ImportModuleCommand`

I'm still working through this but wondering if there is a known issue here. RS5 build of Windows 10.
Thanks,
Kevin

'ignore' apologize for this. I didn't get to the last comment in the .md file... it seems to be there.


Legion GO - desktop mode screen resolution 1200*1600 fails

Describe the bug
In desktop mode, i changed the resolution to 1200*1600 and the screen shows like this :

What did you expect to happen?
show the proper resolution
Output of rpm-ostree status
cvarandas@llg-baz:~$ rpm-ostree status
State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:stable
                   Digest: sha256:94e054df98891bbd320d1f7048e42be36baab5a9598c25aa90ed43c84350bdca
                  Version: 40.20240607.0 (2024-06-07T17:03:13Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck:40-testing-20240605
                   Digest: sha256:177fbfe8466f4d067fed0aae37b0b5a00b325a9c65ba529d859e7363d11d37e0
                  Version: 40.20240605.0 (2024-06-05T16:47:31Z)

Hardware
Legion GO

cvarandas@llg-baz:~$ cat /sys/devices/virtual/dmi/id/product_name
83E1

Extra information or context
I want to revert to the default resolution 1600*2560 , is there a way to do it via ssh ?
I also tried to rebase to the testing latest but no success...

Workaround to revert it :
mv ~/.config/kwinoutputconfig.json ~/.config/kwinoutputconfig.json.old

credits to HikariKnight from ublue discord !

this should be in an FAQ as this happened when i tried to duplicate the screen in desktop mode

this should be in an FAQ as this happened when i tried to duplicate the screen in desktop mode
switch to a console ctrl+alt+f2, login and remove the file

literally in the wiki/documentation and only affects LGO
https://universal-blue.discourse.group/docs?topic=2413#workarounds-known-issues-3


Run dem from any directory within virtual-env

Probably easiest to fetch the VIRTUAL_ENV and go to the parent of that...?

Currently since DEM is not installed into the virtual-env the requirments are missing

Closing, #7 should fix this.


WSL should support enum

Migrated from https://bugs.webkit.org/show_bug.cgi?id=176977:
At 2017-09-15T04:32:20Z<EMAIL_ADDRESS>wrote:
...

At 2017-09-18T19:02:49Z<EMAIL_ADDRESS>wrote:
Ima do this next.

At 2017-09-19T03:21:58Z<EMAIL_ADDRESS>wrote:
Created attachment 321179
the ptach

At 2017-09-19T00:40:57Z<EMAIL_ADDRESS>wrote:
Created attachment 321158
almost done

At 2017-09-19T03:18:24Z<EMAIL_ADDRESS>wrote:
Created attachment 321178
the patch

At 2017-09-19T03:44:15Z<EMAIL_ADDRESS>wrote:
(In reply to Myles C. Maxfield from comment #5)

Comment on attachment 321179 [details]
the ptach
View in context:
https://bugs.webkit.org/attachment.cgi?id=321179&action=review

Tools/WebGPUShadingLanguageRI/Intrinsics.js:111

           type.formatValueFromDoubleLiteral = value => value;

No rounding?

Oh!  Fixed.

Tools/WebGPUShadingLanguageRI/SynthesizeEnumFunctions.js:27
+function synthesizeEnumFunctions(program)

Wow, this is cool! Dynamically generating functions!
I wish I knew how to do this with clang (without emitting a giant string)

Tools/WebGPUShadingLanguageRI/Test.js:3929

   Foo war()

   {

       return Foo.War;

   }

   Foo famine()

   {

       return Foo.Famine;

   }

   Foo pestilence()

   {

       return Foo.Pestilence;

   }

   Foo death()

   {

       return Foo.Death;

   }

Couldn't you do, like, months of the year or something?

;-)

At 2017-09-19T03:35:46Z<EMAIL_ADDRESS>wrote:
Comment on attachment 321179
the ptach
View in context: https://bugs.webkit.org/attachment.cgi?id=321179&action=review

Tools/WebGPUShadingLanguageRI/Intrinsics.js:111

           type.formatValueFromDoubleLiteral = value => value;

No rounding?

Tools/WebGPUShadingLanguageRI/SynthesizeEnumFunctions.js:27
+function synthesizeEnumFunctions(program)

Wow, this is cool! Dynamically generating functions!
I wish I knew how to do this with clang (without emitting a giant string)

Tools/WebGPUShadingLanguageRI/Test.js:3929

   Foo war()

   {

       return Foo.War;

   }

   Foo famine()

   {

       return Foo.Famine;

   }

   Foo pestilence()

   {

       return Foo.Pestilence;

   }

   Foo death()

   {

       return Foo.Death;

   }

Couldn't you do, like, months of the year or something?

At 2017-09-19T03:44:45Z<EMAIL_ADDRESS>wrote:
Landed in https://trac.webkit.org/changeset/222200/webkit

At 2017-09-27T19:36:10Z<EMAIL_ADDRESS>wrote:
rdar://problem/34693578


Use traffic manager

Currently AzureSpeed site is running in West US region which is slow for people in Asia regions, consider enable Traffic Manager to improve performance.

Azure traffic manager has been setup with performance profile with following endpoints

https://azurespeed-westus.azurewebsites.net/
https://azurespeed-eastasia.azurewebsites.net/


Nats msg bus

Hi,
what about to support/use Nats for the tcp proxy forwarding ?
Whit this approach it could be very easy to monitor the tcp traffic.
Bye,
Luca

any benefits?

Nats is a great idea .
The benefit is because NATS is at its core a virtualised router , with anything going through it . I use it for almost everything because you get automatic load balancing , clustering, retry.
As a consequence you can upgrade services or databases with zero downtime.
It’s  more like a mesh router in that way.

I'm not sure what's the relationship between nats and tproxy.


CLI: no assembly, missing main class to start with java -jar

I tried to build mima to use from the CLI.
There is no documentation to do so, so I tried a sbt packages
But then, I get:
java -jar ....reporter/target/scala-2.10/mima-reporter_2.10-0.1.14.jar --prev XXX --curr YYY
Error: main class not found: com.typesafe.tools.mima.cli.Main

I 'm wondering if  #155 didn't remove/broke the assembly target.

Yeah, that's the problem: reverting to commit before #155 (2cd1d8ddb116c20ac14d6f0059cd05e6387c15fe) make assembly task available and the CLI usable again.

you'll need to provide java with a full classpath:
% java -classpath /Users/tisue/.sbt/boot/scala-2.10.6/lib/scala-library.jar:/Users/tisue/.sbt/boot/scala-2.10.6/lib/scala-compiler.jar:/Users/tisue/.sbt/boot/scala-2.10.6/lib/scala-reflect.jar:/Users/tisue/.ivy2/cache/com.typesafe/config/bundles/config-1.0.0.jar:/Users/tisue/migration-manager/core/target/scala-2.10/mima-core_2.10-0.1.13-4-gbed1558.jar:/Users/tisue/migration-manager/reporter/target/scala-2.10/mima-reporter_2.10-0.1.13-4-gbed1558.jar com.typesafe.tools.mima.cli.Main
Usage: mima [<options>]

  necessary options:
                             --prev             Previous classpath/jar for binary compatibility testing.
                             --curr             Current classpath/jar for binary compatibility testing.

  optional settings:
                             --classpath        an optional classpath setting
    --filters          an optional problem filters configuration file, applied to both backward and forward checking
    --backward-filters an optional problem filters configuration file, only applied to backward checking
    --forward-filters  an optional problem filters configuration file, only applied to forward checking
    --generate-filters generate filters definition for displayed problems
    --direction        check direction, default is "backward", but can also be "forward" or "both"

@SethTisue : why not provide the assembly task? It would simpler (I know, everyone loves to build classpath by hand, but still, for the laziest of us :). And it would match the documentation.

FYI https://github.com/xuwei-k/mima

it would match the documentation

I see now that we didn't update https://github.com/typesafehub/migration-manager/wiki/MiMa-Command-Line-Tool at the time we removed the assembly stuff; that was an oversight.

why not provide the assembly task?

Well, I don't have a strong feeling about it one way or the other. The main goal of #155 was to get rid of the S3 stuff and simplify our release process. The assembly stuff came out at the same time, just because everyone we asked was only using the sbt plugin, so it wasn't clear the assembly stuff was worth continuing to maintain.
I don't think we want to go to the effort of actually publishing the assembly jar unless there's a strong indication that it would have more than a handful of users. But if someone wants to a submit a PR restoring the assembly task to the build, I wouldn't be opposed.

OH, I don't think you need to publish an assembly, but having the task would simplify the use of the CLI.
I think there is a relevant use case for the CLI (at least, it's that way we want to use it): we (are going to) need to check if external jars are binary compatible or not so that we can provide stable ABI for a plugin ecosystem. We won't own the jar builds (or not all, at least), so we will the cli.

PR is here: https://github.com/typesafehub/migration-manager/pull/167


Ability to stop autoplay after a swipe

I was wondering if is possible to add the feature to stop autoplay after the carousel has received one swipe.
From: http://baymard.com/blog/homepage-carousel

Auto-rotation should permanently stop after any active user interaction
If the user has interacted with the carousel beyond hover (e.g. actively changed a slide using the carousel controls), the auto-rotation should permanently stop – even when the user isn’t hovering the carousel.

When the user has actively changed slide by clicking the carousel’s next / previous buttons or slide indicators, the selection is likely to be intentional and should not be changed just because the user decides to check out other parts of the homepage before (potentially) returning to their selected slide.

A click is fundamentally different from hover, which at best can be used to gauge user focus. A click is an active user request and is a strong indicator of the user’s interests and intent. Therefore, permanently stop auto-rotation once the user begins actively interacting with the carousel, because they might have intentionally left the carousel at that particular slide.

Hi, I needed this functionality too so I have submitted #593
If you use it, just set props pauseOnSwipe and/or pauseOnChange to true

I propose a PR might related with this issue: https://github.com/akiran/react-slick/pull/589

I'm also interested in this functionality. It may be possible to do using events or methods, but to have it as an option out of the box would be incredibly useful.

yes, I also need this same functionality


In maximized window video is displayed on left.

I'll try with the exposed methods of window manager.


Updated SystemD version

CentOS7 has 219 version that not support cgroups v2. So it not working systemd with latest containers desktop software like Rancher Desktop, Podman Desktop and Docker Desktop.
Solution is upgrade systemd to latest: https://maciej.lasyk.info/2016/Dec/16/systemd-231-latest-in-centos-7-thx-to-facebook/
So I modified Dockerfile
Image build successful and runs.
❯ podman images
REPOSITORY                 TAG         IMAGE ID      CREATED        SIZE
localhost/centos7-ansible  latest      8b90aa09f595  2 hours ago    994 MB
quay.io/centos/centos      7           8652b9f0cb4c  24 months ago  212 MB

Run
docker-centos7-ansible on  master
❯ podman exec -it silly_solomon bash
[root@146df88e0ac0 /]# systemctl --version
systemd 234
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN default-hierarchy=hybrid
[root@146df88e0ac0 /]# systemctl status
● 146df88e0ac0
    State: running
     Jobs: 0 queued
   Failed: 0 units
    Since: Mon 2022-11-07 16:01:05 UTC; 11min ago
   CGroup: /
           ├─init.scope
           │ ├─  1 /usr/lib/systemd/systemd
           │ ├─121 bash
           │ ├─131 systemctl status
           │ └─132 more
           └─system.slice
             ├─systemd-udevd.service
             │ └─28 /usr/lib/systemd/systemd-udevd
             ├─systemd-journald.service
             │ └─21 /usr/lib/systemd/systemd-journald
             ├─dbus.service
             │ └─78 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
             └─systemd-logind.service
               └─77 /usr/lib/systemd/systemd-logind
[root@146df88e0ac0 /]#

Can you merge those changes to you main repo and update image in https://hub.docker.com/r/geerlingguy/docker-centos7-ansible
So it will help me not modify a lot of molecule configuration :)
Thank you in advance.

@geerlingguy This seems to work as expected

There are a lot of other changes in here, too—and I specifically am not upgrading the Python/Pip version because Python's yum/dnf integration that Ansible uses breaks on CentOS 7 and earlier if you run Python 3... it's a bit of a mess on CentOS 7 unfortunately :(

Hello,
Main thing is her probably that works. Python2 is outdated and Python3.6 also in CenOS7 so here in my opinion latest what it can  be.
If you don't want accept my changes just close this PR.


tabline: font color in buffers splits should be the same that for tabs

environment

vim: 8
vim-airline:
OS: arch
Have you reproduced with a minimal vimrc: No
What is your airline configuration:

" Airline Setup {{{
  let g:airline_theme='wombat'
  let g:airline#extensions#tabline#enabled = 1 "Show tabs if only one is enabled.
  let g:airline#extensions#tabline#show_splits = 1 "enable/disable displaying open splits per tab (only when tabs are opened). >
  let g:airline#extensions#tabline#show_buffers = 1 " enable/disable displaying buffers with a single tab
  let g:airline#extensions#tabline#tab_nr_type = 1 " tab number
  let g:airline#extensions#tabline#formatter = 'unique_tail'
  let g:airline#extensions#tabline#switch_buffers_and_tabs = 1
  let g:airline_powerline_fonts = 1
" }}}

if you are using terminal:

terminal: gnome
$TERM variable: xterm-256color
color configuration (:set t_Co?):

set t_Co=256

if you are using Neovim: 0.17
if has('termguicolors') " Truecolor. modern vim or nvim only.
  set termguicolors
  " vim only: RGB colors
  let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum"
  let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum"
endif

does it happen in Vim: Yes

actual behavior

font color of buffers open in splits (on the right at the image) should be the same than in the right. This is green font, instead of gray for my colorscheme.
expected behavior
same color scheme (the one for tabs) for buffers in the tabline.
if this is not the expected behavior, how can I change it?

different highlighting groups are on purpose.