Mobile - Adding Assets to the Project

According to updated mock-ups that can be viewed in #419, mobile project should have icons, images, radios and colors that are planned in mock-ups to make implementation easier.

Updated palette.dart file by adding the design colors and separating them to different classes to make them easier to use.

Updated assets as separating images, icons and radios into different directories. Updated some of the errors that occurred due to the changes in assets. Leaving the remaining errors to avoid conflicts.


Simple guinget UI (copied from OneNote)

List all the package IDs (and/or maybe package names?) in a panel on the left side with a search box and button above the list, then have the main panel (where the package list usually is) display package details with a dropdown for do nothing/install/uninstall/upgrade and a button next to it for it to do that action. There probably should be a version number dropdown somewhere too. The package details area can be like Linux Mint's Software Manager, so it has the app name, package ID, description, any other details like version number (though again a version dropdown may be a good idea unless I find a way to show the latest version, which I would prefer), and screenshots like the idea I have for screenshots in regular guinget.

Not sure if this is a good idea or not, just wanted to get it out  there. Maybe plugins would allow alternate layouts like this.


stats.spatio_temporal_cluster_1samp_test() fails with an index error

Describe the bug
stats.spatio_temporal_cluster_1samp_test() fails for me with an index error. Unfortunately I didn't manage to put together a MWE yet, but hopefully the provided information is sufficient to track things down? Any help would be greatly appreciated. :)
Steps and/or code to reproduce
src = mne.read_source_spaces(surface_source_space_file)
connectivity = mne.spatial_src_connectivity(src)

# Concatenate STCs from individual subjects.
# `stcs` is a list of SourceEstimates, one per subject.
# The resulting shape of the ndarray is (n_subj, n_timepoints, n_vertices)
stcs_for_stats = [s.data.T for s in stcs]
stcs_for_stats = np.array(stcs_for_stats)

mne.stats.spatio_temporal_cluster_1samp_test(
    X=stcs_for_stats,
    connectivity=connectivity,
    n_jobs=1,
    verbose=True)

Expected results
The function should return the results of the test.
Actual results
Using a threshold of 2.109816
stat_fun(H1): min=2.351713 max=20.239683
/Users/hoechenberger/Projects/TaLa/Code/Analysis/EEG/source_70_make_inverse_solution.py:132: RuntimeWarning: Provided stat_fun does not treat variables independently. Setting buffer_size to None.
  verbose=True)
Running initial clustering
Traceback (most recent call last):
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/IPython/core/interactiveshell.py", line 3326, in run_code
    exec(code_obj, self.user_global_ns, self.user_ns)
  File "<ipython-input-2-7331a14a6e31>", line 1, in <module>
    runfile('/Users/hoechenberger/Projects/TaLa/Code/Analysis/EEG/source_70_make_inverse_solution.py', wdir='/Users/hoechenberger/Projects/TaLa/Code/Analysis/EEG')
  File "/Applications/PyCharm.app/Contents/helpers/pydev/_pydev_bundle/pydev_umd.py", line 197, in runfile
    pydev_imports.execfile(filename, global_vars, local_vars)  # execute the script
  File "/Applications/PyCharm.app/Contents/helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
    exec(compile(contents+"\n", file, 'exec'), glob, loc)
  File "/Users/hoechenberger/Projects/TaLa/Code/Analysis/EEG/source_70_make_inverse_solution.py", line 132, in <module>
    verbose=True)
  File "</Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/externals/decorator.py:decorator-gen-218>", line 2, in spatio_temporal_cluster_1samp_test
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/utils/_logging.py", line 88, in wrapper
    return function(*args, **kwargs)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 1382, in spatio_temporal_cluster_1samp_test
    check_disjoint=check_disjoint, buffer_size=buffer_size)
  File "</Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/externals/decorator.py:decorator-gen-217>", line 2, in permutation_cluster_1samp_test
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/utils/_logging.py", line 89, in wrapper
    return function(*args, **kwargs)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 1264, in permutation_cluster_1samp_test
    buffer_size=buffer_size)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 875, in _permutation_cluster_test
    show_info=True)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 431, in _find_clusters
    ndimage)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 475, in _find_clusters_1dir_parts
    t_power, ndimage)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 527, in _find_clusters_1dir
    clusters = _get_clusters_st(x_in, connectivity, max_step)
  File "/Users/hoechenberger/miniconda3/envs/TaLa-source-loc/lib/python3.7/site-packages/mne/stats/cluster_level.py", line 254, in _get_clusters_st
    row, col = np.unravel_index(cl_goods, (n_times, n_src))
ValueError: index 4917600 is out of bounds for array with size 4917600

Additional information
In[3]: stcs_for_stats.shape
Out[3]: (18, 601, 8195)
In[11]: connectivity.shape
Out[11]: (8196, 8196)

Inside mne.stats.cluster_level._get_clusters_st():
In[3]: len(x_in)
Out[3]: 4925195
In[4]: n_src
Out[4]: 8196
In[5]: n_times
Out[5]: 600
In[7]: len(cl_goods)
Out[7]: 4925195

This is with master.

Can you share X and connectivity?

@larsoner Since this is actual, unpublished data, may I share this privately with you?

Sure, feel free to email a link

Done. Thanks for your help, @larsoner!

@larsoner:
I did like you proposed in the email and used the source space after forward computation
src = fwd['src']

instead of the original source space. With this, it works!
Turns out that during creation of the forward model, one data point was being dropped:
1 source space point omitted because of the    5.0-mm distance limit.
so I ended up having a discrepancy.  Good thing this one point had been omitted, otherwise I would have never found out!

Now, when running mne.spatial_src_connectivity() on the correct source space, I get this warning:
RuntimeWarning: 0.0% of original source space vertices have been omitted, tri-based connectivity will have holes. Consider using distance-based connectivity or morphing data to all source space vertices.
The original source spacing was oct6, and make_bem_model() was called with ico=4. Is this warning save to ignore? With matching source and BEM spacings (e.g., ico4 and ico=4, respectively),  the warning disappears.

I get this warning:

Yes this is your one vertex creating a hole. You can use dist-based connectivity instead to help mitigate the problems the hole creates with mesh-edge-based connectivity. If you created your original source space point with add_dist=True you can set e.g. dist=0.007 in spatial_src_connectivity.

With matching source and BEM spacings (e.g., ico4 and ico=4, respectively), the warning disappears.

This is probably because using an ico-4 spacing you've removed a ton of source space points, one of which was the one that got excluded during forward computation. I would not recommend this.

@larsoner

If you created your original source space point with add_dist=True you can set e.g. dist=0.007 in spatial_src_connectivity.

Thank you, this actually makes the warning go away! :)


pip issue

When I try to run the code in colab, it shows the following error for pip, and it also happens when I pip locally in my server:
!pip install -r requirements.txt --quiet
!pip install https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.0.0/en_core_web_sm-3.0.0.tar.gz
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 12.1/12.1 MB 13.2 MB/s eta 0:00:00
  Preparing metadata (setup.py) ... done
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 7.0/7.0 MB 10.2 MB/s eta 0:00:00
  Installing build dependencies ... done
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> See above for output.

  note: This error originates from a subprocess, and is likely not a problem with pip.
  Getting requirements to build wheel ... error
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

We have the same issue.

ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
flask 2.2.5 requires click>=8.0, but you have click 7.1.2 which is incompatible.
dask 2023.8.1 requires click>=8.0, but you have click 7.1.2 which is incompatible.
distributed 2023.8.1 requires click>=8.0, but you have click 7.1.2 which is incompatible.
fiona 1.9.6 requires click~=8.0, but you have click 7.1.2 which is incompatible.
inflect 7.0.0 requires pydantic>=1.9.1, but you have pydantic 1.8.2 which is incompatible.
pip-tools 6.13.0 requires click>=8, but you have click 7.1.2 which is incompatible.

I suspect that this is due to requirements.txt mixing static and non-static entries.

We have the same issue.


Update appveyor.yml

Travis tests have failed
Hey Owen McDonnell,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: ~2.6.1

YOUR TYPESCRIPT VERSION: 2.7.2

Please only submit bug reports when using the officially supported version.

=============
⠋ commands/report.ts⠙ extensions/functions/solidarityReport.ts⠹ commands/snapshot.ts⠸ commands/solidarity.ts⠼ extensions/functions/appendSolidaritySettings.ts⠴ extensions/functions/binaryExists.ts⠦ extensions/functions/buildSpecificRequirement.ts⠧ extensions/functions/checkCLI.ts⠇ extensions/functions/checkCLIForUpdates.ts⠏ extensions/functions/checkDir.ts⠋ extensions/functions/checkENV.ts⠙ extensions/functions/checkFile.ts⠹ extensions/functions/checkRequirement.ts⠸ extensions/functions/checkShell.ts⠼ extensions/functions/findPluginInfo.ts⠴ extensions/functions/getLineWithVersion.ts⠦ extensions/functions/getSolidaritySettings.ts⠧ extensions/functions/getVersion.ts⠇ extensions/functions/printResults.ts⠏ extensions/functions/quirksNodeModules.ts⠋ extensions/functions/removeNonVersionCharacters.ts⠙ extensions/functions/reviewRule.ts⠹ extensions/functions/setSolidaritySettings.ts⠸ extensions/functions/updateRequirement.ts⠼ extensions/functions/updateVersions.ts⠴ extensions/solidarity-extension.ts⠦ ./index.tsProcessed 33 files (993ms) (2 warnings)

Done in 5.50s.

     yarn danger ci

yarn run v1.3.2
$ /home/travis/build/infinitered/solidarity/node_modules/.bin/danger ci
You may have updated from Danger 2.x -> 3.x without updating from `danger` to `danger ci`.
The DANGER_GITHUB_API_TOKEN environmental variable is missing
Without an api token, danger will be unable to comment on a PR
Error:  Error: Cannot use authenticated API requests.
    at Object.getPlatformForEnv (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/platforms/platform.js:16:15)
    at Object.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:68:70)
    at step (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:32:23)
    at Object.next (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:13:53)
    at fulfilled (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:4:58)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:118:7)
    at Function.Module.runMain (module.js:692:11)
    at startup (bootstrap_node.js:194:16)
    at bootstrap_node.js:666:3
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: ~2.6.1

YOUR TYPESCRIPT VERSION: 2.7.2

Please only submit bug reports when using the officially supported version.

=============
⠋ commands/report.ts⠙ extensions/functions/solidarityReport.ts⠹ commands/snapshot.ts⠸ commands/solidarity.ts⠼ extensions/functions/appendSolidaritySettings.ts⠴ extensions/functions/binaryExists.ts⠦ extensions/functions/buildSpecificRequirement.ts⠧ extensions/functions/checkCLI.ts⠇ extensions/functions/checkCLIForUpdates.ts⠏ extensions/functions/checkDir.ts⠋ extensions/functions/checkENV.ts⠙ extensions/functions/checkFile.ts⠹ extensions/functions/checkRequirement.ts⠸ extensions/functions/checkShell.ts⠼ extensions/functions/findPluginInfo.ts⠴ extensions/functions/getLineWithVersion.ts⠦ extensions/functions/getSolidaritySettings.ts⠧ extensions/functions/getVersion.ts⠇ extensions/functions/printResults.ts⠏ extensions/functions/quirksNodeModules.ts⠋ extensions/functions/removeNonVersionCharacters.ts⠙ extensions/functions/reviewRule.ts⠹ extensions/functions/setSolidaritySettings.ts⠸ extensions/functions/updateRequirement.ts��� extensions/functions/updateVersions.ts⠴ extensions/solidarity-extension.ts⠦ ./index.tsProcessed 33 files (1.1s) (2 warnings)

Done in 6.25s.

     yarn danger ci

yarn run v1.3.2
$ /home/travis/build/infinitered/solidarity/node_modules/.bin/danger ci
You may have updated from Danger 2.x -> 3.x without updating from `danger` to `danger ci`.
The DANGER_GITHUB_API_TOKEN environmental variable is missing
Without an api token, danger will be unable to comment on a PR
Error:  Error: Cannot use authenticated API requests.
    at Object.getPlatformForEnv (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/platforms/platform.js:16:15)
    at Object.<anonymous> (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:68:70)
    at step (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:32:23)
    at Object.next (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:13:53)
    at fulfilled (/home/travis/build/infinitered/solidarity/node_modules/danger/distribution/commands/ci/runner.js:4:58)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
    at Function.Module.runMain (module.js:695:11)
    at startup (bootstrap_node.js:188:16)
    at bootstrap_node.js:609:3
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.


Log level settings

Hello! I've downloaded latest EVE app on my iPhone but can't find any LogLevel options in TYPES or on any devices I've checked (bridges, lights). How to change the log level for specific bridge or accessory? I have DiyHue bridge for my TV zone where I have thousands lines of logs about TV dynamic backlight lights.

It's on the accessory that Homebridge Hue exposes for the bridge.

Sorry, but it's not clear where is this device available? In EVE app? There is DiyHUE bridge available but no any TYPES in any UI screens I have. DO you have any demo/screenshots?

Damn, my bad.  Homebridge Hue doesn’t support setting the log level.  This feature is based on homebridge-lib, and only works for dynamic platform accessory plugins.  Homebridge Hue uses the old static platform accessories paradigm.  Changing this would cause you to lose all HomeKit accessories and associated rooms, groups, scenes, and automations, see https://github.com/ebaauw/homebridge-hue/issues/1070.
After having split off deCONZ support to Homebridge deCONZ, I want to split off support for the gen-2 Hue bridge to Homebridge Hue2.  Only after that I might consider refactoring Homebridge Hue for the gen-1 Hue bridge and the likes of DIYHue, if there is enough demand.  No ETA - too many other interesting devices and not enough time.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/699 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit b7d484e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-20-08-45-12 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b7d484e:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-20-08-45-12 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Url not recognised as zip

I am trying to download jabref (url: "https://www.fosshub.com/JabRef.html?dwl=JabRef-5.0-portable_windows.zip") but dl_urls fails to extract it because url_filename cuts off all url arguments and therefore dl_urls treats it is a html file
So is this intended behaviour or a bug?

Unfortunatelly you cannot use classic workaround with file rename like this, due to fosshub: (maybe could be fixed; not sure how painful it would be to fix)
    "url": "https://www.fosshub.com/JabRef.html?dwl=JabRef-5.0-portable_windows.zip#/cosi.zip",
    "hash": "4f410840f7821e25a09a5d1fa6408045df27bc4bcd8684fd8ab273b4933c08b7",
    "extract_dir": "Jabref",

Fully working manifest:
7zip is just for speedup and to not handle reanme the HTML to .zip to comfort Microsoft expand utility
{
    "version": "5.0",
    "description": "",
    "homepage": "http://www.jabref.org/",
    "license": "MIT",
    "url": "https://www.fosshub.com/JabRef.html?dwl=JabRef-5.0-portable_windows.zip",
    "hash": "4f410840f7821e25a09a5d1fa6408045df27bc4bcd8684fd8ab273b4933c08b7",
    "installer": {
        "script": "Expand-7ZipArchive \"$dir\\$fname\" -ExtractDir 'Jabref' -Removal"
    },
    "bin": "JabRef.exe",
    "shortcuts": [
        [
            "JabRef.exe",
            "JabRef"
        ]
    ],
    "checkver": {
        "github": "https://github.com/JabRef/jabref"
    },
    "autoupdate": {
        "url": "https://www.fosshub.com/JabRef.html?dwl=JabRef-$version-portable_windows.zip"
    }
}

Thanks for the working manifest but the main reason for the question was if this behaviour is intended or not, in the second case the code needs a little tweaking. The reason is I can't judge how many other manifest are affected by such a change in the code.


Carbide Feature Declaration

To enable a new feature in Carbide, I should standardize and implement features similar to:
--#FEATURE Carbide.BitOp
print(8 >> 1)

This has been implemented with the 'CARBIDE_EXTENSIONS' directive.


increment versions

@mparent61

LGTM (once Py 3.4 fixed)

that failure is nonsense

(the newer one)


Update Deprecated Functions

Your minimal.lua config
.
Error messages
No response
Log output
.
Health check output
No response
Describe the bug
From the Neovim documentation (doc/deprecated.txt):
DEPRECATED IN 0.10 *deprecated-0.10*
...
• |API| functions:
  - ...
  - *nvim_buf_set_option()*   Use |nvim_set_option_value()| instead.
  - ...

• Lua stdlib:
  - ...
  - *vim.tbl_islist()*   Use |vim.islist()| instead.

These two deprecated functions are currently used in the codecompanion.nvim codebase. To ensure compatibility with future versions of Neovim, it would be best to update to the suggested alternatives.
Reproduce the bug
No response
Final checks

[X] I have made sure this issue exists in the latest version of the plugin
[X] I have tested with the minimal.lua file from above and have shared this
[X] I have shared the contents of the log file

Btw...did you get any notifications about the nvim_buf_set_option() deprecation? I somehow missed it.

Yes

I'm using LazyVim. It make use of lazydev.nvim. I'm not sure but I think that these LSP diagnostic are from LuaLS set up by lazydev


Missing method

Hi there!
There's an issue with the getModel call:
https://github.com/Adldap2/Adldap2-Laravel/pull/287#issuecomment-334532362
(referenced in another package hence the link)
Just an FYI...

Yes - this package is only tested and working with EloquentUserProvider.


SF: Delegate Vanilla registry population to Forge delegates

The purpose of this PR is to fix registries on the SpongeForge side. With SpongeVanilla, we were successfully injecting and registering our own cache. With SpongeForge, Forge jumped in the middle, and expanded upon the vanilla registry system Sponge expected by creating two new registry types: NamespacedWrapper and NamespacedDefaultedWrapper.
Both of these follow the MappingRegistry chain, and were receiving the expected mixin changes. However, the problem with registry registration was that Forge didn't actually write registry contents to these wrappers, but to a ForgeRegistry serving as a delegate to these wrappers. These calls were not tracked, so to Sponge, no registry contents existed.
This set of mixins fixes the issue by registering the wrapper registry as a parent to the ForgeRegistry. This has been tested via debug and against a modded environment, both producing filled registries.
As for prefixes, I took a best guess but perhaps we will want them named differently.

Following the feedback, I've gone ahead and applied a general set of changes. Rather than attempt to set the parent each registration call if none had been set, this new solution only ever tries to append a parent at time of actual forge parent registration. I originally considered just using a Set of RegistryBridges, but figured it would be additionally smart (for debugging purposes) to have a ResourceKey mapped to that bridge for variable evaluation, and given it's available in forge's slave map.
As for the other questions, at present, it looks like every ForgeRegistry simply has 1 parent, and I logged no cases where that number was higher or 0. I've added logging in the case of a registry with no parent established, which will only ever fire once if detected. And if there ever is a scenario where more than one parent exists, the code will now register to each registry it has established as a parent of itself.


parse error on input ‘-- * 'LHsDecl'

I got this error while compiling
[237 of 264] Compiling GHC.Parser.PostProcess.Haddock ( compiler/GHC/Parser/PostProcess/Haddock.hs, dist/build/GHC/Parser/PostProcess/Haddock.o, dist/build/GHC/Parser/PostProcess/Haddock.dyn_o )
compiler/GHC/Parser/PostProcess/Haddock.hs:1469:3: error:
parse error on input ‘-- * 'LHsDecl' produced by 'decl_cls' in Parser.y always have a 'BufSpan'’
|
1469 |   -- * 'LHsDecl' produced by 'decl_cls' in Parser.y always have a 'BufSpan'
|   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
cabal: Failed to build ghc-lib-parser-<IP_ADDRESS>10207 (which is required by
exe:hlint from hlint-3.3).

This is ghc-lib-parser build failure. This issue should be moved there. Would be helpful if you could provide the version of ghc you are building with please?

It's not making a lot of sense. It has literally tripped up on a comment line. If your build compiler was 8.6.5 we'd have expected an earlier failure with a different message.
Interestingly, the comment has a * in it; this has been replaced on HEAD with -.
Before:
  -- * 'LHsDecl' produced by 'decl_cls' in Parser.y always have a 'BufSpan'
  -- * 'partitionBindsAndSigs' does not discard this 'BufSpan'

After:
  -- - 'LHsDecl' produced by 'decl_cls' in Parser.y always have a 'BufSpan'
  -- - 'partitionBindsAndSigs' does not discard this 'BufSpan'

One assumes there is therefore something dodgy about it then.

GHC version 8.10.4
cabal-install version <IP_ADDRESS>
compiled using version <IP_ADDRESS> of the Cabal library
I m running Arch Linux.
I've understood that the problem was related with ghc-lib-parser (i believed it was due to ghc-lib-parser-ex) but was not sure were to report the issue

I'm really sorry you're having this problem! Unfortunately, I am struggling to get it reproduced.
❯ cabal --version
cabal-install version <IP_ADDRESS>
compiled using version <IP_ADDRESS> of the Cabal library
❯ which ghc
/Users/shaynefletcher/ghc-8.10.4/bin/ghc
❯ cabal new-install hlint-3.3
Resolving dependencies...
Build profile: -w ghc-8.10.4 -O1
In order, the following will be built (use -v for more details):
 - base-compat-0.11.2 (lib) (requires build)
...
Starting     ghc-lib-parser-<IP_ADDRESS>10207 (lib)
...
Installing   ghc-lib-parser-<IP_ADDRESS>10207 (lib)
Completed    ghc-lib-parser-<IP_ADDRESS>10207 (lib)
...
Building     hlint-3.3 (exe:hlint)
Installing   hlint-3.3 (exe:hlint)
Completed    hlint-3.3 (exe:hlint)

I have an idea for fixing this despite being unable to reproduce it. If someone could tell me if this script works?
#!/usr/bin/env bash

ghc_lib_parser=ghc-lib-parser-<IP_ADDRESS>10207
curl -o ${ghc_lib_parser}.tar.gz https://hackage.haskell.org/package/${ghc_lib_parser}/${ghc_lib_parser}.tar.gz
gunzip ${ghc_lib_parser}.tar.gz && tar xvf ${ghc_lib_parser}.tar
cd ${ghc_lib_parser}
#I'm on macOS which wants -i to take an extension argument, hence the ''
sed -i '' -e 's/-- \*/-- -/g' compiler/GHC/Parser/PostProcess/Haddock.hs # Fix the pesky comments in this file
cabal new-build

If it does, I'll release a patched version of ghc-lib-parser and we should be on our way.

I have an idea for fixing this despite being unable to reproduce it. If someone could tell me if this script works?
#!/usr/bin/env bash

ghc_lib_parser=ghc-lib-parser-<IP_ADDRESS>10207
curl -o ${ghc_lib_parser}.tar.gz https://hackage.haskell.org/package/${ghc_lib_parser}/${ghc_lib_parser}.tar.gz
gunzip ${ghc_lib_parser}.tar.gz && tar xvf ${ghc_lib_parser}.tar
cd ${ghc_lib_parser}
#I'm on macOS which wants -i to take an extension argument, hence the ''
sed -i '' -e 's/-- \*/-- -/g' compiler/GHC/Parser/PostProcess/Haddock.hs # Fix the pesky comments in this file
cabal new-build

If it does, I'll release a patched version of ghc-lib-parser and we should be on our way.

@Kleidukos tested this for us and found it worked. I'm preparing a new ghc-lib-parser release that incorporates the patch.

ghc-lib-parser-<IP_ADDRESS>10324 is now on hackage

@CantoroMC cabal update&&cabal install should solve the problem. do please let us know how it works out!

works pretty pretty good

nice 🎉 !

Thanks @shayne-fletcher for fixing the bugs! I assume this issue can now be closed, but reopen if not.


Add Backpropagation step

One hot-encode rank
Scale the data
Add the backpropagation step function

Though we are a little delayed in responding, this PR contains your personal work that cannot be added to Udacity's repository (starter-code).


refactor(prettier): impl Display for Doc

Current dependencies on/for this PR:

main

PR #1401   👈

This stack of pull requests is managed by Graphite.

Merge activity

Nov 17, 10:17 PM: @Boshen merged this pull request with Graphite.


fix: externalized error message and toggle developer tools (#734)

Summary
Fix #734
Suggestion from jbodart-argenx: https://github.com/sassoftware/vscode-sas-extension/issues/685#issuecomment-1849425397

Externalized error message 'There was an error executing the SAS Program. See [console log] for more details.'
The 'console log' in the show error message dialog should be a link to open the developer tools.

Testing

Change the language to zh-cn to check if the error message is change to Chinese.
Click the hyper link [console log] to see if the developer tools is opened.

The connection error message has been externalized as expected. Click link 'console log' will fire command:workbench.action.toggleDevTools.


403 Forbidden when fetching packages

Hi, I'm in the process of installing Riak on Ubuntu 13.10.  Thus, I have performed the following steps:
$ sudo bash -c "echo deb http://apt.basho.com $(lsb_release -sc) main > /etc/apt/sources.list.d/basho.list"
$ sudo apt-get update

Here's a brief summary of the output:
Err http://apt.basho.com saucy/main amd64 Packages
  403  Forbidden
Err http://apt.basho.com saucy/main i386 Packages
  403  Forbidden

W: Failed to fetch http://apt.basho.com/dists/saucy/main/binary-amd64/Packages  403  Forbidden

W: Failed to fetch http://apt.basho.com/dists/saucy/main/binary-i386/Packages  403  Forbidden

E: Some index files failed to download. They have been ignored, or old ones used instead.

I am experiencing similar issue when I try to install Riak.
I am using: Ubuntu 14.04.2 LTS
Here is the sequence of commands that I have executed:
curl http://apt.basho.com/gpg/basho.apt.key | sudo apt-key add -
sudo bash -c "echo deb http://apt.basho.com $(lsb_release -sc) main > /etc/apt/sources.list.d/basho.list"
sudo apt-get update

Update gives me the following error:
Failed to fetch http://apt.basho.com/dists/trusty/main/binary-amd64/Packages  403  Forbidden

Thank in advance!


improve about section

Current: Repository of open source content on opentelemetry looks vague.

@zriyansh What would be a better wording?


Remove eslint style rule that typically just gets suppressed.

Description
Disables a subjective eslint rule that we mostly suppressed anyway. @alwayshooin since you were not able to make the Thursday meeting you have veto power. 🙂
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
yarn lint to show no errors with this rule disabled and the suppression comments removed

/retest

/retest


Revert "Unbreak non darwin unified builds"

The change in #746 is not correct. The goal is to use the in-tree dsymutil, which on swift-llvm still has the llvm-prefix. This reverts Dave's change and renames the dependency instead.

@swift-ci please test

Unless I'm missing something, this pull request only appears to revert #746. Where/what is the change that "renames the dependency instead"?

It's not you, it's me. I was looking at Github's revert feature in the web interface but decided to just do it manually. When I came back to the repo the "create PR" suggested Github's branch instead of mine (https://github.com/apple/swift-lldb/tree/revert-746-unbreak_non_darwin_unified_builds). Anyway, I pushed that commit to this branch.

@swift-ci please test

PS – Reverts (and cherry-picks and rebases) aren't formally tracked in the commit schema, therefore I wouldn't go out of my way to use use git revert or whatever GitHub provides. As far as git is concerned, you could be using the classic diff ... | patch -R ... approach for the revert.

Yeah, you're totally right. It was mostly out of curiosity, but once again I would've been better of using my regular workflow... :-)

Go ahead.


Optimize generating new dataset when have existing one

I am not familiar with python so thats why I create this issue.
Would be great to check time of last entity in dataset and parse data from that date, because if needed to update dataset it parse whole bunch of data from start of war. For now it takes a while, in future it can get really much time.

Hello,
I thought about this idea a while ago. The main issue that current datasets doesn't include sirens which were started and still not disabled, so we can't use any max(max(started_at for each record), max(completed_at for each record)) date as initial time for next sync.
One of solutions is to create one more file with current air raid siren records and manage them, another one is to implement (+edit) records when some siren was completed.
I'll probably implement the first solution in the next week, but I can't guarantee that :)
Thank you for this idea! 🇺🇦


Fixing an issue with missing variables.

Kubespray is not working well with weave network.
Full description of the problem is here: https://github.com/kubernetes-incubator/kubespray/issues/2136

thank you for your contribution.
it has been merged via #2259.
To continue to contribute you'll have to sign the CLA.


Use different await! macro between async and async_move

Fixes #924, moves to using a safer stack pinned API for polling StableFutures inside #[async] functions, and polls via the Future trait inside #[async_move] functions (so you need to PinBox any StableFutures you are awaiting there).
I'm not certain this is the best solution, but after actually implementing it it seems reasonable to me.
@cramertj I believe you had some reservations about this stack pinning API? Doing a closure based API here is difficult since you can't yield through the closure, I think it should be possible with a couple of layers of extra generators, but I wasn't able to get the lifetimes working out on my first attempt.
r? @withoutboats

Yes, I have different thoughts about how the stack-pinning API should work, but for now it seems fine to do what you did or just use new_unchecked.


Mobile support

Tested this in mobile and seems like there is no support for it on mobile?
Is that right? or maybe there is something I am missing?

Hi, this should work just the same on mobile - what exact browser (and OS) are you using?
It might be that your browser requires a polyfill for IntersectionObserver, please see:
https://github.com/snipsco/react-inview-monitor#support

Ah i see.
totally missed that part. I ended up solving my issue with another library
as I needed a quick turnaround.
On Wed, May 30, 2018 at 9:28 AM, Jonas Ohlsson Aden <
<EMAIL_ADDRESS>wrote:

Hi, this should work just the same on mobile - what exact browser (and OS)
are you using?
It might be that your browser requires a polyfill for
IntersectionObserver, please see:
https://github.com/snipsco/react-inview-monitor#support
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snipsco/react-inview-monitor/issues/8#issuecomment-393161227,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlR6RCiy6u6IaUIjST11LdTXdOug_-Htks5t3p5ggaJpZM4USH05
.

It's super quick to add the polyfill script for IntersectionObserver, in case you want to try again in the future!

i wish i would ve known this at that time
On Wed, May 30, 2018 at 9:40 AM, Jonas Ohlsson Aden <
<EMAIL_ADDRESS>wrote:

Closed #8 https://github.com/snipsco/react-inview-monitor/issues/8.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snipsco/react-inview-monitor/issues/8#event-1653580204,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlR6RCl3VAN1VFIWu69EguV44AFrweA2ks5t3qFVgaJpZM4USH05
.

That's interesting. What browsers were you trying, on what kind of phone? And what kind of test were you performing?

Tried it on safari and chrome via iPhone.
Simply tried the onInView func and it would not run at all.
Sent from my iPhone

On May 30, 2018, at 11:29 AM, Jonas Ohlsson Aden<EMAIL_ADDRESS>wrote:
That's interesting. What browsers were you trying, on what kind of phone? And what kind of test were you performing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

so the demo page shows all elements on the page with no transitions or
fade? is that the expected behavior?
On Thu, May 31, 2018 at 5:25 AM, Jonas Ohlsson Aden <
<EMAIL_ADDRESS>wrote:

Did you try the demo page on your phone?
https://snipsco.github.io/react-inview-monitor/
If that page works for you, then there's something wrong in your
implementation. If it does not, then I will debug further what's going
wrong!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snipsco/react-inview-monitor/issues/8#issuecomment-393471182,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlR6RLZ1ftQwOG0HjtBrxcepVXJRYSrdks5t37cEgaJpZM4USH05
.

No, it sounds like it is not working for you. The video at the bottom never starts playing either?
What version of Safari do you have on your iPhone?

v 11.3.1
No video as well on the demo page!
On Thu, May 31, 2018 at 10:58 AM, Jonas Ohlsson Aden <
<EMAIL_ADDRESS>wrote:

No, it sounds like it is not working for you. The video at the bottom
never starts playing either?
What version of Safari do you have on your iPhone?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/snipsco/react-inview-monitor/issues/8#issuecomment-393558892,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AlR6RNMKYO8oAUhDjoxO52BTNTe1NWioks5t4AUYgaJpZM4USH05
.

So found a few things:

this library itself was not broken, however:
the IntersectionObserver polyfill requires setting height: 100% on html+body to work correctly in Safari; this was what the examples missed and why they were not working (animating etc) in Safari.
@AISG-NYC Can you test the examples again and confirm they work for you? This means that you can use this library, but you do need to use the Polyfill, and you need to apply the height change in your css. I'm now mentioning this in the README as well.

Finally, there seems to be a separate problem with the video on in the examples, for some reason it's not showing at all in mobile Safari. I'll debug that separately.

We r in business !!
Thanks for the fix mate!
Sent from my iPhone

On Jun 1, 2018, at 1:10 PM, Jonas Ohlsson Aden<EMAIL_ADDRESS>wrote:
So found a few things:
this library itself was not broken, however:
the IntersectionObserver polyfill requires setting height: 100% on html+body to work correctly in Safari; this was what the examples missed and why they were not working (animating etc) in Safari.
@AISG-NYC Can you test the examples again and confirm they work for you? This means that you can use this library, but you do need to use the Polyfill, and you need to apply the height change in your css. I'm now mentioning this in the README as well.
Finally, there seems to be a separate problem with the video on in the examples, for some reason it's not showing at all in mobile Safari. I'll debug that separately.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Look into leveraging vscode.env.shell in remote workspaces

Currently the SSH support works by ignoring which shell you selected and opening the host with the default shell. Perhaps instead we should pull vscode.env.shell which should be the default remote shell and make that the default and potentially remove the other options?
FYI @ricardosantos9521

Yes Windows terminal is using the default shell which can be a problem sometimes. Disabling selection would be the best scenario. We should try to use vscode.env.shell as the default windows terminal shell if we can else try to use the default.
In the remote we should use vscode.env.shell if the remote is windows otherwise use we should use what we have already implemented.
Can we get the default shell of the remote workspace through vscode api when we are a ui extension?

Can we get the default shell of the remote workspace through vscode api when we are a ui extension?

Yep, that's what vscode.env.shell will do. It is not possible to pull /etc/shells with SSH though without making our own connection, we could possibly do it if the SSH extension wanted to expose an API to do it. Maybe we should implement the remote shell detection in WSL first and if it works nicely explore options for SSH?

vscode.env.shell returns always the terminal.integrated.shell.windows so i think we should use terminal.integrated.shell.windows and terminal.integrated.shell.linux as shells for
wsl and ssh


how to enable user pass for OBS?

Hi dear!
I need to set a user pass for my specific stream key to restrict others to access my stream key.
How can I enable authorization??

Hello @siavashfazli ,
I think stream auth doesn't come natively with rtmp module. It requires an additional package to do it. I never used it myself but here are some packages that can be added to do the job:

https://github.com/Nesseref/nginx-rtmp-auth
https://github.com/voc/rtmp-auth

@TareqAlqutami Thank you, I'll check them.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/66920

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67065

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67240

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/68919

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.


DBZ-4014 Warns users not to modify database.server.name

DBZ-4014
Adds admonition to description of database.server.name property for all connectors, warning users that changing the value disrupts connector operations.
Tested in local Antora build.
Need clarification of whether property is intentionally omitted for MongoDB connector.

One comment inline. Same note should be added to "mongodb.name".


Are all scripts used for analyses in the manuscript up-to-date?

ask @benjaminrisk to update his code contributions

need to add:

FisherTestsRaceAndSex.R
QC_Impacts_Analysis_RtoR_comparetosimulateddata.R
QC_Impacts_Analysis_singleseed_noimpute_cb.R

need to update:

QC_Impacts_Plots_PropensitiesOutcome.R - use #' before lines you want to print as normal text in .html
QC_Impacts_DRTMLE_Table_CirclePlotsWhiteBG.Rmd - use knitr::spin to run #1

9ee2cc1d9a5527eae6b8cf404cb0ac1c8c5f0edb : @BenjaminRisk edited QC_Impacts_Analysis_singleseed_cb.R to remove motor overflow imputation.
ReviewerResponse/QC_Impacts_Analysis_singleseed_noimpute_cb.R is now obsolete

34dd4b6b534e4e4936070ec0ae99dbdbb7c604e4: created Run_DRTMLE_ToyAndApplication_Analyses.Rmd to run analyses in sections 2.3.2 and 2.3.3 of the manuscript


dateutil: No module named 'dateutil'

Hi,
I am trying to use fastcoref library but I got the following error as soon as I write from fastcoref import FCoref.
The error is:
ImportError: Unable to import required dependencies: dateutil: No module named 'dateutil'
I am running on Windows in a poetry environment with python 3.8 with no GPU. I tried installing pip install python-dateutil with no success as nothing changed.
Any help would be much appreciated, I can provide more information like the stack trace if needed.
Thanks in advance!

Hello,
I don't know exactly what is your installed packages in the environment. You can create new environment with venv or conda and then install fastcoref ?

Sorry if I did not tried it first, it seems to work as expected, so guess it is a compatibility problem with my environment. I'll try to figure it out then, but just in case there is a chance you can help me spotting the problem I attach here my environment infos and package installed. Thank you very much !
  $ poetry env info
  Virtualenv
  Python:         3.8.10
  Implementation: CPython
  Path:           C:\Users\myUser\Documents\Source\g-core\.venv
  Executable:     C:\Users\myUser\Documents\Source\g-core\.venv\Scripts\python.exe
  Valid:          True

  System
  Platform:   win32
  OS:         nt
  Python:     3.8.10
  Path:       c:\python38
  Executable: c:\python38\python.exe

  $ pip install fastcoref
  WARNING: Ignoring invalid distribution -yrsistent (c:\users\myUser\documents\source\g-core\.venv\lib\site-packages)
  WARNING: Ignoring invalid distribution -yrsistent (c:\users\myUser\documents\source\g-core\.venv\lib\site-packages)
  Requirement already satisfied: fastcoref in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (2.1.1)
  Requirement already satisfied: torch>=1.10.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (1.12.1)
  Requirement already satisfied: transformers>=4.11.3 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (4.25.1)
  Requirement already satisfied: numpy>=1.21.6 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (1.23.5)
  Requirement already satisfied: datasets>=2.5.2 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (2.8.0)
  Requirement already satisfied: tqdm>=4.64.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (4.64.1)
  Requirement already satisfied: wandb>=0.13.4 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (0.13.7)
  Requirement already satisfied: spacy>=3.0.6 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (3.4.4)
  Requirement already satisfied: scipy>=1.7.3 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from fastcoref) (1.10.0)
  Requirement already satisfied: dill<0.3.7 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (0.3.6)
  Requirement already satisfied: pyyaml>=5.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (6.0)
  Requirement already satisfied: multiprocess in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (0.70.14)
  Requirement already satisfied: requests>=2.19.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (2.28.1)
  Requirement already satisfied: aiohttp in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (3.8.3)
  Requirement already satisfied: packaging in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (23.0)
  Requirement already satisfied: pandas in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (1.5.2)
  Requirement already satisfied: huggingface-hub<1.0.0,>=0.2.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (0.11.1)
  Requirement already satisfied: pyarrow>=6.0.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (10.0.1)
  Requirement already satisfied: fsspec[http]>=2021.11.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (2022.11.0)
  Requirement already satisfied: xxhash in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (3.2.0)
  Requirement already satisfied: responses<0.19 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from datasets>=2.5.2->fastcoref) (0.18.0)
  Requirement already satisfied: spacy-loggers<2.0.0,>=1.0.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (1.0.4)
  Requirement already satisfied: thinc<8.2.0,>=8.1.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (8.1.6)
  Requirement already satisfied: murmurhash<1.1.0,>=0.28.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (1.0.9)
  Requirement already satisfied: preshed<3.1.0,>=3.0.2 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (3.0.8)
  Requirement already satisfied: spacy-legacy<3.1.0,>=3.0.10 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (3.0.11)
  Requirement already satisfied: pydantic!=1.8,!=1.8.1,<1.11.0,>=1.7.4 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (1.10.4)
  Requirement already satisfied: jinja2 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (3.1.2)
  Requirement already satisfied: cymem<2.1.0,>=2.0.2 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (2.0.7)
  Requirement already satisfied: langcodes<4.0.0,>=3.2.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (3.3.0)
  Requirement already satisfied: setuptools in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (65.6.3)
  Requirement already satisfied: pathy>=0.3.5 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (0.10.1)
  Requirement already satisfied: wasabi<1.1.0,>=0.9.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (0.10.1)
  Requirement already satisfied: smart-open<7.0.0,>=5.2.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (6.3.0)
  Requirement already satisfied: srsly<3.0.0,>=2.4.3 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (2.4.5)
  Requirement already satisfied: typer<0.8.0,>=0.3.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (0.7.0)
  Requirement already satisfied: catalogue<2.1.0,>=2.0.6 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from spacy>=3.0.6->fastcoref) (2.0.8)
  Requirement already satisfied: typing-extensions in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from torch>=1.10.0->fastcoref) (4.4.0)
  Requirement already satisfied: colorama in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from tqdm>=4.64.0->fastcoref) (0.4.6)
  Requirement already satisfied: regex!=2019.12.17 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from transformers>=4.11.3->fastcoref) (2022.10.31)
  Requirement already satisfied: tokenizers!=0.11.3,<0.14,>=0.11.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from transformers>=4.11.3->fastcoref) (0.13.2)
  Requirement already satisfied: filelock in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from transformers>=4.11.3->fastcoref) (3.9.0)
  Requirement already satisfied: promise<3,>=2.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (2.3)
  Requirement already satisfied: GitPython>=1.0.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (3.1.30)
  Requirement already satisfied: pathtools in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (0.1.2)
  Requirement already satisfied: sentry-sdk>=1.0.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (1.12.1)
  Requirement already satisfied: setproctitle in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (1.3.2)
  Requirement already satisfied: protobuf!=4.21.0,<5,>=3.19.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (4.21.12)
  Requirement already satisfied: docker-pycreds>=0.4.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (0.4.0)
  Requirement already satisfied: Click!=8.0.0,>=7.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (8.1.3)
  Requirement already satisfied: psutil>=5.0.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (5.9.4)
  Requirement already satisfied: shortuuid>=0.5.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from wandb>=0.13.4->fastcoref) (1.0.11)
  Requirement already satisfied: six>=1.4.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from docker-pycreds>=0.4.0->wandb>=0.13.4->fastcoref) (1.16.0)
  Requirement already satisfied: charset-normalizer<3.0,>=2.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (2.1.1)
  Requirement already satisfied: multidict<7.0,>=4.5 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (6.0.4)
  Requirement already satisfied: frozenlist>=1.1.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (1.3.3)
  Requirement already satisfied: attrs>=17.3.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (22.2.0)
  Requirement already satisfied: async-timeout<5.0,>=4.0.0a3 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (4.0.2)
  Requirement already satisfied: aiosignal>=1.1.2 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (1.3.1)
  Requirement already satisfied: yarl<2.0,>=1.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from aiohttp->datasets>=2.5.2->fastcoref) (1.8.2)
  Requirement already satisfied: gitdb<5,>=4.0.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from GitPython>=1.0.0->wandb>=0.13.4->fastcoref) (4.0.10)
  Requirement already satisfied: idna<4,>=2.5 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from requests>=2.19.0->datasets>=2.5.2->fastcoref) (3.4)
  Requirement already satisfied: urllib3<1.27,>=1.21.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from requests>=2.19.0->datasets>=2.5.2->fastcoref) (1.26.13)
  Requirement already satisfied: certifi>=2017.4.17 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from requests>=2.19.0->datasets>=2.5.2->fastcoref) (2022.12.7)
  Requirement already satisfied: confection<1.0.0,>=0.0.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from thinc<8.2.0,>=8.1.0->spacy>=3.0.6->fastcoref) (0.0.3)
  Requirement already satisfied: blis<0.8.0,>=0.7.8 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from thinc<8.2.0,>=8.1.0->spacy>=3.0.6->fastcoref) (0.7.9)
  Requirement already satisfied: MarkupSafe>=2.0 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from jinja2->spacy>=3.0.6->fastcoref) (2.1.1)
  Requirement already satisfied: python-dateutil>=2.8.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from pandas->datasets>=2.5.2->fastcoref) (2.8.2)
  Requirement already satisfied: pytz>=2020.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from pandas->datasets>=2.5.2->fastcoref) (2022.7)
  Requirement already satisfied: smmap<6,>=3.0.1 in c:\users\myUser\documents\source\g-core\.venv\lib\site-packages (from gitdb<5,>=4.0.1->GitPython>=1.0.0->wandb>=0.13.4->fastcoref) (5.0.0)

Ok I'll close this issue since I found out my environment was corrupted, sorry for bother. Thank you very much for the help!


Support for Ember-Source 5

When installing this lib:
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^4.0.0".

Suggested fix for package.json:
"peerDependencies": {
   "ember-source": "^3.28.0 || ^4.0.0 || >=5.0.0"
},

Happy to accept a PR for this change! My bandwidth is pretty low right now but I'll try to get to it in the next couple months otherwise.


istioctl x uninstall not removing everything on istiodless remotes

Bug Description
When the external profile is installed using istioctl install, a subsequent istioctl x uninstall is not cleaning up properly. It is not removing the istio-sidecar-injector mutatingwebhookconfiguration and the istiod service/endpoints, and maybe other things. It seems to clean up correctly if Istio is instead installed using the default profile.
To reproduce:
cat <<EOF > cluster2.yaml
apiVersion: install.istio.io/v1alpha1
kind: IstioOperator
spec:
  profile: external
  values:
    istiodRemote:
      injectionPath: /inject/cluster/cluster2/net/network2
    global:
      remotePilotAddress: <IP_ADDRESS>
EOF
istioctl install -f cluster2.yaml

Then uninstall:
istioctl x uninstall --revision=default

If you now run kubectl get mutatingwebhookconfiguration you'll see that the istio-sidecar-injector webhook is still there.
Version
latest in master

Additional Information
No response

@litong01 That's interesting. So I guess the question is what is the correct behavior when removing --revision=default? Is that working as designed? I think not deleting the service seems wrong no matter what?

@frankbu I would think when revision (even the default get used), the installed webhooks should be removed because their back end services should have been gone, keeping the webhook there wont do anything good. Not sure why it was not. Let me dig a bit deeper and see why it does that. We have so many webhook not being removed issues.

@frankbu this is actually a bug in our uninstall code, PR is coming up soon.


hip_fp8.h doesn't exist before hip 6.2

To maintain backwards compatibility with versions of HIP prior to 6.2.

I understand this might not be the best way to fix it, specifically that I check for the existence of OCP. I'm open to suggestions.

I understand this might not be the best way to fix it, specifically that I check for the existence of OCP. I'm open to suggestions.

i have similar PR https://github.com/ROCm/hipBLASLt/pull/1072/ before. due to i'm not sure if any one use hipblaslt with rocm less than 6.2, so PR has not been merged yet.


Add parent?

I don't think these are related
FYPO:0006686 | decreased DNA double-strand break processing
FYPO:0003660 | decreased double-strand break repair during vegetative growth
could they have a common parent
decreased double-strand break repair
would that work?

i.e I did not find
FYPO:0006686 | decreased DNA double-strand break processing
under
FYPO:0003660 | decreased double-strand break repair during vegetative growth
(but I would not expect to)
anyways I didn't get to
FYPO:0006686 | decreased DNA double-strand break processing


Disable mimalloc, because we suspect it has bugs

For changelog. Remove if this is non-significant change.
Category (leave one):

Bug Fix

Short description (up to few sentences):
Disable mimalloc, because it's not usable.

Mimalloc has memory leak (aka unbounded fragmentation) + leak of memory mappings in some typical scenario.

https://github.com/microsoft/mimalloc/issues/100


Lookup for multiple parameter sets: Factor variables

Currently, we subset the table from the database to only contain values, which are identical to the user supplied parameter set (eg. replace = FALSE)
When supplying multiple parameter sets, this approach doesn't work when supplying conflicting data, because we're trying to remove all the runs with replace != FALSE and replace != TRUE.
Do you have an idea for this problem?

Should be fixed now. Merged also everything to master


.Net: Planner Prompt Examples Need To Be Customizable

Describe the bug
The examples injected into the planner prompt is negatively impacting the planners choices. We have removed the time plugin on our semantic kernel application because it was causing issues, yet the planner still selects 'TimePlugin.Time' even though it isn't listed in our list of functions.
To Reproduce
Steps to reproduce the behavior:

Remove the Time Plugin and ask time related questions.
(Example) You can remove the Time examples from the planner prompt and it will not return the time function (correctly so)

Expected behavior
The examples for the Planner Prompt should be either customizable or based off which functions you have imported. The examples sway the decision making of the LLM far too much to include functions in the examples that are not present in the actual function list.
Prompt
A planner takes a list of functions, a goal, and chooses which function to use.
For each function the list includes details about the input parameters.
[START OF EXAMPLES]
[EXAMPLE]

List of functions:
// Read a file.
FileIOPlugin.ReadAsync
Parameter "path": Source file.
// Write a file.
FileIOPlugin.WriteAsync
Parameter "path": Destination file. (default value: sample.txt)
Parameter "content": File content.
// Get the current time.
TimePlugin.Time
No parameters.
// Makes a POST request to a uri.
HttpPlugin.PostAsync
Parameter "body": The body of the request.
End list of functions.
Goal: create a file called "something.txt".
{"plan":{
"rationale": "the list contains a function that allows to create files",
"function": "FileIOPlugin.WriteAsync",
"parameters": {
"path": "something.txt",
"content": null
}}}
#END-OF-PLAN

[EXAMPLE]

List of functions:
// Get the current time.
TimePlugin.Time
No parameters.
// Write a file.
FileIOPlugin.WriteAsync
Parameter "path": Destination file. (default value: sample.txt)
Parameter "content": File content.
// Makes a POST request to a uri.
HttpPlugin.PostAsync
Parameter "body": The body of the request.
// Read a file.
FileIOPlugin.ReadAsync
Parameter "path": Source file.
End list of functions.
Goal: tell me a joke.
{"plan":{
"rationale": "the list does not contain functions to tell jokes or something funny",
"function": "",
"parameters": {
}}}
#END-OF-PLAN

Platform

OS: Windows
IDE: Visual Studio
Language: C#

Additional context
Add any other context about the problem here.

@teresaqhoang, this could be a good addition to the Handlebars planner you're creating after your finished with the MVP.

@drewbrown27 @matthewbolanos this will be customizable with the Handlebars Planner, since we have to explicitly register all operations as helpers in the Handlebars instance.
We'll only be registering kernel functions as helpers if they're explicitly registered by the users to the kernel. No plugins will be added as helpers by default.
Instead, we'll be baking in utilities and operations as default helpers that will be non-ambiguous with any registered kernel functions. You'll also have the option to opt out of registering or filtering these built-in system helpers, following the same pattern as defined by the Handlebars.Helpers library.

More work to come to filter the helpers SK is baking in as default, but you can track the work here.

You can read all about the different buckets of helpers here: https://github.com/microsoft/semantic-kernel/blob/main/docs/decisions/0023-handlebars-template-engine.md

Hey @drewbrown27, we're deprecating the older Action, Sequential, and Stepwise Planner in favor of the HandlebarsPlanner and FunctionCallingStepwisePlanner.
The HandlebarsPlanner doesn't register any plugins by default, but we do have baked in functionality that is limited to the helpers defined in KernelSystemHelpers. These are mostly utility operations that allow the planner to use loops and engineer the plan better, so it shouldn't cause conflicts.
I have a fast follow work item #3947 that will allow you to filter or omit these built-in helpers.
Try it out and re-open this issue if you're still seeing conflicts!


Remove template manual steps from docs and generalise

PR for issue #1306
What is being addressed
Remove the repetitive manual steps and generalise under the registration section
How is this addressed

Updated env files with comments from the previous env tables for each service

/test

/test

By removing the steps taht a developer has to go through - are we not making it harder to deploy as a developer? I know have to go and work out the paths and the names of the bundles. I think we are missing something that allows me to make guacamole-windows-vm and it interacts with the API. By removing this, I dont know how I would go about automating it - happy for you to close this!

The current docs are organised by role.    The manual steps were removed to avoid causing them confusion of trying to follow them.

I somewhat agree with @ross-p-smith. While this resolves the repetition in the docs, it means you have to have read all of the docs to know about manual registration. Couldn't we have left a link to Manual Deployment in each of these templates?

/test

/test-destroy-env

/test-force-approve


Decide which documentation sets will exist as structured content

This issue is part of https://github.com/mdn/sprints/issues/1787.
For the purposes of this issue a "documentation set" is a single collection of docs on a particular technology. For example, our CSS reference docs is a documentation set.
In stumptown we will include many of the documentation sets from MDN of course - JS, CSS, HTML. We will also not include some - XPCOM, XUL, Tools. And there are some which are possibly debatable.
In this issue we will make an initial determination of which documentation sets will be supported as structured content in stumptown, and which will not. This isn't a definite choice to exclude some doc sets, it's just to help us understand how many different page types we will need to support.

AC:

we have a list of all the doc sets we need to handle in stumptown, reviewed and approved by content lead( @chrisdavidmills ) and/or product manager (@atopal ).

This is done: https://docs.google.com/document/d/1NqccmJhA3j9Yxg85gG8FFcHX8vF-HWqjVM45IcC4QJM/edit#, and reviewed by @chrisdavidmills .


Prevent FD leakage when calling fork(2)+exec(2)

I couldn't think of a better way to test this behavior, but I'm open to suggestions.
This should resolve #555.

Does this fix resolve a leaking file descriptor issue, or just test for it?
I'm tracking down an issue with redis (every so often, my client can't connect to redis for long periods).
I was worried that redis was leaking connections, perhaps this is the case. I've shut down all the redis client process on a client host, yet when I run lsof, I see many open files (>15) to the client host.
    "COMMAND": "redis-ser",
    "DEVICE": "143909",
    "FD": "43u",
    "NAME": "redis.mycompany.com:6379->client.mycompany.com:34660",
    "NODE": "TCP",
    "PID": "869",
    "SIZE/OFF": "0t0",
    "STATUS": "(ESTABLISHED)",
    "TYPE": "IPv4",
    "USER": "redis"

In total ~100 open files (including connections to other machines. Not sure if this the cause of my socket problem -- although it could be if redis also enforces a #sockets cap per client (and fails to release dead connections).

I'll merge the commits and rework the logic to use redisConnectWithOptions


Fixed #120 : App not getting media and communicatoin and healthcare p…

…rojects

I am not sure if it will be a conflict with locale app and the retrieval of translations that we have put there? Because this PR will change media_comunication to media-and-communication? @Ozcino


can't reboot into code in RAM with watchdog_reboot()

I got my code running from RAM. But I cannot reboot into RAM inside the code running from RAM. Is this a bug? Or me using the sdk wrong?
I have asked the same question, other user seem to have the same problem: link
Here is the code I use, I can see with gdb the 4 watchdog scratch reg are set to correct values
            const auto dummy = save_and_disable_interrupts();
            (void)dummy;

            watchdog_reboot(0x2000'0000, 0x2004'2000, 0);
            while (1);

Also trying using my beginner level asm to setup the pc and sp to the correct addr, still doesn't work.
    // put pc on r0
    asm volatile("mov r0, #0x20");
    asm volatile("lsl r0, #0x18");
    asm volatile("add r0, #0x01");

    // put sp on r1
    asm volatile("mov r1, #0x20");
    asm volatile("lsl r1, #0x08");
    asm volatile("add r1, #0x04");
    asm volatile("lsl r1, #0x08");
    asm volatile("add r1, #0x1f"); // or 0x20
    asm volatile("lsl r1, #0x08");

    asm volatile("msr msp, r1");
    asm volatile("blx r0");

Here is my stack trace with my assembly code:
Resetting target with halt
Successfully halted device on reset
--Type <RET> for more, q to quit, c to continue without paging--
0x40004000:     0x00000000
0xe000e010:     0x00000000
0xe000e180:     0x00000000
0xe000e280:     0x00018000
(gdb) c
Continuing.

Program received signal SIGSEGV, Segmentation fault.
isr_hardfault () at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_standard_link/crt0.S:98
98      decl_isr_bkpt isr_hardfault
(gdb) bt
#0  isr_hardfault () at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_standard_link/crt0.S:98
#1  <signal handler called>
#2  0x00000000 in ?? ()
#3  0x200036b4 in __aeabi_double_init () at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_double/double_init_rom.c:51
#4  0x20001d38 in runtime_init () at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_runtime/runtime.c:105
#5  0x20000028 in platform_entry () at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_standard_link/crt0.S:258
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) p/a *(uint32_t[8] *)$msp
$1 = {0x20005280 <sd_table>, 0x24c, 0x80, 0x0, 0x34000040, 0x200036b5 <__aeabi_double_init+88>, 0x0, 0x20000000 <_entry_point>}
(gdb)

Here is the point to enter the rom functions and envently hit the hardfault:
(gdb) c
Continuing.
warning: Breakpoint 1 address previously adjusted from 0x200036b5 to 0x200036b4.

Breakpoint 1, __aeabi_double_init () at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_double/double_init_rom.c:52
52              if (rom_version == 2) {
(gdb) s
64          if (rom_version < 3) {
(gdb) s
69          sf_clz_func = rom_func_lookup(ROM_FUNC_CLZ32);
(gdb) s
rom_func_lookup (code=code@entry=13132) at /home/jms/projects/id_6045_pico/pico-sdk/src/rp2_common/pico_bootrom/bootrom.c:12
12          return rom_func_lookup_inline(code);

@jmswu How are you building you RAM image please?  Please could you share your linker file?
And, how are you loading that image into RAM?
I'm also wondering where the Arm's VTOR register gets set-up.  That must point to the start of the image's vector table before any interrupts are used.  I will look.
Thanks.

Hi @andygpz11 I am building my code as per pico-sdk instruction, I add set(PICO_NO_FLASH ON) on the CMakeLists.txt file. I have not changed the linker script, I think with the above CMake flag. I should be suing this linker script from the pico-sdk
./pico-sdk/src/rp2_common/pico_standard_link/memmap_no_flash.ld
On my application, host MCU connect to the rp2040's SWD pins. My host MCU then act as CMSISI-DAP and load the firmware into the rp2040 every boot. Here is how my main MCU load the code:

Set the DEMCR.VC_CORERESET to halt the rp2040 on reset
Request reset by setting this bit AIRCR.SYSRESETREQ with the correcet key
Load firmware into RAM
Set up VTOR, SP and PC
Enable core and exit bug mode by setting DHCSR reg
My code then will run from this point.

When debugging, I am using GDB to load the .elf file with the load command. Here is how I do it:

start gdb with the .elf file
load these GDB command:

monitor reset halt
load
monitor reset halt
set $lr = 0x20000001
set $pc = 0x20000001
set $msp = 0x20041f00 // or 0x20004200
set $psp = 0x20041f00 // or 0x20004200
set $sp = 0x20041f00 // or 0x20004200

set breakpoint and run

I do find using gdb is not as reliable as using my host MCU's CMSIS-DAP interface, or the picotool over usb.
Per VTOR for rp2040 compile for RAM, the VTOR is at 0x2000'0100. It seem that the there is some bootcode running before hitting the reset vector, here is my disassembled code:
...
20000100 <__VECTOR_TABLE>:
20000100:	20042000 	.word	0x20042000
20000104:	2000000f 	.word	0x2000000f
20000108:	200001c3 	.word	0x200001c3
2000010c:	200001c5 	.word	0x200001c5
20000110:	200001c1 	.word	0x200001c1
20000114:	200001c1 	.word	0x200001c1
20000118:	200001c1 	.word	0x200001c1
2000011c:	200001c1 	.word	0x200001c1
20000120:	200001c1 	.word	0x200001c1
...

My pico-sdk is:
pico-sdk git:(05d41fd) git status
HEAD detached from 1.5.1

Compiler version:
arm-none-eabi-c++ --version
arm-none-eabi-c++ (15:9-2019-q4-0ubuntu1) 9.2.1 20191025 (release) [ARM/arm-9-branch revision 277599]

I was able to reproduce this problem in the debugger and put what I learned in the original forum post here: https://forums.raspberrypi.com/viewtopic.php?t=359490#p2157263
The Boot ROM does appear to try and do the right thing and start executing the code in RAM by setting the PC and SP to the correct values but it triggers a hard fault as soon as it tries to execute the first instruction from RAM. I see there is code in the Boot ROM, enable_clocks, to re-enables the clocks for WDT reboots. Even though enable_clocks is executed before check_wdog maybe the clock for SRAM0 hasn't stabilized yet and leads to this hard fault?

This bypasses the entry point right?

What is the use case for this?

@daveythacher So my app running in the RAM can quickly reboot without reloading

Sorry press the wrong button and close this accidentally.

What causes it to need to reboot?

When I call the watchdog_reboot() api, what are you trying to get to?Sent from my iPhoneOn 19/11/2023, at 1:29 PM, David Thacher @.***> wrote:
What causes it to need to reboot?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

@jmswu I think your problem is that running object code copied to RAM by a Pico-SDK program resident in Flash is not the same as building an image specifically to be located to RAM.
It might sound like the same thing but I believe that the CRT code that initialises the  .data section of the program to be run does not itself get copied to RAM.
So SDK built code can run be from RAM once but it cannot be successfully _re-_run in RAM. because it is not actually complete.
I'm not quite sure what this RAM re-boot buys you anyway?

@andygpz11 Thanks for the reply. What is the best way to fix this? If I understand correctly, I could build the image as normal (not setting set(PICO_NO_FLASH ON) ), but change the linker script to put the code into the RAM region, so I will have a full image, do you think this will work?

All it takes is one bad write and this is done for.
Overall I would ask documentation to clarify the nature of watchdog_reboot's intended purpose. I do not believe this request is consistent with this. I have seen this a few times on the forums.

Closing this in favor of the forum thread; if there is a specific issue/bug then please re-open a new issue


2.0 beta fixes - minio and harbor

I wonder if we even need a table of contents anymore seeing that read the docs handles it on the right panel.
Also yes, for those harbor and minio was when I just deployed everything in the default namespace


Add WebSocket support for RemoteHttpPlugin

Objective
BRP currently has a HTTP transport implementation, including watching requests using SSE (server-sent events).
While SSE can be great, especially when combined with HTTP/2, it has a significant limitation when used with HTTP/1.1. The browser will limit the amount of concurrent requests to a very low number.
There are other nice options today like WebTransport, but all of them (AFAIK) suffer from being limited to secure (HTTPS) connections only. Same thing applies to SSE over HTTP/2.
To keep the developer-friendly experience of not needing a certificate, while also allowing more concurrent watches, WebSocket seems like the only viable option.
Solution

Implemented WebSocket upgrades for RemoteHttpPlugin using tungstenite. This way the connection uses the same endpoint (host/port) as the HTTP requests.
Requests are sent as Text messages serialized to JSON, following the JSON RPC 2.0 format of BRP.
Responses are sent back in undefined order. The client is responsible for keeping track by using the id field in JSON RPC 2.
Batched requests work the same as with HTTP. An array can be sent in, and an array with all the responses will be sent back once they are all processed.
Watchers will keep sending responses with a matching ID.

Limitation: There is no way to cancel a watching request. With SSE this was not a problem since closing the connection worked. For a continous streaming transport like WebSocket, we need a way to unwatch requests. This is handled in #16407

Feature flagged it behind remote_websocket (non-default)
Extra: Made the dependencies used by the http feature optional and only included when the feature is enabled.

Testing

Ran the server example and used a web based tool to test both complete and watched requests, as well as batched requests.
Ran the server/client examples to ensure HTTP still works.

To test it
Run the server example with WebSocket enabled:
cargo run --example server --features remote_websocket

Follow-up
Reduce dependency footprint, potentially by:

Replacing hyper-tungstenite with custom implementation. It is a tiny library, but adds a (non-optional) tokio dependency which should not be needed.
See if the uses of futures-util can be replaced with smol alternatives.

this is a very cool feature, but the more I think about it the more I would prefer it to be a third party crate that would add different protocols: websocket, mqtt, reversed connection, ...
Bevy can't support them all builtin, it makes more sense to have a basic implementation builtin, and ensure other protocols are easy to add

While I do agree that most transports should live in third party crates, I think there should still be at least one well supported transport built in. For web browser-based tooling there are only two non-HTTPS options (as far as I can tell): HTTP and WebSocket. We have HTTP, but the connection limitation for watching requests makes it really clunky...
I really like the idea of being able to just "turn on BRP" to debug any Bevy app, and not care about whether a third party crate is compatible with the Bevy version I'm working with (could be stable, could be main, could be work on a new PR), or what the web based tool I'm using requires. The point of a built-in remote inspection/debug protocol is to not have to pull in extra crates etc IMO.
I guess one alternative could be to re-think the SSE +watch-requests a bit. Instead of one connection per request, there could be one connection to receive any +watch responses. And regular HTTP methods to subscribe/unsubscribe to them.
Another one is to simply not do web based tools. Desktop apps shouldn't have the same limitation... But it's really nice to be able to just open a web page to start inspecting 🔥 especially on mobile/tablet on the same network.
The ideal (for me) would be to be able to run any Bevy example with BRP enabled:
cargo run --example ui --features=remote

And then being able to just open a tool I didn't have to install!


Enable switching app theme based off of OS theme

This is basically just like #14064, but with the theme instead.
If you define a pair of theme names:
    "theme": { "dark": "light", "light": "dark" },

then the Terminal will use the one relevant for the current OS theme. This cooperates with #14064, who sets the scheme based on the app's theme.
This was spec'd as a part of #3327 / #12530, but never promoted to its own issue.
Gif below.

I know we need ThemePair to be class, because that's how it works, but...
I don't like it. It's a whole object for two members, something that is basically a std::pair, it gets an entire interface too and everyone got to QI it to get to the single implementor. But worst of all, it doesn't even help with reducing the amount of boilerplate code, which is what you'd at least expect (45 LOC still?).
...but I know that this is how it works and I would've written the exact same code you did. Also I learned today that the proper name for this is "false dilemma" and is probably what best describes the design decisions that now forced us to write a class with more lines of boilerplate than lines that actually use it.

storing this here because I have to keep looking it up in teams chat history


fix: get applications csv download issues

Fixed bugs to test this ticket: https://pins-ds.atlassian.net/browse/ASB-1755

Default options object parameter in getAllApplications repository
CSV 'GPS co-ordinates'  null checks LongLat value and passes default empty string

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

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


bug: Ionic 4.11.2 and React - navigation causes a stack overflow

Hi,
Since Ionic 4.11.2, there is a major issue in the navigation: navigating to a page that is already in the stack causes a stack overflow.
Below you can find a simple snipped of a crashing app...
Test: run app. Click on button 'Go to Page B'. Click on button 'Go to Page C'. Click on button 'Go to Page A'.
Expected behaviour: normal navigation works
Current behaviour: Browser crashes with
[Error] RangeError: Maximum call stack size exceeded.
removeOrphanedViews (9.chunk.js:7198)
(anonymous function) (9.chunk.js:7202)
forEach
removeOrphanedViews (9.chunk.js:7201)
(anonymous function) (9.chunk.js:7202)
forEach
removeOrphanedViews (9.chunk.js:7201)
(anonymous function) (9.chunk.js:7202)
forEach
removeOrphanedViews (9.chunk.js:7201)
...
const createPage = (title: string, next: string) : React.FC => () => (
  <IonPage>
    <IonHeader>
      <IonToolbar>
          <IonButtons slot="start">
             <IonBackButton/>
          </IonButtons>
          {title}
      </IonToolbar>
    </IonHeader>
    <IonContent>
      <IonButton routerLink={`/${next}`}>Go to page {next}</IonButton>
    </IonContent>
  </IonPage>
)

const App: React.FC = () => (
  <IonApp>
    <IonReactRouter>
        <IonRouterOutlet>
          <Route exact path="/A" component={createPage('Page A','B')}/>
          <Route exact path="/B" component={createPage('Page B','C')}/>
          <Route exact path="/C" component={createPage('Page C','A')}/>
          <Route exact path="/" render={() => <Redirect to="/A" />} />
        </IonRouterOutlet>
    </IonReactRouter>
  </IonApp>
);

Hi @marcoromag,
Thanks for the issues and for providing good test cases, they helped quite a bit in finding the bug. These are fixed in the code base and will be out in the next 4.11.3 release.


Rancher scheduler (1.2.0) unexpected behaviour

As mentioned here: https://forums.rancher.com/t/rancher-scheduler-1-2-0-unexpected-behaviour/4904
Rancher Version: 1.2.0
Docker Version: 1.2.1
OS and where are the hosts located? (cloud, bare metal, etc): ubuntu
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB) simple (single host)
Environment Type: (Cattle/Kubernetes/Swarm/Mesos) Cattle
Steps to Reproduce:
scenario 1:

1 app server, with a number of containers running on it
start a 2nd app server
delete a container (which will make rancher create another instance)

rancher creates it on the same server, even though there is a new empty app server. (it used to try and spread containers across servers, i would expect rancher 1.2 to try and spread the instances)
scenario 2 (increment on the first scenario, scheduling rules)

1 app server, with a service called vote running (5 instances)
voting service has a scheduling rule

Key: io.rancher.scheduler.affinity:container_label_soft_ne
Value: io.rancher.stack_service.name=voting/vote

start 2nd app server (+1 if it re-balanced at this point, but it did not do that before.)
delete instance(s) of the Vote service

rancher schedules the newly created instances on the same server. when scheduling the "new" (replacement) instance it does not take into account the scheduling rules.
this does not seem correct, and differs from the previous behaviour (i guess there would be some changes), however i used this to balance containers across the servers.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


Update Anypoint Security Components

Anypoint Security Edge Policies and Anypoint Security Tokenization are marked as included in US/EU Cloud, but in reality, they can only work with Runtime Fabric. It is not available for Cloudhub deployments.

Thank you, Lucas


fails creation of dataset

What version of FreeNAS are you on?  I'm currently running 11.1-U1 and I'm attempting to POST to create child dataset and it fails with 400 error (which doesn't print to the console by the way) with the following body:
{"name": ["Dataset names must begin with an alphanumeric character and may only contain \"-\", \"_\", \":\", \" \" and \".\"."]}

It seemingly doesn't like the fact that the name has a / in it.  Not sure how this is working for you unless something is off between version of the server.

I am using FreeNAS-9.10.2-U6 (561f0d7a1)

@nmaupu can you confirm if this endpoint works for you in 9.10: http://api.freenas.org/resources/storage.html#id2

This endpoint returns a 404 for me.
The following one is ok but quota (and comments) don't seem to work : http://api.freenas.org/resources/storage.html#datasets
Example:
curl -v -u root --http1.1 -X POST -H 'Content-Type: application/json' -d '{"name":"test", "quota":"100000"}' https://nas.home.fossar.net/api/v1.0/storage/volume/tank/datasets/

@nmaupu I just dropped a code dump in a MR.  Resolves all these issues for me.  I also found another fork that had some similar changes which I took into consideration.

Resolved by PR #6 . Closing.


error in echo server when they are in different ip.

hello!i meet a error.
i start the server in <IP_ADDRESS>
./_build/build/quic/samples/echo -mode=server
it output
I0402 22:29:09.309374 24507 QuicServer.cpp:218] NOT using CCP I0402 22:29:09.309646 24507 EchoServer.h:78] Echo server started at: [::1]:6666
and the i start the client in <IP_ADDRESS>
 ./_build/build/quic/samples/echo -mode=client -host=<IP_ADDRESS>
it output
I0402 22:31:28.019632 32740 EchoClient.h:131] EchoClient connecting to <IP_ADDRESS>:6666 E0402 22:31:28.156893 32740 EchoClient.h:85] EchoClient error: Connect failed; errStr=Connection refused
i had open all the port ,and i can run successfully in local,could you give me some advice how to slove it?
Thanks for your help!

From the log output, it seems the EchoServer started on IPv6 localhost, not <IP_ADDRESS>.

thanks for your help!
i don`t setting anything,so the EchoServer will default  start  in ipv6 ?

you can add -host=<IP_ADDRESS> to the server invocation

thanks,but i use ./_build/build/quic/samples/echo -mode=server -host=<IP_ADDRESS>,
it output
terminate called after throwing an instance of 'folly::AsyncSocketException'
  what():  AsyncSocketException: failed to bind the async udp socket for:<IP_ADDRESS>:6666, type = Socket not open, errno = 99 (Cannot assign requested address)
*** Aborted at<PHONE_NUMBER> (Unix time, try 'date -d @1617381693') ***
*** Signal 6 (SIGABRT) (0x1f400000a11) received by PID 2577 (pthread TID 0x7f8b888ee700) (linux TID 2578) (maybe from PID 2577, UID 500) (code: -6), stack trace: ***
(error retrieving stack trace)
Aborted (core dumped)

i don`t know the reason that cause the error.

make sure the server has that ip address configured on one of the interfaces with ifconfig -a
but since you seem to be running the client on the same host you can also use -host=<IP_ADDRESS> on both client and server

thans for your help!
i want to run  the client on the different host.
in <IP_ADDRESS>
$ ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        ether 02:42:1a:36:08:a4  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>  broadcast <IP_ADDRESS>
        inet6 fe80::5054:ff:fe11:8531  prefixlen 64  scopeid 0x20<link>
        ether 52:54:00:11:85:31  txqueuelen 1000  (Ethernet)
        RX packets 432139  bytes 69284470 (69.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 503470  bytes 250449409 (250.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet <IP_ADDRESS>  netmask <IP_ADDRESS>
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 112703  bytes 10025249 (10.0 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 112703  bytes 10025249 (10.0 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

don`t have <IP_ADDRESS>,but all of them is private ip.
 $curl ifconfig.me
<IP_ADDRESS>

it shows that my pubilc ip is <IP_ADDRESS>.

Perhaps you are behind a NAT so curling ifconfig.me is telling you an address that doesn't belong to your machine?

yes ,i am using  cloud servers ,so i behind the NET.
but i still dont know why i cant connect the echo server....
could you give me some advice?

so ,the mvfst's echo server only support in one machine or in the LAN?
it seems can't run in the different ip

Of course the server can be used across the internet.  You can only bind it to an address on your machine -- I recommend INADDR_ANY if you are unsure (<IP_ADDRESS> or ::).
Your need to point the client to an IP address that routes to this server, so if it is behind some kind of load balancer with a different IP you need to figure that out. Make sure the load balancer, etc has the UDP port for your server open.  6666 (the default) might be blocked by default.  443 is more likely to be open but you'd still need to check your load balancing configuration.


Plugin conflicts and networking issues

If C /C++ plugin is opened at the same time, alt+left click cannot exspan the node , it shows can. t resolve entry function

Only when connected to the network can the graph be displayed, otherwise it will be blank

Hi,
Thanks for bringing these issues to my attention.
Regarding the first issue with the C/C++ plugin, could you try recreating the problem in a clean environment? This would help us isolate the issue and understand if it's specific to certain configurations.
As for the second issue related to the graph not displaying without an internet connection, It's due to dependencies that the extension needs to load. I'll explore the possibility of bundling these dependencies with the extension to ensure it works seamlessly regardless of the network status.


Fix line value outside range

close https://github.com/VidocqH/lsp-lens.nvim/issues/4

the result is look like this :

I tried setting strict to false and virt_lines_above to true, but I still can't display a reference above the line when the line number is 0 or 1, maybe it's related to the neovim upstream, but this PR is better than causing an error

Thanks!


Questions: implementation of WSL 2 networking

Your Windows build number:  18945

This is more of a series of questions/discussion items than an issue - some of which may well relate to Hyper-V and network namespaces, per #4304 - but a few things have occurred to me to ask after assorted fiddling done in the wake of my network issues ( #4342 ). The whole of the thing, really, is a request for a quick outline of how networking's implemented in WSL 2, but these are some specific questions I had:

How does the WSL 2 interface get its IP address? It's not configured statically Linux-side, and it doesn't appear to be using DHCP, so where does that come from?
Could it be made to use DHCP (which also I suppose is the "why doesn't it?" question? In my flailing around with #4342 I observed that a DHCP client inside WSL 2 is perfectly capable of picking up an address, etc., if the WSL virtual switch is bridged to the external network, so it seemed a little odd that it wasn't)?

(I don't have a particular need for this ATM, but I note that in this brave new systemd world, mDNS support, et. al., is build into systemd-resolved rather than using avahi-daemon and can't be turned on except on interfaces configured by systemd-networkd, which so far as I can tell can either entirely ignore the WSL 2 eth0, or else can break it by not being able to get a DHCP IP. It can't set some settings and leave others alone.)

I'm curious as to the reasoning behind WSL 2 using a NATted network rather than just bridging to the existing external network; would appreciate any insight. Is it just as a step towards unifying the IP addresses with the Windows host?
Are there any current major barriers to IPv6 support? That's something that I couldn't get to come up even with a bridged network, which seemed curious, as I have seen it work in Hyper-V VMs before now.

Thanks in advance.

The network uses some kind of DHCP. First the Windows/Hyper-V side NIC is created with a random IPv4 address and configuration. Then

The network uses some kind of DHCP. First the Windows/Hyper-V side NIC is created with a random IPv4 address and configuration (subnet, guest IPv4, DNS, gateway). WSL side IP address is automatically added in that configuration. If WSL (aka. guest/container) is terminated the Windows side NIC remains but WSL side IPv4 address is automatically picked up from previous subnet. More network information can be found in LxssManager.dll and computenetwork.dll.


[BEAM-10884] Add support for Proto in Pubsub table provider

Added a support to read/write Row encoded as protobuf in pubsub payload

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run SQL PostCommit

Run SQL PostCommit

@TheNeuralBit Could you review this? This PR is based on the Avro one, so the only significant code is in the 2nd commit.

Will do, thank you!

I'm closing it for now. I'll come back to this PR later.


feat: add endpoint to invite users

Builds on top of https://github.com/freeCodeCamp/publish/pull/342 (please don't merge until that's in!)
The workflow this allows is

create a user via POST /api/auth/local/register
invite that user via PUT /api/auth/invitation/:id

This creates a user that can only be logged into via Auth0 and sends them an email letting them know they can log in.
To be defensive we can create the user blocked and with long random password, but the main protection is that will disable the email provider in production. It prevents email/password logins, but not registrations, so does not interfere with this workflow.

Why?
This simplifies the invitation process and decouples it from registration. We no longer need to maintain a separate content-type whose purpose was to prevent self-registration. Instead we can allow registration only by Administrators.
It also simplifies roles. When I was trying to understand how user registration worked, I was confused by what invited-user.role did and how it differed from user.role. It's not hard to understand, but it was extra complexity.

In our use case, editors are most likely to be someone from the staff team, so we wanted to simplify the roles into 2 types, Editor and Contributor.

Thanks Yoko, I'll adjust the other PRs, but this PR should be okay.

Users (both editors and contributors) will only use the Next.js app and will not use the Strapi admin panel. So we will still need the /users page (linked from "Staff" in the menu, the file is src/pages/users/index.js) and the user invitation functionality in there.

Yep, understood. I'll put it back in before I'm done updating the invitation flow.