Updating docs for BaseGame camera to clarify how it works

Relates to https://github.com/flame-engine/flame/issues/151

Make your PR point to develop branch please.

@erickzanardo Gotcha, I think I fixed it. I made a new branch of develop, rebased the feature branch on it, the pushed it to this PR's branch.

Thanks for the quick responses


Failed to find autodoc.config.json file. (first time running doc index)

running doc index for the first time gave:
Failed to find autodoc.config.json file. Are you in the right directory?
[Error: ENOENT: no such file or directory, open './autodoc.config.json'] {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: './autodoc.config.json'
}

Hey sorry this project wasn't totally supposed to get launched yet! You can fix your issue by running running doc init before doc index. I'm about to push a change to do this automatically :)


first try at getting .dll files published on the web

Here's an example published artifact:
https://ci.appveyor.com/api/projects/tvatter/vinecopulib/artifacts/vinecopulib-fdb56f4c295f27f1329f83518e341ede7d4139ad-Win32-.zip?job

Very nice! The link does not work for me, but this one does.


field_chunksize='auto' fails when netcdf chunking is entire lat and lon dimensions

Dear Erik, Phillipe and others --
I have found a bug, I think, in the chunking code when using "field_chunksize='auto'" in FieldSet.from_nemo() for netCDF files with certain chunking patterns already defined. I have been looking at oceanparcels version 2.1.4.
I am reading Mercator 1/12 degree global model run. The netCDF files have been chunked with chunksize=(1, 3059, 4320). The last two dimensions are the same size as the grid; this was done to optimize reading them into tracMass.   When I try to load this data with FieldSet with "field_chunksize='auto'" (or with nothing, since this is the default) the code dies in the chunk_data() method of Field. But I think I have traced the problem down to the chunking code that is part of the data_access() method of NetcdfFileBuffer().
In the data_access() method, there is this code
                if self.field_chunksize == 'auto' and data.shape[-2:] == data.chunksize[-2:] and not self.chunking_finalized:                     self.chunking_finalized = True
My runs take this code path, since the last two dimensions of the chunking match the dimensions of the data... But the first dimension does not match the chunk size for the first dimension. If I explicitly specify a field_chunksize (to that of the netcdf file or any other value), it does not take this code path and particles are successfully tracked.
I have not made a pull requests, because my attempts to fix this have broken other things... and there is an easy work around of specifying a chunksize manually. (field_chunksize=False also works but is sub-optimal for all the reasons you explain in the release notes :-).
My apologies for not putting in a pull request, but I find the logic of the chunking code somewhat opaque after a days inspection.  I hope finding this bug was useful.
If you download the files and the code in https://unh.box.com/s/1ohb10r3b2ejzbv11fb2k1mg4ep2fvpv it will recreate the error, and if you uncomment the FieldSet.from_nemo() with the explicit chunksize, it should work.
Jamie

I'll check that soon

Thank you -- needless to say, there is no rush since the work-around (manually setting the chunksize) is so straightforward. Jamie

Hi @JamiePringle ,
We did some considerable work for parcels 2.1.5 (which is the current head and also available via conda-forge) on the chunking. Thus, my first advice for you is to pull the new version and re-run your experiments with that (please).
A distinct look on your specific example tells me you wanna load the data into this other package, TRACMASS. Now, if you do all data and memory tracking there, you can set field_chunksize=False - then, it will load the whole 3D field in one go, no chunking being done there. On the other hand, what you wanna try is just accessing each individual 2D layer (with the depth chunksize being '1'). In that case, there will also be no chunking, because chunking/defer loading only applies to read field data with more than 2 dimensions (hence: either a depth dimension larger than 1, or using the temporal dimension in parcels).
Your specific setup was until now not considered. A work-around is to address this as a 4D field, hence defining time, depth, lat and lon in your field dimensions, and then set field_chunksize-(1,1,3059, 4320).
It would be good to try out those configurations with the new version parcels=2.1.5. Please get back to us with your new feedback then.
Cheers,
Christian

Dear Christian --
We have been using the work around you mentioned since we reported the bug -- explicitly setting the chunk size worked well.

Unfortunately, it will take me a little while to test the new build. Because of Coronavirus, I dispersed my lab computers to my graduate students, and so the computer with the model data is sheltering in place with my graduate student who is doing the particle tracking for his thesis (for now in Tracmass, the FORTRAN version). In a week or so, I should be able to walk a hard drive over to his place and get the data, and then I will test.

Thank you! for your efforts.
Jamie

Dear @JamiePringle ,
Have you had by now the chance to fetch the harddrive and test the new version ? Otherwise we would close the issue for now and wait for your reports later again. Just be aware to use the new versions (2.1.5 or later) when re-running your local simulations again.
Cheers,
Christian

Dear Christian -- this had slipped my mind. I will re-test this afternoon
or tomorrow.
Jamie
On Mon, May 11, 2020 at 9:28 AM Christian Kehl<EMAIL_ADDRESS>wrote:

Caution - External Email
Dear @JamiePringle
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJamiePringle&data=02|01|James.Pringle%40unh.edu|753dc8f41e3143d136e608d7f5af3be7|d6241893512d46dc8d2bbe47e25f5666|0|0|637248005287812419&sdata=Kezayml5RSAZaeaFgQgQu9cvPMFvOFZMuuj5ElwAb4Q%3D&reserved=0
,
Have you had by now the chance to fetch the harddrive and test the new
version ? Otherwise we would close the issue for now and wait for your
reports later again. Just be aware to use the new versions (2.1.5 or later)
when re-running your local simulations again.
Cheers,
Christian
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOceanParcels%2Fparcels%2Fissues%2F761%23issuecomment-626701851&data=02|01|James.Pringle%40unh.edu|753dc8f41e3143d136e608d7f5af3be7|d6241893512d46dc8d2bbe47e25f5666|0|0|637248005287812419&sdata=MXAfUMRfjYMsniq7PIDctYsbtZWvLrNOOayJgizg4%2BA%3D&reserved=0,
or unsubscribe
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADBZR26L6E7IHMRHKSXUGTLRQ74Q5ANCNFSM4K3WV3BA&data=02|01|James.Pringle%40unh.edu|753dc8f41e3143d136e608d7f5af3be7|d6241893512d46dc8d2bbe47e25f5666|0|0|637248005287822414&sdata=npB38DoVLSuIYkCf0t6ZByh%2FxZ50TBoxflLqJMqfj0A%3D&reserved=0
.

I checked this in 2.2.0 and the issue is no longer present. Thanks!

Closed and thank you!
On Mon, May 11, 2020 at 9:28 AM Christian Kehl<EMAIL_ADDRESS>wrote:

Caution - External Email
Dear @JamiePringle
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJamiePringle&data=02|01|James.Pringle%40unh.edu|753dc8f41e3143d136e608d7f5af3be7|d6241893512d46dc8d2bbe47e25f5666|0|0|637248005287812419&sdata=Kezayml5RSAZaeaFgQgQu9cvPMFvOFZMuuj5ElwAb4Q%3D&reserved=0
,
Have you had by now the chance to fetch the harddrive and test the new
version ? Otherwise we would close the issue for now and wait for your
reports later again. Just be aware to use the new versions (2.1.5 or later)
when re-running your local simulations again.
Cheers,
Christian
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOceanParcels%2Fparcels%2Fissues%2F761%23issuecomment-626701851&data=02|01|James.Pringle%40unh.edu|753dc8f41e3143d136e608d7f5af3be7|d6241893512d46dc8d2bbe47e25f5666|0|0|637248005287812419&sdata=MXAfUMRfjYMsniq7PIDctYsbtZWvLrNOOayJgizg4%2BA%3D&reserved=0,
or unsubscribe
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADBZR26L6E7IHMRHKSXUGTLRQ74Q5ANCNFSM4K3WV3BA&data=02|01|James.Pringle%40unh.edu|753dc8f41e3143d136e608d7f5af3be7|d6241893512d46dc8d2bbe47e25f5666|0|0|637248005287822414&sdata=npB38DoVLSuIYkCf0t6ZByh%2FxZ50TBoxflLqJMqfj0A%3D&reserved=0
.


More test content in parser test

Added some test content for the old parser tests.

We should merge this, right?

We should/could. We were thinking about waiting for type::Value to stabilize (@mbutrovich) because of the strings that the parser spits out, but everything else is fine / it is a small change we can make at a future date.
Per yesterday's discussion, type::Value will be immutable so we don't need to do the delete in tests any more @DarkForte.


New App: Chi-L-Tracker, Chicago CTA L Arrival Board

Description
Chicago CTA L Tracker - Station arrival board
An arrival board for your favorite 'L' station.
Features

Two "slots" (top/bottom) on your Tidbyt's screen

Each slot can show one L route's arrivals at a specific station
Slots can be configured to be different stations
Each slot is color coded with your line color and train's direction name (or rather acronym)

Shows multiple upcoming arrivals

First upcoming arrival is in larger, orange font
Subsequent arrivals are in small font
Trains that are marked as delayed are shown in red
On some lines, you might see a suffix after each arrival that denotes an alternate destination

e.g. Blue line trains to UIC/Halstead will have "U" after the number

A "!" suffix means the train is showing a non-standard destination (e.g. during construction)

Option to filter out "scheduled" trains

CTA's train schedule is notoriously inaccurate, so by default only live-tracked trains are shown. This may however not work too well near train terminus as trains aren't live tracked until they leave the first station.
For this case, it might be good to turn on "show scheduled trains" option.
Scheduled trains are shown in a grey font

Animated train separating the slots

This can be turned off in app configuration

Copilot

🤖 Generated by Copilot at f1fe510
Summary
🚇📝🚀

Add a new app for the Tidbyt device called Chi L Track, which shows arrival times for Chicago's CTA L trains. The pull request includes a manifest.yaml file and a README.md file for the app.

Chi L Track app
Manifest and README files
Autumn leaves on rails

Walkthrough

Create a new app for displaying CTA L train arrival times on Tidbyt (link, link)
Add a manifest.yaml file to specify the app's metadata and package name (link)
Add a README.md file to introduce the app, its features, and a GIF image (link)

I have read the CLA Document and I hereby sign the CLA


crash when failing to discover language by extension

Currently glslls just crashes if it can't discover the extension, which can create a lot of core dumps over time. Might be nice to just send an error back to the client.

@nolanderc wanna take a stab at this?

I have been running into this myself after I added support for #include: I have split some common functionality into separate files, but seeing as they can be used in both compute, vertex and fragment shaders, I decided to give them the extension .glsl. However, as this is not a recognized extension, the language server crashes. As I see it, we have two options:

Provide an error message, as suggested by @chergert, to stop the server from crashing (might be nice to have in some other situations as well).
Assume any unrecognized extension is a generic GLSL file, and fall back to some default behaviour. This could allow the server to provide some basic support such as code completion, but may reduce the accuracy of diagnostics.

Unfortunately, it does not seem as if glslang provides an enum variant for such a "generic" shader language. Maybe we could just assume a compute shader, or similar, as they should be closest to a superset of all others?

How about a warning + sane default as you suggested?

I'm also interested in this. Recently I started going over some playlists at https://www.youtube.com/@TheCherno. He has stuff on OpenGL, Game Engines, C++ in general etc.
I think it was in one of his videos from the OpenGL playlist (possibly this one: https://youtu.be/2pv0Fbo-7ms but I'm not sure) where he explains that one of the systems he wants to build is to have one file for multiple shader types. We can probably take a look at how they handle code recognition in that project through some file splitting method. I assume something like this can be done for an LSP as well, but I'm not even an amateur with LSPs so I can't say more.

If there is interest in automatically handling concatenated files, that would certainly be nice. GTK does this, which is what I would want to use this for when working on GTK's GL renderer.
$ cat blend.glsl
// VERTEX_SHADER:
// blend.glsl
...
// FRAGMENT_SHADER:
// blend.glsl
...


SvgXml doesn't render

Copy pasting an example directly from the docs using SvgXml. It simply doesn't render and errors.
Same thing happens in my local project.
Am I missing something obvious?
Expo Snack: https://snack.expo.dev/@paulwongx/react-native-svg_svgxml_doesnt_render
// Taken directly from the docs - still doesn't render
// https://github.com/react-native-svg/react-native-svg#use-with-xml-strings

import * as React from 'react';
import { SvgXml } from 'react-native-svg';

const xml = `
  <svg width="32" height="32" viewBox="0 0 32 32">
    <path
      fill-rule="evenodd"
      clip-rule="evenodd"
      fill="url(#gradient)"
      d="M4 0C1.79086 0 0 1.79086 0 4V28C0 30.2091 1.79086 32 4 32H28C30.2091 32 32 30.2091 32 28V4C32 1.79086 30.2091 0 28 0H4ZM17 6C17 5.44772 17.4477 5 18 5H20C20.5523 5 21 5.44772 21 6V25C21 25.5523 20.5523 26 20 26H18C17.4477 26 17 25.5523 17 25V6ZM12 11C11.4477 11 11 11.4477 11 12V25C11 25.5523 11.4477 26 12 26H14C14.5523 26 15 25.5523 15 25V12C15 11.4477 14.5523 11 14 11H12ZM6 18C5.44772 18 5 18.4477 5 19V25C5 25.5523 5.44772 26 6 26H8C8.55228 26 9 25.5523 9 25V19C9 18.4477 8.55228 18 8 18H6ZM24 14C23.4477 14 23 14.4477 23 15V25C23 25.5523 23.4477 26 24 26H26C26.5523 26 27 25.5523 27 25V15C27 14.4477 26.5523 14 26 14H24Z"
    />
    <defs>
      <linearGradient
        id="gradient"
        x1="0"
        y1="0"
        x2="8.46631"
        y2="37.3364"
        gradient-units="userSpaceOnUse">
        <stop offset="0" stop-color="#FEA267" />
        <stop offset="1" stop-color="#E75A4C" />
      </linearGradient>
    </defs>
  </svg>
`;

export default () => <SvgXml xml={xml} width="100%" height="100%" />;

I'm having problems with this tag too.
I'm not the developer of this project but I think it would be better for everyone if you showed the log with the errors. :)

Same issue,i can't render my image

only works with version 12 doesnot render anything in version 13

It works for me on the current main so it was probably resolved in one of the former commits. I will close this issue then. Feel free to comment here if something is wrong and we can always reopen it then.


Find instructors by country + other improvements

The Find Instructors page had a facelifting.
This fixes #394.
All changes are listed in the commit messages, the important and visible ones:

No more "wanted" field; instead pagination with sorting by distance is in place.
Filter instructors by their country.

After clicking "More... Find Instructors", the page shows all instructors (because there's no filtering in place).  This isn't the behavior I expect - it should initially be blank.
There are some layout problems: the search boxes on the left underlie the display of instructors.

Hi Greg,
On Thu, Jul 9, 2015 at 7:18 PM, Greg Wilson<EMAIL_ADDRESS>wrote:

After clicking "More... Find Instructors", the page shows all
instructors (because there's no filtering in place). This isn't the
behavior I expect - it should initially be blank.

Maybe you expect this behavior because it's what you're used to?
I will argue for the new behavior:

it's consistent with other pages with filters
it drops one barrier for admins (specifying number of wanted instructors)

There are some layout problems: the search boxes on the left
underlie the display of instructors.

Confirmed (it appears on the lower resolution displays), and I have a fix
for that ready.

[image: screen shot 2015-07-09 at 1 08 23 pm]
https://cloud.githubusercontent.com/assets/911566/8601872/ff8da902-263c-11e5-9e32-bbabb3f792db.png
—
Reply to this email directly or view it on GitHub
https://github.com/swcarpentry/amy/pull/420#issuecomment-120076192.

On 2015-07-09 1:33 PM, Piotr Banaszkiewicz wrote:

After clicking "More... Find Instructors", the page shows all
instructors (because there's no filtering in place). This isn't the
behavior I expect - it should initially be blank.

Maybe you expect this behavior because it's what you're used to?

Yes, probably.

I will argue for the new behavior:

it's consistent with other pages with filters
it drops one barrier for admins (specifying number of wanted
instructors)

I'm not arguing about the paginated display - I like that.  I'm arguing
that being shown all instructors, in alphabetical order, is...
overwhelming...  @amyrbrown ?

On Thu, Jul 9, 2015 at 7:38 PM, Greg Wilson<EMAIL_ADDRESS>wrote:

On 2015-07-09 1:33 PM, Piotr Banaszkiewicz wrote:

After clicking "More... Find Instructors", the page shows all
instructors (because there's no filtering in place). This isn't the
behavior I expect - it should initially be blank.

Maybe you expect this behavior because it's what you're used to?

Yes, probably.

I will argue for the new behavior:

it's consistent with other pages with filters
it drops one barrier for admins (specifying number of wanted
instructors)

I'm not arguing about the paginated display - I like that. I'm arguing
that being shown all instructors, in alphabetical order, is...
overwhelming... @amyrbrown ?

So when you go to Ebay, you expect to see no items for sale unless you add
some filtering? :-)

—
Reply to this email directly or view it on GitHub
https://github.com/swcarpentry/amy/pull/420#issuecomment-120082558.

Good point.

Belatedly, I agree that all instructors should be listed until there is a filter is specified. An alphabetized list of all instructors is not very useful, but it's (a) logical, and (b) no less useful than a blank page.

Make it so.

Okay, so it's all resolved now. Merging.


Auto refresh and health check not working  with springboot 2.0.0.M7 and spring-cloud-consul-config 2.0.0.M4

Bug report
spring-cloud-consul:2.0.0M4 does not work properly after changes in springboot-actuator: 2.0.0M7
In order to verify that issue is not with my app I generated 2 projects in http://start.spring.io with dependencies: Consul configuration, Consul Discovery, Web
https://github.com/olehlesiuk/demo-spring-boot-1.5.9
@EnableDiscoveryClient
added to generated configuration:

@EnableDiscoveryClient
config file bootstrap.properties with
spring.application.name=s1pconsuldemo

health check and auto refresh of configuration is woking properly:
2018-01-05 10:45:27.150  INFO 77968 --- [pool-1-thread-1] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@5ca93be9: startup date [Fri Jan 05 10:45:27 CET 2018]; parent: org.springframework.context.annotation.AnnotationConfigApplicationContext@6ffa1428
2018-01-05 10:45:27.151  INFO 77968 --- [pool-1-thread-1] s.c.a.AnnotationConfigApplicationContext : Closing org.springframework.context.annotation.AnnotationConfigApplicationContext@6ffa1428: startup date [Fri Jan 05 10:45:26 CET 2018]; root of context hierarchy
2018-01-05 10:45:27.829  INFO 77968 --- [pool-1-thread-1] o.s.c.e.event.RefreshEventListener       : Refresh keys changed: [foo]
https://github.com/olehlesiuk/demo-springboot-2.0.0.M7
added to generated configuration:

@EnableDiscoveryClient
config file bootstrap.properties with
spring.application.name=s1pconsuldemo
management.endpoints.web.expose=*

health check and auto refresh is not working properly. I noticed that in springboot-actuator 2.0.0M7 endpoint was changed to /actuator/health and /actuator/refresh. spring-cloud-consul still has /health
2018-01-05 10:46:47.787  INFO 78073 --- [           main] o.s.c.c.s.ConsulServiceRegistry          : Registering service with consul: NewService{id='s1pconsuldemo', name='s1pconsuldemo', tags=[], address='<IP_ADDRESS>', port=8080, enableTagOverride=null, check=Check{script='null', interval='10s', ttl='null', http='http://<IP_ADDRESS>:8080/health', tcp='null', timeout='null', deregisterCriticalServiceAfter='null', tlsSkipVerify=null, status='null'}, checks=null}

Duplicates #345, fixed by 5d7331a648e81ef10e22639ab0099589c4fff893
Trying snapshots should fix the problem.

snapshots has problem.
Caused by: java.lang.NoSuchMethodError: org.springframework.cloud.client.serviceregistry.AbstractAutoServiceRegistration.<init>(Lorg/springframework/cloud/client/serviceregistry/ServiceRegistry;Lorg/springframework/cloud/client/serviceregistry/AutoServiceRegistrationProperties;)V

adding 'spring.cloud.consul.discovery.health-check-path=/actuator/health' to bootstrap resolve issue with health check, but issue with configuration auto update still exist.
Any idea why auto refresh of configuration from consul stop working in this version?

@SystemOutPrint you have mismatched versions on your classpath.
@olehlesiuk if you can provide a minimal sample that reproduces the problem, open a new issue.

@spencergibb thank you for advice. Created new issue hope description is good enough:
https://github.com/spring-cloud/spring-cloud-consul/issues/399

thx


Added Sphinx

General Checkups

[x] Have you checked that there aren't other open pull requests for the same issue/update/change?
[ ] If your code includes new features and not just bug fixes/copy editing: Did you include new tests?

Description

Related Issue

Example

@gedankenstuecke @mcescalante @madprime I have added sphinx documentation. The generated documentation can be hosted on github pages by hosting the docs/docs_html/html folder. Hosting is only possible by the project owners. The hound issues are in the autogenerated html files. CodeClimate issues are in the javascript files which are linked to the autogenerated files. Please review. Thanks!

Hi @mcescalante, I have updated the dev-requirements, removed the html files, and also added a section for setting up documentation locally in the README files. Please review. Thanks! :)

Hi @gedankenstuecke , @mcescalante, I have removed sphinx warnings. The warning due to _static was due to untracked empty folder which I fixed. Other indentation error have also been fixed. On my end, the documentation is getting build without any warnings/errors. Please review. Thanks :)

Awesome, we should now set up the readthedocs integration.


move utp code out into its own repo

The utp code (which isnt currently used by default in ipfs) should live in its own repo so it can be independantly tested and maintained.

This was resolved by creating and using https://github.com/libp2p/go-utp-transport/


Server: handle peerinfo

Currently we don't do anything with the peerinfo sent from the client. The client may send IV_PROTO with bit 2 set which means the server MAY send a push reply. In practice it seems our client and the OpenVPN™ client sets IV_PROTO bit 2 and then never sends PUSH REQUEST. This results in the connection timing out because neither parties send any more packets.
(this analysis may not be right, but we should implement handling peerinfo in the server in any case)

done in #229 :)


__typename field in _type query resolves to null

Hi again @devsergiy,
I am trying out the v1 federation example and getting some unexpected behaviour around the __type query when returned with __typename field. I use this for schema and type introspection.

When I run a query without __typename, it returns as expected like this:

query type{
  __type(name: "User") {
    name
    fields{
      name
    }
  }
}

{
  "data": {
    "__type": {
      "name": "User",
      "fields": [
        {
          "name": "id"
        },
        {
          "name": "username"
        },
        {
          "name": "reviews"
        }
      ]
    }
  }
}

As soon as I return __typename, the object is resolved unexpectedly as null:

query type{
  __type(name: "User") {
    name
    __typename
    fields{
      name
    }
  }
}

{
  "data": {
    "__type": null
  }
}

Similarly, if I add __typename to just the fieldsobject, that object unexpectedly becomes null instead:

query type{
  __type(name: "User") {
    name
    fields{
      name
      __typename
    }
  }
}

{
  "data": {
    "__type": {
      "name": "User",
      "fields": null
    }
  }
}

If I was to add __typename to the me query, it works fine as expected:

query me{
	me{
    id
    reviews{
      body
      __typename
    }
    __typename
  }
}

{
  "data": {
    "me": {
      "id": "1234",
      "reviews": [
        {
          "body": "A highly effective form of birth control.",
          "__typename": "Review"
        },
        {
          "body": "Fedoras are one of the most fashionable hats around and can look great with a variety of outfits.",
          "__typename": "Review"
        }
      ],
      "__typename": "User"
    }
  }
}

Your advice would be appreciated on how I can continue to use __typename in the _type query. It is used by our Apollo Client for caching purposes. Is this intended behaviour?
Thanks,
Ben

Another issue I just discovered with the Federation example __type query, is that the description subfield/s are resolved as "" rather than null when compared with __type query called directly in the subgraph.
i.e.
Federation Gateway:
query type{
  __type(name: "User") {
    name
    description
    fields{
      name
      description
    }
  }
}

{
  "data": {
    "__type": {
      "name": "User",
      "description": "",
      "fields": [
        {
          "name": "id",
          "description": ""
        },
        {
          "name": "username",
          "description": ""
        },
        {
          "name": "reviews",
          "description": ""
        }
      ]
    }
  }
}

Compared to subgraph:
query type{
  __type(name: "User") {
    name
    description
    fields{
      name
      description
    }
  }
}

{
  "data": {
    "__type": {
      "name": "User",
      "description": null,
      "fields": [
        {
          "name": "id",
          "description": null
        },
        {
          "name": "username",
          "description": null
        }
      ]
    }
  }
}

Thanks for replying @Aenimus , do you have rough dates/timeline for when v2 will be ready?

@BenjaminYong V2 is already ready. However, if your question is regarding the porting of examples, there is no current time frame.


Malformation of quaternon in quadrupedal formulation

This error appears only for Debug mode, since the quaternion malformation actives a Pinocchio assert (in pinocchio::diff).
It solves the issue #693.

@nim65s @wxmerkt
The CI is broken, this is the message:
The following packages have unmet dependencies:

 robotpkg-py27-example-robot-data : Depends: robotpkg-py27-eigenpy (= 1.6.12) but 2.0.2 is to be installed

                                    Depends: robotpkg-hpp-fcl (= 1.2.1) or

                                             robotpkg-hpp-fcl+doc (= 1.2.1) but it is not going to be installed or

                                             robotpkg-hpp-fcl (= 1.2.2) or

                                             robotpkg-hpp-fcl+doc (= 1.2.2) but it is not going to be installed

 robotpkg-py27-pinocchio : Depends: robotpkg-py27-hpp-fcl (= 1.2.1) or

                                    robotpkg-py27-hpp-fcl (= 1.2.0) or

                                    robotpkg-py27-hpp-fcl (= 1.2.2) or

                                    robotpkg-py27-hpp-fcl+doc (= 1.2.0) but it is not going to be installed

                           Depends: robotpkg-py27-eigenpy (= 1.6.12) but 2.0.2 is to be installed

                           Depends: robotpkg-hpp-fcl (= 1.2.1) or

                                    robotpkg-hpp-fcl+doc (= 1.2.1) but it is not going to be installed or

                                    robotpkg-hpp-fcl (= 1.2.2) or

                                    robotpkg-hpp-fcl+doc (= 1.2.2) but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

The command "/bin/bash .travis/install-prerequisites.sh" failed and exited with 100 during .

do you know the reason?

An upgrade of hpp-fcl & eigenpy is currently running on robotpkg buildfarm.
ref:
https://git.openrobots.org/issues/214
https://github.com/stack-of-tasks/pinocchio/issues/884

An upgrade of hpp-fcl & eigenpy is currently running on robotpkg buildfarm.
ref:
https://git.openrobots.org/issues/214
stack-of-tasks/pinocchio#884
Please just wait a bit for http://robotpkg.openrobots.org/rbulk/rbulk-dispatchd.html to complete and start again :)

Thanks for the info :)

Is there an ETA of when robotpkg will enable staging? This happens pretty frequently for us these days :-(. Otherwise happy to move to ROS Industrial CI for build + unit tests

There is no ETA that I know of.
This is way too far in robotpkg's internals for me, and the main developer did not answer on the issue yet.

Actually, rather than a band-aid added to the problem formulation for the quadruped, shouldn't this be fixed inside the state.diff? Or in other places in Crocoddyl as well?

Actually, rather than a band-aid added to the problem formulation for the quadruped, shouldn't this be fixed inside the state.diff? Or in other places in Crocoddyl as well?

It is not a bug in the diff function (or pinocchio::difference). If the user passes an unsymmetric rotation matrix to a hypothetical function then he/she is making a wrong mistake. This is exactly what it was happening but with a quaternion.
A common software engineering solution is to include an assert to your code, and we follow this approach.
A proper way to handle this issue will be to devise an API that cannot allow users to construct such kind of problem. However, this is not trivial as we might have system without floating base, or states that can be anything else. Additionally it could unnecessary work since asserts are there, and human resources are very limited.

@nim65s thanks for the support. I understand the limitations that we have with robotpkg.
However, we could create a team policy to mitigate this inconvenient as suggested in riot.
I am at your disposal for any further discussion in the riot channel.

Is there an ETA of when robotpkg will enable staging? This happens pretty frequently for us these days :-(. Otherwise happy to move to ROS Industrial CI for build + unit tests

Could we support both?

I wasn't suggesting it's a bug but in the input arguments - and sadly easy enough to make and miss when Pinocchio is in release mode (or from binaries).
Perhaps adding a check and exception (only to check if the multibody-state has a free-flyer, and to check if it has a normalised quaternion) is a workable solution? We should try to protect users from these errors when experimenting and formulating problems (with Pinocchio in release mode they'd be almost impossible to debug "why the DDP doesn't converge/exhibits failure mode XYZ").
We could support both CI. I won't have time for that before IROS though.
Sorry I may miss the point here. What team policy could mitigate an issue that is outwith our control as Guilhem mentioned as it is fully upstream with robotpkg?

@wxmerkt : my CI system on gepgitlab is based on regularly building docker images with everything already automatically installed. This mean that at runtime, we don't have to waste time installing anything, which implies not having errors in the CI in case of network issues or this kind of unfinished job in the robotpkg's buildfarm.
This system will be automatically enabled on this repo in the week.
Now, if you want to build a fully independent CI system on Travis, I think your suggestion to use builds from the ROS buildfarm should do the trick. But please note that I have no bandwidth to support the 2 systems.

This system will be automatically enabled on this repo in the week.

That's great! Can you please add some detail in an issue? I was not aware of this development

And - I think this CI should be additional and not replace the Travis (which should stay required for a PR to be merged) as it's testing one of the userflows that is recommended in the README

It will be additional, don't worry :)
About the details, it will be available in another repo, as the rest of my CI system works with all our packages at once, and there is nothing particular for crocoddyl.

I wasn't suggesting it's a bug but in the input arguments - and sadly easy enough to make and miss when Pinocchio is in release mode (or from binaries).

I agree with you. My concerns are always about the balance between user-friendly vs high-performance software. I am happy to adapt any solution that does not affect the later. Give some time for thinking about it :)


How to make a Connection between EF6 and asp.net core 3

Goal:
Use EF 6 inside of ASP.net core 3 by using a project named ef.
Project EF is the main connection to the database sql server.
Problem:
I get an error saying
Error = Unable to evaluate the expression. Operation not supported. Unknown error: 0x80070057.
What part am I missing from the code in order retrieve the data in asp.net core 3.
Info:
*Uploaded the project at github (https://github.com/candyboyyy/WebApplication1_asp.netcore3)
*Using VS 2019, EF 6, asp.net core 3

``
CREATE TABLE [dbo].[Blogs]
(
[BlogId] [INT] IDENTITY(1,1) NOT NULL,
[Name] NVARCHAR NULL,
[Url] NVARCHAR NULL,
CONSTRAINT [PK_dbo.Blogs]
    PRIMARY KEY CLUSTERED ([BlogId] ASC)
                WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF,
                      IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON,
                      ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]

) ON [PRIMARY]
GO
``

Hello! Thanks for contacting us. This sounds like a general question about using ASP.NET Core and EF6. While we try to look at and respond to all issues, for questions like this we recommend posting to a community support group like Stack Overflow with the asp.net-core tag.


Update throws error messages

Thanks a lot for your update and the implementation of the facebook-events...
But unfortunately after updating I got error messages in both possibilities:
{{ facebook_posts() }} gives this error:
"0 - An exception has been thrown during the rendering of a template ("krsort() expects parameter 1 to be array, null given") in "modular/news.html.twig" at line 10."
{{ facebook_events() }} gives this error:
"0 - An exception has been thrown during the rendering of a template ("Undefined property: stdClass::$end_time") in "modular/news.html.twig" at line 10."
For the moment I disabled the plugin...
But if you want access to my site or more details about it just tell me...
Hope we'll find a quick solution...
Thanks for all your help

The 1.2.0 update was unfortunately such that after it is installed, all the configuration must be reset. Did you do that ? I will try to reproduce the errors you have mentioned.
I think I know the error in facebook_events() but at the moment I am not sure what causes the first error.
Details and/or access to your site could help alot.

I have created release 1.2.2. Please tell me if that fixes the errors above.

It's working perfectly now !!! I don't know you personally, but right now I would say "YOU ARE GREAT" :)
Thanks so much...

For your information, yes, I did change the configuration after the first update. (The new Update doesn't need a re-configuration - great!)

Do you think there is a way to also implement the "Event picture" and a link to the event

This is a very powerful plugin for facebook implementation into grav, would you mind if I continue thinking about how to improve it in the future ?

If so maybe better to not communicate only here in the issue-folder of github... I could send you messages to your email<EMAIL_ADDRESS>or any other if you prefer. Mine is<EMAIL_ADDRESS>

For your information the website I work on right now and where your plugin is used is "test5.prinla.com"... I could send you access if needed by private mail.

Another big thank you for your great cooperation

Glad that problems are gone for you :) I will close this issue and we can continue communicating through emails.


update lua package set + several small fixes

Description of changes

bumped luarocks-nix that now uses nurl to generate nicer fetchers
first stopped adding lua to propagatedinputs because of an issue I had when creating lua environements, but had to bring it back for the setupHook / envHook else lua programs were not getting wrapped. The utils.sh will be useful anyway post-release to record the relative paths in LUA_PATH
BREAKING CHANGE in the format of the csv file. Replaced src column with rockspec - the URL to the actual rockspec - to simplify implementation and remove ambiguity. Before that, luarocks nix was downloading the repo and looking for rockspec files with a certain pattern. I suppose nixpkgs and one of my script is the the only consumer. It was not easy to use the lua updater out of tree before this release.

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

the full nixpkgs review was too much so I've limited my testing to:

built neovim and knot-resolver
run lua-tests
nixpkgs-review on vimPlugins and luaPackages
build my config with it

Bottom line is the resty packages are broken (because they need the submodules I think) but:

some of them are already broken
they have no maintainer
I am not sure yet how to decide how to tell luarocks-nix to generate the src with the submodules (short term a whitelist probably, later a smart mode for submodule autodetection in nurl ?).

The latter issues can be solved easily during ZHF. I would like to get this into staging-next first because it will unblock some fixes for neovim plugin dependencies, which I would like to have in the 24.05 release.

I would like to get this in fast in staging-next to be able to fix a neovim issue with transitive dependencies and have a few days to see if breaks user configs before release.
I've spent quite a bit of time testing this so I will self merge.

luaPackages.toml doesn't look good:
https://hydra.nixos.org/build/258829548/nixlog/2/tail

It escaped me. I dont think it matters that much ? it's a leaf package. I wanted to get the deep changes into staging first.
Then I can fix openresty and this one on master directly.

Yes, it's probably worse that merging master into staging-next now gives a conflict in pkgs/development/lua-modules/generated-packages.nix, and I couldn't immediately see how to resolve it.

(the conflict's been resolved somehow)


Add graphing for numeric values (speed, steering angle, etc.)

Definitely always interested in graphs. Now that we are trapping the data in a semi efficient manner we can probably begin plotting some of it.
I need to map out all the fields and their types so that we can efficiently handle the data so it doesn’t get sluggish.
On Nov 4, 2018, 11:06 PM -0500, Gernby<EMAIL_ADDRESS>wrote:

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


The todos page in the starting template does not work with the static adapter and Caddy

Describe the bug
I have created a new sveltekit app using:
npm init svelte my-app

I have used the following Caddy config to serve the generated files:
http://:9000 {
    handle_path /api/* {
        reverse_proxy <IP_ADDRESS>:7260
    }

    handle {
        root * {env.HOME}/.../my-app/build

        try_files {path} {path}.html / # redirecting nonexistent routes to /index.html
        file_server browse
    }
}

I use npm run build to build the project.
When I click on the todos page, I'll get:

Directly navigating to http://localhost:9000/todos just shows the homepage.
Using npm run preview works fine, but I have no idea what kind of a server it is running under the hood. The todos page is very sluggish with npm run preview though. Everything happens after seconds of delay.
Reproduction
.
Logs
No response
System Info
System:
    OS: macOS 12.2.1
    CPU: (4) x64 Intel(R) Core(TM) i5-6267U CPU @ 2.90GHz
    Memory: 117.42 MB / 8.00 GB
    Shell: Unknown - /bin/dash
  Binaries:
    Node: 18.2.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.9.0 - /usr/local/bin/npm
    Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
  Browsers:
    Chrome: 102.0.5005.61
    Firefox: 92.0
    Safari: 15.3
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.50
    @sveltejs/adapter-static: ^1.0.0-next.34 => 1.0.0-next.34
    @sveltejs/kit: next => 1.0.0-next.350
    svelte: ^3.46.0 => 3.48.0

Severity
blocking all usage of SvelteKit
Additional Information
No response

The todos page requires server-side work to handle the saving of todo items. It's not going to work with a static site.
The preview command runs an un-adapted version of the built site, so what you get there is unrelated to what adapter you have selected.
During static site generation, to crawl pages with dynamic parameters that aren't linked to from other pages, you need to use the entries config. https://kit.svelte.dev/docs/configuration#prerender


🐛 BUG: Getting 1000 Auth error

Which Cloudflare product(s) does this pertain to?
Wrangler
What version of Wrangler are you using?
3.2.0
What operating system are you using?
Mac 13.4.1 (22F82)
Describe the Bug
uname -a
Darwin CQGWXK77CN 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000 arm64

Hi,
Wrangler gives the following error when I try to push code to my account.
Additionally, wrangler whoami does not list my account. I have used wrangler whoami for two Super Admin emails, and neither of them show my account.
I also tried setting CLOUDFLARE_ACCOUNT_ID, there is no change in wrangler whoami / wrangler deploy.
% wrangler deploy index.mjs
 ⛅ wrangler 3.2.0
------------------
✘ [ERROR] ParseError: A request to the Cloudflare API (/accounts/5b3d23f7aa124b3b0701c521a5ca9dc0/workers/services/turnstile-demo-workers) failed.

      at throwFetchError (/opt/homebrew/lib/node_modules/wrangler/wrangler-dist/cli.js:121134:17)
      at fetchResult (/opt/homebrew/lib/node_modules/wrangler/wrangler-dist/cli.js:121087:5)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async deploy (/opt/homebrew/lib/node_modules/wrangler/wrangler-dist/cli.js:147370:31)
      at async Object.deployHandler [as handler]
  (/opt/homebrew/lib/node_modules/wrangler/wrangler-dist/cli.js:137935:3) {
    text: 'A request to the Cloudflare API
  (/accounts/5b3d23f7aa124b3b0701c521a5ca9dc0/workers/services/turnstile-demo-workers) failed.',
    notes: [ { text: 'Authentication error [code: 10000]' } ],
    location: undefined,
    kind: 'error',
    code: 10000
  }

Total Upload: 6.49 KiB / gzip: 1.95 KiB

✘ [ERROR] A request to the Cloudflare API (/accounts/5b3d23f7aa124b3b0701c521a5ca9dc0/workers/scripts/turnstile-demo-workers) failed.

  Authentication error [code: 10000]

  If you think this is a bug, please open an issue at:
  https://github.com/cloudflare/workers-sdk/issues/new/choose

The issue was that API Access was disabled globally for all members in the account.
https://developers.cloudflare.com/fundamentals/api/how-to/control-api-access/#:~:text= Account-level access,and then update the setting.


Extensions

Update extensions for Nanobind
Clean up doc a bit

This is good to go. I tested it locally, works well.

Closes #954


If the directory is too long, it will be truncated automatically and cannot be displayed completely.

Hi, thank you for your hexo theme first, I found a problem in the process of using solar, which is that if there are too many directories in the body, the list of directories in the sidebar will be truncated and only part of it will be displayed, as shown below.

I was wondering if I could make the directory section in the sidebar scrollable so that the directory will be displayed completely.
Hope the author can solve this problem.

I think this could be solved if we update solar-theme to the latest version of cactus ( except the solar part ), but it's hard work...


Use ETS heat pump COP from GMT sys-params

Any background context you want to provide?
We were unintentionally not allowing users to change ETS heat-pump COP values. That is now available
What does this PR accomplish?

Read cop_c and cop_h values from a sys-param file

Enabled possibility of reading any ETS data from sys-param file in the future

Change 2 buildings' ETS COP values in the 13-building upstream sys-param file for demonstration/validation purposes
Fix a few typos
Update all sys-param files to have fifth-gen ETSs attached to the buildings. This was a copy/paste mistake originally

How should this be manually tested?

Run a network test on the command line to create a baseline
Within the relevant sys-param file, change the value of buildings[*][fifth_gen_ets_parameters][cop_heat_pump_heating/cooling] to a test value
Run the test again, calling that sys-param file
Confirm that the test value is output in the terminal under the debug logging for final ets_data

What are the relevant tickets?

Screenshots (if appropriate)

Looks good, but it would be good to add a test here. I merged in multi-ghe locally and ran tests, and they all passed. I think once we have a test for the changes in this branch, I'm good.

Ahh, right. I have the json file to show the changes, but I never actually made an assertion for it. I'll make that happen. Thanks Matt!


SQL quering with parameter returned by elasticseach

I need pass a parameter to SQL on JDBC_RIVER and this parameter must be returned by some search done on elasticsearch . For example:
 "sql" : [   {   "statement" : "select * from \"some_table\" where id > ?"
                "parameter" : [ "max_value(id) from some_table"  ] <-- Return from some_table at elasticsearch
            }    ],

I guess you need to write a nested SQL sentence to perform this, as far as I know river plugin only accepts one SQL statement, and it doesn't seem to hard to do this:
SELECT * FROM some_table WHERE id > (
    SELECT MAX(id) FROM other_table)
)

Ivanlw, thanks your answer, but, I dont can execute this on datase origin. It's something like this:
I have a table in Oracle that we need do input at elasticsearch the incremental records, but, I can't use the $last.sql.end parameter from RIVER to do this cause my table on oracle don't have a time_stamp column.
I need get the last ID record transported to elasticsearch and run the query at oracle with it.
I tried find something on web, but I did not find anything.

I can see your situation now. I have no idea to pick out latest id either.
If I were you, I would import the previous data from Oracle to ES for once, then add a time stamp column for future new added records, then you can import incremental records by comparing to $last.sql.end.

Thank you. I'll try find another way. I can't alter production table.


Revert "Revert "added new tests with recordings""

Reverts Azure/azure-sdk-for-go#23607

Reverting the previous change.


Reconsider block production when system under heavy load

The first thing that happens in block production is a check to see if perhaps we already received a block for the very same slot from another node; this can happen (theoretically speaking) if there are multiple slot leaders and the other node manages to produce their block and have it sent to and adopted by us before we manage to produce our own block.
So we check the current chain, and look at the block at the tip of the chain. If that block has the same slot number as the slot we're trying to produce a block for, we go back one block, basically rolling back one.
If however the block at the tip of the chain has a slot number larger than the current slot number, it means the system must have been under such heavy load that one or more slots passed in between the start of the leadership check and the call to the chain DB. When this happens, we currently just give up and don't produce a block.
We may wish to reconsider this, though we should be a bit careful. See detailed comments in prevPointAndBlockNo in forkBlockProduction.

Could this be potentially related to the reduced leadership check frequency observed in https://input-output.atlassian.net/wiki/spaces/BM/pages/1663827969/GH-1769+BUG+-+chain+stopped+for+more+than+4+minutes+on+producer+relays ?  We have 100% CPU utilisation there.


Live typing

replacing https://github.com/clp-research/slurk/pull/102 and https://github.com/clp-research/slurk/pull/103
unclear whether this should be merged, cf. https://github.com/clp-research/slurk/pull/103#issuecomment-709945435

Triage: This pull request has conflicting files.


Win10, pip install retrogrades Jango to 1.11.29, then when creating myproject, ModuleNotFoundError: No module named 'django.utils.importlib'

Installing collected packages: django
  Attempting uninstall: django
    Found existing installation: Django 3.2.4
    Uninstalling Django-3.2.4:
      Successfully uninstalled Django-3.2.4
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
wagtail 2.13.2 requires Django<3.3,>=2.2, but you have django 1.11.29 which is incompatible.
nemo 3.11.0 requires Django==2.2.24, but you have django 1.11.29 which is incompatible.
djangorestframework 3.12.4 requires django>=2.2, but you have django 1.11.29 which is incompatible.
django-treebeard 4.5.1 requires Django>=2.2, but you have django 1.11.29 which is incompatible.
django-sekizai 2.0.0 requires django>=2.2, but you have django 1.11.29 which is incompatible.
django-formtools 2.3 requires Django>=2.2, but you have django 1.11.29 which is incompatible.
django-filter 2.4.0 requires Django>=2.2, but you have django 1.11.29 which is incompatible.
django-cms 3.8.0 requires Django>=2.2, but you have django 1.11.29 which is incompatible.
django-classy-tags 2.0.0 requires django>=2.2, but you have django 1.11.29 which is incompatible.
Successfully installed django-1.11.29

Traceback (most recent call last):
  File "c:\users\USERNAME\appdata\local\programs\python\python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "c:\users\USERNAME\appdata\local\programs\python\python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\USERNAME\AppData\Local\Programs\Python\Python39\Scripts\mezzanine-project.exe\__main__.py", line 4, in <module>
  File "c:\users\USERNAME\appdata\local\programs\python\python39\lib\site-packages\mezzanine\bin\mezzanine_project.py", line 11, in <module>
    from mezzanine.utils.importing import path_for_import
  File "c:\users\USERNAME\appdata\local\programs\python\python39\lib\site-packages\mezzanine\utils\importing.py", line 5, in <module>
    from django.utils.importlib import import_module
 ModuleNotFoundError: No module named 'django.utils.importlib'`

Are you installing Mezzanine from master or from pip? Compatibility with Django 2+ requires installing from master at the moment


chore: adjust android integration

The type of this PR is: chore
Description
Adds android specific setup for Adjust. Follows docs here: https://segment.com/docs/connections/destinations/catalog/adjust/#android
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Adjust integration - brian, jon

Dev changes

whoops wrong branch 😅


Add fuzzer harnesses

This pull request adds harness programs for use with the AFL fuzzer in order to detect crashes. At first, tests for geoToH3, h3ToGeo, h3ToGeoBoundary, and kRing are added.

Coverage remained the same at 99.315% when pulling e9cf21b755db2bd839511aed91f8a5e4882b1a54 on isaacbrodsky:afl into 3b5641f6665499c68f4f15f3df2f93289695fc16 on uber:master.


Fixed #9 Deployed to heroku

What is the change?
Added Procfile and updated the app.js and deployed to heroku --> BlogSite
Related issue?
issue: #9
Files edited?

ProcFile
app.js

Screenshots or Video:
not required

Fixes #9

Fixes #9

@all-contributors please add @Subhra264 for code

@all-contributors please add @Subhra264 for code


Issue with legend

we are using Chartjs for some graphs and having an issue with clickable legend boxes, as they are being displayed in some cases and not displayed in other cases as in the below snapshots :
without : https://ibb.co/cDgHaF
with : https://ibb.co/mkCjNv
The case that we have observed for displaying these boxes is when the page auto refreshes while it is minimized.
here is the Canvas HTML:
<canvas width="1200" height="600" id="canvas_F2" class="justshowme" ></canvas>
here is the chart option:
			var lineGraph = new Chart($("#canvas_F2"), {
				type: 'line',
				data: chartdata2,
				});

and here is the refresh meta tag:
<meta http-equiv="refresh" content="300">
Can anyone please let us know what is wrong here?
Thanks a lot in advance

This is hard to debug without a fiddle that reproduces the issue. It's likely related to how we detect resizes of the canvas container. Likely fixed in #4596


Caret is mis-located when multibyte characters entered in text box input fields

Describe the bug
In multi-byte environment such as Japanese, when using IME input to insert non-alphabetic (MBSC) characters with text boxes, the actual caret position is located at a different place.
This issue is found in both MacOS and Windows. Tested in Sonoma 14 and Windows 11. This not only occurs in dialogue event text boxes, but also when typing into math equations.

To Reproduce

Create a new scene and set it to show up a message dialogue.
Type in Japanese characters (longer the better). If using a non-multibyte character supported environment, just copy & paste a dummy text such as "あいうえおかきくけこさしすせそ".
Observe the unwanted blank spacings between the end of string and the current caret position.
Now, try to locate and set the caret to somewhere in the middle of the string, such as between "き" and "く".
Type in a character or letter (i.e. "a")
Observe the entered letter inserted at a different position. In this case, the typed in character "a" will be inserted at a different position where the caret is not located.

Expected behavior
The letter should be inserted at the specified position where the caret is currently located.
Platform (please complete the following information):

OS: Windows 11, MacOS 13, 14
App version: 4.0 (Seen in 3.x as well)

Additional context
This issue may be coming from Electron it self.

Hi @tomo666 that's odd I can't seem to replicate this issue at my end following the steps you listed (I'm running macOS 13.5.1)
https://github.com/chrismaltby/gb-studio/assets/16776042/ee339192-3a3d-4094-82c7-ef4328873798
am I missing something in this video?
I can completely understand how this is COULD happen though, both this input and the math equation input are built on top of React Mentions which handles the autocomplete/text code menus as well as highlighting tokens such as variables. And the way that component works is it has a hidden text area that is where you're actually typing (and that handles the caret position / text selection), and a layer of HTML displayed over the top that shows identical content (but with syntax highlighting), the textarea and HTML are supposed to have the EXACT same position of every character and if they were out of sync somehow then what you're seeing would happen. I could imagine that the HTML layer is showing the multibyte characters, but maybe the textarea is editing them as individual bytes causing the text selection width to be wider than the display width, that's just a guess though.
Could you maybe attach a zip of an affected project? Maybe even though I can't reproduce the error I will see it if I open an affected project file.
Thanks

Hi @chrismaltby, thanks for looking into this issue and for your insights.
Please find the test project here:
Caret_Test.zip
It's just a plain new project with scene added with a message dialogue event attached.
Before I've reported this issue, I did some surveys in a Japanese discord thread and asked around few Japanese GBS users and they all seem to have the same issue. Not only Windows but on a Mac too.
Note that some user reported that this issue was not present until version 3.x and was working well in 2.x. I thought it might be something to do with the Electron version as I saw few issues searching around related to multi-lang support with this tool, but since I don't know much around the Electron/NodeJS stuff I'm a bit out of expert here.
If you need anything else, please let me know 🙂

Thanks for this @tomo666 unfortunately your project works fine for me too, I've tried setting my macOS to use Japanese input hoping that might help but no difference. I've also tried on Windows 10 and it was working fine there too :-(
To help understand what's going on I've made a debug build that makes it so the Textarea and HTML are both visible and displayed simultaneously one above the other. See in this screenshot the white form input at the bottom is where you're actually typing and the dark text at the top is the HTML which is normally the only visible part.

In my testing the characters are always aligned perfectly horizontally so when overlaid on top of each other, each character would appear in the same location.
You can get the debug build here: https://github.com/chrismaltby/gb-studio/actions/runs/9697921855
My theory is that for you one of those will look different to the other in some way that will help us identify the cause of the problem. If you could try testing that build and attach some screenshots that would be really useful. Thanks

Thanks @tomo666 that is strange, the font is definitely different in textareas in yours, odd that Latin characters are appearing thinner and Japanese ones are wider too.
Looking into it I noticed the HTML preview had some CSS font-variant-east-asian: normal; that the textarea didn't include, not sure if that's it but worth trying. I've tried explicitly setting all the font CSS fields to be identical, hoping that might improve things.
If you want to try this version instead you can download at
https://github.com/chrismaltby/gb-studio/actions/runs/9763711155
I've also enabled the developer tools so you can play around with the HTML too

Hi @tomo666 I've managed to get a machine configured to use Japanese in a way that reproduces the text issues you were seeing and believe I have a fix in place for this now.
This is included in the latest dev build available at:
https://github.com/chrismaltby/gb-studio/actions/runs/9775487285
and will be part of the next release.
I'll close this issue for now but if this version isn't working for you feel free to reopen it.
Thanks again for all the information you've provided to help locate the cause of this problem.

Thanks @chrismaltby !!
I've confirmed fixed on both Mac & Windows (Intel ver for now) on my side.
This fix was actually a big improvement for us Japanese users as it was long waited for an update (and for someone to report the issue too 😂). So many thanks to you for putting the effort into setting up an environment to reproduce & fix this issue.


Detox doesn't wait for button animation

Description
Hi, I'm new to Detox and not a very experienced developer so apologies if the answer to this is very obvious, I haven't found any other bugs about this problem. In the Detox documentation I read the following in the "Endless looping animations" section:
By default, Detox will wait until animations complete.
But it doesn't do that for me, below is a screen recording of when the test taps a button prematurely, along with the code that's being run.
https://user-images.githubusercontent.com/7572926/108333565-61eda580-71d1-11eb-8b47-26e09629b12b.mov

I also ran the test with the debug-synchronization 500 argument, see log below, I've highlighted where the test taps the button too early.

[x] I have tested this issue on the latest Detox release and it still reproduces

Reproduction
This has been the most puzzling thing about this issue, I've tried different solutions that by all indications seem to be working - for example I added the waitFor + toBeVisible before tapping the button as in the first screen shot above - but when I get back the next morning I see the problem again.
Step by step

Start test
Watch the test tap button too early

Expected behavior
Test should wait for button to animate before tapping it
Environment (please complete the following information):

Detox: 18.2.2
React Native: 0.63.4
Node: 15.7.0
Device: iPhone 11 simulator
Xcode: 12.4
iOS: 14.4
macOS: 10.15.7

Logs
If you are experiencing a timeout in your test

[x] I have followed the instructions under Identifying which synchronization mechanism causes us to wait too much, I have read synchronization debug documentation and am providing the relevant synchronization debug output below: see screen shot of log above

If you are seeing a Detox build problem (e.g. during npm install, not detox build)
I'm not

[ ] I am providing the npm install log below:

Device and verbose Detox logs

[x] I have run my tests using the --loglevel trace argument and am providing the verbose log below:

trace.txt
Thanks for your time

@onnerfors do you by any chance have a timer suspending the button's fade-in animation start, that's longer than 1.5 seconds?

@alon-ha could you check and see which assertion the waitFor(...).toBeVisible() translates to? Namely, whether on top of not being blocked by other view in the hierarchy -- that it takes the alpha into account...

@d4vidi that's an idea I've had, tried reading the code but haven't figured it out so far, and my developer colleague has been sick the past few days so haven't been able to check with him, but will. So it could be that Detox is tapping the button before the animation starts?

Might be. Technically, if the view is set visible (though has alpha set to 0), and a timer suspends the animation's start by more than 1.5s, Detox would consider the app idle and move forward with tapping on the button.

That screen has other animations going on before it gets to the button I want the test to tap, so that means Detox should wait I suppose. Could it have anything to do with specific animation tools? We're using Lottie. I know it's hacky but is there a way to pause the Detox process somehow? As the withTimeout() + toBeVisible() combination of methods only waits until the button is visible to Detox as I understand it, which it is before being animated, I don't see how I can get past this issue temporarily until I've found the root cause

@onnerfors yes, it's probably a good idea to delay the process, and figure out if the animation is the root cause.
await new Promise(resolve => setTimeout(resolve, 5000));

Thank you very much! Now I at least have a workaround, will continue talking to my devs about it, sounded on them like it's possible to turn off animations all together for Detox builds. Let me know if you want more info from me, and close the bug if you want

You might want to give waitFor() + withTimeout() a try, but all in all, Detox should be able to take all running animations into account - so best if you avoid that.
In Detox 18 we've changed the synchronization mechanism. If it doesn't bother you much, could you try the same scenario with the latest Detox 17 and report back?

Seems like an animation we are not tracking. I will check it.
@onnerfors it will be great if you can provide an example project with kind of a similar screen/animation

Hello, sorry for the delay, @d4vidi I tried the same thing with version 17.14.9 and the issue reproduced 19 times out of the 20 I tried, it's the following code that fails:
it('Should tap "Continue" in onboarding', async () => {
    await waitFor(element(by.id('onboardingContinueButton')))
      .toBeVisible()
      .withTimeout(5000);

    await element(by.id('onboardingContinueButton')).tap();  <<< this happens before the button is animated, like in the video attached to the bug description

@alon-ha I wish I could set up something similar to have you guys try it yourselves, but I don't have the RN skills for that yet

@onnerfors Hey, Sorry for the delay. We have a new mechanism in detox 18 to track when the application is idle.
Since you are using Lottie, maybe we don't track the animation at all.. I can set up a basic project myself, but I need at least the json for the button so I can test it.. Otherwise there is no way that I will guess what's the problem is:/
Let us know if you can provide the json for the button / part of the initial code for the button.. Anything that can help before I'm starting to debug it. Thanks

Hi @alon-ha, sure, I've attached the .tsx of the button as well as the Animated.View from the screen it's a part of. Let me know if there's anything else you need.
OnboardingContinueButton.tsx
import React, { useEffect, useRef } from 'react';
import { Animated, StyleSheet } from 'react-native';
import { t } from 'i18n-js';
import Button from '@components/Button';
import OnboardingScreen from './OnboardingScreen';

const styles = StyleSheet.create({
  button: {
    marginVertical: 0,
  },
});

const DEFAULT_DURATION = 420;

type Props = {
  visible: boolean;
  nextScreen: string;
  onPress: () => void;
  animationDuration?: number;
  label?: string;
};

const OnboardingContinueButton = ({
  visible,
  onPress,
  animationDuration = DEFAULT_DURATION,
  nextScreen,
  label,
}: Props): JSX.Element => {
  const opacity = useRef(new Animated.Value(0)).current;

  useEffect(() => {
    Animated.timing(opacity, {
      toValue: visible ? 1 : 0,
      duration: animationDuration,
      useNativeDriver: false,
    }).start();
  }, [animationDuration, opacity, visible]);

  return (
    <Animated.View style={{ opacity }}>
      <Button
        buttonStyle={styles.button}
        title={label || t('onboarding.continueButtonLabel')}
        onPress={onPress}
        isDisabled={!visible}
        testID={`onboardingContinueButton${nextScreen}`}
      />
    </Animated.View>
  );
};

export default OnboardingContinueButton;

Animated.View from OnboardingScreen.tsx
<Animated.View
          style={[
            styles.continueButtonContainer,
            {
              opacity: animatedValue.current.interpolate({
                inputRange: [0, 1],
                outputRange: [1, 0],
              }),
            },
          ]}
        >
          <OnboardingContinueButton
            onPress={onPressContinue}
            label={continueButtonLabel}
            visible={continueButtonVisible}
            animationDuration={continueButtonAnimationDuration}
          />
        </Animated.View>

@onnerfors, may I kindly ask you to check the issue with the latest Detox version?
The thing is, @alon-ha recently fixed something very curious in React Native queue status interrogation mechanism, and I just wonder if that has changed anything about your particular issue.

Good point @noomorph, in fact I thought I was running the latest version, that npm updated the package automagically on npm install. The issue persists with 18.11.1 though.

@onnerfors thanks for the clarification!! 👍

@onnerfors Thanks for all the info, and for bearing with us.
Since this case is a bit unusual (odd set of events + fails even with Detox17), would you mind setting up a very simple, light demo app containing the lottie animation and button in question (or equivalents), where this is reproduced? That would provide a serious boost in our so-far-futile attempts to solve this.

@d4vidi no worries and I have a workaround for now so it's all good, I have some spare time at work now actually, so I will look into setting up an example with a Lottie animation so you guys can debug it. Will get back to you

@onnerfors great, keep us posted!

@onnerfors Pretty please? 😄

Sorry @d4vidi was thrown into a project at work, will try to find some time for it soon

Hi @alon-ha, sure, I've attached the .tsx of the button as well as the Animated.View from the screen it's a part of. Let me know if there's anything else you need.

Hi, Unfortunately the snippet alone wasn't enough to reproduce. Will be great if you post an example project with Lottie animation which cause it.

Hi guys, it's not likely that I'll find time for this anytime soon unfortunately. Maybe the lack of '+1' comments on this thread means that this problem isn't too common. I might take it up after summer as the project I'm using Detox for might resume then

@onnerfors no problem. Hopefully by then we will have a skeletal project you could use (#2746)

@onnerfors with #2746 all done and well, we now have DetoxTemplate ready for easy reproductions. Perhaps you could work out a reproduction based on it? You can easily fork it and have a project up and running in a breeze.

Hello, it seems MotiView animations are not tracked either as I just ran into the same problem with Detox's latest version.

Hello, it seems MotiView animations are not tracked either as I just ran into the same problem with Detox's latest version.

Hey @adrienharnay  could you elaborate on that? Does this happen on Android/iOS/both?


Not a valid resource record name

PHP Fatal error:  Uncaught Badcow\DNS\DNSException: "google._domainkey" is not a valid resource record name. in /Users/necrogami/code/dt/vendor/badcow/dns/lib/ResourceRecord.php:96
Stack trace:
#0 /Users/necrogami/code/dt/vendor/badcow/dns/lib/ResourceRecord.php(59): Badcow\DNS\ResourceRecord->setName('google._domaink...')
#1 /Users/necrogami/code/dt/random.php(88): Badcow\DNS\ResourceRecord->__construct('google._domaink...')
#2 {main}
thrown in /Users/necrogami/code/dt/vendor/badcow/dns/lib/ResourceRecord.php on line 96
Code Snippet
$txt3 = new ResourceRecord('google._domainkey');
$txt3->setRdata(Factory::txt('v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDazaxHRVRVE1vnA3j02HvwgWcIhs2RWZ4U0aXknRapSSeTolKvFgnS+EYRRs8THeUdUDSiGYl5avuru10oIxNbcActybF+YIPClGdGGaGXVFboAs/EZFdUfHrCop/9DzxqS1jYHp33d+P9xoVi8ouQFs1AzoyyBVR0gwbIq8EIHQIDAQAB'));
$zone->addResourceRecord($txt3);

It doesn't seem to like the underscore which is common in srv and txt records

Agreed, this should be changed. Strictly speaking, a non-alphanumeric character at the start of the string is not a valid resource name, that is why it fails. I'm starting to lean to the idea of getting rid of the validation on the resource records altogether and putting the onus on the developers to validate the resource names in their applications. Thoughts?

Yeah, i'm more of the mindset a tool like this should push the validation to higher up the chain. This is more about generating the zone file vs validating a zone file that should be done for a parser or the upstream libraries.

Validation has been removed from the ResourceRecord object. Note that the validator will still validate some Rdata types (e.g. A and MX). This should resolve @necrogami issue.


AddHostedService overload with factory

Summary of the changes (Less than 80 chars)

Added overload to AddHostedService extension method to allow construction via factory method

 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.:x: BEagle1984 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

The build pipeline is failing some checks but it doesn't look like they are related to my commit. Please let me know if otherwise.

Thanks

I was about to submit an issue asking for this. This is going to make things easier to use the generic host. Thank you!


Remove orphaned translation ContentItem

This migration deletes a ContentItem, and all the supporting stuff, that is a translation of a Whitehall DetailedGuide. Whitehall has no knowledge of this translation and the URL currently 404s.
This is probably being caused by a known issue in Whitehall where deleted translations are not currently unpublished from Publishing API. There is a Trello card for fixing this with #core-formats

Looks good 👍

I think we need to include the deletion of links that point to these content_items in the DeleteContentItem helper.
publishing_api_development=# select * from links where target_content_id = '5f5890da-7631-11e4-a3cb-005056011aef';
   id   | link_set_id |          target_content_id           |   link_type    |         created_at         |         updated_at         | passthrough_hash
--------+-------------+--------------------------------------+----------------+----------------------------+----------------------------+------------------
 362499 |       15222 | 5f5890da-7631-11e4-a3cb-005056011aef | documents      | 2016-04-29 10:14:56.503608 | 2016-04-29 10:14:56.503608 |
 433887 |      204637 | 5f5890da-7631-11e4-a3cb-005056011aef | related_guides | 2016-05-13 12:53:11.894725 | 2016-05-13 12:53:11.894725 |
(2 rows)

Good point, even the example in the readme won't catch items where that link to the item. Do you want to put together a quick method?


fix RBAC resource names for ClusterServiceBroker

The ServiceBroker -> ClusterServiceBroker rename went in without the accompanying RBAC name changes.
I've tested this against the walkthrough manually and confirmed this worked. RBAC enforcement will be coming to Jenkins shortly to automatically enforce this.

Thanks for doing this!!


refactor: follow-up to leaf updater uses binary search

The following pr contains all the follow-ups to #529.
One specific thing I would like to ask is an opinion to the introduction of LeafNode::extract_key. It is a small abstraction that still requires some conceptual thoughts. The point is: the layout of the leaf node is mostly encapsulated within its module, and inside keep_up_to, I was extracting the key from the cell_pointers. However, I thought that a modification in the layout of the leaf node could silently break the leaf updater. That's why I added this helper function. In case a layout change happens, the entire leaf/node.rs code would be updated, including the way a key is extracted from the cell pointer.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#565  👈 (View in Graphite)
#564
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

One specific thing I would like to ask is an opinion to the introduction of LeafNode::extract_key. It is a small abstraction that still requires some conceptual thoughts.

This seems reasonable. We should avoid silent breakage (and ideally have a test which prevents those kinds of regressions). Helper functions are usually good, just not worth hiding the format of the leaf from the updater. as we will eventually have greater optimizations by making use of it.


Extra load for component is lauched

I'm trying to migrate RTC project stream with multiple components with history starting not from beginning. After accepting first commit, I'm getting several messages about directory checked out from different place and then exception with generic message "load ... before migrate-to-git".
The problem is that for each component accepting its first commit launches 'load' delegate for that component that fails because the component is already loaded. This only works if each component in the  "target" workspace has "initial baseline" and thus empty content.
As a workaround, "update" option can be specified.

Now I see why load delegate is launched. This is required for e.g. component which migration is started with initial baseline. After loading such component accepting changes doesn't modify local sandbox (which looks to me as very strange scm behaviour). The solution is to fetch components that are loaded into the sandbox before migration and do loading only for newly added components.


Can't add a new cognito custom attribute through auth override

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
10.0
What operating system are you using?
Ubuntu on WSL
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No
Amplify Categories
auth
Amplify Commands
override
Describe the bug
I added an auth override which missed the carrying over existing attributes from resources.userPool.schema. I am trying to add them back later but it is giving me the following issue
🛑 The following resources failed to deploy:
Resource Name: UserPool (AWS::Cognito::UserPool)
Event Type: update
Reason: Invalid AttributeDataType input, consider using the provided AttributeDataType enum. (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException; Request ID: 3aa23190-c93f-4dcc-8c01-e40661b1190c; Proxy: null)
Expected behavior
Auth should be updated with the existing attributes
Reproduction steps

Use old version of amplify auth v1
Add a custom attribute tenantid through cloudformation template
Upgrade the auth to v2
Use amplify auth override and add the following code

import { AmplifyAuthCognitoStackTemplate } from '@aws-amplify/cli-extensibility-helper'

export function override(resources: AmplifyAuthCognitoStackTemplate) {
  const customAttribute = {
    attributeDataType: 'String',
    developerOnlyAttribute: false,
    mutable: true,
    name: 'tenantid',
    required: false,
  }
// Mising the ...(resources.userPool.schema as any[]) part
  resources.userPool.schema = [
    customAttribute,
  ]
}

Amplify push
Update the override to include  ...(resources.userPool.schema as any[])
Code

import { AmplifyAuthCognitoStackTemplate } from '@aws-amplify/cli-extensibility-helper'

export function override(resources: AmplifyAuthCognitoStackTemplate) {
  const customAttribute = {
    attributeDataType: 'String',
    developerOnlyAttribute: false,
    mutable: true,
    name: 'tenantid',
    required: false,
  }
  resources.userPool.schema = [
    ...(resources.userPool.schema as any[]), // Carry over existing attributes (example: email)
    customAttribute,
  ]
}

amplify push

You should see the error now
GraphQL schema(s)
No response
Project Identifier
No response
Log output

# Put your logs below this line

Additional information
No response

hey @devChedar, Thank you for reaching out. I was able to replicate the error from the steps provided. Could you let us know if the Cognito login experience without the carryover attributes works as expected?

I can login but the tenantid that I added through override doesn't have the read or write property.

hey @devChedar, Thank you for the information. Newly added custom attributes are not set as readable or writable attributes by default on the App Clients. We can set the App client attributes by using the following in the override.
import { AmplifyAuthCognitoStackTemplate } from "@aws-amplify/cli-extensibility-helper";

export function override(resources: AmplifyAuthCognitoStackTemplate) {
  const customAttribute = {
    attributeDataType: "String",
    developerOnlyAttribute: false,
    mutable: true,
    name: "tenantid",
    required: false,
  };

  resources.userPool.schema = [
    ...(resources.userPool.schema as any[]),
    customAttribute,
  ];

   resources.userPoolClient.readAttributes = [ //set readable attributes
      "email",
      "custom:tenantid",
    ];
}

output:
before override on readable attributes

after override:

furthermore, I was able to get some additional information on the error Invalid AttributeDataType input, consider using the provided AttributeDataType enum., when we add ...(resources.userPool.schema as any[]), to carry over the attributes cloudformation detects these changes as schema change with adding a new attribute email(example) resulting in the error.
we will be reporting this to the cloudformation team and investigating this. Thank you for reporting.
as a mitigation step i would suggest not removing and readding the carry over. removing the carryover will not remove the required attribute(in this example email) in the console.

Hey @devChedar, following up on this issues. We have updated the Cognito override documentation to align with observed behaviour. Thank you for reporting. Please feel free in reaching out to us again.


Question: manually adding some structions on single player => they were not found.

Hello,
since generation of seed on latest paper version for End dimension is not working.
( End city and end Gateway structions are not found )
I decided to create new single player world and manually find structions on paper and copy them to my single player game.
at the begining it sounded like a good idea but when i have copied succesfully pillars and pillar seed was generated just fine i have found out that SeedCracker is not able to locate my Own created Ender City not even EndGateWay, i tried to search in your code but i didn't found nothing suspicious.
Could you please advise if what i tried to do is even possible or is there any crosscheck against different biom layers so you would be able to recognize manually added structions.
Thank you in advance for your response.
Have a nice day
Best regards
Memory

You need to find intact structures.


[QUESTION] How can I retrieve the Production Cost from a IDEA StatiCa connection?

I'd like to retrieve the production cost as a function of different parameters for an initial optimization strategy.

Hello, this is not possible at the moment, outputs that can be read through IOM are quite limited. We are working on expanding this.


Does the code work for tabular data?

Let's say I want to test it in something like this
from sklearn.datasets import make_blobs
from sklearn.linear_model import LogisticRegression

X, y = make_blobs(n_samples=2000, centers=2, n_features=5, random_state=0)
X_ood, _ = make_blobs(n_samples=1000, centers=1, n_features=5, random_state=0)

How will the code be?

Means no?

Your information is limited, but based on your setting (without even defining a probability distribution to model the data), I don't think it will work in our framework. Our framework is not to find a model.

Does not it work with the X, and X_ood provided in the code snippet?

If you are referring to redefine the X and X_ood with make_blobs given a model pretrained with CIFAR , I am not sure if the model will be able to distinguish them. You can play around with our code and adapt to your application.


ethernet :: low-risc eth driver et al

This is a snapshot of work in progress and expected to have commented out code, hacks, etc.


Convert extract tests, fix test setup

This is my first try at converting an Aniseed test to busted + luassert.
I picked one that required a supporting test module that appears to be a one-off thing. I hope the integration of that module is OK. fennel code formatting might be a bit messed up by my Neovim set up. Advice and corrections are more than welcome.

Sorry, minor fix up to follow https://lunarmodules.github.io/busted/.

Nice! Thank you very much for this. I will probably try to recover that buffer helpers module, I think it gets used in a few places so it'll be worth converting that too.
Thank you for helping out 🎉

Oh after re-reading I realise that it was a one off and see why you
integrated it. Oh well, we have a generic test util module now for the
future if required.
On Mon, 19 Aug 2024, 10:23 Russ Tokuyama, @.***> wrote:

Sorry, minor fix up to follow https://lunarmodules.github.io/busted/.
—
Reply to this email directly, view it on GitHub
https://github.com/Olical/conjure/pull/595#issuecomment-2296090942, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACM6XIT7MQT5Y5DAQJV6JDZSG2P3AVCNFSM6AAAAABMXMHJWCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJWGA4TAOJUGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Registry url is assumed to be https vs http

Bug description
When Adding a registry host:port, portainer interprets it as https. A prefix with http is not interpreted at all. This means Portainer is expecting a secure registry.
Expected behavior
If there are insecure registries, they should be supported. User should be able to use https OR http.
Steps to reproduce the issue:
Steps to reproduce the behavior:
Create an insecure registry (out of scope) of portainer. Then create a new entry. It will be assumed to be accessed via https.
Technical details:

Portainer version: 1.19.2
Docker version (managed by Portainer): 18.06.1-ce
Platform (windows/linux): Linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): default

closing - did not read the bit about insecure settings in daemon.json


No error handling for ghost server

SAR causes the game to crash/freeze when you connect to a server that times out

Should be fixed by 6d00ba8


Update crass to 0.10.*

Failures in Node 4 are the result of cssshrink.
Failures in Node 6+ are the result of more-css.

Hmmm. How do we want to proceed with this?

I'm not really sure. I could look into a fix for more-css, but it looks unmaintained and all of the source comments are in Chinese. The problem actually doesn't stem from their codebase, though. more-css pulls in clean-css and minifies with that. I assume they do it to squeeze out every little optimization they can. The version they use is 3.2.8, which came out May of last year. The current version of clean-css is 3.4.21.
I ran this from the css-minifiers root:
rm -rf node_modules/more-css/node_modules/clean-css/
ln -s node_modules/more-css/node_modules/clean-css node_modules/clean-css

After this, all of the tests pass on Node 6+:
><EMAIL_ADDRESS>test /opt/css-minifiers
> tape test.js | tap-spec

  integration tests

    ✔ should minify css with clean-css
    ✔ should minify css with crass
    ✔ should minify css with css-condense
    ✔ should minify css with csso
    ✔ should minify css with cssshrink
    ✔ should minify css with csswring
    ✔ should minify css with more-css
    ✔ should minify css with ncss
    ✔ should minify css with sqwish
    ✔ should minify css with ycssmin
    ✔ should minify css with cssnano

  benchmark tests

    ✔ clean-css took 16 ms
    ✔ crass took 15 ms
    ✔ css-condense took 15 ms
    ✔ csso took 12 ms
    ✔ cssshrink took 12 ms
    ✔ csswring took 3.12 ms
    ✔ more-css took 2.59 ms
    ✔ ncss took 850 μs
    ✔ sqwish took 537 μs
    ✔ ycssmin took 483 μs
    ✔ cssnano took 16 ms

  metadata tests

    ✔ clean-css version 3.4.21
    ✔ clean-css should be cast to string
    ✔ crass version 0.10.1
    ✔ crass should be cast to string
    ✔ css-condense version 0.1.1
    ✔ css-condense should be cast to string
    ✔ cssnano version 3.8.2
    ✔ cssnano should be cast to string
    ✔ csso version 1.8.2
    ✔ csso should be cast to string
    ✔ cssshrink version 0.0.5
    ✔ cssshrink should be cast to string
    ✔ csswring version 4.2.3
    ✔ csswring should be cast to string
    ✔ more-css version 0.12.0
    ✔ more-css should be cast to string
    ✔ ncss version 1.1.1
    ✔ ncss should be cast to string
    ✔ sqwish version 0.2.2
    ✔ sqwish should be cast to string
    ✔ ycssmin version 1.0.1
    ✔ ycssmin should be cast to string

  total:     44
  passing:   44
  duration:  2.1s

I've filed a PR: https://github.com/army8735/more/pull/32
After I filed mine, I realized there was one filed in June for the same upgrade: https://github.com/army8735/more/pull/30
So it doesn't look likely that it'll get merged soon or at all. In that case, I guess it's up to you how to proceed. What does this mean for the ecosystem you've built on top of this module? In a matter of months Node 4 is going to leave active LTS and enter maintenance mode, leaving 6/7 the active LTS release(s) and 8+ the current releases. If the module doesn't get updated, it likely won't work in any real capacity.
Historically, more-css has done really well on benchmarks, but its correctness has been dubious. "Radical" isn't a term most folks strive for when building minifiers. If the goal of this repo is to show the full breadth of minifiers, I suppose I could write some code that patches more to use the new clean-css version. You could also point it at a fork that uses an updated version. I don't know if there's any sort of obscure package.json technical shizzle-wizzle that can be done to tell it to use a particular version of clean-css.
If the goal is to represent what the community is actually using, I think it might be best to remove it from the library. Nobody using the latest version of Node from April onwards (or potentially August of 2015; I haven't tested with Node 5) has been able to use more.

So my goal with this repo has been to provide a unified API across all minifiers so that we can compare results across engines and get an idea of how well (or not) they perform. I don't believe outside of things like css-minifier-tests that anyone would want to use this in production, so I'm not worried too much about breaking the functionality of this module.
Ideally I'd like to keep more-css in here for completeness' sake but if it doesn't work on the latest versions of Node, and it won't be updated in a reasonable time frame (this is a fair assumption to make given the open pull request) then we can drop it. But I would definitely be OK with re-adding it here should the module work again on Node 6.
I'm not so interested in making sure that more-css works myself, as you say it's not actively maintained. If anyone cares enough to maintain a fork I would also link that from here. So we can probably drop it from this pull request and test on Node 4+?

@mattbasta Thanks for your contribution, I've released 3.0.0 with this patch. 👍


Scroll container width keeps increasing on mouseout on Firefox 61 on Mac

The broken behaviour is described here:
https://github.com/grafana/grafana/issues/12726
I think we're hitting a FFMAC special case in baron, our scroll handler. It adds padding (15px) on each scroll element update:
https://github.com/Diokuz/baron/blob/master/src/core.js#L596
The update here is triggered on an animation or transition event on hover:
https://github.com/Diokuz/baron/blob/master/src/core.js#L209
To verify, you can change your user agent to not match the regexp in https://github.com/Diokuz/baron/blob/master/src/core.js#L46 and the issue disappears.
My guess is that baron no longer needs this special treatment in FF61

@davkal I wrote a patch (referenced in this PR), but want to verify it. Any idea how I can reproduce using the test page? I'm not quite familiar enough with what Grafana is doing to create a good test.
I'm looking at test/index.html and none of the test examples seem to reproduce the issue, even on master.


MSL: Use of MSLVertexAttr

The use of MSLVertexAttr has evolved over time. Currently...almost none of the information it contains is used at all within SPIRV-Cross...I assume because we rely completely on the stage_in construct (originally we supported both stage_in and indexed vertex access.
Like a good government worker...MoltenVK is currently diligently filling out the contents of this struct...even though most of it serves no purpose.
I'm wondering if we should trim this struct...either remove it entirely in favour of other API options...or at least trim (and maybe rename) it for it's current use as a re-mapper of tessellation formats and builtins.
@HansKristian-Work @cdavis5e  ?

Yup, looking at MSLVertexAttr, it does not seem to be relevant anymore. I know the format is used to do fixups, but is that all?
I'm fine changing the API in the C++ backend, but I cannot break any API in the C wrapper. We can deprecate and add a better interface though, as long as we can express the old APIs with the new. As I understand it, most of the fields in MSLVertexAttr are completely ignored anyways, so we don't have to care about those.

Understood about the C ABI...although I wonder if anyone is using the C equivalents to this...since the C++ struct was driven by MoltenVK originally. But we can just stub the references out if we change this struct I guess.
@cdavis5e Since the remaining use of MSLVertexAttr is related to tessellation changes...I'll leave it to you to comment about whether we should simply strip the unused members from the struct...or change the API in some other way (eg- move tess info to a different struct or function and get rid of the struct altogether).

@billhollings @cdavis5e Any further comments?

As I mention...I'm fine to trim it (preferred) or remove it from the C++ API and replace with something simpler. The C ABI could stay the same since it uses a parallel spvc_msl_vertex_attribute struct.
As far as I can tell...SPIRV-Cross only uses the location, builtin, and format values.
@cdavis5e Most of those three are used by code introduced with tess...so you'd be better able to remark on whether we can elide any of those elements too.