Session / Cookies not cleared between tests

I use a custom login command, as follow :
Cypress.Commands.add("login", (email: string) => {
  cy.session(`login ${email}`, () => {
    const now = Date.now();

    cy.visit("/login");
    cy.get('[data-test="login-email"]').type(email);
    cy.get('[data-test="login-submit"]').click();
   ...
  });
});

When running locally, with cypress:run, everything is working perfectly fine and the tests start with a signed out user regardless of the previous ones. However when running it through github actions, the signed in session persists between my tests and thus create chaos all around. Is there any additional configuration necessary to ensure test isolation with this github action ?

Thanks for your answer @MikeMcC399
Here is my workflow :
name: ci preview
# https://docs.github.com/en/actions/reference/events-that-trigger-workflows
on: [deployment_status]
jobs:
  e2e:
    # only runs this job on successful deploy
    if: github.event_name == 'deployment_status' && github.event.deployment_status.state == 'success' && github.event.deployment_status.environment == 'Preview'
    runs-on: ubuntu-latest
    steps:
      - name: Checkout 🛎
        uses: actions/checkout@v3
      - name: Install Vercel CLI
        run: npm i -g vercel@latest
      - name: Link preview alias url to new deployment
        run: vercel alias --token=${{ secrets.VERCEL_TOKEN }} --scope=${{secrets.VERCEL_ORG_ID}} set ${{ github.event.deployment_status.target_url }} ${{ secrets.PREVIEW_URL }}
      - name: Run Cypress 🌲
        uses: cypress-io/github-action@v6
        with:
          record: true
        env:
          CYPRESS_BASE_URL: https://${{ secrets.PREVIEW_URL }}
          CYPRESS_IMAP_EMAIL: ${{ secrets.CYPRESS_IMAP_EMAIL }}
          CYPRESS_RECORD_KEY: ${{ secrets.CYPRESS_RECORD_KEY }}
      - name: Upload Cucumber Report
        run: npm run cypress:upload

It is worth mentioning I'm using https://github.com/badeball/cypress-cucumber-preprocessor ; however since test isolation is working perfectly fine with it locally I do not suspect it to be at cause.

@thibautvdu
I don't see any problem with your workflow which could cause this issue.
(Just one unrelated comment, that you probably don't need -g when you install vercel.)
Which version of Cypress are you using?

@MikeMcC399
I am using the latest version ( 13.1.0 ).
I made some progress ; it seems to be linked with the following issue :
#https://github.com/cypress-io/cypress/issues/1208
I could check that the session local storage was cleared correctly in both cases, but somehow, the indexed databases are only cleared when I run cypress locally, but not through github actions.
I applied the fix mentioned in #https://github.com/cypress-io/cypress/issues/1208#issuecomment-727628571
Now I'm left with another issue : restoring the session works locally but not on the github action ; my guess is that in the same way that the indexed dbs are not deleted between tests, they are not restored either on github. Any help with that last issue, or a cleaner way to deal with the first, are welcome !

@thibautvdu
The Cypress documentation does not cover the use of IndexedDB at all. It does however refer to the related @this-dot/cypress-indexeddb plugin in the Plugins > Custom Commands section. You might find that plugin useful.
You may find users with related experience in the Cypress technical community on Discord who could help with your "how-to" questions:

(click on button)
It does not look like your issue is caused by github-action itself as the action's calls corresponding to your workflow are basically just equivalent to:
npm ci
npx cypress run --record

Thanks for your answers @MikeMcC399
I will close this issue since it is now a duplicate of https://github.com/cypress-io/cypress/issues/18350 , which mention the exact same need of having indexed dbs handled by cypress sessions and offer a workaround.
Strangely I still confirm that the indexed dbs get cleared upon each test run locally on my machine and not on github, with both electron and chrome, and that they also get restored along with cy.session. That last point doesn't need further investigation on my side since I have to implement a workaround for github anyway.

Thanks for your answers @MikeMcC399
I will close this issue since it is now a duplicate of https://github.com/cypress-io/cypress/issues/18350 , which mention the exact same need of having indexed dbs handled by cypress sessions and offer a workaround.
Strangely I still confirm that the indexed dbs get cleared upon each test run locally on my machine and not on github, with both electron and chrome, and that they also get restored along with cy.session. That last point doesn't need further investigation on my side since I have to implement a workaround for github anyway.

@thibautvdu

It's good that you found the feature request https://github.com/cypress-io/cypress/issues/18350! Thanks for posting that link!


s3fs 1.80

close #43

Merged in https://github.com/Homebrew/homebrew-fuse/commit/602d945ea33d6a7ef9d96fd5b9fe56dc83591893. Thank you for your contribution to Homebrew @andyli; we appreciate it! :smiley_cat:


Incorrect placement of thumbnail image

The image below displays a leaflet app utilising the stac-layer to properly align the thumbnail with the map.

Looking at the top left, we can see that there is good agreement between the placement of the thumbnail and the bounding box.

However, as we move towards the east and south, the image appears to be scaling incorrectly.

This occurrence isn't isolated; it's noticeable across various items I've been looking at across other datasets in Planetary Computer.
STAC Item - https://planetarycomputer.microsoft.com/api/stac/v1/collections/esa-worldcover/items/ESA_WorldCover_10m_2021_v200_S57W069
STAC thumbnail - https://planetarycomputer.microsoft.com/api/data/v1/item/preview.png?collection=esa-worldcover&item=ESA_WorldCover_10m_2021_v200_S57W069&assets=map&colormap_name=esa-worldcover&format=png
I'm curious to know if this apparent scaling inconsistency is a known issue.
I have a theory that the root of this issue lies with irregularly shaped polygons. As the map extends downwards, the code seems to be struggling to scale the image accurately while maintaining spatial accuracy.

Just seen a candidate for the issue:
https://github.com/stac-utils/stac-layer/blob/main/src/index.js#L114
If the thumbnail scales to only 5 points in a BBOX rather than the polygon itself, it would scale incorrectly.

Hello.  Thanks for submitting this issue.  Happy to help get to the bottom of it.
Do you know what projection the thumbnail is in?  If the thumbnail is in a different projection than EPSG:3857 or EPSG:4326, that could potentially account for the issue.

Thanks for the quick response!
The polygon and BBOX are both in 4326, but the PNG thumbnail doesn't have a coordinate system, it's just a regular PNG from the rendered_preview STAC asset.

For thumbnails without any metadata we can just make a guess anyway, right?
The other issue is that L.imageOverlay (that's what we use to render the image) only allows to provide bounds. I'm not sure whether it's really our aim with stac-layer to show previews pixel-perfect.

I agree with your points on the Leaflet limitations and the educated guess approach for thumbnails without metadata. Closing this issue makes sense at this stage. We'll keep track of any updates that could enable us to revisit this.


ProjectToSingle breaks if using Automapper 4.1.1

Possibly other extensions may be broken when using Automapper 4.1.1

If you grab https://github.com/AutoMapper/AutoMapper.EF6/blob/master/src/AutoMapper.EF6/EntityFrameworkExtensions.cs and add it directly to your project, it works fine. I think it is just the Nuget package config that is broken, but I'm afraid I don't understand enough about Nuget (specifically testing dev packages) to generate a PR with a fix.
Anyway, it looks like it could be this line of the project.json:
https://github.com/AutoMapper/AutoMapper.EF6/blob/master/src/AutoMapper.EF6/project.json#L17

The problem with ProjectToSingle is caused by this line:
https://github.com/AutoMapper/AutoMapper.EF6/blob/master/src/AutoMapper.EF6/EntityFrameworkExtensions.cs#L60
The QueryableExtensions in Automapper 4.1.1 no longer contain a method ProjectTo with the following signature:
  queryable.ProjectTo<TDestination>().Decompile().Single();

Looking at the source for QueryableExtensions in Automapper 4.1.1, it looks like this will need to be changed to:
 queryable.ProjectTo<TDestination>(null, Mapper.Engine).Decompile().Single();

I have modified my code to use the above method from QueryableExtensions rather than the ProjectToSingle from the EntityFrameworkExtensions.
However, you will need to fix the EntityFrameworkExtensions methods to work with Automapper 4.1.1 for it to be of any use.

I pushed out a new version. That broke because of 4.0 using optional parameters. I don't use optional parameters anymore.

Ok, I will get the latest package.
Thanks.


Can't have a Spec as a field in another model

As a user I would like to use Spec (and presumably Region) as a field in another pydantic model e.g.
class Foo(BaseModel):
    spec: Spec

This produces the following error:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 205, in __new__
    complete_model_class(
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_model_construction.py", line 534, in complete_model_class
    schema = cls.__get_pydantic_core_schema__(cls, handler)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/main.py", line 643, in __get_pydantic_core_schema__
    return handler(source)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_schema_generation_shared.py", line 83, in __call__
    schema = self._handler(source_type)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 512, in generate_schema
    schema = self._generate_schema_inner(obj)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 784, in _generate_schema_inner
    return self._model_schema(obj)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 591, in _model_schema
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 591, in <dictcomp>
    {k: self._generate_md_field_schema(k, v, decorators) for k, v in fields.items()},
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 947, in _generate_md_field_schema
    common_field = self._common_field_schema(name, field_info, decorators)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 1134, in _common_field_schema
    schema = self._apply_annotations(
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 1890, in _apply_annotations
    schema = get_inner_schema(source_type)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_schema_generation_shared.py", line 83, in __call__
    schema = self._handler(source_type)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 1869, in inner_handler
    from_property = self._generate_schema_from_property(obj, source_type)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 679, in _generate_schema_from_property
    schema = get_schema(
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/scanspec/core.py", line 234, in __get_pydantic_core_schema__
    return handler(source_type)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_schema_generation_shared.py", line 83, in __call__
    schema = self._handler(source_type)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 789, in _generate_schema_inner
    return self.match_type(obj)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 875, in match_type
    return self._unknown_type_schema(obj)
  File "/home/vid18871/projects/bluesky/blueapi/venv/lib64/python3.10/site-packages/pydantic/_internal/_generate_schema.py", line 415, in _unknown_type_schema
    raise PydanticSchemaGenerationError(
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'scanspec.specs.Spec'>. Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.

If you got this error by calling handler(<some type>) within `__get_pydantic_core_schema__` then you likely need to call `handler.generate_schema(<some type>)` since we do not call `__get_pydantic_core_schema__` on `<some type>` otherwise to avoid infinite recursion.

For further information visit https://errors.pydantic.dev/2.8/u/schema-for-unknown-type

I also tried this, but got the same error:
@discriminated_union_of_subclasses
class Foo(BaseModel):
    spec: Spec

Can you try with @uses_tagged_union instead of @discriminated_union_of_subclasses ?

@DiamondJoseph same error


Update the URL returned by !help

#646

Merged in https://github.com/Just-Some-Bots/MusicBot/commit/949a4b608973d0aaafd18c7c7b9e0149b36516a6.


show and filter by tags on user interface

This adds functionality to show tags on the user interface, and allows users to filter by tags.  tags only appear on the the source_sets#index view.
Basic CRUD interfaces for tags were added in PR#84; however, tags were only visible to logged-in admins.  This PR introduces functionality available to non-logged-in users.
Here is an example of the how the functionality should work:
A user goes to /primary-source-sets/sets?tags[]=dogs and sees only those sets with a tag whose label is dogs.  All of the tags associated with a set (including dogs) are listed beneath each set.
One set also has a tag cats.  The user clicks on cats, and is taken to /primary-source-sets/sets?tags[]=dogs&tags[]=cats.  The users is shown all sets having both cats and dogs tags.
Changes include:

Updating the source_sets#index controller to parse a tags param.

Adding methods the SourceSets model to request sets by tag.

Updating the views to show the tags and allow filtering.

Styling, including changes to the HTML and CSS.  This includes a JavaScript function to ensure that that the dark blue boxes containing the name of each set are the same height in each row.

A system config that allows us specify whether or not to display tags to the end user.  This will help us to manage deployment - admins need time to add all of the tags before we start showing them to the end user.

Thanks, @AudreyAltman! It works nicely.
General questions:

Could the enable_tags setting be renamed to clarify that it's for enabling the display of tags on the front-end?
Can you explain what vocabularies are? (Is this something that needs a tooltip or label within the application?)
I have a hunch that there's some pure CSS way to do some of the dimensional manipulations, or to design around having to do them, but it's probably not worth figuring out at the moment.

Re. /tags/new:

What is the tag's URI for? (It lets me enter an invalid, badly-formed URI, e.g. "not a URI")
The "Vocabularies" label is apparently for a #tag_vocabularies input, which does not exist. There's <input name="tag[vocabulary_ids][]"> but it has no id. This is with or without my having any Vocabularies entered.

Re style.js:

If $(this) can be assigned to a variable in the various scopes in which it's used, it might help to document what it represents each time. Maybe not each time; maybe just in the outermost scope.

Thanks for the feedback, @markbreedlove!
I've changed the name of the enable_tags setting to display_tags_on_public_ui.  After Franky has had a chance to add all the tags, we may consider removing this setting - I don't really see an ongoing need for it, and it might be needless clutter.
I've also assigned a variable name for the outer ($this) in style.js, along with a top-level comment for the function. Let me know if it need further clarification.
I made a ticket to capture your questions about the tags/vocabs interfaces: https://issues.dp.la/issues/8229  They seemed substantive enough for their own PR.

On last thing - I would love to find a pure CSS way to do dimensional manipulations, but far I haven't had any luck.  I agree that it may be wise to put off that work until after our looming deadline.  I'll make a ticket about that, too.

I've just thought of one last thing I need to do on the public user view, so please don't merge yet.

Ok, I made the changes to the public user view.  They apply styles to unpublished sets.  You can see the diff here: https://github.com/dpla/primary-source-sets/commit/fa6f2667897d45bd205c7513aea7cea43919490d

OK, that all looks good! Should I merge it now?

I will :squash: first.

:squash:ed


Is it possible to use SwaggerSchemaFilter to change object schema per action?

I have two action that return the same object. But the resulting json differs slightly depending on conditional serialization.
Is it possible to apply some schema filter or any annotation, so object has a conditional kind of schema depend on action?
E.g. There's a class in the response
class A{
    // ...
    public int A1 { get; set; }
    public int A2 { get; set; }
}

For action 1, I would like to hide property A1, For action 2, to hide property A2. Imagine other classes depend on A, so subclass A is not a good way due to cascading effects, which may cause a lot of duplications down the line.
v5.6.3

For user defined types, schema definitions are generated per type as opposed to per operation. In other words, the definition is generated and placed in a shared location in the Swagger/OpenAPI doc (i.e. components.schemas) and then that same schema is referenced within any operations that use it (e.g. schema = { $ref: "#/components/schemas/A" }) so without fundamentally changing this, which would cause a myriad of other issues, what you're asking for isn't possible.
With that said, property schemas MAY set the ReadOnly flag to indicate if a property should only be applicable for GET requests. You can set this flag by making the property in your class definition readonly, or private/internal set;. So if you're goal is to hide properties for PUT/POST operations but show them for GET, then this might work for you.

Response provided, closing due to inactivity

Hi @domaindrivendev, sorry for necroing this thread - I couldn't find a better one to ask this question!

...property schemas MAY set the ReadOnly flag to indicate if a property should only be applicable for GET requests...

This solves most of my use cases, but I also have some fields that become read-only after the record creation, i.e. they are allowed to be specified in POST requests, and are visible in GET responses, but they can't be edited via PATCH requests.
{
  "id": "qsc142536", // readonly, only shown for GET
  "foo": 1, // non-readonly, shown for all verbs that support bodies
  "bar": 2 // initonly, shown for all verbs except PATCH
}

Is that a scenario Sb can support without me having to create different models for PATCH requests?


[Fix] lidar2cam error in update_infos_to_v2.py for nus and lyft dataset.

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
lidar2cam error in update_infos_to_v2.py for nus and lyft dataset.
In the latest info version, we save the transformation from lidar to camera coordinate system with a unified transformation matrix, but the original implementation does not multiply the rotation matrix with the translation matrix, leading to errors in transformation matrices. This PR fixes this problem, and users should re-convert info with the new script.
This problem does not affect the currently supported models in 1.x but may yield potential errors for BEV-series detectors.
Modification
change the translation from -t to -R^{-1}t

Hi,thanks your PR. I think you need to modify lidar2sensor in lidar_sweeps too. https://github.com/open-mmlab/mmdetection3d/blob/449ecb0e5ea65184f1b3e6fbd41e9a19478afa45/tools/dataset_converters/update_infos_to_v2.py#L306

And lidar2sensor in image dict. https://github.com/open-mmlab/mmdetection3d/blob/449ecb0e5ea65184f1b3e6fbd41e9a19478afa45/tools/dataset_converters/update_infos_to_v2.py#L333

I have fixed the error in sweep.

Hi, I still need to understand this change fully.
## The code snippet from the nuscenes converter

    R = (l2e_r_s_mat.T @ e2g_r_s_mat.T) @ (
        np.linalg.inv(e2g_r_mat).T @ np.linalg.inv(l2e_r_mat).T)
    T = (l2e_t_s @ e2g_r_s_mat.T + e2g_t_s) @ (
        np.linalg.inv(e2g_r_mat).T @ np.linalg.inv(l2e_r_mat).T)
    T -= e2g_t @ (np.linalg.inv(e2g_r_mat).T @ np.linalg.inv(l2e_r_mat).T
                  ) + l2e_t @ np.linalg.inv(l2e_r_mat).T

I think points_new = points @ R + T # here, R is already transposed makes sense, as it can be calculated from:
R_e2g @ (R_l2e @ points_new + T_l2e) + T_e2g = R_e2g_s @ (R_l2e_s @ points + T_l2e_s) + T_e2g_s.
so why the np.matul(R, T) is needed here?
Thank you a lot in advance. This question bothers me for a long time.


Driver doesn't work with Multi-subnet if some subnets are not accessible

Right now getInstance in tds.go only checks the first resolved address from dialer.DialContext. This means that if the AlwaysOn connector has subnets where the app can't reach, the driver will fail to create any connections. https://github.com/denisenkom/go-mssqldb/blob/master/tds.go#L58.
The solution already exist in the code in dialConnection https://github.com/denisenkom/go-mssqldb/blob/master/tds.go#L1115. This code will go through all resolution of the connector and pick one that works before proceeding. This allows the driver to work with AlwaysOn connectors with unreachable unsubnets. PR created: https://github.com/denisenkom/go-mssqldb/pull/422

The current Get Instances function uses UDP port 1434 to port to the SQL Server Browser. This network service lists available SQL Servers and how they can be connected to.

This AlwaysOn connector appears to be describing something else. Here is how we can work on this:

We need a problem statement along with docs.

In your PR you mentioned a link to MS docs. That's great. It looks like this talks TCP and does something different.
I'm uncertain if @denisenkom is familiar with AlwaysOn or similar, but I'm very much in the dark about what it is and when it is used. Can you provide a summary?

We need a proposal of how this code would work and what it would do.
Ideally we would know how to setup a test environment for this, but I understand that this may be difficult.

Sorry for the late reply. I am not super familiar with AlwaysOn connector either. Let me ask some of the SQL engineers to give me some information. I will get back to you with a code proposal that is more flushed out. Thanks


[Issue]: RPP Test Suite - HIP: Link error with OpenMP

Problem Description
3: [ 75%] Linking CXX executable Tensor_misc_hip
3: ld.lld: error: undefined symbol: omp_register_coarse_grain_mem
3: >>> referenced by Tensor_misc_hip.cpp
3: >>>               CMakeFiles/Tensor_misc_hip.dir/Tensor_misc_hip.cpp.o:(_ovlh_hipHostMalloc(void**, unsigned long, unsigned int))
3: >>> referenced by Tensor_misc_hip.cpp
3: >>>               CMakeFiles/Tensor_misc_hip.dir/Tensor_misc_hip.cpp.o:(_ovlh_hipMalloc(void**, unsigned long))
3: clang++: error: linker command failed with exit code 1 (use -v to see invocation)
3: make[2]: *** [CMakeFiles/Tensor_misc_hip.dir/build.make:157: Tensor_misc_hip] Error 1
3: make[1]: *** [CMakeFiles/Makefile2:111: CMakeFiles/Tensor_misc_hip.dir/all] Error 2
3: make[1]: *** Waiting for unfinished jobs....
3: [100%] Linking CXX executable Tensor_hip
3: ld.lld: error: undefined symbol: omp_register_coarse_grain_mem
3: >>> referenced by Tensor_hip.cpp
3: >>>               CMakeFiles/Tensor_hip.dir/Tensor_hip.cpp.o:(_ovlh_hipHostMalloc(void**, unsigned long, unsigned int))
3: >>> referenced by Tensor_hip.cpp
3: >>>               CMakeFiles/Tensor_hip.dir/Tensor_hip.cpp.o:(_ovlh_hipMalloc(void**, unsigned long))
3: clang++: error: linker command failed with exit code 1 (use -v to see invocation)
3: make[2]: *** [CMakeFiles/Tensor_hip.dir/build.make:157: Tensor_hip] Error 1
3: make[1]: *** [CMakeFiles/Makefile2:85: CMakeFiles/Tensor_hip.dir/all] Error 2
3: make: *** [Makefile:91: all] Error 2
3:
3:
3: ./Tensor_hip /opt/rocm-6.4.0/share/rpp/test/HIP/../TEST_IMAGES/three_images_mixed_src1 /opt/rocm-6.4.0/share/rpp/test/HIP/../TEST_IMAGES/three_images_mixed_src2 /root/test/QA_RESULTS_HIP_2024-12-20_20-03-05 0 0 0 0 1 0 0
3: Traceback (most recent call last):
3:   File "/opt/rocm/share/rpp/test/HIP/runTests.py", line 307, in <module>
3:     run_unit_test(srcPath1, srcPath2, dstPathTemp, case, numRuns, testType, layout, qaMode, decoderType, batchSize, roiList)
3:   File "/opt/rocm/share/rpp/test/HIP/runTests.py", line 91, in run_unit_test
3:     result = subprocess.Popen([buildFolderPath + "/build/Tensor_hip", srcPath1, srcPath2, dstPathTemp, str(bitDepth), str(outputFormatToggle), str(case), "0", str(numRuns), str(testType), str(layout), "0", str(qaMode), str(decoderType), str(batchSize)] + roiList + [scriptPath], stdout=subprocess.PIPE, stderr=subprocess.PIPE)    # nosec
3:   File "/usr/lib/python3.10/subprocess.py", line 971, in __init__
3:     self._execute_child(args, executable, preexec_fn, close_fds,
3:   File "/usr/lib/python3.10/subprocess.py", line 1863, in _execute_child
3:     raise child_exception_type(errno_num, err_msg, err_filename)
3: FileNotFoundError: [Errno 2] No such file or directory: '/root/test/build/Tensor_hip'
1/1 Test #3: rpp_qa_tests_tensor_hip_all ......***Failed   18.20 sec

Operating System
ALL
CPU
ALL
GPU
AMD Instinct MI300
Other
No response
ROCm Version
ROCm 6.0.0
ROCm Component
rpp
Steps to Reproduce
Latest Mainline failures
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
No response
Additional Information
No response

OpenMP definition found
grep -ir "omp_register_coarse_grain_mem" /opt/rocm/
grep: /opt/rocm/lib/llvm/lib/libomptarget.so.19.0git: binary file matches
/opt/rocm/lib/llvm/lib/clang/19/include/openmp_wrappers/hip_host_overlay.h:  omp_register_coarse_grain_mem(*p, sz, /*set_attr*/ 0);
/opt/rocm/lib/llvm/lib/clang/19/include/openmp_wrappers/hip_host_overlay.h:  omp_register_coarse_grain_mem(*p, sz, /*set_attr*/ 0);
/opt/rocm/lib/llvm/include/omp.h:    extern void  __KAI_KMPC_CONVENTION  omp_register_coarse_grain_mem(void *, size_t, int);
grep: /opt/rocm/lib/llvm/lib-debug/libomptarget.so.19.0git: binary file matches
/opt/rocm/lib/llvm/lib-debug/src/offload/src/exports:    omp_register_coarse_grain_mem;
/opt/rocm/lib/llvm/lib-debug/src/offload/src/OpenMP/API.cpp:EXTERN void omp_register_coarse_grain_mem(void *ptr, size_t size, int setattr) {
/opt/rocm/lib/llvm/lib-debug/src/openmp/runtime/src/dllexports:	omp_register_coarse_grain_mem       902
/opt/rocm/lib/llvm/lib-debug/src/openmp/runtime/src/include/omp.h.var:    extern void  __KAI_KMPC_CONVENTION  omp_register_coarse_grain_mem(void *, size_t, int);

Definition missing in old
grep -ir "omp_register_coarse_grain_mem" /opt/rocm/
kiriti@simoncat:~/develop/rpp-kiriti/test$ dpkg -l | grep rocm-core
ii  rocm-core                                  <IP_ADDRESS>400-crdnnh.15028~22.04          amd64        Radeon Open Compute (ROCm) Runtime software stack

def found in
nm /opt/rocm/lib/llvm/lib-debug/libomptarget.so | grep omp_register_coarse_grain_mem
00000000017f2f20 T omp_register_coarse_grain_mem

Explicitly adding this lib - libomptarget.so
3: CMake Warning at CMakeLists.txt:194 (add_executable):
3:   Cannot generate a safe runtime search path for target Tensor_hip because
3:   there is a cycle in the constraint graph:
3:
3:     dir 0 is [/opt/rocm/lib]
3:     dir 1 is [/usr/local/lib]
3:     dir 2 is [/opt/rocm/lib/llvm/lib]
3:       dir 3 must precede it due to runtime library [libomptarget.so.19.0git]
3:     dir 3 is [/opt/rocm/lib/llvm/lib-debug]
3:       dir 4 must precede it due to runtime library [libomp.so]
3:     dir 4 is [/opt/rocm-6.4.0/lib/llvm/lib]
3:       dir 3 must precede it due to runtime library [libomptarget.so.19.0git]
3:
3:   Some of these libraries may not be found correctly.
3:
3:
3: CMake Warning at CMakeLists.txt:249 (add_executable):
3:   Cannot generate a safe runtime search path for target Tensor_misc_hip
3:   because there is a cycle in the constraint graph:
3:
3:     dir 0 is [/opt/rocm/lib]
3:     dir 1 is [/usr/local/lib]
3:     dir 2 is [/opt/rocm/lib/llvm/lib]
3:       dir 3 must precede it due to runtime library [libomptarget.so.19.0git]
3:     dir 3 is [/opt/rocm/lib/llvm/lib-debug]
3:       dir 4 must precede it due to runtime library [libomp.so]
3:     dir 4 is [/opt/rocm-6.4.0/lib/llvm/lib]
3:       dir 3 must precede it due to runtime library [libomptarget.so.19.0git]
3:
3:   Some of these libraries may not be found correctly.
3:
3:
3: -- Generating done
3: -- Build files have been written to: /root/test/build
3: [ 25%] Building CXX object CMakeFiles/Tensor_hip.dir/Tensor_hip.cpp.o
3: [ 50%] Building CXX object CMakeFiles/Tensor_misc_hip.dir/Tensor_misc_hip.cpp.o
3: [ 75%] Linking CXX executable Tensor_misc_hip
3: [ 75%] Built target Tensor_misc_hip
3: [100%] Linking CXX executable Tensor_hip
3: [100%] Built target Tensor_hip


Replace "exact separated text fragment(s)" with "exact text fragment(s) separated by semicolons"

This will let us deal with taxonomy strings that include spaces (e.g. k__Bacteria; p__Proteobacteria; c__Gammaproteobacteria; o__Oceanospirillales; f__Halomonadaceae; g__Candidatus Portiera; s__), because those apparently exist. Huh.
This will also make things clearer for users IMO (taking care of this would be sufficient for #123, I think).

SO a problem with only caring about semicolons is that you have problems with the abc; def pattern you see in some taxonomy strings -- you won't get a match for def, since textToRankArray("abc; def") will give you ["abc", " def"].
I guess we could trim each element produced by textToRankArray(), but dang, this is going to be a pain to address.


Added primary key fields to API endpoints

@pujanm  please review it and merge it

@Rashmil-1999 Did you make any changes on the front side?

@Rashmil-1999 build failed. I guess you forgot to run black.


Disable the 'silent' setting for Dogapi.

If the dogapi encounters a network issue (say Net::ReadTimeout), barkdog will continue processing because no exception was raised from dogapi client. This can cause situations where duplicate monitors are created in DD, and the next run of barkdog will fail due to duplicates existing.
Making dogapi fail loudly forces barkdog to not continue in the event the current list of monitors can't be gathered for any reason.

Thanks!


Ldap error when running the operator with IS 6.x.x

Description:
Since the newer 6.x versions of the wso2is removed the ldap userstore connection by default, if you try to run the operator versions of the operator with newer IS 6.x versions, errors similar to the following will occur.
[2023-05-19 14:08:10,228] [] ERROR {org.wso2.carbon.user.core.ldap.LDAPConnectionContext} - Error obtaining connection. Cannot parse url: ldap://localhost:-1 javax.naming.NamingException: Cannot parse url: ldap://localhost:-1 [Root exception is java.net.MalformedURLException: unsupported authority: localhost:-1]
	at java.naming/com.sun.jndi.ldap.LdapURL.<init>(LdapURL.java:115)
	at java.naming/com.sun.jndi.ldap.DefaultLdapDnsProvider.lookupEndpoints(DefaultLdapDnsProvider.java:47)

This issue is already fixed with https://github.com/wso2/k8s-wso2is-operator/pull/19 but added here for tracking purposes

Fixed with #19


Proposal: add return to this language to replace ret

Simply changing return statements to actually say "return" instead of "ret" will make it a lot more readable and pleasant to look at!

@CaptainChloride


Eventless transitions

Opening a new issue to consider / discuss the possibility of adding Eventless Transitions, as proposed by @morungos:
Originally posted by @morungos in https://github.com/kenkunz/svelte-fsm/issues/8#issuecomment-1237430403

I'm just following up on my to-do list. Turns out, that second commit I removed earlier, which was about adding eventless transitions, has been incredibly useful (aka, more or less essential) to our project, and they weren't hard to add in. If you're interested, check out: https://github.com/morungos/svelte-fsm/commit/0955042122b95f94cfca9b62f574e5f23ed92200 I'd be more than happy to make that a pull request too (we don't really want to maintain a fork), but if not, it can stay independently where it is.

Proposed feature / API change
The proposed change is to allow _enter lifecycle actions to return a new state, which may result is a chain of synchronous state changes from a single event invocation. Subscribers would only be notified after the final state change (and only if the resulting state is different that the pre-event state).

I am open to considering this, but I have some initial hesitancy and would like to understand the potential use case(s) better.
My hesitancy is that this adds a lot of complexity and (imho) makes an fsm more difficult to reason about. With the current behavior, an event invocation results in 0 or 1 state changes, and it's easy to follow the causal sequence. With this change, an event invocation could result in arbitrarily many state changes, making it far more difficult to follow the causal chain.
This also opens the door to strange edge cases that would need to be dealt with – e.g., an infinite state change loop.
@morungos (or anyone else interested in this feature) – can you share more about the use cases / scenarios that are driving this request?
Thanks!

Sure. Our main use case was the navigation state in a component. We want the application to be able to, for example, go to the login state, but if it is already logged in, to automatically transition to that state without some derived store having to somehow to swallow the additional states, which might trigger fast renders of components before it settled into a final state. In effect, directing to a login state might transiently flash a login screen even if you're already logged in. We did attempt to use a derived store to skip transitional states but turned out to be somewhat more complex than the entire FSM, and it required unpacking the states into pre-states so we'd know when to ignore. In effect, we would have needed to restructure the state design significantly to make it possible, and even then we'd have a substantially more complex system, with very tight coupling between these two components, when really all we needed was to hide transitory states from the application.
There are other examples, but they were more or less equivalent -- in every case we wanted to be able to request a state, and then, if certain guard conditions were met, eventlessly fall through into a more appropriate state (each state more or less corresponded to a screen) without rendering all the screens along the way.
xstate, for example, does have eventless transitions -- in its full version -- and they are an accepted part of state charts.
Our logic pretty much followed the state charts description: we always need to guarding against certain conditions. And yes, there absolutely is the risk of creating an infinite loop if you get it wrong. There's a warning to that effect on the xstate pages. In fact, there is anyway, even if you attempt to achieve that with a derived store. In fact, it's worse with a derived store because you're now fighting Svelte's stores as well as the FSM.
But, of course, we'd far rather use this module than xstate, which would more or less double our deployment footprint for this one small requirement.

I am open to considering this, but I have some initial hesitancy and would like to understand the potential use case(s) better.
My hesitancy is that this adds a lot of complexity and (imho) makes an fsm more difficult to reason about. With the current behavior, an event invocation results in 0 or 1 state changes, and it's easy to follow the causal sequence. With this change, an event invocation could result in arbitrarily many state changes, making it far more difficult to follow the causal chain.
This also opens the door to strange edge cases that would need to be dealt with – e.g., an infinite state change loop.
@morungos (or anyone else interested in this feature) – can you share more about the use cases / scenarios that are driving this request?
Thanks!

Hi, has there been any movement towards implementing eventless transitions?

@morungos thanks for sharing the details above – this was very helpful.
I'm working to implement this. For consistency, you will be able to return a state from _exit or _enter. Transitions will be followed until no transitions are returned, so you could transition through many states from a single event invocation. I am leaning towards also supporting internal transitions (i.e., transitioning to the current state will still invoke _exit and _enter).
I'll push a public branch soon for feedback.

@kenkunz You might want to look at: https://github.com/morungos/svelte-fsm/commit/0955042122b95f94cfca9b62f574e5f23ed92200, which was my implementation. There's also a few tests. It might give you some ideas.


feat: account design conversion

[x] issue #33
[x] follows contribution guide
[ ] code change includes tests
[ ] breaking change

This PR introduces

Craete account get started screen
Create account password screen
import existing account screen
Secret revovery phrase UI

Merging, thank you. Im realizing now that this flow will need to be changed around some more, but that can be changed in later issues.

Aleight. Thank you. Would be happy to change it some more


"field" does not inherit all "configure" settings

I use "configure" blocks to setup default rendering for my model attributes and associations. However, when I specify fields in the "edit" block with no options, it does not inherit all the settings fields from the "configure" block. Specifically, :unconfirmed_email should not be displayed when creating a new User, but it is.
config.model 'User' do
  configure :unconfirmed_email, :string do
    label "Email changed to:"
    visible do
      bindings[:object].persisted? && bindings[:object].unconfirmed_email.present?
    end
  end

  edit do
    field :unconfirmed_email
  end
end

The :unconfirmed_email field should not be displayed, however it is. On the other hand, the label is correct -- it is displayed for the field definition.

That's expected, because field directive forces visible true.

@mshibuya what is the correct way to use this to get the result I'm expecting?

Omitting edit block will work.


Implementing component manager

Same as parameters.
It should facilitate its usage. However, because we are working python, it probably better to use python lists to store ids.
my_nodes= [1, 2, 3]
mapdl.nsel("S","",my_nodes)

instead of:
mapdl.components["my_nodes"] = "nodes", [1,2,3]

But if we are working with workbench files (ds.dat) files I think this will be appreciated.
Close #1404

Feedback is appreciated @koubaa @akaszynski
However I promised to work on something else this week (which I didn't know it had less days) so I might post-pone this for later.

I have found out that in order for a CM to appear in CMLIST output, you need to have it selected using CMSEL.
This is consistent with geometry API (*LIST commands will not show unselected elements).
However, mapdl.component module API will closely remind you of mapdl.parameter whereas the component behaviour is a bit different than the mapdl.parameters (you don't need to select parameters).
Then this API might look a bit confusing, because it resemble parameters.
Then I raise the following questions:

Should we keep the current approach to manage CMs? Or should we look for an alternative API different enough to not cause confusion?
If we keep the current (on-going) implementation, shall we make pymapdl raise an error if the CM is not selected (expected by mapdl users)? Or shall we select it and carry on (expected by python users)?

My two cents
I would go for the current implementation, and raise an error if the CM is not selected.

@germa89 I'm surprised to see this behavior but I can confirm it. If no components are selected, cmlis returns an empty list.
I think it's ok in the first implementation to do the current implementation, although I don't think it's right to throw an error if there are no selected components. What if there are no components at all?
Eventually, we can use a *GET query or a new backend method instead of relying on parsing the output of CMLIST

@germa89 I'm surprised to see this behavior but I can confirm it. If no components are selected, cmlis returns an empty list.
I think it's ok in the first implementation to do the current implementation, although I don't think it's right to throw an error if there are no selected components. What if there are no components at all?
Eventually, we can use a *GET query or a new backend method instead of relying on parsing the output of CMLIST

I fixed by using *GET which does not depend on the component to be selected or not.
If it is not selected, it will throw and error and recommend you to select it using CMSEL.
If it does not exists, it will throw an exception ComponentDoesNotExists.
I wonder if we should made that PyMAPDL automatically select the component upon selection (this behaviour can be activated using the attribute mapdl.component._lose_mode=True). However for getting all the components listed in CMLIST, I would have to select all of them, and then I would have to keep track of their selection.
I can do it though.

@clatapie  ... again mapdl.download giving issues...

If you want to have "" as an option you should add "" in the Literal: Literal["VOLU", ..., "NODE", ""] or add another literal with "" in the union:
Union[Literal["VOLU", ..., "NODE"], Literal[""]]
This is probably why black cannot parse the file


Smart custom knit doesn't work when --- separator exists in Rmd

When --- separator exists in Rmd file, the smart custom knit doesn't work; instead, it falls back to rmarkdown::render() default.
However, when --- is taken out, the custom knit works again.
This is critical because the --- separator is often used in presentation output.
Reproducible Examples
Example 1: With --- separator.
---
output: bookdown::gitbook
knit: bookdown::render_book
---

# Test

Para.

---

# Next

Example 2: Without --- separator.
---
output: bookdown::gitbook
knit: bookdown::render_book
---

# Test

Para.

# Next

@ElianHugh Maybe caused by how we handle the frontmatter?

Also, I find that live preview does not work with such document using bookdown::render_book:
processing file: main.Rmd

  |
  |                                                                      |   0%

  |
  |......................................................................| 100%
  ordinary text without R code

output file: /Users/ken/.vscode-R/tmp/main.knit.md

Error in relativeTo(basepath, dir) :
  The path /Users/ken/Workspaces/test/rbook/libs/header-attrs-2.11 does not appear to be a descendant of /Users/ken/.vscode-R/tmp/
Calls: cat ... html_dependencies_as_string -> lapply -> FUN -> relativeTo

Backtrace:

1: stop("The path ", file, " does not appear to be a descendant of ",
2: relativeTo(basepath, dir)
3: FUN(X[[i]], ...)
4: lapply(dependencies, makeDependencyRelative, basepath = output_dir,
5: html_dependencies_as_string(dependencies, lib_dir, output_dir)

6: as_tmpfile(html_dependencies_as_string(dependencies, lib_dir,
7: pandoc_html_extras_args(extras, self_contained, lib_dir, output_dir)
8: base(...)

9: output_format$pre_processor(front_matter, input, runtime, knit_meta,
10: rmarkdown::render(file_path, output_format = set_html, output_file = output_file_loc,

11: cat(lim, rmarkdown::render(file_path, output_format = set_html,

Execution halted

[VSC-R] main.Rmd process exited with exit code 1

Looks like rendering to ~/.vscode-R/tmp makes the paths inconsistent.

Should be fixed via #856.


Can't open existing file without open editor window

Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description
Opening an existing file doesn't work if an editing window isn't open already.
Steps to Reproduce

Open Atom (safe mode or normal)
Close Atom editor windows, but not Atom itself
File > Open...

Expected behavior: Finder opens to allow user to browse to the file they want to open.
Actual behavior: Nothing happens.
Versions
Atom    : 1.11.2
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0
OS: Mac OS 10.12.

This is a duplicate of https://github.com/atom/atom/issues/12508. Feel free to subscribe there for updates.


Make a WeChat Miniprogram example

We already have docs: https://casdoor.org/docs/integration/wechat_miniprogram , but no code yet.

@wenxuan70


Could not resolve @nuxt/vite-builder

Environment

Operating System: Windows_NT
Node Version:     v21.7.3
Nuxt Version:     ^3.11.2
CLI Version:      3.13.1
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      compatibilityDate, devtools
Runtime Modules:  -
Build Modules:    -

Reproduction
@nuxt-vite-builder-instalation-error.zip
Describe the bug
I tried to reproduce this problem https://github.com/nuxt/nuxt/issues/28707, but caught this conflict with dependency error.

I also caught error like this but with @nuxt/test-utils
Can you halp me plz
Additional context
No response
Logs
PS C:\reproduce\nuxt-autocomplit-type-error> npm i
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: nuxt-app@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/vue
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nuxt/vite-builder
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/nuxt
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>|| >=3" from<EMAIL_ADDRESS>npm ERR!   node_modules/@unhead/vue
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/nuxt
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!   6 more (@vitejs/plugin-vue, @vitejs/plugin-vue-jsx, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/vue
npm ERR!   peer vue@">= 2.5 < 2.7" from<EMAIL_ADDRESS>npm ERR!   node_modules/@vue/composition-api
npm ERR!     peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/pinia
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!       1 more (@pinia/testing)
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! C:\Users\AppData\Local\npm-cache\_logs\2024-08-29T20_37_06_687Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: C:\Users\AppData\Local\npm-cache\_logs\2024-08-29T20_37_06_687Z-debug-0.log

Does running this in your project directory make a difference?
echo "legacy-peer-deps=true" >> .npmrc

I could not reproduce with npm v10.2.3. I deleted your lockfile and ran npm i and got the following output:


Feature Request, The ability to Create Random JSON object

We are are having to create random json objects for a project of ours, the contents dont matter, it would be a nice feature to be able to generate a randomized one

+1 love this, would happily accept a PR for this, ideally with some options about what things could be returned, how deeply it could possibly be nested, etc.

Ill take a look over the next week into it

Created the first version here  #418.  Let me know your thoughts, I am right now testing it but I am running into some environment issues I need to fix first.

Awaiting feed back  @victorquinn

Any chance you have had a sec to take a look at the way I am going about this?

Checking back in @victorquinn it's passing the travis tests(though its a very simple travis test)


Added spinner stories

We could add a test for small mode with value.

We also need a dark example.

We could add tests for both modes with value 100% to see the entire spinner, and other with other values. Remove the tests without value because the snapshots are going to change all the times.

Done

We also need dark examples.

Overlay mode should be the dark examples.


av1 obu

move av1 obu code from baresip/av1 to re.
AV1 codec is using Open Bitstream Unit (OBU) format.
Ref:
https://github.com/baresip/re/pull/345
https://github.com/baresip/baresip/pull/1835

I wonder if this fits better in baresip/rem? Like the other codec related code (h264, h265...)

I am planning to move all packetizers from rem to re...
This includes h264 and h265 ...
for AV1 it will be obu format, packetizer, depacketizer.
I think it fits well in either re or rem ...?

rem also defines basic types for audio and video.
I am wondering if we should move this also into re ?
what do you think ?

I am wondering if we should move this also into re ?
what do you think ?

Sounds good to me.


Domain activation is Failed - One or more of the CNAMEs you provided are already associated with a different resource

App Id: dv97k1v3h2snr
Region: ap-southeast-1
Step: Domain activation
Status: Failed
Issue/question
We had issues connecting your custom domain: wesoarhigh.com
Error message
One or more of the CNAMEs you provided are already associated with a different resource.
Additional information
Trying to connect an Amplify hosted application as a subdomain served on Netlify.
Followed the steps found here.

Hi @wsh-startup -- This means that the CNAME you are attempting to add is associated with another cloudfront resource.  Check out the following:
https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#cnamealreadyexistsexception-error
https://aws.amazon.com/premiumsupport/knowledge-center/resolve-cnamealreadyexists-error/

Hi @gwryssekk,
We will be checking the links you provided.
However, just to give context and background to what our setup is currently, please see the details below.

Domain name is bought from GoDaddy.
Landing page (static web app) is hosted via Netlify. Pointed domain details from GoDaddy to our Netlify account.
Our Web app (dynamic web app) is hosted at AWS.

What we want to achieve is that our subdomain (ie. platform.wesoarhigh.com) will be accessible from Netlify pointing to a URL hosted at AWS.
Is this setup possible?

Our records indicate you no longer have a custom domain associated with this app. Re-open if you're still having issues.


5.40 breaks type of webpack-dev-server

Bug report

What is the current behavior?

If the current behavior is a bug, please provide the steps to reproduce.

install webpack and @types/webpack-dev-server
create a variable of type Configuration fromwebpack
Try to access its devServer property

What is the expected behavior?
For webpack 3.38.1, this works

Other relevant information:
webpack version:  5.40.0
Node.js version: v16.3.0
Operating System: macOS 11.4
Additional tools: TypeScript 4.3.2 and<EMAIL_ADDRESS><EMAIL_ADDRESS>also reproduces this issue

Feel free to send PR

Feel free to send PR

:cold_sweat:I notice it doesn't seem to have a declaration file

@alexander-akait
Hi, I tried to solve it, but found yarn run special-lint-fix
type IsAnyReplaceObeject<T> = true extends T & false ? {[Key: String]: Any} : T; type DevServer = IsAnyReplaceObeject<import(‘webpack-dev-server’).Configuration>
Finally, types.d.ts will become DevServer: {[key: string]: any }
Is there any way to skip compiling import(‘webpack-dev-server’).Configuration ?
The extension type in webpack-dev-server does not seem to be automatically recognized

We will need clarification on the appropriate fix for this bug.
This issue says that a PR is appropriate, but #13666 was closed.  webpack ships its own types which eliminates the need for @types/webpack.  Yet in #13666, it is claimed that the webpack-dev-server types should remain in DefinitelyTyped.  This seems contradictory and so is likely to confuse anyone attempting a fix for this issue.

@types/webpack-dev-server extends the webpack typings with the devServer property:
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/415b6859c78cc7fe694fb12a10ea88f1fadfe958/types/webpack-dev-server/index.d.ts#L347-L355
For this to work webpack must not provide a devServer property in Configuration.
This seems fine and nothing has changed between these version.

Make sure you don't have @types/webpack installed (yarn why/npm ls @types/webpack)
Make sure you don't have webpack installed below @types/webpack-dev-server (yarn why/npm ls webpack)
Make sure you don't have multiple versions of webpack or @types/webpack-dev-server installed

The confusion is as follows:
webpack 5 bundles types, eliminating the need for @types/webpack
Does webpack also want to bundle types with the dev server to eliminate the need for @types/webpack-dev-server?
Avoiding @types/webpack and yet requiring @types/webpack-dev-server is inconsistent.  If this is the intended approach, a documentation update can avoid the confusion.
Regardless of the answer, it may necessitate a documentation update: https://webpack.js.org/configuration/configuration-languages/
But I think the update will be different depending on the answer.

We should add types to webpack-dev-server

Does webpack also want to bundle types with the dev server to eliminate the need for @types/webpack-dev-server?

No webpack doesn't want to bundle dev server types. They are not part of webpack.
What you want is webpack-dev-server bundling it's own types.

I think we will do it for 4.1

I think that's a breaking change so it should be a major release...

What you want is webpack-dev-server bundling it's own types.

Yes, that is precisely what I was asking:  "Does the webpack team want to do that?"

Yes, we want to add types for webpack-dev-server


Discovery not working?

I tried modifying the P2P example from issue #36 to make use of discovery:
index1.js
var th = require('telehash'),
    fs = require('fs');

var ENDPOINT_FILE = process.env.ENDPOINT;

th.load({id:ENDPOINT_FILE}, function (e,mesh) {
  if (e) throw e;
  console.log(mesh.uri());

  mesh.discover(true);

  mesh.accept = function (from) {
    console.log("INCOMING:", from.hashname);
    var link = mesh.link(from),
        chan = link.stream();
    chan.write("Hello?");
    var i = 0;
    setInterval(function () {
      chan.write("Test #"+(++i));
    }, 5e3);
    chan.on('data', function (d) {
      console.log("DATA:", d.toString());
    });
  };
});

index2.js
var th = require('telehash'),
    fs = require('fs');

var ENDPOINT_FILE = process.env.ENDPOINT;

th.load({id:ENDPOINT_FILE}, function (e,mesh) {
  if (e) throw e;
  console.log(mesh.uri());

  mesh.discover(true);

  mesh.accept = function (from) {
    console.log("INCOMING:", from.hashname);
    mesh.link(from);
  };

  mesh.stream(function (from, args, accept){
    var chan = accept();
    chan.on('data', function (d) {
      d = d.toString();
      console.log("ECHO:", d);
      chan.write(d.toUpperCase());
    });
  });
});

Nothing happens, in particular no "INCOMING" messages are logged.  Is there something I should be doing differently?

Yeah, same here. Any help?

Hey folks. sorry for the delay. I just pushed some commits to branch 0.3.30, though be warned I'm still in the process of tackling https://github.com/telehash/telehash-js/issues/36. Once I get the reconnect working smoothly I'll publish to npm but for now see if this helps:
npm install git+https://github.com/telehash/telehash-js#0.3.30

thoroughly fixed and example added (./examples/echo) in 0.4.0
Note: due to async crypto and handshakes, must create stream INSIDE the link.status handler (i.e once handshaking has completed and the link is fully up).


Verify NAND programming on revC

There were some spurious errors while reading ONFI-like NAND with revB, it's unclear if they were caused by FXMAs or something else.

I've did a lot of experimenting and it looks like the spurious errors observed on revB are gone. But I'm still not sure where to attribute the random-ish bit errors. Sure, these could be just the flash unreliability, but I feel like that's not the only reason.
Specifically, I've tried reading out the same 1 GiB flash a few times, then XOR'd them together, then looked at the difference. Mostly, I was interested in whether there are lots of missed pages (no, I think there aren't any?) but I've noticed that the bit errors aren't that random. In fact most of the non-zero XOR'd bytes were 01 or 08... and IO1 and IO4 had the longest wires in my wiring harness. This doesn't look like a coincidence at all.

xor.rs
use std::fs::File;
use std::env::args;
use std::io::prelude::*;

fn main() {
    let mut args = args();
    args.next().unwrap();
    let in1 = args.next().unwrap();
    let in2 = args.next().unwrap();
    let out = args.next().unwrap();

    let mut data1 = Vec::new();
    File::open(in1).unwrap().read_to_end(&mut data1).unwrap();
    let mut data2 = Vec::new();
    File::open(in2).unwrap().read_to_end(&mut data2).unwrap();

    let mut datao = Vec::new();
    for (x1, x2) in data1.iter().zip(data2.iter()) {
        datao.push(x1 ^ x2);
    }

    let mut fout = File::create(out).unwrap();
    fout.write(&mut datao[..]).unwrap();
}


Bug: HealthEstimateOverlay disappears/disalign when switching maps

As of 0.7.6, DnD 5e 0.98, when I switch maps the healthestimateoverlay stop working properly. Depending on the map, sometimes it greatly disaligns and others it simply disappears all together. Looking at the console it seems the healthestimateoverlay IS rendering, meaning it must be somewhere off-screen?
When returning to the original map, the issue persists, I need to refresh to fix the issue on any map.

Update:
Testing I figured out why this happens:
The
 is originally inside the
, when you switch maps it gets destroyed and is pushed to the body tag. When it is in the body tag it doesnt work properly.

OOC, what version of HealthEstimate are you using? This sounds similar to the issue I reported in https://github.com/Shylight/healthEstimate/issues/5 , which was present in 2.0.2 but seems to have been resolved in 2.0.3

Nevermind... just updated it and its working now! Sorry about this


[SPARK-40532][CONNECT] Add Python Version into Python UDF message

What changes were proposed in this pull request?
This PR adds the Python version from the remote client.
See also:
https://github.com/apache/spark/blob/56c7cf33929d7d42b7d299c0bb7e895963241214/python/pyspark/context.py#L312
https://github.com/apache/spark/blob/603dc5098217d9580f611873165d25392f41cdfe/python/pyspark/worker.py#L682-L691
Why are the changes needed?
In order to make sure to run it in the same Python version of executors.
Does this PR introduce any user-facing change?
No to end users.
Yes for the dev. Now other Python versions can be used for Spark Connect.
How was this patch tested?
Manually tested.

cc @xinrong-meng @grundprinzip @zhengruifeng

Oh, could you resolve the conflict, @HyukjinKwon ?

sure!

All tests passed. Merged to master/3.4.

Thank you!


konf ns should highlight currently selected namespace by default

When running konf ns the first namespace is highlighted even though that one is not necessarily the currently set namespace.  It should have the currently selected namespace pre-selected.  For example, see how kns works.

I want to share what I have found so far:

The item can be selected by passing CurserPos in the this &promptui.Select call.
The curser position only has an effect, if StartInSearchMode is set to false though. I didn't dig deeper than that.


feature/allow custom error handler for iOS

ℹ  Disclaimer: this pull reuqest was started by awesome work of @tomekfab and then finalised by @azubala
Context
We have identified a sporadic issue after performing backup restore (which we call "white screen of death") where after restore is reported to be completed app starts to behave oddly and with few taps user ends up in white screen and nothing can be done. Restarting app leads to clean state of the app and onboarding being presented.
From logs perspective we just see the following log:
[ERROR] : DefaultDatabaseErrorHandler - Corruption reported by sqlite on database: /Users/aleksanderzubala/Library/Developer/CoreSimulator/Devices/5AD4C6F2-4E37-4EDB-AEB5-7C9E6A19A624/data/Containers/Data/Application/C31A8D1C-D031-490B-AB8B-DEC22210860E/Documents/Databases/thefabulous.db
[ERROR] : DefaultDatabaseErrorHandler - deleting the database file: /Users/aleksanderzubala/Library/Developer/CoreSimulator/Devices/5AD4C6F2-4E37-4EDB-AEB5-7C9E6A19A624/data/Containers/Data/Application/C31A8D1C-D031-490B-AB8B-DEC22210860E/Documents/Databases/thefabulous.db
[DEBUG] : Database - Database created

We have invested a lot of time in the bug investigation (full story in comments in the corresponding story: https://trello.com/c/lfViyH2A) but it turns out that the bug can be reproduced at best 1-2 times out of 10 tries.
Steps to reproduce bug recorded here.
Details
In order to be able to be able to react on the corruption db event we need to provide custom error handler when creating database. This pull reuqest extends constructor of IOSOpenHelper to pass DatabaseErrorHandler implementation when creating new DB.

@kmalmur change for Android open helper pushed: https://github.com/thefabulous/squidb/pull/2/commits/2b4749ae8b6ae20d8086086e7178b4ed0ffd9e68


Nether Dungeon

Like overworld, except nether-ry.
What will actually spawn from these?

Pigmen wouldn't make sense. Wither skeleton would be a good idea. And they could be made out of NetherCobble. And how about some compact Netherack in the treasure? and a epic-ly rare netherstar?

Idea validated! Wil put it on the todo list :)


White header since the last few days.

It's probably due to some recent changes on Google's part, but the header added by your extension is now white instead of blue; making the search bar and the button to the left of the account button invisible.
This is in Firefox.

Hello,
I have the same issue on latest Chrome version.
Regards,

Same issue.

I pushed the fix to the Google Chrome Store for Edge/Chrome.
@johnrandy Can you update the Firefox plugin?

All I have fixed the Google Chrome extension it will update or you can download the plugin manually.
@jonrandy can you update Firefox?

Will do asap, on vacation right now
On Sun Oct 22, 2023, 05:39 PM GMT, Joey Troy @.***> wrote:

All I have fixed the Google Chrome extension it will update or you can download the plugin manually.
@jonrandy https://github.com/jonrandy can you update Firefox?
—
Reply to this email directly, view it on GitHub https://github.com/team-inbox/inbox-reborn/issues/80#issuecomment-1774154358, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALQWMX3PQVSP7BEFOABIMTYAVK6PAVCNFSM6AAAAAA6JVZOHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZUGE2TIMZVHA.
You are receiving this because you were mentioned.Message ID: @.***>

Done


Surprising behaviour for integer kernel_size in linen.Conv

I was quite surprised with how linen.Conv treats int as an argument for kernel_size
key1, key2 = jax.random.split(jax.random.PRNGKey(0), 2)
image = jax.random.normal(key1, (8, 256, 256, 3))
conv = flax.linen.Conv(features=48, kernel_size=5)
params = conv.init(key2, image)

This errors on the last line with
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
google3/third_party/py/numpy/core/fromnumeric.py in _wrapfunc(obj, method, *args, **kwds)
     55     try:
---> 56         return getattr(obj, method)(*args, **kwds)
     57

AttributeError: 'tuple' object has no attribute 'take'

During handling of the above exception, another exception occurred:

IndexError                                Traceback (most recent call last)
11 frames
google3/third_party/py/numpy/core/fromnumeric.py in _wrapit(obj, method, *args, **kwds)
     44     except AttributeError:
     45         wrap = None
---> 46     result = getattr(asarray(obj), method)(*args, **kwds)
     47     if wrap:
     48         if not isinstance(result, mu.ndarray):

IndexError: index 3 is out of bounds for size 3

And I can see it creates a kernel for only 1 spatial dimension.
So it seems it says 5 == (5,)
Changing to conv = flax.linen.Conv(features=48, kernel_size=(5,5)) fixes the error.
Overall I find:
a) the error is cryptic
b) if this is the desired behaviour, perhaps it should only accept kernel_size as a sequence of ints?

Your input is of shape (8, 256, 256, 3), and when you specify a 1D kernel you are applying a 1D convolution. This doesn't work on your input shape, which expects 2D convolutions (your have 2 spatial dimensions). So you can fix this by reducing your input to one special dimension:
from flax import linen as nn
import jax

key1, key2 = jax.random.split(jax.random.PRNGKey(0), 2)
image = jax.random.normal(key1, (8, 256, 4))
conv = nn.Conv(features=48, kernel_size=3)
params = conv.init(key2, image)

Closing this for now but please re-open if you think I missed something!

I think we want to keep this open as we want to get rid of flax's magic integer --> tuple conversion here


Commenting using ctrl+k,ctrl+c does not work for JSX files

Block commenting using ctrl+k,ctrl+c does not work for JavaScript React JSX files.

To clarify, none the commands in the following list work form when working with jsx files with a jsx syntax.

Version 0.10.1
Commit df352367df2efcfa9d602d471e4e2f42140a0f05
Date 2015-11-17T15:25:33.342Z
Shell 0.34.1
Renderer 45.0.2454.85
Node 4.1.1

Version <= 0.10.1
Same here.

It was an oversight that we didn't add the a language.configuration.json definition for .jsx files.

Is this something that we could work around by changing a configuration locally until the fix is officially released? I'm looking through the changes now and trying to figure out how that maps to the installed product on Windows.

These are no code changes and only configuration changes, so you can patch your installation with these changes.
In the installed product the corresponding folder is resources\app\extensions\javascript.

That's great! Thanks @egamma, it has bother me for few days.


Dynamic Themes using Tabs

I keep getting an error when I try to use the dynamicthemewidget change color method inside of the tabbar or tabbar view. How can I fix this?

Sorry, I'll need a bit more information.
Do you have any code samples?


Deploying to Heroku?

My bot is done, looking for some docs on deploying but didn't find any. Any tips? The tunnel seems to start up and listens on localhost on heroku... I do have some log entries though:
2018-05-14T17:45:31.653849+00:00 heroku[router]: at=error code=H10 desc="App crashed" method=GET path= "/webhook?hub.mode= subscribe&hub.challenge= 733323090&hub.verify_token=delamorandiere" host=fast-lowlands-28084.herokuapp.com request_id=31aaa7e9-4372-42e6-988c-7d6ae11871c3 fwd="<IP_ADDRESS>" dyno= connect= service= status=503 bytes= protocol=https

I have the same issue, how did you solve this ?


Add recommendation field name configuration to Meta Review Stage

Add a configuration setting "Meta Review Recommendation Field Name" to the Meta Review Stage that sets 'recommendation' as the default and allows PCs to change the value, like they do in the Review Stage configuration.
'recommendation' is stored in group content.meta_review_recommendation and is called by the PC, SAC, and AC consoles for display.

Fixed here: https://github.com/openreview/openreview-py/pull/2025


Android studio does not recognize flutter plugin java source code.

Steps to Reproduce

use this command to create a flutter plugin project:

flutter create --org com.hoyo.example --template=plugin install
import the project to AS(3.4.1)

The AS can NOT recognize java source code,even though the source code exists in the folder.

Logs

[✓] Flutter (Channel stable, v1.5.4-hotfix.2, on Mac OS X 10.14.1 18B75, locale zh-Hans-HK)
    • Flutter version 1.5.4-hotfix.2 at /Users/xiaohongyao/Work/flutter
    • Framework revision 7a4c33425d (4 weeks ago), 2019-04-29 11:05:24 -0700
    • Engine revision 52c7a1e849
    • Dart version 2.3.0 (build 2.3.0-dev.0.5 a1668566e5)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/xiaohongyao/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✗] iOS toolchain - develop for iOS devices
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
    ✗ libimobiledevice and ideviceinstaller are not installed. To install with Brew, run:
        brew update
        brew install --HEAD usbmuxd
        brew link usbmuxd
        brew install --HEAD libimobiledevice
        brew install ideviceinstaller
    ✗ ios-deploy not installed. To install:
        brew install ios-deploy
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without resolving iOS dependencies with CocoaPods, plugins will not work on iOS.
        For more info, see https://flutter.dev/platform-plugins
      To install:
        brew install cocoapods
        pod setup

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 35.3.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Android Studio (version 3.0)
    • Android Studio at /Applications/Android Studio 2.app/Contents
    • Flutter plugin version 23.2.1
    • Dart plugin version 171.4424
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] IntelliJ IDEA Ultimate Edition (version 2019.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 35.2.2
    • Dart plugin version 191.6183.88

[✓] VS Code (version 1.34.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.0.2

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)

Hi @HoyoShaw
are you still experiencing this issue with the latest version of Flutter?
If so can you please provide your  new flutter doctor -v?
Thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.

I just created a new Flutter plugin by following doc and my Flutter version is the latest one upto now(stable). I did everything even invalidate cache and restart and system restart also. But still the AS did not identifieng plugin source.  Here is a screenshot:

I know that I can add lib manually to AS but is that the expected behaviour?

Duplicate of #https://github.com/flutter/flutter/issues/19830

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.


Line Color not applying in Freehand Draw

When drawing in Freehand draw, setting the line color (Hex) does not change the color of the line.

Test case:
Use branch 290.
Use Ww and Cesium
draw freehand . Set a color in hex (FFFF0036), width = 3. The test is a success if the line changes color, and width. Change the color and width, and test again.

color changes and to go back to original color one have to "exit freehand draw" and commit it.

Reintegrate

Merged into the dev branch. c;losing this issue.


[Feature Request] Automated release drafter SemVer number

Is your feature request related to a problem? Please describe.
All Iter8 repos contain a release drafter GitHub action workflows. However, the workflow does not set the version number or the title of the release draft. We would like to change this so that version numbers and titles are auto populated.
Why is the feature useful for Iter8 users?
Manually entering version numbers is a recipe for violating semantic versioning due to human errors / typos. This feature will help Iter8 maintainers do a cleaner and more confident job of the releases.
Describe the solution you'd like
Compute the next SemVer for a repo... i.e., major.minor.patch will get a patch increment. Modify the release drafter workflow to set version number and title using this incremented SemVer.
https://jon.sprig.gs/blog/post/1175 shows how to do this.
Describe alternatives you've considered
Manual process is now known to be error prone.
Does this issue require a design doc/discussion? If there is a link to the design document/discussions, please provide it below.
There are situations when we actually want to increment the minor version rather than the patch version. We can simply override (manually) the draft version number and title in these situations. Patch version increments are the (very) common case in all our repos.
How will this feature be tested?
Manual. Always pay attention to version numbers during release. If the drafter / new CI does weird things, we should know.
How will this feature be documented?
Appropriate doc strings within the GitHub workflow will suffice.

Done.


Clarification on ModUpdater support

Is it still supported? Should it be removed?
ModUpdater was last updated 2 years ago for 1.16.
This mod checks a file for updates that is also 2 years old.
The reason I bring it up is because it still prints this warning in current versions of Minecraft + BlockMeter which may be confusing to users:
[22:58:05] [main/WARN]: Warnings were found!
 - Mod 'Block Meter' (blockmeter) 1.6 recommends version 1.1.7 or later of modupdater, which is missing!
	 - You should install version 1.1.7 or later of modupdater for the optimal experience.

The CurseForge and Modrinth pages for this mod also mentions ModUpdater.

Good catch, I'll investigate this, https://github.com/ReviversMC/modget-minecraft might be an alternative.

I removed all references to modupdater


TF 2.0 - Gradient of 'tf.keras.layers.Dense with bias' produces non-deterministic result

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): pip install tf-nightly-gpu-2.0-preview==2.0.0.dev20190826
TensorFlow version (use command below): v1.12.1-9705-g0fbc138 2.0.0-dev20190826
Python version: 3.6.9
CUDA/cuDNN version: 10.0.0/7.3.1
GPU model and memory: Titan Xp 11Gb

Describe the current behavior
(1) The following code produces the same 'numpy_data0.pkl', 'initial_params0.pkl', 'loss0.pkl' all the times (which means same data, same parameter, same loss), but 'grad0.pkl' changes. I checked it with 'diff' command between generated files.
(2) It seems only with tensorflow 2.0 GPU version, this happens. I checked the code with tf-nightly-2.0-preview==2.0.0.dev20190830 (CPU version), it was ok. (= shows deterministic result)
(3) Using custom dense layer + tf.keras.layers.ReLU() was ok also. (= shows deterministic result) Custom dense layer was
class MyDenseLayer(tf.keras.layers.Layer):
    def __init__(self, num_outputs):
        super(MyDenseLayer, self).__init__()
        self.num_outputs = num_outputs
    def build(self, input_shape):
        self.kernel = self.add_variable("kernel", initializer=tf.keras.initializers.GlorotUniform(),
                                        shape=[int(input_shape[-1]),
                                               self.num_outputs])
        self.bias = self.add_variable("bias", initializer=tf.zeros_initializer,
                                        shape=[self.num_outputs])
    def call(self, input):
        return tf.matmul(input, self.kernel) + self.bias

And net with
net = tf.keras.Sequential()
net.add(MyDenseLayer(100))
net.add(tf.keras.layers.ReLU())
net.add(MyDenseLayer(100))
net.add(tf.keras.layers.ReLU())
net.add(MyDenseLayer(1))
net.build((None, input_dim))

(+) When 'use_bias=False' option applied on hidden layers, is was ok. (= shows deterministic result)
Describe the expected behavior
Since CUDNN force to behave determinisically (os.environ['TF_CUDNN_DETERMINISTIC'] = 'true'), and all the data/parameter/loss are the same, grad is expected to be same.
Code to reproduce the issue
import os
import pickle
import random
import numpy as np
import tensorflow as tf

os.environ['TF_CUDNN_DETERMINISTIC'] = 'true'

seed = 1234
np.random.seed(seed)
tf.random.set_seed(seed)
random.seed(seed)

# NN Model
input_dim = 5
net = tf.keras.Sequential()
net.add(tf.keras.layers.Dense(100, activation=tf.nn.relu, kernel_initializer=None))
net.add(tf.keras.layers.Dense(100, activation=tf.nn.relu, kernel_initializer=None))
net.add(tf.keras.layers.Dense(1, activation=None, kernel_initializer=None))
net.build((None, input_dim))

# Initial v_params
initial_v_params = net.variables

# Update NN Model one-step
x = np.random.normal(loc=0, scale=1., size=[1000, input_dim])
y = np.random.normal(loc=0, scale=1., size=[1000])

with tf.GradientTape() as tape:
    loss = tf.reduce_mean(tf.square(y - net(x)))
grad = tape.gradient(loss, net.trainable_variables)

# Tag for comparing files
tag = 1

with open('./numpy_data{}.pkl'.format(tag), 'wb') as f:
    pickle.dump([x, y], f)

with open('./initial_params{}.pkl'.format(tag), 'wb') as f:
    pickle.dump(initial_v_params, f)

with open('./loss{}.pkl'.format(tag), 'wb') as f:
    pickle.dump(loss, f)

with open('./grad{}.pkl'.format(tag), 'wb') as f:
    pickle.dump(grad, f)

Please find the gist of colab.

@allenlavoie Any idea on how this would happen (for gradients)?

I don't think this has anything to do with gradient infrastructure, which conceptually is just queuing up some ops. Sounds like some op used in a gradient does not give the same result every time. We don't generally guarantee exact results; if you're using deterministic CuDNN, possibly we're not using CuDNN in some case?
@iganichev (who works on GPUs) could you decide whether this is a problem, or if epsilon differences are expected here?

There can be many reasons for non-determinism. As Allen pointed out TF uses many libraries and hand-written kernels besides cuDNN on GPU including Eigen and cuBLAS. For example, in certain convolutions, it is faster to execute them using a GEMM function in cuBLAS. In general, getting TF to behave deterministically is pretty hard. This is a known issue.
Does this non-determinism cause a serious issue?

Closing this based on above comments. Thanks all!


Remove parameter coercion, match Hack type system

Not entirely sure this is right. We might keep the coercion, but make it more limited.
Also, FB internally will not allow a null for a string, but externally this is fine.

Unless an attribute is required, why is null for a string bad? Also, definitely agree about type coercion. It simplifies things for people who might be used to doing <xhp foo="bar" number="4" /> instead of <xhp foo="bar" number={4} />.

if it's not marked as required, it would ideally be typed as '?string' to match the rest of the type system.
Also, hack currently incorrectly thinkss that it'll be a stringish, not necessarily a string.

We're likely to do this - attribute types must exactly match
For 2.0:

ban particularly crazy conversions (eg array to int)
have consistent errors (XHPInvalidAttributeException, not mix of that and cast errors)
still coerce, but raise deprecation notices
add option to raise XHPInvalidAttributeException instead of coercing

For 2.1 (after HHVM + Typechecker changes)

change default value of option to be throw an exception instead of coercing
add 'num' type, accepting float or int

Later point:

remove coercion entirely

Notably, this makes the attr="foo" syntax much less useful, requiring attr={foo} for everything except strings

new rules here: https://github.com/facebook/xhp-lib/blob/hack/src/core/XHPAttributeCoercion.php

2.0 parts done by https://github.com/facebook/xhp-lib/commit/dd57e38d4a701d5c47eae58d7a952f4bb0fab927
We're also planning to change teh parser to allow myintattr=3, instead of requiring myintattr={3}

We're also planning to change the parser to allow myintattr=3, instead of requiring myintattr={3}

:+1:

For which types?

Almost certainly for int. Float and bool are likely for consistency only, though I think using them would be bad style.

HHVM parser change: https://reviews.facebook.net/D34749

The more I think about it, the less I like allowing <xhp myint=3 />. It seems awkward to me that numbers are special cased in this way. Why not <xhp mybool=true />, <xhp myarray=array() />, or <xhp myvar=$var />?
And then by that point it makes XHP feel a little sloppy. I suppose you could clean it up by doing <xhp myvar = $var />, but putting that in a nested structure seems confusing too.
<xhp:with-lots-of-attributes
  myvar = $var
  myarray = array('foo')
  myint = 3
  mystring = 'string'
  myVector = Vector {1, 2, 3}
/>;

When I compare it to the XHP format now, I just think it looks much better the current way.
<xhp:with-lots-of-attributes
  myvar={$var}
  myarray={array('foo')}
  myint={3}
  mystring={'string'}
  myVector={Vector {1, 2, 3}}
/>;

I can glance into the middle of this list and know immediately it's an XHP instantiation. In the end this is just my opinion though. Maybe I'm old fashioned when it comes to XHP.

It could also be my years of HTML which also allows attribute values without the quotes, but it implies a sloppy coder.

Numbers aren't special - this patch allows any scalar literal: strings, ints, floats, true/false (ok, true/false aren't actually literals...). The current format will continue to work.

So, my main concern is that I want to ban ="" for things that aren't strings. This seemed clean, but I wouldn't particularly mind requiring usage of ={}. That said, supporting both doesn't seem particularly bad to me.

Typechecker work in progress: https://reviews.facebook.net/D35253

@Swahvay: I'm also having second thoughts about that diff for non-string literals... trying to get some more opinions before landing or abandoning :)

Fwiw, I'm still not a fan of <xhp myattr=$foo /> :P

Are there any plans to return HTML string attributes to strings instead of Stringish?

Not sure I think they should be, but just curious if there was a desire for a stricter API.

We're just allowing foo="bar" and foo={$bar}, no more int, float,or bool literals, and foo=$bar was not planned
I feel stringish is useful, eg href={$URI_OBJECT}, and possibly for class and others. Doing this case-by-case seems like a lot of work for not much benefit, and would introduce inconsistencies


Add example of animation with MAPPO trained agent

Would it be possible to add a simple example animation of a MAPPO trained agent?
I don't see it here:
https://colab.research.google.com/github/FLAIROx/JaxMARL/blob/main/jaxmarl/tutorials/JaxMARL_Walkthrough.ipynb
Nor do I see it in any of the baselines etc.
Ideally, the agent will be saved to disk and reloaded for generating the animation. Thank you!

Hey! Providing weights for pre-trained agents is on our TODO list but not a priority. You can generate a gif of the MAPPO agent using the training script provided in the baselines folder

Sorry I meant to ask for a simple example of inference using a MAPPO trained agent. The animation/save/reload were frills that were easy to figure out from your existing code.
I'd like to see your recommended (or canonical) way to reuse the agent/network classes outside the training loop. Thanks!


add operator to rollback release open api

Codecov Report

Merging #2636 into master will decrease coverage by 0.03%.
The diff coverage is 35.71%.

@@             Coverage Diff              @@
##             master    #2636      +/-   ##
============================================
- Coverage      50.2%   50.16%   -0.04%
+ Complexity     2060     2059       -1
============================================
  Files           413      413
  Lines         12641    12648       +7
  Branches       1292     1294       +2
============================================
- Hits           6346     6345       -1
- Misses         5845     5853       +8
  Partials        450      450

Impacted Files
Coverage Δ
Complexity Δ

...ramework/apollo/portal/service/ReleaseService.java
5.74% <0%> (ø)
2 <0> (ø)
:arrow_down:

...ork/apollo/openapi/client/ApolloOpenApiClient.java
48.27% <0%> (ø)
4 <0> (ø)
:arrow_down:

.../openapi/client/service/ClusterOpenApiService.java
91.66% <0%> (-8.34%)
3 <0> (ø)

...pollo/openapi/v1/controller/ReleaseController.java
10% <0%> (-0.53%)
1 <0> (ø)

.../openapi/client/service/ReleaseOpenApiService.java
76.92% <100%> (+1.24%)
4 <0> (ø)
:arrow_down:

...rk/apollo/portal/controller/ReleaseController.java
11.47% <66.66%> (+1.47%)
1 <1> (ø)
:arrow_down:

...work/apollo/biz/message/DatabaseMessageSender.java
56.25% <0%> (-10.42%)
6% <0%> (-2%)

.../apollo/internals/RemoteConfigLongPollService.java
80.24% <0%> (+1.23%)
28% <0%> (+1%)
:arrow_up:

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 15714ac...1fea19d. Read the comment docs.

Coverage decreased (-0.04%) to 53.724% when pulling 1fea19df136a38f993c456a6ceb10fb60b8808a0 on nobodyiam:fix-open-api into 15714ac9e7b6caba4e2da48755457f117038076a on ctripcorp:master.


Your maven server is offline

Can you not use the github maven?

Power outage. Feel free to mirror it :)

Though that said, what exactly do you mean by "github maven"?
I'm not interested in jitpack or anything like that. I don't think github has official support for maven repositories?

Github has its own maven system built in now so you dont have to worry about hosting one
See example project like towny
https://github.com/TownyAdvanced/Towny/packages/27024

Interesting- well thanks, I was not aware of that. I don't see a reason not to switch, I'll look into it.

EffectLib is now on github, updated README with info.


eCAL on NVidia Jetson TX2

Hi, is there a way to run eCAL on the NVidia Jetson TX2 Embedded device?

Hi jldk20,
As we only provide precompiled binaries for Linux AMD64, you have to compile eCAL yourself. But eCAL is known to work on ARM 64 (we use that internally).
If you have a somehow recent Linux on your device there might be a good chance that eCAL will work. If the CPU is somehow capable of compiling, I suggest you do not look into crosscompiling but compile natively on your platform for a first test.
Here are my recommended CMake options (basically turning everything off but the samples):
cmake .. -DCMAKE_BUILD_TYPE=Release -DHAS_HDF5=OFF -DHAS_QT5=OFF -DBUILD_DOCS=OFF -DBUILD_APPS=OFF -DBUILD_SAMPLES=ON

If you  can get your hand on precompiled protobuf binaries it may be worth to also turn off building thirdparty protobuf as that takes a lot of time.
then set your routes any try the ecal_sample_person_snd and ecal_sample_person_rec samples!
Good luck! :)

Hi Florian,
thank you very much, everything is working now after compiling from scratch!

Any plan to release a pre-built version .deb for arm64, for example, Jetson platform?

Hi fei4xu,
We already provide precompiled arm64 builds for Ubuntu 16.04, 18.04, 20.04 and 20.10 (architectures i386, amd64, armhf, arm64). You can get them from the PPA:
https://continental.github.io/ecal/getting_started/setup.html#fa-ubuntu-automatically-install-ecal-from-a-ppa
If you are not using Ubuntu, those builds will probably not fit your plattform and you have to compile eCAL yourself:
https://continental.github.io/ecal/development/building_ecal_from_source.html

thanks for mentioning it, I will give it a try.

I tried and it worked, I successfully installed ecal on Jetson Nano.
One minor issue though: the python binding is not installed along with the ppa installation.
I'm not sure the amd64 .whl file can work on the arm64 platform.


Enable PETSc for HIP machines

When building Serac TPLs for tioga/ rzvernal I encountered two problems related to building PETSc:

PETSc doesn't like when the HIP prefix is /opt/rocm-5.7.1 in the spack.yaml (prefers /opt/rocm-5.7.1/hip, which messes up Axom, Tribol, Serac build systems).
PETSc had to be built with no optimization flags (Serac spec contained ^petsc cflags=-O0)

The process of getting PETSc to build previously is outlined here: https://github.com/spack/spack/issues/46468
Ideally, we want to build PETSc while keeping the HIP prefix the same and with full optimization flags. This will likely involve changes in PETSc's Spack package and/ or a patch, as well as some help from PETSc developers.

using newer rocm version (6 and up) will likely resolve some of the issues: https://github.com/LLNL/radiuss-spack-configs/pull/114#issuecomment-2485406330


[Autocomplete] Fix type for multiple values to use readonly arrays

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
The following should work
  // values accepts const and value has correct type
  useAutocomplete({
    options: ['1', '2', '3'] as const,
    multiple: true,
    value: ['1', '3'] as const,
    onChange(event, value) {
      expectType<ReadonlyArray<'1' | '2' | '3'>, typeof value>(value);
    },
  });

Current behavior 😯
Typescript complains that the value is an immutable array.
Expected behavior 🤔
accept it.
Context 🔦
A fix was proposed in #38253 and got merged, it got reverted in #38253 because of #38817.
The steps proposed by @mnajdova were to

move the current useAutocomplete in Material UI
iterate on the useAutocomplete in Base UI - test the changes in Joy UI
in v6, migrate Material UI's Autocomplete to use the Base UI's useAutocomplete

Your environment 🌎
No response

@mnajdova I'm not sure what you mean by moving the "current" useAutocomplete in Material UI:

is Material UI, the package in the folder mui-material?
are you suggesting that we copy the current version of useAutocomplete to mui-material for instance without exporting it and just using it the Autocomplete component?

Thanks for creating the issue @pcorpet. To give some clarification, at this moment Material UI uses the useAutocomplete from Base UI. If we want to make breaking changes to this hook at this point, we can't do it because a stable package depends on it. This is why I said that we should copy the current version to Material UI: /packages/mui-material/ and then we can safely iterate on the Base UI's version of the useAutocomplete. We can replace the useAutocomplete in Material UI in the next major, together with the other planned breaking changes.

@mnajdova is #39738 what you had in mind for the first steps?


Fix swiftmodule copying during Index Build

Fixes #467.
Index Build doesn't respect DEPLOYMENT_LOCATION, but we also don't need the DYLD_LIBRARY_PATH fix for it. So we use $(INDEX_ENABLE_BUILD_ARENA) as a way to customize for Index Build.

Now that I know of INDEX_ENABLE_BUILD_ARENA, I can possibly remove the Products folder navigator hack as well. I'll look into that next.

YES when Index Build is building, otherwise NO or sometimes it's not set.


try

34wet

This PR seems to be a mistake. I'm afraid, but I am closing this PR unless you are providing more details.
Have a good day!
Adel


Issue 242: Check that -Project was not specified, not that is null.

Check that a parameter with a config default was not specified. Previously, we had check that the parameter was not null.
Also fix a problem with writing the progress of random operations.

Fixes issues #242  and #284.

LGTM


Add IPFS Podcasting icon

Added IPFS Podcasting icon for incoming sats from 'ipfspodcasting' app name.
Working on sub-splits / dynamic splits for nodes hosting IPFS episodes. When a split is sent to IPFS Podcasting, it will be divided and sent to nodes hosting the episode. This is to display an IPFS app icon when sats arrive due to IPFS hosting/participation.
No ETA on this functionality, but wanted to get the icon into the next helipad release. - Thanks

Thanks!


Remove dead (and wrong) viewFromProto overload

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

@tgroh I failed to actually delete this unused method in resolving conflicts on #3509.

LGTM

Coverage increased (+0.02%) to 70.85% when pulling aaffe15ee891b5656e448eac4bd3a7ff72eee315 on kennknowles:viewFromProto into a22f1a05a2d4d4ff643a7cb175542a635a8b8c02 on apache:master.


build: alternate export in protos.js

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/2d09a9e0-e49f-4d2b-b5ea-2b554f1b32ec/targets

This is out of date due to https://github.com/googleapis/nodejs-pubsub/pull/1014/


Retire .NET API analyzer content as it is deprecated

Summary

Retire .NET API analyzer content as it is deprecated
Adjust TOC accordingly - remove it from listing
Apply appropriate redirect entry, now redirects to platform-compat-analyzer.md
Update existing article refs and content

Fixes #22856

I assume we don't need to archive the old material?

What old material are you specifically referring to, I'm not really sure?

I assume we don't need to archive the old material?

What old material are you specifically referring to, I'm not really sure?

This file: docs/standard/analyzers/api-analyzer.md

I assume we don't need to archive the old material?

What old material are you specifically referring to, I'm not really sure?

This file: docs/standard/analyzers/api-analyzer.md

I'm now realizing that "archive" is probably something more formal that I'm familiar with. I just assumed we'd delete it and redirect. Do you have any details on archiving, and how does one formally do that?

"Archiving" means moving it to docs.microsoft.com/previous-versions. There's an Archive tool on the OPS portal that generates a PR to add it for you.


Add as_usize convenience method

Just a little convenience method for my own purposes. Useful when allocating buffers of a specific amount of bytes, where the size is expected to be a usize.
Previously you would have to write:
4.mebibytes.as_u64() as _

which is a bit clunky.

The problem with this, and the reason it isn't implement now, is that it truncates the internal value if it cannot be represented as a usize. This is likely surprising behavior in the context of such a method. The idea is that if the caller really wants to potentially truncate, they can explicitly call as usize.

Ah, forgive me. I forgot about 32-bit environments and figured it would always fit, since in my head u64 == usize.

Then you can go ahead and close this. While I've got you though, love your work on Rocket, definitely one of my favorite projects!

Thank you for the kind words!


Fix Docker CE 17.03.x installation

Due to issues with some dependencies, Docker CE 17.03 installation on CentOS/RHEL 7 can't be accomplished using standard yum module. This PR fixes the installation by using a command module to run yum directly.
Addresses issue #72 (see conversation there for links to dependencies issues referenced above).

BTW, I have verified that this issue does not affect Ubuntu; hence, this PR includes commits affecting the CentOS/RHEL playbooks only.