Make sure all hidden files are outside the background image

If the user enabled Mac OS X to show hidden files then when mounted the
generated DMG package may show some of them within the bounds of the
background image.

This change makes sure that all items in the DMG package are moved to a
position outside the bounds of the background image. The
POSITITION_CLAUSE and APPLICATION_CLAUSE that are executed later will
still place the app icon and Application correctly.

This is an awesome change, thank you very much!

When I mount my DMG file the window is scrolled to the far right displaying my hidden files.

The icons for my application and the Application folder are located at the coordinates where I placed them, but I have to manually scroll to the left to see them.

Currently, I do not have a background image for my DMG.

@hermwong sorry for this! I create PR https://github.com/andreyvit/yoursway-create-dmg/pull/36 to resolve the issue.

PR merged.

@kaloyan-raev no worries, just glad that I was able to help out. Thanks for the quick resolution to the issue!


Update documentation to replace Apache Arrow DataFusion with Apache DataFusion

Which issue does this PR close?

Part of https://github.com/apache/arrow-datafusion/issues/9691
Rationale for this change

DataFusion is now a top-level project
What changes are included in this PR?

Documentation changes only.
There are no changes to links or release process yet.
Are these changes tested?

No
Are there any user-facing changes?

We should have separate PR on repo specific things, like paths, but this gonna be when code moved to the new repo, imho

We should have separate PR on repo specific things, like paths, but this gonna be when code moved to the new repo, imho

I have filed https://github.com/apache/arrow-datafusion/issues/10134 to track this


Layer above overlay layer not transparent

When I added README's Adding Hillshade to the example, the background of the Hillshade layer was displayed without transparency and the base map layer became invisible.
Is there a setting to make it transparent?
Thank you

The example in the readme relies on fill-opacity for this purpose. Can you add your theme to this issue so that we can see what you've done?

What I want to do is to overlay a map showing a specific area on top of the basemap layer.
`
FlutterMap(
mapController: _mapController,
children: [
VectorTileLayer(
theme: _style(),
tileProviders: TileProviders({
'openmaptiles': _cachingTileProvider(_basemapPath()),
'overlay': _cachingTileProvider(_overlayPath()),
})
),
],
),
Map<String, dynamic> _style() {
return
{
...
"sources": {
"openmaptiles": {"type": "vector", "url": "mbtiles://japan.mbtiles"},
"overlay": {
"type": "vector",
"url": "mbtiles://assets/data/tsunami-shinsui.mbtiles"
}
},
...
"layers": [
{
"id": "background",
"type": "background",
"source": "openmaptiles",
"paint": {"background-color": "#f8f4f0"}
},
{
"id": "background",
"type": "background",
"source": "overlay",
"paint": {"background-color": "#ffffff", "fill-opacity": 0}
},
...
basemap style here
...
{
"id": "tsunamishinsui",
"type": "fill",
"source": "overlay",
"source-layer": "tsunamishinsui",
"layout": {"visibility": "visible"},
"paint": {"fill-color": "#0000FF", "fill-opacity": 0.2}
}
}
`
Thank you

I deleted the background of the overlay layer, but the problem that the background is not transparent does not change
Thank you

{
    "id": "background",
    "type": "background",
    "source": "openmaptiles",
    "paint": { "background-color": "#f8f4f0" }
},
{
    "id": "background",
    "type": "background",
    "source": "overlay",
    "paint": { "background-color": "#ffffff", "fill-opacity": 0 }
}

Don't use the same id twice. Choose another id for the "overlay" layer like background-overlay:

{
    "id": "background",
    "type": "background",
    "source": "openmaptiles",
    "paint": { "background-color": "#f8f4f0" }
},
{
    "id": "overlay-background",
    "type": "background",
    "source": "overlay",
    "paint": { "background-color": "#ffffff", "fill-opacity": 0 }
}

If you want to have your overlay background layered over your real background then try the following:

{
    "id": "background",
    "type": "background",
    "source": "openmaptiles",
    "paint": { "background-color": "#f8f4f0", "fill-opacity": 1 }
},
{
    "id": "overlay-background",
    "type": "background",
    "source": "overlay",
    "paint": { "background-color": "#ffffff", "fill-opacity": 0. 2 }
}

Hope it helps as I am unable to test it

I deleted the background of the overlay layer, but the problem that the background is not transparent does not change

The overlay layer is the one you want to be a bit transparent. You don't want the main layer to have any transparency.

I tried, but it doesn't work.
I've tried changing some fill-opacity values, but no change.
Isn't fill-opacity being ignored?
Thank you

I have the same issue for now ...

I've added some examples here: https://github.com/greensopinion/flutter-vector-map-tiles-examples
The examples don't directly address the issue of using multiple tile sources and transparency, but they do show hillshade.

I was able to make it work as expected by hacking.
Here is the sample code

FlutterMap(
  mapController: _controller,
    options: MapOptions(
      ...
    ),
  children: [
      VectorTileLayer(
        theme: ThemeReader().read(osmBrightJaStyle()),
        tileProviders: TileProviders(
          {
            "openmaptiles": NetworkVectorTileProvider(
                maximumZoom: 14,
                urlTemplate:
                    "https://tiles.stadiamaps.com/data/openmaptiles/{z}/{x}/{y}.pbf?api_key=API_KEY"),
          }  // Doesn't work if multiple TileProviders are specified
        ),
      ),
      VectorTileLayer(
        theme: ThemeReader().read(osmBrightJaStyle()),
        tileProviders: TileProviders({
          'thunderforest_outdoors': NetworkVectorTileProvider(
              maximumZoom: 14,
              urlTemplate:
                  'https://a.tile.thunderforest.com/thunderforest.outdoors-v2/{z}/{x}/{y}.vector.pbf?apikey=API_KEY')
        }),
      ),
  ],
)

Map<String, dynamic> osmBrightJaStyle() {
  return <String, dynamic>{
  ...
    'layers': [
      {
        'id': 'background',
        'type': 'background',
        'source': 'openmaptiles',
        'paint': {
          'background-color': 'rgba(248,244,240,0)',   // set transparency to 0
        }
      },
      {
        'id': 'landcover-glacier',
        'type': 'fill',
        'metadata': {'mapbox:group': '1444849388993.3071'},
        'source': 'openmaptiles',
        'source-layer': 'landcover',
        'filter': ['==', 'subclass', 'glacier'],
        'layout': {'visibility': 'visible'},
        'paint': {
          'fill-color': '#fff',
          'fill-opacity': {
            'base': 1,
            'stops': [
              [0, 0.9],
              [10, 0.3]
            ]
          }
        }
      },
      ...
      {
        "id": "hillshade_highlight_brightest",
        "type": "fill",
        "source": "thunderforest_outdoors",
        "source-layer": "hillshade",
        "filter": [
          "any",
          [">=", "level", 225]
        ],
        "paint": {"fill-color": "rgba(255,255,255,0.08)"}
      },

thank you

I've provided a multi-layer example: https://github.com/greensopinion/flutter-vector-map-tiles-examples
See https://github.com/greensopinion/flutter-vector-map-tiles-examples/blob/main/lib/examples/multi_layer.dart for details.


OC Cluster Up command support

Hello,
I would like to use the oc cluster up command to start a local OpenShift all-in-one cluster.
I tried to use the plugin and configured the local registry, but I still can't build and push the project.
Unfortunately I don't understand the error message
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.3.5:build (default-cli) on project messaging-proxy: Failed to execute the build: Unable to build the image using the OpenShift build service: Failure executing: POST at: https://<IP_ADDRESS>:8443/oapi/v1/namespaces/default/buildconfigs/messaging-proxy-s2i/instantiatebinary?commit=. Message: build messaging-proxy-s2i-11 failed: : . Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=build messaging-proxy-s2i-11 failed: : , metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal io.fabric8:fabric8-maven-plugin:3.3.5:build (default-cli) on project messaging-proxy: Failed to execute the build
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to execute the build
	at io.fabric8.maven.plugin.mojo.build.BuildMojo.buildAndTag(BuildMojo.java:233)
	at io.fabric8.maven.docker.BuildMojo.executeInternal(BuildMojo.java:44)
	at io.fabric8.maven.plugin.mojo.build.BuildMojo.executeInternal(BuildMojo.java:210)
	at io.fabric8.maven.docker.AbstractDockerMojo.execute(AbstractDockerMojo.java:223)
	at io.fabric8.maven.plugin.mojo.build.BuildMojo.execute(BuildMojo.java:189)
	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
	... 20 more
Caused by: io.fabric8.maven.core.service.Fabric8ServiceException: Unable to build the image using the OpenShift build service
	at io.fabric8.maven.core.service.openshift.OpenshiftBuildService.build(OpenshiftBuildService.java:90)
	at io.fabric8.maven.plugin.mojo.build.BuildMojo.buildAndTag(BuildMojo.java:230)
	... 26 more
Caused by: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://<IP_ADDRESS>:8443/oapi/v1/namespaces/default/buildconfigs/messaging-proxy-s2i/instantiatebinary?commit=. Message: build messaging-proxy-s2i-11 failed: : . Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=build messaging-proxy-s2i-11 failed: : , metadata=ListMeta(resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}).
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:332)
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:271)
	at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:241)
	at io.fabric8.openshift.client.dsl.internal.BuildConfigOperationsImpl.fromInputStream(BuildConfigOperationsImpl.java:271)
	at io.fabric8.openshift.client.dsl.internal.BuildConfigOperationsImpl.fromFile(BuildConfigOperationsImpl.java:228)
	at io.fabric8.openshift.client.dsl.internal.BuildConfigOperationsImpl.fromFile(BuildConfigOperationsImpl.java:66)
	at io.fabric8.maven.core.service.openshift.OpenshiftBuildService.startBuild(OpenshiftBuildService.java:247)
	at io.fabric8.maven.core.service.openshift.OpenshiftBuildService.build(OpenshiftBuildService.java:82)
	... 27 more

Do I have to configure other settings? Please see my POM.xml
Does this plugin support another OpenShift cluster which is not started with Minishift?
Info

f-m-p version : 3.3.5
Maven version (mvn -v) : 3.3.9
oc v1.5.0+031cbe4
kubernetes v1.5.2+43a9be4

Can you reach you OpenShift cluster with e.g. oc get nodes  ? It look like a connection problem to the openshift server.

Yes, the OC client works.
oc get builds
NAME                     TYPE      FROM      STATUS    STARTED   DURATION
messaging-proxy-s2i-10   Source    Binary    Failed
messaging-proxy-s2i-11   Source    Binary    Failed

I investigate why the builds have failed.

But if should work in general, I can close the issue and investigate further.

Yes, it should work. We use f-m-p very often with minishift which internally uses oc cluster up, too. This shouldn't be a general problem.
You can leave this issue open if you need some further assistance (even when its not a bug ;-)

I guess I have the same issue like this issue: https://github.com/openshift/origin/issues/13915 or this issue: https://github.com/openshift/origin/issues/13937

yes, I've seen that. It's a regression coming in probably with origin 1.5.0 so if you have the chance to use still an older version you could retry (minishift comes with an option to the select the origin version)

I could be my Docker version: https://github.com/openshift/origin/issues/13284

It works after downgrading from Docker v17.04.0-ce to Docker 1.13.1

Spam spam :) Btw the plugin is awesome work. Thanks :+1:

It doesn't look like a bug to me, so closing this. Feel free to reopen if anyone still faces this.


Change ReferenceNamers getPrefix into getReference. fixes #9

to fix #9 I created a non backwards compatible change in the Interface, and added a small test.
The PropertyReferenceNamer isn't the best usecase for this, but this is how I would use it. We can move this to the testing namespace, if you feel like it.
best regards
Philipp

Hi,
can someone have a look at this?

This looks pretty good. Let me have a look at it later today and I’ll see about getting it merged in.

Alright, it's merged in and I tagged a new release. Working on AliceGeneratorBundle now. Let's see if I can get Symfony 4 support working...
Thanks so much for contributing! Sorry it took me so long to get to this.


Remove Logentries in favor of standard 12factor logging

We should remove the le gem in favor of logging to STDOUT.

I can take this!


[BUG]: putting output on a different drive breaks it

Program version
5.1.4
Operating System
Linux
Type
CLI
Service
Crunchyroll
Command used
aniDL --service crunchy --dubLang eng --episode GEVUZ7WGP --force n --fileName ./anime/en-US/Blue Exorcist/Season 03/Blue Exorcist - S03E09 - Help Me
Show ID
G649PJ0JY
Episode
GEVUZ7WGP
Console Output
=== Multi Downloader NX 5.1.4 ===

USER: <Removed>
Your Country: <Removed>

Requested object ID: GEVUZ7WGP
 ✓[S:GRVNC2E78|E:GEVUZ7WGP|EPI.928563] Blue Exorcist -Shimane Illuminati Saga- (English Dub) - 9 - Help Me [23m40s, SUB, DUB, STREAM]

Requesting: [E:GEVUZ7WGP] Blue Exorcist -Shimane Illuminati Saga- (English Dub) - 9 - Help Me
Chapter request successful
Selecting raw stream
Full stream found! (✓1: adaptive_chrome_dash_drm/eng/- )
Downloading video...
Playlists URL: https://cr-play-service.prd.crunchyrollsvc.com/v1/manifest/GEVUZ7WGP/evs3/b369b4ddf71b40fc98b97d7cdabc95f1/assets/p/2b74255b8cc31b8e25a6e095b788d7bd_,5535061.mp4,5535062.mp4,5535060.mp4,5535058.mp4,5535059.mp4,4496.txt,.urlset/manifest.mpd?playbackGuid=0e-426c151d-bb75-43be-851f-3ce8ac98c37b&accountid=25e2f192-51d8-558e-a8f3-64d310785a25 (adaptive_chrome_dash_drm/eng/-)
Servers available:
	fy.v.vrv.co
Available Video Qualities:
	[1] 428x240 (487KiB/s)
	[2] 640x360 (973KiB/s)
	[3] 848x480 (1946KiB/s)
	[4] 1280x720 (3903KiB/s)
	[5] 1920x1080 (7798KiB/s)
Available Audio Qualities:
	[1] 64kB/s
	[2] 96kB/s
	[3] 128kB/s
Selected quality:
	Video: 1920x1080 (7798KiB/s)
	Audio: 128kB/s
	Server: fy.v.vrv.co
Stream URL: https://fy.v.vrv.co/evs3/b369b4ddf71b40fc98b97d7cdabc95f1/assets/p/2b74255b8cc31b8e25a6e095b788d7bd_,5535061.mp4,5535062.mp4,5535060.mp4,5535058.mp4,5535059.mp4,4496.txt
Total parts in video stream: 355 (36*10)
Saving stream to «/home/blastbolt5/anime/temp-GEVUZ7WGP.video.enc.m4s»...
Download and save init part...
Init part downloaded.
10 of 355 parts downloaded [3%] (28s | 41Mb/s)
20 of 355 parts downloaded [6%] (23s | 57Mb/s)
30 of 355 parts downloaded [8%] (24s | 57Mb/s)
40 of 355 parts downloaded [11%] (23s | 60Mb/s)
50 of 355 parts downloaded [14%] (21s | 62Mb/s)
60 of 355 parts downloaded [17%] (21s | 61Mb/s)
70 of 355 parts downloaded [20%] (20s | 61Mb/s)
80 of 355 parts downloaded [23%] (19s | 64Mb/s)
90 of 355 parts downloaded [25%] (18s | 63Mb/s)
100 of 355 parts downloaded [28%] (17s | 65Mb/s)
110 of 355 parts downloaded [31%] (17s | 64Mb/s)
120 of 355 parts downloaded [34%] (16s | 64Mb/s)
130 of 355 parts downloaded [37%] (15s | 65Mb/s)
140 of 355 parts downloaded [39%] (14s | 65Mb/s)
150 of 355 parts downloaded [42%] (13s | 65Mb/s)
160 of 355 parts downloaded [45%] (12s | 66Mb/s)
170 of 355 parts downloaded [48%] (12s | 64Mb/s)
180 of 355 parts downloaded [51%] (11s | 63Mb/s)
190 of 355 parts downloaded [54%] (11s | 62Mb/s)
200 of 355 parts downloaded [56%] (10s | 63Mb/s)
210 of 355 parts downloaded [59%] (9s | 63Mb/s)
220 of 355 parts downloaded [62%] (9s | 64Mb/s)
230 of 355 parts downloaded [65%] (8s | 64Mb/s)
240 of 355 parts downloaded [68%] (7s | 64Mb/s)
250 of 355 parts downloaded [70%] (7s | 64Mb/s)
260 of 355 parts downloaded [73%] (6s | 64Mb/s)
270 of 355 parts downloaded [76%] (5s | 64Mb/s)
280 of 355 parts downloaded [79%] (5s | 65Mb/s)
290 of 355 parts downloaded [82%] (4s | 64Mb/s)
300 of 355 parts downloaded [85%] (3s | 65Mb/s)
310 of 355 parts downloaded [87%] (3s | 65Mb/s)
320 of 355 parts downloaded [90%] (2s | 65Mb/s)
330 of 355 parts downloaded [93%] (1s | 66Mb/s)
340 of 355 parts downloaded [96%] (1s | 66Mb/s)
350 of 355 parts downloaded [99%] (0s | 66Mb/s)
355 of 355 parts downloaded [100%] (0s | 65Mb/s)
Total parts in audio stream: 355 (36*10)
Saving stream to «/home/blastbolt5/anime/temp-GEVUZ7WGP.audio.enc.m4s»...
Download and save init part...
Init part downloaded.
10 of 355 parts downloaded [3%] (2s | 11Mb/s)
20 of 355 parts downloaded [6%] (5s | 4.7Mb/s)
30 of 355 parts downloaded [8%] (4s | 6.0Mb/s)
40 of 355 parts downloaded [11%] (4s | 6.0Mb/s)
50 of 355 parts downloaded [14%] (3s | 6.6Mb/s)
60 of 355 parts downloaded [17%] (3s | 7.3Mb/s)
70 of 355 parts downloaded [20%] (3s | 7.1Mb/s)
80 of 355 parts downloaded [23%] (2s | 7.5Mb/s)
90 of 355 parts downloaded [25%] (3s | 6.9Mb/s)
100 of 355 parts downloaded [28%] (2s | 7.3Mb/s)
110 of 355 parts downloaded [31%] (2s | 7.7Mb/s)
120 of 355 parts downloaded [34%] (2s | 8.1Mb/s)
130 of 355 parts downloaded [37%] (2s | 8.5Mb/s)
140 of 355 parts downloaded [39%] (2s | 8.8Mb/s)
150 of 355 parts downloaded [42%] (2s | 9.1Mb/s)
160 of 355 parts downloaded [45%] (1s | 9.4Mb/s)
170 of 355 parts downloaded [48%] (1s | 9.7Mb/s)
180 of 355 parts downloaded [51%] (1s | 9.4Mb/s)
190 of 355 parts downloaded [54%] (1s | 9.6Mb/s)
200 of 355 parts downloaded [56%] (1s | 9.3Mb/s)
210 of 355 parts downloaded [59%] (1s | 9.5Mb/s)
220 of 355 parts downloaded [62%] (1s | 9.6Mb/s)
230 of 355 parts downloaded [65%] (1s | 9.7Mb/s)
240 of 355 parts downloaded [68%] (1s | 9.9Mb/s)
250 of 355 parts downloaded [70%] (1s | 10Mb/s)
260 of 355 parts downloaded [73%] (1s | 10Mb/s)
270 of 355 parts downloaded [76%] (1s | 10Mb/s)
280 of 355 parts downloaded [79%] (0s | 10Mb/s)
290 of 355 parts downloaded [82%] (0s | 11Mb/s)
300 of 355 parts downloaded [85%] (0s | 11Mb/s)
310 of 355 parts downloaded [87%] (0s | 11Mb/s)
320 of 355 parts downloaded [90%] (0s | 11Mb/s)
330 of 355 parts downloaded [93%] (0s | 11Mb/s)
340 of 355 parts downloaded [96%] (0s | 11Mb/s)
350 of 355 parts downloaded [99%] (0s | 11Mb/s)
355 of 355 parts downloaded [100%] (0s | 11Mb/s)
Decryption Needed, attempting to decrypt
Started decrypting video

> "mp4decrypt" --show-progress --key <removed> "/home/blastbolt5/anime/temp-GEVUZ7WGP.video.enc.m4s" "/home/blastbolt5/anime/temp-GEVUZ7WGP.video.m4s"
Decryption done for video
node:fs:1032
  binding.rename(
          ^

Error: EXDEV: cross-device link not permitted, rename '/home/blastbolt5/anime/temp-GEVUZ7WGP.video.m4s' -> '/home/blastbolt5/anime/anime/en-US/Blue Exorcist/Season 03/Blue Exorcist - S03E09 - Help Me.English.video.m4s'
    at Object.renameSync (node:fs:1032:11)
    at eIe.<anonymous> (/snapshot/_builds/index.cjs)
    at Generator.next (<anonymous>)
    at fulfilled (/snapshot/_builds/index.cjs)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  errno: -18,
  code: 'EXDEV',
  syscall: 'rename',
  path: '/home/blastbolt5/anime/temp-GEVUZ7WGP.video.m4s',
  dest: '/home/blastbolt5/anime/anime/en-US/Blue Exorcist/Season 03/Blue Exorcist - S03E09 - Help Me.English.video.m4s'
}

Node.js v20.11.1

Additional Information
Seems to be an issue that the software renames the file instead of moving it which isn't allowed when moving across partitions
This used to work so something must have changed at some point, so something must have changed in the past month or so since I last updated

Ah, yea DRM saves to a temp name and then moves it, as it turns out though apparently nodes way of moving things is more akin to a rename than a move, so it doesn't work across filesystems... I'll see if I can implement a function to copy the file, then delete the temp file after the copy, rather than a direct move. (ideally only if it's on a different filesystem, but that may be hard to check)

Yeah leaving it in a temp directory, moving and then deleting it is my temp fix for now (cause I have it mostly automated)
Weird that it used to work fine tho


Minimum Deployment target

Context 🕵♀
Apps and frameworks have a minimum deployment target, which defines the lowest OS version, on which they can run.
What 🌱
Currently the Carthage.xcodeproj defines the following minimum deployment targets:
iOS: 11.2
mac: 10.13
This forces the very current OS versions. Is this necessary? A lot of users (especially on macOS) are on older versions and this would force developers to only support the above versions upwards.
Proposal 🎉
I've got it running on at least macOS 10.12. So the current requirement is not necessary. I would suggest lowering the deployment target to the lowest version you want to support. If you provide me with the info I can create a PR.

Good point @olbrichj.
The carthage project is generated via Xcodegen. To change the deployment target the carthage-project.yml needs to define them explicitly otherwise it uses the default of the newest SDK's in Xcode
name: Carthage
options:
  deploymentTarget:
    iOS: 9.0
    macOS: 10.11
...

and the project has to be regenerated with rake generate_carthage_project
Not sure what sensible values are here. I don't have an older version of macOS to test with. To be sure we could try some different versions on travis. I think the above values should be fine though.
@olbrichj are you happy to open a PR for this?

Found the time today :D. Though XcodeGen parses 10.10 oddly. It results in 10.1 so, for now, it's set to 10.11. Will create an issue in XcodeGen correspondingly.
On the other hand I've tried your suggested version via options but it didn't work. So the PR uses IPHONEOS_DEPLOYMENT_TARGET and MACOSX_DEPLOYMENT_TARGET.


Manage to run one of the interactive environments, e.g. ReplicaCAD

Okay, so, I did manage to run the environment, and the interaction works, but I am able to clip through the walls. I can also walk through all the objects that can be interacted with.
The former I think is caused by an erroneous viewer configuration. I think this could be fixed if we looked into it.
The latter seems to be a design choice of the simulator — it doesn't take dynamic objects into account when computing the navmesh.


Redisgraph expects the query params to be in a separate argument than the query

GRAPH.QUERY <graph_name> "MATCH (p:Person {name: $name_param, birth_year: $birth_year_param}) RETURN p" query_params "CYPHER name_param = 'Niccolò Machiavelli' birth_year_param = 1469"

Reference: https://github.com/RedisGraph/RedisGraph/pull/1849


Allow manually setting default command queue via default_queue()

By doing so, the associated default device and context will automatically match the user-provided command queue. It
Guarantees unique default queue/device/context is returned when calling from multiple threads (requires config macro BOOST_COMPUTE_THREAD_SAFE)
Resolves issue #827

There seems to have missing pthread linkage when compiling with std::thread on some machines (reported by travis-ci). But on my Linux virtual machine I couldn't repro the same issue. So I think maybe if updating to newer compiler helps?

Coverage increased (+0.005%) to 84.03% when pulling 73580396ef28276b8f35c4e65360d477ed0cbf5d on rosenrodt:pr-set-default-command-queue into 5a29a4d0a1ad8adf9cc19a115252930a628d8b48 on boostorg:develop.

@jszuppe any comment on it? 😃

I'm really sorry for delay. I had a busy week and then a few days of holidays without PC.

@jszuppe Glad to hear you back from your holiday. I have left some reply under your comments and I am eager to start working on the feature again

I just force-pushed a one line fix for test_attach_user_queue_error.cpp due to CI check failure
compute::device user_device = compute::system::devices().front();
compute::context user_context(user_device);
compute::command_queue user_queue(user_context, user_device);

//compute::system::default_device();
compute::system::default_context();
// ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
// purposefully set the default context that is incompatible with user-provided command queue

BOOST_CHECK_THROW(
    compute::system::default_queue(user_queue),
    compute::set_default_queue_error);

Fails in CI are unrelated to the PR. Merging. Good job!


A couple of errors building with ncurses

I encountered an error building with ncurses that is described at https://bbs.archlinux.org/viewtopic.php?id=255197 where the ncursesw/ncurses.h could not be found. The suggested workaround was to appending the following to stack.yaml
flags:
  ncurses:
    force-narrow-library: true

This helps, but then leads to the following error when building:
[1 of 3] Compiling Lib
[2 of 3] Compiling Paths_pong
[3 of 3] Compiling Pong
<command line>: -lpanelw: cannot open shared object file: No such file or directory

I'm using Arch linux, so there appears to be some missing system dependencies although from looking at /usr/lib I see ncurses and panelw shared object files.

I had a bit better luck using Ubuntu. I'll create a PR with a Vagrant file that can be used to provision a VM with the required dependencies.

Here's a PR that sets up a dev VM that can build with ncurses: https://github.com/caryman/pong/pull/11

I am running a vm with Ubuntu 20.04.3 LTS with no issues. Stack builds pong and runs out of the box.

I'm fine for now using Ubuntu for this project. It looks like the haskell-ncurses project includes ncursesw/ncurses.h, but apparenty, it should have included ncurses.h instead. Since haskell-ncurses appears to be somewhat abandoned, we'd have to fork that project to fix it, so it's probably not worth that effort.
For that matter, instead of a VM, I could have probably built a docker container image to reduce resources. Maybe I'll take a look at doing that. I think I will at least upgrade the Vagrant box to Ubuntu 20.04 LTS just so we're all using roughly the same distribution.

I've updated the Ubuntu version to 20.04 LTS in the Vagrantfile in https://github.com/caryman/pong/pull/13. Also, in that PR, I added a Dockerfile with steps to build and run pong within a Docker container which avoids some of the VM overhead. With these multiple options to build and run pong, I'm going to close this issue.


Show number of GPU's being used at any given moment for each cluster (out of the total number of GPUs available)

From INC0339970

I am writing this email to give somewhat feedback on ondemand.osc.edu website. In the website, I usually check Clusters > System Status section to check which cluster is least busy before I submit a job. I use the cluster that is least busy to shorten the queued time. This has worked pretty well. However, if I want to use GPU to boost up my calculation, it is hard to know how many GPUs are being used at the moment. As there are much smaller number of GPUs than CPUs, my jobs were queued much longer than my expectation based on System Status. So, I was wondering if we can have 'GPU System Status' or something that tells how many GPUs are being used and how many GPU runs are queued etc. GPGPU being more and more popular, I think this kind of update will help people including myself who wants to use GPU in OSC a lot

Maybe call out how many free nodes/procs/gpus there are:

Very cool.

Alan Chalker, Ph.D.
alanc<EMAIL_ADDRESS>614-247-8672
From: Eric Franz<EMAIL_ADDRESS>Sent: Wednesday, March 13, 2019 10:23 AM
To: AweSim-OSC/osc-systemstatus<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [AweSim-OSC/osc-systemstatus] Show number of GPU's being used at any given moment for each cluster (out of the total number of GPUs available) (#68)
[screen 2019-03-13 at 10 17 22 AM]https://user-images.githubusercontent.com/512333/54285968-53c09480-4579-11e9-9603-05bab7351ccc.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/AweSim-OSC/osc-systemstatus/issues/68#issuecomment-472440631, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGe2cj_Nc5lCktMl_7Q04fYSFTvyeSxIks5vWQnHgaJpZM4bsNX5.

While we’re at it, should we also do the same for the big-mem nodes?

Alan Chalker, Ph.D.
alanc<EMAIL_ADDRESS>614-247-8672
From: Eric Franz<EMAIL_ADDRESS>Sent: Wednesday, March 13, 2019 10:23 AM
To: AweSim-OSC/osc-systemstatus<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [AweSim-OSC/osc-systemstatus] Show number of GPU's being used at any given moment for each cluster (out of the total number of GPUs available) (#68)
[screen 2019-03-13 at 10 17 22 AM]https://user-images.githubusercontent.com/512333/54285968-53c09480-4579-11e9-9603-05bab7351ccc.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/AweSim-OSC/osc-systemstatus/issues/68#issuecomment-472440631, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGe2cj_Nc5lCktMl_7Q04fYSFTvyeSxIks5vWQnHgaJpZM4bsNX5.

The states of all the GPUs we can get a list of nodes with GPUs in XML format:
pbsnodes -s pitzer-batch.ten.osc.edu -x :gpu

This produes a bunch of nodes like:
  <Node>
    <name>p0256</name>
    <state>job-exclusive</state>
    <power_state>Running</power_state>
    <np>40</np>
    <properties>r740,ib-i4l1s11,ib-i4,eth-pitzer-rack06h1,eth-pitzer-rack06b1,pitzer-rack07,pitzer,gpu,v100,pfsdir,vis,ime</properties>
    <ntype>cluster</ntype>
    <jobs>0-39/420639.pitzer-batch.ten.osc.edu</jobs>
    <status>opsys=linux,uname=Linux p0256.ten.osc.edu 3.10.0-862.11.6.el7.x86_64 #1 SMP Fri Aug 10 16:55:11 UTC 2018 x86_64,sessions=15376<PHONE_NUMBER>01,nsessions=3,nusers=3,idletime=86941,totmem=445132568kb,availmem=430368088kb,physmem=394800924kb,ncpus=40,loadave=40.11,gres=,netload=2947886376928,size=881223036kb:892434684kb,state=free,varattr= ,cpuclock=Fixed,macaddr=24:6e:96:dd:63:34,version=6.1.2,rectime=1552502390,jobs=420639.pitzer-batch.ten.osc.edu</status>
    <mom_service_port>15002</mom_service_port>
    <mom_manager_port>15003</mom_manager_port>
    <gpus>2</gpus>
    <gpu_status>gpu[1]=gpu_id=0000:D8:00.0;gpu_pci_device_id=498340062;gpu_pci_location_id=0000:D8:00.0;gpu_product_name=Tesla V100-PCIE-16GB;gpu_memory_total=16130 MB;gpu_memory_used=11 MB;gpu_mode=Exclusive_Process;gpu_state=Unallocated;gpu_utilization=0%;gpu_memory_utilization=0%;gpu_ecc_mode=Disabled;gpu_temperature=24 C,gpu[0]=gpu_id=0000:3B:00.0;gpu_pci_device_id=498340062;gpu_pci_location_id=0000:3B:00.0;gpu_product_name=Tesla V100-PCIE-16GB;gpu_memory_total=16130 MB;gpu_memory_used=554 MB;gpu_mode=Exclusive_Process;gpu_state=Exclusive;gpu_utilization=75%;gpu_memory_utilization=17%;gpu_ecc_mode=Disabled;gpu_temperature=49 C;gpu_display=Enabled,gpu_display=Enabled,driver_ver=410.79,timestamp=Wed Mar 13 14:39:50 2019</gpu_status>
    <total_sockets>2</total_sockets>
    <total_numa_nodes>2</total_numa_nodes>
    <total_cores>40</total_cores>
    <total_threads>40</total_threads>
    <dedicated_sockets>0</dedicated_sockets>
    <dedicated_numa_nodes>0</dedicated_numa_nodes>
    <dedicated_cores>40</dedicated_cores>
    <dedicated_threads>40</dedicated_threads>
  </Node>

The complexity comes in that this node has 2 GPUs and the state of each GPU is in the gpu_status string, so parsing is slightly more challenging.
These commands also seems to do the trick:
efranz@pitzer-login01:~$ function gpu_states { pbsnodes -s $1 :gpu | ruby -n -e 'puts $_.scan(/gpu_state=(\w+)/)'; }
efranz@pitzer-login01:~$ echo "Pitzer: $(gpu_states pitzer-batch.ten.osc.edu | grep 'Unallocated' | wc -l)/$(gpu_states pitzer-batch.ten.osc.edu | wc -l)"
Pitzer: 30/64
efranz@pitzer-login01:~$ echo "Owens: $(gpu_states owens-batch.ten.osc.edu | grep 'Unallocated' | wc -l)/$(gpu_states owens-batch.ten.osc.edu | wc -l)"
Owens: 3/158

Its better in the context of a request to do one exec to get the XML though (or the non XML output) and parse the resulting data, than doing multiple execs.

Yes we should absolutely do big mem though I don't know the easiest approach to query that. I'll open a separate issue to track that work.

Note that even with this reporting it doesn't guarantee that you will get the queue time you want. Let say for example, PItzer above has 30/64 GPUs in use, but because Pitzer has 32 GPU nodes with two GPUs each, what if all 30 jobs have reserved the entire node and one GPU. In this case, while there are 34 GPUs that have the state Unallocated, there actually might only be 1 node and 2 GPUs available. This means that multiple users trying to request that resource will be stymied by queue times, and using the metric 30/64 is not helpful to determine which cluster to submit a GPU job to in order to get the shortest queue time.
In fact this is the example we have in the above node XML. There we have node p0256 with 2 GPUs, one in the state Unallocated and the other in the state Exclusive and one job 420639.pitzer-batch.ten.osc.edu is running on it.
I think you can take <dedicated_threads>40</dedicated_threads> over <total_threads>40</total_threads> (but not dedicated_cores, total_cores) to determine how many cores are reserved.
For example, here is a node o0700 that has 3 jobs running on it, the GPU is in use, but not all the cores are in use:
o0700
     state = free
     power_state = Running
     np = 28
     properties = broadwell-ep,r730,ib-i2l1s02,ib-i2,eth-owens-rack12h1,owens-rack12,owens,gpu,p100,vis,pfsdir,ime,beegfs
     ntype = cluster
     jobs = 0/4862755.owens-batch.ten.osc.edu,2-3,5-10/4890615.owens-batch.ten.osc.edu,11-18/4890616.owens-batch.ten.osc.edu
     status = opsys=linux,uname=Linux o0700.ten.osc.edu 3.10.0-862.25.3.el7.x86_64 #1 SMP Wed Nov 7 05:19:18 EST 2018 x86_64,sessions=7947<PHONE_NUMBER>44<PHONE_NUMBER>12<PHONE_NUMBER>31,nsessions=7,nusers=4,idletime=1374883,totmem=182247356kb,availmem=175375756kb,physmem=131915712kb,ncpus=28,loadave=5.09,gres=,netload=1293332383259,size=909151504kb:909207804kb,state=free,varattr= ,cpuclock=Fixed,macaddr=14:18:77:60:d1:58,version=6.1.2,rectime=1552504283,jobs=4862755.owens-batch.ten.osc.edu 4890615.owens-batch.ten.osc.edu 4890616.owens-batch.ten.osc.edu
     mom_service_port = 15002
     mom_manager_port = 15003
     gpus = 1
     gpu_status = gpu[0]=gpu_id=0000:04:00.0;gpu_pci_device_id=368578782;gpu_pci_location_id=0000:04:00.0;gpu_product_name=Tesla P100-PCIE-16GB;gpu_memory_total=16280 MB;gpu_memory_used=513 MB;gpu_mode=Default;gpu_state=Shared;gpu_utilization=16%;gpu_memory_utilization=1%;gpu_ecc_mode=Enabled;gpu_single_bit_ecc_errors=0;gpu_double_bit_ecc_errors=0;gpu_temperature=31 C,gpu_display=Enabled,driver_ver=410.79,timestamp=Wed Mar 13 15:11:17 2019
     total_sockets = 2
     total_numa_nodes = 2
     total_cores = 28
     total_threads = 28
     dedicated_sockets = 0
     dedicated_numa_nodes = 0
     dedicated_cores = 0
     dedicated_threads = 17

This line shows 17 cores in use:
jobs = 0/4862755.owens-batch.ten.osc.edu,2-3,5-10/4890615.owens-batch.ten.osc.edu,11-18/4890616.owens-batch.ten.osc.edu

Which corresponds to 17 requested ppn:
efranz@owens-login01:~$ qstat -f 4862755.owens-batch.ten.osc.edu | grep Resource_List.nodes
    Resource_List.nodes = 1:ppn=1:gpus=1:default
efranz@owens-login02:~$ qstat -f 4890615.owens-batch.ten.osc.edu | grep Resource_List.nodes
    Resource_List.nodes = 1:ppn=8
efranz@owens-login01:~$ qstat -f 4890616.owens-batch.ten.osc.edu | grep Resource_List.nodes
    Resource_List.nodes = 1:ppn=8

This will take some more thought. Lets put this on temporary hold.

This needs more design, but based on offline discussion the idea is knowing how many jobs that have requested gpus:

are currently running
are currently queued (or held)

Same with big mem nodes: how many jobs have requested big mem that:

are currently running
are currently queued (or held)

This should be available in the native hash attribute of the Info object returned for each job - hopefully this includes "gpus_reserved".
Using qstat -f you can see what this looks like. On Owens there is only 1 GPU per node so you have results like this:
    efranz@owens-login01:~$ qstat -f | grep gpus_reserved
        gpus_reserved = o0675:0
        gpus_reserved = o0676:0
        gpus_reserved = o0767:0+o0742:0+o0703:0+o0704:0

Notice each gpu node reserved is delimited using +. The gpu # in use is specified by the 0. So this matters on Pitzer:
efranz@pitzer-login03:~$ qstat -f | grep gpus_reserved
    gpus_reserved = p0243:0
    gpus_reserved = p0244:0
    gpus_reserved = p0244:1
    gpus_reserved = p0250:0
    gpus_reserved = p0250:1
    gpus_reserved = p0245:0
    gpus_reserved = p0245:1
    gpus_reserved = p0232:0-1
    gpus_reserved = p0240:0-1
    gpus_reserved = p0235:0-1
    gpus_reserved = p0225:0-1
    gpus_reserved = p0230:0-1
    gpus_reserved = p0242:0-1

Here a job that has reserved both GPUs on a GPU node on Pitzer shows a range: p0242:0-1.
I wonder if there were three or more gpus, if instead of a range it would use comma delmited numbers, 0,2 or a mixture 0,2-3. But that would require some investigation.
As far as jobs queued that requested, gpus, qstat -f shows Resource_List.feature = gpu and Resource_List.nodect = 1 and Resource_List.nodes = 1:ppn=40:gpus=2. But for queued jobs it looks like parsing Resource_List.nodes value to see if 2 gpus per node or one gpu per node was requested or not is required.

Report 4 numbers:

Number of GPUs unallocated (this is the free GPUs you have identified)
Number of full nodes available that contain one or more GPUs available
Number of jobs that have requested one or more GPUs that are currently queued
Number of GPUs requested by jobs that are currently queued


Problem render pages to pdf with images

I'm trying to render html body from email (MimeKit) that contains an embededs images.
I test two ways:

Changing the attribute img src to "file://" that are locate in an existing local path. For this case, trying to see the html when I paste the html code it makes an error with the image.
Changing the attribute img src to "data:image" and pasting the string for the bytes[] decoded. In this case it works and I can see the html but I can't create the pdf because there is an error creating the pdfdocument with this image.

Regards,
Andrews

I have done exactly what you are trying to do. I started out saving the images locally and using file:// references. Works OK but some browsers don't allow local file access so you may not see the images if you're opening the HTML to preview it during your development/testing. Later I took the other approach: replacing the img src references with data URIs (embedding the image inline as data). I did that mainly so the HTML document would be portable as Chrome doesn't really MHT/MHTML very well. Both approaches work fine for generating PDF using HtmlRenderer.PdfSharp. What specific error are you getting?


Tray

System tray works?
Do you intend to make it work?

System tray support would be nice, but I haven't ran into a program myself yet where there is a tray icon. I tried Dropbox I recall, but I wasn't able to figure out at the time what window messages to look out for.
Do you have any examples of programs that use a tray that could help test this?

Discord, Obs Studio

I added some basic system tray icon support in f2e2a122. There is an issue with icon transparency I haven't sorted out yet. I used OBS as the test case and as far as I have seen, the basic functionality seems to be working.

Perfect

Closing issue - any specific issues with the new tray support can be filed as separate issues.


Request for numbering clarification

Unless I've missed something obvious (which I don't think I have!) there seems to be absolutely no explanation of why the numbering used in all the code examples:
4    3    2
5    7    1
  6    0

doesn't match the numbering printed on the silkscreen:
7    1    2
6    8    3
  5    4

https://cdn.shopify.com/s/files/1/0174/1800/products/Dum_HAT_2_of_2_1024x1024.JPG?v=1450364274 from https://shop.pimoroni.com/products/drum-hat
Very confusing!

This is going to hurt a few existing users, but you've made a valid point.
I've included pad mapping into the library as part of https://github.com/pimoroni/drum-hat/commit/7c2b13c3815e2f7735a7831a70de7bb09a08eec1 which sorts out this complete insanity.
drumhat.on_hit now requires a pad number from 1 to 8, and so do the LED control functions.
The event ( of type CapTouchEvent ) argument handed down from the CapTouch library is also tagged up with the pad number which was hit, so you can:
def handle_hit(event):
    print("Hit on pad number {}".format(event.pad))

drumhat.on_hit(1,handle_hit)

Great! I guess you need to "fix" the numbering used in the drums.py and direct.py examples too?

I think direct.py will stay the same, since it's a barebones example that uses the Cap1xxx library directly, but yes... I need to fix that in drums.py!
I've fixed README.md too.

Sorted in https://github.com/pimoroni/drum-hat/commit/cc6ffa9fa58a70709240833385bdaca14a8ae35b. Oh this library has been an adventure in me-being-too-busy-to-give-it-the-attention-it-deserves. Thank you for pointing out the flaws, it's much easier to make progress when you've got a little more clarify on "the right approach."


azure-identity-cpp 1.10.0 requires azure-core-cpp >= 1.14.0

azure-identity-cpp 1.10.0 was released yesterday (https://github.com/Azure/azure-sdk-for-cpp/releases/tag/azure-identity_1.10.0)
None of its requirements in sdk/identity/azure-identity/vcpkg/vcpkg.json were updated between 1.9.0 and 1.10.0 (https://github.com/Azure/azure-sdk-for-cpp/compare/azure-identity_1.9.0...azure-identity_1.10.0)
The minimum required version of azure-core-cpp for azure-identity-cpp 1.10.0 is >= 1.9.0 (https://github.com/Azure/azure-sdk-for-cpp/blob/azure-identity_1.10.0/sdk/identity/azure-identity/vcpkg/vcpkg.json#L21)
azure-core-cpp 1.14.0 introduced a new file sdk/core/azure-core/inc/azure/core/resource_identifier.hpp (https://github.com/Azure/azure-sdk-for-cpp/compare/azure-core_1.13.0...azure-core_1.14.0)
azure-identity-cpp 1.10.0 requires this new file. Thus it fails when compiled against azure-core-cpp 1.13.0 (https://github.com/conda-forge/azure-identity-cpp-feedstock/pull/14#issuecomment-2402473981)
azure-identity-cpp was bumped to 1.11.0-beta.1, but it's minimum version of azure-core-cpp has still not been updated (https://github.com/Azure/azure-sdk-for-cpp/pull/6080)
This PR updates vcpkg.json to include the requirement azure-core-cpp >= 1.14.0

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[x] Descriptive title/description

[x] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[x] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

API change check
API changes are not detected in this pull request.


Question : How do I change between themes?

I wanted to change to the black-green theme but i dont understand how to

Hi, currently you can change skins by editing the main files.
This will change in the next update,
for powercord you have to edit the theme.scss and for better discord you have to edit the crearts.theme.css file.
Skins are loaded by commenting or not.
Lines with // are not loaded
Lines without // are loaded.
The file should look like this:

im new to powercord.. do i have to  make a pull request for this?

im new to powercord.. do i have to make a pull request for this?

to switch a skin, you actually need to edit the theme.scss in the themes folder. (Powercord)
This will change with v3, in v3 you only paste the skin code in the QuickCS/Custom CSS
I'm actually work on v3 but I cant say when it's done.

thanks! i figured it out!! kinda like betterdiscord!

Outdated from CreArts v2.


Properly handle when git encounters an unrecoverable error

Don't infinitely loop. Resolves #9208

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests

As much as I hate to admit it, I don't think this is the right solution. The Environment.Exit is wrong. The source of the unhandled exception is because we're running in two different "modes" in the proxy.

On CLI invocation of restore or push, we want to report a git error to CLI, then early exit from whatever command we're invoking.
When the proxy is running in a server, we want to throw a GitProcessException (which is an HttpException) because our custom ASP.NET middleware will turn that unhandled exception into a clean HTTP response for the user.

Effectively, my solution will cause the server to straight crash if anything goes wrong with any "unhandled" git exception.

As much as I hate to admit it, I don't think this is the right solution. The Environment.Exit is wrong. The source of the unhandled exception is because we're running in two different "modes" in the proxy.

On CLI invocation of restore or push, we want to report a git error to CLI, then early exit from whatever command we're invoking.
When the proxy is running in a server, we want to throw a GitProcessException (which is an HttpException) because our custom ASP.NET middleware will turn that unhandled exception into a clean HTTP response for the user.

Effectively, my solution will cause the server to straight crash if anything goes wrong with any "unhandled" git exception. I'm going to refactor so we can know what mode we're in via function signature update.

Added a bit for this exact binary setting to GitProcessHandler, and honor it. That addresses the above without entirely rewriting every usage of GitHandler.Run.

/azp run tools - test-proxy - tests

/azp run tools - test-proxy - tests


chore(git): HTTPS Clone

Description
Clone with https. Ssh is fickle when privileged git users are missing ssh keys for authentication with github. Instead, we can just use https to provide a secure, less fallible clone.

Current dependencies on/for this PR:

main

PR #74   👈

This comment was auto-generated by Graphite.


fixup traceserver.py

Correct process launching. Add 'start', 'stop' commands for daemonizing the
process.

I cleaned up your traceserver.py script. You can now use ./bin/traceserver.py to launch the jetty server in the foreground. You can also pass in start to launch the process in the background and stop to terminate the background process (on Linux/OSX).

Thanks


Uncaught TypeError: Cannot read property 'data' of null

[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.3
System: Mac OS X 10.11.1
Thrown From: nav-panel package, v0.0.6
Stack Trace
Uncaught TypeError: Cannot read property 'data' of null
At /Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:132

TypeError: Cannot read property 'data' of null
    at NavView.module.exports.NavView.getPanelState (/Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:132:17)
    at NavView.module.exports.NavView.saveFileState (/Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:200:14)
    at /Users/Adam/.atom/packages/nav-panel/lib/nav-panel.coffee:84:18
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:86:11)
    at PaneContainer.module.exports.PaneContainer.willDestroyPaneItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane-container.js:285:27)
    at Pane.module.exports.Pane.destroyItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:442:17)
    at Pane.module.exports.Pane.destroyActiveItem (/Applications/Atom.app/Contents/Resources/app.asar/src/pane.js:429:12)
    at Workspace.module.exports.Workspace.destroyActivePaneItem (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:639:35)
    at Workspace.module.exports.Workspace.destroyActivePaneItemOrEmptyPane (/Applications/Atom.app/Contents/Resources/app.asar/src/workspace.js:678:21)
    at atom-workspace.commandRegistry.add.core:close (/Applications/Atom.app/Contents/Resources/app.asar/src/register-default-commands.js:170:32)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:533:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:356:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:99:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
     -2:47.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -2:40.7.0 tree-view:add-file (span.name.icon.icon-file-directory)
  3x -2:38.5.0 core:backspace (atom-text-editor.editor.mini.is-focused)
  2x -2:33.5.0 editor:select-to-beginning-of-word (atom-text-editor.editor.mini.is-focused)
  3x -2:29 editor:move-to-beginning-of-word (atom-text-editor.editor.mini.is-focused)
     -2:26 core:confirm (atom-text-editor.editor.mini.is-focused)
     -2:10.6.0 core:paste (atom-text-editor.editor.is-focused)
     -2:07.2.0 atom-beautify:beautify-editor (atom-text-editor.editor.is-focused)
     -2:01.9.0 core:copy (atom-text-editor.editor.is-focused)
     -1:58.7.0 core:paste (atom-text-editor.editor.is-focused)
     -1:47.4.0 core:save (atom-text-editor.editor.is-focused)
     -1:10.6.0 tree-view:add-folder (li.file.entry.list-item.status-modified.selected)
     -1:08.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)
     -0:58.7.0 tree-view:cut (li.file.entry.list-item.status-added.selected)
     -0:53.5.0 tree-view:paste (span.name.icon.icon-file-directory)
     -0:02.2.0 core:close (ol.tree-view.list-tree.has-collapsable-children.focusable-panel.full-menu)

Config
{
  "core": {
    "audioBeep": false,
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ]
  }
}

Installed Packages
# User
MagicPython, v0.5.7
antialiased, v0.1.0
atom-beautify, v0.28.19
atom-material-syntax, v0.2.5
atom-material-ui, v0.8.0
autoclose-html, v0.19.0
autocomplete-paths, v1.0.2
file-icons, v1.6.12
linter, v1.11.2
linter-csslint, v1.1.0
minimap, v4.16.1
nav-panel, v0.0.6
open-in-browsers, v0.0.7
pigments, v0.19.0
tool-bar-main, v0.0.8
wakatime, v5.0.1

# Dev
No dev packages

Fixed in v0.0.7

Happened again:
[Enter steps to reproduce below:]

...
...

Atom Version: 1.2.4
System: Mac OS X 10.11.1
Thrown From: nav-panel package, v0.0.8
Stack Trace
Uncaught TypeError: Cannot read property 'data' of null
At /Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:430

TypeError: Cannot read property 'data' of null
    at NavView.module.exports.NavView.destroyPanel (/Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:430:38)
    at NavView.module.exports.NavView.updateFile (/Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:125:6)
    at /Users/Adam/.atom/packages/nav-panel/lib/nav-panel.coffee:75:22

Commands
     -8:45 core:backspace (atom-text-editor.editor.is-focused)
     -8:35 core:copy (atom-text-editor.editor.is-focused)
  2x -8:33.4.0 core:paste (atom-text-editor.editor.is-focused)
     -8:29.2.0 core:save (atom-text-editor.editor.is-focused)
     -8:27.3.0 core:backspace (atom-text-editor.editor.is-focused)
     -8:26.3.0 core:save (atom-text-editor.editor.is-focused)
  2x -8:13.3.0 core:backspace (atom-text-editor.editor.is-focused)
     -8:11.9.0 core:save (atom-text-editor.editor.is-focused)
  2x -1:37.7.0 core:backspace (atom-text-editor.editor.is-focused)
     -1:32.3.0 core:save (atom-text-editor.editor.is-focused)
     -0:31.8.0 core:backspace (atom-text-editor.editor.is-focused)
     -0:31.4.0 core:save (atom-text-editor.editor.is-focused)
  2x -0:04.6.0 core:undo (atom-text-editor.editor.is-focused)
     -0:02.0 core:redo (atom-text-editor.editor.is-focused)
     -0:01.6.0 core:save (atom-text-editor.editor.is-focused)
     -0:01.6.0 core:close (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "audioBeep": false,
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ]
  }
}

Installed Packages
# User
MagicPython, v0.5.7
antialiased, v0.1.0
atom-beautify, v0.28.19
atom-material-syntax, v0.2.6
atom-material-ui, v0.8.0
autoclose-html, v0.19.0
autocomplete-paths, v1.0.2
file-icons, v1.6.12
linter, v1.11.3
linter-csslint, v1.1.0
minimap, v4.16.2
nav-panel, v0.0.8
open-in-browsers, v0.0.7
pigments, v0.19.1
tool-bar-main, v0.0.8
wakatime, v5.0.1

# Dev
No dev packages

Happened in latest version of Aom, just closing files this time.
[Enter steps to reproduce below:]

...
...

Atom Version: 1.3.1
System: Mac OS X 10.11.2
Thrown From: nav-panel package, v0.0.10
Stack Trace
Uncaught TypeError: Cannot read property 'data' of null
At /Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:430

TypeError: Cannot read property 'data' of null
    at NavView.module.exports.NavView.destroyPanel (/Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:430:38)
    at NavView.module.exports.NavView.updateFile (/Users/Adam/.atom/packages/nav-panel/lib/nav-view.coffee:125:6)
    at /Users/Adam/.atom/packages/nav-panel/lib/nav-panel.coffee:75:22

Commands
     -9:57.6.0 autocomplete-plus:confirm (atom-text-editor.editor.is-focused.autocomplete-active)
     -9:50.5.0 core:backspace (atom-text-editor.editor.is-focused)
     -9:49.6.0 core:move-down (atom-text-editor.editor.is-focused)
  3x -9:49.2.0 editor:select-to-beginning-of-word (atom-text-editor.editor.is-focused)
     -9:47.6.0 core:paste (atom-text-editor.editor.is-focused)
     -9:42.9.0 core:copy (atom-text-editor.editor.is-focused)
     -9:41.2.0 editor:newline (atom-text-editor.editor.is-focused)
  5x -9:40.1.0 core:backspace (atom-text-editor.editor.is-focused)
     -9:32.4.0 editor:newline (atom-text-editor.editor.is-focused)
     -9:32.2.0 core:paste (atom-text-editor.editor.is-focused)
     -9:26.2.0 core:save (atom-text-editor.editor.is-focused)
  6x -0:12.3.0 core:close (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "audioBeep": false,
    "themes": [
      "atom-material-ui",
      "atom-material-syntax"
    ]
  }
}

Installed Packages
# User
MagicPython, v0.5.7
antialiased, v0.1.0
atom-beautify, v0.28.19
atom-material-syntax, v0.2.10
atom-material-ui, v0.8.0
autoclose-html, v0.19.0
autocomplete-paths, v1.0.2
caniuse, v0.5.5
file-icons, v1.6.13
imdone-atom, v1.3.11
js-hyperclick, v1.4.1
linter, v1.11.3
linter-csslint, v1.1.0
minimap, v4.18.0
nav-panel, v0.0.10
neon-cursor, v1.4.0
open-in-browsers, v0.0.7
pigments, v0.19.3
tool-bar-main, v0.0.8
wakatime, v5.0.2

# Dev
No dev packages

Was happening after saving newly created file. Fixed in v0.0.11


[arrow:x64-windows-static] Arrow 12 issue with acero

Operating system
Windows
Compiler
MSVC
Steps to reproduce the behavior
.\vcpkg\vcpkg.exe install "arrow[core,csv,dataset,filesystem,json,parquet]" --triplet=x64-windows-static  --recurse

Failure logs
CMake Error at C:/Program Files/CMake/share/cmake-3.24/Modules/CMakeFindDependencyMacro.cmake:47 (find_package):
By not providing "FindArrowAcero.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"ArrowAcero", but CMake did not find one.
Could not find a package configuration file provided by "ArrowAcero" with
any of the following names:
ArrowAceroConfig.cmake
arrowacero-config.cmake

Add the installation prefix of "ArrowAcero" to CMAKE_PREFIX_PATH or set
"ArrowAcero_DIR" to a directory containing one of the above files.  If
"ArrowAcero" provides a separate development package or SDK, be sure it has
been installed.
Additional context
is FindArrowAcero.cmake supposed to be generated?

Where did the ArrowAcero come from? There is no ArrowAceroin arrow's dependencies and features.
I run the command you provided and the result is normal.

Arrow does build successfully but when we try and build the library into our product we see the error above.

Arrow does build successfully but when we try and build the library into our product we see the error above.

How do you use it in your project? What is the error message?

I have the same problem on Linux. ArrowAcero is a dependency of ArrowDataset (ArrowDatasetConfig.cmake calls find_dependency(ArrowAcero)) but in the vcpkg installation of Arrow there is no ArrowAceroConfig.cmake nor FindArrowAcero.cmake, hence the error.
I think this is a bug in the vcpkg port of Arrow 12 and ArrowAceroConfig.cmake should be included in the port.

Yes this is indeed a problem, it is caused by the ArrowAceroConfig.cmake file not being exported, I will fix it.


Fixed tests broken by refactoring

[ ] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] Documentation added for any new functionality
[ ] Entries added to ./unreleased/ for any new functionality

Some paths were misconfigured after #2230 (or other refactoring) and a path string was hardcoded.

LGTM, but what tests were broken? Didn't we catch those in CI?

Well, maybe broken is too strong of a word, they were pointing at a hardcoded resource folder, which should have been moved with the tests originally, but wasn't. So two wrongs cancelled out, in a way.


What if I establish a relationship between two models from different Bookshelf instances?

Say you have two different Bookshelf instances.
Bookshelf client is the same: mysql.
hosts can be different.
databases are different.
May I establish a relationship between two models from different Bookshelf instances mentioned above?

The project leadership of Bookshelf recently changed. In an effort to advance the project we close all issues older than one year.
If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.
We also started an open discussion about the future of Bookshelf.js here https://github.com/bookshelf/bookshelf/issues/1600. Feel free to drop by and give us your opinion.
Let's make Bookshelf great again


Have there been any experiments on classification task?

i could find experiments about forecasting and anomaly detection in your paper.
Have there been any experiments on classification task?

Sorry, we did not perform the classification with FITS. We did not come up with a way to formulate the classification task as frequency interpolation.

If there is no further question. I will close this issue. Please feel free to reopen it.


Implement Navigation

NextJS provide navigation between pages out of that box, but we need to solve this also for react-native.

I think react-navigation is the only choice when it comes to expo-apps.
I also think it is time to use the workspaces, and have a structure like
apps/
----- web/
----- mobile/
----- shared(core) /
with web containing nextjs pages, which uses components from shared app and
mobile containing react-navigation which also uses components from shared.
what to you think?
@FilipMessa @RobinCsl

Ah, so you would like to decouple entirely the navigation and have it per platform?
I just hope we can find a satisfactory way to reuse logic, because there are some key differences (passing data as params in react-navigation and using url params in next.js?)

Yeah, but these differences are there even if we keep it all together right?

I guess you're right.
So we want to roll with react-navigation for mobile, and next.js's default navigation for web. Agreed?
So we might need some kind of wrapper to abstract these away?
I will try and build the navigation of the screens we need and see what problems I encounter.

From me it sounds like a nice way, I don't have any better idea so let's try.
BTW: I would like to also split graphql from the app as I mention here https://skypicker.slack.com/archives/CEFT2NAE8/p1544279888003100.

Yes, I saw it, it could also go into app folder,
so we have apps -> graphql, web, native, core and packages that supports the apps


Can you provide the preprocessing code for the s3dis data set? thank you very much

I want to reproduce your code to complete my graduation project study, but there are no files in the processed directory of the data set. Can you provide the preprocessing code for the s3dis data set? Thank you very much.

Hi @gyy520cyaowu thanks for your interest in our project !
All code for preprocessing, training, and evaluating on S3DIS, DALES, and KITTI-360 is available. Please refer to the README and the docs/ for getting started with this project. Also, the codebase is fairly commented 😉
PS: if you are interested in or using this project, don't forget to give our repository a ⭐, it matters to us !


Communicate with Neutron API using keystone

Currently we connect directly to Neutron API. Valid approach would be to use keystone.

In the first stage, just moving to unsecured keystone is OK. In next one, we should allow auth configuration using Kubernetes secrets.

Fixed in #14


syatem navigation bar color

Hello
is there a way to set system navigation bar color depending on theme ?

You can listen to theme mode changes and set your status bar accordingly. I believe there's a package to manage that.
Check this out in README.md
AdaptiveTheme.of(context).modeChangeNotifier.addListener(() {
  // set status bar here.
});

Thanks
I’ll close the issue for now
I’ll try the solution later to see what happen


Add bits-service

[#151325376]
/CC @idev4u

@cppforlife Addressed both your comments.
The final release can be found at https://github.com/cloudfoundry-incubator/bits-service-release/releases/tag/1.4.0.


treewide: migrate to -fno-common

Motivation for this change
GCC 10 defaults to -fno-common, a change that broke some packages. To ease the transition when migrating to GCC 10, we changed the default back in our build of GCC. This commit undoes that, bringing us closer to upstream and reducing our technical debt. (Clang, which made the same change, also cites "performance and code-size benefits"; it's unclear if this is the case for GCC.)
In an effort to reduce the potential breakage from this PR, I've made no effort to patch or upgrade packages broken by this. Instead, for any package that fails to build, I fix it by setting NIX_CFLAGS_COMPILE = "-fcommon", i.e. returning to the status quo. This brings the vast majority of packages onto the new default, and has no risk of introducing new bugs due to incorrect patches. As the rest of the world migrates towards GCC 10, most of these will probably get fixed by upstream, and we can remove the flag; for the rest, we can decide whether to write/find a patch or keep the flag indefinitely.
This PR is not ready to merge at this point. Before doing so, I'd like to try building at least these things:

[ ] The configuration.nix of the laptop I'm testing this on
[ ] Some (or all) of the configurations in release.nix
[ ] Packages listed as broken (or previously broken) in the Gentoo and Fedora issues for migrating to GCC 10.

It might also be a good idea to set up a hydra job.
Things done

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

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

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

Huh, it's weird that this causes an stdenv rebuild on darwin. It should only affect GCC.

Huh, it's weird that this causes an stdenv rebuild on darwin. It should only affect GCC.

https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html
-fcommon
In C code, this option controls the placement of global variables defined without an initializer, known as tentative definitions in the C standard. Tentative definitions are distinct from declarations of a variable with the extern keyword, which do not allocate storage.

The default is -fno-common, which specifies that the compiler places uninitialized global variables in the BSS section of the object file. This inhibits the merging of tentative definitions by the linker so you get a multiple-definition error if the same variable is accidentally defined in more than one compilation unit.

The -fcommon places uninitialized global variables in a common block. This allows the linker to resolve all tentative definitions of the same variable in different compilation units to the same object, or to a non-tentative definition. This behavior is inconsistent with C++, and on many targets implies a speed and code size penalty on global variable references. It is mainly useful to enable legacy code to link without errors.

https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html
-fcommon
In C code, this option controls the placement of global variables defined without an initializer, known as tentative definitions in the C standard. Tentative definitions are distinct from declarations of a variable with the extern keyword, which do not allocate storage.

The default is -fno-common, which specifies that the compiler places uninitialized global variables in the BSS section of the object file. This inhibits the merging of tentative definitions by the linker so you get a multiple-definition error if the same variable is accidentally defined in more than one compilation unit.

The -fcommon places uninitialized global variables in a common block. This allows the linker to resolve all tentative definitions of the same variable in different compilation units to the same object, or to a non-tentative definition. This behavior is inconsistent with C++, and on many targets implies a speed and code size penalty on global variable references. It is mainly useful to enable legacy code to link without errors.

iso_minimal now builds. I can upload to cachix if it helps anyone.

iso_minimal now builds. I can upload to cachix if it helps anyone.

Bah, there's a merge conflict, but if I try to merge in https://github.com/NixOS/nixpkgs/commit/aa8868c7cca8d30706a68a876d048968c83e1cf1 (the output of git merge-base origin/master origin/staging), the PR pulls in a bunch of unrelated commits for some reason.

Bah, there's a merge conflict, but if I try to merge in https://github.com/NixOS/nixpkgs/commit/aa8868c7cca8d30706a68a876d048968c83e1cf1 (the output of git merge-base origin/master origin/staging), the PR pulls in a bunch of unrelated commits for some reason.

There’s a conflict in squashfsTools because lz4 support recently became unconditional, and it touched related lines.

There’s a conflict in squashfsTools because lz4 support recently became unconditional, and it touched related lines.

Clang 11 is making the same change (changelog, D75056) so these changes shouldn't be restricted to GCC. I ran into this when working on aarch64-darwin which has a hydra job. It could be useful to pick through the set of new failures in the change from clang 10 to clang 11: https://hydra.nixos.org/eval/1646384?compare=1646102#tabs-now-fail.

Sorry this PR is languishing (and for all the force pushes) - I can't manage to fix the merge conflict without GitHub pulling in thousands of unrelated commits. I thought git merge xyz, where xyz is a commit appearing in both master and staging, would do the trick, but it doesn't seem to work.

Alright, a rebase worked (thanks, jtojnar in IRC)

As far as I'm aware, we're still changing the defaults of gcc and clang to keep these packages building. Not stale.

Well, nothing in this PR really moved in the last 14 months. The progress looks pretty stale to me.

Yikes, sorry - not sure I have the time to pick this up at the moment. Not sure what the best way forward is - this seems worth doing, but it's not exactly a huge priority.

From what I understand clang-11+ does default to -fno-common in fresh versions as well and nixpkgs does not change the default. I usually use it as an immediate justification for -fno-common fixes in nixpkgs ( https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+fix+fno-common+toolchain ).

Well, nothing in this PR really moved in the last 14 months. The progress looks pretty stale to me.

Progress does seem stale, and I don't intend to apply pressure. I think the change is important enough to keep the ticket open as a tracking issue, even if we don't expect any changes in the near future.

Yikes, sorry - not sure I have the time to pick this up at the moment. Not sure what the best way forward is - this seems worth doing, but it's not exactly a huge priority.

Thank you for your hard work on this! I'm just keeping the stale bot away.

From what I understand clang-11+ does default to -fno-common in fresh versions as well and nixpkgs does not change the default. I usually use it as an immediate justification for -fno-common fixes in nixpkgs ( https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+fix+fno-common+toolchain ).

For clang 11 exactly, the compiler used for darwin platforms, nixpkgs does change the default. I added this as part of #105026 hoping it'd be temporary.
https://github.com/NixOS/nixpkgs/blob/62745b65f4684a4772bd70fdfa09669a9c6af874/pkgs/development/compilers/llvm/11/clang/default.nix#L53-L64

Thank you for your hard work on this! I'm just keeping the stale bot away.

It is not going to close anything here.

To get it easier to incrementally get to the state where we can just flip the flag I'll add a list of known broken packages with /without pending fixes. In many cases they can go directly to master branch:

[ ] read-edid: https://github.com/NixOS/nixpkgs/pull/171776

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/help-disabling-fno-common-hack/19031/1

Bah, there's a merge conflict, but if I try to merge in aa8868c (the output of git merge-base origin/master origin/staging), the PR pulls in a bunch of unrelated commits for some reason.

Revising should be used

Jobset: https://hydra.nixos.org/jobset/nixpkgs/pr-110571

And we got first new failure! libipfix. TODO for this iteration:

[ ] libipfix:

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/help-disabling-fno-common-hack/19031/2

All failing packages noticed on hydra are now fixed in master or staging. I'd like to do one extra run once staging trickles down into master to check if we have any extra darwin fallout: https://github.com/NixOS/nixpkgs/pull/177171
After that we'll be ready for merge.

Failures extracted from this iteration:

[ ] lttng-ust-2.10.5 (no nice attribute name, override via vscode-extensions/python):
[ ] ocaml-ng.ocamlPackages_4_05.lablgtk:

Jobset: as x86_64-darwin is now catching up about a week of outage on Hydra, I canceled it here and put in aarch64-darwin instead (was idling right now).

I hereby declare all (~240) the knows failures to be fixed. Should be ready for staging.

@ofborg build nixosTests.gnome

Thanks.  This must've taken really lots of work.  I'm convinced it's in good enough shape for staging.  Minor remaining issues can always get fixed during staging-next.

Recent package additions that fail now:

[ ] decoder: https://github.com/NixOS/nixpkgs/pull/180820

Thank you for your efforts trofi


Can't select a project from autocomplete popup

💻 Environment
Platform: macOS
OS Version: macOS 10.14
Toggl Version: 7.4.1012
🐞 Actual behavior
Selecting a project from the autocomplete dropdown doesn't do anything
💯 Expected behavior
The project should be selected
🔨 Steps to reproduce

Type in the start of a project name
Select a project from the dropdown
It doesn't do anything :(

📦 Additional info
User report

User report

User report

User report

User report


401 Unauthorized from AWS

This just suddenly started happening without anything changing on our end. Oddly enough, we run this lib both in a staging environment and prod, but only the prod server stopped working. Both servers have the exact same configuration, running boto (2.35.1).
>>> from boto.ec2 import EC2Connection, get_region
>>> conn=EC2Connection(aws_access_key_id='KEY ID', aws_secret_access_key='KEY SECRET')
>>> conn.get_all_regions()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/boto/ec2/connection.py", line 3477, in get_all_regions
    [('item', RegionInfo)], verb='POST')
  File "/usr/local/lib/python2.7/dist-packages/boto/connection.py", line 1185, in get_list
    raise self.ResponseError(response.status, response.reason, body)
boto.exception.EC2ResponseError: EC2ResponseError: 401 Unauthorized
<?xml version="1.0" encoding="UTF-8"?>
<Response><Errors><Error>AuthFailure<Message>AWS was not able to validate the provided access credentials</Message></Error></Errors><RequestID>53deb9bb-b3f5-484c-82aa-a0cb60c2be0a</RequestID></Response>

I know I'm really late in responding to this, but can you provide some more detail? Does this issue persist or was it a problem resolved by updating Boto?

Hey Mark, thanks for the reply. I forgot I submitted this issue. It's due to time drift on the server, running an ntp update resolves the issue. Be cool if AWS gave a more helpful response, but there's no issue with the autoscale library for sure.

Thanks!


Authentication failed

I am facing the Authentication failed problem during login action is executed.
const string DEV_HOST = "<IP_ADDRESS>";
const int ASTERISK_PORT = 5038;
const string ASTERISK_HOST = "<IP_ADDRESS>";
const string ASTERISK_LOGINNAME = "admin";
const string ASTERISK_LOGINPWD = "secret";
I can login on my asterisk server by using above credential. After successful login, it lands up on dashboard. But i am not able to make a successful login through code. Where am i going wrong.
Any help would be much appreciated.

I assume you're using some Asterisk based PBX, not vanilla Asterisk. Don't assume your login details are also valid AMI login details.

Yes you are right. I am using Asterisk based PBX. So how can i get the login details of AMI? I looked into the pbx setting and found that there is manager.config for AMI details and I tried to login by using that AMI login details but getting same error. My AMI details looks something like that:
[general]
enabled = yes
port = 5038
bindaddr = <IP_ADDRESS>
displayconnects=no ;only effects 1.6+
[admin]
secret = amp111
deny=<IP_ADDRESS>/<IP_ADDRESS>
permit=<IP_ADDRESS>/<IP_ADDRESS>
read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
writetimeout = 5000

Looks like you're not permitting anything but localhost?

How can I permit for other IPs?

This issue has gone after writing
[admin]
secret = amp111
deny=<IP_ADDRESS>/<IP_ADDRESS>
permit=<IP_ADDRESS>/<IP_ADDRESS>
permit=(ANY IP)/<IP_ADDRESS>
read = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
write = system,call,log,verbose,command,agent,user,config,command,dtmf,reporting,cdr,dialplan,originate
writetimeout = 5000
and then  reload asterisk server.


fix: Amends psalm assertion syntax on Uuid::isValid() to prevent incorrect type inference

Description
The reason for this change is described in #478
Closes #478

Just realised that I should be able to remove the PHPStan suppression shipped in the original PR - I'll rebase and try it…

The previous error suppression will have to stay for now :(

I'm not sure why the workflow didn't run when you did the force push. Normally, that should have triggered a build.

I've pushed an additional test case to trigger CI. GHA was being weird for me on other repos earlier!

Thank you for contributing! 🎉


Basic Foundation & Front-End Setup

Items implemented:

foundation-rails gem - nicely packages an up-to-date build of Foundation for Sites for our use on the front end
font-awesone-rails gem - similarly makes the Font Awesome icon set easily accessible in our app.  Even provides a handy fa_icon helper to DRY up our markup!
Basic "Battle Banner" summary design for Battles#show view - gives basic details of the battle (Topic, description, author, and indicates if a winner has been chosen)
Moved Devise-related nav elements and placeholder top level navigation links (Tags#index, Battles#index, Comments#index) into an off-canvas menu.

NOTE: Usually you'll see me assert that a single Pull Request should contain a single commit.  Every rule has exceptions.  This PR, for example, contains 4 commits, as each contains a single change (adding/configuring a new gem, or adding a major interface element) that together amount to the purpose of this PR - getting the front-end of this project on its feet.

Tagging @J3RN, @trouta23, @dimitryraymondMOBI, & @supdood so they see this summary of changes (PR merge is imminent)

:+1:


Powdr2

New assembly structure containing:

machines
instructions
program

Should be recursion oriented.
Tasks:

[x] https://github.com/powdr-labs/powdr/issues/428
[x] https://github.com/powdr-labs/powdr/issues/429
[x] https://github.com/powdr-labs/powdr/issues/430
[x] https://github.com/powdr-labs/powdr/issues/431

I guess we can close this issue and open another one more specific to PIL2? Closing for now, please re-open if needed.

Nice!


[BUG] Tasks not added to .tasks after upgrade from 1.3 to 2.3

Describe the bug

I had AWS OpenSearch 1.3
Using Cloudformation I updated to 2.3
I had a lot of code that relied on GET /_tasks/{task_id} and now sth is broken after the upgrade. Tasks are created and in response to the query I am getting task_id but when I want to get details of it I am getting 404.
If I will run the .tasks/_count returned number is all the time the same 2907 which is the number probably which was there before the update (not 100% sure)
List of indexes is my cluster

green open transfers_version_3 Y0MyC6vHQbaqISI5O2zLMA 12 1 7405154 176  7.3gb   3.6gb
green open activity_version_3  hijXZSuOQxS2kGEd1OyXTw  6 1   17074   0 37.4mb  18.7mb
green open .kibana_1           smtt79uyRTeJDUlE81a2KQ  1 1       2   0   20kb    10kb
green open .tasks              vkS0Dfg7Sq2ZxhM5XIN00A  1 1    2907  18  1.1mb 589.9kb

Expected behavior
Should be able to create new tasks and receive details about them
Plugins
No

@MRabenda not all tasks store results by default. Could you share some requests that are expected to store results at your end?

An example is POST /transfers_version_3/_delete_by_query?wait_for_completion=false ....
The entire code is based on this - earlier this produced task that I was able to check. Now it is producing a task but when I am trying to get it - the response is 404.

Hello,
Observing the same behavior with an update by query task. Task is not added and does not exist after launching the update.

Response from AWS support
Q -  Is no way to store information about the completed tasks in the way that we did in the previous version of OpenSearch?

A - Due to the modification of the Tasks API, and deprecation of this “.tasks” index functionality, the long running tasks are no longer stored in “.tasks” index and _tasks API only returns the current running tasks.

Q - Whether the task that returned an error is available in the API - GET _tasks?

A - I regret to inform you that the Tasks that fail or return errors cannot be retrieved using the “GET _tasks”  API. Only the tasks that are currently running are returned as an output.

This change is so bad ... why we need tasks/jobs if we can not fetch results? Can someone from the project team explain how we should understand this change?

@chelma, @kartg could you please provide your input with thiss. Seems that index/task is not being added post upgrade to 2.3.

@MRabenda  is the domain hosted by AWS or is it on self managed cluster?

Hosted by AWS as managed service. Like I wrote in first 2 points of issue description

This looks related to https://github.com/opensearch-project/OpenSearch/issues/5376 which was fixed in open-source with https://github.com/opensearch-project/OpenSearch/pull/5412.

Reading #5412 it looks like this was fixed in 2.4.
@MRabenda Could you try the OSS 2.4 version to confirm? And if it works as you expect, we can close this. I don't have an ETA for Amazon Managed OpenSearch having 2.4 available, but maybe Amazon support will be able to give you a date.

I contacted AWS about that - they said that they still do not have an ETA. When I will upgrade to 2.4 (as far as I understand this has to be 2.4.1) I will let you know about this issue status. Thanks for your entire support.

Closing this issue since we have fixed it in OpenSource OpenSearch 2.4. The issue will be fixed on AWS OpenSearch 2.4 end. Feel free to open the issue if it is still present in managed service 2.4.


upgrade to clap 3 for argument parsing

May not be idiomatic as I just followed the errors until the compiler was happy.

bors r+


[BUG]: Need to update sotopia episode data

Description of the bug
The serialization output has rewards in the jsonlines. However, in the released huggingface dataset, it does not have reward attributes.
Steps To Reproduce
https://huggingface.co/datasets/cmu-lti/sotopia/tree/main No rewards
Additional Information
No response

Also, I think we can serialize all of our sotopia-pi data from the database use this part of serialization code. @ruiyiw @sharonwx54

will fix it soon.

@sharonwx54  I think I am pointing to sotopia not sotopia-pi data. Both needs to be updated.

@sharonwx54 I think I am pointing to sotopia not sotopia-pi data. Both needs to be updated.

Yes, I did upload latest data with rewards for both. They are in separate PR under sotopia and sotopia-pi.

nice~


Unrecognized field "subject"

Describe the bug
We are seeing some strange behaviour when using the latest docker image and creating a custom role for the schema registry
This is what we are seeing on error:
Caused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "subject" (class com.purbon.kafka.topology.model.users.Other), not marked as ignorable (6 known properties: "transactionId", "idempotence", "principal", "metadata", "group", "topic"])

This is our custom role:
  - name: "schemaRegistryPrefix"
    acls:
      - resourceType: "Subject"
        resourceName: "{{subject}}"
        patternType: "PREFIXED"
        host: "*"
        role: "ResourceOwner"

This is our topology file:
---
context: ""
source: ""
projects:
  - name: ""
    schemaRegistryPrefix:
      - principal: "User:svc-account"
        subject: "test.subject."

To Reproduce
Steps to reproduce the behavior:

Create the files above
Using the latest docker image, create the custom role binding
See error

Expected behavior
Creation of the custom role binding
Screenshots
n/a
Runtime (please complete the following information):
n/a
Additional context
Add any other context about the problem here.

Problem is identified here by missing subject alias in this context https://github.com/kafka-ops/julie/blob/master/src/main/java/com/purbon/kafka/topology/model/users/Other.java#L24-L32
related to #401

I am also keen to get this solution both for the schema/subject and the connectors. Also, that would require RBAC scope to be extended to the schema-registry and the connector cluster.

Hi @shahriar52, this has a simple solution, it is required to extend the properties included in the referenced Other object. Contributions are very much welcome!, otherwise I will push a fix as soon as I collect a couple of hours available ;-)

Thanks, @shahriar52 and @DanielMabbett this would be fixed with the merge of #406. This future will be included in the next release.


Fix submission lost changes after save

References

(Possibly) Fixes #2940

Description
This embeds the item in the PATCH request when saving the submission. This ensures cached item and workspace item don't go out of sync. It solved an issue I had with one particular DSpace on 7.6 where the metadata seemed to disappear when you saved the submission form, but reappeared after a refresh.
I can't reproduce #2940, but I suspect it may have a similar cause
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

I can confirm that this change seemed to stabilise patch ops and uploads in item submission, though I didn't catch the issue @tdonohue brought up.. that could be making all our patch ops unnecessarily large I guess, or even invalid if they don't apply to items?

Manually ported to 7.x in #3053


Extend '-Wmaybe-uninitialized' suppression to GCC.

There's a suppression in place for MSVC. Extend it to GCC which also complains, while excluding clang which doesn't.
In the future it may make sense to pre-define 'compiler tests' up front, so there's only one definition of them.

If it was my code I would probably use value-initialization of these structures instead, and do away with the suppressions just for simplicity. Hard to believe this would have any major performance impact.
ALIGNED( 64 ) __m256 bestLBox{}, bestRBox{};            // 64 bytes


2.2.5 lib

How to disable this errors in windows XP?

The procedure entry point strtok_s could not be located in the dynamic link library msvcrt.dll

The procedure entry point InitOnceExecuteOnce could not be located in the dynamic link library kernel32.dll

ref: http://www.videolan.org/developers/vlc/doc/doxygen/html/group__libvlc__core.html
SEM_FAILCRITICALERRORS

AHH LOL... I will leave it, hope to help someone.
`       [DllImport("kernel32.dll")]
static extern ErrorModes SetErrorMode(ErrorModes uMode);
[Flags]
public enum ErrorModes : uint
{
SYSTEM_DEFAULT = 0x0,
SEM_FAILCRITICALERRORS = 0x0001,
SEM_NOALIGNMENTFAULTEXCEPT = 0x0004,
SEM_NOGPFAULTERRORBOX = 0x0002,
SEM_NOOPENFILEERRORBOX = 0x8000
}
public Form1()
{
SetErrorMode(ErrorModes.SEM_FAILCRITICALERRORS);
InitializeComponent();
}`


[FEATURE REQUEST] Update RHEL images in CI pipelines and docs

Is your feature request related to a problem? Please describe.
Until resolving #1355 Epiphany is limited to support RHEL images on Azure only with versions up to 7.7.
So CI pipelines use quite old images (RedHat:RHEL:7-RAW:7.7.2019090418).
There are also references to old images in docs (in OS_PATCHING.md and CLUSTER.MD).
Describe the solution you'd like

Update CI pipelines to use RHEL 7.9
Update docs to not contain any references to RHEL 7.7 (update to 7.9)

Describe alternatives you've considered
n/a
Additional context
This will allow to resolve #1776.
NOTE: Switching to RedHat:RHEL:7lvm-gen2:7.9.2020111205 (or newer) requires OS disk in size of 64 GB or you will get such error:
Message="The specified disk size 32 GB is smaller than the size of the corresponding disk in the VM image: 64 GB. This is not allowed. Please choose equal or greater size or do not specify an explicit size." Target="osDisk.diskSizeGB".
Example query to get images for RHEL 7.9:
az vm image list --publisher RedHat --offer RHEL --all --location westeurope --output table | grep '7\.9' | grep -v byos

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

Does this error regarding disk size ( 32 instead of 64 ) appear when disk size is set to 64 and root partition shows still 32?
If we change our docs & pipelines at first - we have to immediately fix the disk size issue because deployments will fail, am I right?

The error will occur when you set for OS disk less than 64GB. Currently the Epiphany default is disk_size_gb: 32 so this default should be changed in the scope of this task. However, it's possible to overwrite the default - but this has to be done for each component, which is not convenient and error prone.

CI pipelines updated by @przemyslavic, I only updated documentation and checked if RHEL version is the latest one - yes it it.
RHEL:7-LVM:7.9.2020111202, (kernel 3.10.0-1160.el7.x86_64) - used.
PR for the task:

Updated also AWS RHEL image to RHEL-7.9_HVM-20210208-x86_64-0-Hourly2-GP2


Downscale result inconsistent with PIL?

Given a simple input image:

When comparing downscaling bicubically by a factor of 8 (from 128 pix to 16), results are inconsistent with PIL and do not look too good:
from torchvision import transforms
import resize_right as rr

x = transforms.ToTensor()(pil_img);  # pil_img is a PIL.Image loading the attached circle image
pil_resize = transforms.ToTensor()(pil_img.resize((16,16), Image.Resampling.BICUBIC))
pt_resize = transforms.Resize(size=16, interpolation=transforms.InterpolationMode.BICUBIC,antialias=True)(x).clip(0,1)
rr_resize = rr.resize(x, scale_factors=0.125, interp_method=rr.interp_methods.cubic, antialiasing=False).clip(0,1)

This results with the following resized images:

As you can see, the output of resize-right has artifacts near the corners, where it shouldn't have.

Hi Shai! Thanks for this!

Can't reproduce. I think the attached image is processed when attached to the text so not identical to original file. Anyway, this is what I get directly from the URL
response = requests.get('https://user-images.githubusercontent.com/1818351/177781442-edbaee21-b9d2-4f45-9a3e-8b68b4065c17.png') img = Image.open(BytesIO(response.content)) x = transforms.ToTensor()(img).squeeze(0) rr_resize = rr.resize(x, scale_factors=0.125, interp_method=rr.interp_methods.cubic, antialiasing=False) plt.imshow(rr_resize)

Nevertheless, I believe the reason for what you see is the fact that rr defaults to zero padding while the others default to 'reflect'. However, rr supports all padding methods of Torch/NumPy so you can rr.resize(x, ..., pad_mode='constant').
One other experiment is to take 1-x: so the background value is zero which is the same as the padding.
Also I noticed that you used antialaiasing in pt but set False in rr. Not sure why.
That said, with antialiasing off and such drastic scale factor, I think padding should not influence. I am not able to reproduce anything that looks like it, even with my own circle.  Are you sure this is actually with antialiasing=False? It looks like a legit result for antialiasing=True.
There shouldn't necessarily be consistency with PIL.

@assafshocher Thanks for the reply.
Here's a code that reproduce the results:
import numpy as np
from PIL import Image
from ResizeRight import resize_right as rr
import matplotlib.pyplot as plt
from torchvision import transforms

# generate the circle image
[x, y] = np.meshgrid(np.linspace(-1, 1, 128),np.linspace(-1, 1, 128))
x = np.exp( -((x ** 2) + (y ** 2) - 1)**2 / 0.0025 )
pil_img = Image.fromarray((255 - x*255).astype(np.uint8))

# convert to tensor
x = transforms.ToTensor()(pil_img)

# compare resizing methods
r = [(transforms.ToTensor()(pil_img.resize((16,16), Image.Resampling.BICUBIC)), 'pil_resize'),
     (transforms.Resize(size=16, interpolation=transforms.InterpolationMode.BICUBIC,antialias=True)(x), 'pt_resize'),
     (rr.resize(x, out_shape=(16, 16), interp_method=rr.interp_methods.cubic, antialiasing=True), 'rr_resize')]

# plot
fig, ax = plt.subplots(1,3)
[(a_.imshow(r_[0].clip(0,1).numpy()[0]), a_.set_title(r_[1]))  for a_, r_ in zip(ax.flat, r)]
[(a_.axis('off'), a_.grid(None)) for a_ in ax.flat]
plt.show()

It does seem to be related to the padding.

Thanks!
Okay. So it seems that in your first example, antilaliasing was actually on.
The difference then is the default padding I mentioned before.
Here are the different variants (beginning of the code is identical to yours):
'''
def compare(x):
# compare resizing methods
r = [(rr.resize(x, out_shape=(16, 16), interp_method=rr.interp_methods.cubic, antialiasing=True), 'antialiasing=True, \npad_mode="constant"'),
(rr.resize(x, out_shape=(16, 16), interp_method=rr.interp_methods.cubic, antialiasing=False), 'antialiasing=False, \npad_mode="constant"'),
(rr.resize(x, out_shape=(16, 16), interp_method=rr.interp_methods.cubic, antialiasing=True, pad_mode='replicate'), 'antialiasing=True, \npad_mode="replicate"'),
(transforms.Resize(size=16, interpolation=transforms.InterpolationMode.BICUBIC,antialias=True)(x), 'pt_resize_aa_on'),
(transforms.Resize(size=16, interpolation=transforms.InterpolationMode.BICUBIC,antialias=False)(x), 'pt_resize_aa_off')]
# plot
fig, ax = plt.subplots(1,5, figsize=(17,7))
[(a_.imshow(r_[0].clip(0,1).numpy()[0]), a_.set_title(r_[1]))  for a_, r_ in zip(ax.flat, r)]
[(a_.axis('off'), a_.grid(None)) for a_ in ax.flat]
plt.show(fig)

compare(x)
compare(1-x)
'''

You can see that the result you got is because of padding. However, without AA, the padding has no effect.
For the 1-x, the zero padding and replicate padding are actually the same, this is why the leftmost result has no padding artifacts.
At the time I considered having default pad_mode='replicate' but decided against it as the natural signal processing common is zero-padding.
Thanks for this!

@assafshocher Thanks. I think this can close the issue.


Extract mime-types-redirector to a dedicated repo/gem

Directory is extracted to
https://github.com/ManageIQ/mime-types-redirector , and will be
published as mime-types gem on https://rubygems.manageiq.org

@NickLaMuro @bdunne Please review.
@bdunne when you have a chance can you build that gem and push it to rubygems.manageiq.org?  Then this PR should go green.

@NickLaMuro @bdunne Please review.
@bdunne when you have a chance can you build that gem and push it to rubygems.manageiq.org?  Then this PR should go green.


HHH-15135 Respect precision in temporal version types when generating timestamps

https://hibernate.atlassian.net/browse/HHH-15135

:+1:

Any chance or plan to backport this to version 5.x too?
We found some related issues when migrating to Java17(Spring boot 2.x, Hibernate 5.x)

No plans to backport, sorry.


v35 release

Integration branch for v35.

[x] Tracks main
[x] Publishes to @next release channel
[ ] All component deprecation / breaking changes are merged into this branch

Closing this PR because breaking changes should now be merged into next-major instead of next/v35.0.0 https://github.com/primer/react/pull/1910


Removed mkhalusova as a default reviewer

Removed @MKhalusova as a default reviewer

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Remove any unneeded videoconferencing code

Once we're sure that code and data collection responsibilities are handed off to the Zoom and BlueJeans service teams, we should remove any files related to these processes and update the README and configuration file. This does not include the Canvas Zoom LTI placement code, which will continue to be included and maintained by T&L.
Issues related to these processes should also be labeled wontfix and closed.

This was partially resolved by PR #131. We're working/talking about the rest.

I think with PRs #131, #136, and #140, this is fully finished.


Do not leave account without admin user

If there is an attempt to revoke admin privileges from the last admin in the account: reject the action.

Fixed