:sparkles: Add ontology lamin upload

Fixes #270
Remaining TODOs

[x] Test thoroughly
[ ] Add script to add the new paths to the versions.yml
[ ] Use https://github.com/marketplace/actions/create-pull-request to create a PR with the changed file

The current version creates
version: 0.1.0
Species:
  ensembl:
    versions:
      release-108:
      - s3://lukas-bionty-test/OGYoEt4UwMCBisCxW7Uq
      - ''
    name: Ensembl
    website: https://www.ensembl.org/index.html
Gene:
  ensembl:
    versions:
      release-108:
      - https://ftp.ensembl.org/pub/release-108/mysql/
      - ''
      release-107:
      - https://ftp.ensembl.org/pub/release-107/mysql/
      - ''
    name: Ensembl
    website: https://www.ensembl.org/index.html
Protein:
  uniprot:
    versions:
      2022-04:
      - https://ftp.uniprot.org/pub/databases/uniprot/current_release/
      - ''
      2022-03:
      - https://ftp.uniprot.org/pub/databases/uniprot/previous_releases/release-2022_03/
      - ''
    name: Uniprot
    website: https://www.uniprot.org/
CellMarker:
  cellmarker:
    versions:
      '2.0':
      - http://bio-bigdata.hrbmu.edu.cn/CellMarker/CellMarker_download_files/file/Cell_marker_All.xlsx
      - ''
    name: CellMarker
    website: http://bio-bigdata.hrbmu.edu.cn/CellMarker/
CellLine:
  clo:
    versions:
      '2022-03-21':
      - s3://lukas-bionty-test/0hJUeKDLwaBIi3gQB4yD
      - ea58a1010b7e745702a8397a526b3a33
    name: Cell Line Ontology
    website: https://bioportal.bioontology.org/ontologies/CLO
CellType:
  cl:
    versions:
      '2023-02-15':
      - http://purl.obolibrary.org/obo/cl/releases/2023-02-15/cl-base.owl
      - 9331a6a029cb1863bd0584ab41508df7
      '2022-08-16':
      - s3://lukas-bionty-test/TD075dpP4D0xRBmwLddU
      - d0655766574e63f3fe5ed56d3c030880
    name: Cell Ontology
    website: https://obophenotype.github.io/cell-ontology/
  ca:
    versions:
      '2022-12-16':
      - https://www.ebi.ac.uk/ols/ontologies/hcao/download
      - 98ba0d340bd1b34659e8a0bdd9535127
    name: Human Cell Atlas Ontology
    website: https://github.com/HumanCellAtlas/ontology
Tissue:
  uberon:
    versions:
      '2023-02-14':
      - s3://lukas-bionty-test/gniTOWbervGMCm2ggdxI
      - 3f94e22fae4cdde88a555c5cd59c47da
      '2022-08-19':
      - http://purl.obolibrary.org/obo/uberon/releases/2022-08-19/uberon.owl
      - c7c958a1ee48fdce146f2c1763eed27e
    name: Uberon multi-species anatomy ontology
    website: http://obophenotype.github.io/uberon/
Disease:
  mondo:
    versions:
      '2023-02-06':
      - s3://lukas-bionty-test/J1j6s94asalfhOmoYFmk
      - 2b7d479d4bd02a94eab47d1c9e64c5db
      '2022-10-11':
      - http://purl.obolibrary.org/obo/mondo/releases/2022-10-11/mondo.owl
      - 04b808d05c2c2e81430b20a0e87552bb
    name: Mondo Disease Ontology
    website: https://mondo.monarchinitiative.org/
  doid:
    versions:
      '2023-01-30':
      - http://purl.obolibrary.org/obo/doid/releases/2023-01-30/doid.obo
      - 9f0c92ad2896dda82195e9226a06dc36
    name: Human Disease Ontology
    website: https://disease-ontology.org/
Readout:
  efo:
    versions:
      3.48.0:
      - http://www.ebi.ac.uk/efo/releases/v3.48.0/efo.owl
      - 3367e9a9ae3dee9113024e5108c49091
    name: The Experimental Factor Ontology
    website: https://bioportal.bioontology.org/ontologies/EFO
Phenotype:
  hp:
    versions:
      '2023-01-27':
      - s3://lukas-bionty-test/3mNyWmp5KII917J8MBzO
      - ceeb3ada771908deef620d74cd8e6b0f
    name: Human Phenotype Ontology
    website: https://hpo.jax.org/
Pathway:
  pw:
    versions:
      7-74:
      - s3://lukas-bionty-test/II07y7XuK0IfhXe5PZM2
      - a6df86616149dcdfe08fe16c900cba85
    name: Pathway Ontology
    website: https://www.ebi.ac.uk/ols/ontologies/pw

lnschema-bionty fails with
Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/lndb/dev/_setup_schema.py", line 97, in check_schema_version_and_import
    module = importlib.import_module(get_schema_module_name(schema_name))
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 984, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'lnschema_bionty'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/importlib_metadata/__init__.py", line 383, in from_name
    return next(cls.discover(name=name))
StopIteration

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/hostedtoolcache/Python/3.9.16/x64/bin/lamin", line 8, in <module>
    sys.exit(main())
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/lndb/__main__.py", line 103, in main
    result = _init_instance.init(
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/lndb/_init_instance.py", line 139, in init
    persist_settings_load_schema(isettings)
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/lndb/_init_instance.py", line 49, in persist_settings_load_schema
    load_schema(isettings)
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/lndb/dev/_setup_schema.py", line 115, in load_schema
    module = check_schema_version_and_import(schema_name)
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/lndb/dev/_setup_schema.py", line 101, in check_schema_version_and_import
    module_version = get_pip_version(get_schema_module_name(schema_name))
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/importlib_metadata/__init__.py", line 877, in version
    return distribution(distribution_name).version
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/importlib_metadata/__init__.py", line 850, in distribution
    return Distribution.from_name(distribution_name)
  File "/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/importlib_metadata/__init__.py", line 385, in from_name
    raise PackageNotFoundError(name)
importlib_metadata.PackageNotFoundError: No package metadata was found for lnschema_bionty


Add a basic clang 6 build as well

Using MPICH without Fortran (cause I can't get it to build with a mixed clang/gfortran compiler setup).

Hm, when not building Fortran bindings, I guess it's not necessary to require MPI_Fortran in CMake? Let me see if that's patchable.

bors merge


Preprocessing script error

I'm not sure how to set up the data properly in order to get the data to be preprocessed correctly.
This is the error I am receiving when running the preprocess.ipynb:
KeyError                                  Traceback (most recent call last)
Cell In[6], line 34
32 trial = os.path.splitext(forcefile)[0].split(bar)[-1]
33 motion = trial[14:-2]
---> 34 if motiontype[motion] == 'ballet_high':
35     continue
36 if participant == 's001' and motion == 'idling':
KeyError: 's001/ballethighleg'

Not sure if this's the cause, but have you checked if you're using the correct version of SMPL-X model? The third link on SMPL-X's website is the one that's built for Mosh codebase.


added a splash screen

Added a custom splash screen

@vipuluthaiah Thanks for your contribution.
Splash screen is not matching with the internal UI of application, it is not looking good right now please fix the splash screen in accordance with internal UI.

i will update it soon

updated splash screen

why did u cancle the repo?


Fix a go binding install error on windows platform

If running go generate github.com/tensorflow/tensorflow/tensorflow/go/op on windows platform, it well show

\go_path/src/github.com/tensorflow/tensorflow: warning: directory does not exist.
Cannot convert path "\go_path/src/github.com/tensorflow/tensorflow/tensorflow/core/framework/*.proto" to or from Windows style ..\genop\main.go:17: running "bash": exit status 1
..\github.com\tensorflow\tensorflow\tensorflow\go\op\generate.go:17: running "go": exit status 1

So this commit will automatically convert windows style slashes.

@googlebot I signed it!

@jhseu Can you please review this PR ? Thanks!

@jhseu/@frankchn Can you please review this PR ? Thanks!

@bbbboom Can you please check @frankchn's comments and keep us posted ? Thanks!


Outset passing arguments to scripts resulting in unexpected script argument errors

Describe the bug
Installed the new version of outset. Ran outset --login to test our login scripts.
Most scripts ran fine, but we have a script that has a specific set of optional arguments that is now failing due to being passed what looks like additional arguments.
To Reproduce
Deploy script to login-privilaged* directories (either works).
Expected behavior
Script runs as expected.
Screenshots
2023-05-10 14:07:34.638000-0700 0xca1f40   Debug       0x0                  97660  0    Outset: [io.macadmins.Outset:main] Completed task /usr/local/outset/login-privileged-every/upgradeWatcher.py with status 2
2023-05-10 14:07:34.638075-0700 0xca1f40   Debug       0x0                  97660  0    Outset: [io.macadmins.Outset:main] Task output:
2023-05-10 14:07:34.638103-0700 0xca1f40   Error       0x0                  97660  0    Outset: [io.macadmins.Outset:main] usage: upgradeWatcher.py [-h] [--testfile TESTFILE]
                         [--testosversion TESTOSVERSION]
upgradeWatcher.py: error: unrecognized arguments: mczack

System Details:

OS: macOS 12.6.5 and macOS 13.4 RC
arm64
Version 4.0.0-b2 (this looks to not have gotten updated with latest package release)

Additional context
N/A

ok - could be because all scripts get passed the current logged in user as argument 1.
Will need to think about how to manage that behaviour. is upgradeWatcher.py something that is public or can be shared?

Unfortunately, not at this point in time.

You happy to work around with the knowledge that all scripts in v4 have the console user passed in as the first script argument?
I've documented that behaviour here https://github.com/macadmins/outset/wiki/FAQ#script-processing

I think so. I think we should document and maintain a method that works in case additional variables are added :)
Shell scripts don't really care, but python and argparse can get thrown from it. Example code
import argparse
parser = argparse.ArgumentParser()
parser.add_argument("user", metavar="user", nargs=1, help="User to run against, used by outset", default=None)
args = parser.parse_args()
print(args)

> Namespace(user=['mczack'])

Updated the wiki to cover this. Resolving.


--cache-location is an unknown option

According to knip documentation --cache-location is a valid option of the CLI. Whenever I try to specify the cache option:
knip --cache --cache-location .cache/knip

I get the following error:
Unknown option '--cache-location'
│ ✂  Find unused files, dependencies and exports in your JavaScript and TypeScript projects
│ Usage: knip [options]
│ Options:
│   -c, --config [file]      Configuration file path (default: [.]knip.json[c], knip.js, knip.ts or package.json#knip)
│   -t, --tsConfig [file]    TypeScript configuration path (default: tsconfig.json)
│   --production             Analyze only production source files (e.g. no test files, devDependencies)
│   --strict                 Consider only direct dependencies of workspace (not devDependencies, not other workspaces)
│   -W, --workspace [dir]    Analyze a single workspace (default: analyze all configured workspaces)
│   --directory [dir]        Run process from a different directory (default: cwd)
│   --cache                  Enable caching
│   --cache-location         Change cache location (default: node_modules/.cache/knip)
│   --watch                  Watch mode
│   --no-gitignore           Don't use .gitignore
│   --include                Report only provided issue type(s), can be comma-separated or repeated (1)
│   --exclude                Exclude provided issue type(s) from report, can be comma-separated or repeated (1)
│   --dependencies           Shortcut for --include dependencies,unlisted,binaries,unresolved
│   --exports                Shortcut for --include exports,nsExports,classMembers,types,nsTypes,enumMembers,duplicates
│   --files                  Shortcut for --include files
│   --fix                    Fix issues
│   --fix-type               Fix only issues of type, can be comma-separated or repeated (2)
│   --allow-remove-files     Allow Knip to remove files (with --fix)
│   --include-libs           Include type definitions from dependencies (default: false; implied with classMembers)
│   --include-entry-exports  Include entry files when reporting unused exports
│   --isolate-workspaces     Isolate workspaces into separate programs
│   -n, --no-progress        Don't show dynamic progress updates (automatically enabled in CI environments)
│   --preprocessor           Preprocess the results before providing it to the reporter(s), can be repeated
│   --preprocessor-options   Pass extra options to the preprocessor (as JSON string, see --reporter-options example)
│   --reporter               Select reporter: symbols, compact, codeowners, json, can be repeated (default: symbols)
│   --reporter-options       Pass extra options to the reporter (as JSON string, see example)
│   --tags                   Include or exclude tagged exports
│   --no-config-hints        Suppress configuration hints
│   --no-exit-code           Always exit with code zero (0)
│   --max-issues             Maximum number of issues before non-zero exit code (default: 0)
│   -d, --debug              Show debug output
│   --performance            Measure count and running time of expensive functions and display stats table
│   -h, --help               Print this help text
│   -V, --version            Print version
│ (1) Issue types: files, dependencies, unlisted, unresolved, exports, nsExports, classMembers, types, nsTypes, enumMembers, duplicates
│ (2) Fixable issue types: dependencies, exports, types
│ Examples:
│ $ knip
│ $ knip --production
│ $ knip --workspace packages/client --include files,dependencies
│ $ knip -c ./config/knip.json --reporter compact
│ $ knip --reporter codeowners --reporter-options '{"path":".github/CODEOWNERS"}'
│ $ knip --tags=-knipignore
│ Website: https://knip.dev

I am using:

knip 5.12.2
on Windows 11

Thank you,
Patrick

:rocket: This issue has been resolved in v5.12.3. See Release 5.12.3 for release notes.
Using Knip in a commercial project? Please consider sponsoring me.

Thanks @patricklafrance! Should be fixed.


fix: All events should show every event instead of no events

Fixes Issue #8700

Changes proposed

Added a check that if there is no future events(which is default action), then it shows every event instead of showing No event found.

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Using `/amandamartin-dev` profile as an example. Since this profile doesn't have any future events, which was the default event type. So instead of showing no events, now it shows all events.
Note to reviewers

Can you provide some images

Yes sure, Updated above screenshot section with little description.


Skip shards in progress for temporal compaction

Commit message: "when picking shards ..."

First commit looks good

Looks good


Fix managing-your-clusters links

Signed-off-by: Kevin Cormier<EMAIL_ADDRESS>https://github.com/open-cluster-management/backlog/issues/17724

/hold

/unhold


Please rename your Image Save and Save Text File nodes

These nodes conflict with WAS Node Suite. You should be using custom_node standards and use the class name for the NODE_CLASS_MAPPINGS and a safe name for NODE_DISPLAY_NAME_MAPPINGS
WAS Node Suite was made before NODE_DISPLAY_NAME_MAPPINGS and doesn't use it. And for me to make my node suite compatible with yours, it means breaking everyone workflows back to basically the release of ComfyUI. It would make much more sense for  you to update your relatively new suite that isn't in thousands and thousands of workflows.

I will update it right now.

I put it in 5c689121534c51c650ddc244995d2d7783e2ce84


Packages without a stable release (according to semver) isn't usable

Packages without a stable release is currently not usable without specifying an explicit version number
Current behavior

The default page of jsr.io, example: https://jsr.io/@pup/pup shows nothing but "This package has not published a stable release yet.
meta.json gives 404: Example<EMAIL_ADDRESS>deno install fails: Example deno install jsr:@pup/pup gives error: Could not find constraint in the list of versions: @pup/pup

This makes pre-releasing binary packages (?) really hard, as we have to instruct the users to install specific versions like<EMAIL_ADDRESS>instead of just @pup/pup.
Expected behavior if there are no stable version available:

The latest pre-release is shown on default page of jsr.io, but with a badge "PRE-RELEASE" or similar
meta,json is generated, with an additional key "prerelease" containing the latest pre-release version (or something similar)
deno install jsr:@pup/pup installs the latest pre-release version if there are no stable.

Possible Workaround
When using a non-standard way of pre-releasing, such as giving the prerelease a semver-stable-but-possibly-not-stable version number, such as 0.0.1, everything works fine. The problem only occur when using semver pre-release identifiers.

I propose an alternative:

For non latest stable versions, the usage instructions say: deno add jsr<EMAIL_ADDRESS>On the index page, we show the latest pre-release if there are no stable versions at all.
We do not change the behaviour of deno add jsr:@pup/pup.

Has there been any discussions about tags or channels, allowing for something like deno add jsr:@pup/pup@prerelease on a per-project basis?
That would relieve the pain from having to update version numbers for every version of pre-release docs.

Agree with @Hexagon about adding a pseudo version name that will install the latest version regardless of stability, but it'd be useful if it worked everywhere, not just on a per-project basis. Other options could be @unstable or @canary:
deno add jsr:@ns/pkg@unstable

If @ns/pkg has the available versions 1.0.0, 2.0.0-rc.1, and 2.0.0-rc.2, this will install 2.0.0-rc.2. That way you don't have to manually specify the version number when upgrading to bleeding-edge versions (or when using a package that doesn't yet have a stable release).
The index page would still show the unversioned install command (if a stable version is unavailable) and the latest versioned install command (if only unstable versions are available).
Also it'd be nice if unstable releases still showed documentation like other packages. I'm not sure if the lack of docs is intended to nudge authors toward providing a stable version, but if so, there are other ways of doing that (e.g. make the "This package has not published a stable release yet" notice more prominent and with a red background). If the experience of using pre-release versions is so much worse, it'll just incentivise authors to use 0.x.x versions instead.


Close Cluster executor once the cluster is closed (TINKERPOP3-972)

Thanks for noticing this and offering a fix.  Somehow I missed closing that executor.
Looking at your PR, you do a executor().shutdownNow() in Cluster.close().  That still leaves a problem for those doing Cluster.closeAsync() as that executor will continue to hang around. Maybe your change should somehow be down here:
https://github.com/apache/incubator-tinkerpop/blob/0feaa8b47de2797e177310cd1ea3bf38d7230420/gremlin-driver/src/main/java/org/apache/tinkerpop/gremlin/driver/Cluster.java#L607
maybe you tack something on to the closeIt future to shutdown the executor after if finishes all its jobs? or maybe we don't use the executor for shutdown of the channel so that we separate that task from any other running activities?  do you have any thoughts on how best to do this?

Thanks for the review.  Indeed I forgot the async version of close().
We could use CompletableFuture::thenRun(Runnable, Executor) with the common Fork/Join pool to shut down the executor but it may take a while if that pool is overwhelmed...
I am trying another implementation where executor().shutdown() is called immediately after the call to .submit() returns.  According to the Javadoc of ExecutorService, it should work:
Initiates an orderly shutdown in which previously submitted tasks are executed, but no new tasks will be accepted.

If the build succeeds, I will replace my previous commit with that new change.

yeah - that would be another way.  would you also block (i.e. awaitTermination()) in that method when you call shutdown()?  That's not so good for closeAsync() if we block i guess....

I think this case is exactly the reason why methods like shutdown() exist independently from shutdownNow(). As you mentionned, adding .awaitTermination(...) would make the async call synchronous.
I can only see 3 use cases here, and all of them are covered:

I want a synchronous shutdown, I should use cluster.close()
I want a asynchronous shutdown, I should use cluster.closeAsync()
I want a timely asynchronous shutdown, I should use cluster.closeAsync().get(5, TimeUnit.SECONDS)

Ok - so just to be clear, for your cases 2 and 3, the executor that you called shutdown() on might still be active when the CompletableFuture finishes to say the "cluster is closed"?  In other words, all resources haven't been really shutdown at the point the future returns because the executor might still be working on that since you aren't blocking.  Is that a problem or am I not thinking of that right?
actually, I'm trying to think of what weird things might happen if there is something long running in the executor and then we call closeAsync()? If there was such a situation, that will schedule a job to close the transport which might somehow be in use by that long run job.  It seems like it is wrong to try to use the executor in shutdown.  Maybe it would be better if it was just a standalone "shutdown" thread?  in that way it could call executor.shutdown() and awaitTermination() and then call factory.shutdown() and then complete the future.  wdyt?  am i thinking too much?

I am not an expert in the Tinkerpop codebase but my understanding of the code is the following:
Yes, the CompletableFuture can be executed in parallel with other tasks by the executor, since it may be multithreaded.  However, I don't think it can complete if tasks are still being executed.  It calls factory.shutdown() which delegates the action to Netty.
That factory.shutdown() closes Netty's event loop after a grace delay of roughly 17 seconds (that's the "sensible values" described by EventLoopGroup::shutdownGracefully().  A long running task that uses the transport layer may therefore encounter an IOException, but I don't think that is a really bad thing, considering it is the user who explicitly triggered the cluster.close() without waiting for all of the pending requests to complete.
I mean, as a developer, if my code is reading a file and I call inputStream.close() in another thread, I don't expect the latter call to block indefinitely until the whole file has been read.
In the alternative approach you describe, how long would you wait for the termination to happen?

I don't expect the latter call to block indefinitely until the whole file has been read.

What you wrote above makes sense to me - I just wanted to work through all the ramifications of close() to make sure we were doing what devs would expect...Thanks for talking that through with me.  I'll merge shortly.

This was a minor change - one line of code - merged by CTR.


: 'test-results\\test-case-organization-organization-test-add-organization-py-test-add-organization-default-user-chromium'

..\..\Python312\Lib\shutil.py:650: PermissionError

@zhaod34  i'm obtaining the same problem (access denied),
            try:

              os.unlink(fullname)

E                   PermissionError: [WinError 5] Accesso negato: 'test-results\test-test-browser-test-user-test-megasearch-test-content-visualization-py-testcontentvisualization-test-content-visualization-with-docuviewer-chromium-pdf\video-1.webm'
that's happening because of xdist,
indeed even if there is the exception,
the folder is deleted,
that means that xdist, spawning different processes, is trying to delete the same files simuntaneally to other xdist processes,
i'm tring to use one of the pytest webhook to empty the folder.
did you found another solution in the meanwhile?

for now i'm using this workaround
def pytest_sessionstart(session):     """     at the very beginning     """     print("deleting folder containing video results, if exists")     temptative = 0     while temptative < 3 and os.path.exists('test-results'):         try:             shutil.rmtree('test-results')         except Exception as e:             print("retrying")         time.sleep(1)         temptative =+ 1     print("folder deleted.")

I have the same issue also using xdist. The workaround is rerunning the tests again as the folder is deleted and in the second run you do not see the error. But it wastes a lot of time.

This should be fixed in v0.5.1 which is getting published rn.


Create Closing a deal

Adding a new page to the handbook regarding the post sale process
Description
Adding a new page to the handbook regarding the post sale process
Related Issue(s)
n/a
Checklist

[x ] I have read the contribution guidelines
[ x] I have considered the performance impact of these changes
[x ] Suitable unit/system level tests have been added and they pass
[x ] Documentation has been updated

Thanks for the PR, I made a few changes. Maybe worth checking out @zackwasli :

Renamed the file to closing-a-deal.md

using - instead of spaces
add the .md extension

Added a link to the index page
Did a markdown trick to make a numbered list
Minor rewording


feat: Updates for accounting Section and Zone changes

Description
This PR have following fixes and updates,

Changed renderEachConfigV2 to accommodate SECTION_V2, SINGLE_COLUMN_ZONE, and DOUBLE_COLUMN_ZONE.
Added classes to form render components to handle parallel use of old config and new config.
Updated Section and Zone component CSS to use nested structure.
Fixed the height difference between label with JS toggle and without JS toggle.

Fixes #35544
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!IMPORTANT]
🟣 🟣 🟣 Your tests are running.
Tests running at: https://github.com/appsmithorg/appsmith/actions/runs/10456040271
Commit: 3dcc0df29aaffb0e2470e1561fb996fde3fc4837
Workflow: PR Automation test suite
Tags: @tag.All
Spec: ``
Mon, 19 Aug 2024 15:13:26 UTC

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

Summary by CodeRabbit

New Features

Improved styling for toggle buttons and dropdowns for a better user experience.
Enhanced layout adaptability through updated class names and properties across various components.
Introduced a new function for more efficient rendering of form sections and nested components.

Bug Fixes

Addressed potential layout shifts and visual inconsistencies by enforcing minimum heights on key components.

Documentation

Updated CSS selectors for better readability and maintainability without altering existing functionalities.

/build-deploy-preview skip-test=true


QR Code List Item Command View Set

Q
A

Bug fix?
no

New feature?
no

New sample?
yes

Related issues?

What's in this Pull Request?
A list item command view set which generates a printable QR code for a list item.

Hi Hugo,
Loving your new sample, thank you so much for contributing it! Always a pleasure to merge your PRs. :)
Laura

Thank you @LauraKokkarinen! Your feedback is always the highlight of every pull request!

Hi @hugoabernier ,
Would you like to show us a short demo about this sample in one of the future SPFx community calls?
Laura

@LauraKokkarinen I would be delighted to! Let me know when

@hugoabernier Would the 24th of October work for you? Or the 7th of November?
L

November 7th would be best, if you don't mind

Not at all! :) I'll note down that you'll be presenting a 10-15 min demo on that date. Cheers!
Laura

Hi @hugoabernier ,
It was just decided that we'll do some kind of an "Ignite special" call on the 7th of November and will not have any demos on that community call. I'm so sorry about having to cancel your demo that we've already agreed for that date! :( Would you be ok doing it some other time? There is still an open spot for a demo on the 24th of October, for example.
Laura

@LauraKokkarinen I'm looking forward to an ignite special, so I don't mind being bumped. I'm not available on the 24 (will be on a plane) but I'm available any time after that

@LauraKokkarinen I'm looking forward to an ignite special, so I don't mind being bumped. I'm not available on the 24 (will be on a plane) but I'm available any time after that. Just name a date and assume I'll be there.

@hugoabernier The 21st of November it is then. :) Thank you!
Laura


Allow function/method calls to be mixed with keys

I'm thinking of something like this:
class Foo:
    bar = appcli.param(
            Key(ConfigA),
            Call(lambda: ...),
            Key(ConfigB),
    )

The Key objects would get their values by querying the corresponding configs, while the Call objects would get their values by calling the given function.  There could be several of these classes, e.g. to return scalar values, to call methods (e.g. functions with the self argument), etc.  These classes actually correspond with the default parameters that I was thinking about expanding in #10.
It's worth noting that you could probably achieve the same end result using custom configs, but I think this is still a paradigm worth supporting.  I want to think of parameters as being able to read values from arbitrary sources in arbitrary order, and this makes it much easier to fit calculated values into that ordering.
The other nice thing about this approach is that the functions/methods can raise AttributeError to be skipped, which default values can't do.

More syntax examples:

class MyApp:

    def _helper(self):
        pass

    bar = appcli.param(
            Key(ConfigA),
            Method(_helper),
            Key(ConfigB),
    )

I like that Method is a noun in the same sense as Key, if you know what I
mean.

Note that the Method/Func/Value objects could replace the default and default_factory arguments to param().  They provide all of the equivalent functionality and more.  But the default arguments are useful syntactic sugar, so I'm not going to get rid of them.


Return git errors gracefully instead of rendering them as 500 Server Error

Many errors, especially those from git, are rendered as 500 Server Error pages. It seems to me that in many situations the end users could work out the problem if they were aware of the actual error, which is completely hidden from them in production mode.
The end user may or may not have rapid access to the Gitea administrator to help them with this problem, and they certainly don't have access to a quick new Gitea version that fixes it, if it's Gitea's to fix at all. They may also be pressed to finish some work and they may be blocked by their problem.
So I think that it would be great if Gitea used functions like ctx.RenderWithErr() to give the user a tidy feedback instead of a crash page. Something similar could be said about the git server.
Security should be considered, though, as error messages might expose data unintendedly.

Agreed. We jump straight to 500 far too often when we could recover.
In terms of the merge issues I'm looking at detecting merge fails a bit better and being able to report these a little nicer.


[Bug] "Duplicate" functionality does not create a distinct element

Describe the bug
"Duplicate" functionality no longer provides a unique name. Therefore, Ctrl+D, Enter will override the current duplicated request with itself i.e. effectively noop It seems I found another "feature": Duplicated requests are not created underneath the duplicated element, but rather last (https://github.com/Kong/insomnia/issues/1946).
While it is impossible (and maybe not desirable) to create a globally unique name, it still feels weird that now duplicating elements over and over will give no cohesion: no "naming related to the ancestor" and https://github.com/Kong/insomnia/issues/1946 I cannot longer effectively create some kind of tree structure
Disclaimer: Maybe I should revise my naming practices or my workflow in general; however, so far it "seems to work better" to just duplicate templates and add whatever bells and whistles to run the appropriate query. It does not, however, change the fact that the proposed name does not appear to be a feature.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.

Name of the request is also search (Copy)
Desktop (please complete the following information):
Version 7.1.0
Shell 3.1.13
Node 10.2.0
V8 6.6.346.32
Architecture x64

libcurl/7.67.0 OpenSSL/1.1.1d zlib/1.2.11 nghttp2/1.29.0

Additional context
Add any other context about the problem here.

Hello, sorry for the late reply.  This does feel like a feature request and I agree, an easier experience on Insomnia is something we all want.  If you're still interested in this feature, what I'm hearing from the description is that you'd like Insomnia to help with understanding your request "tree structure" as it evolves via duplication (did I get that right?).  What do you use that request-origination tree structure for and how does it help you in your workflow?

Hello @wongstein, and thank you for your response.
Sadly, as the issue report is 2 years old, I don't remember entirely what is this about.
I vaguely remember that for "one flow", multiple requests are needed, in order. Copy-pasting one specific request (e.g. the login one), means that if the login request changes, then I'll have to manually update all of the login copies.

Unfortunately, I am not using Insomnia anymore; cost (pain) and benefit (usability/necessity) make it a poor choice for me.

Ah I see a bit what you're saying.  The expectation is, if I create children requests from a parent requests, then I expect changes in that parent requests should be propagated down to the children.
Just a follow up to that: Should a parent request change always override?  For example, let's say you make a change in the child request, and then you change the parent request in the same field.  Should the parent change then override the child changes?

Just a follow up to that: Should a parent request change always override? For example, let's say you make a change in the child request, and then you change the parent request in the same field. Should the parent change then override the child changes?

If you'd change the same field, nooo, I don't think the child should "hear" about that change. However, if you "undo" the child's override, then parent's value should be used (kinda like system/global/per-dir configuration option schemes: if system is set, and then you set global, any change above is transparent to "the overriding level and below")

Closing as there's no support for overrides and linking of duplicates


Add first test

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@db13782). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   41.55%
=========================================
  Files             ?        2
  Lines             ?      154
  Branches          ?       18
=========================================
  Hits              ?       64
  Misses            ?       83
  Partials          ?        7

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@db13782). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   45.45%
=========================================
  Files             ?        2
  Lines             ?      154
  Branches          ?       18
=========================================
  Hits              ?       70
  Misses            ?       76
  Partials          ?        8

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@db13782). Click here to learn what that means.
The diff coverage is 71.42%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   72.36%
=========================================
  Files             ?        2
  Lines             ?      152
  Branches          ?       17
=========================================
  Hits              ?      110
  Misses            ?       39
  Partials          ?        3

Impacted Files
Coverage Δ

async_sender/api.py
72% <71.42%> (ø)

Continue to review full report at Codecov.

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


Add cross-os

Added https://github.com/milewski/cross-os

Looks good, I want to test out cross-os before merging.
Ignore the failing Travis Build BTW.

Hey @milewski; sorry so long in getting around to reviewing this. A couple suggestions to make cross-os more awesome:

Should error out if a script is not defined for the users OS. (i.e. a script is set for win32 and darwin, but the user is on linux) This needs to be rectified before I merge this.

Consider moving (or at least allowing) cross platform scripts to be set outside the scripts key:
{
  "scripts": {
     "foo": "cross-os foo"
  },
  "cross-os": {
    "foo": {
      "darwin": "echo something",
      "linux": "echo 'somthing else'"
    }
  }
}

Perhaps revise the language in the README for the linux example script.

Should error out if a script is not defined for the users OS. (i.e. a script is set for win32 and darwin, but the user is on linux) This needs to be rectified before I merge this.

I have many cases where i only want to run script for one OS only.. for example... if i force a fail if scripts is not found i will be forced to add empty scripts on the config which doesnt looks nice.. take this example for instance
{
  "scripts": {
     "foo": "cross-os foo"
  },
  "cross-os": {
    "foo": {
      "freebsd": "",
      "sunos": "",
      "win32": "",
      "darwin": "",
      "linux": "add-apt-repository --yes ppa:stebbins/handbrake-releases && apt-get update &&  apt-get install -qq handbrake-cli"
    }
  }
}

As im using node process.platform to get the current os it could be any of darwin, freebsd, linux, sunos or win32
currently what i am doing if a script is not specified for a platform.. just console.log('script: foo not found') instead of fail hard..

Consider moving (or at least allowing) cross platform scripts to be set outside the scripts key

Done!

Perhaps revise the language in the README for the linux example script.

Hehe.. that i have copied from an epic batter of rap between Steven Job / Bill Gates. but anyway i have updated it to some simple foo bar stuff

I have many cases where i only want to run script for one OS only.. for example... if i force a fail if scripts are not found i will be forced to add empty scripts on the config which doesnt looks nice..

I agree. I'm fine with just warning the user; however, if I have this:
{
  "scripts": {
    "test": "cross-os test"
  },
  "cross-os": {
    "test": {
      "darwin": "echo FooBar"
    }
  },
  "devDependencies": {
    "cross-os": "^1.0.1"
  }
}

and I'm on linux, running npm test doesn't print any warning. It should at least tell the user that there's no script available for their OS.

Ohh thats true.. i was only getting that message thought tests i didnt realized it wasnt poping up when it was being used on the "real world" env... i have fixed it and pushed to npm as 1.1.2`

Sorry so long in getting to test this. LGTM, merging.


Throws 'Cannot read property nullable of undefined'

Trying to run a very minimalist setup, using the pet store example on swagger.io:
{
  "url": "https://petstore.swagger.io/v2/swagger.json",
  "dir": "./test",
  "language": "typescript",
  "ignore": {}
}

When running swagger-typescript, I get the following error:
yarn run v1.22.5
$ node ./node_modules/swagger-typescript/lib/index.js
{
  error: TypeError: Cannot read property 'nullable' of undefined
      at /home/thomas/react/inviteanerd/node_modules/swagger-typescript/lib/utils.js:135:57
      at Array.every (<anonymous>)
      at Object.getParametersInfo (/home/thomas/react/inviteanerd/node_modules/swagger-typescript/lib/utils.js:135:28)
      at /home/thomas/react/inviteanerd/node_modules/swagger-typescript/lib/generator.js:25:117
      at Array.forEach (<anonymous>)
      at /home/thomas/react/inviteanerd/node_modules/swagger-typescript/lib/generator.js:12:35
      at Array.forEach (<anonymous>)
      at Object.generator (/home/thomas/react/inviteanerd/node_modules/swagger-typescript/lib/generator.js:11:37)
      at generate (/home/thomas/react/inviteanerd/node_modules/swagger-typescript/lib/index.js:20:34)
      at processTicksAndRejections (internal/process/task_queues.js:93:5)
}

Version info:
typescript 3.7,
node 14.13,
yarn 1.22.5

Hi there,
As mentioned in the README Swagger-Typescript just working with OpenApi v3, it seems your configured JSON is not OpenApi v3.

If you are interested in testing it, use this JSON: https://generator3.swagger.io/openapi.json

Right, I had used my own semi-handcrafted json file (generated with swagger-php from phpdoc annotations). It was missing the components/schema (as I hadn't created any schemas yet), and so it fails.
Perhaps a basic validation of the entire file, or some better error messages, when something goes wrong would be good.. Otherwise you are shooting in the dark, when trying to figure out what is wrong.

Right, I had used my own semi-handcrafted json file (generated with swagger-php from phpdoc annotations). It was missing the components/schema (as I hadn't created any schemas yet), and so it fails.
Perhaps a basic validation of the entire file, or some better error messages, when something goes wrong would be good.. Otherwise you are shooting in the dark, when trying to figure out what is wrong.
(Feel free to close this, if you want to.. could be considered as a reminder for future features)

Thank you.
I will do it soon.

Fixed (https://github.com/hosseinmd/swagger-typescript/commit/379f8611fb3e9dd7507ecedb3774fdfed633faa8)
Released (https://github.com/hosseinmd/swagger-typescript/commit/86a6b56eda7d058d718157cb86a34c1423138727)


Geoalchemy example not working?

I'm trying to decide if I can use flask-admin with geoalchemy.  I'm a complete novice to flask.  It looks like MAPBOX_MAP_ID is deprecated with Mapbox?

I am also trying to run this but it seems this url:
https://api.mapbox.com/styles/v1/mapbox/'+window.MAPBOX_MAP_ID+'/tiles/{z}/{x}/{y}?access_token='+window.MAPBOX_ACCESS_TOKEN
is not valid anymore

Did you try something like MAPBOX_MAP_ID = 'light-v10'? There may be some css issue but I can get  the tiles to display this way.

I've added MAPBOX_MAP_ID = 'light-v10' to the example directly - should make it a bit easier to run.


⚠ Young Discoverers has degraded performance

In f454f89, Young Discoverers (https://youngdiscoverers.org.au) experienced degraded performance:

HTTP code: 200
Response time: 5117 ms

Resolved: Young Discoverers performance has improved in 8bf7c39.


Clarify needed "monkey-patch dependency"

The README says that you need to install a monkey-patch dependency in step two, however, does not specify which one. What should the user download?

You’ll need to install iocave.monkey-patch. Note that as of VS Code 1.74 and newer, the monkey patch extension has been broken by changes to VS Code. You’ll need to use VS Code 1.73 or VSCodium to continue to use this extension.

Alright. By the way, do you have a screenshot of what it looks like with the icons?

There’s a screenshot in the readme! https://github.com/j-f1/sf-symbols-vscode

Yes however that one doesn't show the file icons, which are the main part I think :)


Datagrid fails on initial load when isFetching is true and using the filter panel

What package(s) are you using?

[x] Carbon for IBM Products (or Carbon for IBM Cloud & Cognitive)
[ ] Legacy/CDAI
[ ] Legacy/Security

Detailed description

Describe in detail the issue you're having.

Datagrid fails on initial load when isFetching === true and filter panel is used. The error originates from componentStack:    at FilterPanel (webpack-internal:///./node_modules/../../node_modules/@carbon/ibm-products/es/components/Datagrid/Datagrid/addons/Filtering/FilterPanel.js:59:25)
isFetching is set to true on initial load because we are waiting on data from our api call. When I set isFetching to false, the datagrid loads in an empty state, then renders the returned data.

Is this issue related to a specific component?

Datagrid, filter panel

What did you expect to happen? What happened instead? What would you like to
see changed?

expected the datagrid to load without errors

What browser are you working in?

Chrome

What version of the @carbon/ibm-products (or @carbon/ibm-cloud-cognitive)
package are you using?

"@carbon/ibm-products": "2.27.0", I believe the changes here: https://github.com/carbon-design-system/ibm-products/pull/4207 may have introduced this bug. @matthewgallo

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

CP4AIOps

Please create a reduced test case in CodeSandbox
https://codesandbox.io/s/github/carbon-design-system/ibm-products/tree/main/examples/carbon-for-ibm-products/SidePanel

Additional information

Screenshots or code
Notes

@matthewgallo I've tested this on 2.30.0-alpha.9 and 2.30.0 and confirmed the added checks allows the datagrid to load properly. 👍🏽

Great news 😄


Add note that Windows Authentication can't be used with gRPC

Fixes https://github.com/grpc/grpc-dotnet/issues/409

Ready for approve/merge 🙏


Update immutable-storage-overview.md

If there is version level Immutable policy configured on the account level, the inventory report tends to fails as it is a conflicting feature. Additionally, if there an immutable policy configured on the destination containers of the report, then also the report shall tend to fail.
Adding both the scenarios on this documentation too and in the same request for review.

@normesta
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


TOMEE-2405 Migrate MP README's to adoc and create MP index-group

I resolved the conflicts for Cesar on https://github.com/apache/tomee/pull/317. So this PR can be closed.


chore(domains): update to *.speckle.systems domains

Part of https://linear.app/speckle/issue/WEB-1337/update-hard-coded-references-to-specklexyz-and-latestspeckledev

@iainsproat yeah, I am going to look at it as soon as I can


Can't log in with ver. 0.3.0

have forked hubpress to my own repo, changed config.json, confirmed this is hubpress 0.3.0 and uploaded to my https://github.com/jnorthr/hubpress.io account.
Now have 'log on' panel at http://jnorthr.github.io/hubpress/#/login

as shown in hubpress demo, but no combination of user name or email plus password gets me thru. Only box top-right says 'consult console for more informations' but where is that console ? and should i be using my github credentials to log on or some thing else ?

update of javascript console screen prints when logging in from firefox / chrome /opera browsers

Hi @jnorthr,
In your repository, on each branch, you did not change the config.json file.

merci for that idea -
does this mean my config.json values must be identical for each branch in
jnorthr/hubpress.io https://github.com/jnorthr/hubpress.io/hubpress
https://github.com/jnorthr/hubpress.io/tree/master/hubpress/config.json*
?*
thx
On 29 May 2015 at 19:42, Anthonny Quérouil<EMAIL_ADDRESS>wrote:

Hi @jnorthr https://github.com/jnorthr,
In your repository, on each branch, you did not change the config.json
file.
—
Reply to this email directly or view it on GitHub
https://github.com/HubPress/hubpress.io/issues/226#issuecomment-106883065
.

since here is only one branch on my hubpress.io git repo have changed config.json to same as all other places it is held. Tried to log in with a safari 5.1.10 browser i've not used before for this task. Which fails to load due to line 51 in app.js looking for 'map' variable, so maybe this is something else ? pls see this:

my google chrome browser still fails with this 404 page fault even after all fixes as suggested

if you do not use the jnothr.github.io name for your repository, you can't use the branch master

In the configuration f your repository, you must set the branch gh-pages as default.
On the branch gh-pages, you must update the file config.json with your username and the repositoryName (here hubpress.io)
You can access to HubPress via the URL http://jnorthr.github.io/hubpress.io/hubpress

thank you for your patience :-)
at the moment i have a master and a gh-pages branch in https://github.com/jnorthr/jnorthr.github.com/tree/master and https://github.com/jnorthr/jnorthr.github.com/tree/gh-pages
Both are exact copies of hubpress.io 0.3.0  and because i don't really know what i am doing i also have a repo at https://github.com/jnorthr/hubpress.io with hubpress.io 0.3.0 and 3 branches: master, development and gh-pages.
Please advise WHICH repo needs to have the gh-pages set as the default ?  Then i will try to learn how to adjust github to make that happen. Also which config.json in which branch of which repo needs to have the correct values ?
Right now i have http://jnorthr.github.io/ working and am guessing that it is coming from the master branch of https://github.com/jnorthr/jnorthr.github.com/tree/master. I am also guessing that when i have hubpress.io working then any new posts i make thru hubpress.io will come back into https://github.com/jnorthr/jnorthr.github.com/tree/master (or gh-pages?)
So can we say that hubpress.io is really like a publishing tool that lets users write new posts in a given repo within github ?  peut-être i have lost the plot  ;-D

am using this link to learn http://octopress.org/docs/deploying/github/  what is possible - hopefully

Ok, have confirmed all branches of both repos have identical credentials and point to https://github.com/jnorthr/hubpress.io
also made gh-pages as default on both repos.
Next: when attempting a log on, there is a module failure at app.js line 51 that says missing variable : Map

The repositoryName in your config.json is not good. You must put the repository name only (in your case hubpress.io), not the url

ok merci for that. Have made that change to :
{   "meta": {"username": "jnorthr","repositoryName": "hubpress.io",branch":
"gh-pages"},   "theme": {   "name": "Casper"   }
}
and http://jnorthr.github.io/hubpress/#/login now gets me to signin page.
Enter jnorthr+password gives 404 as shown in this screen shot. It is
looking for https://github.com/jnorthr/hubpress.io?143... but cannot find
it. But if i manually enter https://github.com/jnorthr/hubpress.io into
browser address bar, it correctly locates target. This makes me think it is
a token failure now. Is that possible ?
thx jim
On 3 June 2015 at 00:02, Anthonny Quérouil<EMAIL_ADDRESS>wrote:

The repositoryName in your config.json is not good. You must put the
repository name only (in your case hubpress.io http://hubpress.io),
not the url
—
Reply to this email directly or view it on GitHub
https://github.com/HubPress/hubpress.io/issues/226#issuecomment-108111460
.

WELL Houston - I think i have lift-off !!!  Did all the changes to my config.json repository name in four different branches :  master and gh-pages in both my jnorthr.github.com and my hubpress.io repo too. I still do not understand which of these repos is being used by hubpress.
But anyway, i have started testing on yet another iMac PPC that i had not used before to access hubpress. So am thinking the cookies/connect tokens for my other browsers on other machines may have been stopping hubpress from working. Will let you know how it goes.
merci for your time
jim


Problem when using different versions of Java (eclipse vs. mvn-command)

Do you think the following mistake is worth to be mentioned in a developer-FAQ?
After mvn eclipse:eclipse I got the following error:
Unbound classpath container: 'JRE System Library [JavaSE-1.8]' in project 'shogun2-dao'

Solution##
Use the same Java-version for Eclipse and for executing mvn eclipse:eclipse.
If they differ, you can set the version manually on the command line like:
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64/jre/ mvn eclipse:clean eclipse:eclipse

Yes please! A PR with such a doc change would be appreciated.

The doc is a bit outdated. I suggest to use Eclipse with the m2e plugin (in latest version), which is not mentioned in the doc. After a clone of the SHOGun2 repo, you can easily use the "Import existing Maven project" functionality of eclipse/m2e. This has some advantages, for example that dependencies can be resolved within the eclipse workspace.
I will expand the documentation regarding this!


[girder] easy to start/throw away development instance

There is docker compose and https://github.com/dandi/infrastructure/wiki/Girder-setup-on-aws describing details of current deployment.
I would like us to have a recipe/image/compose/whatever so we could quickly start the whole platform (locally or in the cloud) with some pre-populated users and possibly datasets.  Possibly even make those parametric so we could test our scripts/cli in various scenarios easily.  May be @mgrauer already has some scripts to establish such test instances of girder?

no girder, we have ways to deploy via docker-compose


MMDistributedDataParallel

hello, Can someone explain ｀MMDistributedDataParallel｀, Compared to the official one, I am confused about the forward function is relatively simple: 1) only one  _sync_params before training; 2）where is the details of the distributed average_gradients from each devices. i can not find anything about the dist_op eg. reduce, all_reduce, gather and so on.
haha, just a newbaby about pytorch.

Here: https://github.com/open-mmlab/mmdetection/blob/master/mmdet/core/utils/dist_utils.py#L54


Resistors For USB Host

Does this project follow the USB Specification for the host implementation? Im having trouble understanding if it requires 15k (changed to 14.5k - 24.8k) resistors and if there something that needs to be disconnected after the device negotiates what speed its using. Or does PIO USB implement this somewhere I havent seen? There is a resistor pdf in the link below.
https://www.usb.org/sites/default/files/usb_20_20230224.zip
P.S, What are the 22ohm resistors mentioned in the README used for?

I was wondering too. I don't have a proper answer, but I saw this application note describing these 22 ohm resistors and thought it might be useful: https://www.onsemi.com/pub/collateral/and8074-d.pdf
I think the 15K pull up and 1.5K pull down are for indicating upstream/downstream and low speed/full speed.
I'm not sure how these can be omitted (See Adafruit's RP2040 USB Host Schematic with only 22ohm resistors) but I guess it works anyway.


⚠ SceneTime has degraded performance

In 81d7fce, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 2874 ms

Resolved: SceneTime performance has improved in 3156838 after 6 minutes.


Update Office 365 Outlook service

update domain from live.com to office.com

Pre-flight Checklist
Please ensure you've completed all of the following.

[ ] I have read the Contributing Guidelines for this project.
[ ] I agree to follow the Code of Conduct that this project adheres to.

Description of Change

Hi, I've not run any tests yet (just changed the URL in my local service)
The Contributing guidelines link is dead, so I assume I should look at here
Also, I didn't see ant policy regarding version numbers, so I also assumed that changing the service url is a relatively major change, so I bumped to 1.7.0

Hi @Thelm76 thanks for the PR.
However, I don't think we will change that at the moment. Indeed, the usage of either urls live.com and office.com seem to be the norm. I don't know which one is globally more present than the other, but both are definitely very common. For this reason, we added the "self-hosting" setting for that recipe so that users could set the domain name that correspond to the account they connect to (I personally use both domains as the different emails I log in behave differently). Changing now which one is the default would disconnect some users which are currently staying connected.

Oh I see... I hadn't tested with my former live address and yup' it doesn't work... Easiest setting for users would be to have a 3-buttons selection at setup (as it is not very clear that we have to switch from live.com to office.com)...

I'll work on this when I get some time to dig in this

Hey @Thelm76, any chance that you can finish up this PR? Otherwise, I will close it.

Closing due to inactivity


Add EnsembledSampler

Contributor Agreements
Please read the contributor agreements and if you agree, please click the checkbox below.

[x] I agree to the contributor agreements.

[!TIP]
Please follow the Quick TODO list to smoothly merge your PR.

Motivation

Experimental implementation of sampler ensemble.
It might mitigate some issues of existing samplers, such as falling into local optima by certain sampler's biases.
Description of the changes

Implemented EnsembledSampler, which ensembles multiple samples given by users.
For each trial, it samples a sampler from the list and then samples parameters based on that sampler.
TODO List towards PR Merge
Please remove this section if this PR is not an addition of a new package.
Otherwise, please check the following TODO list:

[x] Copy ./template/ to create your package
[x] Replace <COPYRIGHT HOLDER> in LICENSE of your package with your name
[x] Fill out README.md in your package
[x] Add import statements of your function or class names to be used in __init__.py
[x] Apply the formatter based on the tips in README.md
[x] Check whether your module works as intended based on the tips in README.md

@HideakiImamura Could you review this PR?


dont recommend

[Enter feedback here]
web page dont give any response at question: "how to use azure cli in docker" . I mean .. what env vars are required, best practices .. any options, but give nothing.

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

ID: d884a3fe-07cf-e518-085d-602425fe2480
Version Independent ID: 1636994b-e193-74e2-9936-a07e43913326
Content: How to run Azure CLI in a Docker Container
Content Source: docs-ref-conceptual/run-azure-cli-docker.md
Service: azure-cli
GitHub Login: @dbradish-microsoft
Microsoft Alias: dbradish

@maliaga-pantoja , Thanks for your feedback.
We have assigned this to the content owner/author @dbradish-microsoft for review.

I mean .. what env vars are required, best practices .. any options, but give nothing.

I think this belongs more to the topic of docker usage. You may check docker manual https://docs.docker.com/desktop/ instead.

@maliaga-pantoja, is there something specific to Azure CLI, not docker that should be included in the doc?

Maybe what volumes should be mapped to have the Azure CLI configuration or login information persisted, for instance.

adriancuadrado, Thanks for providing feedback that helps improve our documentation.  This feedback has been passed to the appropriate team at Microsoft and as there has been no continued discussion since March, 2022, this GitHub issue is being closed.


(tsan / c++ / linux) tests.bins/tsan/qps_test

https://grpc-testing.appspot.com/job/gRPC_master/15496/config=dbg,language=c++,platform=linux/
Recent builds where this failed:
https://grpc-testing.appspot.com/job/gRPC_master/15496
https://grpc-testing.appspot.com/job/gRPC_master/15492
https://grpc-testing.appspot.com/job/gRPC_master/15471
https://grpc-testing.appspot.com/job/gRPC_master/15463

Today qps_test has flaked under TSAN.
https://grpc-testing.appspot.com/job/gRPC_master/15811/config=tsan,language=c++,platform=linux/testReport/junit/(root)/tests/bins_tsan_qps_test/
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)

It that just a flake or something that might have been introduced by recent merges?

This is an outdated clang version. It may have been introduced by a recent
merge, it may be the weather.
We need to move our TSAN builds to a more recent clang (we'll likely want
to build from source).
On Tue, Mar 15, 2016 at 10:36 AM Jan Tattermusch<EMAIL_ADDRESS>wrote:

Today qps_test has flaked under TSAN.
https://grpc-testing.appspot.com/job/gRPC_master/15811/config=tsan,language=c++,platform=linux/testReport/junit/(root)/tests/bins_tsan_qps_test/
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
FATAL: ThreadSanitizer CHECK failed: /tmp/buildd/llvm-toolchain-3.5-3.5/projects/compiler-rt/lib/sanitizer_common/sanitizer_stacktrace.cc:68 "((count)) < ((size))" (0x1, 0x1)
It that just a flake or something that might have been introduced by
recent merges?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/5509#issuecomment-196940305

Alright, I've seen this several times over last X builds. Almost definitely something we didn't have before.
Marking this as P0 as greeness it at stake.
CC @ctiller , @nicolasnoble

Seen many times today, e.g. (https://grpc-testing.appspot.com/job/gRPC_master/15850/config=tsan,language=c++,platform=linux/testReport/junit/(root)/tests/bins_tsan_qps_test/)

Seen again today https://grpc-testing.appspot.com/job/gRPC_master/15855/config=tsan,language=c++,platform=linux/testReport/junit/(root)/tests/bins_tsan_qps_test/

It's not really flaky though, it just fails consistently in all runs.

Seen again as (consistently) failing:
https://grpc-testing.appspot.com/job/gRPC_master/15886/config=tsan,language=c++,platform=linux/testReport/junit/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15887/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15888/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15889/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15890/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15891/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15893/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15894/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15895/config=tsan,language=c++,platform=linux/testReport/(root)/tests/bins_tsan_qps_test/
https://grpc-testing.appspot.com/job/gRPC_master/15897/config=tsan,language=c++,platform=linux/testReport/junit/(root)/tests/bins_tsan_qps_test/

@vjpai   this is failing most of our builds on master. Feel free to ask for help from anyone on the team if that would speed up fixing.

So, the issue is that updating tsan to unbreak this test ends up giving us
a more sensitive tsan that breaks 9 other tests. We need to resolve those.
On Fri, Mar 18, 2016, 2:38 PM Jan Tattermusch<EMAIL_ADDRESS>wrote:

@vjpai https://github.com/vjpai this is failing most of our builds on
master. Feel free to ask for help from anyone on the team if that would
speed up fixing.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/5509#issuecomment-198554762

And obviously, I want to fix those 9. It's just a question of when to do
it. Is it okay to have those 9 temporarily broken?
On Fri, Mar 18, 2016, 3:07 PM Vijay Pai<EMAIL_ADDRESS>wrote:

So, the issue is that updating tsan to unbreak this test ends up giving us
a more sensitive tsan that breaks 9 other tests. We need to resolve those.
On Fri, Mar 18, 2016, 2:38 PM Jan Tattermusch<EMAIL_ADDRESS>wrote:

@vjpai https://github.com/vjpai this is failing most of our builds on
master. Feel free to ask for help from anyone on the team if that would
speed up fixing.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/5509#issuecomment-198554762

I'm of the opinion that 'new' failures from more sensitive instruments aren't really 'new' at all. casts vote

Let's disable qps_test for now and file a P0 issue to re-enable it once we fix the 9 failing tests (and address those as P0 too, of course).

Seems fixed. Thanks!


Bump Zeebe Hazelcast Connector to 1.4.0

Bump zeebe-hazelcast-connector to version 1.4.0
Fixes issue https://github.com/camunda-community-hub/zeebe-simple-monitor/issues/541

This is a required update, since when using more recent version of zeebe-hazelcast-exporter an exception is thrown:
(this exception is because of protobuf data packages are compiled in the exporter/server with a newer protobuf compiler version, than the client uses)
This is the fix.
2023-11-16 19:26:55.425  INFO 27166 --- [  restartedMain] io.zeebe.monitor.ZeebeSimpleMonitorApp   : Started ZeebeSimpleMonitorApp in 3.319 seconds (JVM running for 3.567)
Exception in thread "grpc-default-executor-0" io.grpc.StatusRuntimeException: INTERNAL: Failed to frame message
	at io.grpc.Status.asRuntimeException(Status.java:530)
	at io.grpc.internal.MessageFramer.writePayload(MessageFramer.java:154)
	at io.grpc.internal.AbstractStream.writeMessage(AbstractStream.java:65)
	at io.grpc.internal.ForwardingClientStream.writeMessage(ForwardingClientStream.java:37)
	at io.grpc.internal.DelayedStream$6.run(DelayedStream.java:283)
	at io.grpc.internal.DelayedStream.drainPendingCalls(DelayedStream.java:182)
	at io.grpc.internal.DelayedStream.access$100(DelayedStream.java:44)
	at io.grpc.internal.DelayedStream$4.run(DelayedStream.java:148)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.UnsupportedOperationException: This is supposed to be overridden by subclasses.
	at com.google.protobuf.GeneratedMessageV3.getUnknownFields(GeneratedMessageV3.java:302)
	at io.camunda.zeebe.gateway.protocol.GatewayOuterClass$TopologyRequest.getSerializedSize(GatewayOuterClass.java:34489)
	at io.grpc.protobuf.lite.ProtoInputStream.available(ProtoInputStream.java:108)
	at io.grpc.internal.MessageFramer.getKnownLength(MessageFramer.java:208)
	at io.grpc.internal.MessageFramer.writePayload(MessageFramer.java:138)
	... 9 more


Add circle ci config for front only project

@williamdclt @ghamaide @Remy-Luciani I took your requests into account. Please review :)


Update UI when a new message arrives

When a new message arrives (already done), the UI should be updated to reflect the new messages

I'll do it

Done


PDF Layout corrections requested from Co-Site. Sept 2024

See PDF with comments. https://wiki.tib.eu/confluence/pages/viewpage.action?pageId=338566914

Page number - job

I added checkboxes to the list of tasks and checked what I got done.


Fix "cc -dumpversion" error

On some systems cc -dumpversion returns only the major version. There should be a check against that.
  File "./gyp_learnuv.py", line 94, in <module>
    (major, minor), is_clang = compiler_version()
ValueError: need more than 1 value to unpack

Fixed via https://github.com/thlorenz/learnuv/pull/33


egl-wayland: depend on libdrm instead of mesa

Description of changes
We don't actually need Mesa here.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg eval
(ofborg went down and might have missed this PR, sorry!)


Possibe to add "Connect/Disconnect" option ?

Hi,
remote-sync is currently mry preferred remote editing option via sftp. I like the window at the bottom of the editor which shows the upload / download progress.
Is it possible to add a;
"Connect To Remote Host"
"Disconnect to Remote Host"
option when we rightclick on the project folder ?
This will help when the connection freezes - we have to close / open atom editor to get a connection.

Even if there was just a term button to kill the current process... would be ideal to have some way to just stop it.

Is this project abandoned ?

Looks like it. Hope it gets revived.


Slug History

Keep Track of Slug History
Add a table for previous and current slugs of organizations.
Why?
We want to be able to keep track of the previous and current slugs of organizations.
Acceptance Criteria

[ ] Add backend table for previous and current slugs
[ ] Add functionality to update organization API call that will add the new slug to the slug history table

@KrisJordan is this still a feature we want to implement (would we rather make this as part of #189 )?

I think we can backburner this. If we ever build more of a cms feature to the site, perhaps we can revive it, but it's highly unlikely we're changing slugs much after creation.


maintainers: Change first name and mail of erictapen

Time to make it official :tada:
Also changed my pronouns to she/her btw.
Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Congrats :)

Can you add your new gpg key to your GitHub profile? The commit currently appears as unverified.

@mweinelt Sure, just did that. Also uploaded it here.


Added content response on write enabled feature to Gateway and Direct TCP

This PR:

Adds contentResponseOnWriteEnabled argument to CosmosClientBuilder and all internal client builders.
By default the value for the argument is set to false -> Item write operations will not return content response.
This feature only works in Gateway and Direct TCP mode. (Direct HTTP is implemented on the backend, but needs to be released)
Exposes new APIs - getETag() on CosmosItemResponse and CosmosAsyncItemResponse
Added configuration options for Write Throughput and Write Latency Benchmarks.
Updated client builders in TestSuiteBase to support contentResponseOnWriteEnabled  testing.
Updated and closed some open github issues that have already been fixed.

/azp run java - cosmos - tests

Would be nice to behcnmark with this change in.

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

Single region session long CI failed after running all the tests with spot bugs jar downloads.
2020-05-07T15:44:56.2558748Z [ERROR] Failed to execute goal com.github.spotbugs:spotbugs-maven-plugin:<IP_ADDRESS>:spotbugs (spotbugs) on project azure-cosmos: Execution spotbugs of goal com.github.spotbugs:spotbugs-maven-plugin:<IP_ADDRESS>:spotbugs failed: Plugin com.github.spotbugs:spotbugs-maven-plugin:<IP_ADDRESS> or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.bcel:bcel:jar:6.3.1, net.jcip:jcip-annotations:jar:1.0, org.dom4j:dom4j:jar:2.1.1, jaxen:jaxen:jar:1.1.6: Could not transfer artifact org.apache.bcel:bcel:jar:6.3.1 from/to ossrh (https://oss.sonatype.org/content/repositories/snapshots/): Transfer failed for https://oss.sonatype.org/content/repositories/snapshots/org/apache/bcel/bcel/6.3.1/bcel-6.3.1.jar: Connection reset -> [Help 1]

Single Region Strong Https e2e failed because of lots of SSLEngine closed already reactor-netty issue.
I think it might have caused the VM to crash. I have added more information on this issue:
https://github.com/Azure/azure-sdk-for-java/issues/7349


Error with Tensorflow >=1.14

Description
Unable to use the ampligraph 1.3 with Tensorflow 1.4 as recommended in the readme file
Module model_utils imports tensorflow projector from a deprecated location
from tensorflow.contrib.tensorboard.plugins import projector
Actual Behavior
Traceback (most recent call last):
  File "/home/gadelrab/anaconda3/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/gadelrab/anaconda3/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/gadelrab/ExDEC/experiments/run_experiments.py", line 7, in <module>
    from cli.main import initiate_problem, get_parser
  File "/home/gadelrab/ExDEC/cli/main.py", line 1, in <module>
    from ampligraph.latent_features import set_entity_threshold
  File "/home/gadelrab/anaconda3/lib/python3.7/site-packages/ampligraph/latent_features/__init__.py", line 32, in <module>
    from ..utils import save_model, restore_model
  File "/home/gadelrab/anaconda3/lib/python3.7/site-packages/ampligraph/utils/__init__.py", line 12, in <module>
    from .model_utils import save_model, restore_model, create_tensorboard_visualizations, \
  File "/home/gadelrab/anaconda3/lib/python3.7/site-packages/ampligraph/utils/model_utils.py", line 16, in <module>
    from tensorflow.contrib.tensorboard.plugins import projector
ModuleNotFoundError: No module named 'tensorflow.contrib'

Would you issue any quick fix for this error the library is not usable? Add to that using Tensorflow 1.3 produces many warning.

Hello @mhmgad,
Note installation guide suggests minimum tf version is 1.14.0. TF version 1.4 is not supported.
Tried this on my end and it works OK:
Can you please double-check on your side? Which tf version are you on?
import tensorflow as tf
print(tf.version.VERSION)

1.14.0

import ampligraph
ampligraph.__version__

'1.3.0'

import numpy as np
from ampligraph.latent_features import TransE
from ampligraph.utils import create_tensorboard_visualizations

X = np.array([['a', 'y', 'b'],
              ['b', 'y', 'a'],
              ['a', 'y', 'c'],
              ['c', 'y', 'a'],
              ['a', 'y', 'd'],
              ['c', 'y', 'd'],
              ['b', 'y', 'c'],
              ['f', 'y', 'e']])
model = TransE(batches_count=1, seed=555, epochs=20, k=10, loss='pairwise',
               loss_params={'margin':5})
model.fit(X)

WARNING - All triples will be processed in the same batch (batches_count=1). When processing large graphs it is recommended to batch the input knowledge graph instead.

create_tensorboard_visualizations(model, 'tensorboard_files')

Thank you @lukostaz for the quick response.
First 1.4 was a mistake it is 1.14
So, I found out that I have a conflict in the environment packages between conda and pip. pip was listing tensorflow 2.0 while conda showing 1.15 or 1.14. I created a clean environment and made sure that there is no tensorflow installed on the pip list and installed using conda, it works fine.
Thank you for your time, and sorry for the inconvenience.

No problem at all, glad you sorted that out.


[BUG] epel-release package not available (access forbidden)

Describe the bug
The link we use to download the epel-release package is currently unavailable (Forbidden).
https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
Forbidden
You don't have permission to access this resource.

This causes the installation of RHEL/CentOS clusters to fail downloading the requirements (https://github.com/epiphany-platform/epiphany/blob/develop/core/src/epicli/data/common/ansible/playbooks/roles/repository/files/download-requirements/redhat-7/download-requirements.sh#L691)
How to reproduce
Steps to reproduce the behavior:

Deploy any RHEL/CentOS cluster (repository component is enough to reproduce).

Expected behavior
The package is available, the cluster installs without problems.
Environment

Cloud provider: [all]
OS: [RHEL/CentOS]

epicli version: all epicli versions affected
Additional context
To workaround, manually install epel-release package on repostiory vm (for example from this link https://dl.fedoraproject.org/pub/epel/7/x86_64/Packages/e/epel-release-7-14.noarch.rpm).

DoD checklist

[ ] Changelog updated (if affected version was released)
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Case covered by automated test (if possible)
[ ] Idempotency tested
[ ] Documentation updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Backport tasks created / doesn't need to be backported

Fortunately the issue is gone. Closing.


Error with create notification

$notification = Notification::create()     ->withTitle('title')     ->withBody('body');
Exception: Firebase/Messaging/Notification.php:28

throw new InvalidArgumentException('The title and body of a notification cannot both be NULL');

Thanks for the... Notification 😅
Until this is addressed, please use
$notification = Notification::create('title', 'body');

The documentation was indeed incorrect - as it's not possible to send a message with a Notification that doesn't have a title nor a body, it wouldn't make sense to be able to create a notification with neither 😅


Transfer to reactjs

Hi @ellbee and @faassen :) We've merged everything in @rackt into @reactjs. Trying to unite the community under a single umbrella. Would you guys like me to move this repo as well?

Hi @mjackson, I say yes please on this. Cheers!

done!


[65053] Rename wrapper to starter in form

I suppose this PR should be divided into two separate PRs - one should be targeted to the master branch and include source changes, the second should be based on first and should be targeted to the gh-pages branch and include only changes with generated and built static files (that are in /docs directory)

I did not understand about the second PR: you say that it should be based on the first one (which targetes the master and includes only source changes) and, at the same time, the second PR should include only changes in the docs directory. If the second PR is based on the first one, how come it includes only changes in the docs directory?

I suppose this PR should be divided into two separate PRs - one should be targeted to the master branch and include source changes, the second should be based on first and should be targeted to the gh-pages branch and include only changes with generated and built static files (that are in /docs directory)

I did not understand about the second PR: you say that it should be based on the first one (which targetes the master and includes only source changes) and, at the same time, the second PR should include only changes in the docs directory. If the second PR is based on the first one, how come it includes only changes in the docs directory?
Or you mean that changes in the docs should be built from the first PR?

Exactly, first we need to merge first PR to put source changes to master branch, then we need to checkout to gh-pages branch, merge master branch to gh-pages branch and after that run command to generate and build static that should appear in the docs folder - it would be the content for the second PR

I have excluded the built static files - this PR contains only source changes.


Operator precedence

Replace syntax of operator definition, and replace numerical precedence with partial ordering of operators:
// Before
infix operator <> { precedence 100 associativity left }

// After
precedencegroup Comparative {
  associativity(left)
  precedence(> LogicalAnd)
}
infix operator <> : Comparative

Removed declarations of special operators from grammar. I added this feature myself, noone gave positive review of it, and now I think, that was a mistake. It was largely inconsistent. I changed the proposal back to a previous version.


Example with QwQ-32b raises ValueError on generated dict_keys

i mapping llm model, 'qwq-32b'
i execute this code, 'generate_answer_with_chain_of_thought(question=dev_example.question)'
source code, 'print(fields)'
fields :
signature : StringSignature(question -> reasoning, answer
instructions='Answer questions with short factoid answers.'
question = Field(annotation=str required=True json_schema_extra={'__dspy_field_type': 'input', 'prefix': 'Question:', 'desc': '${question}'})
reasoning = Field(annotation=str required=True json_schema_extra={'prefix': "Reasoning: Let's think step by step in order to", 'desc': '${reasoning}', '__dspy_field_type': 'output'})
answer = Field(annotation=str required=True json_schema_extra={'desc': 'often between 1 and 5 words', '__dspy_field_type': 'output', 'prefix': 'Answer:'})
)

ValueError                                Traceback (most recent call last)
File /data01/anaconda3/envs/dspy/lib/python3.13/site-packages/dspy/adapters/base.py:25, in Adapter.call(self, lm, lm_kwargs, signature, demos, inputs, _parse_values)
24 for output in outputs:
---> 25     value = self.parse(signature, output, _parse_values=_parse_values)
26     assert set(value.keys()) == set(signature.output_fields.keys()), f"Expected {signature.output_fields.keys()} but got {value.keys()}"
File /data01/anaconda3/envs/dspy/lib/python3.13/site-packages/dspy/utils/callback.py:234, in with_callbacks..wrapper(instance, *args, **kwargs)
233 if not callbacks:
--> 234     return fn(instance, *args, **kwargs)
236 # Generate call ID as the unique identifier for the call, this is useful for instrumentation.
File /data01/anaconda3/envs/dspy/lib/python3.13/site-packages/dspy/adapters/chat_adapter.py:85, in ChatAdapter.parse(self, signature, completion, _parse_values)
84 if fields.keys() != signature.output_fields.keys():
---> 85     raise ValueError(f"Expected {signature.output_fields.keys()} but got {fields.keys()}")
87 return fields
ValueError: Expected dict_keys(['reasoning', 'answer']) but got dict_keys([])

class BasicQA(dspy.Signature):
# question = dspy.InputField()
reasoning = dspy.InputField()
answer = dspy.OutputField()
generate_answer_with_chain_of_thought = dspy.ChainOfThought(BasicQA)
generate_answer_with_chain_of_thought(reasoning=dev_example.question)
=================================================================================
fields : [{'reasoning': 'This is where I explain how I came up with the answer.', 'answer': 'This is the final answer.'}, {'reasoning': 'I need to add two numbers together: 2 and 2. Addition is the operation that combines these two quantities. Starting from 2, if I add 2 more, I count up two places: 3, 4. Therefore, 2 plus 2 equals 4.', 'answer': '4'}, {'reasoning': '{here I will write my thought process}', 'answer': '{and here the final answer}'}, {'reasoning': "The sky appears blue due to a phenomenon called Rayleigh scattering. Rayleigh scattering describes how light is scattered by particles in the atmosphere that are smaller than the wavelength of visible light. Sunlight consists of various colors, each with different wavelengths, ranging from red (longer wavelength) to violet (shorter wavelength). Blue light has a shorter wavelength compared to other visible colors. When sunlight enters the Earth's atmosphere, the gas molecules cause the light to scatter in all directions. Shorter wavelengths, like blue and violet, are scattered more than longer wavelengths because they are scattered by smaller particles. Although violet light is scattered even more than blue light, our eyes are more sensitive to blue light, and the sun emits more energy in blue than in violet wavelengths. Therefore, the sky appears blue to the human eye.", 'answer': 'The sky appears blue due to Rayleigh scattering, where shorter wavelengths like blue are scattered more by the atmosphere, making the sky appear blue to observers on Earth.'}]
signature : StringSignature( -> reasoning, answer
instructions='Given the fields reasoning, produce the fields answer.'
reasoning = Field(annotation=str required=True json_schema_extra={'prefix': "Reasoning: Let's think step by step in order to", 'desc': '${reasoning}', '__dspy_field_type': 'output'})
answer = Field(annotation=str required=True json_schema_extra={'__dspy_field_type': 'output', 'prefix': 'Answer:', 'desc': '${answer}'})
)
==========================================================================
It is difficult to configure dspy.Signature because the InputField name is 'reasoning' and the OutputField name is 'reasoning'. Is there a way? I think it's because qwq is a reasoning model.

Maybe use dspy.Predict?

Maybe use dspy.Predict?

Right, i use intro.ipynb.

intro.ipynb is deprecated, it is NOT supported in 2.5+
Please use the tutorials at https://dspy.ai


Cache parsed modules

This PR reworks large parts of the caching API:

UriCache has been split up into several parts:

UriCacheResult is now used to make it more clear the distinction between UriCache and UriCacheFailed (previously one was a record and the later wasn't, which was a horrible idea)
CachedModule is now replaced with CachedInfo which doesn't contain the actual GHC module - this is held separately inside UriCache

CacheableModule is a new class which TypecheckedModule and ParsedModule are instances of. UriCache stores both and the class defines a function for extracting the module from it. I would like to bike shed on this name (and others), since the naming around ModuleCache and GhcModuleCache is getting confusing
ifCachedModule/withCachedModule are now polymorphic in which type of module from GHC they should take.

withCachedModuleAndData still waits for typechecked modules. Would their be use cases of caching data generated from the parsed module?
The first significant benefit we get from this is now document symbols only rely on being able to parse the module, and hie can now respond to requests even when the module doesn't typecheck and there is no cache for it available.
The next milestone would be to cache the renamed module separately from the typechecked module, but as @alanz has pointed out this may be difficult due to how GHC intertwines the two processes.

The principle looks good.  What are your concerns about the cache naming?

@alanz I think having a separate ModuleCache and GhcModuleCache modules is confusing, I would like to see them just merged into the one. I'd also like to see GhcModuleCache renamed to something like AllCaches/GlobalCaches, but I see there's a to-do to move that into ghc-mod-core. I'm not sure what parts would be able to go into ghc-mod though, since any UriCache stuff seems specific to hie.


Add gitignore for Python, Node, VSCode, Visual Studio, and IntellIj

This .gitignore file was generated by PyCharm by right clicking new file > .ignore > Git ignore. I selected the following options:

Python
Node
VSCode
Visual Studio
IntellIj

The only question is where to put this file.


Release files included with XInclude after reading

Next attempt to fix an old bug :) https://github.com/zanyants/mvp.xml/pull/1

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


buf_redux: The last buffer you'll ever need

I noticed I ended up duplicating some work from this repo in buf_redux (which I use in multipart). Since we have the same need for an extensible BufReader, I figure, hey, why not just use buf_redux in Hyper?
Once specialization lands, I'll be using it to elide buffer zeroing for trusted Read impls. It would be cool to have UninitSafe implemented by server::Request so this optimization will apply in multipart.

buf_redux looks interesting! All my current work is trying to get the async IO support done, in the mio branch, which no longer uses a big BufReader.

It'll be cool to see when that's done! I've been wanting to add support in multipart for rotor.

Yes, synchronous I/O is being removed from hyper. A "hypersync" or similar crate will likely exist. I'm close to merging that into master, so I'm going to close this issue for now. Thanks for the suggestion though!


[cs] use trait suffix for traits to prevent opening

Honesty first :1st_place_medal:

Hey, sorry to dig up this old (merged) PR.
I'm curious about the ideas in favor of these modifications.
You mention "Honesty", I'm not to sure towards who or what?
I don't understand how mentioning the type helps.
How about suffixing class names with Class?
You also mention "prevent[ing] opening", could you elaborate on that point, please?
Feel free to point me to a more suitable place to talk about that, or to ignore my message (I understand that I'm digging an old thread, which might lead to no answer, no worries).

Hi,
no problem :+1:
I would copy-paste this a post where I focus on how naming helps with legacy:
https://tomasvotruba.com/blog/2019/05/02/alias-as-a-code-smell


HBASE-23154 list_deadservers return incorrect no of rows

No of rows should be equivalent to no of dead region servers but mistakenly included current system time in it.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
0m 50s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

:green_heart:
mvninstall
7m  9s
master passed

:green_heart:
javadoc
0m 17s
master passed

_ Patch Compile Tests _

:green_heart:
mvninstall
6m 16s
the patch passed

:broken_heart:
rubocop
0m 11s
The patch generated 1 new + 166 unchanged - 0 fixed = 167 total (was 166)

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
javadoc
0m 16s
the patch passed

_ Other Tests _

:green_heart:
unit
7m  3s
hbase-shell in the patch passed.

:green_heart:
asflicense
0m 15s
The patch does not generate ASF License warnings.

23m 35s

Subsystem
Report/Notes

Docker
Client=19.03.3 Server=19.03.3 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-717/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/717

Optional Tests
dupname asflicense javac javadoc unit rubocop

uname
Linux 527d432f7afb 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-717/out/precommit/personality/provided.sh

git revision
master / 1aee5f0552

Default Java
1.8.0_181

rubocop
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-717/1/artifact/out/diff-patch-rubocop.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-717/1/testReport/

Max. process+thread count
2776 (vs. ulimit of 10000)

modules
C: hbase-shell U: hbase-shell

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-717/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) rubocop=0.75.0

Powered by
Apache Yetus 0.11.0 https://yetus.apache.org

This message was automatically generated.


Fix headers in README.md

Some of the third level headers didn't have a space between the hashtags and the text, so this PR fixes that

oh theres already a pr that fixes that


xnresize: Add version 1.00

XnResize: A fast, powerful and free cross-platform image resizer.

Use Copy over persist method for xnresize.ini

Sorry, I don't understand what it means.

Copy the file form persist on installation
Copy the file to persist on uninstallation

The xnresize.ini file is locate in $APPDATA\XnResize, copy this file to persist folder? why I need to do this?

Open xnresize
Change configuration
Close xnresize
Open folder APPDATA\Xnresize
Copy xnresize.ini to $dir
Rename folder APPDATA\Xnresize to xnresize.backup
Launch xnresize
Change settings
Notice that configuration file was changed in $dir

OK, understand.

The xnresize.ini file seems not support hard link. XnResize will break the link.

As every QT application. Thats why I tell you to use copy over method

/verify


Minimum not version is not correct on How to Contribute wiki page

At https://github.com/Microsoft/vscode/wiki/How-to-Contribute#installing-prerequisites, it says:

You'll need git and a recent version of Node.JS (any v6.x is recommended, on Windows you need at least v6.x). nvm is also highly recommended.

However, I was not able to build with v6.x. Perhaps the minimum now is v7.x?

Yes, that info is outdated.
I always use the version that comes with VS Code's Electron version. Currently this is 7.4.


vertical orbital dystopia

Add:
vertical orbital dystopia (child of abnormal eye distance/ position MP:0001299 AND abnormal orbit morphology MP:0010030 )
DEF: the orbits do not lie on the same horizontal plane, that is, one eye is lower than the other
EXACT SYNONYMS: misaligned eyes; unequal eye height; eyes at different heights; vertical misalignment of the orbits; uneven eyes
SOURCE: HP:0030867
Annotation in J:169366

vertical orbital dystopia MP:0030253


Failed to conform to ES5.1, Section 8.7.2 PutValue (V, W), [[Put]], Step 2.b

It seems to me that S5 does not conform to ES5.1, Section 8.7.2 PutValue (V, W), [[Put]], Step 2.b.
For the following test program:
// 8.7.2 PutValue (V, W), [[Put]], Step 2.b

// 2. If the result of calling the [[CanPut]] internal method of O with argument P is false, then
//     a. ...
//     b. Else return.

// For [[Put]] for a reference with a primitive base,
// if [[CanPut]] returns false, and Throw is false, then it does nothing.

// NOTE: In this example, [[CanPut]] returns false, because 'writable' is false.

Object.defineProperty(Number.prototype, "x", { "value" : 0, "writable" : false, "enumerable" : true, "configurable" : true });
try {
  1["x"] = 10; // Nop
} catch (e) {
  $ERROR('Object.defineProperty(Number.prototype, "x", { "value" : 0, "writable" : false, "enumerable" : true, "configurable" : true }); 1["x"] = 10; does nothing. Actual: ' + e);
}

S5 throws an exception, while it should have succeeded:
$ ./s5-test262  /tmp/03.js
../envs/es5.env:6:0-5029:0
<unknown>:13:-1--4
<unknown>:13:-1--4
<unknown>:13:-1--4
<unknown>:16:-3--179
<unknown>:16:-3--9
../envs/es5.env:977:28-983:3
../envs/es5.env:980:11-982:5
../envs/es5.env:287:28-293:1
Uncaught exception: {[#proto: @9, #class: "Object", #extensible: true,]
 'message' : {#value "Unbound identifier: $ERROR" ,
              #writable true ,
              #configurable false}}

Fatal error: exception Failure("Runtime error")

Is there anything that I'm missing?

Is it because S5 supports only strict mode?

Not applicable in the strict mode.