Enable filenames with colon (:) on drvfs

Insider build 14986
Trying to create a filename with a colon on a drive mounted with drvfs is not working whereas I can create the file on lxfs:
$ mount | grep home
home on /home type lxfs (rw,noatime)

$ touch foo+bar:0185.somext

$ ls -l
-rw-rw-rw- 1 doehrm doehrm 0 Dec 16 23:26 foo+bar:0185.somext

$ mount | grep \/e
E: on /mnt/e type drvfs (rw,noatime)

$ touch foo+bar:0185.somext
touch: setting times of 'foo+bar:0185.somext': No such file or directory

$ echo "Foo Bar" > foo+bar:0185.somext
bash: foo+bar:0185.somext: Invalid argument

$ echo "Foo Bar" > foo+bar\:0185.somext
bash: foo+bar:0185.somext: Invalid argument

The drive connected is an external USB drive formatted with NTFS
Am I missing something?
--
Markus

Unfortunately NTFS defines a set of reserved characters, while Unix-ish filesystems (ext, zfs, hfs), on which "/" is the only special character. Part of that is because of Microsoft still being tied to the boat anchor that is DOS.
As an aside, Unix is tied somewhat to the boat anchor that is bash, and ":" is de-facto problematic also; because, there is no way to escape ':' in a PATH environment variable. Curious what your use case is, because you pretty much have to avoid ':' on Linux too (but by convention only).
https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx

The use case is "chromium-os" ;-)
I build a special version for an older laptop of mine. The official build host is an Ubuntu 16.04.1. The whole build is done in a chroot'ed environment so basically only a few tools need to be installed on the OS (python, git, curl and a few others), the rest is downloaded and compiled in the chroot.
While downloading the repository descriptions I come across a few files that cannot be sync'ed because of the colon:
error: unable to create file frontend/client/src/autotest/public/Open+Sans:300.woff (Invalid argument)
error: unable to create file frontend/client/src/autotest/public/Roboto+Bold:700.woff (Invalid argument)
error: unable to create file frontend/client/src/autotest/public/Roboto+Light:300.woff (Invalid argument)
error: unable to create file frontend/client/src/autotest/public/Roboto+Medium:500.woff (Invalid argument)
error: unable to create file frontend/client/src/autotest/public/Roboto+Regular:400.woff (Invalid argument)
error: unable to create file server/site_tests/display_EdidStress/test_data/edids/weekly/SCT_272_STEELCASE_m:s_HDMI.txt

The original sources really contain that colon:
https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/frontend/client/src/autotest/public
My aim was to have a "somewhat native" possibility to compile a new version on my laptop rather than to have Hyper-V and virtual network cards and switches messing with my non-trivial network/VPN setup (if you ever set up half a dozen VPNs (SSTP, OpenVPN and PPTP mixed with ipv4/ipv6) and you install Hyper-V and you wonder, why nothing is working any more, you'll understand ;-) )
But I understand that it'd be problematic allowing it, despite I'm not looking to have it as a directory name but "just a file name".

Tangent -- : was the Mac path separator prior to OS X.  Graphical Mac applications still allow filenames to contain / and not :.  Basically, : is weird everywhere.
Anyway, it's an interesting question whether DrvFs should (for compatibility purposes) be allowed to construct filenames that wouldn't be allowed for regular Windows applications, and if so, what the semantics of such files should be.

@doehrm -- can you not build in WSL's $HOME?  As you mention, it works.  And it should have better performance as well.

I still work on an OS that has filenames such as NODE::DKA0:[FOO.BAR.BAR2]foobar.dat;5 where a colon is a separator, no possibility to create a filename with a colon there and I guess, that's also where deep in the Windows (NT 4.0) kernel it [was|is] forbidden too.
And yes, I'll try that next - as soon as I can get rid of some older insider builds still stored on the disk and make some space.

Interestingly enough, I could clone the repository using GIT on Windows:
C:\Users\curry\test>..\Git\bin\git.exe clone https://chromium.googlesource.com/chromiumos/third_party/autotest
Cloning into 'autotest'...
remote: Sending approximately 434.56 MiB ...
remote: Counting objects: 9793, done
remote: Finding sources: 100% (16/16)
remote: Total 177259 (delta 128226), reused 177251 (delta 128226)
Receiving objects: 100% (177259/177259), 434.38 MiB | 698.00 KiB/s, done.
Resolving deltas: 100% (128226/128226), done.
Checking out files: 100% (9006/9006), done.

and it seems there is some sort of semantics already existing:
c:\Users\curry\test\autotest\frontend\client\src\autotest\public>dir /r
 Volume in drive C has no label.
 Volume Serial Number is 8203-5049

 Directory of C:\Users\curry\test\autotest\frontend\client\src\autotest\public

17.12.16  02:01    <DIR>          .
17.12.16  02:01    <DIR>          ..
[...]
17.12.16  02:01                 0 Open+Sans
                           21 744 Open+Sans:300.woff:$DATA
17.12.16  02:01                 0 Roboto+Bold
                           19 812 Roboto+Bold:700.woff:$DATA
17.12.16  02:01                 0 Roboto+Light
                           21 080 Roboto+Light:300.woff:$DATA
17.12.16  02:01                 0 Roboto+Medium
                           20 636 Roboto+Medium:500.woff:$DATA
17.12.16  02:01                 0 Roboto+Regular
                           21 132 Roboto+Regular:400.woff:$DATA
[...]
              21 File(s)         66 494 bytes
               2 Dir(s)  46 544 334 848 bytes free

A plain dir shows the first line (size 0, short filename up to the colon), dir /r reveals the complete name with a "$DATA" at the end.

@therealkenc The real reason doesn't have anything to do with DOS iirc.  The ":" character is reserved for alternate data streams in ntfs.

I'd not say OS/2 but rather VMS (OpenVMS). Windows and VMS share quite a few things (http://www3.sympatico.ca/n.rieck/docs/Windows-NT_is_VMS_re-implemented.html).

I was now able to download all the code to $HOME. When I try to enter the chroot the system either freezes (and I have to hard reboot) or BSODs  :-( with APC_INDEX_MISMATCH.
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1, {7fce84d0c357, 0, 1, ffffc701f5f0dc80}

Page 10ad38 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntkrnlmp.exe ( nt!KiSystemServiceExitPico+194 )

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

APC_INDEX_MISMATCH (1)
This is a kernel internal error. The most common reason to see this
bugcheck is when a filesystem or a driver has a mismatched number of
calls to disable and re-enable APCs. The key data item is the
Thread->CombinedApcDisable field. This consists of two separate 16-bit
fields, the SpecialApcDisable and the KernelApcDisable. A negative value
of either indicates that a driver has disabled special or normal APCs
(respectively) without re-enabling them; a positive value indicates that
a driver has enabled special or normal APCs (respectively) too many times.
Arguments:
Arg1: 00007fce84d0c357, Address of system call function or worker routine
Arg2:<PHONE_NUMBER>000000, Thread->ApcStateIndex
Arg3:<PHONE_NUMBER>000001, (Thread->SpecialApcDisable << 16) | Thread->KernelApcDisable
Arg4: ffffc701f5f0dc80, Call type (0 - system call, 1 - worker routine)

Debugging Details:
------------------

Page 10ad38 not present in the dump file. Type ".hh dbgerr004" for details

FAULTING_IP:
+8c0
00007fce`84d0c357 ??              ???

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
BUGCHECK_STR:  0x1
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff80084d60929 to fffff80084d55240

STACK_TEXT:
ffffc701`f5f0dab8 fffff800`84d60929 : 00000000`00000001 00007fce`84d0c357 00000000`00000000 00000000`00000001 : nt!KeBugCheckEx
ffffc701`f5f0dac0 fffff800`84d6082b : ffffc701`f5f0dc00 ffffb703`396c6200 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffc701`f5f0dc00 00007fce`84d0c357 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x194
00007fff`ce8dcf98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fce`84d0c357

STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!KiSystemServiceExitPico+194
fffff800`84d6082b 4883ec50        sub     rsp,50h

SYMBOL_STACK_INDEX:  2
SYMBOL_NAME:  nt!KiSystemServiceExitPico+194
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nt
IMAGE_NAME:  ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP:  58427289
BUCKET_ID_FUNC_OFFSET:  194
FAILURE_BUCKET_ID:  0x1_SysCallNum_0_nt!KiSystemServiceExitPico
BUCKET_ID:  0x1_SysCallNum_0_nt!KiSystemServiceExitPico
ANALYSIS_SOURCE:  KM
FAILURE_ID_HASH_STRING:  km:0x1_syscallnum_0_nt!kisystemserviceexitpico
FAILURE_ID_HASH:  {48293086-2975-82e2-87d1-2bab5cd63ecf}

I switched on a full dump and will reproduce the problem again (if that helps).

@doehrm Please email<EMAIL_ADDRESS>ATTN: Ben Hillis or Russ Alexander with a copy of a minidump.

Done so, thanx @fpqc for pointing me in the direction and sorry for messing this issue up with nonrelated BSOD's.
Since NTFS seems to have a way to handle those files, doesn't/couldn't/shouldn't that mean DrvFS should too?

@doehrm The path "a:b" refers to an alternate data stream of the file "a" on NTFS.  It is not a valid path.

or it's internally "mapped" to a Unicode character (U+F000 - U+F0FF)...

The result of your dir /r indicates that alternate data streams were stored.

@doehrm - I received your dump and took a look. The cause of the bluescreen was a locking issue in a terminal ioctl. The fix just reached the rs_prerelease branch so it should be in the next Windows Insider build.

Thanks for reporting. Closing since this issue should have been fixed in an insider build in early 2017, and there's been no recent activity on this issue.

@bitcrazed is this "fix" in the creators update too? If so, is it allowed to have a filename with colon on an NTFS partition and be accessible from WSL?

No, it was just closed incorrectly.

Thanks @therealkenc Maybe dev wouldn't mind if I open a new one to get some clarity here..

@SRGOM Repurpose your #2061 by changing the title. I didn't say anything at the time this was closed because I knew someone would report a dupe eventually (this issue was closed 9 days after #1828 was marked as a dupe). I don't know the chances/timeframe for this being supported because it will probably take some cooperation from the NTFS win32 side people which might or might not be forthcoming. Notwithstanding Cygwin style hacks anyway, which I suppose could be a reasonable enough approach in the absence of alternatives.

Well I created https://github.com/Microsoft/BashOnWindows/issues/2070 (and closed #2061). I'd love to have this feature but what I'm actually looking for is clarity- Since Rich says that this has already been implemented, maybe a reg switch is all that I need?

Rich probably just conflated the terminal ioctl related Blue Screen being squashed above with the issue title. A reg switch to turn on and off filename colon support in DrvFS would make no sense, and even if it did, it wouldn't be a secret switch. And... if it were a secret switch... well... those in the know would be sworn to secrecy... wouldn't they.

Reopening until the win32 reserved characters (: ? etc) fix lands so this can get a fixedinsiders tag. Which I gather might be forthcoming.

@therealkenc - Thanks, didn't realize this one was closed.

The reserved character issue should be resolved as of Insiders Build 17101.

I have Windows 10 Pro N (1803, build: 17101.1000)
Looks like now it is possible to create file with colon in name on / (rootfs) and on /mnt/<letter>
Still I have some problems with colons on /mnt/<letter>
I run simple script that connects to my remote host with Debian and performs backup. The script is based on rsync. On the server I have some services, one of them are Dovecot/Postfix servers.
The files that represent email have complex names like:
.1519283136.M726136P495.articode.pl,S=23068,W=23405:2,Sc.KXvFzt
When I run my script from rootfs all works fine. But when destination location to save is some folder inside /mnt/<letter> then rsync try to make some strange rename actions on not existing files.
Example:
rsync: rename "/mnt/e/articode.pl/current/mail/articode.pl/biuro/.Trash/cur/.1519283136.M726136P495.articode.pl,S=23068,W=23405:2,Sc.KXvFzt" -> "articode.pl/biuro/.Trash/cur/1519283136.M726136P495.articode.pl,S=23068,W=23405:2,Sc": No such file or directory (2)
Oryginal rsync parameters:
rsync -az -e ssh --delete --rsync-path="sudo rsync" "${REMOTE_LOGIN}@${REMOTE_SERVER}:/var/mail/" "${BACKUP_DIR}/current/mail/"

I guess this made 1803 after all (17101 < 17134)


Support to download partial videos

Hey,
I am trying to download 10 second video clips from long videos. I don't think pytube supports this yet.
A function of the type yt.crop(start_time, end_time).download() will be really helpful if it is integrated with the library.

My overly simplistic solution was to save a copy of the file when it got to the number of bytes I was looking for.  I did this the show_progress callback.
What I haven't figured out is how to terminate the download at that point.
The wild-shot of raising StopIteration didn't do it.

I think it's possible using ffmpeg.
ffmpeg -ss (start time) -i (direct video link) -t (duration needed) -c:v copy -c:a copy (destination file)

direct video link can be obtained from yt.player_config_args


fix(tasks/compat_data): fix misplaced features

closes #7279

#7284  👈
main

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

Join @Boshen and the rest of your teammates on  Graphite


Add ore bag area pickups

Apparently it does it in 13.
https://github.com/space-wizards/space-station-14/assets/31366439/aedc4ed3-4cb0-4a18-a112-63bd5309befa
:cl:

add: Added automatic area pickups to ore bags.

fixes #17949 :trollface:

fixes #17949 :trollface:

noob

no, pro

doesnt do the pickup animation? i think it might not be obvious enough whats happening. should probably have a description change as well + maybe guidebook

Do you have any suggestions as item pickup animations were not built to handle entities being deleted the same tick.

could that not spawn a client copy and then run animation on that, deleting it when its over

could that not spawn a client copy and then run animation on that, deleting it when its over

That is how pickup animations work but the code is scrungly bungly and I am like 60% sure will just die because the entities are immediately deleted (i.e. where stack stuff is picked up).

Gonna need to refactor storagesystem entirely for this to be predicted so will come back to itTM.

doesnt do the pickup animation? i think it might not be obvious enough whats happening. should probably have a description change as well + maybe guidebook

I did all that except guidebook coz I've never done it and uhhhh not sure where it'd go.


Ragged reduce_variance returns negative value & reduce_std -> NaN

Click to expand!
This is not a contribution.
Issue Type
Bug
Source
binary
Tensorflow Version
2.9
Custom Code
No
OS Platform and Distribution
Linux, macOS
Mobile device
No response
Python version
3.7
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
The implementation of `tf.math.reduce_variance` for ragged tensors is not constrained to be non-negative. Also as this subroutine is used in `tf.math.reduce_std`, this causes NaNs when trying to `sqrt` the negative value.

Standalone code to reproduce the issue
import tensorflow as tf
c = tf.ragged.constant([[[0.214441], [0.214441], [0.214441], [0.214441], [0.214441], [0.214441], [0.214441]]], inner_shape=(1,))
tf.math.reduce_variance(c, axis=1)
>>> <tf.Tensor: shape=(1, 1), dtype=float32, numpy=array([[-1.1175871e-08]], dtype=float32)>
tf.math.reduce_std(c, axis=1)
>>> <tf.Tensor: shape=(1, 1), dtype=float32, numpy=array([[nan]], dtype=float32)>

Relevant log output
No response

@peteboothroyd Could you please have a look at this gist and confirm the issue?
Thank you!

@sushreebarsa yes that's the issue


Comments stripped from Schema?

Haven't really looked at it too much, but for whatever reason comments seem to get stripped out of the SDL entirely.

I dug in slightly further, it appears that when using import typeDefs from '~/schema.graphql'; that it strips comments, but if you use the file string directly it does not. So I guess something somewhere is stripping things.

Yep, that is the problem:
GraphQLLoaderPlugin({
      mapDocumentNode: (documentNode) => {
        return optimizeDocumentNode(documentNode); // <----- the default optimizers strip out comments
      }
    }),

Fixing it is as simple as:
return optimizeDocumentNode(documentNode, [removeEmptyNodes, removeLoc]);

Marking as "resolved" since it really isn't the fault of the framework here.


Unload function

https://github.com/EquiFox/KsDumper/blob/master/KsDumperDriver/Driver.c#L100
function signature should be with NTSTATUS return val (not required to return something actually).
Also:
https://github.com/EquiFox/KsDumper/blob/master/KsDumperDriver/Driver.c#L105
It's better make the symLink global and you are deleting wrong link anyway, it should be the one with "Dos" in the name. If have time, i'll make a pull request.

Thanks for spotting this one !
My bad, totally missed it.


User: XXX because no identity-based policy allows the cognito-idp:GetGroup action

Environment information
0 verbose cli C:\Program Files\nodejs\node.exe C:\Users\Eduardo\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 silly config load:file:C:\Users\Eduardo\AppData\Roaming\npm\node_modules\npm\npmrc
4 silly config load:file:F:\Projects\pensionflow\.npmrc
5 silly config load:file:C:\Users\Eduardo\.npmrc
6 silly config load:file:C:\Users\Eduardo\AppData\Roaming\npm\etc\npmrc
7 verbose title npm exec ampx info
8 verbose argv "exec" "--" "ampx" "info"
9 verbose logfile logs-max:10 dir:C:\Users\Eduardo\AppData\Local\npm-cache\_logs\2024-10-18T11_38_01_308Z-
10 verbose logfile C:\Users\Eduardo\AppData\Local\npm-cache\_logs\2024-10-18T11_38_01_308Z-debug-0.log
11 silly logfile start cleaning logs, removing 1 files
12 silly logfile done cleaning log files
13 silly packumentCache heap:4345298944 maxSize:1086324736 maxEntrySize:543162368
14 http fetch GET 200 https://registry.npmjs.org/ampx 775ms (cache miss)
15 verbose stack Error: could not determine executable to run
15 verbose stack     at getBinFromManifest (C:\Users\Eduardo\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\get-bin-from-manifest.js:17:23)
15 verbose stack     at exec (C:\Users\Eduardo\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\index.js:202:15)
15 verbose stack     at async Npm.exec (C:\Users\Eduardo\AppData\Roaming\npm\node_modules\npm\lib\npm.js:207:9)
15 verbose stack     at async module.exports (C:\Users\Eduardo\AppData\Roaming\npm\node_modules\npm\lib\cli\entry.js:74:5)
16 verbose pkgid<EMAIL_ADDRESS>17 error could not determine executable to run
18 verbose cwd F:\Projects\pensionflow
19 verbose os Windows_NT 10.0.22631
20 verbose node v20.17.0
21 verbose npm  v10.8.3
22 verbose exit 1
23 verbose code 1
24 error A complete log of this run can be found in: C:\Users\Eduardo\AppData\Local\npm-cache\_logs\2024-10-18T11_38_01_308Z-debug-0.log

Describe the bug
I created a new env and i tried to push the backend to it. Resulting in the following error: Resource handler returned message: "User: arn:aws:sts::XXXXX:assumed-role/eu-central-1_K3YXJVKQN_Full-access/amplifyadmin is not authorized to perform: cognito-idp:GetGroup on resource: arn:aws:cognito-idp:eu-central-1:XXXXX:userpool/eu-central-1_He0G2wrhm because no identity-based policy allows the cognito-idp:GetGroup action (Service: CognitoIdentityProvider, Status Code: 400, Request ID: abfcf153-b16b-44a8-85a7-84ead72265a6)" (RequestToken: 6b86c0b7-4b2a-ce88-1139-b91d18ccd86c, HandlerErrorCode: GeneralServiceException)
Reproduction steps
amplify push

Hey @GenGraphic, thank you for reaching out. It appears the eu-central-1_K3YXJVKQN_Full-access role is trying to perform a GetGroup on a Cognito userpool resource. To mitigate the issue, you should be able to add the cognito-idp:GetGroup as an inline policy on the eu-central-1_K3YXJVKQN_Full-access role in the AWS IAM console.

Hi @ykethan. Thank you for the fast reply, this is much appreciated. what we are trying to do is to duplicate our production env, and use it as development env. I created the new env and i get this error while trying to push the backend to the new created env. So a new user pool is created (along with functions, Tables, S3), and trying to get and create a new AdminsGroup (like we have on our prod env). So adding an inline policy is the fisrt thing i tried, but i cant give it the right Resource, since the i don't know the new user pool ARN because it doesn't exist yet. Tank you!

@GenGraphic since the new resource name would contain a random hash value, adding the inline policy may not be idea.
but you could try adding the cognito-idp:GetGroup action similar to the managed policy for Amplify.
https://docs.aws.amazon.com/aws-managed-policy/latest/reference/AdministratorAccess-Amplify.html

@ykethan Thanks for your Replay. I already gave the role Administrator policy, this means the role should have full access. I managed to solve the problem by adding the cognito-idp:GetGroup and cognito-idp:AddGroup to all resources (this included also the future ones) and the new env got successfully created.


Potential issue related to AWS SDK 3.2

Hi,
I have updated config today to make a new docker build and I got the error:
2017-09-05 14:47:19 +0000 [error]: unexpected error error_class=NameError error=#<NameError: uninitialized constant Aws::CloudWatchLogs>
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.0/lib/fluent/plugin/out_cloudwatch_logs.rb:69:in `start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/agent.rb:71:in `block in start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/agent.rb:70:in `each'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/agent.rb:70:in `start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/root_agent.rb:108:in `start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/engine.rb:237:in `start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/engine.rb:187:in `run'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:570:in `run_engine'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:162:in `block in start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:366:in `main_process'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:339:in `block in supervise'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:338:in `fork'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:338:in `supervise'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/supervisor.rb:156:in `start'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/lib/fluent/command/fluentd.rb:173:in `<top (required)>'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  2017-09-05 14:47:19 +0000 [error]: /usr/lib/ruby/gems/2.3.0/gems/fluentd-0.12.35/bin/fluentd:5:in `<top (required)>'
  2017-09-05 14:47:19 +0000 [error]: /usr/bin/fluentd:22:in `load'
  2017-09-05 14:47:19 +0000 [error]: /usr/bin/fluentd:22:in `<main>'

comparing my current build with old builds (which are working perfectly) I noticed that during installation it did install aws-sdk-core-3.2.0 while old builds install aws-sdk-core-2.10.31
Could it be the issue?

https://aws.amazon.com/blogs/developer/aws-sdk-for-ruby-modularization-version-3-2/
v3 requires gems for each service to be explicitly required.

that means we need to strict aws-ask in gemspec file to ~>2.0? I have forked the repo and trying this at the moment.
is there a better solution? sorry I'm not a ruby dev.

Yes.
For example: https://github.com/sampointer/fluent-plugin-cloudwatch-ingest/blob/master/fluent-plugin-cloudwatch-ingest.gemspec#L36

I've moved onto the plugin above as this plugin doesn't seem to get much pull-request love. I therefore don't have the means to test my PR. I'm sure if you submit a PR it'll be fine.

Fair enough. Thanks a lot for confirming the bug. I will submit a PR in case someone faced the same error.

Hi, since I need to use v3 to work with other plugins, there's just two changes that need to be done, 1. install the aws-sdk-cloudwatchlogs gem and 2. adding a require aws-sdk-cloudwatchlogs to the out_cloudwatch_logs.rb, is this possible?

Thanks for the tip, @liche60 !
I've submitted a PR if @ryotarai wants to move to v3.

fyi) I got the same error by fluent-gem install fluent-plugin-s3


[Question] Duplicate child key found! This will cause problems in ReactGridLayout.

ReactGridLayout is automatically creating duplicate keys.
componentWillReceiveProps (nextProps) {
  if (nextProps.fetched && !this.props.fetched) {
      const layout = _.map(nextProps.regions, region => {
        return {
          x: toInteger(region.left),
          y: toInteger(region.top),
          h: 2,
          w: 1,
          maxH: 40,
          static: true,
          isDraggable: false,
          isResizable: false,
          i: toString(region.region_id)
        }
      });
     console.log('my layout', { layout: { lg: layout, md: layout }});
     this.setState({ layout: { lg: layout, md: layout }} );
  }
}

and i have a onLayoutChange callback
onLayoutChange (layout, layouts) {
    console.log('onLayoutChange', layout, layouts);
}

and in my render function
render() {
   return (
       <ResponsiveReactGridLayout
            className="layout" rowHeight={40}
            breakpoints={{lg: 1200, md: 996, sm: 768, xs: 480, xxs: 0}}
            cols={{lg: 12, md: 10, sm: 6, xs: 4, xxs: 2}}
            onLayoutChange={this.onLayoutChange} layouts={this.state.layout}
            onBreakpointChange={this.onBreakpointChange}
            verticalCompact={false} isDraggable={shouldBeDraggable} isResizable={false}
       >
       {myRegions}
     </ResponsiveReactGridLayout>
  )
}

Where am I doing wrong?

It is likely your region ids are not unique.
On Feb 11, 2017 2:16 PM, "Subham Agarwal"<EMAIL_ADDRESS>wrote:
ReactGridLayout is automatically creating duplicate keys.
componentWillReceiveProps (nextProps) {
if (nextProps.fetched && !this.props.fetched) {
const layout = _.map(nextProps.regions, region => {
return {
x: toInteger(region.left),
y: toInteger(region.top),
h: 2,
w: 1,
maxH: 40,
static: true,
isDraggable: false,
isResizable: false,
i: toString(region.region_id)
}
});
console.log('my layout', { layout: { lg: layout, md: layout }});
this.setState({ layout: { lg: layout, md: layout }} );
}
}
and i have a onLaoutChange callback
onLayoutChange (layout, layouts) {
console.log('onLayoutChange', layout, layouts);
}
and in my render function
render() {
return (
<ResponsiveReactGridLayout
className="layout" rowHeight={40}
breakpoints={{lg: 1200, md: 996, sm: 768, xs: 480, xxs: 0}}
cols={{lg: 12, md: 10, sm: 6, xs: 4, xxs: 2}}
onLayoutChange={this.onLayoutChange} layouts={this.state.layout}
onBreakpointChange={this.onBreakpointChange}
verticalCompact={false} isDraggable={shouldBeDraggable}
isResizable={false}
>
{myRegions}

)
}
Where am I doing wrong?
[image: image]
https://cloud.githubusercontent.com/assets/7915409/22851924/baf41d22-f056-11e6-8522-55fb2054389c.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/STRML/react-grid-layout/issues/481, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJFP_dtLDWpVGNVhbWh64-X7-_HAWFZks5rbWAwgaJpZM4L-GzM
.

I have checked them. They are unique. Why is it that onLayoutChange is called with a list of 25 objects when I have provided only 5?

Hi, I think the error message should definitely print the duplicated key for debugging purposes.


Document ListValueComparer breaking change

Issue or suggestion
See https://github.com/dotnet/efcore/pull/33456

@AndriySvyryd am not sure exactly which breaking change this refers to... Do you mind taking this one as reviewed the PR etc.?

This breaking change was fixed in https://github.com/dotnet/efcore/pull/34312


Add seldon v0.1.5 to use updated images

This change sets the seldon-core-operator and engine images to version 0.4.0.

/lgtm


Files should not be installed during build

There should be a separate install step, files should not be installed during build. Also:

Desktop files do not need a shebang
The desktop file and icon should not be installed to XDG_DATA_HOME when not building as user
The Exec and Icon paths reference the build directory, not where they are actually being installed:Exec=/build/huekeys/src/huekeys/huekeys menu
Icon=/build/.local/share/huekeys/icon.png

Yeah, I cringed a bit when I went that path. I'll fix it up to avoid those unless running as a standard user w/ a desktop setup.

should be fixed in v0.5.10

Well, the desktop and icon can still be generated during build. I added them manually for now.


IR Emitter Led

I know that there are many other issues about similar topics but I think that one fixed it really:
I have a Lenovo E15 with IR Emitter. My IR Emitter is working because on Windows it worked.
It seems that my cam is also working on ubuntu with sudo howdy test  even though the picture is only black. I can see 30 fps tag and really small  image changes. So it's obvious that the problem is my IR Emitter Led which is not turning on.
Simple Question:
How to say Howdy to turn on the IR Emitter Led
Nice day,
BierDav

Hello, go have a look on my repo : https://github.com/EmixamPP/linux-enable-ir-emitter.
I think you will find your answer, there everything is explained.
I remain available if you need help :smiley:


Fix typos and improve readability of README.md

"Template classes to represent vectors and matrices written in C++" -> "This project written in C++ provides template classes to represent vectors and matrices." (make the sentence complete and concise)
"Currently offers" -> "Existing features include" (gives the subject of the sentence)
(Under Motivation) re-organized the order to "learn", "extend", "apply", "test", "improve" (make things happen logically)
"test and .... correctly" -> remove "correctly" (no one all want them to be incorrect :D so just remove it)
"templated classes" -> "template classes" (small typo, template is a noun)
"are planned" -> "are on plan" (avoid using passive voice and try to make it more formal)
Made the bullets of the last part (Future) consistent

Hi, I hope it's not disturbing. I've read your repo and thank you if you could check my pull request.

Appreciate the effort, but this is still a work-in-progress right now, and I'll be overhauling the current README soon when some more functionality has been added. So unfortunately I'll be closing the pull request.


Transaction data set correctly, but action is not done

I'm getting what looks to be correct messages in console, but the action itself is not being done in the first place.
VM1659 babrahams_transactions.js?hash=8ed90df…:110 Started "update article" with transaction_id: 3zwh9dmfJyfhZ8XWB (auto started)
2VM1659 babrahams_transactions.js?hash=8ed90df…:110 Pushed update command to stack: 3zwh9dmfJyfhZ8XWB
VM1659 babrahams_transactions.js?hash=8ed90df…:110 Auto committed: 3zwh9dmfJyfhZ8XWB
VM1659 babrahams_transactions.js?hash=8ed90df…:110 Beginning commit with transaction_id: 3zwh9dmfJyfhZ8XWB

Relevant line of code: return Articles.update(query, { $set: data }, {tx: true});

Just check that the query object has an _id value set.  The transactions package ignores everything else in the query object.  That query isn't treated like a true mongo selector (at all).

The query definitely has an _id value set. Does this mean I can't undo an update to a document with multiple fields being changed?

The query object definitely has an _id value set, and it's the only value set in that object.
Any other suggestions?

Bump

Hmmm... not sure what to suggest here.  That code looks fine to me.  Note: the return value from the method shown above will not be the return value from the mongo update command, it will just be true if the transaction has been completed as expected.
If there's a minimal repro I could look at I could figure out what's going on.


Allow amenity=bureau_de_change preset to be used on buildings/areas

Only seems to work on points and vertexes at the moment.

And can we add address and opening hour fields too?

Hmm, it kind of makes sense to me if it's a building, but https://wiki.openstreetmap.org/wiki/Tag:amenity=bureau_de_change suggests that it should only be tagged on points.
Can you ask for a second opinion on tagging@ or some other channel?   From the wiki description, it reads like these are machines like ATMs, but that doesn't seem right - I've definitely seen kiosks and small shops that do this service.

I asked on IRC and have updated the wiki.

I asked on IRC and have updated the wiki.

I'm on IRC, and no you didn't ask.

@bhousel I did on channel #talk

Sorry @lakedistrictOSM I just saw it within the past hour.
I'll make the change and I'm pasting the chat here for anybody who wants to see.
8:35:18 AM lakedistrict: The wiki says that amenity=bureau_de_change can only be tagged on points. This seems incorrect so can it be changed to include areas? https://wiki.openstreetmap.org/wiki/Tag:amenity=bureau_de_change
8:35:34 AM Marc_marc: of course
8:42:43 AM ThorstenE: that doesn't sound like uk english, I thought all tags were supposed to be in uk english?
8:43:55 AM FredrikLindseth: Im not a en_gb speaker but, wikipedia claims its widely used in europe https://en.wikipedia.org/wiki/Bureau_de_change#Nomenclature
8:44:15 AM lakedistrict: We do use that term in the UK
8:45:42 AM FredrikLindseth: I tought maybe it was one of those sneaky tags like jewelry
8:46:07 AM ThorstenE: well, I haven't been to the UK except for a few day in London 10 years ago, so I don't know. But I haven't seen that term used anywhere in australia so far. Not that I'm going out of my way to look up currency exchanges...
8:52:36 AM SK53: ThorstenE: yeah it was pretty much standard when I was growing up; we use some other french words in similar contexts like passport ￼
8:53:02 AM ThorstenE: you should have done a better job keeping the Normans out...
8:54:47 AM FredrikLindseth: passport!
8:55:14 AM FredrikLindseth: I never would have guess it was not-english
8:55:21 AM FredrikLindseth: (except when I think about it)
8:57:15 AM lakedistrict: Marc_marc: Thanks, I've update the wiki
8:57:23 AM lakedistrict: *updated


Version mismatch when installing extensions in Livebook

Hey there,
Thank you for creating an Elixir client for DuckDB. Hopefully this is helpful information for you.
After failing to install the default way of installing extensions, I tried following the documentation for local installation.
Local Installation
Livebook code
Mix.install([
  {:duckdbex, "~> 0.2.5"}
])

conf = %Duckdbex.Config{allow_unsigned_extensions: true}
{:ok, db} = Duckdbex.open(conf)
{:ok, conn} = Duckdbex.connection(db)

{:ok, _} = Duckdbex.query(conn, "INSTALL 'parquet.duckdb_extension';")
{:ok, _} = Duckdbex.query(conn, "LOAD 'parquet.duckdb_extension';")

Error message
There are 2 v's in the DuckDB version causing what looks like a version check to fail.

Invalid Input Error: Extension "parquet.duckdb_extension" version (v0.9.1) does not match DuckDB version (vv0.9.1)

** (MatchError) no match of right hand side value: {:error, "Invalid Input Error: Extension \"parquet.duckdb_extension\" version (v0.9.1) does not match DuckDB version (vv0.9.1)"}
    (stdlib 5.1.1) erl_eval.erl:498: :erl_eval.expr/6
    #cell:oqbiodtkmzckg5pxjqqbx54hmbx3scm2:1: (file)

Default installation
Livebook code
Similar setup to above. Except
{:ok, _} = Duckdbex.query(conn, "INSTALL 'parquet';")

Error message
There isn't a version vv0.9.1 available from extensions.duckdb.org.

HTTP Error: Failed to download extension "parquet" at URL "http://extensions.duckdb.org/vv0.9.1/linux_amd64/parquet.duckdb_extension.gz"
Extension "parquet" is an existing extension.

** (MatchError) no match of right hand side value: {:error, "HTTP Error: Failed to download extension \"parquet\" at URL \"http://extensions.duckdb.org/vv0.9.1/linux_amd64/parquet.duckdb_extension.gz\"\nExtension \"parquet\" is an existing extension.\n"}
    (stdlib 5.1.1) erl_eval.erl:498: :erl_eval.expr/6
    #cell:sotjunmtzt7gdddxbhho643be53rftzr:1: (file)

Thank you again for your effort creating this library. If I could identify the issue in the code to contribute more I would have.

Perhaps some environment information is helpful. I'm running Livebook via Docker by executing the command:
docker run -p 8080:8080 -p 8081:8081 -v $(pwd):/data --pull always ghcr.io/livebook-dev/livebook
It's being launched from a directory that includes the downloaded parquet.duckdb_extension for DuckDB version 9.1 for my CPU architecture.

Hi! It was the bug in the DuckDb source code
Created the new release of the of duckdbex with duckdb 0.9.2 bug fix release

Amazing, thank you!

Amazing, thank you!


CRIO Annotation Hooks

Description
In the hooks document it is stated that the Annotations fields is matched against the container annotations:

List of regular expressions to match against the Annotations in the container runtime spec, if an Annotation matches the hook will be run

However, the current implementation matches the Annotation field against the sandbox annotations
Is the documented behavior incorrect or is the implementation correct?
For some context, we implemented a feature to add annotations to Containers from the Kubernetes Device Plugin.
For NVIDIA GPUs, we need to invoke our pre-start hook on containers requesting a GPU, the container behavior is preferred as some containers in a pod might not be requesting a GPU.
Thanks!

We can actually prefer containers annotation over sandboxes. Is that OK?

We can actually prefer containers annotation over sandboxes. Is that OK?

Yep :)

And by that I mean,

Look for container annotation
If there's a container annotation, use it
It there is no, fall back to sandbox annotation

That's probably a good compromise, as it wouldn't break existing clients :)
In our case we don't intend to add annotations to the sandbox, so that behavior would be a good fit.

@RenaudWasTaken https://github.com/kubernetes-incubator/cri-o/pull/1320 PTAL


Split channels to send to master (stats vs. locust things)

After about 20 minutes of running, I see boomer stop sending heartbeats to the master node. I want to split out the channels we use to see if that has an affect on heartbeats.
The next step is to put the sendMessage in its own goroutine so that we're aren't waiting for it

Codecov Report

Merging #75 into master will decrease coverage by 0.11%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master      #75      +/-   ##
==========================================
- Coverage   87.80%   87.68%   -0.12%
==========================================
  Files          10       10
  Lines         984      991       +7
==========================================
+ Hits          864      869       +5
- Misses         84       85       +1
- Partials       36       37       +1

Impacted Files
Coverage Δ

client_gomq.go
72.97% <77.77%> (-0.17%)
:arrow_down:

runner.go
85.60% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 901d7fa...133e677. Read the comment docs.

@myzhan this should be ready for review

No progress.


Many issues...

Hi,
I have many issues when using this library on Android, for instance:

fileName argument is not used to build the final filename when the directory is not "docs".
Not able to save in the user "Downloads" folder.
Application crashes when it can't create the directory to the file. It should check the result of the mkdir call in convert and return an error if it didn't succeed instead of crashing.

Is it possible to add an option to save to the user Downloads folder? Thanks.

Take a look at this PR: https://github.com/christopherdro/react-native-html-to-pdf/pull/81 and see if it helps you.

@boliveira in android default folder for downloads is "Download"(not plural).

I solved the issue by adding permission request before converting


lit: add space after -color-diagnostics

Some tests put no space after %target-swift-frontend and the flag that follows it, so we can end up with -color-diagnostics-emit-module.

@swift-ci smoke test


Responsive and Attractive footer

Adding responsiveness and attractive style to footer.
Can you assign me this issue under GSSoC with level.

Hey @Priyaaa1 I can fix this issue easily please assign this to me


Add SPO voting power table

After https://github.com/IntersectMBO/cardano-ledger/issues/4061 the voting power of SPOs is not directly related to their staking power, since proposal deposits count towards the stake reward account where they will be returned. This means that epoch_stake doesn't properly depict the spo voting power. A new table can be introduced, which includes pool_hash_id, lovelace ammount and epoch can be introduced. The spo voting power can be extracted as the result of the drep pulser.

PoolStat table has them (is not populated by default)


SmartIR Climate homekit broken

Home Assistant version
0.97.2
SmartIR version
1.7.2
SmartIR configuration
smartir:
climate:

platform: smartir
name: sala3
unique_id: sala3
device_code: 1101
controller_data: <IP_ADDRESS>
temperature_sensor: sensor.temperature
humidity_sensor: sensor.humidity
power_sensor: binary_sensor.ac_power

switch:

platform: broadlink
friendly_name: 'brmini3'
host: <IP_ADDRESS>
mac: 'C8:F7:42:F5:F3:31'

Describe the bug
The issue is only related to Homekit. I can select the temperature, but the button  "AUTOMATIC" does not perform any action on the climate entity in home assistant.
Moreover when I ask to siri: "set 23 degress on room3" homekit by default use the "automatic" switch, so the climate never starts to work.
In homekit the climate button has available the temperature and 4 different modes: OFF, WARM, COLD and AUTOMATIC.
Using them manually they all works except "automatic"
Debug log
Sat Aug 24 2019 11:51:14 GMT+0200
Error executing service <ServiceCall climate.set_hvac_mode (c:f9dd397f6cc74f31be0d8fb935042090): entity_id=['climate.sala3'], hvac_mode=heat_cool>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 1243, in _safe_execute
await self._execute_service(handler, service_call)
File "/usr/src/homeassistant/homeassistant/core.py", line 1260, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 210, in handle_service
self._platforms.values(), func, call, service_name, required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 334, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 356, in _handle_service_platform_call
await getattr(entity, func)(**data)
File "/config/custom_components/smartir/climate.py", line 299, in async_set_hvac_mode
await self.send_command()
File "/config/custom_components/smartir/climate.py", line 331, in send_command
command = self._commands[operation_mode][fan_mode][target_temperature]
KeyError: 'heat_cool'

**Additional context**

The last version that was working properly (from HomeKit) was 0.95.4 with smartir 1.5.0
I was able to discover that this issue seems to be present since the version 0.96.0 with smartir 1.6.1

Thanks in advance for any help

Are you using your own json file or one of this repo?

Are you using your own json file or one of this repo?

helllo Vassilis, thanks for your reply
I'm not using my own json (actually i don't even know how I could)
I've even tried to install hassio from scratch, just adding

platform: broadlink
platform: smartir (syntax in YAML and smartir files "1.7.2" in "custom_components")
homekit as a new bridge

The results is the same: OFF, WARM and COLD work if used by hand in homekit
Siri always fails to turn on the climate because as far as I've understood it uses the "automatic" function.
Anyway using the "automatic" button from HASSIO works properly, and the climate can be successfully turned on

Ok. Could you replace the json file under /codes/climate, restart and send me your results?
1101.zip

I've substituted the 1101.json that you sent me.
Ive restarted HASSIO and now it's working properly even from homekit and SIRI!
I've noticed that the JSON you just sent me is different from the same file conteined in the 1.7.2 "codes" folder. (lines 20 and 38, right?)
Thanks a lot for your support!
you were awesome

Yes. It seems that homekit now use heat_cool instead of auto.


Update TMC e2e tests to have them supporting multi-shard

Update TMC e2e tests to use the updated TMC fixtures correctly to support multi-shard.
Goal is to be able to remove the framework.TODO_WithoutMultiShardSupport() currently used in all the TMC e2e tests.

/transfer-issue contrib-tmc


[extractor/pbskids] Add support for pbskids.org videos

IMPORTANT: PRs without the template will be CLOSED
Description of your pull request and other information

This PR adds support for videos on the pbskids.org site.  I added it as a second extractor to the existing extractor/pbs.py, but if that's not appropriate I can split it out to its own file, it doesn't share any code with the existing extractor.
I think I found all the proper convenience methods, passes flake8
Fixes #2440
Template

Before submitting a pull request make sure you have:

[X] At least skimmed through contributing guidelines including yt-dlp coding conventions
[X] Searched the bugtracker for similar pull requests
[X] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[X] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[X] New extractor (Piracy websites will not be accepted)
[ ] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Copilot Summary

🤖 Generated by Copilot at ec225c9
Summary
🚚🧒📊

Added a new extractor for PBS Kids videos. The PBSKidsIE class in pbs.py handles the JSON data from the PBS Kids website and extracts the video formats and metadata. The class is registered in _extractors.py as a supported extractor.

To support PBS Kids videos
We imported json and traverse_obj modules
And created a new class PBSKidsIE
That parses the data and extracts the info we need
To download and enjoy the shows

Walkthrough

Add a new extractor class PBSKidsIE to handle PBS Kids videos (link)
Import json module and traverse_obj function to parse and access JSON data embedded in the webpage (link, link)
Register PBSKidsIE as a supported extractor in _extractors.py (link)
Define the URL pattern, test cases, and extraction method for PBSKidsIE (link)
Extract various metadata fields from the JSON data, such as title, description, duration, series, categories, upload_date, etc. (link)
Extract the m3u8 playlist URL and call _extract_m3u8_formats_and_subtitles to get the available formats and subtitles (link)
Return a dictionary with the extracted information (link)

Thanks for the review!

@pukkandan Could you take a look? I've got the changes in place.  Would you prefer a cleaner PR with just a single commit?

The PR will be squashed upon merge, resulting in a single commit anyways. Do not worry about commit messages and amount of commits


Help with Paginator and mdt-row

If my research serves me right, it appears that you can't use mdt-row-paginator with mdt-row.
And example of what I'm trying to do, is when an ajax request comes back, base on the query params, some columns are either displayed or not. Then, in mdt-row, I would use ng-repeat, to display the results.
Just a quick sample of what I was trying to do:
<mdt-table
    paginated-rows="{isEnabled: true, rowsPerPageValues: [5,10,20,50]}"
    mdt-row-paginator="vm.paginatorCallback(page, pageSize)"
    mdt-row-paginator-error-message="Error happened during loading nutritions."
    selectable-rows="true">
    <mdt-header-row>
        <mdt-column align-rule="left">Dessert (100g serving)</mdt-column>
        <mdt-column align-rule="right">Calories</mdt-column>
        <mdt-column align-rule="right">Fat (g)</mdt-column>
        <mdt-column align-rule="right">Carbs (g)</mdt-column>
        <mdt-column align-rule="right">Protein (g)</mdt-column>
        <mdt-column align-rule="right">Sodium (mg)</mdt-column>
        <mdt-column align-rule="right">Calcium (%)</mdt-column>
        <mdt-column align-rule="right">Iron (%)</mdt-column>
    </mdt-header-row>

    <mdt-row
        ng-repeat="nutrition in vm.nutrition.results track by nutrition._id"
        table-row-id="nutrition.id">
        <mdt-cell>{{nutrition.name}}</mdt-cell>
        <mdt-cell>{{nutrition.calories}}</mdt-cell>
        <mdt-cell>{{nutrition.fat}}</mdt-cell>
        <mdt-cell>{{nutrition.carbs}}</mdt-cell>
        <mdt-cell>{{nutrition.protein}}</mdt-cell>
        <mdt-cell>{{nutrition.sodium}}</mdt-cell>
        <mdt-cell>{{nutrition.calcium}}</mdt-cell>
        <mdt-cell>{{nutrition.iron}}</mdt-cell>
    </mdt-row>
</mdt-table>

Hi @whnunlife, yes you right.
Try to avoid mdt-row, since it will be deprecated.

Gotcha, thanks for the update @iamisti


FancyZones drop windows from second display after wakeup

Microsoft PowerToys version
0.45.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
PowerToysReport_2021-09-08-08-22-04.zip
I have 2 displays on configuration:

✔ Expected Behavior
Windows must stay on they zones.
❌ Actual Behavior
When monitors turn off by inactivity, and then turn on, windows from 2 monitor zones drops to same zones of 1 monitor.
Other Software
No response

does this issue still happen with v0.73.0? /needinfo


[Bug]: Patch not bumped

What happened?
Hello,
I enjoy Uplift because it is simple to configure, but I have a problem. Something is not working as expected. Uplift can only successfully create Minor versions (when I have a "feat:" commit for example). But for the case of Patch, it doesn't work, see logs below:
$ uplift --debug --no-push bump --prerelease beta.1
   • checking git
      • checking if git is installed
      • checking for git repo     cwd=/builds/domain.net/mint
      • checking if repository is dirty
      • checking for detached head
      • checking if shallow clone used
   • next semantic version
      • largest increment detected from commits increment=Patch
      • appending prerelease version metadata= prerelease=beta.1
      • identified next semantic version version=1.21.0-beta.1
   • building next commit
      • overwriting commit author name from uplift config
      • overwriting commit author email from uplift config
      • overwriting commit message from uplift config
      • changes will be committed with<EMAIL_ADDRESS>message=ci: bumped version [skip ci] name=Tech Team
   • bumping files
      • attempting file bump      count=0 file=./README.md regex=$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./README.md next=1.21.0-beta.1
      • attempting file bump      count=0 file=./current-version.txt regex=$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./current-version.txt next=1.21.0-beta.1
      • attempting file bump      file=./package.json path=version semver=true
      • file bumped               current=1.21.0-beta.1 file=./package.json next=1.21.0-beta.1
      • successfully staged file  file=./package.json
      • attempting file bump      count=0 file=./k8s-manifests/api-pod.yaml regex=api:$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./k8s-manifests/api-pod.yaml next=1.21.0-beta.1
      • attempting file bump      count=0 file=./k8s-manifests/db-migrator-pod.yaml regex=db-migrator:$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./k8s-manifests/db-migrator-pod.yaml next=1.21.0-beta.1
      • attempting file bump      count=0 file=./k8s-manifests/web-pod.yaml regex=web:$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./k8s-manifests/web-pod.yaml next=1.21.0-beta.1
      • bumped files staged       count=1
   • committing changes
      • no files staged skipping push

It says identified next semantic version version=1.21.0-beta.1, but it actually should be version=1.21.1-beta.1.
Anyone has a clue here ? thanks
Steps to reproduce it
Use a config similar to the one I provided, create a "fix" (edited) commit, then try to apply the uplift --debug --no-push bump --prerelease beta.1 command.
Your uplift configuration
bumps:
  - file: ./README.md
    regex:
      - pattern: "$VERSION"
        semver: true
        count: 0
  - file: ./current-version.txt
    regex:
      - pattern: "$VERSION"
        semver: true
        count: 0
  - file: ./package.json
    json:
      - path: "version"
        semver: true
  - file: ./k8s-manifests/api-pod.yaml
    regex:
      - pattern: "api:$VERSION"
        semver: true
        count: 0
  - file: ./k8s-manifests/db-migrator-pod.yaml
    regex:
      - pattern: "db-migrator:$VERSION"
        semver: true
        count: 0
  - file: ./k8s-manifests/web-pod.yaml
    regex:
      - pattern: "web:$VERSION"
        semver: true
        count: 0
commitMessage: "ci: bumped version [skip ci]"
commitAuthor:
  name: "Tech Team"
  email<EMAIL_ADDRESS>

### Which version?

The one used by gembaadvantage/uplift Docker image.

### Which operating system(s) are you using?

Linux

### Optional debug output

_No response_

### Code of Conduct

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

Hi @tony-engineering. Thanks for raising this issue. I'll take a look

Would you be able to provide me with a snapshot of your git log? I have just tried the following, and it worked as expected. I am curious as I can see that it has detected a patch but calculated the next version as a minor.
commit 6f9a84d9d1ff9e29fd113874a8b03480edafc836
Author: paul.t<EMAIL_ADDRESS>Date:   Wed Oct 5 10:46:12 2022 +0100

    docs: this is just some docs

commit d1b9027297819031d9f8c664070758e574993021
Author: paul.t<EMAIL_ADDRESS>Date:   Wed Oct 5 10:46:09 2022 +0100

    fix: a bug fix

commit ffc4c481751143efd06b8e1129e767a46312590d
Author: paul.t<EMAIL_ADDRESS>Date:   Wed Oct 5 10:46:04 2022 +0100

    ci: this is just a ci change

commit aff795b767716620582d23db3f501247d3b3e6ad (tag: v0.1.0)
Author: paul.t<EMAIL_ADDRESS>Date:   Wed Oct 5 10:43:52 2022 +0100

    feat: a new feature

Then I run uplift --debug --no-push bump --prerelease beta.1, I get the following output:
uplift --debug --no-push bump --prerelease beta.1
   • checking git
      • checking if git is installed
      • checking for git repo     cwd=/dev/github.com/gembaadvantage/uplift-bug
      • checking if repository is dirty
      • checking for detached head
      • checking if shallow clone used
   • next semantic version
      • largest increment detected from commits increment=Patch
      • appending prerelease version metadata= prerelease=beta.1
      • identified next semantic version version=v0.1.1-beta.1
   • building next commit
      • overwriting commit author name from uplift config
      • overwriting commit author email from uplift config
      • overwriting commit message from uplift config
      • overwriting commit author from git config
      • changes will be committed with<EMAIL_ADDRESS>message=ci: bumped version [skip ci] name=paul.t
   • bumping files
      • attempting file bump      count=0 file=README.md regex=$VERSION semver=true
      • trimming 'v' prefix from version
      • file bumped               current=v0.1.0 file=README.md next=v0.1.1-beta.1
      • successfully staged file  file=README.md
      • bumped files staged       count=1
   • committing changes
      • attempting to commit changes
      • staged changes committed
      • skipping push of commit to remote

Thanks for the quick reply. Our history looks like this (I checked out the commit that triggered the bump job mentioned above):
commit caa979ac7c8a8e57fb58dac82a55af64ce5b1931 (HEAD)
Merge: 37dd7ca1 1546b31b
Author: S A <>
Date:   Tue Oct 4 09:23:11 2022 +0000

    fix(web): removes SMTH from tab name

    Closes MINT-327.

    Commits:
    * removes SMTH from tab name

commit 37dd7ca15f529378f63af62b7955c16b7ca5ac64
Merge: 7f366788 90336d03
Author: S A <>
Date:   Tue Oct 4 07:32:26 2022 +0000

    docs: update the readme file with the command to reset the database migration

    .

    Commits:
    * update the readme file with the command to reset the database migration

commit 7f36678858e1c72667fa597ebe71b976c542f5ea
Merge: 5304bf66 3f39bef0
Author: C S <>
Date:   Mon Oct 3 16:53:36 2022 +0000

    fix: I made the following fields are mandatory:
    status,country,action,turbine_id

    Closes MINT-312

    Closes MINT-312.

    Commits:
    * make variableId from maintenace table optionally

    * make variableId from maintenace table optionally

Our workflow is the following (we use Gitlab):

Developer creates a branch + MR

Developer writes a meaningful description for the MR.

In the UI, when we display a commit from master (when the bump happens), it looks like this:

Awesome. Thanks for all the information. I have access to a GitLab instance, so I can try it out there.
So before that job was run, what was the current tag in the repository? Can I ask what merging strategy you use? And are you running Uplift in the same way as defined in the document: https://upliftci.dev/ci/gitlab/ ?

Here is the log output from the release job that is run at the end of the pipeline.
$ uplift --debug release --prerelease beta.1
   • checking git
      • checking if git is installed
      • checking for git repo     cwd=/builds/domain.net/mint
      • checking if repository is dirty
      • checking for detached head
      • checking if shallow clone used
   • detecting scm provider
      • parsing repository remote
      • scm provider identified   scm=GitLab
   • next semantic version
      • largest increment detected from commits increment=Patch
      • appending prerelease version metadata= prerelease=beta.1
      • identified next semantic version version=1.21.0-beta.1
   • building next commit
      • overwriting commit author name from uplift config
      • overwriting commit author email from uplift config
      • overwriting commit message from uplift config
      • changes will be committed with<EMAIL_ADDRESS>message=ci: bumped version [skip ci] name=Tech Team
   • bumping files
      • attempting file bump      count=0 file=./README.md regex=$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./README.md next=1.21.0-beta.1
      • attempting file bump      count=0 file=./current-version.txt regex=$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./current-version.txt next=1.21.0-beta.1
      • attempting file bump      file=./package.json path=version semver=true
      • file bumped               current=1.21.0-beta.1 file=./package.json next=1.21.0-beta.1
      • successfully staged file  file=./package.json
      • attempting file bump      count=0 file=./k8s-manifests/api-pod.yaml regex=api:$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./k8s-manifests/api-pod.yaml next=1.21.0-beta.1
      • attempting file bump      count=0 file=./k8s-manifests/db-migrator-pod.yaml regex=db-migrator:$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./k8s-manifests/db-migrator-pod.yaml next=1.21.0-beta.1
      • attempting file bump      count=0 file=./k8s-manifests/web-pod.yaml regex=web:$VERSION semver=true
      • skipping bump             current=1.21.0-beta.1 file=./k8s-manifests/web-pod.yaml next=1.21.0-beta.1
      • bumped files staged       count=1
   • generating changelog
      • pre-tagging latest commit for changelog creation tag=1.21.0-beta.1
      • determine changes for release tag=1.21.0-beta.1
      • no log entries between tags prev=1.21.0-beta.1 tag=1.21.0-beta.1
   • committing changes
      • no files staged skipping push
   • tagging repository
      • no version change detected current=1.21.0-beta.1 next=1.21.0-beta.1

before that job was run, the current tag in the repository was: 1.21.0-beta.1
merge strategy is this one

Commits squash is enforced.
Here is the config of the release job:
release:
  stage: release
  rules: !reference [.conditions, on_success_on_master]
  image:
    name: gembaadvantage/uplift
    entrypoint: [""]
  variables:
    GIT_DEPTH: 0
  before_script:
    - PROJECT_URL=${CI_PROJECT_URL#"https://"}
    - git remote set-url origin<EMAIL_ADDRESS>  script:
    # GitLab by default checks out a detached HEAD
    - git checkout $CI_COMMIT_REF_NAME
    # Make a beta release (this time commit new version)
    - uplift --debug release --prerelease beta.1
  dependencies: []

I see that we didnt put the rule '$CI_PIPELINE_SOURCE == "merge_request_event"', but we have this for on_success_on_master:
.conditions:
  on_success_on_master:
    - if: '$CI_COMMIT_REF_NAME != $CI_DEFAULT_BRANCH'
      when: never
    - if: '$CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH'
      when: on_success

Mh, I now realize that we might have a concurrency problem. The following could happen:

pipeline 1

bump to 1.21 (no push)
build & tag Docker images with 1.21 (take a long time, 1.21 tag still not pushed)

pipeline 2 (starts before pipeline 1 is finished)

bump to 1.21 (no push)
build & tag Docker images with 1.21 (take a long time, 1.21 tag still not pushed)

pipeline 1

push 1.21 tag

pipeline 2

push 1.21 tag

Thanks again for all the extra info above. I will add some additional logging around the calculation of the next semantic version. The bumping is deferred to another library, https://github.com/Masterminds/semver. I will try this tonight. I am aiming to release another version of uplift tomorrow morning

So having tried a couple of different tools and looked at the code and documentation associated with https://github.com/Masterminds/semver, the increment seems to behave as designed in that library.
If you patch increment a version, say 0.21.0-beta.1, it will up the version to 0.21.0, dropping the prerelease and metadata. We then append a new prerelease of beta.1, which takes us back to the existing version.
I think what is needed is an additional flag to control this behaviour better. Something like --ignore-prerelease will ensure the prerelease is not considered when calculating the next semantic version.
Will work on that change now

If you patch increment a version, say 0.21.0-beta.1, it will up the version to 0.21.0 => didnt know about that.
Thanks for the fix, Im gonna try that out now

Just to confirm: I have a branch where I made 3 commits:

the
and the bump job is still calculating a MINOR change, not PATCH change. Is that because Uplift takes in account all commits made between HEAD and the latest tag ?

Uplift scans all the commits between the latest tag and HEAD when determining the increment. It used to always just look at the latest commit, but that failed quite early on with all of the different commit strategies out there and the fact users wanted to batch a load of commits together when releasing


Verification code !!

Hello ,I tried signing up by can't receive the code ,I tried using another number and still nothing ?im from Belgium would like to know how to fix the problem please

Same thing


Iterators now respect std::iterator deprecation and are now correct...

...in terms of iterator_traits (pointer and reference are not actually uint32_t* and uint32_t& but regular uint32_t (this enables reversed_iterator among other things))

How do those "decayed" pointer and reference types work? By doing such changes you most likely made mutation basing on iterator impossible - and I imagine not making pointer_type an actual pointer will break cases where iterator is explicitly dereferenced.

Not C++ 98 compliant

Could it be streamlined though? Apparently inheriting std::iterator was never the way to go (at least according to the deprecation warning VS gives), so maybe it would be feasible to fish this change out and use a typedef instead of using? This way it should be fine.


Upgrade dotnet/docker-tool to 8fa03e2

The go-infra-images validation pipeline is currently failing because the checked in dotnet/docker-tools version is too old: https://dev.azure.com/dnceng/internal/_build/results?buildId=2431394&view=results.
This PR upgrades  dotnet/docker-tools to 8fa03e2 and updates our image pool selection accordingly.

Granted, and I went through the go-* variable groups to fix up some old permissions.

Building cbl-mariner fails due to our friend curl#60: SSL peer certificate or SSH remote key was not OK: https://dev.azure.com/dnceng/internal/_build/results?buildId=2441331&view=logs&j=fc59f0f2-c1bd-58ae-b870-833d1e8a924c&t=8d53baa0-ff68-5ea5-041a-af0e08303d7f&l=256.
@dagood you recently investigated this failure mode in another context. Any idea to get it fixed?

My first guess is that it's because we're trying to use a Mariner 1.0 image, but 1.0 is EOL so its repositories are offline (or lack cert updates, etc.). Updating to 2.0 is probably the right fix.


Invalid bitcode version

I'm trying to archive an ios project and I'm getting this error:
id: could not reparse object file in bitcode bundle: 'Invalid bitcode version (Producer: '9<IP_ADDRESS>_0' Reader: '9<IP_ADDRESS>_0')', using libLTO version 'LLVM version 9.0.0, (clang-9<IP_ADDRESS>)' for architecture armv7
It was working fine before and I didn't add or remove any library. I've downloaded 9.2 xcode version and the error is still happening. Also i've tried to remove build and derivedData folders but nothing is working. Any help please.
React Native version:
System:
OS: macOS Sierra 10.12.6
Binaries:
Node: 11.11.0 - ~/.nvm/versions/node/v11.11.0/bin/node
SDKs:
iOS SDK:
Platforms: iOS 11.2, macOS 10.13, tvOS 11.2, watchOS 4.2
Xcode: 9.2/9C40b - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.9 => 0.59.9

I finally fixed it after update xcode to 10.2.

@vgm8 If the problem was solved, you can close this issue. Thanks!


Update go-cni to v1.1.2

Fixes panic when exec is nil

Error: cannot use servertesting.NewFakeCNIPlugin() (value of type *"github.com/containerd/containerd/pkg/cri/server/testing".FakeCNIPlugin) as cni.CNI value in map literal: missing method Check (typecheck)
32
Error: c.netPlugin[defaultNetworkPlugin] (map index expression of type cni.CNI) cannot have dynamic type *"github.com/containerd/containerd/pkg/cri/server/testing".FakeCNIPlugin (missing method Check) (typecheck)
33
Error: c.netPlugin[defaultNetworkPlugin] (map index expression of type cni.CNI) cannot have dynamic type *"github.com/containerd/containerd/pkg/cri/server/testing".FakeCNIPlugin (missing method Check) (typecheck)

/retest

What is going on with e2e ci?
+ /home/prow/go/src/github.com/containerd/containerd/test/../test/push.sh
Your credentials are invalid. Please run
$ gcloud auth login
Creating gs://cri-containerd-staging/...
ServiceException: 409 A Cloud Storage bucket named 'cri-containerd-staging' already exists. Try another name. Bucket names must be globally unique across all Google Cloud projects, including those outside of your organization.

/retest

/test pull-containerd-node-e2e

will want to pick this one up too https://github.com/containerd/go-cni/commit/e559bd8b26eeb6b23c92686b808c057225ec5cfb


File -> Save As and Add Folder to Workspace has the same shortcut

VSCode Version: Code 1.18.0 (dcee2202709a4f223185514b9275aa4229841aa7, 2017-11-08T21:22:49.932Z)
OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

vscode-mocha
Com
0.1.1

vscode-eslint
dba
1.4.3

vscode-npm-script
eg2
0.3.3

auto-close-tag
for
0.5.3

code-runner
for
0.8.3

rest-client
hum
0.16.0

search-node-modules
jas
1.2.0

prettify-json
moh
0.0.3

cpptools
ms-
0.14.2

csharp
ms-
1.13.1

sublime-keybindings
ms-
3.0.3

vscode-arduino
vsc
0.2.10

nodejs-extension-pack
wad
0.1.9

JavaScriptSnippets
xab
1.5.0

(1 theme extensions excluded)

When I tried to use Alt-F, A to do a File, Save As, nothing happens. Then I found that Add Folder to Workspace has the same shortcut key of "A".
Steps to Reproduce:

Press Alt-F, then A.
Nothing happens as both File Save As and Add Folder to Workspace has the same shortcuts.

Reproduces without extensions: Yes/No

We fixed that, and will include it in our next stable update.

The latest 1.18.1 still has this issue. Both Add Folder to Workspace and File Save As are assigned "A" for the shortcut key, so I am still unable to trigger a File Save As using Alt-F, A.


Update our UAA fork to v3.7.4

Coverage decreased (-0.2%) to 83.99% when pulling 66d124190c070607bcae408f3d7d2b5a85605248 on 18F:merge-upstream-374 into be24805bcecc8756ed588608583086a4327cbe9c on cloudfoundry:master.

Coverage decreased (-0.2%) to 83.99% when pulling 66d124190c070607bcae408f3d7d2b5a85605248 on 18F:merge-upstream-374 into be24805bcecc8756ed588608583086a4327cbe9c on cloudfoundry:master.


Failed letsencrypt execution (because of different Plesk port?)

When I want to obtain a certificate, I get this error message:
`Failed letsencrypt execution: Saving debug log to /opt/psa/var/modules/letsencrypt/logs/letsencrypt.log
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for example.com
http-01 challenge for www.example.com
Cleaning up challenges
An unexpected error occurred:
ConnectionError: HTTPSConnectionPool(host='<IP_ADDRESS>', port=8443): Max retries exceeded with url: /enterprise/control/agent.php (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7f81ce33f050>: Failed to establish a new connection: [Errno 111] Connection refused',))
Please see the logfiles in /opt/psa/var/modules/letsencrypt/logs for more details.
IMPORTANT NOTES:

If you lose your account credentials, you can recover through
e-mails sent to<EMAIL_ADDRESS>Your account credentials have been saved in your Certbot
configuration directory at /opt/psa/var/modules/letsencrypt/etc.
You should make a secure backup of this folder now. This
configuration directory will also contain certificates and private
keys obtained by Certbot so making regular backups of this folder
is ideal. `

I see that something wants to connect to port 8443. The default Plesk ports are blocked on my server. I have set a specific IP and port combination in my Plesk config file, all other IPs and ports do not work. Maybe this is the problem here? Then the extension has to use the correct port (I don't know whether the localhost IP works then).

Since version 2.0 API requests are performed internally and do not depend on port.


Hot Exit forgets language mode for unsaved files

VSCode Version: 1.8.1
OS Version: Windows 10

Steps to Reproduce:

File > New File
Select Language Mode > Change to HTML (or whatever)
Make any edits to file
Quit VSCode
Open VSCode

The Untitled-1 file reopens, but the Language Mode is reset to Plain Text.  VSCode should remember the Language Mode that was set.

Duplicates #16803


Can't build dockerfile.Windows on Hyper-V containers

Yeah, I need to figure out what's going on. Can only use in Windows server containers. See https://github.com/docker/docker/pull/28261.

To clarify, the Dockerfile can be built without problem. The Docker build cannot be run inside the container (because none of the POSIX tools from Git work) when using process isolation.

This has been fixed for a while. Closing.


Hugo 0.56.0 requires modification in gallery code

Just discovered that the gallery code doesn't work with hugo 0.56.0, which sneaked in on my system through brew. Went back to 0.55.6 and all fine. With 0.56.0 a {{< gallery >}} causes:
Error: Error building site: "/Users/hartmut/Code/Web/technotecture/content/project/memlebeninteractive/index.md:30:6": failed to render shortcode "gallery": failed to process shortcode: "/Users/hartmut/Code/Web/technotecture/themes/academic/layouts/shortcodes/gallery.html:22:17": execute of template failed: template: shortcodes/gallery.html:22:17: executing "shortcodes/gallery.html" at <.Resize>: can't evaluate field Resize in type resource.Resource

There are known bugs related to image processing in Hugo v0.56.0. Also, the above error can occur with non-ASCII chars: https://discourse.gohugo.io/t/cant-evaluate-field-resize-in-type-resource-resource/9953/7

I had this issue, and the problem was that my featured image format was PNG instead of png!


Validator callback

It would be very useful to have a callback on the validation call to customize error handling.
I suggest the following:
$(form).formtools('validate', function (field, errorMsg) {
  return false; // prevents default behavior (aka adding has-error to form-group
  return true; // or nothing -> default behavior
}

I'm working on this. @nyxgear

Done in #8


typo 'hoppy'

Just look how hoppy they are! after beat all 24 courses.

Hi @delusionxb!
I believe this is intended. The frogs on the right are "hopping" (jumping).
The next line also has a similar pun "If you found this ribbeting," Ribbeting is the sound frogs make, "riveting" is the word that is being referred to.

O...K..., this is an acceptable explanation.


subdivide retinal cone cell types

From Melissa:
At some point we should have MP terms that distinguish S type cone cells from L & M type cone cells.
Not a screaming need at this time, but should be part of the hierarchy eventually.

resources
https://www.ncbi.nlm.nih.gov/books/NBK11522/
http://www.newworldencyclopedia.org/entry/Cone_cell
http://journals.plos.org/plosone/article?id=10.1371/journal.pone.0102392
https://www.ncbi.nlm.nih.gov/pubmed/16567464
Issue here is whether S/M/L cones are the same thing in all mammals or at least used in a consistent manner
S = short wavelength responsive (peak at 437nm in human, peak at 360nm in mouse)
M = medium wavelength responsive (peak at 533nm in human, peak at 508nm in mouse)
L = long wavelength responsive (peak at 564nm in human)
according to https://www.ncbi.nlm.nih.gov/books/NBK11522/ most mammals have only S and M cones so it seems like there is consistent use of these terms. Although some mouse papers use L for what would be M in human for mouse L/M cones since there are only 2 types of cones in mouse
mouse wavelengths from https://www.ncbi.nlm.nih.gov/pubmed/16567464

http://www.sciencedirect.com/science/article/pii/S0896627300000623

http://www.nature.com/nrn/journal/v11/n8/full/nrn2880.html?foxtrotcallback=true


Add ColorSerializer to Bungee's gson instance to prevent illegal reflection warnings

Users updating to Java 11 have started to commonly report warnings like these:
[Server] INFO WARNING: An illegal reflective access operation has occurred
[Server] INFO WARNING: Illegal reflective access by com.google.gson.internal.bind.ReflectiveTypeAdapterFactory (file:/cache/patched_1.16.4.jar) to field java.awt.Color.value
[Server] INFO WARNING: Please consider reporting this to the maintainers of com.google.gson.internal.bind.ReflectiveTypeAdapterFactory
[Server] INFO WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
[Server] INFO WARNING: All illegal access operations will be denied in a future release

Personally I just ignore these warnings, but for some users these warnings can cause quite a bit of confusion. I tracked the source of the warning to when I convert from Adventure to Bungee components (in order to use certain Paper APIs) using adventure-text-serializer-bungeecord on Java 9+. By registering a type adapter for java.awt.Color, we can avoid having these warnings. The adapter used in this PR is taken from here

java.awt.Color isn't actually used in adventure? (unless I've missed a usage somewhere)
It doesn't really make sense for us to provide a serializer for a type we don't use - probably best to find out what actually is using it, then PR there instead.

I agree -- if you can reproduce this reliably, you should be able to change the --illegal-access flag to give you more info:
    --illegal-access=<value>
                      permit or deny access to members of types in named modules
                      by code in unnamed modules.
                      <value> is one of "deny", "permit", "warn", or "debug"

Hope you can track it down!

Thanks for the info, I was not aware of the debug option. I've done some more testing and am able to reproduce consistently. I've included some test code and the output of using --illegal-access=debug
debug output:
https://paste.gg/p/anonymous/957711e1633f46dba970e1961f84d86a
test code:
// No warnings
final ItemStack test = new ItemStack(Material.STONE);
final ItemMeta meta = test.getItemMeta();
meta.setDisplayNameComponent(
  ComponentSerializer.parse(GsonComponentSerializer.gson().serialize(MiniMessage.get().parse("<rainbow>Test 123")))
);

// Illegal !!!
final ItemStack test1 = new ItemStack(Material.STONE);
final ItemMeta meta1 = test1.getItemMeta();
meta1.setDisplayNameComponent(
  BungeeComponentSerializer.get().serialize(MiniMessage.get().parse("<rainbow>Test 123"))
);

I am so far unable to reproduce this without using adventure-text-serializer-bungeecord, which is why I haven't opened a PR to bungee yet.


Video Thumbnail Features don't work with Scriptish

None of the video thumbnail features work with Scriptish nightly-2014-11-20-1200 (the latest nightly): no animations, quality, rating bar, rating count etc. Using Developer Build v495 on FF 36.0.4. They work as expected with Greasemonkey however.

well scriptish is outdated, so use greasemonkey instead, for chrome you can use tampermonkey.
but the real problem is Seamonkey browser, gm doesn't work there, all we have is scriptish, so we don't have a fully functional script.


Meta-class destructor is not called on exit

Reporting a bug

As stated in the title, meta-class destructors (__del__ on a meta-class instance) are not called on exit when using njit-ed functions. In the example below, Test class deleted is not printed after the script exits. The problem goes away with any of the following changes:

Removing njit decorator from njit-ed function.
Passing a scalar to njit-ed function (e.g calling jitted(1) instead of jitted(x))

Strangely, the issue also happens even if you pass a scalar to the function but define a numba.typed.List with tuple elements (shown in the commented sample).
The class destructor (__del__ on a class instance) is called (not shown in the sample code).

I don't understand well what could be happening, but I'm guessing the issue lies somewhere around the use of numba.typed.List ?

[x] I am using the latest released version of Numba (most recent is visible in
the change log (0.49.1).
[x] I have included below a minimal working reproducer.

Environment:

numba 0.49.1
python 3.7.2

import numba
# bug: meta-class destructor is not called on exit
#   (in this example, "Test class deleted" is not printed)
#
# The problem goes away with any of the following changes:
#    * removing njit decorator from jitted()
#    * Passing a scalar to jitted (e.g. calling jitted(1) instead of jitted(x))

@numba.njit
def jitted(x):
    return x

class deltype(type):
    def __del__(self):
        print(f"{self.__name__} class deleted")

Test = deltype("Test", (object,), {})

x = numba.typed.List()
for i in range(10):
    x.append(123)
jitted(x)

# Strangely, this also reproduces the issue:
# x = numba.typed.List()
# for i in range(10):
#     x.append(tuple(float(i) for i in range(3)))
# jitted(1)  # note that x is never actually used

I can reproduce this - it also happens if you use a reflected list, by declaring x = [] instead of using a typed list. I wonder if it is related to refcounting rather than specifically the use of typed or reflected lists.

Also happens with a NumPy array:
import numba
import numpy as np

@numba.njit
def jitted(x):
    return x

class deltype(type):
    def __del__(self):
        print(f"{self.__name__} class deleted")

Test = deltype("Test", (object,), {})

x = np.zeros(10)
jitted(x)


feat: truncation of winbar when there is not enough room

Reference: #16

All seems to be working great. I keep get an annoying barbecue: truncation methods other that 'simple' are not supported yet prompt on startup though

Yeah I didn't want to have the default method be simple. But since it was the only one that's been implemented, I left a notification there and made it set method to simple temporarily. It's going to be removed once merged.
Here's a workaround though
require'barbecue'.setup({
  truncation = {
    method = 'simple'
  }
})


New package: 7gxycn08.ForceAutoHDR version <IP_ADDRESS>

Checklist for Pull Requests

[ yes ] Have you signed the Contributor License Agreement?
[ no ] Is there a linked Issue?

Manifests

[ yes ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ yes ] This PR only modifies one (1) manifest
[ yes ] Have you validated your manifest locally with winget validate --manifest <path>?
[ yes ] Have you tested your manifest locally with winget install --manifest <path>?
[ yes ] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Program Files (x86)\ForceAutoHDR\ForceAutoHDR.exe returned exit code: 1

(Automated response - build 880.)


Extraneous output in Serial window

CircuitPython Version
CircuitPython 9.1.1 on QT Py ESP32-C3

Workflow(s)
USB
Browser(s)
Version 127.0.6533.99 (Official Build) (64-bit) on Ubuntu 24.04

Console Log
nothing unusual in console log

Steps

Shift reload https://code-beta.circuitpython.org/
select USB and choose serial. The board has previously had storage.erase_filesystem() done, so CIRCUITPY is in good shape.
open Serial window
edit code.py and another another print() statement

Description
I see extraneous output in the Serial Window, copied below. I see soft restarts, raw REPL info, a few errors, the file I'm writing, etc.

raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKFalse
>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
connected

>>>
>>>
soft reboot

Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Hello World!

Code done running.

Press any key to enter the REPL. Use CTRL-D to reload.

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKFalse
>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKsd 16384 0 946684802
settings.toml 32768 0 946684802
code.py 32768 22 946684802
lib 16384 0 946684802
boot_out.txt 32768<PHONE_NUMBER>04
>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKprint("Hello World!")

>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKTraceback (most recent call last):
  File "<stdin>", line 6, in <module>
NameError: name 'os' is not defined
>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
soft reboot

Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Hello World!
foo

Code done running.

Press any key to enter the REPL. Use CTRL-D to reload.

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
>>>
soft reboot

Auto-reload is on. Simply save files over USB to run them or enter REPL to disable.
code.py output:
Hello World!
foo

Code done running.

Press any key to enter the REPL. Use CTRL-D to reload.

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKsd 16384 0 946684802
settings.toml 32768 0 946684802
code.py 32768 34 946684856
lib 16384 0 946684802
boot_out.txt 32768<PHONE_NUMBER>04
>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>

Adafruit CircuitPython 9.1.1 on 2024-07-22; Adafruit QT Py ESP32C3 with ESP32-C3FN4
>>>
raw REPL; CTRL-B to exit
>raw REPL; CTRL-B to exit
>OKprint("Hello World!")
print("foo")
>

Additional information
No response

Thanks. I'll look into this today.

I noticed this as well and was able to reproduce the issue locally. I haven't traced down the exact cause yet.

This is now via #231.


Avoid error "SQLITE_BUSY: database is locked"

Avoid error "SQLITE_BUSY: database is locked" by allowing SQLITE to wait up to 5 seconds to do a write
Description
I noticed in the logs of my Uptime-kuma container this error occuring several times per day:
uptime-kuma    | Trace: [Error: insert into `heartbeat` (`duration`, `important`, `monitor_id`, `msg`, `ping`, `status`, `time`) values (20, false, 2, '200 - OK', 116, 1, '2022-07-31 03:14:03.651') - SQLITE_BUSY: database is locked] {
uptime-kuma    |   errno: 5,
uptime-kuma    |   code: 'SQLITE_BUSY'
uptime-kuma    | }
uptime-kuma    |     at consoleCall (<anonymous>)
uptime-kuma    |     at Timeout.safeBeat [as _onTimeout] (/app/server/model/monitor.js:563:25)
uptime-kuma    | 2022-07-31T03:14:05.557Z [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues
uptime-kuma    | 2022-07-31T03:14:05.557Z [MONITOR] INFO: Try to restart the monitor

After searching in the documentation of SQLITE and over internet for a fix I found that the issue could be avoided by executing this SQLITE command:
PRAGMA busy_timeout = 5000;
Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist

[X] My code follows the style guidelines of this project
[X] I ran ESLint and other linters for modified files
[X] I have performed a self-review of my own code and tested it
[X] I have commented my code, particularly in hard-to-understand areas
(including JSDoc for methods)
[X] My changes generate no new warnings

Not sure whether it helps, but let's try. Thanks.


omni_base_navigation: 2.1.1-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository omni_base_navigation to 2.1.1-1:

upstream repository: https://github.com/pal-robotics/omni_base_navigation.git
release repository: https://github.com/pal-gbp/omni_base_navigation-release.git
distro file: humble/distribution.yaml
bloom version: 0.12.0
previous version for package: 2.0.7-1

omni_base_2dnav
* fix laser frames
* Contributors: andreacapodacqua

omni_base_laser_sensors

No changes

omni_base_navigation

No changes

omni_base_rgbd_sensors

No changes

Holding for Humble sync


Add an option to change max steps limit in protostar test

As a StarkNet smart contract developer, I want to change max steps limit when testing so that I can test contracts which exceed this limitation.
Ref: https://discord.com/channels/793094838509764618/964116575387021413/1036683939189891133

related #777

I did a quick grep and I think we should simply pass custom value here: https://github.com/software-mansion/protostar/blob/fc5e2ef3448a71596aa851ac0722b6daef5c3d4e/protostar/starknet/cheatable_invoke_function.py#L39, but this requires testing...


rubyPackages.zlib: init at 3.1.1

Ruby interface for the zlib compression/decompression library
https://github.com/ruby/zlib
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Thanks for the PR. A couple of requests:

Please add the new gem to the Gemfile per the instructions in the manual. That way if anyone runs the update script, your new package is not automatically removed from the Nix file you edited in this PR. You can probably skip the step of running the update script (or run it just to make sure the changes it makes to the Nix file agree with the changes you've made yourself) because I see there are other differences and updates to the file that the update script creates which you probably do not want your PR to need to address.
Can you squash your two commits into one and format the commit message the same way for formatted your PR title (rubyPackages.zlib: init at 3.1.1)?


Any update on the phone & tablet frame frames?

❤ An amazing library
A big thank you 🙏
Do you have plans to provide frames for phone & tablet?

Thanks, @sagrawal31.
I do plan on eventually adding phone and tablet frames. Not sure when I'll circle back to updating this library, but I likely will eventually.


Transferring bash-it config between computers

Is there a file that stores settings/what's enabled that I could transfer from one comp to the next to transfer over my bash-it config?

@bsgreenb I use a ~/etc.git to keep track of my stuff.
mkdir ~/etc && mv ~/.bash_profile ~/etc/bash_profile && ln -s ~/etc/bash_profile ~/.bash_profile
mkdir ~/etc && mv ~/.bash_it ~/etc/bash_it && ln -s ~/etc/bash_it ~/.bash_it
I move most my .dotfiles and other config type stuff in to ~/etc and symlink where it belongs. then I keep my etc backed up. I use boxen to create those repos and symlinks for new systems to help keep everything in sync. there are probably more elegant solutions but this is what i'm doing now.

@bsgreenb I copy the entire directory to my new computer, or restore from a back up. I'd say that if you want a settings export feature, a PR would be more than welcomed.
@nwinkler my guess is that this can be closed.

I posted this somewhere else around here, but think sharing it here could be useful too:
bashit-backup.sh (gist)
# Exports Bash-it components as a series of 'enable' commands.
# The output can be saved to a file and sourced as needed to re-enable components.
# A 'disable all' statement is present for each component, but commented by default.

Thanks for posting your Gist here! I use a similar script that also produces an executable file with all the enable/disable statements. It can be found here: https://github.com/nwinkler/dotfiles/blob/master/home/bin/backup-bash-it
I'm wondering whether we want to either add this to the Wiki section, or add it as a function to Bash-it. Something like bash-it backup...

Why was this closed? It seems backup is not a recognized function of bash-it.

Hey @finn-matti ,
I think this was closed since, at the time, the discussion resulted in some working solutions (for example, see the gist I link to a couple posts above)
However, there is also a current effort to bring some form of official support to bash-it:

add profile subcommand

So keep an eye on that PR !

@davidpfarrell That looks great. Also thanks for the clarification. 👍


updated installation code in readme

The React Native community frowns upon using npm in RN projects. Instead, yarn is preferred, so we need to change npm install to yarn add

Yeah true, majority of Js devs still use npm by default