Update AWS-CREDENTIALS.md

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Updated AWS-CREDENTIALS.md to address https://github.com/rusoto/rusoto/issues/1597

Thanks for the PR, just have the one change to make and it looks good to go. 😄

Thanks! This is ready to merge once the builds pass. 😁


Add support for https://github.com/jscs-dev/node-jscs

https://github.com/jscs-dev/node-jscs

Merged with ESLint


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter sbfspot for common errors and appropiate suggestions to keep this adapter up to date.
This check is based on the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.sbfspot
   -
:thumbsup: No errors found
WARNINGS:

[ ] :eyes: [W508] attribute "xs" for staticImage should specify a value of "12" at admin/jsonConfig.json/items/tab-main/icontest

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Mon, 09 Dec 2024 12:42:17 GMT based on commit 89ce361c16c13442c64fd64685bd84c8e6added2
ioBroker.repochecker 3.2.2

@iobroker-bot recheck


'package:flutter/src/widgets/navigator.dart': Failed assertion: line 1748 pos 12: '!_debugLocked':  is not true.

'package:flutter/src/widgets/navigator.dart': Failed assertion: line 1748 pos 12: '!_debugLocked':
is not true.

Getting issue while routing from one screen to another.

I have meeted same problem, and find this error  is actually the second exception, first exception is
 Failed assertion: line 175 pos 12: **'!_transitionCompleter.isCompleted**

the first exception will cause the second exception.
and my fault is calling Navigator.push() in OnTap(){} closure, when I call it in onPress(){} closure then the problem disappear.  it's very strange! finally, I use Navigator.pushNamed() to jump another screen, and I haven't meet this error again.

@sovoereign Do you encounter the issue using current flutter stable or master?

════════ Exception caught by widgets library════════
The following assertion was thrown building Panel(dirty):
setState() or markNeedsBuild() called during build.
This Overlay widget cannot be marked as needing to build because the framework is already in the process of building widgets.  A widget can be marked as needing to be built during the build phase only if one of its ancestors is currently building. This exception is allowed because the framework builds parent widgets before children, which means a dirty descendant will always be built. Otherwise, the framework might not visit this widget during this build phase.
The widget on which setState() or markNeedsBuild() was called was: Overlay-[LabeledGlobalKey#781f4]
state: OverlayState#219d4(entries: [OverlayEntry#0e838(opaque: false; maintainState: false), OverlayEntry#c325c(opaque: false; maintainState: true), OverlayEntry#3194a(opaque: false; maintainState: false), OverlayEntry#94ae7(opaque: false; maintainState: true)])
The widget which was currently being built when the offending call was made was: Panel
dirty
User-created ancestor of the error-causing widget was:
Scaffold file:///C:/Users/Reza%20Abdollahi/Desktop/gui/ajans_app/lib/pages/Panel.dart:9:17
When the exception was thrown, this was the stack:
#0      Element.markNeedsBuild. (package:flutter/src/widgets/framework.dart:3687:11)
#1      Element.markNeedsBuild (package:flutter/src/widgets/framework.dart:3702:6)
#2      State.setState (package:flutter/src/widgets/framework.dart:1161:14)
#3      OverlayState.insertAll (package:flutter/src/widgets/overlay.dart:346:5)
#4      OverlayRoute.install (package:flutter/src/widgets/routes.dart:43:24)
...
════════ (2) Exception caught by widgets library ════════
'package:flutter/src/widgets/navigator.dart': Failed assertion: line 2247 pos 12: '!_debugLocked': is not true.
User-created ancestor of the error-causing widget was:
MaterialApp file:///C:/Users/Reza%20Abdollahi/Desktop/gui/ajans_app/lib/pages/Panel.dart:8:12
═════════════════════════════════════════

i have same error.
Flutter v1.9.1+hotfix.2
Dart 2.5.0

I have met same problem, and find this error is actually the second exception, first exception is
 Failed assertion: line 175 pos 12: **'!_transitionCompleter.isCompleted**

the first exception will cause the second exception.
and my fault is calling Navigator.push() in OnTap(){} closure, when I call it in onPress(){} closure then the problem disappear. it's very strange! finally, I use Navigator.pushNamed() to jump another screen, and I haven't meet this error again.

Worked too, Tks. @sunxianglei

Unhandled Exception: 'package:flutter/src/widgets/navigator.dart': Failed assertion: line 1930 pos 12: '!_debugLocked': is not true.

https://github.com/flutter/flutter/issues/16602#issuecomment-407916243

in my case, it was empty default tab controller causing this issue.

In my case, I set route with a screen then try to call the same screen using navigator... without pushnamed somewhere else and this error came up. If you're using routes for a particular screen then always use routes for that screen. It was a clumsy mistake on my part.

The same thing started happening to me after I updated Flutter and Dart (after a long time without updating).
In my case I realized that I had another exception before this error appeared.
setState() or markNeedsBuild called during build

I fixed it by using a PostFrameCallback
          WidgetsBinding.instance.addPostFrameCallback((_) {
            Navigator.of(context)
                .pushReplacementNamed(MyScreen.routeName);
          });

Hope this helps someone.
Flutter 1.17.4
Tools • Dart 2.8.4

The same thing started happening to me after I updated Flutter and Dart (after a long time without updating).
In my case I realized that I had another exception before this error appeared.
setState() or markNeedsBuild called during build

I fixed it by using a PostFrameCallback
          WidgetsBinding.instance.addPostFrameCallback((_) {
            Navigator.of(context)
                .pushReplacementNamed(MyScreen.routeName);
          });

Hope this helps someone.
Flutter 1.17.4
Tools • Dart 2.8.4

THANKS @toritroniks !!!

The same thing started happening to me after I updated Flutter and Dart (after a long time without updating).
In my case I realized that I had another exception before this error appeared.
setState() or markNeedsBuild called during build

I fixed it by using a PostFrameCallback
          WidgetsBinding.instance.addPostFrameCallback((_) {
            Navigator.of(context)
                .pushReplacementNamed(MyScreen.routeName);
          });

Hope this helps someone.
Flutter 1.17.4
Tools • Dart 2.8.4

Thanks a lot, been trying to figure this out for a while.

The same thing started happening to me after I updated Flutter and Dart (after a long time without updating).
In my case I realized that I had another exception before this error appeared.
setState() or markNeedsBuild called during build

I fixed it by using a PostFrameCallback
          WidgetsBinding.instance.addPostFrameCallback((_) {
            Navigator.of(context)
                .pushReplacementNamed(MyScreen.routeName);
          });

Hope this helps someone.
Flutter 1.17.4
Tools • Dart 2.8.4

THANKS @toritroniks !!!

It's not working if I use:-
WidgetsBinding.instance.addPostFrameCallback((_) {
Navigator.pop(context);
});
Can you please suggest to me, how to fix this issue.

The same thing started happening to me after I updated Flutter and Dart (after a long time without updating).
In my case I realized that I had another exception before this error appeared.
setState() or markNeedsBuild called during build

I fixed it by using a PostFrameCallback
          WidgetsBinding.instance.addPostFrameCallback((_) {
            Navigator.of(context)
                .pushReplacementNamed(MyScreen.routeName);
          });

Hope this helps someone.
Flutter 1.17.4
Tools • Dart 2.8.4

Lifetime saver

Hi @sovoereign
are you still experiencing the issue with the latest stable (or above)?
if so could you please provide
your updated flutter doctor -v,
your flutter run --verbose
and a minimal reproducible code sample.
Thank you

The same thing started happening to me after I updated Flutter and Dart (after a long time without updating).
In my case I realized that I had another exception before this error appeared.
setState() or markNeedsBuild called during build

I fixed it by using a PostFrameCallback
          WidgetsBinding.instance.addPostFrameCallback((_) {
            Navigator.of(context)
                .pushReplacementNamed(MyScreen.routeName);
          });

Hope this helps someone.
Flutter 1.17.4
Tools • Dart 2.8.4

THANKS @toritroniks !!!

It's not working if I use:-
WidgetsBinding.instance.addPostFrameCallback((_) {
Navigator.pop(context);
});
Can you please suggest to me, how to fix this issue.

I would also like to know the answer to this question - the solution for me did not work for .pop()

Was getting something similar, the fix for me was to use await before Navigator:
if (response.statusCode == 200) {
await Navigator.pushNamedAndRemoveUntil(context, '/home', (_) => false); ...
            if(dialogOpen) {
              Navigator.of(context).pop();
            }

This usually arises if you do not put the Navigator function inside (){}. I faced something like it and I simply added my Navigator.push()...  inside (){}.
And the error resolved.

Hi all,
There are  some cases

You are changing the state of current widget and redirecting to other screen without completing build
You are redirecting to same route same route
You are calling setState{()} method in build method of widget
You redirecting to other screen without closing dialog properly
In my case I was push the screen in init state method so its have not time to build

@override
void initState() {
super.initState();
_con.initPlatFormChannel();
Future.delayed(Duration.zero, () {
_con.buildList(context: context);
});
/* if (userRepo.currentUser.value.apiToken != null) {
Navigator.of(context).pushReplacementNamed('/Pages', arguments: 2);
}*/
}
like this than i have comment the code

I change flutter version to v1.20.3 to fixed this

setState() or markNeedsBuild() called during build.

i am also facing the sam issue
package:flutter/src/widgets/navigator.dart': Failed assertion: line 3352 pos 12: '!_debugLocked': is not true.


Create home page according to mockups

Adds icons and buttons according to mockups

Maybe this should be a separate issue, but the "I need printing/I can print" text doesn't scale well when changing the zoom level

The responsiveness of this page will need to be addressed after this weeks deadline but i will go ahead and merge. I added your bug @Jasper-Nelligan to the milestone 2 project.


Glowing Chorus Fruit persists in death

Minecraft version & Mod Version: MC 1.12, Cyclic 1.7.9
Single player or Server: Singleplayer
The flying effect from the glowing chorus fruit persists in death, potentially trapping you in hours of creative flight.
Also, there is a small naming inconsistency: It's the "Corrupted Chorus" but the "Glowing Chorus Fruit".

Youre right on both counts

It does persist flying through death.  But this is working as intended, as long as the timer still expires and removes flying (timer in top right)
So my steps were
-eat in survival, get the flying timer

kill self many times
still flying, timer still works
wait until it expires. flying goes off as normal.

Is this the same thing you notice.

If the timer runs out and its still flying, that is a bug, but i didnt see that happen

Oh no then it's not a bug.
I was talking about hours because I stacked up ~70 minutes of flight in my testworld and thought it could be an issue in survival if people used it as food or just tried to see how high it would go. Mostly due to the slower block breaking speed. I just now found out that you can sneak to get around that, so I don't see an issue anymore. It's just unexpected.


Fix impress instance shutting down on metalog reload

Landed in https://github.com/metarhia/impress/commit/5d713d08c6525efb11b9065ef6d95673b48de399


Allow custom connection_timeout to LogEntries handler

It would be great to set the connection_timeout configuration from parameters instead of getting it from php.ini configuration

I think this applies to most handlers doing network stuff really.. maybe we could think of a global solution to this.

I am currently experiencing this issue, with logEntries in particular.
I try to log inside a long-running Console script. Everything works nicely until i get a next long-running request to a 3rd party.
After that script crashes with
exception 'RuntimeException' with message 'End-of-file reached, probably we got disconnected (sent 0 of 2128)' in /var/app/current/vendor/monolog/monolog/src/Monolog/Handler/SocketHandler.php:281
timelapse is the following
[2016-04-06 11:36:01] production.INFO: got ...stripped for security....
[2016-04-06 11:37:54] production.ERROR: exception 'RuntimeException' with message 'End-of-file reached, probably we got disconnected (sent 0 of 2128)' in /var/app/current/vendor/monolog/monolog/src/Monolog/Handler/SocketHandler.php:281

this happens with the (already) increased default_socket_timeout=6000
Can someone advise me the steps to fix it?

Maybe I am missing the point of this issue, but one can use setConnectionTimeout() for this, right?

Yeah I think I'm gonna close this. Doesn't seem really worth having global configuration (at least not more than php.ini stuff) for this. Can be done at the handler level.


get pixel size from wgpu

Objective

Rather than maintain a big match statement get the info from wgpu instead. wgpu already maintains a list of this info https://docs.rs/wgpu-types/0.14.0/src/wgpu_types/lib.rs.html#2359
remove PixelInfo and just use the block_size. For some formats there isn't a correct type_size like for rg11b10Float, which uses 11bits for red and green and 10bits for blue. There wasn't any uses of pixel_info() in bevy, only calls to pixel_size().

Breaking Changes
TextureFormatPixelInfo::pixel_info has been removed. PixelInfo::components can be gotten from texture_format.describe().components. PixelInfo::type_size can be gotten from texture_format.describe().block_size/ texture_format.describe().components. But note this can yield incorrect results for some texture types like Rg11b10Float
Notes

We could could potentially remove the TextureFormatPixelInfo and just use block_size directly. This would require converting though from a u8 to a usize in most usages.

I think block_size =! type_size, so need to investigate more on what the equivalence is.

So there's one mismatch and that is on Depth24Plus. The size on that one before this PR is 3 and after this PR is 4. There is a FIXME on that line, so I'm inclined to trust wgpu on this one. Ideally we'd test it somehow, but I'm not sure how at the moment.

I now see there's an old PR that tried to do something similar. https://github.com/bevyengine/bevy/pull/4124. It seems like there's some issues around compressed textures that this PR might not be dealing with correctly.

I now see there's an old PR that tried to do something similar. #4124. It seems like there's some issues around compressed textures that this PR might not be dealing with correctly.

I knew I’d seen a PR for this before.

Closing now that #6820 is getting merged. We can add the extra step in a new PR.


 Driver aufs failed to remove root filesystem ...
while [ 1 ] ; do
time docker run --rm -t ubuntu /bin/echo 1
done

can reproduce on latest

Also see #9665, which seems to be related.

This issue seems to be more severe when container run times are shorter. Running 32 containers with a 1s mean run time and I see the error for almost every container, if the mean run time is 75s it is a rare occurence.
@rakeshcusat mentioned that a related issue was solved when using 3.19.0-25-generic - has anyone found this to be the case?
# uname -a
Linux ip-10-130-12-223 3.13.0-68-generic #111-Ubuntu SMP Fri Nov 6 18:17:06 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

docker -D version && docker -D info
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:12:04 UTC 2015
 OS/Arch:      linux/amd64
Containers: 41
Images: 21
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 103
 Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-68-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 32
Total Memory: 58.97 GiB
WARNING: No swap limit support

For me upgrading to kernel 3.19.0-25-generic appears to have solved the problem.

I'm using kernel 3.19.0-39-generic and the bug is still there for me.
Kernel Version: 3.19.0-39-generic
Operating System: Ubuntu 14.04.3 LTS

Reproduced again, today.
I'm running 2 containers (a postgres and an nginx) not linked.
Docker daemon failed with a stack overflow when I tried launching
docker run -it --link postgres --rm postgres:9.4 sh -c 'exec psql -h "$POSTGRES_PORT_5432_TCP_ADDR" -U postgres'
$ docker ps -a
CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                                      NAMES
0019145e8a8d        postgres:9.4        "/docker-entrypoint.s"   15 minutes ago      Dead
ded20ccb105c        nginx-shepard       "nginx -g 'daemon off"   13 hours ago        Up 15 minutes       <IP_ADDRESS>:80->80/tcp, <IP_ADDRESS>:443->443/tcp   nginx
f6447948a433        postgres:9.4        "/docker-entrypoint.s"   2 days ago          Up 15 minutes       <IP_ADDRESS>:5432->5432/tcp

$ docker info
Containers: 3
Images: 37
Server Version: 1.9.1
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 43
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-39-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 8
Total Memory: 31.43 GiB
Name: shepard
ID: YAWF:OY7V:IGZ5:GGI4:3RYT:2K3W:UU3N:ZKKH:BFST:S6PF:YCYU:UAYO
Username: zfil
Registry: https://index.docker.io/v1/

docker.log.zip
After that it is impossible to remove the container:
Error response from daemon: Driver aufs failed to remove root filesystem 0019145e8a8dd551c1da0e5fcce49d63fab3f32301db763f0598902d6b739870: rename /var/lib/docker/aufs/mnt/0019145e8a8dd551c1da0e5fcce49d63fab3f32301db763f0598902d6b739870 /var/lib/docker/aufs/mnt/0019145e8a8dd551c1da0e5fcce49d63fab3f32301db763f0598902d6b739870-removing: device or resource busy
Error: failed to remove containers: [0019145e8a8d]

Got again the error after a machine reboot (kernel version is now 3.19.0-42-generic).
2 containers are configured to restart automatically, both failed in the daemon log same problem stuck in an infinite loop while trying to configure cgroups.
Rebooting the machine fixes the issue.
From what I see I don't think it related to auf actually, looks more a racing issue in the native driver cgroup setup.

ping @WeiZhang555 should this be fixed by https://github.com/docker/docker/pull/20848 as well?

i cannot reproduce it anymore:
$ docker info
Containers: 16
 Running: 0
 Paused: 0
 Stopped: 16
Images: 106
Server Version: 1.11.2
Storage Driver: overlay
 Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null host bridge
Kernel Version: 4.7.4-towo.1-siduction-amd64
Operating System: Debian GNU/Linux stretch/sid
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.692 GiB
Name:
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/

$ docker version
Client:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.6.3
 Git commit:   b9f10c9
 Built:        Wed, 20 Jul 2016 16:34:52 -0700
 OS/Arch:      linux/amd64

Server:
 Version:      1.11.2
 API version:  1.23
 Go version:   go1.6.3
 Git commit:   b9f10c9
 Built:        Wed, 20 Jul 2016 16:34:52 -0700
 OS/Arch:      linux/amd64

@ekle thanks for update!


knownArch in gb/importer/pkg.go misses s390x

Go in Ubuntu 16.04 has a patch enabling support for s390x, but gb doesn't realize that it shouldn't compile files called things like asm_s390x.s.

I'll do a 0.4.1 release soon to pick up these small improvements.
On Tue, Mar 15, 2016 at 12:30 PM, Michael Hudson-Doyle <
<EMAIL_ADDRESS>wrote:

Go in Ubuntu 16.04 has a patch enabling support for s390x, but gb doesn't
realize that it shouldn't compile files called things like asm_s390x.s.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/constabulary/gb/issues/580


Playing around with generics and options

In playing around with the ergonomics of the current API and looking at our feature requests, I thought it would be a good pattern to break our second argument into an options object. We have a chance to break since we're going 5.0. Here's a first pass on what it might look like.
collectionChanges(ref) (default all events, includeMetadata true)
collectionChanges(ref, { events: ['added'] })
collectionChanges(ref, { events: ['added'], snapshotListenOptions: { includeMetadata: false } })
Also I've typed the idField option a little better, given our recent generics work.
collectionData(ref) => Observable<DocumentData[]>
collectionData(ref, { idField: 'id' }) => Observable<DocumentData[]>
collectionData<Foo>(ref, { idField: 'id' }) => Observable<Foo[]> with typescript erroring if Foo doesn't contain an id: string field.
I don't think I could force it to be DocumentData & { id: string } (like we do in AngularFire [but some folk don't like]) in the case that they don't explicitly pass a generic, unless we hurt the DevExp with something like collectionData<Foo, 'id'>(ref, { idField: 'id' }), which I'd rather not do. This would also forbid us from being flexible with options and adding something like collectionData<Foo>(ref, { idField: 'id', referenceField: 'ref', metadataField: 'meta' }), etc. which have been requested.
WDYTT? If you're both amenable, I'll draft it up for the other functions too.

Sounds cool! Leaving the API open for more options (maybe an optional custom snapToData function so people could add in whatever metadata they want?) would be nice, and getting some extra type enforcement is always a plus

@davideast – any chance of getting something like this in the next (breaking) version, and available in https://github.com/angular/angularfire/pull/3402? This would resolve the "double updates" issue.
I'm happy to contribute a PR, with some guidance.

@jits If you'd like to create an proposal first and open it as an issue for discussion I would love to review it with you. I'm very much in favor!

@davideast – sounds good! Will do, in the next couple of days.

@davideast – https://github.com/FirebaseExtended/rxfire/issues/84 🎉


Veeam Backu V12 XML: Structural error in xml file, 2 open items. -- JSON: Das zurückgelieferte JSON entspricht nicht der erwarteten Struktur (Invalid JSON.). (Code: PE231)

I just upgraded to V12 ov Veeam B&R and got this error
XML: Structural error in xml file, 2 open items. -- JSON: Das zurückgelieferte JSON entspricht nicht der erwarteten Struktur (Invalid JSON.). (Code: PE231)
Probe Server and Veeam Server are different Servers. Console on PRTG Server is also updated to V12.
Script opened directly in Powershell on PRTG Server runs fine
Successful Backups      : 1
Warning Backups         : 0
Failes Backups          : 0
Failed Backups          : 0
Running Backups         : 0
Total Backup Transfer   : 20
Total Backup Read       : 550
Warning BackupCopys     : 0
Failes BackupCopys      : 0
Failed BackupCopys      : 0
Running BackupCopys     : 0
Idle BackupCopys        : 1
Successful Replications : 0
Warning Replications    : 0
Failes Replications     : 0
Failed Replications     : 0
Running Replications    : 0
Seccessful Endpoints    : 0
Warning Endpoints       : 0
Failes Endpoints        : 0
Running Endpoints       : 0

Successful-Backups
1
1
1

Warning-Backups
0
1
1
0
1

Failes-Backups
0
1
1
0
1

Failed-Backups
0
1
1
0
1

Running-Backups
0
1
1

TotalBackupRead
550
Custom
GB
1
1

TotalBackupTransfer
20
Custom
GB
1
1

Successful-BackupCopys
1
1
1

Warning-BackupCopys
0
1
1
0
1

Failes-BackupCopys
0
1
1
0
1

Failed-BackupCopys
0
1
1
0
1

Running-BackupCopys
0
1
1

Idle-BackupCopys
1
1
1

Successful-Replications
0
1
1

Warning-Replications
0
1
1
0
1

Failes-Replications
0
1
1
0
1

Failed-Replications
0
1
1
0
1

Running-Replications
0
1
1

Successful-Endpoints
0
1
1

Warning-Endpoints
0
1
1
0
1

Failes-Endpoints
0
1
1
0
1

Running-Endpoints
0
1
1

REPO - Default Backup Repository
9
Percent
1
1
20
10
1

REPO - XXXXXXXXXXXXXX
79
Percent
1
1
20
10
1

XXXXXXXXXXXl>
74
Percent
1
1
20
10
1

PS C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML>
Im am using PRTG-VeeamBRStats-v3.ps1
I have some identical Setups with V11 working fine.
By the way, is there a scitpt for Monitoring Veeam 365 Backup ?
Any idea ?
best regards
Jörg

Hi @joergbruse ,
at first, ist good to know that the script works with v12 GA. I have only verified it with RC Builds so far.

Probe Server and Veeam Server are different Servers. Console on PRTG Server is also updated to V12.
Script opened directly in Powershell on PRTG Server runs fine

Is the Probe Server another server or is the PRTG Master also the Probe for this sensor?
Please start and connect the Veeam B&R Console on all of the used PRTG Probes to make sure latest updates of the PS SnapIn are installed after the v12 update. I have seen some cases where a reboot was required after the update to make this work for all users on the server.

Im am using PRTG-VeeamBRStats-v3.ps1

To get rid of maintaining Veeam Console in the PRTG Probe you can schedule a Windows Task on the Veeam B&R Server to push the Sensor data to the PRTG Server. Example:
PRTG-VeeamBRStats-v3.ps1 -httppush:$true -httpserver <IP_ADDRESS> -httptoken 24A26A91-D292-4FF7-895D-B5E128A4D6C9 -httpport 5050

By the way, is there a scitpt for Monitoring Veeam 365 Backup ?

@jorgedlcruz is doing awesome work with his Grafana Dashboards: https://github.com/jorgedlcruz/veeam-backup-for-microsoft365-grafana


Removed code that removes the "X-Forwarded-Proto" header.

For some reason in an ASP.Net WebForms application, the OWIN pipeline appears to restart before a response is generated after the OpenIdConnectAuthenticationHandler.InvokeAsync. This results in ForwardedProtocolMiddleware being executed twice. Being as Steeltoe removes the "X-Forwarded-Proto" header, the scheme ends up being http instead of https resulting in a bad request_uri querystring parameter. It works fine in an ASP.NET MVC application. I can reproduce this and I am still working to isolate why the OWIN pipeline appears to restart. There is no harm in leaving "X-Forwarded-Proto" header and it resolves this issue.

@kadkins-pivotal  I'm sorry, but it looks like we were missing the .NET Foundation CLA bot when this PR was entered, can you confirm that you've signed the CLA? - https://cla.dotnetfoundation.org/SteeltoeOSS/steeltoe?pullRequest=81

I have signed the CLA.
Kendall Adkins
Senior Platform Architect
Tel:<PHONE_NUMBER>  |<EMAIL_ADDRESS>|
linkedin.com/in/kendalladkins/ https://www.linkedin.com/in/kendalladkins/
https://springoneplatform.io/2019/why-attend
https://pivotal.io/
The Pivotal Effect https://youtu.be/YyJbSFRjkuI
On Tue, Jul 16, 2019 at 11:38 AM Tim Hess<EMAIL_ADDRESS>wrote:

@kadkins-pivotal https://github.com/kadkins-pivotal I'm sorry, but it
looks like we were missing the .NET Foundation CLA bot when this PR was
entered, can you confirm that you've signed the CLA? -
https://cla.dotnetfoundation.org/SteeltoeOSS/steeltoe?pullRequest=81
https://urldefense.proofpoint.com/v2/url?u=https-3A__cla.dotnetfoundation.org_SteeltoeOSS_steeltoe-3FpullRequest-3D81&d=DwMCaQ&c=lnl9vOaLMzsy2niBC8-h_K-7QJuNJEsFrzdndhuJ3Sw&r=puyqNApXm2TZn2f5HE46EAOm8Irm-FqmZfZwudEjvw8&m=cW8q5op-l56C63AVzJcPYrC0wXWxEN7FV5gSNzc9Dug&s=WQK4KDS59AWkP3JA60ROsxcqVBxUdCfgAz6x8FWMbMo&e=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SteeltoeOSS/steeltoe/pull/81?email_source=notifications&email_token=AJTPZNKTBRJVRJH2AEMNX5DP7X2QFA5CNFSM4IBQOJB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2BN7UA#issuecomment-511893456,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJTPZNNIMDL4YACGHJKV32LP7X2QFANCNFSM4IBQOJBQ
.


Configure grafana for Cantus Database staging

@jacobdgm @lucasmarchd01 @softcat477
This has been completed, and logs are now available in my grafana cloud account. Example of what that looks like:

There are a two things I have run into:

The grafana cloud free tier only allows three users. I'm happy to invite Lucas and Jacob, which may be enough for CantusDB, or we can create a shared user from some DDMAL-shared email address. Or Ich will need to pay for the next tier. Or we will need to host our own grafana stack.
Grafana cloud....doesn't really persist the logs! sad face If we had our own stack, we could, but the cloud version only holds on to them for 30 days. So it is definitely useful in things we need logs for imminently (eg. figuring out why CantusDB just went down) and it will hold on to logs between starting and stopping of docker containers, but it won't completely solve #1112

I will add invite @jacobdgm and @lucasmarchd01 as discussed in the email, but please take a look at the rest of the comment

@softcat477, we assigned this to you because you recently and successfully set up Grafana on several of DDMAL's other sites. This will need to be a separate setup because it's not on Ich's allocation, but we'd appreciate your help in getting this running!

It looks like there is no longer a grafana instance on our allocation. I think the simplest thing is going to be to just ensure that docker logs persist somewhere between runs, etc. We should be able to do this locally, and it looks like docker has the local log driver that handles log rotation, etc. Changing the title for this issue.


README.md and bootstrap.sh changes

I am using a 5 node coreos cluster and ran into some issues, proposed changes:

the ansible_python_interpreter variable setting in the README.md didn't work for me, I had to change it (tested working)
I use an offline mirror of the pypy tar file, I made the download URL a variable to easily repoint the location
Added some comments to bootstrap.sh

the only change I like from this is the PYPY_URL variable. The rest isn't needed I think.

ansible_python_interpreter="PATH=/home/core/bin:$PATH python"
I am not sure if this was intentional to have a PATH= line inside the quotes, but the sample didn't work for me til i changed this to
ansible_python_interpreter="/home/core/bin/python"
i agree that the PYPY_URL change and added comments is not needed, but for me it made it easier to understand


[Request] List with compatible wallet apps

I'd love a list in the Readme with all the compatible wallet apps where the QR scan works best with your app. Eg. as in the price gets filled in automatically, etc.
Because not all wallet apps have the same scanning specifications I think.

Actual usage of the QR protocol is currently very fractured and gives different and unexpected results based on which wallet the user uses.

Toshi wallet crashes on QR code scan (at time of writing 2018-07-24)

None of the wallets we tried use the value field...

For now I have forked the package here and changed the field called value to amount. If there would be an update in the future to have an option to also support the amount field next to the value field, that would be great!


Component Governance: Need to upgrade dependencies.

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-1045

Upgrade to version Microsoft.AspNetCore.App - 2.1.22, Microsoft.AspNetCore.All - 2.1.22,Microsoft.NETCore.App - 2.1.22, Microsoft.AspNetCore.Http - 2.1.22

https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-26701

Upgrade to version System.Text.Encodings.Web - 4.5.1,4.7.2,5.0.1

Package at fault:

Microsoft.ApplicationInsights.AspNetCore

Microsoft.AspNetCore.Hosting v2.1.1

Microsoft.AspNetCore.Http v2.1.1 CVE-2020-1045
Microsoft.AspNetCore.Hosting.Abstractions v2.1.1

Microsoft.AspNetCore.Http.Abstractions v2.2.0

System.Text.Encodings.Web v4.5.0 CVE-2021-26701

https://github.com/microsoft/ApplicationInsights-dotnet/blob/2b19327fc5853d69010712953961960aa8c3ee5e/NETCORE/src/Microsoft.ApplicationInsights.AspNetCore/Microsoft.ApplicationInsights.AspNetCore.csproj#L47-L56
Remediation

Upgrading to Microsoft.AspNetCore.Hosting v2.2.0 will upgrade Microsoft.AspNetCore.Http to v2.2.0.
We must take a temporary explicit dependency on System.Text.Encodings.Web until one of the other dependencies in this chain is updated.

We are also dependent on getting the updated Microsoft.ApplicationInsights.AspNetCore due to CVE-2021-26701. What is the ETA for the update?

Also wondering this.
This is causing compliance violations for CVE-2021-26701 because of dependencies on older versions of: System.Text.Encodings.Web

2.18 Milestone due date is May 31, is that the ETA?

This is a summary of the changes we made for this issue in #2243:
<ItemGroup Condition=" '$(TargetFramework)' == 'netstandard2.0' OR '$(TargetFramework)' == 'net461' ">
    <!--
    Microsoft.AspNetCore.Http has a vulnerability https://msrc.microsoft.com/update-guide/vulnerability/CVE-2020-1045
    System.Text.Encodings.Web has a vulnerability https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-26701

    These are both implicit dependencies from Microsoft.AspNetCore.Hosting.
    (Microsoft.AspNetCore.Hosting > Microsoft.AspNetCore.Http)
    (Microsoft.AspNetCore.Hosting > Microsoft.AspNetCore.Hosting.Abstractions > Microsoft.AspNetCore.Http.Abstractions > System.Text.Encodings.Web)
    -->

    <!--
    Taking a dependency on Microsoft.AspNetCore.Hosting v2.2.0 would resolve this issue, but would also break support for NetCore v2.1.
    Instead I'm taking a direct dependency on the fixed version Microsoft.AspNetCore.Http.
    We can remove this when NetCore v2.1 reaches EOL on August 21, 2021.
    -->
    <PackageReference Include="Microsoft.AspNetCore.Http" Version="2.1.22" />

    <!--
    We must take a temporary dependency on this newer version until Microsoft.AspNetCore.Hosting updates their dependencies.
    -->
    <PackageReference Include="System.Text.Encodings.Web" Version="4.5.1" />
  </ItemGroup>


Support for W31-N15 Confirmed

Hey, Looks like the W31-N15 is supported fully with this. I have full control of the RGB color, temperature, brightness, and toggle. I don't quite know how to update the wiki myself but it's all working on my end as of 9/14/21

Thank you.

This is it, I have the same bulbs.

This is it, I have the same bulbs.

I would like to confirm that it does indeed work, I just connected four of them. Seems faster than the sengled app, too.


Java alb

adding a common package to register and de-register a dropwizard application in aws target group
ping @tbaylis , @fredrikbackstrom

Seems ok, but maybe some documentation describing how to use the package would be nice?

Also, nitpicking: please use spaces instead of tabs, and make sure each file has a newline at EOF.


Update or replace mock-django

We use the package mock-django in edx/ecommerce. This package isn't maintained now and it doesn't have support for Django3.2. Please follow the guidance in https://openedx.atlassian.net/wiki/spaces/AC/pages/3036972032/Handling+Outdated+Dependencies to resolve the problem this poses for the Open edX Django 3.2 upgrade.

Hi, I can help with this issue.

@Jacatove Thank you for reaching out.  I will assign this to you.  Please let me know once this is done.

Hi @jmbowman I have a question but first let me give you some context of what I have done.

I opened a draft PR. A solution based on the 5th option to Handling Outdated Dependencies. (There is more information explaining the reason I choose the 5th option in the PR description)
I have received an email from the maintainer of the dependency:
"no intention to maintain it on my side. Happen to give you maintainership though if thats interesting. Otherwise feel free to pull in the relevant code yall need. I can double check license to make sure theres no concerns, but I imagine its BSD/Apache-like."

Now my questions:
Is 1. the better option for edx?
if yes, then where should I put the copied code from the dependency?

@diegomillan This is the ticket I need help with.

Hi @Jacatove thanks for your efforts on the issue. Your PR has been merged. Since it is only a testing dependency so it'll be removed when merging the upgrade branch to master hence you won't need to create separate PR for that.
I'll mark this issue as done. Thanks.


Stop supporting TLS 1.0 and TLS 1.1

The server seems to support TLS 1.0 and TLS 1.1: https://www.ssllabs.com/ssltest/analyze.html?d=bitclout.com&s=<IP_ADDRESS> …but this seems, to me, to present security issues: https://blog.qualys.com/product-tech/2018/11/19/grade-change-for-tls-1-0-and-tls-1-1-protocols

Done, thanks!


Ability to hide reposts and quote posts per followed account

Is your feature request related to a problem? Please describe.
I know that I can hide reposts and quote posts via my settings. But I'd like to be able to decide that for each account I'm following.
Describe the solution you'd like
A setting to hide reposts yes/no for each account I'm following.
Describe alternatives you've considered
It would be nice to also have the setting per account for quote posts, but that's less important for me.
Additional context
I used that a lot on twitter: the decision depends on how much the person reposts, and if I find their reposts interesting or not.

Looking forward to this :-)

In the meantime I'm using https://bsky.app/profile/skyfeed.xyz/feed/only-posts, which hides reposts.

as a new bluesky user, I love my friends but some of them repost too much or repost bad posts. I would like to mute their reposts please.

We're definitely aware of the importance of this feature — blocked on a few things on the backend so we can't prioritize it right now, but we're planning to get to it as soon as those blockers are solved.

Congrats on the fast pace bsky's been evolving, just coming here to reinforce the request for this!
Hope thos blockers get solved soon ♥

This would be a great addition. OnlyPosts is helpful in reducing the clutter of reposts, but I'd like more control over my feed than all-or-nothing.

Looking forward to this! 😊

Looking forward to this feature!

Looking forward to this!

I will just say this specific feature is pretty vital for a lot of folks trying to migrate over. I have folks I follow that I want to see on my feed but I dont need to see the dozen reposts they propagate each day (for various reasons). I'm finding myself holding off following a lot of folks until this is implemented.

Looking forward to this feature

Totally understand there being more pressing concerns, but this would be a VERY nice feature on top of all the curation tools the dev team has given us. Eager to see this be implemented!

Related, and immediately actionable given existing features: I could not find a feed that displays one's own posts with reposts filtered out. It would be nice if I could add this to my feeds list so that people who want to check out my profile can take a look to see what I post, without seeing what I repost. This is currently possible if I make a custom feed of my own, but it doesn't make too much sense for everyone to do this independently.
This has good synergy with an eventual "filter out reposts" option, because this feed would basically represent what they'd be seeing if they do so.

+1 for this. I know you guys are working hard behind the scenes, i just hope that whatever backend issue is preventing this from being implemented is given attention soon as fully half of my feed is tainted by bad reposts

Could we just add '👍' emoji reaction at the top of this issue, instead of just commenting "+1" or "looking forward" or whatever? I've subscribed this issue for a while ago, and some recent comments feel like redundant.

Any update on this being added?

I really wish this feature existed. Sure, you can turn off reposts for everyone, but it would be great to have the option to disable them for specific users who tend to overdo it. As someone mentioned before, I love my friends, but some of them repost way too much. I’d prefer to turn off only their reposts rather than disabling reposts for everyone (which is why the "only posts" feed doesn’t fully solve the issue). This was a feature I frequently used back on Twitter.

I really wish this feature existed (it seems to have been on the roadmap for over a year now). Sure, you can turn off reposts for everyone, but it would be great to have the option to disable them for specific users who tend to overdo it. As someone mentioned before, I love my friends, but some of them repost way too much. I’d prefer to turn off only their reposts rather than disabling reposts for everyone (which is why the "only posts" feed doesn’t fully solve the issue). This was a feature I frequently used back on Twitter.

i am desperate for this feature.

I know I'm going to get downvoted, but seriously, this is probably Bluesky's biggest feature gap right now and it's killing the experience, especially as a flood of new people repost everything. Any updates on priority, timeline -- anything at all -- would be greatly appreciated.

Fwiw you can probably write a quick user script to hide reposts for some users on the web version for now, though I get your frustration.

As much as I don't think comments saying how important the feature is are useful (clearly the team are already well aware, they just also have lots of other very important tasks on their plate, and there are other ways to express this without emailing everyone subscribed to this issue), I do want to do something more constructive than just give them a thumbs down. As @uncenter says, it should be possible to filter reposts out if using the web version at least. Here's a filter rule (compatible with uBlock Origin, but probably other content filtering tools) which will work to hide reposts from a given account:
bsky.app##div[data-testid^="feedItem-by-"]:has-text(/Reposted by you/)
This blocks your own reposts. Obviously that probably isn't what you want, so change the text in the rule from "you" to the display name of the account in question.  It would also break if an account changes their display name (or if you followed two accounts with the same display name, e.g. let's say if they both just use their first name), or obviously if the markup changes. But hopefully this is at least a way to make the site usable for some people, while they wait for a real solution?

bsky.app##div[data-testid^="feedItem-by-"]:has-text(/Reposted by you/)`

For those of us somewhat technically aware: great! For those of us not 100% up to speed on BlueSky* configuration, where do I put this?
(*) I wish I could abbreviate BlueSky the same way I abbreviate WikiPedia.

I know I'm going to get downvoted, but seriously, this is probably Bluesky's biggest feature gap right now and it's killing the experience, especially as a flood of new people repost everything. Any updates on priority, timeline -- anything at all -- would be greatly appreciated.

Please believe me, everyone on the team is aware this is a huge missing feature. The backend team is at capacity at the moment and this feature in particular is gnarly to implement within the constraints of how our backend works today. In other words, this is very much a known gap but no amount of asking here will help bump it up. I want it yesterday too.


jakttest: Don't spin while polling child processes

This patch removes the WNOHANG from the waitpid call in jakttest/process.cpp so that we no longer have to call process::poll_process_exit in a loop: instead, we simply resume when the child process actually finishes.
Fixes #1228.

The runtime error you're getting is an 'interrupted syscall' error, which probably happens when calling waitpid. Probably ignoring the EINTR that you're getting from waitpid would suffice to remove the hanging.
Problem aside, I think this might not be the main issue. Reason is that the main Jakt process only calls waitpid with WNOHANG repeatedly to pop one by one all the children that have exited in case someone else exits when it's checking another child's exit. When waitpid errors with ECHILD, it goes back to the "wait for free directory" part where it (at least under POSIX) tells the OS to only wake up on SIGCHLD (see man 3 sigwait): https://github.com/SerenityOS/jakt/blob/520128b89e433f4a6cc81681ca4edc0856314007/jakttest/jakttest.jakt#L575-L587.

yeah, since it's just waiting it would be better to let stuff run instead of staying there. Good catch, thanks!

Can we just use the process stuff that the compiler itself is using? not sure how this is used, but there's a process pool abstraction in there that might be useful too.


Add zksync docs

Describe the bug
The code and past PRs suggest zksync is supported, however there is no documentation in the code. Could this be added please?

+1


Write a dynamism RFC

MHLO's design for supporting dynamic shapes is pretty battle-tested already, and we've inherited it in StableHLO by bootstrapping from MHLO. Let's further iterate on it to address some of the rough edges, e.g. one possibility would be to merge dynamic ops like dynamic_pad with regular ops like pad. We already had some discussions about dynamism with the TCP effort, and I'm looking forward to continuing that.

I haven't gotten a chance to make progress with this ticket yet. This week, I was focusing on unblocking adoption of StableHLO by integrating it into MLIR-HLO, so that existing MHLO producers / consumers have an easy way to experiment with it. Next week, I'm planning to work on compatibility guarantees (#4), and then I'm hoping to get to this ticket next.

I'll need to spend some more time on integration work (the recently opened ticket on integration with TF, JAX, PyTorch/XLA and Torch-MLIR), but I'm aiming to start working on dynamism in early Q4. I have a pretty fleshed out draft, but haven't yet had the time to finish and publish it.

"I'm aiming to start working on dynamism in early Q4. I have a pretty fleshed out draft, but haven't yet had the time to finish and publish it". In early Q4, I got involved in speccing statically-shaped ops, and this was a very interesting experience. The more I worked on the specs, the more I realized that the dynamism RFC should be written differently that what I imagined before.
Previously, I planned to approach the dynamism RFC similarly to #194 - describe the baseline, summarize design goals, write down which fields will be added / changed in which ops, provide some examples, and that's it. However, when writing and reviewing specs, I observed that this approach can leave a lot of corner cases out of sight / out of mind. Given that we are not blocked on the dynamism RFC (the design of dynamism that we inherited from MHLO has many known issues but it works), I'm hoping to approach this differently.
In December, I expect that two things will happen: 1) we will finish speccing statically-shaped StableHLO ops, 2) we will formalize syntax and evaluation of StableHLO programs (#484). Once that's done, I'm planning to write the dynamism RFC as the delta to this formalism (where the usual design document will be accompanied with changes to spec.md). I think this won't be too hard and will result in a higher-quality design, because we'll be forced to explore more details.
Moreover, having a formalism in place will allow us to prove things about StableHLO programs. E.g. specifying the conditions under which type inference can specialize dynamically-shaped programs to static shapes. Or resolving open questions like #229. I think this is worth investing the extra time.

Had offline chats with @smit-hinsu.
Logically speaking, we may want to break up the discussion into three segments - see below. Happy to hear what other folks have in mind.

What's our bounded dynamism API proposal?
What's our unbounded dynamism API proposal?
What's our proposed path to unify the bounded and unbounded API?

CC @burmako

Milad, thank you for the introduction! I also wanted to provide some additional context on StableHLO's plans for dynamism. In a nutshell these plans involve:

Support for bounded dynamism (already informally exists in StableHLO, needs to be formalized).
Support for unbounded dynamism (already informally exists in StableHLO, needs to be formalized).
Potential unification.

1) For bounded dynamism, the RFC linked by Milad talks about the design in StableHLO which involves roughly the same functionality as HLO: a) bounds for dimension sizes in tensor types, b) get_dimension_size and set_dimension_size ops that map directly on HLO ops. In StableHLO, we take compatibility very seriously, and we want to keep providing these APIs for frontends like PyTorch/XLA that have investment in HLO-style dynamism.
2) For unbounded dynamism, we're going to have a separate RFC in the near future, and the work on this RFC is tracked in https://github.com/openxla/stablehlo/issues/8. In the unbounded dynamism RFC, we'll be aiming to:

Unify already existing dynamic_foo and foo ops (e.g. dynamic_reshape and reshape).
Provide clear principles by which we decide what metadata can be dynamic and what metadata must be static (e.g. should ReverseOp::dimensions be static or dynamic? what about SliceOp::*indices?).
Decide on the API to represent shapes (shape as a separate entity? shape as a vararg of dimension sizes? something else?).

3) In the long term, we would also like to unify bounded and unbounded APIs, and the RFC linked by Milad talks about some initial ideas in this area (see the "(P4) Aspirational: Migration to unbounded dynamism" section). This is some very early thinking, and I'm not yet sure how this will work out - it would be preferable to have just one API, but maybe we'll end up with two.

Here's the long awaited RFC: #1668.

The RFC has been merged: https://github.com/openxla/stablehlo/pull/1881
See it here: https://github.com/openxla/stablehlo/blob/main/rfcs/20230704-dynamism-101.md


Connection Error: error returned from database: invalid value for parameter "TimeZone": "UTC"

Running in an devcontainer as user 'vscode'.
This error comes when I try to connect with sea-orm like Database::connect(pg.settings().url(database_name)).await
Installing tzdata and setting the timezone to UTC seems to have resolved it. Perhaps this is something that can be resolved in the crate itself?

Were you attempting to use this https://github.com/theseus-rs/postgresql-embedded/tree/main/.devcontainer  ?
If so, could you provide the steps to reproduce, and/or a PR with the changes you made that worked for you?

Using my own container. This was the fix:
RUN apt-get update && \
    DEBIAN_FRONTEND=noninteractive apt-get install -y \
        tzdata

# Set the timezone environment variable
ENV TZ=UTC

# Configure timezone
RUN ln -snf /usr/share/zoneinfo/$TZ /etc/localtime && echo $TZ > /etc/timezone

Thanks for the follow up @ShelbyJenkins; glad you got everything working.


Data on the Web Best Practices

The Data on the Web Best Practices group would like TAG review on our Best Practices document:  http://w3c.github.io/dwbp/bp.html
Given that I'm co-chairing the WG and a contributor to the document, we (the TAG) thought it would be good to get some wider review from the TAG family.  @JeniT, might you be able to help us?

Adding in co-chairs @deirdrelee and @yaso, and editors @bernafarias, @cburle and @newtoncalegari

Closing this... Data on the Web Best Practices is now a Rec: https://www.w3.org/TR/dwbp/


Upgrade deprecated python runtime

Upgrade deprecated python runtime
The lambda runtime used for the functions is python3.7. This runtime is being deprecated on lambda on Nov 27, 2023 (Phase 1).
Are there plans to upgrade and test using a newer runtime before AWS stop supporting the current runtime?

A reproducible test case or series of steps

Nothing out of the ordinary here.

The version of our code being used

5.18

Any modifications you've made relevant to the bug

No

Anything unusual about your environment or deployment

No. Deployed using SAM cli.

Following is the notice from AWS regarding the deprecation:

We are ending support for Python 3.7 in AWS Lambda. This follows Python 3.7 End-Of-Life (EOL) reached on June 27, 2023 [1].
As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in two stages. Starting November 27, 2023, Lambda will no longer apply security patches and other updates to the Python 3.7 runtime used by Lambda functions, and functions using Python 3.7 will no longer be eligible for technical support. In addition, you will no longer be able to create new Lambda functions using the Python 3.7 runtime. Starting January 25, 2024, you will no longer be able to update existing functions using the Python 3.7 runtime.
We recommend that you upgrade your existing Python 3.7 functions to Python 3.11 before November 27, 2023.
End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.
...
[1] https://peps.python.org/pep-0537/
[2] https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html

Solved by #56


how to calculate the parameter number of model

Is there any function or script to calculate the total number of parameters of the model?
Thanks!

@xypu98 https://github.com/open-mmlab/mmdetection/blob/main/docs/en/user_guides/useful_tools.md#model-complexity


[HM3D Annotation] --HM3D SSD file support; Misc SSD Fixes

Motivation and Context
This PR adds the following functionality for SSD support :

More intelligent default file name choices for stage atttributes (not only SSD but semantic mesh and navmesh as well)
Function for setting the colormap to use for the TextureVisualizerShader, so that an external map can be used (instead of being forced to use the hard-coded Magnum turbo colormap)
A colormap is synthesized when a ply is loaded based on vertex colors, to be used for Semantic Scene visualizations.  The Magnum Turbo colormap is still supported as a fallback option.
HM3D SSD file (house file) load and process supported based on the current annotation file format from Appen.
More consistent naming and access for SSD files from StageAttributes.

What's left is appropriate bindings and tests.

How Has This Been Tested
Locally C++ and Python tests.

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Ah, whoops nvm then.
On Mon, Nov 8, 2021 at 11:53 AM John Turner @.***>
wrote:

@.**** commented on this pull request.
In src/esp/metadata/managers/StageAttributesManager.cpp
https://github.com/facebookresearch/habitat-sim/pull/1556#discussion_r744914280
:

     // datasets

     ssdFileName =

         Cr::Utility::Directory::splitExtension(attributesHandle).first +

         ".scn";

   }

 }

 newAttributes->setSemanticDescriptorFilename(ssdFileName);

 // Build default semantic mesh filename as root stage name ending with

 // "_semantic.ply", for back-compat with Mp3d

 std::string semanticMeshFilename =

     this->findFilenameUsingCriteria(attributesHandle, {"_semantic.ply"});

 // if present, file was found, so set value (overriding attributes

 // default)

 if (!semanticMeshFilename.empty()) {

   newAttributes->setSemanticAssetHandle(semanticMeshFilename);

All these string setters are const string& setters, so moving isn't really
useful here, is it?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookresearch/habitat-sim/pull/1556#discussion_r744914280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPVMXZLWH47XINCVAN4NMDUK76AVANCNFSM5HHM6A3A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

This looks like the Simulator is segfaulting or failing some other way when loading the WebGL build.

Most recent force-push changed how shaders were loading. Loading them in the Renderer constructor (as this PR previously introduced) was not compatible with the current Javascript calling protocols, so this mechanism was removed and the existing on-demand instancing is being used instead.


Could not alert in 0.13 if use count?

Hi, I have built telegraf + influxdb + grafana and they works well!
And I use kapacitor as an alert tools, and I use the example in https://docs.influxdata.com/kapacitor/v0.13/introduction/getting_started/#trigger-alert-from-batch-data to build an alert test, but it failed..
Here is the tickscript, it should count the usage_idle and sent alert email to me, but I could not receive the email nor the log.. And I want to know where the codes goes wrong..
Thx a lot!
batch
    |query('''
        SELECT count(usage_idle)
        FROM "telegraf"."default"."cpu"
        WHERE "usage_idle" < 100
        ''')
        .period(30s)
        .every(30s)
        .groupBy(time(30s))
    |alert()
        .warn(lambda: "count" > 1)
        .crit(lambda: "count" > 7)
        .id('api_calls')
        .message('Alert: {{ .Level }}')
        .details('''

ID: {{ .ID }}

        Level: {{ .Level }}

Time: {{ .Time }}

        ''')
<EMAIL_ADDRESS>
        .log('/data/kapacitor/log/exception_alert.log')

It seems the count goes wrong... If  .warn(lambda: "count" > 1) changes to .warn(lambda: "count" > 0), I will receive many emails...

@EricQAQ How frequently are you sending data to InfluxDB from Telegraf? The default is 10s and you are only querying the last 30s of data so at most your count would be 3.
Also remove the group by time as its not needed in this case. Only use group by time when your period is larger than your group by time interval.

It's the default setting, every 10s the telegraf will send data to InfluxDB.
And I remove the group by, it also cannot work..
When I execute the kapacitor replay, the log of kapacitor is belowing:
[task_master] 2016/08/31 10:10:56 I! opened
[httpd] 2016/08/31 10:10:56 I! <IP_ADDRESS> - - [31/Aug/2016:10:10:55 +0800] POST /kapacitor/v1/replays HTTP/1.1 201 260 - KapacitorClient 26aa0cb1-6f20-11e6-8072-000000000000 36.350707ms
[task_master] 2016/08/31 10:10:56 I! Started task: cpu-alert
[task_master] 2016/08/31 10:10:56 I! Stopped task: cpu-alert
[task_master] 2016/08/31 10:10:56 I! closed
[httpd] 2016/08/31 10:10:56 I! <IP_ADDRESS> - - [31/Aug/2016:10:10:56 +0800] GET /kapacitor/v1/replays/50b72009-0501-490d-8b49-2fdfa79047ec HTTP/1.1 200 261 - KapacitorClient 26fc3418-6f20-11e6-8073-000000000000 2.557352ms

@EricQAQ Try using this TICKscript:
batch
    |query('''
        SELECT count(usage_idle)
        FROM "telegraf"."default"."cpu"
        WHERE "usage_idle" < 100
        ''')
        .period(30s)
        .every(30s)
        .groupBy(time(30s))\
    |log()
        .prefix('QUERY RESULT')
    |alert()
        .warn(lambda: "count" > 1)
        .crit(lambda: "count" > 7)
        .id('api_calls')
        .message('Alert: {{ .Level }}')
        .details('''

ID: {{ .ID }}

        Level: {{ .Level }}

Time: {{ .Time }}

        ''')
<EMAIL_ADDRESS>
        .log('/data/kapacitor/log/exception_alert.log')

Check the Kapacitor logs and look for QUERY RESULT and see if the count value matches your expectations.

@nathanielc Thx for your answer! My script goes well..
But it is strange that if I use kapacitor record batch -task batch_cpu_alert -past 30s, it couldn't work, but if I change 30s to 1m, it worked well... Is it because I set every(30s), kapacitor will not execute this tasks in first 30 seconds, and when it start the time is out?


Fix supports_attribute without a colname

If you use supports_attribute without a colname, just with :feature => feature_name defining the virtual_attribute fails ecause colname is nil
GET /api/providers?expand=resources&filter[]=supports_cloud_volume_create=true
{
  "error": {
    "kind": "bad_request",
    "message": "Must filter on valid attributes for resource",
    "klass": "Api::BadRequestError"
  }
}

Fixes https://github.com/ManageIQ/manageiq-ui-classic/issues/7960

I like your newer fix better
The original code had different rules for defining different fields


Subscriptions

So the roadmap will or will not support subscriptions ?
so but I found the reasons to be ambiguously describing this

There are no current plans for implementing subscriptions as of yet, but we'd certainly welcome contributions from the community. The management of WebSockets and how holding on to them makes Bramble stateful is the main hurdle to overcome. We haven't really spent any time thinking about this too much yet.

See #23 about keeping track of implementing/supporting subscriptions


Feature Request: Support installation on non-interactive environment

Right now, when I run ./cli-install, the script is waiting for user input.  Please provide flags that will allow us to run this without additional interaction.
Use Case

I'm trying to use this in ADO build but can't because this require interaction.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 29493ec8-b119-457b-21c1-348a6b807884
Version Independent ID: bf64c389-7811-b33c-6c2a-b8d69a9ec7d3
Content: Install the VSTS CLI
Content Source: latest/docs-ref-conceptual/install.md
Product: vsts
GitHub Login: @elbatk
Microsoft Alias: elbatk

The Azure CLI with the Azure DevOps extension has replaced the VSTS CLI. The VSTS CLI has been deprecated and will no longer be receiving new features. We recommend that users of the VSTS CLI switch to the Azure CLI and add the Azure DevOps extension.
This issue will no longer be a concern since Azure-CLI and Azure DevOps extension install can be done non-interactively.
Let us know if that solves your problem.

we should update documentation to remove reference to VSTS CLI.  I  didn't know about VSTS CLI until I was "told" to use it when setting up Feed in ADO Artifacts

@mydiemho  Thank you for the feedback.
The documentation update is planned to happen soon (cc: @geverghe since he is tracking it. )
We did update the VSTS CLI documentation here.
I will go ahead and close this issue. Feel free to open a new bug/feature request in this repo if you face any issue in using Azure DevOps Extension.


(MAINT) Bump Ruby puppet version

This is needed to maintain acceptance test parity with the new version
of MRI Puppet.

This looks like the SHA where the PUPPETVERSION was bumped to 3.7.4, so assuming that's what we want, :+1:.

I think Puppet 3.7.4 is used with a newer version of Facter, too, so we probably should bump our submodule for that also.  I think the right version is 2.4.0 - GIT SHA 8ff4fa5e0251aaa1b3fea1e2e308a34b2ffe6027.

@camlow325 Bumped facter up to 2.4.0

I think you'll also need to update the "returns the correct puppet version number" test in .../spec/puppet-server-lib/puppet/jvm/master_spec.rb from '3.7.3' to '3.7.4'.

I dang, I only ran 2 different tests suites before submitting this

:+1:


Add dependabot for github workflow and go dependencies

Just opening up an issue here so I don't forget. Not high on my list of priorities but we're in the middle of taking care of this on the majority of OSS repositories.
Those who normally contribute, please let me know if you foresee any issues with a Go version/packages update.

I can do that, will open up a PR the next days


Multi page selection in debug console

I assume the console view is virtualized and so I can't copy a large amount of output at once. This is useful when debugging the Chrome adapter since it has a setting to write tons of logs into the console.

Until you can select more than one page, could you maybe implement https://github.com/Microsoft/vscode/issues/3974 so at least the whole output could be copied at once, directly? I am also often in the position that I ask people to send me their logs and they cannot...

I believe this is fixed now in 1.8+ and can be closed out :+1:  @roblourens

@MarkPieszak no, it is not fixed unfortunetly 🐝

Oh strange maybe I was in another tab sorry! Apologies :(

https://github.com/Microsoft/vscode/commit/e261525aad152779f5fda7c253a0f62d92a529ff
Did this commit just add a "copy" item to the right click context menu? If so, that button still has this same issue. If it's not feasible or easy to add a way to copy all selected text instead of only what's in the window, a "copy all" button would suffice.

A hack of this would be redirect output to a file, what I did was to add ">" and then a filename like "output.txt" to "launch.json" in the "args" field. Works fine for now.

Is "selecting and copying a region of text" really so novel or difficult to figure out? I can swear I've seen such a thing in another app once.

@benjamin21st mind adding a quick snippet so we can see this formatting? This sounds very useful. Will it overwrite each time we run the debugger, or always add to the file?

@JacobJT  Just like in command line you can do something like:
./myprogram > output.txt
In VS Code, you can set up your launch.json file such that it has the following args in one of your tasks:
"args": [   "arg1",   "arg2",   ">",   "output.txt" ]

This issue is so disturbing. It basically makes the debug console useless... worse than useless actually since you need to change perfectly good reporting code just to be able to read some logs.

Would love to see this.  Trying to debug some rather lengthy request body differences that would be much easier to use a diff tool on.

It would also give us a way to search the console output, which currently I am not able to figure out how to do.

This issue makes me think twice before attempting to file issues for an extension. The hack @benjamin21st mentioned does not work for me (I'm on linux)

I have investigated today for the things needed in order to make this work:

The tree needs to auto reveal top and bottom as the selection changes. This is possible to get done using the selectionchange and selectstart events
Since the tree is virtualised the native selection can never span through elements which are currently not visible. In order to make copy work we would need to append selected textas we are scrolling in the tree. This can be rather tricky if the selection is changing directions

An alternative approach is to determine on what element in the model the selection started and where it ended and to copy the content between these elements. However the issue here is that the selection will not in some cases match what is being copied.
Another alternative approach is to use the editor for the debug console implementaion which is captured here #11462
Since the ideas above require quite an effort and would introduce additional issues for now we have chosen a pragmatic solution already suggested by @felixfbecker and have added a context menu action to simply copy all the output. So keeping this issue open as a feature request to be able to do more fine grained multi page copying but pushing it to backlog as I believe this workaround will help with most scenarios.
You can try it out in tomorrows insider build or in the next stable at start of june.

Can we add a "Copy All (Unformatted)" or "Copy All (Plain text)" function to the menu?
When I copy/paste the log into editor (like Notepad++), there are characters that editor can't display. It would be a lot easier to analyze the log if we can just copy the log as plain text.

@zhaihm please open a new issue / feature request for this and ping me on it. Thanks

Thanks for the replay. @isidorn  I opened #28094 for this feature.

I am using latest version 1.13.1, I can not see Copy All. Is there any flag to enable this?

@smarigowda that is the variables panel, not the debug console

thank you. I can see it in debug console. Impressed with your lightning fast reply 👍

This issue also applies to less-than-multipage selections in my opinion. Select a single character in the Debug Console, scroll the Debug Console up or down just far enough that the selection disappears, then scroll back to the original scroll position - the selection is gone.

Another problem is that I can't select the first charactor.
For example, I can't select the charactor n in following screenshot:

Unfortunately I don't think this is practical with the virtualized debug console as it currently works. I think the "Copy All" context menu option which now exists is the best option.


test PR with Github API

Please pull this in!

Docs Build status updates of commit 8abbd9a:
:warning: Validation status: warnings
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[WIP] Integrate with external Tower Workflow

https://bugzilla.redhat.com/show_bug.cgi?id=1468339
Part of https://github.com/ManageIQ/manageiq/issues/17441

@Fryguy can you take a look? Some modeling work here and so would like to gather feedback early on. thanks

@miq-bot remove_label wip
@miq-bot add_labels enhancement, providers/ansible_tower


Migrate lagging 'net' builds to 'netlrts'

Original issue: https://charm.cs.illinois.edu/redmine/issues/1070

Based on net-linux-x86_64 and net-darwin-x86_64 vs their netlrts equivalents, the conv-mach files can be copied straight over from net to netlrts to make a working build.
Subbugs should copy over for their designated platform, test, make adjustments as necessary, and commit.

Original date: 2017-03-23 15:45:10

net-linux-amd64 and net-linux-cell are the only net builds left without netlrts equivalents. Do we even want to have netlrts versions of those?

Original date: 2017-03-23 16:32:34

Sam White wrote:

net-linux-amd64 and net-linux-cell are the only net builds left without netlrts equivalents. Do we even want to have netlrts versions of those?

Isn't amd64 the same as x86_64?


[Payment settings] Failure to save new custom token

Tried adding the NPXS token as a payment method. It seems to be added successfully and shows up on the list of crypto payments but disappears when I click "update".
Probably related to #295 .
Video here

Update: the NPXS token showed up on the payment settings page after a few hours.

Should be fixed by #340


Add shorthand for "⇐"

This closes #492.

related: https://github.com/typst/typst/pull/2488#issuecomment-1790472436

Yeah, thanks for the contribution, but I'm afraid it's the same as with #2488. Moreover, I think =< for ⇐ is rather confusing since it's not visually the same thing.


Feat: New Latinamerican Spanish localization

It is basically the same file as the Spanish one from Spain, but with changes in the names of the monsters.

Please rename the file to match the pattern of the other filenames.
language_country where language is in the ISO 639 format


sea-orm-cli errors exit with error code 0

Description
When using the CLI, any error returns the status code 0, which suggests that the command worked properly.
Steps to Reproduce

Write an incorrect migration
Run sea-orm-cli migrate; echo "status = $?"

Expected Behavior
sea-orm-cli migrate; echo "status = $?" should output status = 1 or some other code.
Actual Behavior
sea-orm-cli migrate; echo "status = $?" outputs status = 0, suggesting that the command worked.
Reproduces How Often
Always
Versions
│   ├── sea-orm v0.10.6
│   │   ├── sea-orm-macros v0.10.6 (proc-macro)
│   │   ├── sea-query v0.27.2
│   │   │   ├── sea-query-derive v0.2.0 (proc-macro)
│   │   ├── sea-query-binder v0.2.2
│   │   │   ├── sea-query v0.27.2 (*)
│   │   ├── sea-strum v0.23.0
│   │   │   └── sea-strum_macros v0.23.0 (proc-macro)
├── sea-orm v0.10.6 (*)

Additional Information
This is likely quite easy to fix, it just requires exiting with error code 1 on any error :slightly_smiling_face:
My particular use case is I have a script to run migrations in development that looks like the following:
dropdb -U postgres -h localhost -p 5432 -w postgres
createdb -U postgres -h localhost -p 5432 -w postgres
sea-orm-cli migrate \
    && sea-orm-cli generate entity \
        -o entity/src/entities \
        --expanded-format \
        --with-serde both

In this case, I want the script to stop running if the migration failed, since it's easier to debug without the rest of the data from generating entities. The && will only run the second command if the first one exits with a return value of 0.

I did reproduce this issue and would like to work on it.
@tyt2y3 @billy1624
I saw no member has commented on this can you please confirm once?

Hey @AngelOnFira, thanks for the report. After some digging I found that we didn't check the status code of the executed command.
To handle it properly, we should:
// Run migrator CLI on user's behalf
println!("Running `cargo {}`", args.join(" "));
let exit_status = Command::new("cargo").args(args).status()?; // Get the status code
if !exit_status.success() { // Propagate the error if any
    return Err("Fail to run migration".into());
}

Source code location: https://github.com/SeaQL/sea-orm/blob/ca205543a37ba734a90fed8f23daf1cf0e45ce0d/sea-orm-cli/src/commands/migrate.rs#L67-L69
I simply thrown an error and it will be handled by handle_error function at https://github.com/SeaQL/sea-orm/blob/ca205543a37ba734a90fed8f23daf1cf0e45ce0d/sea-orm-cli/src/bin/main.rs#L18-L30

Hey @Diwakar-Gupta, thanks for the initiative! Any opinions?
Maybe we should double check all places where we have used std::process::Command?

@billy1624
I did checked the suggested code and I worked.
Apart from sea-orm-cli/src/commands/migrate.rs we also need to handle same in sea-orm-cli/src/commands/generate.rs file.
I will raise a PR with this changes soon.

Thanks again for contributing! :D

Thanks for the fix @Diwakar-Gupta!


Example?

Allo,
Humble apologies. Maybe I just need to delve right in but I was wondering if it's possible to provide at least one worked through example please? I would like to try your code with ESP32S3 Sense. Could you please tell me if that's possible before I try...Maybe then I can help illustrate the whole approach?
With thanks.

See the examples folder. And yes, it should work, but please read the documentation. If you want more insides in the example code ask chatgpt

Allo,
Thank you for such a quick reply! It's good to know it should work with ESP32S3 Sense. I took a look at all of your documentation. I don't use chatgpt. I'll schedule some time at the weekend and if if get chance document a worked through example.
All best.

Hello,
Thanks again for your efforts. I got the Xiao ESP32S3 Sense camera working with the following initialisaion. There's a little lag presently on the webcam example but that doesn't worry me as I'll most likely be using still images eventually.
cam = Camera(
    data_pins=[15,17,18,16,14,12,11,48],
    vsync_pin=38,
    href_pin=47,
    sda_pin=40,
    scl_pin=39,
    pclk_pin=13,
    xclk_pin=10,
    xclk_freq=20000000,
    powerdown_pin=-1,
    reset_pin=-1,
    pixel_format=PixelFormat.JPEG,
    frame_size=FrameSize.VGA,
    init=False
)

All the best. WW.

Thanks for the feedback.
But, why are you not using the precompiled firmware for the Xiao? You can then skip passing the whole pin assignments.

Hello,
No problem. I did use the xiao firmware but without assigning the pins the camera wasn't displaying an image in the example web cam application. Is the firmware for the Sense camera I wonder?
Thanks.

Yes, it should. I worked for me without a problem (I have the same)

Hmm... sorry then I don't know what's different. Although I did read that there are two versions of the sense board. Who knows. It definitely works with the pins explicitly assigned though. All the best.

Are exactly the same. So, probably the issue is somewhere else. But they r it works it's fine. Please close the issue then.


Sensor Error

Hello i'm trying to use your script and get this error in the sensor
XML: Junk after document element  -- JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)

Hello could you please run the Script in Powershell and show me you Parameter and Output?

I've upgraded PRTG to the last version and now it working fine


Update multi-modules.mdx to add a note about it being a good idea to mark your schema module as a jvm-only module

Add a note about it being a good idea to make your schema module a jvm-only module when building for Android
Please feel free to completely reject this change if you feel like this is not the right place for it to be in, or to completely change the wording in any way you wish, as I am not sure if I am conveying my point as well and clearly as I would like to.
Perhaps the second paragraph of this note is note necessary at all. Also, the part which talks about how apollo-kotlin is KMP compatible and android modules can depend on pure jvm moduels is also just not necessary in this part of the docs and can be considered already known information.
I just wanted to propose this as a note somewhere in the docs as I recently did this change in our project and I saw a ~2.5x times faster compilation of our schema module in clean builds, which results in much better build parallelization which I was very happy about.

!docs preview

!docs preview


Kubernetes Deployment is not working

Hi,
I'm following https://docs.mattermost.com/install/install-kubernetes.html guide to install on kubernetes.
it is failing while executing the following command, with error of unable to create CustomResourceDefinitions.
kubectl apply -n mattermost-operator -f https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yaml
rajashekhar_gundeti@Azure:~/clouddrive/mattermost$ kubectl apply -n mattermost-operator -f https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yaml
serviceaccount/mattermost-operator unchanged
clusterrole.rbac.authorization.k8s.io/mattermost-operator configured
clusterrolebinding.rbac.authorization.k8s.io/mattermost-operator unchanged
deployment.apps/mattermost-operator configured
unable to recognize "https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1"
unable to recognize "https://raw.githubusercontent.com/mattermost/mattermost-operator/master/docs/mattermost-operator/mattermost-operator.yaml": no matches for kind "CustomResourceDefinition" in version "apiextensions.k8s.io/v1"
Please help me here.

Hi @rajashekhargundeti. I'm sorry you're having this issue, and I'd like to recommend posting in our Kubernetes channel on our community server if you haven't already. You can also post in our forum, in the Troubleshooting section.
You are also welcome to update the documentation with your findings and submit a PR. We welcome community feedback on the docs! :)

Hi @rajashekhargundeti. I wanted to follow up on this and find out whether you were able to resolve the issue you were having. :)

Closing ticket


Running MNIST samples on Datascience VM fail

I am not able to run any of MNIST sample from MachineLearning on the Datascience VM.
Here is my issue on Github: https://github.com/Microsoft/Windows-Machine-Learning/issues/10 that I started on the UWP thread: https://github.com/MicrosoftDocs/windows-uwp/issues/436
Thanks,
Thierry

@tja2000
Thanks for the feedback !  We will investigate and get back to you.

@tja2000 Hi, thank you for your feedback. But for non-document issues, MSDN/StackOverflow can help more. Git is just for solving document-related problems. Can you please post your problem in MSDN or StackOverflow so that we can help more?

@tja2000 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Set activation_state to 'active' after password reset?

I was going to work on a pull request for this but wanted some feedback first.
Currently my update method on my PasswordResets controller attempts to log in the user after they change their password.
If the user has not activated, they will not be authenticated and cannot login, even with their new password, until they click the activation link in their email.
Since the user has already gotten the password reset link out of their email, should they be considered active?
Should sorcery detect that the user activation submodule is active and mark the user as activated in change_password!?

Yes, it makes sense to make the user automatically active again after
password change.
Another possibility is to call @user.activate! manually, which will enable
developers to decide if they want it or not.
On Thu, Oct 27, 2011 at 2:30 AM, Tyler Montgomery <
<EMAIL_ADDRESS>
I was going to work on a pull request for this but wanted some feedback
first.
Currently my update method on my PasswordResets controller attempts to log
in the user after they change their password.
If the user has not activated, they will not be authenticated and cannot
login, even with their new password, until they click the activation link in
their email.
Since the user has already gotten the password reset link out of their
email, should they be considered active?
Should sorcery detect that the user activation submodule is active and mark
the user as activated in change_password!?
--
Reply to this email directly or view it on GitHub:
https://github.com/NoamB/sorcery/issues/114

That sounds OK, though on second thought I'm not sure why anyone would want to not activate.
We can start with just activating automatically, and see if someone needs otherwise...


fix: outline

Fixed the outline margin error that was coming in search box
Fixes issue #400.

Thanks @sharmashubam!


[stable/keycloak] Feature request: Update Keycloak to 4.5.0.Final

Keycloak team released version 4.5.0.Final. Please release an updated version of Helm Chart for app version 4.5.0.Final. Release notes: https://www.keycloak.org/docs/latest/release_notes/index.html.
Keycloak Chart maintainer: @unguiculus.
Keep in mind that docker-entrypoint.sh moved to /opt/jboss/tools/docker-entrypoint.sh in 4.4.0.Final so we will need to update ConfigMap:
https://github.com/helm/charts/blob/eede5b897459d55e4023802ba1dce1665a3a154a/stable/keycloak/templates/configmap.yaml#L24

https://github.com/helm/charts/pull/8192 should fix this issue.


GPU/CPU

Two related issues:

The software currently forces the user to use a GPU if it is available. The user should directly specify whether they want to use CPU/single-GPU/multiple-GPU.
Currently, multiple-GPU support does not work. The software should force the user to use a single-GPU only until this bug is resolved later.

Resolved by commit de92181 with utils/setup_gpu_support( ). Note that this function is only used in training; it should be used in testing as well.


R CMD check results

Run devtools::check() to perform R CMD check and the tests included in the package. R CMD check currently detects a few problems.
In the long run, we should get rid of all of these problems, this is required by CRAN. In the short run, we should get rid of the 3 warnings, in order to pass the checks on travis (to be implemented). Two warnings are straightforward, related to documentation, but we need to discuss the third one:
Compilation used the following non-portable flag(s):
  ‘-Wdate-time’ ‘-Werror=format-security’ ‘-Wformat’

Any idea how we could get rid of it?
Output of the R CMD check:
R CMD check results
0 errors | 3 warnings | 4 notes
checking for missing documentation entries ... WARNING
Undocumented code objects:
  ‘AnyNA’ ‘DayOfWeek’ ‘NumNA’ ‘Predetermined.d’ ‘Predetermined.m’
  ‘Y_sub’ ‘mlDFM’
All user-level objects in a package should have documentation entries.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.

checking Rd \usage sections ... WARNING
Undocumented arguments in documentation object 'BDFM'
  ‘Bp’ ‘Hp’ ‘ITC’

Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.

checking compilation flags used ... WARNING
Compilation used the following non-portable flag(s):
  ‘-Wdate-time’ ‘-Werror=format-security’ ‘-Wformat’

checking for hidden files and directories ... NOTE
Found the following hidden files and directories:
  .travis.yml
These were most likely included in error. See section ‘Package
structure’ in the ‘Writing R Extensions’ manual.

checking installed package size ... NOTE
  installed size is  7.8Mb
  sub-directories of 1Mb or more:
    libs   7.6Mb

checking top-level files ... NOTE
File
  LICENSE
is not mentioned in the DESCRIPTION file.

checking R code for possible problems ... NOTE
Predetermined.d: no visible global function definition for ‘head’
Predetermined.d: no visible global function definition for ‘tail’
Predetermined.d: no visible global function definition for ‘dnorm’
Predetermined.d: no visible binding for global variable ‘holiday’
Predetermined.m: no visible binding for global variable ‘holiday’
Predetermined.m: no visible global function definition for
  ‘End_Next_Month’
SeasAdj_WE: no visible global function definition for ‘var’
Y_sub: no visible global function definition for ‘na.omit’
mlDFM: no visible global function definition for ‘na.omit’
mlDFM: no visible global function definition for ‘Matrix’
mlDFM: no visible global function definition for ‘Diagonal’
mlDFM: no visible global function definition for ‘sparseMatrix’
Undefined global functions or variables:
  Diagonal End_Next_Month Matrix dnorm head holiday na.omit
  sparseMatrix tail var
Consider adding
  importFrom("stats", "dnorm", "na.omit", "var")
  importFrom("utils", "head", "tail")
to your NAMESPACE file.
Warning message:
roxygen2 requires Encoding: UTF-8

Not at all sure where
Compilation used the following non-portable flag(s):
  ‘-Wdate-time’ ‘-Werror=format-security’ ‘-Wformat’

but I'll thrash around in the files a bit and see if I can figure it out. The Rcpp build generates a lot of stuff, so it might be something in there... we'll see.

I did not see it on travis, so this may be just something of my local linux installation. Don't worry for the moment.
But we need to fix the other two warnings.


added new header

I made this change when playing on Windows a few nights ago. Still somehow missed it in the review.


Neocomplete invasively changes behavior of Enter and Esc keys

Background: Debian Jessie, stock vim, fresh install under new user, multiple separate systems. I haven't tested extensively for whether it's spf13 integration fault or inherent neocomplete problem though.
When neocomplete encounters a line, that has snippets available, instead of silently nooping on , it inserts "(neosnippet_expand)" string instead.
In addition to that, when there is a neocomplete popup present,  key behaviour gets modified: instead of returning vim to normal mode, it returns vim to normal mode and activates insert mode with a brief delay, reactivating popup. Depending on connection speed sometimes it means that it's impossible to exit said popup prompt without killing vim.

I am having a somewhat relevant problem, so I am not opening a new issue.
First of all when I type and a snippet is available (lets say main for a c file), I get the popup but when I hit tab and enter I get:
main(neosnippet_expand)
Of course if I hit Control + K I get the proper snippet and the (main) autocomplete works.
Have you tried hitting C - k instead of enter?
Secondly, I am having another problem with autocomplete.
When I type something and a suggestion pops (not a snippet), the autocomplete should work as:
Hit tab and enter and the word will autocomplete.
When I hit tab I get the word autocomplete, as it should, but when I hit enter to choose the proper autocomplete, vim gets me back to the word as I wrote it before the autocomplete popped (as if nothing happened).
For example:
I open .vimrc.local and I write: "colorscheme twili"
and now opens the autocomplete popup, I hit two tabs to get "twilight256" so now vim has:
"colorscheme twilight256"
Then I hit enter and now vim has:
"colorscheme twili"
I got it to wok by hitting tab, writing a letter and then hitting backspace, but it gets disturbing.
Any suggestions especially for the second issue?

Having the same issue since I update spf13 and bundles.
Probably related to https://github.com/spf13/spf13-vim/issues/775 and https://github.com/Shougo/neocomplete.vim/issues/347

I think this configuration from vim multiplecursors page should go into spf13 default configuration (this solved the problem for me):
" Called once right before you start selecting multiple cursors
function! Multiple_cursors_before()
  if exists(':NeoCompleteLock')==2
    exe 'NeoCompleteLock'
  endif
endfunction

" Called once only when the multiple selection is canceled (default <Esc>)
function! Multiple_cursors_after()
  if exists(':NeoCompleteUnlock')==2
    exe 'NeoCompleteUnlock'
  endif
endfunction

Try my configuration of NeoComplete, in my fork ;-)

@FiloSpaTeam could you point me where is it?

I too am having the issue that tchar is having. It's literally the most frustrating thing at the moment.

Any updates on this issue? I'm having the same problem pointed by @tchar.
@FiloSpaTeam I looked in your github repository and didn't find your fork =/
@rodfersou you can give me more details of how you solved this problem by using the  multiplecursors snippet code ?


No mention of thread-local variables in "Getting started" guide

The Future trait uses a thread-local variable to track the current task. This should be discussed in the "Getting started" guide as it is a common question.

Do we think there needs to be discussed in depth? It seems like this would be a good thing for an "aside" where we say "by the way, the current task is kept track of in a thread local variable. If you want to know more, check out this internals guide with more information". I think the getting started guide should really focus on usage, and reserve answering any burning questions about implementation in asides.


Semver-incompatibility

Looks like there are issues when the Bundle-Version is specified by using the semver form M.m.b+timestamp, more precisely by having in the bnd file the form 1.0.0+${tstamp}.
Sorry for the horribly brief description. If you need more details I could look into it better.

hey @yuchi having a + as the separator between the micro and qualifier is not supported by OSGi. The only legal separator is .
i.e. 1.0.0.${tstamp}

That's what I feared. Then why is it the standard value in the bnd.bnd file built by blade create. Gonna investigate more. Thanks @rotty3000

My bad, it's me that changed the form into the semver complaint one.


Branch1

Hi  @MehaKaushik is this PR still relevant?

Hey it isn't. Thanks for reminding me of this @isra-fel


How to get links to all calendar/tag pages

Expected behaviour

I'd like to display links to all other pages on the calendar/tag pages within a given calendar/tag page.

Actual behaviour

I'm only able to obtain prev_page and next_page links, and can't figure out a clean interface by which to obtain links to all of the other pages.

Additional information

Ruby version: 2.3.8
Middleman version: 4.3.4
Middleman Blog version: 4.0.3
OS version: macOS 10.14.5

Looks like you are right, that data for the full set is never captured or shared with templates:
It kind of happens here:
https://github.com/middleman/middleman-blog/blob/master/lib/middleman-blog/paginator.rb#L51-L64
Where would it make sense to share that data? Along side prev_page and next_page variables? I can refactor things to make that possible.

I started to look into making a variable called page_list that would just contain an array of all of the resources. I did find exactly that section of the code and that's where I started making changes.
What I managed to do was to hack together a helper that would keep wandering through prev_page and next_page until there were none left. So I would keep accessing current_resource.locals['prev_page'] and building up an array as I walked through. It was pretty hacky but it worked without me needing to change any code in middleman-blog.
If this is a pretty fringe request I don't mind if you close it off given that there is a workaround -- it just took me quite a while to try to figure out how I could get a list of all the pages and I felt like other people might also want to do that.

That's clever. Can you put your solution code here for future folks searching for this?

Yep -- I should be able to post something tonight. I'll edit this comment with the general idea.

ℹ This issue is stale because it has been open for more than 90 days with no activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.


Resetting of search value doesn't work

Old ticket: https://github.com/swiss/styleguide/issues/306
Description: IE 10 renders an extra "X". Pressing the "X" does only delete the value, if you start typing right after you clicked the "X". If you enter something, then press "X" and then leave the field, the entered value is still going to be present
Browsers affected: IE 10
Screenshot:

Thank you. We'll look into this one.

Is being worked on in PR #346


Can no longer load a model from a memory buffer.

I have just upgraded my xgboost package from 0.90 to 1.0.1. I noticed I can no longer load a model from a memory buffer despite the Booster.load_model() parameters suggesting I can. Please can this be looked into?

@slarge1 The issue is fixed in 1.0.2 release.


Fix bug in axes

List of Changes

Change parameters provided to CoordinateSystem.__init__ from self,**kwargs to self

Motivation

CoordinateSystem is an abstract class and only takes in its dim/dimension as a parameter for initialisation. By having **kwargs it causes an error on trying to pass additional parameters to Axes.
Explanation for Changes

Removes **kwargs and makes everything work like its supposed to.
The rest are just merges from master, don't know if they'll effect anything.
Acknowledgement

[x] I have read the Contributing Guidelines

The black check is pointing out files not relevant to this PR, so I'm ignoring them for now. Must have been something to do with the master-merges.

I guess this does not need a test, what do you think ?

Yep, that's why I omitted that section.

Feel free to merge if you think black is being silly.

I just wanted to confirm if this won't mess up anything due to the merges, messing up the commit history and stuff.


Pull names of ontology terms into enhanced simulation submission form

Can be done once #2354 is completed

Done. Duplicate code for pulling ontology terms should still be moved to a shared library.