Changing URL without changing state

Here's the use case to prove my point.
I'm editing a Model. On save I want to change URL to /model/:id (id comes form server), but calling $state.transitionTo('model', {id: ...}) causes the state change and hence the model is RELOADED. As if it were not on client!
I'm trying to pass the existing model to the state, so that may keep it (by reusing in resolve): state.transitionTo('model', {model: modelObject}). But the normalization code stringifies the "model", so that's not an object any more.
Is what I'm doing conceptually wrong? Is there any really good reason to keep normalization which prevents it from working?

@nateabele Do you have an updated timeframe on when dynamic-params might get merged?
dynamic-params would be really helpful to a few projects we are working on as well. I'm currently using @jjaburke91's workaround but that has its own quirks.
In general, I think dynamic-params would be a big help for any view that tries to represent a nested resource on a single page.

When will it merge into master?

@nateabele is there a reason for not merging dynamic-parameters to master? if so maybe we can help?

@jjaburke91 thank you for your solution - works like a charm! :+1:

@nateabele I'm here to contribute to this if you need help.

This is very confusing. All I want to do is  update the params in the url without reloading the controller to the current state and also have that updated params be reflected in $state.params.  It sounds like there are two methods in the works that could possibly fix this issue.
$urlRouterProvider.deferIntercept();  -> how does this solve my problem?  I get the concept: you call this in the config function for your app and you define some logic for when to sync and not sync the url BUT how does only have access to the new url and old url help me determine an appropriate line of logic?
@AlJohri in your example your showing:
  if ($state.current.name !== 'MYSTATE') {
    $urlRouter.sync();
  }

This doesn't look scalable to me. It's specific to a state name not a situation where a method is being used and in that method i specify that i don't want the controller to reload.
Can someone please give me an example that shows me how i could use this to update params on a url without reloading the controller from soup to nuts?
thanks

So my solution for now is:
• reloadOnSearch: false ( to keep the page from reloading with params change )
• $location.search ( to change params ) which isn't ideal because it's not a $state method there is a loss of communication between the two systems
• sync then doesn't work to let $state know about the new params so in order to keep the params and $state.params in sync I extend $state.params at the same time I apply the new params to the url. The issue with this is that you could end up with something in $state.params that's not a valid param based on the $state defenition
I think dynamic params is the solution I am actually looking for an I'm sure I could probably hack $urlRouterProvider.deferIntercept(); to be something similar to what I'm doing right now.

Does someone has solution?

+1

+1, i digged up a lot of old issues, and it seems like a lot of them didn't get merged back to the master for release. Not sure what's the reason, but somehow all these issues related to dynamic state parameters are dead. :(

Please reopen this issue as the branch still has not been merged

2 years from the initial issue and this is still not easily achievable? :disappointed:

Thanks zaggino, I saw and used 'notify: false' literally 15 minutes after you posted that here and I had missed the earlier mention =O You may have saved me lots of time.

If you want to change URL params without reloading.
$state.current.reloadOnSearch = false;
$location.path('/my/path/123').replace();
setTimeout(function(){
$state.current.reloadOnSearch = true;
}, 0);

I have been doing this and it has been updating the URL just fine and has not been changing my state:
$state.go('my.state', {id:data.id}, {notify:false, reload:false});
And to remove the id from the url:
$state.go('my.state', {id:undefined}, {notify:false, reload:false});
I believe that the same thing could be applied to whatever is needed, though I may be missing something or misunderstanding something in this issue. (ui-router version 0.2.15)

$state.params.id = '123'
  $state.transitionTo($state.current, $state.params, {
                    inherit: true,
                    notify: true,
                });

I have kind of an odd case where I am building a highly responsive app for a company. Basically it has to determine whether to only show the list or the item based on the routed url. If you go to the url directly it has to know what to load, but if you're already in that state, it can't reload the state again because it cases lag and flicker just because the amount of data. I ended up doing a crazy mash up of some of the previous answers, and what is amazing is that the events for going into the state still fired!
So now using:
$state.transitionTo('newnav.view', { code : ing.code });

then listening for
$scope.$on('$stateChangeSuccess', function(event) {
});

I'm able to achieve this awesome no-reload but data syncing structure in my split view. I hope this little insight helps someone! Thank you all for your insightful comments previous of this, it saved my life.

@l-liava-l Lot of thaks, that was exactly what I needed :)

@l-liava-l thanks.

@l-liava-l thanks x 10000

Anyone else notice when you use $state.go('my.state', {id:data.id}, {notify:false, reload:false}); ?
There's something weird that happens to the routing mech afterwards. After it fires and i change even one param without the state reloading and I try to click any link href or ng-href ( i.e. #/myroute/page ) I have to click the link twice for the state to actually change.
I'm not really sure what's going on but it's def related to $state.go('my.state', {id:data.id}, {notify:false, reload:false}); because before I do that it only takes one click.

I've also noticed if you use @l-liava-l method it doesn't update $state.params afterwards with whatever you've updated on the url. Does anyone have a solution for this?

This is absolutely not fixed can we please reopen this issue?
The original requirements were to be able to change the url without the state reloading:
deferIntercept sort of allows you to do this:
$urlRouterProvider.deferIntercept();

if you're willing to use a method to change the url that's outside of the API i.e. $location.search
what it does allow you to do:
• it allows you to change the params without reloading the state
• If done correctly you can use $location.search without having the use reloadOnSearch:false which creates a crappy experience
what it doesn't do:
• the updated params are then not reflected in $state.params so it becomes a manual process. You have to keep track of and then merge the params back into the $state.params
If you go with an apposing solution which is a hack of $state.go which is:
$state.go($state.current.name,params,{
    // prevent the events onStart and onSuccess from firing
    notify:false,
    // prevent reload of the current state
    reload:false,
    // replace the last record when changing the params so you don't hit the back button and get old params
    location:'replace',
    // inherit the current params on the url
    inherit:true
});

On first glance this looks like a good solution and it seems to work for 5 minutes until you try to navigate to another state.... the router then reloads the same state you're on including the controller again and doesn't navigate to the other state.
It sounds like dynamic params is the solution to this problem and I see what looks like the beginning of dynamic params here https://github.com/gGonz/ui-router/commit/b43ece41d3837ca8f5461f418a53818457dea1a4 but it's not being talked about or as far as I can tell it's not merged in. Even if it is there is no documentation about it.  Also from the example given on the top of that page that only looks like a url param /myState/:myparam how do you use the params object to declare a dynamic query param i.e. /myState?myparam
Could someone please clear all of this up.

@btm1 solution worked for me!
Changing the url without reloading the controller and without the { notify: false } state reload bug.

@l-liava-l  and @btm1
The solutions worked for me to not reload the Controller, however, my resolve methods are still firing with each url change. Any ideas?

@l-liava-l honestly the best way to do this right now is to use $urlRouterProvider.deferIntercept();
i.e.
app.run(function($rootScope, $urlRouter) {
       $rootScope.someVariableThatYouToggle = true;
	//------------------------ this keeps the current controller form reloading every time you change a query param on the url ------------------------//
	$rootScope.$on('$locationChangeSuccess', function(e) {
		// Prevent $urlRouter's default handler from firing
		e.preventDefault();

		if($rootScope.someVariableThatYouToggle) {
			$urlRouter.sync();
		}
	});
});

where right before you change the url you set $rootScope.someVariableThatYouToggle to false and then change your param and then change it back again. It's ugly I know but it works:
this.queryString = function(params) {
		//------------------------ tell the router to stop listening to url changes: top of run function application.js ------------------------//
		$rootScope.someVariableThatYouToggle = false;

		$timeout(function(){
			var search = $location.search();

			//------------------------ merge new params into search params ------------------------//
			if (angular.isObject(params)) {
			  angular.extend(search, params);
			}

			//------------------------ replace them on the url ------------------------//
			$location.search(search).replace();

			//------------------------ sync $state.params with new params ------------------------//
			angular.extend($state.params,search);
			angular.extend($stateParams,search);

           $rootScope.someVariableThatYouToggle = true;
      },0);
};

So I am a little bothered that I-lava-I gets credit for what I posted earlier that day, but I had many issues with this as well. I found a better solution on stackoverflow, though I don't know from exactly where.
$state.current.reloadOnSearch = false;
$location.search('query', paramValues);
$timeout(function () {
  $state.current.reloadOnSearch = undefined;
});

@spiffy2man i'm pretty sure that's the same thing I posted. Either way who really cares who gets credit for what. We're all just trying to solve a problem here.  Also it looks as thought they've fixed the issue with the current state's controller getting reloaded when using the $state.go hack so all of this may be irrelevant with the next release.

Does anyone know this is resolved in v 0.2.15?
I'm trying to make use of this feature with client side pagination. I have a state with a resolve, that fetches all users from the server. Then a client side pagination control. On each click of page number, I'd like to change the url query parameter to append, for example "?page=5" , however, currently it reloads the state, making the server api call again.
app.js
$stateProvider
      .state('users', {
        url: '/users?page',
        templateUrl: 'views/user/users.html',
        controller: 'UsersController as users',
        resolve: {
          allUsers: function(ApiService) {
            return ApiService.allUsers();
          }
        }
      })

users.html

        {{user.firstName}} {{user.lastName}}

  <dir-pagination-controls max-size="6" on-page-change="users.pageChangeHandler(newPageNumber)"></dir-pagination-controls>

UserController.js
 this.pageChangeHandler = function(pageNum) {
      $state.go('users', {page: pageNum});
 };

This works, however, ApiService.allUsers() is being called every time user clicks a page number.

@danielabar see my answer where I describe the the various methods for changing a query param without the state reloading the controller... I'm not sure if the new version has the fix in it yet so this can be accomplished by just using $state.go

@btm1 I got a little confused with all the various code snippets in this thread, which one(s) formed the total solution. So just to confirm, is it the code posted in this comment?

@danielabar that's correct yes .... the first part is put in the run function and the second part is an example of executing a param change. It's not ideal by any means but it does work for the time being.

@btm1 But this still triggers the onEnter event, isn't it?

no if you do the $urlRouterProvider.deferIntercept(); method and pause listening to change the url it will not cause any events to be fired.

I wanted to refresh the query parameters based on some form change. This is working for me:
$state.go('items', { value: value }, {notify:false, reload:true})

@davidcunha This works for me too, until I need to go to another state.
In your example, once I go to another state, then the controller for 'items' is reloaded before the new state is loaded.

@davidcunha @cseils yes this method doesn't really work. You'll need to use $urlRouterProvider.deferIntercept();

I found something that works for what I need if you are not using html5 mode
parent.location.hash = "collection/new";

+1

Is there a way to just change the url?
Idea: change the language/locale after which a 'translateChangeSuccess' (from angular translate) is issued and from there just change the url. State is the same, so no need to actually reload it or execute the controller again.
I've used a number of combinations from here but it doesn't seam to work, and I suspect it's because I actually have to change the $stateParams to their localized values.
Any idea?

I'm using this inelegant solution of changing the url and not causing the controller to fully reload when leaving the state.
I put this at the top of the controller:
app.controller('TestController', function($state) {
   if ($state.transition) return;
   ...
});

Then just call:
$state.go('items', { value: value }, {notify:false, reload:true});

The controller still reloads when the state has changed, but it exits straight away.
Not a great solution, but so far it works for me.

Yes. Got it to work now. The concept is as stated throughout here.
I translate my url like this:
//on app.run()
$rootScope.$on('$translateChangeSuccess', function(){
      $rootScope.routerTranslate();
})
$rootScope.routerTranslate = function(){
   if($state.$current.name){ //if there's an actual state
      //newParams => iterate through params and translate them
      $state.go($state.$current.name, newParams, {notify: false});
   }
};

It's fine now. No reload (I was not creating a proper 'newParams' object), and only url change as intended.

@ nmpribeiro yes that works, but when you navigate to a other url/state the current (old) state is also completly reloaded and this can create some troubles like wrong url, ....

@squadwuschel it dependes. I am only scratching the surface since I only know angular for a couple of months. Buy here is my method:

I have a 'routes' array in the translations .json files from angular translation that I actually load before the angular is bootstraped so I can know of all my routes in advance.
My states are constructed from native parameters.
that function I showed will iterate all parameters and check if there are native key, if such then translate them. If not, use the native keys.

That means, if I have a new state it will basically re-write the process once a translation is triggered. Of course, if I change state I also do this 'routerTranslate' function.
So, that means when I reload to a new state, that new state will get translated as well. All the ways I've thought about it these one seams the best. This translation is done on rootScope, so no need to bother about it anymore. If there are translations, awesome, if there aren't, not a problem at all.

Is there any change in behaviour in the new UI router 1.0 here? I've tried most, if not all, of the suggested solutions in this thread but I am not able to achieve what I want. Basically I want to show a modal (an image light box) with a specific URL, exactly like facebook does it when you look at images. The image light box modal should show up, the URL is change, and when you close the modal the URL is changed back. All this so that you can copy-paste or deep-link the URL to the image if you want to.
I actually have achieved the described behaviour, but not without my application reloading the controllers once I get back from my light box and start navigating again.

I've tried almost all solutions suggested here, but couldn't make the url change work properly. When I call $state.go it works as expected, not re-initiating the controller, however when I move to a new state it re-initiate the old controller.
My route is something like this: host/parent/{id}/child, and I'm changing the state like this:
this.$state.go(this.$state.current.name, param, {
   notify: false,
   reload: false,
   location: 'replace'
});

Has anyone found a solution for this?

@alexandrejunges
Worked for me on 0.2.18
$state.go($state.$current.self.name, stateParams, {notify: false});

@Mikaeru001 By "worked", do you mean that the transitions happen as expected, or do you mean that you manage to execute the transitions without the controller reloading when executing subsequent transitions? I think what most people is having trouble with is the latter. I've also managed to get the transitions to work precisely as I want, but my controllers keep reloading...

@averas I mean the method works as expected. URL changes and the state stays the same. Controller is not initialized twice. On 0.2.13 I had another problem with {notify: false}. On $state.go call URL changes, state isn't reloaded. But when I click a link to go to another state, the state from the previous $state.go({notify: false}) appears. It is not a case now since I'm on 0.2.18.

@averas Or is it exactly the same problem you describe?

This is what I experience.
Say that I am on state: x.y.z
I execute $state.go(a.b.c, stateParams, {notify: false, location: "replace"});
This works, the URL is replaced, nothing appears to reload or anything.
I then want to get back to my previous state, so I do a:
$state.go(x.y.z, stateParams, {notify: false, location: "replace"});
This also seems to work, the URL is changed, everything looks good. However, when I then do a normal transition to a sibling state, which normally only loads the last controller in the chain:
$state.go(x.y.a)
.. all controllers (including the ones for x and y) reload. This does only happen after I changed the URL like above. I think what most people are saying in this thread is that you do not need to go back and forth like I do for this to happen. When you start interacting after you have performed the URL-replacing trick the controller reloads.

@averas Sorry. Can't help you with that.

Hi @Mikaeru001,
I was using 0.2.15 and updated to 0.2.18, but the controller keeps being reloaded after I change the URL, as described by @averas.
Did you change another thing?

@Mikaeru001 I honestly believe that you will strike the same problem as soon as you start interacting in you own application, you just don't know it yet. ;-)

@averas Probably.
@alexandrejunges No. Just what I've copy-pasted previously.

Any update on this one? I'm trying to do exactly what @averas said with 1.0, but so far no luck...

credits to @cseils if ($state.transition) return; works for me so far. For sure this hack is workaround so wait with you aligant solution.
**I added if ($state.transition) return; to all controllers that change URL without reloading

In case anybody is wondering, this is working for me now:
https://github.com/angular-ui/ui-router/issues/1758#issuecomment-205060258. To be specific, just adding {dynamic: true} to a param allows me to use $state.go like normal and it does not reload the controller.

Hello Dear All Friends,
I have a website on blogger, i need a image iframe when i click on this image, imgae open a new website inside,.. i need the other website page on my website in same page, i mean when we click on a image my website not refresh it just open the spacfic url in the same page

Hi Everyone.
i have a situation that i have a community type page that load recent posts lazy load on scroll and on post click , open a modal and change url , but when close modal go back to previous state and do not reload page


Update schema

Include explicit start and end times
Include explicit lower and upper confidence intervals

Resolves #17

@eschrom Curious for your thoughts on this, having thought about this data for a bit longer than me.

Confirmed in #32 that we will need monthly data in some cases, so the schema will need to account for both weekly and monthly option.


soc: arm: adi: add ADSP-SC598 A55 support

Initial basic port of the ADSP-SC598 A55 core.
Application can boot and use console but currently no drivers.  Partial OpenOCD support - use CCES 2.12.0 for now.
Signed-off-by: Murray Anderson <murray.anderson<EMAIL_ADDRESS>Llopis, Daniel<EMAIL_ADDRESS>

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_adi
N/A
analogdevicesinc/hal_adi@main
N/A

Note: This message is automatically posted and updated by the Manifest GitHub Action.


virtual DOM and diff ？

I've seen moonjs trigger data changes with update and recompile view, Although it is accurate enough, but is it virtual DOM and diff not better?

Moon used to use a virtual DOM. Now, it compiles views into direct JavaScript code — it is never "recompiled". Virtual DOM works by creating an abstraction over the normal DOM. When a change is made, Moon used to iterate through the new virtual DOM, compare it with the old virtual DOM, and use normal DOM operations to update the view.
With v1, instead of having to have the abstraction of the virtual DOM, Moon directly generates the normal DOM operations instead.


Unable to use the Extension

Problem encountered on https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/create
Operating System: windows
I installed the extension but it does not show up in the menu. I am running Visual Studio 2019 v16.4 and My app uses .Net Core 2.1

Can you share a screenshot of your installed extensions? Is it showing up as installed but disabled?

Thank you for your response.
I got the problem sorted out. Apparently restarting Visual Studio and
reinstalling the extension worked out.
Thanks Again!
On Tue, 11 Feb 2020, 10:50 Jake<EMAIL_ADDRESS>wrote:

Can you share a screenshot of your installed extensions? Is it showing up
as installed but disabled?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/506?email_source=notifications&email_token=AN7LVOBQ6HJPAN26ZIW3TZDRCIYRDA5CNFSM4KSWVI22YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELLHZKQ#issuecomment-584481962,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN7LVOAWNREDVGI624EP76TRCIYRDANCNFSM4KSWVI2Q
.

Of course! Thanks for reporting and I'm glad you found a way to resolve it!


Remove version: Nj0be.HandBrake-SVT-AV1-SPY version 20240922-402dd3fd5

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Hi @Exorcism0666,
This manifest has the highest version number for this package. Is it available from another location? (This might be in error if the version is switching from semantic to string, or string to semantic.)
(Automated response - build 896.)

Duplicate of #178787


How can I use controls outside the

First of all, thank you for this library. Works perfectly.
I've been breaking my head how to access controls for a TransformComponent outside the TransformWrapper.
My use case is that I display horizontally stacked images (one at a time). In the navbar, which is not part of the TransformWrapper and stays the same for all images I want to play controls for zoomIn, zoomOut of the currently displayed image.
Here's a simply code example:
import React, { Component } from "react";

import { TransformWrapper, TransformComponent, useControls } from "react-zoom-pan-pinch";

const Controls = () => {
  const { zoomIn, zoomOut, resetTransform } = useControls();
  return (
      <button onClick={() => zoomIn()}>
        Zoom In
      </button>
      <button onClick={() => zoomOut()}>
        Zoom Out
      </button>
      <button onClick={() => resetTransform()}>
        Reset
      </button>
  )
}

const Example = () => {
  return (

     <Controls />
     {Array.from({length: 3}).map((_, index) => (
        <TransformWrapper key={index}>
          <TransformComponent>

          </TransformComponent>
        </TransformWrapper>
       ))}

  );
};

So ideally, I can target a particular TransformWrapper/TransformComponent with useControls or useTransformContext.
I think this should be possible, but I haven't found a way yet. Perhaps someone knows.

I just figured it out, so I thought I'll share it with folks here.
import React, { MutableRefObject, useRef } from "react";
import { TransformWrapper, TransformComponent, ReactZoomPanPinchContentRef } from "react-zoom-pan-pinch";

const Controls = ({pageNumber, refs}: {pageNumber: number; refs: MutableRefObject<(ReactZoomPanPinchContentRef | null)[]>;}) => {

  return (
      <button onClick={() => refs.current[pageNumber - 1]?.zoomIn()}>
        Zoom In
      </button>
      <button onClick={() => refs.current[pageNumber - 1]?.zoomOut()}>
        Zoom Out
      </button>
      <button onClick={() => refs.current[pageNumber - 1]?.resetTransform()}>
        Reset
      </button>
  )
}

const Example = () => {
  const pinchRefs = useRef<(ReactZoomPanPinchContentRef | null)[]>([]);

  return (

     <Controls pinchRefs={pinchRefs} />
     {Array.from({length: 3}).map((_, index) => (
        <TransformWrapper
           key={index}
           ref={(ref) => { pinchRefs.current[index] = ref; }}
         >
          <TransformComponent>

          </TransformComponent>
        </TransformWrapper>
       ))}

  );
}


Minor dream-mirage fixes

The doc changes try to mirror the organisation in dream.mli as closely a possible.
As a follow up PR I can re-organise dream-mirage to exactly mirror the main dream docs.
It would be helpful for them to be in sync and it makes it easier to see what has changed when diffing dream and dream-mirage. What do you think @aantron ?

For fcc20d0 I get the following error when installing the minimum bounds for dream and dream-mirage. Which I understood to mean lwt_ppx is using an older version of the ocaml parse tree that doesn't support complex opens. They were added in 4.08 with Generalized open statements.
# File "src/mirage/dune", line 20, characters 13-26:
# 20 |  (preprocess (pps lwt_ppx))
#                   ^^^^^^^^^^^^^
# (cd _build/default && .ppx/bcab0be011c28261c514e69f4fe141f8/ppx.exe --cookie 'library-name="dream__mirage"' -o src/mirage/mirage.pp.ml --impl src/mirage/mirage.ml --dump-ast)
# Fatal error: exception File "src/mirage/mirage.ml", line 389, characters 2-34: complex open are not supported before OCaml 4.08

I'm currently unable to test this because of
λ eval (opam env --switch=dream-mirage-4.14.1 --set-switch)
λ opam repo list                                                                                2

[NOTE] These are the repositories in use by the current switch. Use '--all' to see all configured repositories.

<><> Repository configuration for switch dream-mirage-4.14.1 ><><><><><><><><><>
 1 dune-universe git+https://github.com/dune-universe/opam-overlays.git
 2 default       https://opam.ocaml.org

λ mirage configure -t unix
λ make depends

using overlay repository mirage: [opam-overlays, mirage-overlays]
[opam-overlays] no changes from git+https://github.com/dune-universe/opam-overlays.git
[NOTE] Repository opam-overlays has been added to the selections of switch dream-mirage-4.14.1 only.
       Run `opam repository add opam-overlays --all-switches|--set-default' to use it in all existing switches, or in newly created switches, respectively.

[mirage-overlays] no changes from git+https://github.com/dune-universe/mirage-opam-overlays.git
[NOTE] Repository mirage-overlays has been added to the selections of switch dream-mirage-4.14.1 only.
       Run `opam repository add mirage-overlays --all-switches|--set-default' to use it in all existing switches, or in newly created switches, respectively.

 ↳ generate lockfile for monorepo dependencies
==> Using 1 locally scanned package as the target.
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
opam-monorepo: [ERROR] There is no eligible version of cmdliner that matches >= 1.1.0
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
opam-monorepo: [WARNING] Couldn't calculate a set of packages to satisfy the request. Note that opam monorepo lock will fail if not all of the project dependencies use dune as their build system, in your project that would be ptime,
                         ocamlfind, logs, fmt,
                         astring. To solve this issue there exists a dune-universe opam-repository which contains dune ports for some opam packages, but it is currently not set in your current switch. If you wish to set it up, run the following command:
opam repository add dune-universe git+https://github.com/dune-universe/opam-overlays.git
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
opam-monorepo: [ERROR] Can't find all required versions.
Selected: arp.3.1.0 base-bigarray.base base-bytes.base base-domains.base
          base-nnp.base base-threads.base base-unix.base cppo.1.6.9
          csexp.1.5.2 cstruct.6.2.0 cstruct-lwt.6.2.0 domain-name.0.4.0
          dune.3.7.1 dune-configurator.3.7.1 duration.0.2.1 ethernet.3.2.0
          functoria-runtime.4.3.6 hello-unix.zdev ipaddr.5.5.0
          ipaddr-cstruct.5.5.0 lru.0.3.1 lwt.5.6.1 lwt-dllist.1.0.1
          macaddr.5.5.0 macaddr-cstruct.5.5.0 metrics.0.4.0
          mirage-bootvar-unix.0.1.0 mirage-clock.4.2.0
          mirage-clock-unix.4.2.0 mirage-flow.3.0.0 mirage-logs.1.3.0
          mirage-net.4.0.0 mirage-random.3.0.0 mirage-runtime.4.3.6
          mirage-time.3.0.0 mirage-unix.5.0.1 ocaml-base-compiler.5.0.0
          ocaml-options-vanilla.1 ocplib-endian.1.2 parse-argv.0.2.0
          psq.0.2.1 randomconv.0.1.3 seq.base tcpip.8.0.0
          ocaml-base-compiler&hello-unix ocaml base-domains ocaml
          ocaml-base-compiler
- astring -> (problem)
    No usable implementations:
      astring.0.8.5: Doesn't build with dune
      astring.0.8.4: Doesn't build with dune
      astring.0.8.3: Doesn't build with dune
      astring.0.8.2: Doesn't build with dune
      astring.0.8.1: Doesn't build with dune
      ...
- cmdliner -> (problem)
    functoria-runtime 4.3.6 requires >= 1.1.0
    Rejected candidates:
      cmdliner.0.9.5: Incompatible with restriction: >= 1.1.0
      cmdliner.0.9.4: Incompatible with restriction: >= 1.1.0
      cmdliner.0.9.2: Incompatible with restriction: >= 1.1.0
      cmdliner.1.2.0: Doesn't build with dune
      cmdliner.1.1.1: Doesn't build with dune
      ...
- dream-mirage -> (problem)
    No known implementations at all
- fmt -> (problem)
    No usable implementations:
      fmt.0.9.0: Doesn't build with dune
      fmt.0.8.10: Doesn't build with dune
      fmt.0.8.9: Doesn't build with dune
      fmt.0.8.8: Doesn't build with dune
      fmt.0.8.7: Doesn't build with dune
      ...
- logs -> (problem)
    No usable implementations:
      logs.0.7.0: Doesn't build with dune
      logs.0.6.3: Doesn't build with dune
      logs.0.6.2: Doesn't build with dune
      logs.0.6.1: Doesn't build with dune
      logs.0.6.0: Doesn't build with dune
      ...
- ocaml -> (problem)
    User requested = 4.14.1
    ocaml-base-compiler 5.0.0 requires = 5.0.0
    Rejected candidates:
      ocaml.4.14.1: Incompatible with restriction: = 5.0.0
- ocamlfind -> (problem)
    No usable implementations:
      ocamlfind.1.9.6: Doesn't build with dune
      ocamlfind.1.9.5: Doesn't build with dune
      ocamlfind.1.9.3: Doesn't build with dune
      ocamlfind.1.9.2: Doesn't build with dune
      ocamlfind.1.9.1: Doesn't build with dune
      ...
- ptime -> (problem)
    No usable implementations:
      ptime.1.1.0: Doesn't build with dune
      ptime.1.0.0: Doesn't build with dune
      ptime.0.8.6: Doesn't build with dune
      ptime.0.8.5: Doesn't build with dune
      ptime.0.8.4: Doesn't build with dune
      ...
removing overlay repository [opam-overlays, mirage-overlays]
Repositories removed from the selections of switch dream-mirage-4.14.1. Use '--all' to forget about them altogether.
Repositories removed from the selections of switch dream-mirage-4.14.1. Use '--all' to forget about them altogether.
make[2]: *** [Makefile:36: mirage/hello-unix.opam.locked] Error 1
make[1]: *** [Makefile:39: lock] Error 2
make: *** [Makefile:51: depends] Error 2

I am working in example w-mirage, which I have copied out to its own separate directory. Do you know, by chance, what could be causing this?
As a sanity check,
λ opam info ptime

<><> ptime: information on all versions <><><><><><><><><><><><><><><><><><><><>
name                   ptime
all-installed-versions 1.1.0 [dream-4.14.1 dream-5.0.0 dream-serve-4.14.1 /home/antron/code/style /home/antron/code/serve]
all-versions           0.8.0  0.8.1  0.8.2  0.8.3  0.8.4  0.8.5  0.8.5+dune  0.8.6  1.0.0  1.0.0+dune  1.0.0+dune2  1.1.0  1.1.0+dune

<><> Version-specific details <><><><><><><><><><><><><><><><><><><><><><><><><>
version      1.1.0+dune
repository   dune-universe
url.src      "https://github.com/dune-universe/ptime/releases/download/v1.1.0%2Bdune/ptime-1.1.0.dune.tbz"
url.checksum "sha256=9aa6645808ce539eeafe4eaf781d6d0ae5639c90592cee31d15cf9363acf9234"
             "sha512=0d037fc8f11c25b407f5501bd614dbbadb83fd6dce2fff5c0eeae27a9cd616f69f399f0cb3a04a2b0588cf1866cb16d6d1ae599791509cb995a92d3ae33ad1a0"
homepage     "https://github.com/dune-universe/ptime"
bug-reports  "https://github.com/dbuenzli/ptime/issues"
dev-repo     "git+https://github.com/dune-universe/ptime.git"
authors      "The ptime programmers"
maintainer   "Daniel Bünzli <daniel.buenzl<EMAIL_ADDRESS>license      "ISC"
tags         "time" "posix" "system" "org:erratique"
depends      "dune" "ocaml" {>= "4.08.0"}
synopsis     POSIX time for OCaml
description  Ptime has platform independent POSIX time support in pure OCaml. It
             provides a type to represent a well-defined range of POSIX timestamps
             with picosecond precision, conversion with date-time values,
             conversion with [RFC 3339 timestamps][rfc3339] and pretty printing to
             a human-readable, locale-independent representation.
             The additional Ptime_clock library provides access to a system POSIX
             clock and to the system's current time zone offset.
             Ptime is not a calendar library.
             Ptime has no dependency. Ptime_clock depends on your system library or
             JavaScript runtime system. Ptime and its libraries are distributed
             under the ISC license.
             [rfc3339]: http://tools.ietf.org/html/rfc3339
             Home page: <http://erratique.ch/software/ptime>

I see the +dune versions in the output, so why is make depends saying that there isn't a version of, for instance, ptime that builds with Dune?

Also
λ opam --version
2.1.4

I think the problem is more about dream-mirage:
- dream-mirage -> (problem)
    No known implementations at all

Did you pin the dream-mirage package to let opam and the 0install-solver to know about this package?

I did and do have it pinned. To be sure:
λ rm -rf Makefile _build/ dist dune dune-project dune-workspace dune.build dune.config mirage

λ ls

README.md  config.ml  unikernel.ml

λ mirage configure -t unix^C
λ opam pin list

dream-mirage.~dev  (uninstalled)  git  git+file:///home/antron/code/dreamworld/dream#patch-1

λ opam repo list

[NOTE] These are the repositories in use by the current switch. Use '--all' to see all configured repositories.

<><> Repository configuration for switch dream-mirage-4.14.1 ><><><><><><><><><>
 1 dune-universe git+https://github.com/dune-universe/opam-overlays.git
 2 default       https://opam.ocaml.org

λ mirage --version

v4.3.6

λ ocaml -version

The OCaml toplevel, version 4.14.1

λ which ocaml

/home/antron/.opam/dream-mirage-4.14.1/bin/ocaml

λ mirage configure -t unix

λ make depends

using overlay repository mirage: [opam-overlays, mirage-overlays]
[opam-overlays] no changes from git+https://github.com/dune-universe/opam-overlays.git
[NOTE] Repository opam-overlays has been added to the selections of switch dream-mirage-4.14.1 only.
       Run `opam repository add opam-overlays --all-switches|--set-default' to use it in all existing switches, or in newly created switches, respectively.

[mirage-overlays] no changes from git+https://github.com/dune-universe/mirage-opam-overlays.git
[NOTE] Repository mirage-overlays has been added to the selections of switch dream-mirage-4.14.1 only.
       Run `opam repository add mirage-overlays --all-switches|--set-default' to use it in all existing switches, or in newly created switches, respectively.

 ↳ generate lockfile for monorepo dependencies
==> Using 1 locally scanned package as the target.
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
opam-monorepo: [ERROR] There is no eligible version of cmdliner that matches >= 1.1.0
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
opam-monorepo: [WARNING] Couldn't calculate a set of packages to satisfy the request. Note that opam monorepo lock will fail if not all of the project dependencies use dune as their build system, in your project that would be ptime,
                         ocamlfind, logs, fmt,
                         astring. To solve this issue there exists a dune-universe opam-repository which contains dune ports for some opam packages, but it is currently not set in your current switch. If you wish to set it up, run the following command:
opam repository add dune-universe git+https://github.com/dune-universe/opam-overlays.git
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
[WARNING] Unknown variable "ocaml-system:version"
[WARNING] Unknown variable "ocaml-base-compiler:version"
[WARNING] Unknown variable "ocaml-variants:version"
opam-monorepo: [ERROR] Can't find all required versions.
Selected: arp.3.1.0 base-bigarray.base base-bytes.base base-domains.base
          base-nnp.base base-threads.base base-unix.base cppo.1.6.9
          csexp.1.5.2 cstruct.6.2.0 cstruct-lwt.6.2.0 domain-name.0.4.0
          dune.3.7.1 dune-configurator.3.7.1 duration.0.2.1 ethernet.3.2.0
          functoria-runtime.4.3.6 hello-unix.zdev ipaddr.5.5.0
          ipaddr-cstruct.5.5.0 lru.0.3.1 lwt.5.6.1 lwt-dllist.1.0.1
          macaddr.5.5.0 macaddr-cstruct.5.5.0 metrics.0.4.0
          mirage-bootvar-unix.0.1.0 mirage-clock.4.2.0
          mirage-clock-unix.4.2.0 mirage-flow.3.0.0 mirage-logs.1.3.0
          mirage-net.4.0.0 mirage-random.3.0.0 mirage-runtime.4.3.6
          mirage-time.3.0.0 mirage-unix.5.0.1 ocaml-base-compiler.5.0.0
          ocaml-options-vanilla.1 ocplib-endian.1.2 parse-argv.0.2.0
          psq.0.2.1 randomconv.0.1.3 seq.base tcpip.8.0.0
          ocaml-base-compiler&hello-unix ocaml base-domains ocaml
          ocaml-base-compiler
- astring -> (problem)
    No usable implementations:
      astring.0.8.5: Doesn't build with dune
      astring.0.8.4: Doesn't build with dune
      astring.0.8.3: Doesn't build with dune
      astring.0.8.2: Doesn't build with dune
      astring.0.8.1: Doesn't build with dune
      ...
- cmdliner -> (problem)
    functoria-runtime 4.3.6 requires >= 1.1.0
    Rejected candidates:
      cmdliner.0.9.5: Incompatible with restriction: >= 1.1.0
      cmdliner.0.9.4: Incompatible with restriction: >= 1.1.0
      cmdliner.0.9.2: Incompatible with restriction: >= 1.1.0
      cmdliner.1.2.0: Doesn't build with dune
      cmdliner.1.1.1: Doesn't build with dune
      ...
- dream-mirage -> (problem)
    No known implementations at all
- fmt -> (problem)
    No usable implementations:
      fmt.0.9.0: Doesn't build with dune
      fmt.0.8.10: Doesn't build with dune
      fmt.0.8.9: Doesn't build with dune
      fmt.0.8.8: Doesn't build with dune
      fmt.0.8.7: Doesn't build with dune
      ...
- logs -> (problem)
    No usable implementations:
      logs.0.7.0: Doesn't build with dune
      logs.0.6.3: Doesn't build with dune
      logs.0.6.2: Doesn't build with dune
      logs.0.6.1: Doesn't build with dune
      logs.0.6.0: Doesn't build with dune
      ...
- ocaml -> (problem)
    User requested = 4.14.1
    ocaml-base-compiler 5.0.0 requires = 5.0.0
    Rejected candidates:
      ocaml.4.14.1: Incompatible with restriction: = 5.0.0
- ocamlfind -> (problem)
    No usable implementations:
      ocamlfind.1.9.6: Doesn't build with dune
      ocamlfind.1.9.5: Doesn't build with dune
      ocamlfind.1.9.3: Doesn't build with dune
      ocamlfind.1.9.2: Doesn't build with dune
      ocamlfind.1.9.1: Doesn't build with dune
      ...
- ptime -> (problem)
    No usable implementations:
      ptime.1.1.0: Doesn't build with dune
      ptime.1.0.0: Doesn't build with dune
      ptime.0.8.6: Doesn't build with dune
      ptime.0.8.5: Doesn't build with dune
      ptime.0.8.4: Doesn't build with dune
      ...
removing overlay repository [opam-overlays, mirage-overlays]
Repositories removed from the selections of switch dream-mirage-4.14.1. Use '--all' to forget about them altogether.
Repositories removed from the selections of switch dream-mirage-4.14.1. Use '--all' to forget about them altogether.
make[2]: *** [Makefile:36: mirage/hello-unix.opam.locked] Error 1
make[1]: *** [Makefile:39: lock] Error 2
make: *** [Makefile:51: depends] Error 2

To additionally check:
λ opam info ptime                                                                                2

<><> ptime: information on all versions <><><><><><><><><><><><><><><><><><><><>
name                   ptime
all-installed-versions 1.1.0 [dream-4.14.1 dream-5.0.0 dream-serve-4.14.1 /home/antron/code/style /home/antron/code/serve dream-social-4.14.1]
all-versions           0.8.0  0.8.1  0.8.2  0.8.3  0.8.4  0.8.5  0.8.5+dune  0.8.6  1.0.0  1.0.0+dune  1.0.0+dune2  1.1.0  1.1.0+dune

<><> Version-specific details <><><><><><><><><><><><><><><><><><><><><><><><><>
version      1.1.0+dune
repository   dune-universe
url.src      "https://github.com/dune-universe/ptime/releases/download/v1.1.0%2Bdune/ptime-1.1.0.dune.tbz"
url.checksum "sha256=9aa6645808ce539eeafe4eaf781d6d0ae5639c90592cee31d15cf9363acf9234"
             "sha512=0d037fc8f11c25b407f5501bd614dbbadb83fd6dce2fff5c0eeae27a9cd616f69f399f0cb3a04a2b0588cf1866cb16d6d1ae599791509cb995a92d3ae33ad1a0"
homepage     "https://github.com/dune-universe/ptime"
bug-reports  "https://github.com/dbuenzli/ptime/issues"
dev-repo     "git+https://github.com/dune-universe/ptime.git"
authors      "The ptime programmers"
maintainer   "Daniel Bünzli <daniel.buenzl<EMAIL_ADDRESS>license      "ISC"
tags         "time" "posix" "system" "org:erratique"
depends      "dune" "ocaml" {>= "4.08.0"}
synopsis     POSIX time for OCaml
description  Ptime has platform independent POSIX time support in pure OCaml. It
             provides a type to represent a well-defined range of POSIX timestamps
             with picosecond precision, conversion with date-time values,
             conversion with [RFC 3339 timestamps][rfc3339] and pretty printing to
             a human-readable, locale-independent representation.
             The additional Ptime_clock library provides access to a system POSIX
             clock and to the system's current time zone offset.
             Ptime is not a calendar library.
             Ptime has no dependency. Ptime_clock depends on your system library or
             JavaScript runtime system. Ptime and its libraries are distributed
             under the ISC license.
             [rfc3339]: http://tools.ietf.org/html/rfc3339
             Home page: <http://erratique.ch/software/ptime>

λ opam info dream-mirage

<><> dream-mirage: information on all versions ><><><><><><><><><><><><><><><><>
name         dream-mirage
all-versions ~dev

<><> Version-specific details <><><><><><><><><><><><><><><><><><><><><><><><><>
version     ~dev
pin         git+file:///home/antron/code/dreamworld/dream#patch-1
source-hash fcc20d00
url.src     "git+file:///home/antron/code/dreamworld/dream#patch-1"
homepage    "https://github.com/aantron/dream"
doc         "https://aantron.github.io/dream"
bug-reports "https://github.com/aantron/dream/issues"
dev-repo    "git+https://github.com/aantron/dream.git"
authors     "Anton Bachin<EMAIL_ADDRESS>maintainer  "Anton Bachin<EMAIL_ADDRESS>license     "MIT"
tags        "http" "web" "framework" "websocket" "graphql" "server" "http2" "tls"
depends     "bigarray-compat"
            "bigstringaf"
            "digestif" {>= "1.0.0"}
            "dream"
            "dream-httpaf"
            "dream-pure"
            "dune" {>= "2.7.0"}
            "duration"
            "emile" {>= "1.1"}
            "letsencrypt" {>= "0.3.0"}
            "lwt"
            "lwt_ppx" {>= "1.2.2"}
            "mimic" {>= "0.0.6"}
            "mirage-time"
            "rresult"
            "tcpip"
            "tls-mirage"
synopsis    Tidy, feature-complete Web framework
description Dream is a feature-complete Web framework with a simple programming
            model and no boilerplate. It provides only two data types, request and
            response.
            Almost everything else is either a built-in OCaml type, or an
            abbreviation for a bare function. For example, a Web app, known in
            Dream as a handler, is just an ordinary function from requests to
            responses. And a middleware is then just a function from handlers to
            handlers.
            Within this model, Dream adds:
            - Session management with pluggable back ends.
            - A fully composable router.
            - Support for HTTP/1.1, HTTP/2, and HTTPS.
            - WebSockets.
            - GraphQL, including subscriptions and a built-in GraphiQL editor.
            - SQL connection pool helpers.
            - Server-side HTML templates.
            - Automatic secure handling of cookies and forms.
            - Unified, internationalization-friendly error handling.
            - A neat log, and OCaml runtime configuration.
            - Helpers for Web formats, such as Base64url, and a modern cipher.
            Because of the simple programming model, everything is optional and
            composable. It is trivailly possible to strip Dream down to just a
            bare driver of the various HTTP protocols.
            Dream is presented as a single module, whose API is documented on one
            page. In addition, Dream comes with a large number of examples.
            Security topics are introduced throughout, wherever they are
            applicable.

It's super weird because opam-monorepo doesn't see packages from the dune-universe repository. But they seem to be added by the makefile:
using overlay repository mirage: [opam-overlays, mirage-overlays]
[opam-overlays] no changes from git+https://github.com/dune-universe/opam-overlays.git
[NOTE] Repository opam-overlays has been added to the selections of switch dream-mirage-4.14.1 only.
       Run `opam repository add opam-overlays --all-switches|--set-default' to use it in all existing switches, or in newly created switches, respectively.

[mirage-overlays] no changes from git+https://github.com/dune-universe/mirage-opam-overlays.git
[NOTE] Repository mirage-overlays has been added to the selections of switch dream-mirage-4.14.1 only.
       Run `opam repository add mirage-overlays --all-switches|--set-default' to use it in all existing switches, or in newly created switches, respectively.

@tmcgilchrist 's patch works for me on Opam 2.1.5 and OCaml 5.1.0. I had to put an upper bound on caqti-lwt<2.0.0 (unrelated problem on master)

#+TITLE: Testing Dream Mirage
#+AUTHOR: Tim Dysinger
#+EMAIL<EMAIL_ADDRESS>#+DATE: <2023-10-06 Fri>
#+OPTIONS: toc:nil
@aantron, I have taken the time to show that @tmcgilchrist patch works with a demo.
Here I started with master and cherry-picked @tmcgilchrist's ebb6d5705bcdad4ed535641fd2437a32d6e20aa0 commit.
#+BEGIN_SRC text
~/src/ml/dream> git checkout -b test upstream/master
branch 'test' set up to track 'upstream/master'.
Switched to a new branch 'test'
~/src/ml/dream> git cherry-pick ebb6d5705bcdad4ed535641fd2437a32d6e20aa0
[test 0f112ee] Update Dream_mirage with remove deprecated values changes.
Author: Tim McGilchrist<EMAIL_ADDRESS>Date: Tue May 16 10:49:02 2023 +1000
2 files changed, 22 insertions(+), 40 deletions(-)
~/src/ml/dream> git submodule update
#+END_SRC
Then I added the following Dockerfile to the base of Dream repo:
#+BEGIN_SRC dockerfile :tangle Dockerfile
ARG ocaml
FROM ocaml/opam:debian-unstable-ocaml-$ocaml as base
INSTALL OPAM 2.1 & MIRAGE
ARG mirage
ADD https://raw.githubusercontent.com/ocaml/opam/master/shell/install.sh /tmp/
RUN sudo chmod 755 /tmp/install.sh
RUN sudo sed -i 's|read BINDIR|BINDIR=/usr/local/bin|' /tmp/install.sh
RUN /tmp/install.sh
RUN opam install mirage=$mirage
COPY & PIN THIS REPO
COPY ./ /usr/local/src/dream/
RUN opam pin -n dream        /usr/local/src/dream
RUN opam pin -n dream-pure   /usr/local/src/dream
RUN opam pin -n dream-httpaf /usr/local/src/dream
RUN opam pin -n dream-mirage /usr/local/src/dream
CLONE THE EXAMPLE
WORKDIR /usr/local/src/example
RUN sudo chown $(whoami) /usr/local/src/example
RUN rsync -r /usr/local/src/dream/example/w-mirage/ /usr/local/src/example/
COMPILE KVM IMAGE
FROM base as hvt
RUN opam exec -- mirage configure -t hvt
RUN opam exec -- make
COMPILE XEN IMAGE
FROM base as xen
RUN opam exec -- mirage configure -t xen
RUN opam exec -- make
COMPILE VIRTIO IMAGE
FROM base as virtio
RUN opam exec -- mirage configure -t virtio
RUN opam exec -- make
COMPILE POSIX EXE
FROM base as unix
RUN opam exec -- mirage configure -t unix
RUN opam exec -- make
RUNTIME POSIX IMAGE
FROM debian:unstable as runtime
RUN apt-get update ; apt-get install -y libev4 libgmp10
COPY --from=unix /usr/local/src/example/dist/hello /usr/local/bin/hello
ENTRYPOINT /usr/local/bin/hello
EXPOSE 8080
#+END_SRC
I used Docker to build, with each version of OCaml, a dream-mirage 'hello' unikernel (or 4.)
#+BEGIN_SRC sh
docker build --build-arg ocaml=4.10 --build-arg mirage=4.2.1  --tag dream-mirage-hello:ocaml-4.10+mirage-4.2.1 ./.
docker build --build-arg ocaml=4.12 --build-arg mirage=4.4.0  --tag dream-mirage-hello:ocaml-4.12+mirage-4.4.0 ./.
docker build --build-arg ocaml=4.14 --build-arg mirage=4.4.0  --tag dream-mirage-hello:ocaml-4.14+mirage-4.4.0 ./.
docker build --build-arg ocaml=5.0  --build-arg mirage=4.4.0  --tag dream-mirage-hello:ocaml-5.0+mirage-4.4.0  ./.
docker build --build-arg ocaml=5.1  --build-arg mirage=4.4.0  --tag dream-mirage-hello:ocaml-5.1+mirage-4.4.0  ./.
#+END_SRC
If it compiles it will run with docker run like so:
#+BEGIN_SRC sh

docker run -i -t --rm -p 8080:8080 dream-mirage-hello:ocaml-4.14+mirage-4.4.0
2023-10-06 11:37:39 +00:00: INF [tcpip-stack-socket] Dual IPv4 and IPv6 socket stack: connect
#+END_SRC

The following is a table of what worked and what did not:
| Dream | OCaml | Mirage | Mirage Compiled? | Example Compiled? | Note                                                          |
|-------+-------+--------+------------------+-------------------+---------------------------------------------------------------|
| ~dev  |  4.08 |        |                  |                   | 4.10 isn't working so I didn't bother with 4.08               |
| "     |  4.10 | 3.10.8 | Yes              | No                | config.ml (mirage api) error                                  |
| "     |  4.10 |  4.2.1 | Yes              | No                | resolve error                                                 |
| "     |  4.10 |  4.3.6 | No               | No                | resolve error                                                 |
| "     |  4.10 |  4.4.0 | No               | No                | resolve error                                                 |
| "     |  4.12 |  4.4.4 | Yes              | Yes               |                                                               |
| "     |  4.14 |  4.4.0 | Yes              | Yes               |                                                               |
| "     |   5.0 |  4.4.0 | Yes              | Yes/No            | posix works, ocaml-solo5: Requires ocaml >= 4.12.1 & < 4.15.0 |
| "     |   5.1 |  4.4.0 | Yes              | No                | resolve error                                                 |
| "     |   5.2 |  4.4.0 |                  |                   | 5.1 isn't working so I didn't bother with 5.2                 |
In summary, I vote to at least cherry-pick ebb6d5705bcdad4ed535641fd2437a32d6e20aa0. Nothing with mirage works without it.

I'm running a topgit stack of patches for Dream, so I am able to do my thing, but I would love to see Mirage working again in master.

I was able to get this working now and I'm ready to merge. Thank you and sorry for the huge delay!
Why is there a bound of 0.0.6 on Mimic now?
As for Lwt_ppx, it seems like that bound would have to be fixed upstream. If that's not an option, we can still merge it, though. If we need to do it in Dream, would it be better to put the 2.1.0 bound into dream-mirage.opam rather than dream.opam?

I reverted the Lwt_ppx constraint change, because (1) I was unable to reproduce the problem it was trying to fix, (2) to first appearances, it seems like it should be addressed upstream and not in Dream, could be wrong about that, (3) I could not make sense of the error message "complex open are not supported before OCaml 4.08" in light of the fact that Dream has OCaml 4.08 as a lower bound.
I was able to lower the mimic constraint to 0.0.5, as required by the vendored paf. Everything still appears to build and work.

Thank you!
Please send more PRs, or link me to any public forks that I can cherry-pick more patches from!

Thanks for merging this fix @aantron
I have not been doing any Dream / Mirage work recently and forgot about this PR. The main users of this functionality are https://github.com/ocurrent/mirage-ci, https://github.com/mirage/mirage-www and the linked ocaml-matrix library.

I could not make sense of the error message "complex open are not supported before OCaml 4.08" in light of the fact that Dream has OCaml 4.08 as a lower bound.

I think it was caused by lwt_ppx using an old version of the ocaml parse tree to do transforms but I can't reproduce it anymore either.


qemu: desktop files not built for emulation

Motivation for this change
Qemu will only install desktop files on "system" builds,
if you build qemu for emulation (eg: aarch64-linux-user) as
it is used for nix emulated builds, build will fail with error:
rm: cannot remove '/nix/store/nzwv6nkzidyp6vvclip70a5kw1vlvwpp-qemu-5.2.0/share/applications/qemu.desktop': No such file or directory
As it is not installed.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

Duplicate of #110721

Duplicate of #110721


tests: Windows tests small cleanup

What this PR does / why we need it:
Cleans up windows test code:

Removes tests checking kubectl - it is not windows specific
Removes tests that check VM start and stop - also not windows specific
Simplify test code

Release note:
None

/sig code-quality

/lgtm
Thank you @akrejcir!

/retest

/retest

/approve
/hold
@kbidarkar Can you please confirm? Thanks!

/unhold , because of @kbidarkar recent comment

/unhold


FlightTask: Yawspeed slew rate for smooth motion

Describe problem solved by this pull request
This is a split out from the monster pr #12072. At the same time it provides a comparable solution to #13430.
Describe your solution

I created a SlewRate class which implements a generic template slew rate with unit testing.
I created a PositionLock class to handle reusable position and yaw lock logic for stick flying. It implements the yaw handling using the SlewRate which this pr is about and breaks out other already duplicate or well reusable related functions. This is part of the effort to make the whole flight task library more rely on reusable libraries than on overly complex inheriting.
I adapted FlightTaskManualAltitude and FlightTaskManualPosition to call the reusable functions inside PositionLock.

Describe possible alternatives
A low pass filter like suggested in #13430.
Test data / coverage
SlewRate has unit testing, PositionLock I tested a lot in SITL and also multiple times on a real vehicle before it was 1:1 taken over from #12072. The calls based on current master are untested at the moment.

The lowpass method showed good results and there is no obvious reasons why we should try something different now. Closing for now and we can still re-open if we change our mind.


feat: add pr template and issue templates

I would like to add the pull request and issue templates so that it'll be easy for folks contributing to the project to mention the reason in a structured manner.

Go for it! :)


change multi-line aliases to functions

Although not really necessary, functions can be easier to read than multi-command aliases.
Feel free to reject this or rework for your own workflow.
Great git presentation at LFNW 2015, BTW! :penguin:
Signed-off-by: Ryan P.C. McQuen<EMAIL_ADDRESS>

Thank you!

Enjoy!


[Bug] [web] scroll bar is missing when table display out of screen

Search before asking

[X] I had searched in the issues and found no similar issues.

Operating system information
Linux
Python version information
3.10
DB-GPT version
main
Related scenes

[X] Chat Data
[ ] Chat Excel
[ ] Chat DB
[ ] Chat Knowledge
[ ] Model Management
[ ] Dashboard
[ ] Plugins

Installation Information

[X] Installation From Source

[ ] Docker Installation

[ ] Docker Compose Installation

[ ] Cluster Installation

[ ] AutoDL Image

[ ] Other

Device information
CPU: Intel Xeon Processor (Skylake)
NUMA node0 CPU(s):     0-15
GPU:NONE
OS: centos 7.9
Models information
LLM: chatgpt-3.5
embedding: text2vec-large-chinese
What happened

What you expected to happen
There is a scroll bar when table display is not completed.
How to reproduce

open a session for chat data
make dbgpt response a table with a enough width

Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Thanks for your feedback, we will fix it in the feature.


javascript.validate.enable for certain folders

Currently I have many projects in a one workspace. Some projects use Typescript JSDoc comments other use Flow. When I edit any files in Flow projects the JS linter shows many errors, therefore I should disable it. But if I will disable the JS linter then the Typescript JSDoc validation  doesn't work anymore.
Would be the best way to be able to disable/enable javascript.validate.enable setting in projects.

https://code.visualstudio.com/docs/editor/multi-root-workspaces
https://code.visualstudio.com/docs/getstarted/settings#_creating-user-and-workspace-settings

@octref there is no answer how can I set javascript.validate.enable per folders in a workspace.

@octref oh yes, thanks.

@octref only it doesn't work.
I've created folder .vscode in one subfolder of my workspace and I've put there .code-workspace file:
{
  "folders": [
    {
      "path": "../"
    }
  ],
  "settings": {
    "javascript.validate.enable": true
  }
}

But it hasn't any effect. I tried to change the folder path, I tried without the folder path. Also I even tried create the settings.json with content { "javascript.validate.enable": true } but then the editor showed  warning me that it will be applied only when I will open this folder directly (i.e. not in my workspace).

I think you are looking for "javascript.implicitProjectConfig.checkJs": true.

@octref no, I don’t use checkJs because I have tsconfig.json in those root folders where I want Typescript check JS files. And some root folders have Flow types therefore there Typescript shouldn’t work.

"javascript.validate.enable": true only enables syntactical checks. This works for me in a multi-root folder.

@octref you show me how you change it for whole workspace. Though I told you about certain folders in one workspace. I can't set this setting at the folder level in one workspace. My workspace contains many Github repos. Some repos use Flow types other use Typescript in JSDoc comments. That type checking in VSCode works for JSDocs comments I need this setting to turn on. But because I can't turn on this setting only for certain repos in my workspace other repos which use Flow types shown with errors on Flow types annotations (because VSCode doesn't support Flow without separate extension). Therefore now I when edit files in a Typescript project I enable this setting but when I edit files in a Flow types project I disable it. Only it is very not comfortable because I often have are open files from both types of projects.

I don't know why this setting is window scoped, meaning it can only be set in user/workspace/remote settings but not folders. Giving to @mjbvz.


[WIP] Updated Landing Page

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


[FEAT] Linux support

I like macos big sur themes so I want to make firefox look like safari,but this theme doesn't work on Linux.

I'd recommend trying this theme if you're using linux: https://github.com/vinceliuice/WhiteSur-gtk-theme/tree/master/src/other/firefox

Does that also work for kde?
And also,I just want to use the safari theme,I don't want to use a whole different gtk theme.

You can always copy the folder in the link above into your firefox profile folder to get it working. Otherwise i'm pretty sure you can use the ./tweaks.sh -f script to install it automatically also

Hi @AdamXweb Are you the author of "Firefox CSS Theme Store"?

@AdamXweb Does this look the same as your project?

@Toadfield Actually yeah. @AdamXweb You gotta learn about licensing and don't forget to add COPYING in your repo :D But don't worry tho, I already asked Vince to relicense WhiteSur to MIT which is more permisive

But it would be cooler if this would work on Linux cause this is more than a firefox theme,but I only need the firefox theme.

It's usable but doesn't quiet work
WhiteSurFirefoxThemeMacOS

WhiteSur GTK Theme

I think we need some query to detect the OS so we can make this theme more portable. References:

https://codepen.io/jimmykup/pen/ExarGPG
https://stackoverflow.com/questions/8493589/is-there-a-css-media-query-to-detect-windows

Hi @AdamXweb Are you the author of "Firefox CSS Theme Store"?

Nope, I just added the theme with a pull request into their main repo

But it would be cooler if this would work on Linux cause this is more than a firefox theme,but I only need the firefox theme.

It would be cool, however like what @rivanfebrian123 mentioned with licensing and copying, i've tried to avoid stepping too close to the original, and to make something for PC and Mac users. If @vinceliuice and @rivanfebrian123 are ok with it, i'd be happy to add support for Linux

@Toadfield Actually yeah. @AdamXweb You gotta learn about licensing and don't forget to add COPYING in your repo :D But don't worry tho, I already asked Vince to relicense WhiteSur to MIT which is more permisive

I'll be sure to add it this week!

It's usable but doesn't quiet work
I think we need some query to detect the OS so we can make this theme more portable. References:
* https://codepen.io/jimmykup/pen/ExarGPG

* https://stackoverflow.com/questions/8493589/is-there-a-css-media-query-to-detect-windows

Definitely possible! The theme already has a few windows specific features (using media queries), so adding some for linux shouldn't be too difficult hopefully
Also, I should have a few updates later this week, just been a bit preoccupied moving house

however like what @rivanfebrian123 mentioned with licensing and copying, i've tried to avoid stepping too close to the original, and to make something for PC and Mac users

Hey, you know what? WhiteSur is now MIT licenced, so distributors like you, don't have to worry about taking some code from the upstream repo.

Definitely possible! The theme already has a few windows specific features (using media queries), so adding some for linux shouldn't be too difficult hopefully

Just don't worry about those "bloated" things :) Keep your code clean and neat so it wouldn't be that huge and scary. CMIIW

For others looking for Linux support, please check this out:
https://github.com/vinceliuice/WhiteSur-firefox-theme
I'm in the process of adding variables to the theme so that it'll be universal and more compatible. Progress can be viewed here until I receive access to the repo to make modifications:
https://github.com/AdamXweb/WhiteSur-firefox-theme/tree/MacOSWindowsSupport


Is it possible to have a deeper nested path?

For example,
GET /users/{fred}/resources
GET /users/{fred}/resources/{resource}
I am not able to get either of these to work.  Is this possible?

figured it out - was a problem w/ my nginx server


Results are now showing in sorted order by rating

Results are now displayed in descending order by rating

closes #10

Good work on the code


Dev Priorities / Timeline

Student

[ ] Application Summary
[ ] Application Offering dates to use in application
[ ] Display Offering, no dates/costs?
[ ] Save assessment
[ ] Display assessment
[ ] income validation
[ ] Select what to apply for
[ ]
Institution
[ ] Complete program information request
[ ] Confirm enrollment
[ ]
Integrations
[ ] ESDC File Integration
[ ] ATBC Integration
[ ]
Technical Abilities
[ ] Reassessment
[ ] Cancel Application
[ ] Audits
[ ] Save draft application
[ ]
Ministry Portal
[ ] What do?
[ ]

Sprint board updated to reflect dev discussions


Add missing virtual repos for cargo, and vagrant

The virtual repository resource for cargo and vagrant are missing. I've tried to use the virtual generic for existing repositories, but Artifactory failed with:
│ Error:
│ 400 POST https://<artifactory>/artifactory/api/repositories/<cargo-repo>
 {
│   "errors" : [ {
│     "status" : 400,
│     "message" : "Changing a repository's type once it's set is not supported"
│   } ]
│ }

Describe the solution you'd like
Support virtual repository resources for cargo and vagrant:
artifactory_virtual_cargo_repository
artifactory_virtual_vagrant_repository
Describe alternatives you've considered
I tried to use the virtual_generic but it failed when applying the changes. Also it seems this doesn't allow setting the package_type, which would be useful to avoid the above error
Additional context
This is part of a painful migration from the version 2+ where generic resources matched pretty much the Artifactory REST API.

@rinconjc, thanks for the ticket! I'll add the missing repos soon. Can you please explain, what do you mean by ...generic resources matched pretty much the Artifactory REST API? What doesn't match now?

Hmm, @rinconjc virtual Cargo and Vagrant repositories are not supported by Artifactory. See the list of supported repositories in 7.46.8:

Hi @danielmkn thanks for your quick reply :)
Sorry, that might have sounded as a criticism :( What I meant is that there's only 1 Artifactory API endpoint to create all the repository types, and the earlier provider version (2+) also had only one resource, so we were able to reuse quite a lot. On the plus side, I understand that now there's more strict validation in Terraform side.

Hi @danielmkn right I see that now. Hmm I'm guessing the API allows creating virtual repos for cargo and vagrant, and that's how the previous provider version managed to create the virtual repos for them. :(

The provider is reflecting the behavior you see in the UI, so I'd rather not try to create repos you don't see there :)

@danielmkn  The docs here https://github.com/jfrog/terraform-provider-artifactory/blob/master/docs/resources/virtual.md, mention explicitly:

Arguments have a one to one mapping with the JFrog API. The following arguments are supported: ...

And in the above configuration, cargo and vagrant are really supported in the packageType for virtual repository configuration:
application/vnd.org.jfrog.artifactory.repositories.VirtualRepositoryConfiguration+json
...
  + "packageType": "alpine"|"cargo"|"composer"|"bower"|"chef"|"cocoapods"|"conan"|"cran"|"debian"|"docker"|"helm"|"gems"|"gitlfs"|"go"|"gradle"|"ivy"|"maven"|"npm"|"nuget"|"opkg"|"pub"|"puppet"|"pypi"|"rpm"|"sbt"|"swift"|"terraform"|"vagrant"|"yum"|"generic" (default)

Alternatively, if the UI is to be taken as the reference, then maybe the docs should also be updated to avoid confusion (and false expectations)
Thanks

Yes, you're right. I'll figure out the truth and update here.

Hi @rinconjc! The API documentation has been updated! Cargo and Vagrant repos are removed now, because they are not supported.


Remove unused model HostsStorages

There is a HostsStorages and HostsStorage model.
Merged them.
/cc @agrare

I believe there was a reason for the 2 models, but I can't remember...maybe @agrare does.

@Fryguy thanks.
Verified with him, and we think it was an oversight.

@Fryguy Not sure why two modes, hosts_storages was added in 2010 and hosts_storage in 2011.  Agree with @kbrock think it was just an oversight.


sniþþetrosh

HOME
LABELS
STARS

http://git.io/snippetrosh
þ = þ ASCII code 231, Lowercase letter Thorn
Features
Keyboard shortcuts
using-keyboard-shortcuts

c: Create an issue
/: Focus the issues search bar
l: Filter by or edit labels
m: Filter by or edit milestones
a: Filter by or edit assignee
r: Quote the selected text in your reply

Searching
With searching-issues you can use sharing-filters for quick links.

Issues search bar: priority no:label type:issue
exculde pulls search-by-missing-metadata-on-an-issue-or-pull-request

Update don't Erase
Issues cannot be deleted, you can close and put it in Closed tab.
Only thing you cannot edit is created_at.

Edit issue 🆓 along with Title and Labels
Comment issue, for time tracking, cannot delete ⛔

Edit comment 🆓
Permalink comments 🆓

Editor

Attach images by dragging & dropping, selecting them, or pasting from the clipboard.
More than just images: PDF, Word, Excel, PowerPoint, and text files
Deep undo ⌘Z

Recover
If you mess up with tabs

⌘Y ⇢ chrome://history/
Open last tabs
Search on back button's history for New Issue

Anyway ⌘A ⌘C

Markdown
Todo lists showed as

Link to highlighted code

View a file and highlight code
Press Y to expand URL to its canonical form: getting-permanent-links-to-files
Copy the URL, example

References
You can link to this post with #7 #7

Local issue – #Num: #7
Local issue – User#Num: petrosh#1
Remote issue – User/Repository#Num: jlord/sheetsee.js#26
Local SHA – SHA: 52e27423c74b4e0ce700eb70c827b30782e4007c
Remote SHA – User@SHA: jlord@a5c3785ed8d6a35868bc169f07e40e889087fd2e
Remote SHA – User/Repository@SHA: jlord/sheetsee.js@a5c3785ed8d6a35868bc169f07e40e889087fd2e
Mistery issue – GH-Num: GH-7

Emoji
We all :cupid: that :expressionless:

Shortcut: ⌃⌘space and digit
Snippet: : and digit
Cheatsheet

Ideas

[ ] Folder in master to fast create/paste files
[ ] Put some of this on README.md (or link here #7) with fast links (1 click away)
[x] Milestones for alarms – https://github.com/starsystem/starsystem.github.io/milestones
[ ] Make un tepijo con snippetrosh e funzioni incorporate

always remember michael/github#105

Domains

gattiecani.org	22/7/2016	Redirect senza Posta
huguette.it	14/12/2016	Redirect
petrosh.com	26/9/2016	Hosting Linux Basic
petrosh.it	19/6/2016	Hosting Windows Basic
raveuprecords.com	8/11/2016	Gestione DNS senza posta


CTest3 is No longer used.

CTest3 is No longer used.

[AMD Official Use Only - General]
Line 32 deleted.
From: Saad Rahim @.>
Sent: Wednesday, November 23, 2022 10:17 AM
To: ROCmSoftwarePlatform/rocThrust @.>
Cc: Kostrov, Sergiy @.>; Author @.>
Subject: Re: [ROCmSoftwarePlatform/rocThrust] CTest3 is No longer used. (PR #261)
Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
@saadrahim commented on this pull request.

In .jenkins/common.groovyhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FROCmSoftwarePlatform%2FrocThrust%2Fpull%2F261%23discussion_r1030707896&data=05|01|Sergiy.Kostrov%40amd.com|ab2b50674df84236c2ae08dacd7689fa|3dd8961fe4884e608e11a82d994e183d|0|0|638048206249738852|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=nSqw58xip9PHUhFaPEwIvZ9zROFkAHxxRnHg2baVlXg%3D&reserved=0:

@@ -31,8 +31,7 @@ def runTestCommand (platform, project)

 String sudo = auxiliary.sudo(platform.jenkinsLabel)

 String centos = platform.jenkinsLabel.contains('centos') ? '3' : ''

do you need this line anymore?

Reply to this email directly, view it on GitHubhttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FROCmSoftwarePlatform%2FrocThrust%2Fpull%2F261%23pullrequestreview-1192036715&data=05|01|Sergiy.Kostrov%40amd.com|ab2b50674df84236c2ae08dacd7689fa|3dd8961fe4884e608e11a82d994e183d|0|0|638048206249895076|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=PqrNxtkwnm%2FS1bB526eKzbUxhKCteB6kAOnD7iZy%2B7g%3D&reserved=0, or unsubscribehttps://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA4BZS3ENB3T2EQWEBRRTRJDWJZGQ5ANCNFSM6AAAAAASG52BTQ&data=05|01|Sergiy.Kostrov%40amd.com|ab2b50674df84236c2ae08dacd7689fa|3dd8961fe4884e608e11a82d994e183d|0|0|638048206249895076|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=ol7VdkHG8ptiVIlSQPtUtwNb1w7dbeEYTjBcwyJ7Gm0%3D&reserved=0.
You are receiving this because you authored the thread.Message ID: @.***>


Extract Shared Assessment Layout from modeling assessment ui

Checklist

[x] I tested the changes and all related features on the test server https://artemistest.ase.in.tum.de.
[x] I documented my source code using the ~JavaDoc /~ JSDoc style.
[x] ~I added integration test cases for the server (Spring) related to the features~
[X] I added integration test cases for the client (Jest) related to the features
[X] I added screenshots/screencast of my UI changes
[x] ~I translated all the newly inserted strings~

Motivation and Context
For updating the text assessment UI, we want to reuse existing UI from modeling assessment.
Description
This PR extracts a majority of the modeling assessment layout into it's own component, so we can simply reuse it for text exercises. This does not modify the visual appearance!
Steps for Testing

Participate with a modeling exercise (create before if necessary)
Assess your submission
Submit a complaint
Respond to the complaint
Find no differences to the same flow before this change.

Screenshots

This is also not related to this specific PR, but I am able to submit score, that is more than maximal and this value is saved in Modeling Assessment Editor (even if I exit and open it again). On the tutor exercise dashboard it is saved properly. But maybe we should warn tutor that he exceeded the maximum amount of points.

@maxr96: this is the intended behavior. Tutors are allowed to submit scores higher than the max score, for the student the displayed score is limited by the max score though. A warning about exceeding the max score might be a good idea, but it is out of scope of this PR.

Since you already try to generalize the whole layout, it would be awesome if we have the same header as for text exercise. This is what I planned to do anyway.
-- @maxr96

Currently, we are planning to move away from the large header in the text exercises a well, as this is mostly wasting space.

This issue is probably not really related to this PR, but when I try to add feedback for class the dialog is a bit cut off. This works properly for Chrome, but not Firefox (both tested on Linux)
-- @maxr96

If this is still the case, we should raise a separate issue for this.

Note, that this PR will conflict with #794 where I change the query parameter showBackButton to hideBackButton.
-- @SiggZ

I updated this PR with your changes.


ARROW-11259: [Python][Dataset] Allow creating nested field ref

We can't yet filter on a nested field ref, so this merely adds syntactical support.

but does it add value to support construction of nested field references if we can't filter on them yet

Probably not, but it also should be relatively orthogonal to future refactors?

We do plan to support nested field references in filters? If so I am fine with already merging this, but no strong opinion.

Should I close this PR? @bkietz

Now there is actual support for nested field refs (https://github.com/apache/arrow/pull/11466), this PR can be revived?

@jorisvandenbossche Do you want to take it up?

Yes, will do


Update the GIF in the README

Update the GIF in the README to show the current website.

I would like to work on this ?
Can you Please add the GGSoC label ?

I would like to work on this .
Can you please add the GSSoC label ?

Sir is it okay ?

Sir is it okay ?

Looks good.

Sir what should i do in this ? it is showing all the commits ?

But if i compare gif-new with your master branch then it will show only one commit .


Elasticsearch

I'm actually skipping the S3 step as it seems most efficient to insert into Elasticsearch directly.
Schema design
Using a single index for now, pages, with the following fields:

url
timestamp
content type
status code
body
text

Kibana dashboard
Here's how the Kibana dashboard looks like:

Sample search:

Reviewing within the next hour

This looks great! We can plan more how we want to integrate this into a search page on crossfeed, and maybe add some of these views to the risk dashboard page for visualizations.
We'll also want to plan out the kind of data we're extracting from crawls, e.g. like https://github.com/hakluke/hakrawler JavaScript files (which we could then run tools like https://github.com/GerbenJavado/LinkFinder to find relative urls), urls, external JS files, etc.

Adding @jhackshaw & @TimLillis for front-end / UX things related to this request

Superseded by #438.


Documentation Out of Date

A user reports that our documentation has my_projects = rf.projects() but this causes an error. Likely because it needs to come from the workspace vs the top level Roboflow object. The docs likely need to be updated.
Other docs that may be out of date:

rf.project("project-id") is not clear that you need to also include the workspace id.
all_version=project.versions() may need to be my_projects.list_versions()

We should go through the docs & dogfood them to ensure they work with the current version of the roboflow pip package.

Hey @yeldarby , is this issue still valid?

Closing due to inactivity, new doc will come along with all the new changes


Karpenter fails to provision some nodes due to swap partition and getting stuck

Description
Observed Behavior:
Karpenter stuck on provisioning
Reproduction Steps (Please include YAML):
Given the following config:
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  annotations:
    karpenter.sh/provisioner-hash: "15591017375434095235"
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"karpenter.sh/v1alpha5","kind":"Provisioner","metadata":{"annotations":{},"name":"default"},"spec":{"consolidation":{"enabled":true},"kubeletConfiguration":{"containerRuntime":"containerd","maxPods":110},"limits":{"resources":{"cpu":500}},"providerRef":{"name":"default"},"requirements":[{"key":"karpenter.sh/capacity-type","operator":"In","values":["spot"]},{"key":"karpenter.k8s.aws/instance-category","operator":"In","values":["c","m","t"]},{"key":"karpenter.k8s.aws/instance-size","operator":"In","values":["small","medium"]},{"key":"kubernetes.io/arch","operator":"In","values":["arm64","amd64"]}],"ttlSecondsUntilExpired":604800}}
  creationTimestamp: "2023-09-13T13:43:40Z"
  generation: 1
  name: default
  resourceVersion: "304744"
  uid: aabfb199-16e2-4093-a740-9cdd2686c7f2
spec:
  consolidation:
    enabled: true
  kubeletConfiguration:
    containerRuntime: containerd
    maxPods: 110
  limits:
    resources:
      cpu: "500"
  providerRef:
    name: default
  requirements:
  - key: karpenter.sh/capacity-type
    operator: In
    values:
    - spot
  - key: karpenter.k8s.aws/instance-category
    operator: In
    values:
    - c
    - m
    - t
  - key: karpenter.k8s.aws/instance-size
    operator: In
    values:
    - small
    - medium
  - key: kubernetes.io/arch
    operator: In
    values:
    - arm64
    - amd64
  - key: kubernetes.io/os
    operator: In
    values:
    - linux
  ttlSecondsUntilExpired: 604800
status:
  resources:
    cpu: "4"
    ephemeral-storage: 62902252Ki
    memory: 5265744Ki
    pods: "330"

#➜ kubectl get awsnodetemplate default -o yaml
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  annotations:
    karpenter.k8s.aws/nodetemplate-hash: "7233672322700999508"
  creationTimestamp: "2023-09-13T13:43:40Z"
  generation: 1
  name: default
  resourceVersion: "308102"
  uid: 04da1248-79a6-4ba9-b1e7-a7ee8813e85b
spec:
  instanceProfile: karpenter-dev-tooling-eks
  securityGroupSelector:
    karpenter.sh/discovery: dev-tooling-eks
  subnetSelector:
    karpenter.sh/discovery: dev-tooling-eks
  tags:
    Name: dev-tooling-eks-karpenter-node
    Project: dev-tooling-eks
    Terraform: "Yes"
    karpenter.sh/discovery: dev-tooling-eks
status:
  amis:
  - id: ami-013895b64fa9cbcba
    name: amazon-eks-node-1.27-v20230825
    requirements:
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
    - key: karpenter.k8s.aws/instance-gpu-count
      operator: DoesNotExist
    - key: karpenter.k8s.aws/instance-accelerator-count
      operator: DoesNotExist
  - id: ami-0fe7215c073c7bb34
    name: amazon-eks-gpu-node-1.27-v20230825
    requirements:
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
    - key: karpenter.k8s.aws/instance-accelerator-count
      operator: Exists
  - id: ami-0fe7215c073c7bb34
    name: amazon-eks-gpu-node-1.27-v20230825
    requirements:
    - key: kubernetes.io/arch
      operator: In
      values:
      - amd64
    - key: karpenter.k8s.aws/instance-gpu-count
      operator: Exists
  - id: ami-0266a75a5e281d943
    name: amazon-eks-arm64-node-1.27-v20230825
    requirements:
    - key: karpenter.k8s.aws/instance-accelerator-count
      operator: DoesNotExist
    - key: kubernetes.io/arch
      operator: In
      values:
      - arm64
    - key: karpenter.k8s.aws/instance-gpu-count
      operator: DoesNotExist
  securityGroups:
  - id: sg-068bb2a93d25bf751
    name: eks-cluster-sg-dev-tooling-eks-1960709586
  subnets:
  - id: subnet-0189c195194d93fb9
    zone: us-east-1b
  - id: subnet-05b6b7b4eaa4d1dc3
    zone: us-east-1a

Karpenter tries to launch 3

nodes (to satisfy affinity requests for haproxy)
Only one node with t3.small architecture comes up, 2 others (m1.small) won't. Karpenter will try to delete and recreate them by joining ttl but since it's trying to reuse the same machines, they won't join the cluster.
I realize that this is probably fixable by setting higher generation (has not tried yet), but my question is: given the persistence of the behaviour, should not karpenter switch to another instance type if the chosen once constantly fails?
Full log
controller.log
Versions:
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27+", GitVersion:"v1.27.4-eks-2d98532", GitCommit:"3d90c097c72493c2f1a9dd641e4a22d24d15be68", GitTreeState:"clean", BuildDate:"2023-07-28T16:51:44Z", GoVersion:"go1.20.6", Compiler:"gc", Platform:"linux/amd64"}

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Unclear to me why the small was unable to join
2023-09-14T10:40:59.070Z	DEBUG	controller.machine.lifecycle	terminating due to registration ttl	{"commit": "637a642", "machine": "default-bc9lg", "provisioner": "default", "ttl": "15m0s"}

Any chance you can dig into the kubelet logs? https://karpenter.sh/docs/troubleshooting/#node-notready. Hard to guess

given the persistence of the behaviour, should not karpenter switch to another instance type if the chosen once constantly fails?

We try to avoid being "smart" like this, since we really don't know why the node won't join. In these unknown scenarios, we'll try again, but if you tell us to use smalls, we'll keep trying. We expect operators to identify these cases and determine the misconfiguration.

Ah, the reason was the presence of the swap partition. Kubelet was refusing to come up due to that.
Once I've added generation requirement (without touching anything else), the error went away and new nodes were able to join the cluster.

We try to avoid being "smart" like this, since we really don't know why the node won't join. In these unknown scenarios, we'll try again, but if you tell us to use smalls, we'll keep trying.

What I meant is: lets say that karpenter has a list of 10 possible choices for deployment, as far as I understand it will try with the cheapest one, so my suggestion was more along the lines of "if the lowest one does't work, try with the next one in the list and report the issue"
But I do get your point, probably we might add the case scenario in the troubleshooting document above that  m1.small and c1.medium instances will never be able to join the cluster because of the swap
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-store-swap-volumes.html

The c1.medium and m1.small instance types have a limited amount of physical memory to work with, and they are given a 900 MiB swap volume at launch time to act as virtual memory for Linux AMIs.

"if the lowest one does't work, try with the next one in the list and report the issue"

It's not possible for us to tell if it's a transient failure, or a permanent issue. Further, we want to provide operators with the opportunity to correct misconfigurations. If we just went up a size, operators may be frustrated that they're paying more, when they would have rather fixed the issue on the smaller size.

Sure, should be able to do so.

Hello,
How could the issue be solved, except excluding special instance types?
Best regards,
Andrei


Fix bugs

Hi, cuda-grep developers!
I fixed some bugs, that crashes cuda-grep on cuda 5.
() at nfa.cpp the last line was forgotten if file does't contain '\n' at the end
() in main function pMatch is called and in third arg the pointer to numRegexes is passed,
and this pointer dereference in device and kernel crash.
(*) this line wrong.    source[++newLen] = '\0';
(*) cudaFree(&devResult); i don't know what prototype has this function later, but now
cudaError_t cudaFree ( void * devPtr)
(*) in tests grep must match whole line, but not subline. key -x does this.

Confirmed working again!
Thanks!


Add code of conduct from link

Fill in the code of conduct rather than linking to CNCF code of conduct to list available escalation points related to this project.

Maybe this PR doesn't make sense anymore since the project is under CNCF now. Linking prevents the code of conduct from becoming out of date

This is maybe a question for @caniszczyk, but I noticed Prometheus and some other CNCF projects do link to CNCF CoC in their source tree.


Closing Gazebo creates Segmentation Faults and Sometimes Server does not die

Environment

OS Version: Ubuntu 20.04
Source built

Description
Closing Gazebo from
Steps to reproduce

Closing Gazebo with the close button.

Output
Stack trace (most recent call last):
#31   Object "ign gazebo gui", at 0x55d69875817e, in
#30   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132de245d, in ruby_run_node
#29   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132ddd5f0, in
#28   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f4ccf1, in rb_vm_exec
#27   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f465e0, in
#26   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f35805, in
#25   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f4f2da, in
#24   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f424b4, in
#23   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132ea03be, in
#22   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132de0742, in rb_protect
#21   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f59f80, in rb_yield
#20   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f4ccf1, in rb_vm_exec
#19   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f465e0, in
#18   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f35805, in
#17   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f4f2da, in
#16   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f424b4, in
#15   Object "/usr/lib/x86_64-linux-gnu/ruby/2.7.0/fiddle.so", at 0x7ff12eb86714, in
#14   Object "/lib/x86_64-linux-gnu/libruby-2.7.so.2.7", at 0x7ff132f13929, in rb_nogvl
#13   Object "/usr/lib/x86_64-linux-gnu/ruby/2.7.0/fiddle.so", at 0x7ff12eb868fb, in
#12   Object "/lib/x86_64-linux-gnu/libffi.so.7", at 0x7ff12eb7b409, in
#11   Object "/lib/x86_64-linux-gnu/libffi.so.7", at 0x7ff12eb7bff4, in
#10   Object "/home/otore19/workspace_luca/install/lib/libignition-gazebo7-gz.so.7.0.0~pre1", at 0x7ff12e0b1110, in runGui
#9    Object "/home/otore19/workspace_luca/install/lib/libignition-gazebo7-gui.so.7", at 0x7ff12dec404e, in gz::sim::v7::gui::runGui(int&, char**, char const*, char const*)
#8    Object "/home/otore19/workspace_luca/install/lib/libignition-gui7.so.7", at 0x7ff12c93675c, in gz::gui::Application::~Application()
#7    Object "/home/otore19/workspace_luca/install/lib/libignition-gui7.so.7", at 0x7ff12c9364b6, in gz::gui::Application::~Application()
#6    Object "/lib/x86_64-linux-gnu/libQt5Widgets.so.5", at 0x7ff12c3ca49d, in QApplication::~QApplication()
#5    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7ff12cc3897d, in QCoreApplication::~QCoreApplication()
#4    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7ff12cc6a4be, in QObject::~QObject()
#3    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7ff12cc5feed, in QObjectPrivate::deleteChildren()
#2    Object "/home/otore19/workspace_luca/install/lib/libignition-gazebo7-gui.so.7", at 0x7ff12ded13bc, in gz::sim::v7::GuiRunner::~GuiRunner()
#1    Object "/home/otore19/workspace_luca/install/lib/libignition-gazebo7-gui.so.7", at 0x7ff12ded13a1, in gz::sim::v7::GuiRunner::~GuiRunner()
#0    Object "/home/otore19/workspace_luca/install/lib/libignition-gazebo7-gui.so.7", at 0x7ff12df25b1b, in void gz::utils::detail::DefaultDelete<gz::sim::v7::GuiRunner::Implementation>(gz::sim::v7::GuiRunner::Implementation*)
Segmentation fault (Address not mapped to object [0x7ff0f8de4ef8])

I was wondering whether anyone encounter similar issue or not. Wondering whether this is something related to my setup or a general.


[SMYS 1.7.1] Game boots, but Mojang loading screen never fades out.

Show Me Your Skin: 1.7.1
Minecraft: 1.20.4
Fabric Loader: 0.15.6
Issue:
Minecraft will successful load in, but the Mojang loading screen will stay stuck on screen and not fade away. The game is not frozen, background music will play and you can hear options being selected when you click on the screen. It seems to be a conflict with Wildfire's Female Gender mod, since booting the game without it loads fine, and booting the game with WFG mod but without SMYS loads fine.
Cause:
Conflict with Wildfire's Female Gender Mod (1.20.2-3.2.1)
Mod List:
- appleskin 2.5.1+mc1.20.3
- capes 1.5.3+1.20.2
- continuity 3.0.0-beta.4+1.20.2
- fabric-api 0.91.3+1.20.4
- fabric-language-kotlin 1.10.17+kotlin.1.9.22
- fabricloader 0.15.6
- ferritecore 6.0.3
- immediatelyfast 1.2.8+1.20.4
- iris 1.6.14
- litematica 0.17.0
- lithium 0.12.1
- malilib 0.18.0
- midnightcontrols 1.9.2+1.20.4
- midnightlib 1.5.3
- modmenu 9.0.0
- notenoughanimations 1.7.0
- raised 3.1.1
- reeses-sodium-options 1.7.0+mc1.20.2-build.97
- showmeyourskin 1.7.1+1.20.4
- shulkerboxtooltip 4.0.8+1.20.4
- sodium 0.5.5
- sodium-extra 0.5.3+mc1.20.2-build.114
- wildfire_gender 1.20.2-3.2.1
- xaerominimap 23.9.7
- xaeroworldmap 1.37.7

This is a known issue, see #63.


Raise issues on repositories where the default branch is called 'master'

Lower priority than #394, but we should start addressing the repositories where master is the default branch. The organisation seems to have converged on 'main' as the name.

Intro: https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/
Github API for organisations will return the repos and it will state what the name of the default branch is called: https://docs.github.com/en/rest/reference/repos#list-organization-repositories
or
https://docs.github.com/en/rest/reference/repos#get-a-repository
Info about changing repo name: https://docs.github.com/en/rest/reference/repos#update-a-repository

See repo: https://github.com/ministryofjustice/github-repository-standards/tree/main
The GH Action will run the script in the bin folder that will run the ruby code in these two files:
http_client.rb and issue_creator.rb to create issues against repo's where the default branch is not set to main


Clipboard question

I’m seeing a weird behavior when trying to copy paste from xrdp session to windows machine.
If I copy some text in pycharm, then try to paste it into Skype for Business, I get an error like its invalid.  I think same thing with paste into outlook.  I can paste into Notepad just fine though.
I’m wondering if anyone has an idea what is happening here.  I know there are multiple clipboards but it’s not clear to me how to debug.
Maybe there’s an issue with RichText or something?

Update:
Paste into outlook works just fine.   Also, it doesn't seem to be just stuff out of pycharm. If I copy from Chrome within xrdp session and try to paste into Skype for Business that fails to.
So it definitely seems like an issue with Skype, just not sure what it could be.   If someone with experience with the clipboard could give me some pointers (how do I inspect the clipboards' contents?), I would appreciate it.

Clipboard is handled by xrdp-chansrv. You can see xrdp-chansrv log dumped to stdout.  You need to run xrdp-sesman in foreground to see xrdp-chansrv stdout. You might be required to increase log level and rebuild to see detailed log. To see clipboard contents of server to client copy & paste, maybe you can add printfs in clipboard_event_selection_notify() function.

This exact problem still occurs with  xrdp 1:0.9.11-5.el7 on Centos 7.6.1810

Which data do you need to analyse this ticket?


Log and error handling for compliance collection

@miq-bot add_label providers/containers, enhancement, smart_state
fyi @enoodle about https://github.com/moolitayer/image-inspector-client/pull/6/files
@jrafanie could you take a look please? thanks

@simon3z please review

Thanks @chessbyte


Locations endpoint is timing out

Example from your docs:
http://www.patentsview.org/api/locations/query?q={"inventor_last_name":["Yamazaki","Weder","Edison"]}&f=["assignee_lastknown_city","assignee_lastknown_state","assignee_lastknown_country"]

Now working