Documentation is not clear and impossible to understand/ How to draw segmentations ?

Describe the Bug
Hello,
Sorry for the noob question if it appears like this but I'm really misunderstanding how to properly draw segmentations on the image.
I have a set of points to draw a segmentation, but there is nothing that explicitely explain how I can put my points, or I don't understand anything...
Can someone simply explain me from scratch how I can apply my array of { x , y } to a visible segmentations with color (fill and stroke), etc ?
As well how to link segmentation representations, segmentations, tool, view... I tried lots of thing following the documentation but nothing appears on the image. I'd like to work it both for stack and volume views.
Thank you.
Steps to Reproduce
Just explain me how it works concretely. The documentation examples are buggy with undeclared and unexplained variables, and the examples are working but the code is not given......
The current behavior
Documentation is impossible to understand
The expected behavior
A concise explaination about how to draw segmentations from scratch with examples without undeclared variables, imports etc...
OS
Mac OS
Node version
20.0.0
Browser
Chrome

I would love to get the code for this example for example:
https://www.cornerstonejs.org/live-examples/contourrendering

You can read code if open console and click on index.ts

Or you can clone cornerstone3D and there are examples folder.

Thx. But it doesn't help completely.
In your example you're working with contours and I did the same but it doesn't work by my side and I can't understand why...
I'd like a tutorial, not just code, but a complete explaination of each steps , with example of codes, how to have this result. From scratch. Talk to us like if we were total ignorant... :/
Here are snippets of my code I coded following your tutorial and example of code. NOT WORKING!!!!
What misses??? Can you explain to me what misses??
useEffect(() => {
    const effect = async () => {
      if (!viewport || !renderingEngine || toolGroup || !isReady) return;
      // Define tool groups to add the segmentation display tool to
      const toolGrp = initTools(toolGroupId); // THIS CONTAINS new ToolGroup and toolGroup.addTool(SegmentationDisplayTool) and more...
      if (!toolGrp) return;
      toolGrp.setToolEnabled(SegmentationDisplayTool.toolName);
      toolGrp.setToolActive(SegmentationDisplayTool.toolName);

      toolGrp.addViewport(viewport.id, renderingEngine.id);

      setToolGroup?.(toolGrp);

      const segmentationVolume = await volumeLoader.createAndCacheDerivedVolume(
        volumeId,
        {
          volumeId: segmentationId
        }
      );
      setSegmentationVolumes((volumes) => ({
        ...volumes,
        [segmentationId]: segmentationVolume
      }));

        if (!segmentations?.length) return;
        const geometryIds = await segmentations.reduce<Promise<string[]>>(
          async (segs, segmentation) => {
            const acc = await segs;
            const { color, slices, id } = segmentation;
            if (_segmentation.state.getSegmentation(id)) {
              return acc;
            }
            if (!slices?.[sliceId]?.contours) return [];
            const geometryIds = await Promise.all(
              slices[sliceId].contours
                ?.map(async (contour, index) => {
                  const c = contour[index];
                  if (!c) return "";
                  const points =
                    getSegmentationPoints(slices, sliceId, index)?.map(
                      (point) => [point.x, point.y, sliceId] as Point3
                    ) || [];
                  const { r, g, b } = hexToRgb(color.fill);

                  const geometryData: ContourSetData = {
                    id: `${id}:${Math.round(c.x)}:${Math.round(c.y)}`,
                    frameOfReferenceUID: v4(),
                    color: [r, g, b],
                    data: slices.map((slice, index) => ({
                      points,
                      color: [r, g, b],
                      type: ContourType.CLOSED_PLANAR,
                      segmentIndex: index
                    }))
                  };
                  const geometry = await geometryLoader.createAndCacheGeometry(
                    geometryData.id,
                    {
                      type: GeometryType.CONTOUR,
                      geometryData
                    }
                  );
                  // geometry.data.frameOfReferenceUID
                  return geometry.id;
                })
                .filter(async (value) => !!(await value))
            );

            return geometryIds;
          },
          Promise.resolve([])
        );

        if (geometryIds?.length) {
          // _segmentation.addSegmentations(segmentationInputArray);
          const segmentationId = "SEGMENTATION_ID_" + sliceId;
          const segmentation: SegmentationPublicInput = {
            segmentationId,
            representation: {
              type: Enums.SegmentationRepresentations.Contour,
              data: {
                geometryIds
              } satisfies ContourSegmentationData
            }
          };
          const existingSegmentation =
            _segmentation.state.getSegmentation(segmentationId);
          if (existingSegmentation) {
            _segmentation.state.removeSegmentation(segmentationId);
          }
          _segmentation.state.addSegmentation(segmentation);

          const ids = await _segmentation.addSegmentationRepresentations(
            toolGroupId,
            [
              {
                segmentationId,
                type: Enums.SegmentationRepresentations.Contour
              }
            ],
            {
              renderInactiveSegmentations: false,
              representations: {
                CONTOUR: {
                  outlineWidthActive: 1,
                  outlineWidthInactive: 1,
                  outlineOpacity: 0.7,
                  outlineOpacityInactive: 1,
                  renderOutline: true,
                  renderFill: true,
                  fillAlpha: 1,
                  fillAlphaInactive: 1
                }
              }
            }
          );

          _segmentation.state.addSegmentationRepresentation(toolGroupId, {
            segmentationId,
            segmentationRepresentationUID: ids[0],
            type: Enums.SegmentationRepresentations.Contour,
            active: true,
            segmentsHidden: new Set([]),
            colorLUTIndex: 0,
            config: {}
          });

          _segmentation.activeSegmentation.setActiveSegmentationRepresentation(
            toolGroupId,
            ids[0]
          );

          console.log(
            "STATE >> ",
            _segmentation.state.getSegmentationRepresentations(toolGroupId),
            _segmentation.state.getSegmentations(),
            _segmentation.activeSegmentation.getActiveSegmentationRepresentation(
              toolGroupId
            )
          );
        }
      };

      setToolReady(true);
    };

    effect();
    }

Also, I'd like those contours to be editable with the brush tool. Is it possible? I tried to add annotation with the points but same s**t...
I also tried with labelmap but I don't understand how I can add labelmap... I have some labelmaps array but I don't know how to add them in the state of segmentation...
It's a real pain point, your library is very very difficult to understand and use... :/ Need real help :( thanks!

I got this error :
updateContourSets.ts:75 Uncaught (in promise) TypeError: Cannot destructure property 'data' of 'geometry' as it is undefined.
at geometryIds.reduce.contourSets (updateContourSets.ts:75:21)
at Array.reduce ()
at updateContourSets (updateContourSets.ts:72:63)
at addOrUpdateContourSets (addOrUpdateContourSets.ts:21:3)
at Object.render2 [as render] (contourDisplay.ts:85:3)
at SegmentationDisplayTool.ts:157:44
at Array.map ()
at SegmentationDisplayTool.renderSegmentation (SegmentationDisplayTool.ts:142:73)

@sedghi

How can I use labelmap instead? A tutorial?
I have the labelmap data available as well in my data (not only points). I just don't understand how I can use them to generate segmentations, and also I'd like to make them editable with brush. Thanks

There are at least 10+ examples on how to use labelmaps, look here  https://www.cornerstonejs.org/docs/examples
In the source code, each of them has examples/ folder for the source code


Update  prebuilt wheel files for Linux

This is a follow-up of #126.
In trying to fix #123, #29, #86, I have built wheel files for Linux with build targets:
TORCH_CUDA_ARCH_LIST="6.1+PTX"

In theory, it should be running fine on Pascal (GTX 1000) and later GPUs.
But edge cases came up and now I have covered more with build targets:
TORCH_CUDA_ARCH_LIST="5.2+PTX;6.0;6.1+PTX;7.5;8.0;8.6;8.9"

Now this should be good enough for GPUs from Maxwell (GTX 900) to Ada Lovelace (GTX 4000) according to gencode list.

And also, for anyone who want to build these wheels, I have wrote the steps in this repo:  https://github.com/YanWenKun/ComfyUI-3D-Pack-LinuxWheels

Thanks friend, I'll add that link into install guide, cheers 👍


samples: bluetooth: update prj.conf (added CONFIG_GPIO)

Enable GPIO for all ble applications that use additional GPIO (e.g. for LED or button)

without this update ble samples which are using GPIO, will return compile error on platforms which by default has disabled GPIO in board (e.g. cyw920829m2evk_02)

But with this change, any board that does not support GPIO will have a build warning.
If you want to enable it for a specific board the disables it by default, then it should should into a board specific .conf file in the boards subdirectory

But with this change, any board that does not support GPIO will have a build warning.
No, any board that does not support GPIO will have a build error in anyway, because those samples  currently are using GPIO.

No, any board that does not support GPIO will have a build error in anyway, because those samples currently are using GPIO. Am i right?

All GPIO related code should be guarded by the Kconfig, so if GPIO=n the samples should still build and run fine. The samples that does not have CONFIG_GPIO=y does not require it; it is entirely optional.
If you want to enable GPIO for a specific board for specific samples, that should be in done in the board-specific files.

also, there are couple bt samples which has enabled GPIO:

Not sure if that is intentional or a mistake from the author.

ok. I will enable CONFIG_GPIO for cyw920829m2evk_02 from board.
Close this PR


[v1.24] disable dependent resource watching

fixes: https://github.com/kiali/kiali/issues/3482

I tested and can confirm this turns off the multiple reconciliation runs due to dependent resource watching being disabled.


get Cookies from a Middleware

What version of Hono are you using?
3.8.2
What runtime/platform is your app running on?
Cloudflare Workers
What steps can reproduce the bug?
I'm running the project locally with wrangler, so I've 2 routes: /sign-in and /me.
At the first, I sign with and return the token as cookie.
At the second, I have a middleware authenticate that check if has cookie and throw or continue...
The issue is in this middleware.
// ...
const { token } = getCookie(c);
// ...

Token is never getted using getCookie or c.cookies (as I know that is will deprecated on v4).
What is the expected behavior?
I want to get the cookies from the domain.
What do you see instead?
the empty object from c.cookies or getCookie(c)
Additional information
No response

Hi @emersonlaurentino
Could you show me the code to reproduce it. It can be minimal.

Sure, here is a minimal example:
// routers.ts
app.post("/sign-in", signIn);
app.get("/me", authenticate(), userLogged);

// signIn.tsx
// ...
setCookie(ctx, "access_token", access_token);
setCookie(ctx, "refresh_token", refresh_token);
// ...

// middlewares.ts
export function authenticate(): MiddlewareHandler {
  return async (ctx: Context, next) => {
    const cookies = getCookie(ctx);
    console.log('cookies', cookies);
    await next();
  }
}

@yusukebe I found the issue, As I am using setCookie within the /sign-in route, the cookie is only available for this path, so I added path as / in the options and the cookie is available for all routes.
Thanks for your help.


worldToScreenPoint confusing behaviour

Hi i am trying to get values from worldToScreenPoint function and as documentation says

Convert a point from world space into screen space. X will be between zero and the width of the SceneView. Y will be between zero and the height of the SceneView. Z will always be zero.

I was expecting a values between zero and my width of SceneView which is 1440 (I used sceneview.getWidth for getting this value). Also note that my height is 2960. I use Galaxy S8. However these are the results when i try to get 4 anchor points by worldToScreenPoint.

Top Left Screen: 	[x=-2356.9062, y=275.14087, z=0.0]
Top Right Screen: 	[x=1046.9188, y=403.88892, z=0.0]
Bot Left Screen: 	[x=-1796.7367, y=2886.1548, z=0.0]
Bot Right Screen: 	[x=1067.6101, y=2431.1519, z=0.0]

Also note that the bottom left and top left anchors were not in the screen bounds whereas top right and bot right were in the bounds while i was taking these measurements from the camera. Is this a bug of the arcore or is it something about my implementation ? Thank you!

I wrote a sample that placed an anchor on a plane, and then called worldToScreenPoint on every frame and updated a TextView.  What I saw was the return values were not always in the range of [0,width].  Values that were larger than the dimension or less than 0 were actually not visible.
So I think you'll need to get the width/height of the view and compare the value to make sure your world point is still visible (and < 0 is also not visible).
I propose the documentation is wrong and it should be updated to accurately reflect the current behavior.
Clamping the value is not as useful.  For example you can use the off-screen values to direct the user to look in a certain direction, where as if it is clamped, you can't tell if they should move the device.
Thoughts?


Update run docker to support toil >= 4.2

Not sure why but the update to toil>=4.2 makes it such that the docker python SDK client cannot authenticate from the docker config file.

Is quitting() not needed anymore?

Ya.. quitting was actually only useful if you're just running the python script locally.  Unfortunately since we are running the workflow in a docker container, when we do docker stop, the signal is actually a "kill" signal so it the script never actually executed what is in "quitting" while running submissions via the orchestrator.


Question: Cached images

is there a way for skipping a css animation if an image was already loaded and is in cache?
Basically right now all my images always css animate, and I would like to have that effect only for new/not yet cached images...

This isn't really doable. What I did for a customer was that I created a kind of a blur up plugin, that only did the blur up animation if image loading took longer than 33ms.
The hole code looked something like this:
const matchingMedia = (source)=> {
    const media = source.getAttribute('media');
    return !media || matchingMedia(media).matches;
};

const createBlurup = (insertElement, img, src)=>{
    let timer, blurImg;
    const removeImg = ()=>{
        requestAnimationFrame(()=>{
            blurImg.remove();
        });
    };
    const onload = ()=> {
        clearTimeout(timer);
        img.removeEventListener('load', onload);

        if(blurImg){
            blurImg.classList.add('is_loaded');
            setTimeout(removeImg, 999);
        }
    };

    img.addEventListener('load', onload);

    timer = setTimeout(()=>{
        if(!img.complete){
            requestAnimationFrame(()=>{
                if(!img.complete) {
                    blurImg = document.createElement('img');
                    blurImg.className = 'mediabox_blurupmedia';
                    blurImg.src = src;
                    insertElement.parentNode.insertBefore(blurImg, insertElement.nextSibling);
                }
            });
        }
    }, 33);
};

document.addEventListener('lazybeforeunveil', function(e){
    const img = e.target;
    const picture = img.closest('picture');
    const sources = picture ?
        Array.form(picture.querySelectorAll('source, img')) :
        [img]
    ;
    const source = sources.find(matchingMedia);
    const src = source.getAttribute('data-lowsrc');

    if(src){
        createBlurup(picture || img, img, src);

    }
});

FWIW there seems to be consensus on SO that the check img.complete || img.width + img.height > 0 should allow you to check whether an image is cached or not... possibly one could use the lifecycle hooks to append a different class (e.g. is-cached) or set of classes, and hang the animation/transition CSS on those?

@lunelson
I will look into this. I'm currently on holiday.

@aFarkas first of all, many thanks for this library, it's terrific.
I'm currently looking for solutions to this issue but haven't quite find one. it would be amazing if you add this functionality

@mario-merino
In case you are working with effects plugin you can already use the following configuration:
lazysizes.cfg.blurupMode = 'auto'; // default is 'always'

or from an image by image basis:
img {
    font-family: "blur-up: always", "object-fit: cover";
}


Version 1; Craft 2; Not showing transformed files

For example, image gets resized and the folder "_400xAUTO_crop_center-center_85" is created, but any file in this folder is 404ing ...

OK, so works if I don't create the transforms in the template ...


refactor: refactor x/amm module

Description

Simplify logic inside AfterPoolOrdersExecuted
Store Pool's CurrentSqrtPrice instead of CurrentPrice
Use cremath.BigDec for CurrentSqrtPrice

Closing. See #223


Object/factory with  type SharedPreferencesService is not registered inside GetIt.

I am getting this error when I try to run my app.
The following assertion was thrown building MyApp:
Object/factory with  type SharedPreferencesService is not registered inside GetIt.
(Did you accidentally do GetIt sl=GetIt.instance(); instead of GetIt sl=GetIt.instance;
Did you forget to register it?)
'package:get_it/get_it_impl.dart':
package:get_it/get_it_impl.dart:1
Failed assertion: line 372 pos 7: 'instanceFactory != null'

I am using SharedPreferences package in some places. without registering it in the locator dependency
My app.dart file
@StackedApp(
  routes: [
    MaterialRoute(page: StartupView, initial: true),
    MaterialRoute(page: OnboardingView),
    MaterialRoute(page: LoginView),
  ],

  dependencies: [
    LazySingleton(classType: NavigationService),
    LazySingleton(classType: BottomSheetService),
    LazySingleton(classType: DialogService),
    LazySingleton(classType: SnackbarService),
    LazySingleton(classType: MobileAuth),
    LazySingleton(classType: PushNotificationService),
    LazySingleton(classType: ThemeService),
    Singleton(classType: FirebaseAuthenticationService),

    LazySingleton(classType: GraphQLService),
    LazySingleton(classType: AccountService),
  ],
)

class AppSetup {
  /** Serves no purpose besides having an annotation attached to it */
}

I also try to add SharedPreferences like this, but it doesn't work,
also i try this as well SharedPreferences
dependencies: [
    ...
    Presolve(classType: SharedPreferences , presolveUsing: SharedPreferences.getInstance),
  ],

I have the same issue.

Did you initialise your ThemeManager?
Add await ThemeManager.initialise(); in you main() function

How to call SharedPreferences in ViewModel?
Because I still got the problem.

The following assertion was thrown building MyApp:
Object/factory with  type SharedPreferencesService is not registered inside GetIt.
(Did you accidentally do GetIt sl=GetIt.instance(); instead of GetIt sl=GetIt.instance;
Did you forget to register it?)
'package:get_it/get_it_impl.dart':
package:get_it/get_it_impl.dart:1
Failed assertion: line 372 pos 7: 'instanceFactory != null'

Thank you.


Decrypt assertion returns wrong error value

In decode_response.go post decryption if there is an error in deflating the xml post decryption then the handler returns the error from decryption which will always be nil. It should return the error in parsing the decrypted XML
	raw, derr := encryptedAssertion.DecryptBytes(decryptCert)
	if derr != nil {
		return fmt.Errorf("unable to decrypt encrypted assertion: %v", derr)
	}

	doc, _, err := parseResponse(raw)
	if err != nil {
		return fmt.Errorf("unable to create element from decrypted assertion bytes: %v", derr)
	}

After parseResponse, it returns derr which will always be nil whereas it should be returning err. Is this a wrong expectation or am I missing something here?

Fixed in #95 and released in v0.8.1 - thanks for reporting!


Implement cross-compatibility testing by means of SauceLabs

While working on GlobaLeaks, we found out that It would be valuable to implement an integration with SauceLabs in order to perform end-to-end testing in the cloud testing against cross-browser compatibility.
Given the fact that flow.js is using Grunt, this would be really simple by using karma-sauce-launcher
This way the library would benefit of an output like the following: https://github.com/globaleaks/GlobaLeaks

Digging into the current flowjs codebase i've find out that flowjs is already under testing on saucelabs but currently only Chrome is tested.
I would suggest that we add at least:

IE10, IE11, Edge
Chrome (first compatible, latest version)
Firefox (first compatible, latest version)
Safari (first compatible, latest version)
Iphone (first compatible, latest version)
Android (first compatible, latest version)

Improvals:

The badge could be added to the ReadME.md

the authorization token for saucelabs could be encrypted: http://docs.travis-ci.com/user/sauce-connect/

Would be great, can you add it?

sure! :)

In case you haven't noticed, I have added you to flowjs group at github. You can access repository directly and add it without a pull request. Thanks for your effort!

yeah yeah! i noticed! thank you so much and let's make this projects rocks! :)

merged!


Trailing Slash Bug For Cached Index Route

Laravel Version: 7.2.2
PHP Version: 7.2.5

Description:
I am using this route:
Route::get('/', 'IndexController@index')->name('index');

Which does not work when I run php artisan route:cache
Error that gets outputed: The GET method is not supported for this route. Supported methods: HEAD.
I located this file: Illuminate/Routing/CompiledRouteCollection.php
Inside that file it uses this function that removes trailing slashes from a routes URI:
protected function requestWithoutTrailingSlash(Request $request)
{
    $trimmedRequest = Request::createFromBase($request);

    $parts = explode('?', $request->server->get('REQUEST_URI'), 2);

    $trimmedRequest->server->set(
        'REQUEST_URI', rtrim($parts[0], '/').(isset($parts[1]) ? '?'.$parts[1] : '')
    );

    return $trimmedRequest;
}

If I were to remove the / from rtrim($parts[0], '/') my index route now starts working like normal.
Steps To Reproduce:
Create a route inside web.php which has just a slash as the URI.
Cache the routes by using php artisan route:cache

Works perfectly for me. Please paste your entire routes file and paste what the output of php artisan route:list is.

PHP Version: 7.2.5

This is a very old version of PHP, and has lots of known bugs and security problems. Have you tried with the latest patch release of PHP 7.2?

@GrahamCampbell My PHP version is now 7.2.7 and still no fix. As requested here are my routes @driesvints
|        | GET|HEAD  | /                                             | index                         | App\Http\Controllers\IndexController@index                             | web,Closure
                                         |
|        | GET|HEAD  | _debugbar/assets/javascript                   | debugbar.assets.js            | Barryvdh\Debugbar\Controllers\AssetController@js                       | Barryvdh\Debugbar\Middleware\DebugbarEnabled,Closure
                                         |
|        | GET|HEAD  | _debugbar/assets/stylesheets                  | debugbar.assets.css           | Barryvdh\Debugbar\Controllers\AssetController@css                      | Barryvdh\Debugbar\Middleware\DebugbarEnabled,Closure
                                         |
|        | DELETE    | _debugbar/cache/{key}/{tags?}                 | debugbar.cache.delete         | Barryvdh\Debugbar\Controllers\CacheController@delete                   | Barryvdh\Debugbar\Middleware\DebugbarEnabled,Closure
                                         |
|        | GET|HEAD  | _debugbar/clockwork/{id}                      | debugbar.clockwork            | Barryvdh\Debugbar\Controllers\OpenHandlerController@clockwork          | Barryvdh\Debugbar\Middleware\DebugbarEnabled,Closure
                                         |
|        | GET|HEAD  | _debugbar/open                                | debugbar.openhandler          | Barryvdh\Debugbar\Controllers\OpenHandlerController@handle             | Barryvdh\Debugbar\Middleware\DebugbarEnabled,Closure
                                         |
|        | GET|HEAD  | _debugbar/telescope/{id}                      | debugbar.telescope            | Barryvdh\Debugbar\Controllers\TelescopeController@show                 | Barryvdh\Debugbar\Middleware\DebugbarEnabled,Closure
                                         |
|        | GET|HEAD  | auth/steam                                    | auth.steam                    | App\Http\Controllers\Auth\SteamAuthController@redirectToSteam          | web
                                         |
|        | GET|HEAD  | auth/steam/handle                             | auth.steam.handle             | App\Http\Controllers\Auth\SteamAuthController@handle                   | web
                                         |
|        | GET|HEAD  | loadingscreens/{loadingscreen}                | loadingscreens.show           | App\Http\Controllers\LoadingscreensController@show                     | web
                                         |
|        | POST      | login                                         | generated::ph7QVHPwXthg5pJe   | App\Http\Controllers\Auth\LoginController@login                        | web,guest
                                         |
|        | GET|HEAD  | login                                         | login                         | App\Http\Controllers\Auth\LoginController@showLoginForm                | web,guest
                                         |
|        | POST      | logout                                        | logout                        | App\Http\Controllers\Auth\LoginController@logout                       | web
                                         |
|        | GET|HEAD  | manage                                        | manage.dashboard              | App\Http\Controllers\Manage\ManageController@index                     | web,auth,permission:manage-view-management
                                         |
|        | POST      | manage/announcements                          | manage.announcements.store    | App\Http\Controllers\Manage\ManageAnnouncementsController@store        | web,auth,permission:manage-view-management,permission:manage-view-announcements,permission:manage-create-announcements   |
|        | GET|HEAD  | manage/announcements                          | manage.announcements.index    | App\Http\Controllers\Manage\ManageAnnouncementsController@index        | web,auth,permission:manage-view-management,permission:manage-view-announcements
                                         |
|        | GET|HEAD  | manage/announcements/create                   | manage.announcements.create   | App\Http\Controllers\Manage\ManageAnnouncementsController@create       | web,auth,permission:manage-view-management,permission:manage-view-announcements,permission:manage-create-announcements   |
|        | DELETE    | manage/announcements/{announcement}           | manage.announcements.destroy  | App\Http\Controllers\Manage\ManageAnnouncementsController@destroy      | web,auth,permission:manage-view-management,permission:manage-view-announcements,permission:manage-delete-announcements   |
|        | PUT|PATCH | manage/announcements/{announcement}           | manage.announcements.update   | App\Http\Controllers\Manage\ManageAnnouncementsController@update       | web,auth,permission:manage-view-management,permission:manage-view-announcements,permission:manage-edit-announcements     |
|        | GET|HEAD  | manage/announcements/{announcement}/edit      | manage.announcements.edit     | App\Http\Controllers\Manage\ManageAnnouncementsController@edit         | web,auth,permission:manage-view-management,permission:manage-view-announcements,permission:manage-edit-announcements     |
|        | GET|HEAD  | manage/clear                                  | manage.clear                  | App\Http\Controllers\Manage\ManageController@clearCache                | web,auth,permission:manage-view-management,permission:manage-cache
                                         |
|        | GET|HEAD  | manage/clear/redirect                         | manage.cache.redirect         | App\Http\Controllers\Manage\ManageController@redirect                  | web,auth,permission:manage-view-management,permission:manage-cache
                                         |
|        | POST      | manage/discord                                | manage.discord.store          | App\Http\Controllers\Manage\ManageDiscordController@store              | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | DELETE    | manage/discord/{discord}                      | manage.discord.destroy        | App\Http\Controllers\Manage\ManageDiscordController@destroy            | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | PUT|PATCH | manage/discord/{discord}                      | manage.discord.update         | App\Http\Controllers\Manage\ManageDiscordController@update             | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | GET|HEAD  | manage/discord/{discord}/edit                 | manage.discord.edit           | App\Http\Controllers\Manage\ManageDiscordController@edit               | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | POST      | manage/features                               | manage.features.store         | App\Http\Controllers\Manage\ManageFeaturesController@store             | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | DELETE    | manage/features/{feature}                     | manage.features.destroy       | App\Http\Controllers\Manage\ManageFeaturesController@destroy           | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | PUT|PATCH | manage/features/{feature}                     | manage.features.update        | App\Http\Controllers\Manage\ManageFeaturesController@update            | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | GET|HEAD  | manage/features/{feature}/edit                | manage.features.edit          | App\Http\Controllers\Manage\ManageFeaturesController@edit              | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | POST      | manage/links                                  | manage.links.store            | App\Http\Controllers\Manage\ManageLinksController@store                | web,auth,permission:manage-view-management,permission:manage-view-links,permission:manage-create-links                   |
|        | GET|HEAD  | manage/links                                  | manage.links.index            | App\Http\Controllers\Manage\ManageLinksController@index                | web,auth,permission:manage-view-management,permission:manage-view-links
                                         |
|        | GET|HEAD  | manage/links/create                           | manage.links.create           | App\Http\Controllers\Manage\ManageLinksController@create               | web,auth,permission:manage-view-management,permission:manage-view-links,permission:manage-create-links                   |
|        | DELETE    | manage/links/{link}                           | manage.links.destroy          | App\Http\Controllers\Manage\ManageLinksController@destroy              | web,auth,permission:manage-view-management,permission:manage-view-links,permission:manage-delete-links                   |
|        | PUT|PATCH | manage/links/{link}                           | manage.links.update           | App\Http\Controllers\Manage\ManageLinksController@update               | web,auth,permission:manage-view-management,permission:manage-view-links,permission:manage-edit-links                     |
|        | GET|HEAD  | manage/links/{link}/edit                      | manage.links.edit             | App\Http\Controllers\Manage\ManageLinksController@edit                 | web,auth,permission:manage-view-management,permission:manage-view-links,permission:manage-edit-links                     |
|        | POST      | manage/loadingscreens                         | manage.loadingscreens.store   | App\Http\Controllers\Manage\ManageLoadingscreensController@store       | web,auth,permission:manage-view-management,permission:manage-view-loading-screen,permission:manage-create-loading-screen |
|        | GET|HEAD  | manage/loadingscreens                         | manage.loadingscreens.index   | App\Http\Controllers\Manage\ManageLoadingscreensController@index       | web,auth,permission:manage-view-management,permission:manage-view-loading-screen                                         |
|        | GET|HEAD  | manage/loadingscreens/create                  | manage.loadingscreens.create  | App\Http\Controllers\Manage\ManageLoadingscreensController@create      | web,auth,permission:manage-view-management,permission:manage-view-loading-screen,permission:manage-create-loading-screen |
|        | DELETE    | manage/loadingscreens/{loadingscreen}         | manage.loadingscreens.destroy | App\Http\Controllers\Manage\ManageLoadingscreensController@destroy     | web,auth,permission:manage-view-management,permission:manage-view-loading-screen,permission:manage-delete-loading-screen |
|        | PUT|PATCH | manage/loadingscreens/{loadingscreen}         | manage.loadingscreens.update  | App\Http\Controllers\Manage\ManageLoadingscreensController@update      | web,auth,permission:manage-view-management,permission:manage-view-loading-screen,permission:manage-edit-loading-screen   |
|        | GET|HEAD  | manage/loadingscreens/{loadingscreen}/edit    | manage.loadingscreens.edit    | App\Http\Controllers\Manage\ManageLoadingscreensController@edit        | web,auth,permission:manage-view-management,permission:manage-view-loading-screen,permission:manage-edit-loading-screen   |
|        | GET|HEAD  | manage/pages                                  | manage.pages.index            | App\Http\Controllers\Manage\ManagePagesController@index                | web,auth,permission:manage-view-management,permission:manage-view-pages
                                         |
|        | POST      | manage/pages                                  | manage.pages.store            | App\Http\Controllers\Manage\ManagePagesController@store                | web,auth,permission:manage-view-management,permission:manage-view-pages,permission:manage-create-pages                   |
|        | GET|HEAD  | manage/pages/create                           | manage.pages.create           | App\Http\Controllers\Manage\ManagePagesController@create               | web,auth,permission:manage-view-management,permission:manage-view-pages,permission:manage-create-pages                   |
|        | DELETE    | manage/pages/{page}                           | manage.pages.destroy          | App\Http\Controllers\Manage\ManagePagesController@destroy              | web,auth,permission:manage-view-management,permission:manage-view-pages,permission:manage-delete-pages                   |
|        | PUT|PATCH | manage/pages/{page}                           | manage.pages.update           | App\Http\Controllers\Manage\ManagePagesController@update               | web,auth,permission:manage-view-management,permission:manage-view-pages,permission:manage-edit-pages                     |
|        | GET|HEAD  | manage/pages/{page}/edit                      | manage.pages.edit             | App\Http\Controllers\Manage\ManagePagesController@edit                 | web,auth,permission:manage-view-management,permission:manage-view-pages,permission:manage-edit-pages                     |
|        | GET|HEAD  | manage/roles                                  | manage.roles.index            | App\Http\Controllers\Manage\ManageRolesController@index                | web,auth,permission:manage-view-management,permission:manage-view-roles
                                         |
|        | POST      | manage/roles                                  | manage.roles.store            | App\Http\Controllers\Manage\ManageRolesController@store                | web,auth,permission:manage-view-management,permission:manage-view-roles,permission:manage-create-roles                   |
|        | GET|HEAD  | manage/roles/create                           | manage.roles.create           | App\Http\Controllers\Manage\ManageRolesController@create               | web,auth,permission:manage-view-management,permission:manage-view-roles,permission:manage-create-roles                   |
|        | DELETE    | manage/roles/{role}                           | manage.roles.destroy          | App\Http\Controllers\Manage\ManageRolesController@destroy              | web,auth,permission:manage-view-management,permission:manage-view-roles,permission:manage-delete-roles                   |
|        | PUT|PATCH | manage/roles/{role}                           | manage.roles.update           | App\Http\Controllers\Manage\ManageRolesController@update               | web,auth,permission:manage-view-management,permission:manage-view-roles,permission:manage-edit-roles                     |
|        | GET|HEAD  | manage/roles/{role}/edit                      | manage.roles.edit             | App\Http\Controllers\Manage\ManageRolesController@edit                 | web,auth,permission:manage-view-management,permission:manage-view-roles,permission:manage-edit-roles                     |
|        | POST      | manage/sections                               | manage.sections.store         | App\Http\Controllers\Manage\ManageSectionsController@store             | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-create-sections             |
|        | GET|HEAD  | manage/sections                               | manage.sections.index         | App\Http\Controllers\Manage\ManageSectionsController@index             | web,auth,permission:manage-view-management,permission:manage-view-sections
                                         |
|        | GET|HEAD  | manage/sections/create                        | manage.sections.create        | App\Http\Controllers\Manage\ManageSectionsController@create            | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-create-sections             |
|        | DELETE    | manage/sections/{section}                     | manage.sections.destroy       | App\Http\Controllers\Manage\ManageSectionsController@destroy           | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-delete-sections             |
|        | PUT|PATCH | manage/sections/{section}                     | manage.sections.update        | App\Http\Controllers\Manage\ManageSectionsController@update            | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-edit-sections               |
|        | GET|HEAD  | manage/sections/{section}                     | manage.sections.show          | App\Http\Controllers\Manage\ManageSectionsController@show              | web,auth,permission:manage-view-management,permission:manage-view-sections
                                         |
|        | GET|HEAD  | manage/sections/{section}/discord/create      | manage.discord.create         | App\Http\Controllers\Manage\ManageSectionsController@createDiscord     | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-create-sections             |
|        | GET|HEAD  | manage/sections/{section}/edit                | manage.sections.edit          | App\Http\Controllers\Manage\ManageSectionsController@edit              | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-edit-sections               |
|        | GET|HEAD  | manage/sections/{section}/feature/create      | manage.features.create        | App\Http\Controllers\Manage\ManageSectionsController@createFeature     | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-create-sections             |
|        | GET|HEAD  | manage/sections/{section}/server/create       | manage.servers.create         | App\Http\Controllers\Manage\ManageSectionsController@createServer      | web,auth,permission:manage-view-management,permission:manage-view-sections,permission:manage-create-sections             |
|        | POST      | manage/servers                                | manage.servers.store          | App\Http\Controllers\Manage\ManageServersController@store              | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | DELETE    | manage/servers/{server}                       | manage.servers.destroy        | App\Http\Controllers\Manage\ManageServersController@destroy            | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | PUT|PATCH | manage/servers/{server}                       | manage.servers.update         | App\Http\Controllers\Manage\ManageServersController@update             | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | GET|HEAD  | manage/servers/{server}/edit                  | manage.servers.edit           | App\Http\Controllers\Manage\ManageServersController@edit               | web,auth,permission:manage-view-management,permission:manage-view-sections,Closure                                       |
|        | GET|HEAD  | manage/settings                               | manage.settings.index         | App\Http\Controllers\Manage\ManageSettingsController@index             | web,auth,permission:manage-view-management,permission:manage-settings
                                         |
|        | POST      | manage/settings/edit                          | manage.settings.edit          | App\Http\Controllers\Manage\ManageSettingsController@edit              | web,auth,permission:manage-view-management,permission:manage-settings
                                         |
|        | GET|HEAD  | manage/store                                  | manage.store.settings         | App\Http\Controllers\Manage\ManageStoreSettingsController@index        | web,auth,permission:manage-view-management,permission:manage-store
                                         |
|        | POST      | manage/store/edit                             | manage.store.settings.edit    | App\Http\Controllers\Manage\ManageStoreSettingsController@edit         | web,auth,permission:manage-view-management,permission:manage-store
                                         |
|        | POST      | manage/store/packages                         | manage.store.packages.store   | App\Http\Controllers\Manage\ManageStorePackagesController@store        | web,auth,permission:manage-view-management
                                         |
|        | PUT|PATCH | manage/store/packages/{package}               | manage.store.packages.update  | App\Http\Controllers\Manage\ManageStorePackagesController@update       | web,auth,permission:manage-view-management
                                         |
|        | DELETE    | manage/store/packages/{package}               | manage.store.packages.destroy | App\Http\Controllers\Manage\ManageStorePackagesController@destroy      | web,auth,permission:manage-view-management
                                         |
|        | GET|HEAD  | manage/store/packages/{package}/edit          | manage.store.packages.edit    | App\Http\Controllers\Manage\ManageStorePackagesController@edit         | web,auth,permission:manage-view-management
                                         |
|        | GET|HEAD  | manage/store/servers                          | manage.store.servers.index    | App\Http\Controllers\Manage\ManageStoreServersController@index         | web,auth,permission:manage-view-management
                                         |
|        | POST      | manage/store/servers                          | manage.store.servers.store    | App\Http\Controllers\Manage\ManageStoreServersController@store         | web,auth,permission:manage-view-management
                                         |
|        | GET|HEAD  | manage/store/servers/create                   | manage.store.servers.create   | App\Http\Controllers\Manage\ManageStoreServersController@create        | web,auth,permission:manage-view-management
                                         |
|        | PUT|PATCH | manage/store/servers/{server}                 | manage.store.servers.update   | App\Http\Controllers\Manage\ManageStoreServersController@update        | web,auth,permission:manage-view-management
                                         |
|        | GET|HEAD  | manage/store/servers/{server}                 | manage.store.servers.show     | App\Http\Controllers\Manage\ManageStoreServersController@show          | web,auth,permission:manage-view-management
                                         |
|        | DELETE    | manage/store/servers/{server}                 | manage.store.servers.destroy  | App\Http\Controllers\Manage\ManageStoreServersController@destroy       | web,auth,permission:manage-view-management
                                         |
|        | GET|HEAD  | manage/store/servers/{server}/edit            | manage.store.servers.edit     | App\Http\Controllers\Manage\ManageStoreServersController@edit          | web,auth,permission:manage-view-management
                                         |
|        | GET|HEAD  | manage/store/servers/{server}/packages/create | manage.store.packages.create  | App\Http\Controllers\Manage\ManageStoreServersController@createPackage | web,auth,permission:manage-view-management
                                         |
|        | POST      | manage/users                                  | manage.users.store            | App\Http\Controllers\Manage\ManageUsersController@store                | web,auth,permission:manage-view-management,permission:manage-view-users
                                         |
|        | GET|HEAD  | manage/users                                  | manage.users.index            | App\Http\Controllers\Manage\ManageUsersController@index                | web,auth,permission:manage-view-management,permission:manage-view-users
                                         |
|        | POST      | manage/users/search                           | manage.users.search           | App\Http\Controllers\Manage\ManageUsersController@search               | web,auth,permission:manage-view-management,permission:manage-view-users
                                         |
|        | DELETE    | manage/users/{user}                           | manage.users.destroy          | App\Http\Controllers\Manage\ManageUsersController@destroy              | web,auth,permission:manage-view-management,permission:manage-view-users,permission:manage-delete-users                   |
|        | PUT|PATCH | manage/users/{user}                           | manage.users.update           | App\Http\Controllers\Manage\ManageUsersController@update               | web,auth,permission:manage-view-management,permission:manage-view-users,permission:manage-edit-users                     |
|        | GET|HEAD  | manage/users/{user}/edit                      | manage.users.edit             | App\Http\Controllers\Manage\ManageUsersController@edit                 | web,auth,permission:manage-view-management,permission:manage-view-users,permission:manage-edit-users                     |
|        | GET|HEAD  | pages/{page}                                  | pages.show                    | App\Http\Controllers\PagesController@show                              | web
                                         |
|        | POST      | password/confirm                              | generated::nfD4BjjDYXmh1iif   | App\Http\Controllers\Auth\ConfirmPasswordController@confirm            | web,auth
                                         |
|        | GET|HEAD  | password/confirm                              | password.confirm              | App\Http\Controllers\Auth\ConfirmPasswordController@showConfirmForm    | web,auth
                                         |
|        | POST      | password/email                                | password.email                | App\Http\Controllers\Auth\ForgotPasswordController@sendResetLinkEmail  | web
                                         |
|        | POST      | password/reset                                | password.update               | App\Http\Controllers\Auth\ResetPasswordController@reset                | web
                                         |
|        | GET|HEAD  | password/reset                                | password.request              | App\Http\Controllers\Auth\ForgotPasswordController@showLinkRequestForm | web
                                         |
|        | GET|HEAD  | password/reset/{token}                        | password.reset                | App\Http\Controllers\Auth\ResetPasswordController@showResetForm        | web
                                         |
|        | POST      | register                                      | generated::Z6igR0HfoXnj5zLV   | App\Http\Controllers\Auth\RegisterController@register                  | web,guest
                                         |
|        | GET|HEAD  | register                                      | register                      | App\Http\Controllers\Auth\RegisterController@showRegistrationForm      | web,guest
                                         |
|        | GET|HEAD  | store                                         | store.index                   | App\Http\Controllers\StoreController@index                             | web,auth,permission:view-store
                                         |
|        | POST      | store/credits                                 | store.credits.create          | App\Http\Controllers\CreditsController@createPayment                   | web,auth,permission:view-store
                                         |
|        | GET|HEAD  | store/credits/execute                         | store.credits.execute         | App\Http\Controllers\CreditsController@executePayment                  | web,auth,permission:view-store
                                         |
|        | GET|HEAD  | users                                         | users.index                   | App\Http\Controllers\UsersController@index                             | web,Closure
                                         |
|        | POST      | users                                         | users.store                   | App\Http\Controllers\UsersController@store                             | web,Closure
                                         |
|        | GET|HEAD  | users/create                                  | users.create                  | App\Http\Controllers\UsersController@create                            | web,Closure
                                         |
|        | POST      | users/profile/comment/create                  | users.comments.create         | App\Http\Controllers\ProfileCommentsController@create                  | web,auth,permission:create-account-comment
                                         |
|        | DELETE    | users/profile/comment/{comment}/delete        | users.comments.delete         | App\Http\Controllers\ProfileCommentsController@destroy                 | web,auth,permission:delete-account-comment
                                         |
|        | POST      | users/profile/comment/{comment}/react         | users.comments.react          | App\Http\Controllers\ProfileCommentsController@react                   | web,auth
                                         |
|        | GET|HEAD  | users/{user}                                  | users.show                    | App\Http\Controllers\UsersController@show                              | web,Closure
                                         |
|        | PUT|PATCH | users/{user}                                  | users.update                  | App\Http\Controllers\UsersController@update                            | web,Closure
                                         |
|        | DELETE    | users/{user}                                  | users.destroy                 | App\Http\Controllers\UsersController@destroy                           | web,Closure
                                         |
|        | GET|HEAD  | users/{user}/edit                             | users.edit                    | App\Http\Controllers\UsersController@edit                              | web,Closure
                                         |
|        | POST      | users/{user}/steam/link                       | users.steam.link              | App\Http\Controllers\Auth\SteamAuthController@redirectToSteam          | web
                                         |

Same here.
PHP 7.4.4
My app is under subdirectory and requesting /subdir/ throws exception, but if I request /subdir/index.php then it is ok.
Without route:cache works.
If I comment out $trimmedRequest->server->set then it works.

Difference in $trimmedRequest when requesting /subdir/ and /subdir/index.php
  pathInfo: "/subdir"
  requestUri: "/subdir"
  baseUrl: ""
  basePath: ""
  method: "GET"

  pathInfo: "/"
  requestUri: "/subdir/index.php"
  baseUrl: "/subdir/index.php"
  basePath: "/subdir"
  method: "GET"

@hulkur we don't support running Laravel in a subdirectory: https://laravel.com/docs/7.x/installation#directory-configuration

@Rainnerz are you by any chance also running Laravel in a subdirectory?

@driesvints if this makes any difference my app is in a pod and only served under subdir

@hulkur it doesn't. Please don't place your laravel app in a subdirectory.

Ok. It worked in Laravel 5.8 and 6

@driesvints Yes, I am using XAMPP where I do my local development. So my project path is under htdocs/feather
And my URL: http://localhost/feather/
However I used to create Laravel projects under subdirectories all the time and this issue never happened. I am now trying to possibly ovveride the vendor class with my own helper class to change that function.

We don't support Laravel projects in sub directories, sorry.

Hi I know this issue is closed, and I understand you guys do not want to serve Laravel in a subdirectory due to security concern. However, in our current PROD setup, we have multiple apps (built by different teams, some built in laravel and some aren't) that sit behind an application load balancer (ALB). ALB will route traffic to appropriate app based on URL (e.g. domain/app1 and domain/app2). So technically, we are not violating the no-serving-Laravel-application-out-of-a subdirectory-of-the-web-directory-on-web-server rule. I know this is a very particular setup, but I can't imagine we are the only one doing this. With this change, we are now pretty tightly cornered into either being stuck on an older Laravel version for our apps, or finding some way to hack things and make it work (e.g. overriding framework class). Is it not possible for you guys to enforce the said rule in a different way? Or can you provide an opt-out settings?

With the introduction of this breaking change, has anyone managed to come up with a workaround so they can continue using Laravel 7.x?

We are in the same boat. I work at a college and we use a sub-directory setup similar to many other colleges I have heard from that don't have luxury of obtaining infinite sub-domains for all the apps we build. We had to just stop caching our routes due to this change. We also cannot use Laravel Nova. In both of these cases, well documented and fairly trivial code changes could allow for sub-directory setups like ours.

Like @walliby we have the same problem at our University.
Like @pkid169  we are not violating the no-serving-Laravel-application-out-of-a subdirectory-of-the-web-directory-on-web-server rule, and there is no security concern on my server or whatsoever. (Also remember without caching it works)
Like @derekps I am looking for a fix.
If not possible, Laravel please update your doc to: You can't have a website under https://yourdomain/website with caching enabled.
Problem raised in 32236 and ignored or responded with very vague answer without explanation.
Regards,


Clarification regarding one issue

Facing this issue while running an application on VM. Please check the below log for this issue.
(node:10700) UnhandledPromiseRejectionWarning: Error: The specified module could not be found.
<EMAIL_ADDRESS>at process.func [as dlopen] (node:electron/js2c/asar_bundle:5:1800)
at Object.Module._extensions..node (node:internal/modules/cjs/loader:1199:18)
at Object.func [as .node] (node:electron/js2c/asar_bundle:5:1800)
at Module.load (node:internal/modules/cjs/loader:988:32)
at Module._load (node:internal/modules/cjs/loader:829:12)
at Function.c._load (node:electron/js2c/asar_bundle:5:13331)
at Module.require (node:internal/modules/cjs/loader:1012:19)
at Module.patchedRequire [as require] (C:\Users\Admin\Desktop\Backup\DesktopBridgeOrchestrators\common\temp\node_modules\diagnostic-channel\dist\src\patchRequire.js:14:46)
at require (node:internal/modules/cjs/helpers:94:18)
at Function.load (C:\Users\Admin\Desktop\Backup\DesktopBridgeOrchestrators\common\temp\node_modules@bentley\imodeljs-native\NativeLibrary.js:65:31)
(Use electron --trace-warnings ... to show where the warning was created)
(node:10700) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

Can you provide some more information?
What version of iTwin.js are you using?
 If so, what does your webpack config look like?


Migrate Blueprint Components to IDL

There are 4 components that are only used by blueprints. These will be the final tail end of LegacyComponent before we can remove arrow2-convert interfaces.
They can be found here

AutoSpaceViews:

just a bool

SpaceViewMaximized

an optional SpaceViewId.  This is just a UUID so really doesn't need serdefield.

ViewportLayout:

A set of SpaceViewId. This can just be a list of UUIDs, so again doesn't need serdefield.
An egui_tiles::Tree. Probably want to stick with serde for this for now. Can just be a Binary and we can manually load/unload the serde data in load_viewport_blueprint

SpaceViewComponent

A SpaceViewBlueprint. Probably want to stick with serde for this for now. Can just be a Binary and we can manually load/unload the serde data in load_spaceview_blueprint

This is done!


Updated list of compatible plugins

The Imunify360 and APO incompatibility issue was fixed in Imunify360 v5.4.2 (DEF-14652) on Nov 12, 2020. The current stable version is 6.9.2.

https://blog.imunify360.com/release-notes-imunify360-v.5.4-2
https://www.imunify360.com/getting-started-recaptcha/

@dcpena , can you prioritize the review of this pull request as it is crucial for CloudLinux team to fix the misleading info in the docs.
Thank you in advance!

Thanks for the tag. This was updated in https://github.com/cloudflare/cloudflare-docs/pull/7175


chore(package): update rollup-plugin-terser to version 3.0.0

Closes #94

Coverage remained the same at 100.0% when pulling 797df92e7226ebcdb0687b5615904d7270e91d04 on greenkeeper/rollup-plugin-terser-3.0.0 into c9ded6b32a32bd21bfc8ebd748e9c2b9852c6a42 on master.


null-ls root_dir

project.nvim doesn't appear to be setting the correct root directory for null-ls.nvim
For example, it's set one level higher than pylsp finds it's (correct) root directory, which is a subdir.
Let me know if I can get you any more information.

I'm already using ignore_lsp = { "null-ls.nvim" } (have also tried just "null-ls"). From :LspInfo
Language client log: /Users/dsully/.cache/nvim/lsp.log
  Detected filetype:   python

  2 client(s) attached to this buffer:

  Client: null-ls (id: 1, pid: 5001, bufnr: [1, 1, 1])
  filetypes:       *, python, markdown, sh, c, cpp, cs, java, javascript, javascriptreact, typescript, typescriptreact, vue, svelte, fish, json, go, nginx, css, scss, html, yaml, rust, lua, text
  autostart:       true
  root directory:  /Users/dsully/dev/repo

  Client: pylsp (id: 2, pid: 191, bufnr: [1])
  filetypes:       python
  autostart:       true
  root directory:  /Users/dsully/dev/repo/module
  cmd:             pylsp

  Configured servers list: sumneko_lua, bashls, clangd, cmake, cssls, html, pylsp, jsonls, denols, dockerls, gopls, yamlls, null-ls, sourcekit, graphql

$ pwd
/Users/dsully/dev/repo/module

To help debug the situation please set silent_chdir = false in your setup. This will show a message everytime the CWD is changed as you can see from this picture.

If you still can't see the message you can use :messages

Closed as stale.

Hello there. I was facing similar issue. Plase let me provide some pointers.
Basically, in my case, null-ls interferes with project.nvim to change dir. You need to add ignore_lsp = { "null-ls" } like below:
project_nvim.setup({
  -- debug: get a message when `project.nvim` changes dir
  silent_chdir = false,
  ignore_lsp = { "null-ls" },
})

If it still doesn't work, you may go to your null-ls set up. For example, I have the following:
null_ls.setup({
  debug = false,
  sources = sources,
  root_dir = nls_utils.root_pattern(".git"),
})

Removing root_dir = nls_utils.root_pattern(".git") should help.
Cheers!


Use larger runner and only test vit_h_14

Test still fails even with the larger runner and only running it in isolation.


Slideshow tutorial: update package install and references to reactflow for consistency.

Hello! Thanks for this wonderful library! I'm enjoying working through your tutorials.
The slideshow tutorial installation instructions use the reactflow package, but the code examples look like they want @xyflow/react. It didn't work for me as written, but was simple to figure out with either package.
I hope this is sufficient. Please let me know if you have any questions. Thanks again!

Thanks @awcurtin for catching this. Looks like this file got missed with the version update. Found another typo while reviewing.


Full FEA with Adaptive regions

🔍 Before submitting the issue

[x] I have searched among the existing issues
[x] I am using a Python virtual environment

🐞 Description of the bug
I added a trapezoidal region with rounded corners to a motor with two layers of magnets. The geometry is set correctly in the edit - Geometry tab (see the picture 1), and in Geometry - Radial too (see the picture 2) . The mechanical calculation is carried out without errors. Electromagnetic calculation with Hybrid FEA is also normal (see figure 3). However, if you select the AC loss calculation method as FullFEA, then an error occurs in the geometry (see figure 4.)

Trapezoid.txt
📝 Steps to reproduce
Trapezoid.txt
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
2024.1.2
🐍 Which Python version are you using?
3.11
📦 Installed packages
N/A

Hi @d1m4ansky. I think Motor-CAD might be rotating your adaptive region with the stator.
There is beta functionality to set the type of region manually. Try setting it to a rotor duct with Region._set_region:
from ansys.motorcad.core.geometry import RegionType, Region

my_region = Region()
my_region._region_type = RegionType.rotor_duct


Governance proposal transactions should be dry-run during proposal or make-release

Expected Behavior
One should be able to determine a proposal is going to revert prior
Current Behavior
If proposal transactions fail, it is only discovered at execution time

serial transactions may fail (should not be a blocking check) but still valuable


[idl mode] Fix red brackets and commas

The red brackets and commas were getting annoying. This "fixes" the problem, although I am not sure this is the best way to fix it.
Before:

After:

Agreed -- valid syntactic elements shouldn't blindly be styled error. Merged as 9d9337f


Crate version missing based on compiler version

Problem
error: failed to select a version for the requirement `egui = "^0.18"`
candidate versions found which didn't match: 0.17.0, 0.16.1, 0.16.0, ...

egui = { version = "0.18", optional = true }
egui_glium = { version = "0.18", optional = true }
glium = { version = "0.31", optional = true }
egui_demo_lib = { version = "0.18", optional = true, features = ["serde"] }
clipboard-win = { version = "4", optional = true }

but versions 0.18.0 and 0.18.1 existed at the time
Steps

use rustc 1.60
create crate with feature that depends on the crates listed above. (egui  is probably enough, but I did not test it)
try to build it and it will (hopefully) fail with same error I did get

Possible Solution(s)
I solved it by updating with rustup
nightly-i686-pc-windows-msvc updated - rustc 1.63.0-nightly (e6a4afc3a 2022-05-20) (from rustc 1.60.0-nightly (ee5d8d37b 2022-01-17))
Notes
I am not 100% sure if this is an cargo issue, because updating compiler did help, but I think that crate resolution trough Cargo.toml is part of cargo, and did not find any about missing crate version in either issues.
I have no easy way to test it (deleting rust and downloading another version for 30 minutes is not a good option).
To be clear failing is not an issue, but the error message is. If the message would say that newer rustc version is required, instead of crate version not found it would be clear what is going on.
I found out about the upgrade by trying version 0.17 which by the error message exist, and have the change I wanted, and then compilation failed saying one of crates needs at least rustc 1.61, without that I would not even think about updating, because I did not see any interesting feature in the release notes. And after updating I tried if the version 0.18 did exist, and it did.
Please let me know if it is rustc bug, and I should report it there.
Version
cargo 1.60.0-nightly (06b9d3174 2022-01-11)
release: 1.60.0-nightly
commit-hash: 06b9d31743210b788b130c8a484c2838afa6fc27
commit-date: 2022-01-11
host: x86_64-pc-windows-msvc
libgit2: 1.3.0 (sys:0.13.23 vendored)
libcurl: 7.80.0-DEV (sys:0.4.51+curl-7.80.0 vendored ssl:Schannel)
os: Windows 10.0.19044 (Windows 10 Pro) [64-bit]

This is an issue with Cargo, but not one that's easy to fix.
The issue comes because egui uses the new dep: syntax.
Older Cargos don't know how to interpret this syntax and so skip parsing the version.
Cargo could error on versions that they don't know how to interpret, but then you would be unable to build older versions using an older cargo just because newer versions used a newer feature.
The correct solution here is for Cargo to keep track of a reason why any given package/version/feature cannot be selected and display it when relevant. Unfortunately the "when relevant" hard is a really hard feature. There are often hundreds of "reasons" that relate to the final resolution/error, only a handful of which are actually interesting to the user.
We might be able to make incremental progress on these simple cases, but I am saving my effort for the multi year project of using pubgrub for our error messages.

Thank you for explanation, one of the main reasons why I was not sure if it is related to cargo, or rustc was that cargo version is still 1.60, so I guess it did not get updated by rustup.
Unless the file will not start with required version to parse it, I do not think there is any reliable way to do forward compatibility checks :(

btw we have https://github.com/rust-lang/cargo/issues/10623 for tracking improving the usability of the errors in this context

🤔 interesting that githug did not find it, I guess this one can be closed then?


AttributeError: 'Delaunay' object has no attribute 'vertices'

for the Example: very complex augmentation pipeline
/usr/local/lib/python3.10/dist-packages/skimage/transform/_geometric.py in estimate(self, src, dst)
982         # find affine mapping from source positions to destination
983         self.affines = []
--> 984         for tri in self._tesselation.vertices:
985             affine = AffineTransform(dimensionality=ndim)
986             success &= affine.estimate(src[tri, :], dst[tri, :])
AttributeError: 'Delaunay' object has no attribute 'vertices'

had the same issue, the skimage lib was outdated.
!pip install --upgrade scikit-image


Add a --fail-on-deprecated option to istioctl validate

Describe the feature request
We use istioctl in our pipelines (and our local cli wrapper) to prevent deploy time failures.  It would be really great if we could make istioctl fail when a deprecated resource is detected, to force users to update to the newer version.
For example authentication.istio.io/v1alpha1 was deprecated and replaced with peerauthentications.security.istio.io/v1beta1.  It'd have been great if istioctl validate --fail-on-deprecated existed, as it would have forced the update to happen in our pipelines way before the 1.6 upgrade we just did (where the crd was removed thus breaking a bunch of applications - admittedly we missed the upgrade notes around this, I'd just like to have more automated processes to protect against the human error).
Describe alternatives you've considered
None, open to suggestions
[x] Docs
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[x] User Experience
[ ] Developer Infrastructure
Additional context

We also recently added warnings. I think deprecation should be exposed as warnings, then we should make this --fail-on-warning. Super useful I think

istioctl analyze has a --failure-threshold which would do similar
@esnible I think validate is a subset of analyze, do we intend to keep both around? Is validate deprecated in favor of analyze? Should it be?

We should deprecate istioctl validate.
I don't think --fail-on-deprecated should be added.  We have --suppress <code>=<resource>.  If we need this we should probably handle it the same way, with --only IST0002=* or similar.

@esnible sorry I'm not familiar with the syntax, would that enable me to exit with a non-zero status code when deprecated apis are detected?

@Stono We don't have a good way to suppress all-but one type.
As a work-around, until we have a design and merged implementation, istioctl analyze | grep IST0002 works in scripts.  It does a bit of extra work, and it sets $? to the opposite of what you want, but it can be used in scripting.

@esnible just to be clear I'm not looking to suppress all but one type, I'm happy for all warnings to come through, I was just looking for a way to set at which level we would fail?
Of course I could parse the output from istioctl analyze with some custom scripts, however what I was requesting is quite a common pattern with any sort of linting or validation tool, you set a failure threshold or failure codes and the tool itself will exit none-zero when those conditions are met.

--failure-threshold is already there, takes info/warn/error. Then if there is some check that is false positives you can filter it out with --suppress.
What @esnible is suggesting, which I think may be useful but not required, is an allowlist option rather than denylist of --suppress

Ahhh so I could do istioctl analyze --failure-threshold=warn and IST0002 = deprecated warning?

We should deprecate istioctl validate.

This seems to make sense to me by the way so long as we're able to continue to do offline validation with analyze, I don't see any reasons validate exists.

Can you see what i'm doing wrong here?:
Deprecated API:
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: release-name
  labels:
    app: release-name
    heritage: "Tiller"
    release: "release-name"
    group: delivery-platform
  annotations:
    'atcloud.io/locality-routing': 'true'
spec:
  host: app
  trafficPolicy:
    outlierDetection:
      interval: 5s
      consecutiveGatewayErrors: 5
      consecutive5xxErrors: 0
      baseEjectionTime: 30s
      minHealthPercent: 50
      maxEjectionPercent: 25
    # Note: These values also get modified by shippr-cli during deployments
    loadBalancer:
      localityLbSetting:
        enabled: false
      simple: RANDOM
    connectionPool:
      http:
        h2UpgradePolicy: DO_NOT_UPGRADE
        http1MaxPendingRequests:<PHONE_NUMBER>
        http2MaxRequests:<PHONE_NUMBER>
        maxRequestsPerConnection:<PHONE_NUMBER>
        maxRetries:<PHONE_NUMBER>
        idleTimeout: 30m
      tcp:
        maxConnections:<PHONE_NUMBER>
        tcpKeepalive:
          time: 30s
          interval: 30s
    tls:
      mode: "ISTIO_MUTUAL"

❯ istioctl analyze --use-kube=false example.yaml
✔ No validation issues found when analyzing namespace: search-solr.

@howardjohn Are networking.istio.io/v1alpha3 DestinationRules deprecated?  It does not say so in https://istio.io/latest/docs/reference/config/networking/destination-rule/
@Stono @jasonwzm I looked into how we might implement a warning for v1alpha3 DRs as in Stono's example.  What I discovered is that the validation framework is internally translating v1beta1 resources into v1alpha3 resources encountered on the mesh for the purpose of validating them.  I can't easily distinguish the old from the new, this makes issuing a deprecation warning impossible.
What's worse, when the CRs are passed in as files, the back-translation isn't done.  https://github.com/istio/istio/issues/28719


freva-web: solr has lost "experiment_prefix" utility-> it affects web decadal analysis

As far as I am aware of, the freva-web has lost the solr/view.py experiment_prefix part:
        elif facets == "experiment_prefix":
            args["experiment"] = args.pop("experiment_prefix")
            results = reorder_results(freva.count_values(facet="experiment", **args))
            results["experiment_prefix"] = remove_year(results.pop("experiment"))
        else:
            if "experiment_prefix" in args:
                args["experiment"] = args.pop("experiment_prefix")[0] + "*"
            results = reorder_results(freva.count_values(facet=facets, **args))

as it now uses freva-databrowser endpoint instead that it does not consider it anymore (?) and has broken the web query utility.
Basically any web query relying on that will not work anymore: that means that e.g. decadal data plugin web runs are broken.
this issue is related to

this issue wiht problems

and will affect this general issue

I am not sure I entirely understand this, but this sounds to me that it's a plugin issue.

I am afraid is a problem on the freva-web side,
Some plugins (mostly decadal) rely on experiment_prefix that was part of the freva-web in order to search all decadal experiments such as:
> freva databrowser project=dcpp --facet experiment

dcppa-hindcast2005
dcppa-hindcast2006
dcppa-hindcast2007
dcppa-hindcast2008
dcppa-hindcast2009
dcppa-hindcast2010
...

where the prefix here would be dcppa-hindcast
right now the the web is unable to resolve that (it was before, but since the recent update where the piece of code I mentioned above was removed is not anymore)


Change package for Strings.hasText

Description
Change package for Strings.hasText
Issues Resolved
OpenSearch core is refactored.
https://github.com/opensearch-project/OpenSearch/commit/1e08b5a075fa6018be6c0af959b2d638c2743d56
Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

integTest is failing because the latest OpenSearch core is not released yet. However, without this change, compile will fail.


DOC: add DataFrame.assign to API docs

@TomAugspurger does this look like the right place to put this?
@jorisvandenbossche can we possibly merge this into the docs for v0.16?

yep, will do when I do an update of the docs (planned to do that anyway one of the coming days when I fix the Accessor thing, so there are several things I have to include)


[bug] Load image error on Ubuntu.

Describe the bug

I got this error when I load image on Ubuntu, everything works on Mac and Windows.
Reproduction
No response
Expected behavior
No response
Platform and versions
Environment
  › OS: Ubuntu 20.04 X64
  › Node.js: 16.15.1
  › npm: 8.11.0
  › pnpm: 6.11.0
  › yarn: 1.22.15
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-unknown-linux-gnu

Packages
  › @tauri-apps/cli [NPM]: 1.0.0
  › @tauri-apps/api [NPM]: 1.0.1
  › tauri [RUST]: 1.0.0,
  › tauri-build [RUST]: 1.0.0,
  › tao [RUST]: 0.11.2,
  › wry [RUST]: 0.18.3,

App
  › build-type: bundle
  › CSP: default-src 'self' customprotocol: asset: https://asset.localhost; img-src 'self' asset: https://asset.localhost
  › distDir: ../dist
  › devPath: http://localhost:3000/
  › framework: Vue.js

App directory structure
  ├─ src-tauri
  ├─ public
  ├─ dist
  ├─ src
  ├─ .github
  ├─ node_modules
  ├─ lib
  ├─ .git
  └─ .vscode

Stack trace
No response
Additional context
No response

Can you share how you're loading the asset? Is it a fetch?

This is a CORS issue - we set the headers on macOS and Windows (that's why it works on those platforms) but webkit2gtk only added support for this recently, so we can't update yet :/

Can you share how you're loading the asset? Is it a fetch?

I load image using this code:

This is a CORS issue - we set the headers on macOS and Windows (that's why it works on those platforms) but webkit2gtk only added support for this recently, so we can't update yet :/

Is that mean webkit2gtk already supports this? Can tauri update for that?

We're working to update it - but it's complicated, see #3961

In your specific case it works if you remove i.crossOrigin = 'Anonymous' @LuoXin-s

It wouldn't work if you were using fetch() but for video/img tags it works just fine.

In your specific case it works if you remove i.crossOrigin = 'Anonymous' @LuoXin-s

I remember that if I remove i.crossOrigin = 'Anonymous', there is another problem. that's why I added that. I'll test again and make a response to you.

We're working to update it - but it's complicated, see #3961

ok

@lucasfernog If I remove i.crossOrigin = 'Anonymous', I can't export canvas to dataurl. I load image into canvas, and export it to image.

Ahh that's also a CORS issue. If the images are small (and you're not loading several images) you could read the files directly and parse them for the image element but that's.. hard and suboptimal.

@wusyong do you know if there's a way to disable CORS checks for custom protocols on Linux?

Ahh that's also a CORS issue. If the images are small (and you're not loading several images) you could read the files directly and parse them for the image element but that's.. hard and suboptimal.

I need to operate many images and they are large usually.

Reference discussions: https://github.com/tauri-apps/tauri/issues/2327#issuecomment-898887548
https://github.com/tauri-apps/wry/issues/366#issuecomment-898201274
https://github.com/tauri-apps/wry/issues/348

I tried to use https://docs.rs/webkit2gtk/latest/webkit2gtk/trait.SecurityManagerExt.html#tymethod.register_uri_scheme_as_cors_enabled but it didn't help :/

@LuoXin-s Not really :/ I'll need to implement asset protocol functionality inside the tauri protocol.

@wusyong do you know if there's a way to disable CORS checks for custom protocols on Linux?

Sorry I think I missed this mention. There's the updated webkit2gtk but I haven't added because some data race issues.
If you can bring a minimum example to wry. I'll test it along the way.


[BUG]: Race condition Bug

Contact Details [Optional]
No response
System Information
Linux
What happened?
Hello team,
Please check report here https://huntr.com/bounties/81d30840-0e2f-40c3-946b-ae1fd9946eba
Reproduction steps

...
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hey @rook1337, thanks for reporting! I prepared a bug-fix for that.

@avishniakov
Thank you for your response, can you please accept it here so that it doesnt close automatically after 60 days


Sending transaction adds to balance

Describe the bug
Attempting to clear a wallet of $7. The first attempt to send the money received a failure to send notification in Bitkit, yet did arrive at the destination wallet. Bitkit offered to send again, even though money was already cleared out. Sending again was successful (though obviously no transaction received in the destination wallet).
The two transactions both added, rather than deducted, from the wallet balance to total approx $14.
Refreshing Bitkit resolved all issues.
To Reproduce
It seems to occur when there are connectivity issues.
Expected behavior
If a notification is received that a transaction was not sent, there should be no funds received at destination.
If there is no money in the wallet, it should not lead the user to believe that they can still send money.
The balance should be deducted on sending a transaction.
Smartphone (please complete the following information):

OS: Android

Tested this extensively today and were unable to reproduce the bug. So we will close it for now.


Contexts & contextual data

Supersedes https://github.com/SpongePowered/SpongeCommon/pull/304
API | Common | Forge
(and yes, this intentionally has just the submodule update currently)

People are constantly asking about features that would suit data contexts well. I know this is a very old PR, but is there any encountered issues with getting this up to date or mergable?


"Backing up world file..." Missing CRLF

I found that every time the text Backing up world file... is displayed in the console, it's lacking a crlf. This results in concatenated text where it should not be and text that's not as easily read.
I think I've seen more instances of this happening with other strings too.

Still seems not fixed in b6b0de75f37acee8ae3096f71a93419a82fc2852
save-all
3/11/2015 1:43:30 AM Command> Saving world.....
Saving world data: 82%
Validating world save: 56%
Backing up world file...3/11/2015 1:43:30 AM Command> Saving data...
3/11/2015 1:43:30 AM Command> Saving Complete.

This new line should be fixed in 332978ddc750d77c0e571c67ec7b418883f634d6.
Still a few issues, but it may just be the mono console (those strange characters). I should test in windows as well...

Not resolved. I get varying results. A lot of times it works fine. Other times the results are different each time. Below are some examples of results I have seen.
Windows.
Terraria Server v<IP_ADDRESS>

Listening on port 7777
Type 'help' for a list of commands.

7/12/2015 1:34:56 AM Command> Ready for commands.
exit
7/12/2015 1:34:57 AM Command> Exiting on request.

Saving world data: 100%7/12/2015 1:34:58 AM Run>

Linux
Terraria Server v<IP_ADDRESS>

Listening on port 7777
Type 'help' for a list of commands.

7/12/2015 1:30:18 AM Command> Ready for commands.
exit
7/12/2015 1:30:21 AM Command> Exiting on request.

Saving world data: 98%
Validating world save: 89%user@DragonSlayer:~/tdsm-rebind-test$

[Update] For the automated save this has been resolved, but still exists upon exiting.

[Update] I have played some more on this and managed to get OTA to hook the statusText updates. I'll close this off when fully completed (not thinking about making these as hooks since they should only ever be modified by one plugin)

Moved out from B6 as this is not crucial for the update.


Temporary Access Pass: Time between generation and use within 10 seconds is not working

SO link:- https://stackoverflow.microsoft.com/questions/261510
Temporary Access Pass: Time between generation and use within 10 seconds is not working

Document Details
Expectation:- Could you please update the document with proper reason why 10 seconds is the time to use TAP code.
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5eeab12d-7578-3f86-4461-10603274408b
Version Independent ID: f4911928-14be-ecf6-0b02-cc80871ae365
Content: Configure a Temporary Access Pass in Azure AD to register Passwordless authentication methods
Content Source: articles/active-directory/authentication/howto-authentication-temporary-access-pass.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@jitendraRai Thank you for your feedback . We will engage with the content team and see how best documentation can be updated ?

Closing this issue since @Justinha responded on the internal Stack Overflow post regarding documentation updates for this.


[Event Request] Table 904 - UpdateAsm

Hi,
please add a publisher in function "UpdateAsm" in table "Assemble-to-Order Link" as follows:
(...)
// >>> new Code
OnBeforeSynchronizeAsmFromSalesLine(Rec,AsmHeader,NewSalesLine);
// <<< new Code
SynchronizeAsmFromSalesLine(NewSalesLine);
INSERT;
(...)

Is it possible to request an update to this event? It is quite useless as long as the "AsmHeader" parameter is not defined as VAR.


Cursor movement causes automatic logout

Cursor movement causes automatic logout in a dual monitor setup, not applicable with a single monitor (a laptop)

When I connect the HDMI out on my laptop to my TV, I don't see this issue --- I can move my mouse around and hovering over an action (on either display) causes it to be highlighted on both displays. Everything pretty much works as expected, though there is some glitchy-ness where sometimes one display is updated but the other is not in response to keyboard input.
What do you mean by "automatic logout" --- does the app close immediately, or is the logout action immediately activated? Are you running with the default-action set?
Can you try running from a terminal with the example command from README.md ?  What is the output in the terminal after the app closes?

My own setup is a desktop with two monitors connected, I used the example you recommended in the example, it also resulted in the auto logout from the window manager (hyprland) into the display manager, all info from the terminal was lost due to automatic logout on cursor movement. Could we write the debug to an output, through this we may find out what is going on, or the problem is coming from my own set up.

Yes the automatic logout occurs in hyprland and not in sway, further testing maybe required in hyprland if it is to be used in hyprland, if not the documentation should state compatible window manager. Thank you for the good work.

So I installed hyprland and tried it out. Even without a second display attached, when I move the mouse in waylogout it actually causes hyprland itself to crash (which has the side effect of logging the user out). Is this what happens for you? You can test this by logging in through a TTY and launching hyprland manually instead of logging in through your display manager.
Then again, for me hyprland also segfaults just by exiting normally with Super+M ....
So seems like it might be a hyprland bug. According to the Archlinux wiki, Hyprland switched from wlroots to aquamarine as its rendering library, maybe it has something to do with that.
You should have some Hyprland crash reports related to this in ~/.cache/hyprland/ that you can submit to the Hyprland project if you think they should know.

Yes you are right, I tested swaylock-effects on hyprland, it did not work when blurring is applied, probably auto crashing like you mentioned above, but the normal swaylock-effects without blurring works just like the swaylock.


Uses Github Actions To Run Automated Tests

As there's a ton(and I mean a TON) of liter errors, the linter is currently disabled on automated tests until they get resolved.

This PR also bumps up dhive to 1.2.4 to fix ripemd160 deprecation from openssl.


Nav2 Path Planning

Description
Finish #56 first!
Path planning based on our costmaps enables the autonomous movement necessary for part 3 of the URC Competition.
Requirements

Implement local and global path planning algorithms based on the competition
Integrate into the Nav2 behavior tree stack
Test and bug-check the configuration

Stale issue, remake when needed


Add enum helpers and basic symbol support

Add Basic Symbol support
Update Custom Error
Add some more examples

Codecov Report

Merging #42 (ba527d9) into main (46bc6b6) will increase coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
+ Coverage   97.66%   97.88%   +0.21%
==========================================
  Files          32       34       +2
  Lines         515      568      +53
  Branches      123      126       +3
==========================================
+ Hits          503      556      +53
  Misses         12       12

Impacted Files
Coverage Δ

ts-utils/src/helpers/array.ts
100.00% <ø> (ø)

ts-utils/src/object/for_each_key.ts
100.00% <ø> (ø)

ts-utils/src/helpers/customError.ts
100.00% <100.00%> (ø)

ts-utils/src/helpers/enum.ts
100.00% <100.00%> (ø)

ts-utils/src/object/object.ts
94.44% <100.00%> (ø)

ts-utils/src/polyfills/symbol.ts
96.87% <100.00%> (+0.87%)
:arrow_up:

ts-utils/src/symbol/symbol.ts
95.45% <100.00%> (ø)

ts-utils/src/symbol/well_known.ts
100.00% <100.00%> (ø)


@MavenRepository with credentials fails on spaces

Resolving dependencies fails if I use spaces around the = sign
this will fail (notices the spaces around the equals sign after user and password
// @file:MavenRepository("my-art", "http://localhost:8081/artifactory/authenticated_repo", user = "auth_user", password = "password")
without spaces it works
// @file:MavenRepository("my-art", "http://localhost:8081/artifactory/authenticated_repo", user="auth_user", password="password")
Unfortunately most auto-formatters will add the spaces around the equals sign, which makes the syntax currently unusable.
On a sidenote: Without specifying user= and password= the options are ignored altogether (repository is used but without authentication). I am not sure whether this is intended.

relates to https://github.com/holgerbrandl/kscript/pull/214


[LLC] Generated fields include _tokenCredential even when ctor is disabled

If clients disable the default ctors, you will run into this error:
C:\Users\chhamo\Programming\azure-sdk-for-net\sdk\purview\Azure.Analytics.Purview.Catalog\src\Generated\PurviewTypes.cs(22,42): error CS0414: The field 'PurviewTypes._tokenCredential' is assigned but its value is never used [C:\Users\chhamo\Programming\azure-sdk-for-net\sdk\purview\Azure.Analytics.Purview.Catalog\src\Azure.Analyti

I looked into this. Here's what I found:

It is non-trivial for the code generator to detect that the ctors have been suppressed. Suppression happens in the roslyn layer post codegen, so we'd have to wire up some sort of modeling or way of checking what's going to be suppressed.
The use case (purview) was suppressing to customizing the ctor to model operations grouped together. I don't expect this is a common use case.

The current work around is either:

Suppress the warning (that gets promoted to an error).
Manually set these fields to something (unused) in the ctor

I am going to move this to our backlog for consideration in the future, if it becomes painful for future us.


doc: remove dbaas badge from readme

What does this fix or implement?
Remove DBaaS badge from readme.
Checklist

[ ] PR name added as appropriate (e.g. feat:/fix:/doc:/test:/refactor:)
[ ] Tests added or updated
[ ] Documentation updated
[ ] Changelog updated and version incremented (label: upcoming release)
[ ] Github Issue linked if any
[ ] Jira task updated

@cristiGuranIonos why are we doing this?

@cristiGuranIonos why are we doing this?

DBaaS is working on some issues, until they solve them we will remove the test badge.


bump rimraf dependency

When I updated several packages in my project to the latest major versions I faced an issue with tsukuru:
yarn rebuild
yarn run v1.22.19
$ tsukuru --clean
✔ Cleaning CJS outputs (25ms)
⠼ Checking & building changed projects for CJS...

node_modules/@types/rimraf/index.d.ts:33:21 - error TS2694: Namespace '"{PATH}/node_modules/glob/dist/commonjs/index"' has no exported member 'IOptions'.

33         glob?: glob.IOptions | false | undefined;
                       ~~~~~~~~

Errors occurred before emitting. Exiting.
Process exiting with error code '1'.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Seems like some packages conflict with @types/rimraf<EMAIL_ADDRESS>for example). If I manually remove @types/rimraf from node_modules it works again.  Updating rimraf to the latest version (5.0.5) and removing @types/rimraf package solves the problem as well (tested locally using yalc). So, can I bump rimraf here or do you have any reasons to stay on 3.x.x?

I would probably just prefer getting rid of it entirely, as we can just fs.rm(path, { force: true, recursive: true });

That sounds like a plan. I'll look forward to the update 😉


neither eventClick or  dateClick callback triggered ？

It's weired that neither eventClick or  dateClick callback triggered.
anything wrong?
browser : Chrome
resources:

    <link rel="stylesheet"<EMAIL_ADDRESS>/>
    <script<EMAIL_ADDRESS>
      new window.EventCalendar(this.$refs.calendar, {
        view: 'timeGridWeek',
        events: this.createEvents(),
        allDayContent: 'all day.',
        pointer: true,

        dayMaxEvents: true,
        eventClick: function(e) {
          console.log('eventClick', e)
        },
        dateClick(e) {
          console.log('dateClick', e)
        }
      });

Everything seems to work fine https://jsbin.com/hoqotalubu/edit?js,output

Everything seems to work fine https://jsbin.com/hoqotalubu/edit?js,output

Thanks you for you reply. It's my mistake. I haven't noticed console messages were filtered . 😅
By the way, it's a nice project.  And it will be much better to have more demo for it has so many options . Group the options into a few ones might be more clear.

@mutongwu Thanks for the tips, I'll definitely take them into account in the future.

I have the same problem. When you click on dateclick, event click is also activated. The noeventclick function does not work in this case.


managedAccountBalances

⚠⚠⚠ This PR contains Data Migrations ⚠⚠⚠
⚠⚠⚠ Please read this article to ensure you don't lose your data when reviewing this branch! ⚠⚠⚠

removed balance from managedAccounts, and rather put them in the new managedAccountBalances slice.
Added an initial call to fetch all your managed Account's balances
Fixed an existing bug, where if you sent coins, the top left green number (sum of all your balances) didn't update

closes #367

closes #367

closes #417

closes #417


I'm using Eclipse and it says "Too few arguments"

How do I fix this?
usage: retrieve_msgs.py [-h] [-a] [-d] [-g GROUP] [-c CSV] [-o] token
retrieve_msgs.py: error: too few arguments
I put my token into Line 24 and replaced the None in
TOKEN = None

Don't change the code. Just add your token to the command line:
python retrieve_msgs.py [TOKEN]

On what compiler? I’m using Eclipse
Shiv Gidumal
Duke University 2017
(917) 301 6700
<EMAIL_ADDRESS>
On Dec 19, 2016, at 9:32 PM, Youyang Gu<EMAIL_ADDRESS>wrote:
Don't change the code. Just add your token to the command line:
python retrieve_msgs.py [TOKEN]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/youyanggu/groupme_stats/issues/28#issuecomment-268137867, or mute the thread https://github.com/notifications/unsubscribe-auth/AXhLlxjKlwP0vhjbA7KqM1V10j3Gez7Aks5rJz48gaJpZM4LRQSV.

You don't need a compiler. You just need python. Exit Eclipse and type the above command in your Terminal/Command Prompt.

RuntimeError: Cannot retrieve groups. Is your token correct?
I put in my token but it still won’t work. Any advice?

On Dec 19, 2016, at 10:04 PM, Youyang Gu<EMAIL_ADDRESS>wrote:
You don't need a compiler. You just need python. Exit Eclipse and type the above command in your Terminal/Command Prompt.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/youyanggu/groupme_stats/issues/28#issuecomment-268142052, or mute the thread https://github.com/notifications/unsubscribe-auth/AXhLl8TTTxgJ7CgmrHTsOqN9pwajR8-Mks5rJ0XUgaJpZM4LRQSV.

It's saying there are no groups found. You don't need quotes or braces around your tokens, not sure if that is the issue...