Date / Time Problem

Hi,
By leaving the timezone setting blank, the date in the event records have the correct date (real time 00.56 - Time reported: 00:56):

but the local time is two hours behind (real time sep 03 01:02:23 - time reported: sep 02 23:02:23

and also in the motion_files (see the end date) it is two hours behind (Real Time: 03.09.2021 00:58:22 - Time Reported: 2021.09.02 22:57:12)

If I set the timezone with the Italian value, the date in the event log is two hours ahead.
How should I set the value for the timezone to have a synchronization of all dates / times?
Thanks

How do you set timezone in the yi app?

How did you set timezone in the yi app?

Hi @roleoroleo
timezone in YIhome: UTC +1:00

Plase, try to set timezone = GMT in the app.
Check this post: https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/203#issuecomment-918762012

Plase, try to set timezone = GMT in the app.
Check this post: #203 (comment)

Perfect!
Set UTC +0 in the YIHome app and set the correct timezone to YI-HACK.
Now the time is correct everywhere

The name should be "Coordinated universal time".

The name should be "Coordinated universal time".

That's right, I set Coordinated universal time!
Thanks

@roleoroleo Am I missing a step?  I'm getting confused because it's not working as expected...
Yi Home 1080p
IFUSY65U5W
<IP_ADDRESS>_202105081647
y211ga
Even if I disable NTPD, times don't seem to match up, universally.  There seem to be different variables.
For example, if the time is December 4, 2021 23:05:00 (GMT-6) and I've set the following and then rebooted:
Yi-Hack: CST6CDT,M3.2.0,M11.1.0
Yi-Hack NTPD: disabled
Yi app: Coordinated universal time
I'm rounding off numbers and keeping them consistent after observing the changes, for simplicity in showing the issue...
Bolded are changes.
I'm sorry for the wall of text, but I wanted you to see what changes.
My computer shows "December 4, 2021 23:05:00" (correct)
Yi-Hack web status shows "Sat Dec 4 23:05:00 CST 2021" (correct)
Recording folder being recorded to is "2021Y12M04D23H" (correct)
Filezilla client to Yi-Hack FTP recorded file (dynamically changes, not read/write) modified time shows "12/4/2021 17:05:00" (6 hours behind)
Now, if I remove the timezone set in Yi-Hack configuration page, save, power cycle completely (not a soft reboot):
My computer shows "December 4, 2021 23:05:00" (correct)
Yi-Hack web status shows "Sun Dec 5 05:05:00 GMT 2021" (6 hours ahead)
Recording folder being recorded to is "2021Y12M05D05H" (6 hours ahead)
Filezilla client to Yi-Hack FTP recorded file modified time shows "12/4/2021 23:05:00" (correct)
Now, if I change the Yi app timezone to UTC-06:00, power cycle, nothing seems to change.
Now, if I change the Yi-Hack timezone to CST6CDT,M3.2.0,M11.1.0, save, power cycle:
My computer shows "December 4, 2021 23:05:00" (correct)
Yi-Hack web status shows "Sat Dec 4 23:05:00 CST 2021" (correct)
Recording folder being recorded to is "2021Y12M04D23H" (correct)
Filezilla client to Yi-Hack FTP recorded file (dynamically changes) modified time shows "12/4/2021 17:05:00" (6 hours behind)
Now, if I "Disable Cloud", "Enable Recording without Cloud", "Enable NTPD", save, power cycle:
My computer shows "December 4, 2021 23:05:00" (correct)
Yi-Hack web status shows "Sat Dec 4 23:33:12 CST 2021" (correct)
Recording folder being recorded to is "2021Y12M04D23H" (correct)
Filezilla client to Yi-Hack FTP recorded file (dynamically changes) modified time shows "12/4/2021 18:05:00" (5 hours behind)
Now, if I change the Yi app timezone to Coordinated universal time, power cycle, nothing changes.
Now, if I re-enable "Cloud" (keeping NTPD enabled), save, power cycle:
My computer shows "December 4, 2021 23:05:00" (correct)
Yi-Hack web status shows "Sat Dec 4 23:33:12 CST 2021" (correct)
Recording folder being recorded to is "2021Y12M04D23H" (correct)
Filezilla client to Yi-Hack FTP recorded file (dynamically changes) modified time shows "12/4/2021 18:05:00" (6 hours behind)

I have the same issue with invalid dates in recording folders, as well as in file names.

@roleoroleo , I am also having issues with timestamp / time zone on my Yi 1080 Home.
BUT.... the issue only presents itself on the date/timestamp overlay that is overlaid on the rtsp stream.
My setup is:

Yi 1080 Home, QFUS

Using Yi App:  Time zone set to UTC +0000

Yi Hack web: set time zone to my correct time zone, disabled cloud, enabled NPT time sync, reboot.

The result:
Yi Hack web reports the local time correctly - 10:14am (I am GMT-4, so GMT would be 2:14pm)
However, the timestamp overlay on the rtsp stream shows 8 hours ahead!  It's as if it has added 4 hours to GMT, rather than subtracted 4 hours. (it is showing 18:14, as shown below).
I have tried different combinations of Yi time zone, NTP on/off, Yi Hack time zone, and cannot get these to agree.

Your problem is different because is related to the overlay.
And I don't know hot to solve it because it depends on the yi firmware.
But check if the "rmm" process has the correct environment variables.
Login with ssh.
Find the process id: ps | grep rmm
Check the environment: cat /proc/<PID>/environ

Thanks for the quick reply - appreciate it.   The output is below.  Looks cryptic to me, but maybe something will jump out at you.

TZ variable is absent.
This is not ok.
What is yout timezone setting in the web interface?

pasted from web interface:  EST5EDT,M3.2.0,M11.1.0

I checked the script and I can't understand.
Try another command:
cat /proc/1172/environ | tr '\0' '\n'

di you fix it?
i habe UTC-0 in Yi app.
my timestamp up left in the video is incorret.

I don't know how to fix it, at the moment.

FWIW I found using the setting GMT in the Yi app and TZ in Yi-Hack breaks the seek time in the Yi android app when trying to playback video. For those using RTSP and personal recorders I guess it doesn't matter but I ended up changing both yi app and yi hack to the proper timezone and only applying the timezone inline where needed in system.sh. For example with httpd, although others might be added.
export TZ=$(get_config TIMEZONE)
if [[ $(get_config HTTPD) == "yes" ]] ; then
    mkdir -p /tmp/sd/record
    mkdir -p /tmp/sd/yi-hack/www/record
    mount --bind /tmp/sd/record /tmp/sd/yi-hack/www/record
    httpd -p $HTTPD_PORT -h $YI_HACK_PREFIX/www/ -c /tmp/httpd.conf
fi
# maybe some other apps here too
export -n TZ

But what works for me might not work for others and I don't know if Yi use daylight savings, maybe someone with daylight savings can shed some light? :)
Example with above and +7hrs set for both Yi Hack (where needed) and the Yi app. The r30gb needs a workaround but the other camera's b091qp/h60ga seem fine.

I wanted to try to do the opposite: run rmm without TZ.
But probably your solution is better.

@SeriousPat
Try this system.sh (overwrite the original one).
Set your timezone in the app (instead of UTC).
Reboot and check:

Date/time in status web page.
The watermark printed on the video and on the snapshot.
If you are able to play videos captured with a motion (both web gui and app).

system.tar.gz

What about the date/time of the table in the "Events" page.
Is it ok? Or is it shifted by an offset?
I changed the system.sh and I reconfigured the correct time in the app.
Now, the time of the events is not ok.

Not sure who you are asking, if it's me then my event page is fine. Don't use MQTT, CRON and SSH seems to do it's own thing with time, as I said before I'm a noob with Linux and not that much better with Windows so don't know.
TBH just telnet/ssh and ftp would be enough for me with these camera's but it's nice to learn so I try a few things. Even learning a little arm and wrote a test grabber with piped aac and video streams from fshare. Audio was a bit hit and miss with my modification to rtsp_server_yi, the newer one you submitted works better than my attempt. Not sure what to do with videofile.cpp to get the 265 working, all those brackets and semi colons do my head in.  :/

Not sure what to do with videofile.cpp to get the 265 working, all those brackets and semi colons do my head in. :/

Check the last commit:
https://github.com/roleoroleo/RtspServer/tree/yi

Forgot to mention I'm not using ONVIF either and RTSP is being used for learning purposes, no dedicated box for it's use. Cloud is enabled but no cloud storage.

Check the last commit: https://github.com/roleoroleo/RtspServer/tree/yi

Cool, will try it out later today. Will start another thread under discussions.

Thanks for the excellent software. Its magical to be able to ssh and play around into the camera.
Am facing similar date time problems.
I moved the export TZ to just before the rmm is executed, this seems to fix the folder label. However the overlay on top left is still 8 hours behind.
FYI: I am not using Yi App at all and all cloud features are disabled. Is there anyway to modify the firmware timezone offset? I am looking through #203 . Any tips?

I don't know how to set the internal timezone (I mean the same that the app changes).

I'm having the same issue. The timestamp on the rtsp feed is off by 5hrs, whenever I disable cloud. I have the yi app set to UTC. If I set the timezone to EST (which should subtract 5 hrs from UTC), it adds 5 hours more to the timestamp, so it shows a time that is 10hrs ahead. I tried multiple combinations of turning off ntdp, timezones, reboot cycles, but the timestamp seems to be always off unless I don't disable cloud.

Is your TZ positive or negative?

It's supposed to be negative... my TZ is EST5 (Eastern time, which UTC - 5 hr)

Try to overwrite 2 files contained inside this archive:
patch.tar.gz
/tmp/sd/yi-hack/bin/set_tz_offset
/tmp/sd/yi-hack/script/system.sh

Thanks a lot, I'll try that. Do I just ssh into the cam and overwrite those files, and reboot?, or Do I turn off the cam, take the micro sd and change the files in my computer, and then power on the cam?

As you prefer.
Normally I use ftp. No need to change permissions because the file system is a fat32.
A reboot is required.

I can confirm that these 2 files corrects the issue!   Beautiful!
Thanks @roleoroleo .... greatly appreciated!

the patch works!!! Thanks a lot @roleoroleo, no more incorrect timestamp!

Sadly, the system.sh file crashes both of my cameras on the current F/W (0.2.5)  (model: y211ga)

Pay attention when you copy the file to the cam.
The file must be in linux format (LF line termination).

Pay attention when you copy the file to the cam.
The file must be in linux format (LF line termination).

That should be easy since my daily is PopOs 😊
When it failed I also opened it up in VSCode to see what's up and I saw all \n no \r

Please, check this commit:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/commit/4db939ee69d7b134313dd2610be2b71cc328bf32

Please, check this commit: 4db939e

Just applied, if it fails, I only have 1 more shot til much later. At work right now. 😊
Technology is great.

FWIW I found using the setting GMT in the Yi app and TZ in Yi-Hack breaks the seek time in the Yi android app when trying to playback video. For those using RTSP and personal recorders I guess it doesn't matter but I ended up changing both yi app and yi hack to the proper timezone and only applying the timezone inline where needed in system.sh. For example with httpd, although others might be added.

Hi ghost, did you obtain the result when Cloud was disable?
I met trouble to set the good timezone for the built-in YI timestamp at left top (#606).

Hi,
I applied the patch, but as soon as I set TIMEZONE to anything, the camera wouldn't boot.
I was trying the TZP_SET calculation in /bin/sh, and I kept getting a 'bad substitution' with the  ${TZP:0:1} syntax.
I got it to work using sed:
TZP_SET=$(echo $TZP | sed 's/\(.\)/\1 /g' | awk '{ print ($1($2$3)*3600+($4$5)*60) }')
My camera boots now and the times seem to be correct.
Sadly, it's not doing motion detection anymore though, but that's probably a different issue.
Thanks
-chuck

I was trying the TZP_SET calculation in /bin/sh, and I kept getting a 'bad substitution' with the ${TZP:0:1} syntax.

This is strange.
What happens if you run the followin commands?
root@yi-hack:~# export TIMEZONE=CET-1CEST,M3.5.0,M10.5.0/3
root@yi-hack:~# export TZP=$(TZ=$TIMEZONE date +%z)
root@yi-hack:~# export TZP_SET=$(echo ${TZP:0:1} ${TZP:1:2} ${TZP:3:2} | awk '{ print ($1$2*3600+$3*60) }')
root@yi-hack:~# echo $TZP_SET

Hi,
/bin/sh
sh$ export TIMEZONE=CET-1CEST,M3.5.0,M10.5.0/3
sh$ export TZP=$(TZ=$TIMEZONE date +%z)
sh$ export TZP_SET=$(echo ${TZP:0:1} ${TZP:1:2} ${TZP:3:2} | awk '{ print ($1$23600+$360) }')
sh: 3: Bad substitution
sh$ echo $TZP_SET
sh$
That syntax seems to work in bash, not sh though.
/bin/bash
bash$ export TIMEZONE=CET-1CEST,M3.5.0,M10.5.0/3
bash$ export TZP=$(TZ=$TIMEZONE date +%z)
bash$ export TZP_SET=$(echo ${TZP:0:1} ${TZP:1:2} ${TZP:3:2} | awk '{ print (
$1$23600+$360) }')
bash$ echo $TZP_SET
+7200
bash$
Thanks
-chuck
On Thursday, June 22, 2023 at 10:46:01 PM PDT, roleo @.***> wrote:

I was trying the TZP_SET calculation in /bin/sh, and I kept getting a 'bad substitution' with the ${TZP:0:1} syntax.

This is strange.
What happens if you run the followin commands?
@.:~# export TIMEZONE=CET-1CEST,M3.5.0,M10.5.0/3
@.:~# export TZP=$(TZ=$TIMEZONE date +%z)
@.:~# export TZP_SET=$(echo ${TZP:0:1} ${TZP:1:2} ${TZP:3:2} | awk '{ print ($1$23600+$360) }')
@.**:~# echo $TZP_SET
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Sorry bu I don't understand, inside the cam sh and bash are symbolic links to ash.
Where are you running, these commands?

Hi
Yes, sorry, I was running them on a linux machine, I tried it on the camera there is no error.
Now I'm not sure why the camera wasn't booting with that code in there.
It's working now..
Thanks
-chuck

Try to overwrite 2 files contained inside this archive: patch.tar.gz
/tmp/sd/yi-hack/bin/set_tz_offset
/tmp/sd/yi-hack/script/system.sh

I can confirm that the set_tz_offset in this patch fixes the OSD timestamp for a negative tz offset (CST/CDT) but does not appear to be included in the latest version (0.2.9). I tested this on RFUS both Indoor (y211ga) and Outdoor (h30ga) cameras running version 0.2.9. Note: I did not need to replace system.sh.
To get this to work:

I re-enabled cloud integration and rebooted
I set to timezone to Coordinated universal time in the Yi-Home app
I disabled cloud integration, set the correct timezone and enabled time OSD in Yi-Hack
Rebooted (Offset was still doubled, IE +10 instead of -5)
I replaced set_tz_offset from the patch on the camera
Rebooted (now the OSD timestamp is displaying correctly)

This is weird.
I included the fixes in the master branch and tested again in this moment.
It works with my h52ga (0.2.9) using "CST6CDT,M3.2.0,M11.1.0".
Please run the commands in this post, using your timezone and check the output.

@roleoroleo I actually did try those commands prior to replacing set_tz_offset on 0.2.7 and 0.2.9 and it always gave the correct offset for me of -18000. This lead me to think that the issue was with set_tz_offset and not system.sh. I should have included this in my last post but I am also using "CST6CDT,M3.2.0,M11.1.0" as my Timezone in the UI.
Here are the commands ran on one of my cameras:
root@yicamout:~# export TIMEZONE=CST6CDT,M3.2.0,M11.1.0
root@yicamout:~# export TZP=$(TZ=$TIMEZONE date +%z)
root@yicamout:~# export TZP_SET=$(echo ${TZP:0:1} ${TZP:1:2} ${TZP:3:2} | awk '{ print ($1$23600+$360) }')
root@yicamout:~# echo $TZP_SET
-18000
I did some more testing and tried replacing set_tz_offset from different patches on one of my RFUS cameras running y211ga 0.2.9 and below are the resulting OSD:
From patch.tar.gz: OSD is UTC-5 (correct)
y211ga (0.2.9): OSD is UTC+5
h52ga (0.2.9): OSD is UTC+5
y211ga (0.2.7): OSD is UTC+5
y211ga (0.2.6): OSD is UTC-5 (correct)
y211ga (0.2.5): OSD is UTC-5 (correct)
y211ga (0.2.4): OSD is UTC-5 (correct)

Ok, the last try:
set_tz_offset writes 4 bytes to the file /tmp/mmap.info
You can check if it writes properly reading the file:
hexdump -C -s 0x04e0 -n 4 /tmp/mmap.info
The offset depends on the model and it's in the following table:
    { 0x4a0, 1 },    // Y20GA_9
    { 0x4a4, 1 },    // Y20GA_12
    { 0x4a0, 1 },    // Y25GA
    { 0x4a0, 1 },    // Y30QA

    { 0x4e0, 1 },    // H30GA_9
    { 0x56c, 0 },    // H30GA_11     Already present
    { 0x4e0, 1 },    // H51GA
    { 0x4e0, 1 },    // H52GA
    { 0x560, 0 },    // H60GA        Already present
    { 0x4e0, 1 },    // Q321BR_LSX
    { 0x4e0, 1 },    // QG311R
    { 0x4e0, 1 },    // R30GB
    { 0x56c, 0 },    // R35GB        Already present
    { 0x560, 0 },    // R40GA        Already present
    { 0x4e0, 1 },    // Y211GA_9
    { 0x570, 0 },    // Y211GA_12    Already present
    { 0x4e0, 1 },    // Y21GA_9
    { 0x564, 0 },    // Y21GA_12     Already present
    { 0x4e0, 1 },    // Y28GA
    { 0x56c, 0 },    // Y291GA_9     Already present
    { 0x570, 0 },    // Y291GA_12    Already present
    { 0x4e0, 1 },    // Y29GA
    { 0x000, 0 }     // B091QP       0x560 or 0x56c but already present

Try to run set_tz_offset and check if the number is ok.
For example:
root@yi-hack-h52ga:~# set_tz_offset -c tz_offset_osd -m h52ga -f 9 -v -18000
root@yi-hack-h52ga:~# hexdump -C -s 0x04e0 -n 4 /tmp/mmap.info
000004e0  b0 b9 ff ff                                       |....|
000004e4

I should also mention that I am running v12 of the firmware and each test below was performed after a fresh reboot of the camera. I also ran the hexdumps (for both v9 and 12 addresses) before and after the set_tz_offset command.
Booted with set_tz_offset from y211ga_0.2.9:
root@YICAM1:~/bin# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  50 46 00 00                                       |PF..|
00000574
root@YICAM1:~/bin# hexdump -C -s 0x4e0 -n 4 /tmp/mmap.info
*
000004e0
root@YICAM1:~/bin# set_tz_offset -c tz_offset_osd -m y211ga -f 9 -v -18000 -d
debug on
The size of the buffer is 3756
Mapping file /tmp/mmap.info, size 3756, to b6f8d000
Closing the file /tmp/mmap.info
Unmapping file /tmp/mmap.info, size 3756, from b6f8d000
root@YICAM1:~/bin# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  50 46 00 00                                       |PF..|
00000574
root@YICAM1:~/bin# hexdump -C -s 0x4e0 -n 4 /tmp/mmap.info
000004e0  b0 b9 ff ff                                       |....|
000004e4

Since I am on version 12 of the firmware I also tried changing that in the command line (looks like it doesn't work when passing in version 12):
root@YICAM1:~# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  50 46 00 00                                       |PF..|
00000574
root@YICAM1:~# hexdump -C -s 0x4e0 -n 4 /tmp/mmap.info
*
000004e0
root@YICAM1:~# set_tz_offset -c tz_offset_osd -m y211ga -f 12 -v -18000 -d
debug on
root@YICAM1:~# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  50 46 00 00                                       |PF..|
00000574
root@YICAM1:~# hexdump -C -s 0x4e0 -n 4 /tmp/mmap.info
*
000004e0

Not sure if this will help but with set_tz_offset from patch.tar.gz (when OSD is showing correctly):
root@YICAM1:~# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  b0 b9 ff ff                                       |....|
00000574
root@YICAM1:~# hexdump -C -s 0x4e0 -n 4 /tmp/mmap.info
*
000004e0
root@YICAM1:~# set_tz_offset -c tz_offset_osd -m y211ga -f 12 -v -18000 -d
set_tz_offset: unrecognized option: c
set_tz_offset: unrecognized option: m
set_tz_offset: unrecognized option: f
debug on
Setting timezone to -18000000 ms
root@YICAM1:~# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  b0 b9 ff ff                                       |....|
00000574
root@YICAM1:~# hexdump -C -s 0x4e0 -n 4 /tmp/mmap.info
*
000004e0

Also thank you for all your hard work on helping make this project possible!

The problem is probably related to the "-f" parameter.
You should usd "-f 12" but it doesn't work.
I will check it.

I think I found the problem.
Based on the dumps I received from other users, I thought it was already set for this model.
So the code skips the write operation.
I will remove this limit.

Please, try this:
set_tz_offset.gz

Looks good, thank you.
After replacing set_tz_offset with the one in the previous post and rebooting the camera, I now see the correct OSD and the hexdump looks good.
root@YICAM1:~# hexdump -C -s 0x570 -n 4 /tmp/mmap.info
00000570  b0 b9 ff ff                                       |....|
00000574

Also tested on Yi Camera Outdoor RFUS on firmware version 12 running 0.2.9 for h30ga and it looks good.

Please, try this:
set_tz_offset.gz

i'm experiencing the same error, can I use this on my y291ga with 9.3.5 fw?
im on the latest update since now (0.2.9)...
just overwrite the bin file?

Yes, you can try it.
Rename the old binary and copy the new one.

Thanks, it worked like a charm!
Em seg., 23 de out. de 2023 às 09:01, roleo @.***>
escreveu:

Yes, you can try it.
Rename the old binary and copy the new one.
—
Reply to this email directly, view it on GitHub
https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/246#issuecomment-1775038939,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFIQOOLDS2Q5VYXLAP2K7WDYAZMB3AVCNFSM5DKFPESKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZXGUYDGOBZGM4Q
.
You are receiving this because you commented.Message ID:
@.***>

updating this issue,
it does not corrected, I think that after a period of time the cam lost de access of ntp and returning back to UTC without TZ

I saw the 0.3.1 changelog and was very excited because the long standing issue of OSD timezone is corrected!
We're getting there! but for 1 of my 3 y29ga, the timezone is incorrect.
On the one y29ga, set_tz_offset -c tz_offset_osd -m y29ga -f 9 -v 0 -d did correct the OSD time
The two y29ga without timezone issue had Base Version <IP_ADDRESS>_202103291039
The one which required manual set_tz_offset has <IP_ADDRESS>_202006090939
I do not have yi app so that settings is whatever value the default is.


Update requirements to use guzzlehttp/guzzle instead of guzzle/guzzle

https://github.com/jayzeng/virustotal_apiwrapper/blob/master/composer.json#L17
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.

Didn't know about the update, will take a look at it.

Thanks @mbarany for taking care of this, I will cut a new build today.

https://packagist.org/packages/jayzeng/virustotalapi#0.1.6 is now available.

Aesome, Thank you!


This rule must be suppressed when implementing IXmlSerializable

Moved issue to .NET
Old issue: https://github.com/MicrosoftDocs/visualstudio-docs/issues/5797, opened by @viniciusvillas
The method GetSchema inherited from IXmlSerializable does not fit any of the described exceptions on the article (listed below). Nonetheless, it's impossible to adhere to these rules when implementing System.Xml.Serialization.IXmlSerializable, because the method must be implemented.

The method performs a time-consuming operation. The method is perceivably slower than the time that is required to set or get the value of a field.
The method performs a conversion. Accessing a field does not return a converted version of the data that it stores.
The Get method has an observable side effect. Retrieving the value of a field does not produce any side effects.
The order of execution is important. Setting the value of a field does not rely on the occurrence of other operations.
Calling the method two times in succession creates different results.
The method is static but returns an object that can be changed by the caller. Retrieving the value of a field does not allow the caller to change the data that is stored by the field.
The method returns an array.

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

ID: a179bb9e-510b-27ca-0bd9-4cca0d253faf
Version Independent ID: 0fa225dd-442f-0fd6-31ff-f14d8e8c8b22
Content: CA1024: Use properties where appropriate (code analysis) - .NET
Content Source: docs/fundamentals/code-analysis/quality-rules/ca1024.md
Product: dotnet-fundamentals
GitHub Login: @gewarren
Microsoft Alias: gewarren

@viniciusvillas Could you log a bug at https://github.com/dotnet/roslyn-analyzers? See https://github.com/dotnet/docs/pull/22113#discussion_r546993267.


Wrong exit code upon error in promu release

See https://circleci.com/gh/prometheus/prometheus/3370
$ promu release .tarballs
error: could not upload, status code (422 status code 422), msg: Validation Failed, errors: [field: name, code: already_exists]
$ echo $?
0

Looks like the part using github-release.

Probably linked to #28.

promu crossbuild also always seems to exit 0


Unreadable log files error

Hopefully last road block.  For some reason the mounted container logs are not readable by the fluentd container.
/mnt/log/containers/fluentd-48fc6_default_fluentd-736a8af93bb05b2d247c994ea6177952e16e14137bd01f03e682a465a9725d2d.log unreadable. It is excluded and would be examined next time.

I've tried running as privileged, but not luck.  Perhaps you've hit this before and know a solution?

I didn't have the location the symlinks were pointing to mounted as well.  I had /var/log/containers but didn't mount /var/lib/docker.

I'm having this same issue:
/mnt/log/containers/kube-apiserver-ip-10-131-51-160.ec2.internal_kube-system_kube-apiserver-c7a8163d649d8c56993670717b8aaa72704a7a9930aa115bd45971072f0ac96d.log unreadable. It is excluded and would be examined next time

I deployed the DaemonSet and Secret on my K8s cluster following the directions of the README file.
My cluster is running on K8s v1.6. I was able to get this to work on my K8s cluster that was running v1.5.
Has anyone seen this issue on v1.6?


DEP: Add support for py3.11

Hello,
thank you very much for this library.
I have Python 3.11 locally and installing it from pip fails because sportgems wheel for 3.11 is not available.
Not sure if python3.11 also needs to be added to the Dockerfile?

Looks good to me. Thanks for the contribution :slightly_smiling_face:
Could be that the release pipeline might be broken, as I didn't release any updates in quite some time. Will try to release a new version soon after merging this.

@naglis seems like v0.8.0 was successfully released for ubuntu and macos for python 3.11: https://github.com/fgebhart/sportgems/actions/runs/5673354209


installation fails - too many arguments in elasticsearch.go adapter

when I am trying to install transporter, it fails on this step:
go get -a ./cmd/...

giving these errors:
pkg/adaptor/elasticsearch.go:120: too many arguments in call to e.indexer.Delete
pkg/adaptor/elasticsearch.go:123: too many arguments in call to e.indexer.Index

I tried to fix it in this PR https://github.com/compose/transporter/pull/134
the tests are failing but at least I am able to install it now.

Is anybody looking at this? I'm getting the same error when attempting to install the new version. There's a clear mismatch between the function arguments expected and arguments given.
Elastigo Bulkindexer.Delete
definition: https://github.com/mattbaird/elastigo/blob/53bd637ad02af3043244da16c1b9f13633e8e912/lib/corebulk.go#L309
usage: https://github.com/compose/transporter/blob/master/pkg/adaptor/elasticsearch.go#L120
Elastigo Bulkindexer.Index
definition: https://github.com/mattbaird/elastigo/blob/53bd637ad02af3043244da16c1b9f13633e8e912/lib/corebulk.go#L289
usage: https://github.com/compose/transporter/blob/master/pkg/adaptor/elasticsearch.go#L123
Each are being given an extra argument - it looks as if the final argument (false) is unnecessary in both cases.

It's been almost a month since somebody from compose team answered or took any action regarding this project. So I guess they are busy right now. However I am using transporter with that fix I made and it works.

The issue comes if you are following the head of the elastigo project. The change was made 19 days ago and appears to be part of redesigning how the BulkIndexer works.
https://github.com/mattbaird/elastigo/commit/c698cdaa601e80e722feffba2a0b5284624160ef
You can of course build the project with any version of Elastigo pre that commit.

Thanks for the heads up @codepope - how would I go about changing the commit from which elastigo is built? I've just been using go get -a ./cmd/... and go build -a ./cmd/... to build everything.
Seems as if the dependency versions should be shrink wrapped to prevent future issues like this from occurring.

I am installing transporter with docker, this is my dockerfile where I specify different github branch (forked one)
FROM golang:1.4.2

RUN mkdir -p /go/src/github.com/compose
RUN cd /go/src/github.com/compose && git clone https://github.com/Alino/transporter.git && \
    cd transporter && git checkout patch-1
RUN cd /go/src/github.com/compose/transporter && go get -a ./cmd/...
RUN cd /go/src/github.com/compose/transporter && go build -a ./cmd/...

ENV GOPATH /go
WORKDIR /go/src/github.com/compose/transporter

we also provide steps in the README, https://github.com/compose/transporter#build
we added Godep as a result of constant changes with elastigo as well as the gorethink driver

@jipperinbham thanks for the heads up, built with godep and it worked fine. You guys have 2 different build processes in the README which was confusing, I was under the impression that you had to do both (not very familiar with golang).

I had some issues in the past, using godep, that's why my dockerfile is not using it. I will try it next time if I will have to rebuild the docker image again.

Could you clarify if there is any fix to this issue? I have been doing a fresh install on Windows following the steps in the READMEWINDOWS. I am also getting the following errors:

pkg/adaptor/elasticsearch.go:120: too many arguments in call to e.indexer.Delete
pkg/adaptor/elasticsearch.go:123: too many arguments in call to e.indexer.Index

I tried using godep go install without solving the problem...

@Alino Sir, maybe you missed this step [https://github.com/compose/transporter#build](installing godep)
I managed to generate the transporter.exe file after installing godep and repeat these process:
go get -a ./cmd/transporter
go build -a ./cmd/transporter

revise the link:
installing godep

closing this in favor of https://github.com/compose/transporter/issues/209


Correct README DB start commands and exclude data link dir

Fix one command in the README
add data to gitignore (so we can link the data dir into the repo)

Thanks !


UnicodeDecodeError: 'gbk' codec can't decode byte 0xa6 in position 18260: illegal

neoclide/coc.nvim#1828
Before i through is Coc.nvim problem but now look like it's vim-snippets
Describe the bug
OS : window10
Neovim: 0.4.3
i check again the CocInfo it't return different message
CocInfo

Output channel: Python
Starting Jedi Python language engine.
Output channel: snippets
[Info 17:39:57] Using ultisnips directories: UltiSnips E:\spacemacs\emacs26-3\AppData\Local\coc\ultisnips
[Info 17:39:58] Using ultisnips python command: pyx
Error on execute python script:
request error nvim_command - Vim(return):Error invoking 'python_execute_file' on channel 4 (python3-script-host):
error caught in request handler 'python_execute_file ['C:\Users\ADMINI~1\AppData\Local\Temp\coc.nvim-6652\coc-ultisnips-KLQQlwM_rh.py', 1, 1]':
Traceback (most recent call last):
File "E:\python\python3.8.1\lib\site-packages\pynvim\plugin\script_host.py", line 106, in python_execute_file
script = compile(f.read(), file_path, 'exec')
UnicodeDecodeError: 'gbk' codec can't decode byte 0xa6 in position 18260: illegal multibyte sequence

init.vim

Plug 'neoclide/coc.nvim',{'branch':'release'}

inoremap <silent><expr> <TAB>
      \ pumvisible() ? "\<C-n>" :
      \ <SID>check_back_space() ? "\<TAB>" :
      \ coc#refresh()
inoremap <expr><S-TAB> pumvisible() ? "\<C-p>" : "\<C-h>"

" Snippet
" Plug 'SirVer/ultisnips'
Plug 'honza/vim-snippets'

Try
I thought it's cmd default  encoding problem so change to utf-8 but don't work

what python version? see https://github.com/neovim/pynvim/pull/439 (merged but not released)

python :3.8.1

actually why is "gbk" encoding involved? Only utf8 is supported.

It seems binary file decoding error.
    @rpc_export('python_execute_file', sync=True)
    def python_execute_file(self, file_path, range_start, range_stop):
        """Handle the `pyfile` ex command."""
        self._set_current_range(range_start, range_stop)
        with open(file_path) as f:
            script = compile(f.read(), file_path, 'exec')
            try:
                exec(script, self.module.__dict__)
            except Exception:
                raise ErrorResponse(format_exc_skip(1))

open() opens file as text file.
But your opened file is invalid text(binary) file.
f.read() decodes byte as gbk codecs (system default encoding??), but it failed.

It is  #439 related problem.
I think open() should use encoding argument to detect encoding.

I think open() should use encoding argument to detect encoding.

maybe we can show a better error. But supporting non-utf8 file for python_execute_file does not seem like something we should do.

maybe we can show a better error. But supporting non-utf8 file for python_execute_file does not seem like something we should do.

If so, open(encoding='utf-8') should be used instead.
And to add the documentation.
Note: I don't know what pyfile supports encodings in Vim8.

Is there a solution to this problem
Describe the bug

OS : window7
Python: 3.7.7
Neovim: 0.5.0
pynvim: 0.4.1
Same as above

modify python_path\Lib\site-packages\pynvim\plugin\script_host.py +107 can work.
with open(file_path, 'rb') as f:        #with open(file_path) as f:

@bfredl Ping.

#465 is merged. So it can be closed.

When will the fix be released? The issue still exists in the latest release.

@bfredl Ping.  When the new version is released?
This is very important problem for me.

version 0.4.3 is released.  It should be closed.

Thanks.


Version 4 Plan - Features and Enhancements Roadmap

Version 4 Plan - Features and Enhancements Roadmap
This is to document the enhancements, features and other changes to bring to LmcUser in a forthcoming version 4.
Rationale
LmcUser is a port of ZF-Commons/ZfcUser to Laminas.  ZfcUser was developed several years ago and was based on Zend Framework v2 and v3.  The port of ZfcUser to Laminas did not bring significant improvements or new features to the package.  New frameworks based on Laminas MVC, such as Laminas API Tools have, come along and the Laminas Components have also evolved. It is long overdue to give it a serious upgrade.
LmcRbacMvc has been installed more than 25K times according to Packagist which is a good indication that the package has its usefulness in web application.  We are looking for users of the package to provide inputs into the development roadmap for Version 4.
Process

Comment on this issue if you want to add an enhancement or a feature to be included in Version 4.
Issues will be created for enhancements/features selected for inclusion in V4 and will be added to the development Backlog and will be labeled as v4
Development toward V4 will be done on the 4.x branch.
A GitHub project for LmcUser was created and issues to be added to the project so that progress can be managed
Issues will be assigned to contributors

Selected Enhancements

Proposed enhancements

Adding #46 to the list of enhancements

Adding #48 to the list of enhancements

Adding #56 to list of enhancements

A few suggestions.
General suggestions:

Remove the Service Locator usage. Service Manager should not be injected into services
Move listeners to ListenerAggregates to get them out of bootstrapping.
Remove EventManager\EventProvider as EventManagerAwareInterface / EventManagerAwareTrait makes this redundant as far as I can tell.

Forms:

Move logic to the forms init methods and out of the Form classes constructors.
Register Forms via the FormElementManager. The FormElementManager is a plugin manager designed specifically for forms and form elements. It has the Initializable initializer running against all instances (iirc) and verifies that the instances are compatible.
Move most current logic to fieldsets so its reusable and entities can be bound to them to simplify controller logic.
Provide a PasswordFilter for hashing the password.
Use the provided Laminas Authentication provided Validator for logging the user in upon form validation (if possible not sure if your workflow will lend itself to that.)

More to come.

Thanks @tyrsson
I will create new issues accordingly


Raining in Winter

Describe the bug
It rains when the temperature is way below 0 Celsius. This looks very weird.
Edit: This happens in winter transition 1 to 3 even if the temperature is way colder than 0C.
Edit2: In fall transition 3, it snows in some chunks and rains in some chunks even though the temperature is way below 0C. I have set custom temperatures for each season so it is lower than what it is by default. This should not change the problem with temperatures and when it is supposed to rain vs snow.
How to reproduce
Change the season to winter. Either wait for it to rain, or summon rain.
Screenshots / Videos

Server Log
No response

Fixed!


Changed variable name from $pwd to$passwd in the example 3

$pwd is an automatic variable and using it like this causes issues

Docs Build status updates of commit 47556b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureadps-2.0/AzureAD/Connect-AzureAD.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Hi @random82
Per the read me file:
Please be aware that if you have any updates to automatically generated reference content, you should create an issue and not a PR.  The issue will then be created into a bug and triaged accordingly.  We do this because the reference content must mirror the *dll-help.xml file and subsequent updates to the reference content may overwrite any changes made through the repo.  Capturing it in the source code ensures that this does not occur.  Any PR with changes to automatically generated reference content will be closed.
Automatically generated reference content is any of the content under this Reference node, such as Get-AzureADUser
This only applies to reference content and not conceptual content.  Pull requests for changes to conceptual content are accepted and encouraged.  An example of the conceptual content is the Overview or a scenario such as importing data.
Thank you!
Bill


Use the faster hamlit parser instead of haml

@skateman : please, fix the ugly helper and other than that this is great! :+1: :beers:

We need more testing, because the hamlit parser is more strict about haml syntax and doesn't tolerates some errors which are acceptable when using haml.

@martinpovolny Please review

LGTM :+1:  Made a minor comment about .detect vs .any?

@skateman It seems there are 2 PRs in one here.  One to convert to hamlit, and the other to refactor to use new method check_roles.  How are they related?

Hamlit is not so fault tolerant than the haml parser and doesn't treats multiline if statements as minor errors. So to use it, I had to rewrite all the bad code.


first iteration on contributor-guidance.md

@mwengren I have some extra text that requires some work but let's get something in ASAP.

@ocefpaf Thanks! I agree with what @MathewBiddle said in #50, let's move this to the project root instead of the year folder to simplify.
I'll merge my changes in and update the link.

@ocefpaf I merged my PR.  Please move this file to https://github.com/ioos/gsoc/blob/main/contributor-guidance.md to match the README and go ahead and merge whenever.


using "export" instead of "module.exports"

this way it works on expo-web

Hey @cherniv thanks for the PR!
Looks like this might be covered by #439.
Will try and get that merged in.


VoIP users + Exchange On-premises

Per the announcement that voicemail would be coming to all VoIP users, and that voicemail is stored in the Exchange Online mailbox, will users with on-premises Exchange be able to use voicemail features (using the shadow Exchange Online mailbox) or will it be unavailable altogether?

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

ID: 8228f9b2-a7de-abb4-6f41-70db0b3af155
Version Independent ID: 8fd9fafb-dd76-59a8-e609-56f06d539a31
Content: Set up Cloud Voicemail
Content Source: Teams/set-up-phone-system-voicemail.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

Please see the following topic and let us know if it doesn't answer your question:  https://docs.microsoft.com/en-us/SkypeForBusiness/hybrid/plan-um-migration
We will also add a link in the Set up Phone System voicemail topic.


Possible malware, do not install

https://www.spigotmc.org/threads/list-of-found-malware.389467/page-41#post-4420993

🤥

Haha, yeah, no way that's accidental. It's completely not possible to do that accidentally

so you're saying an other person had access to your spigotmc account (because I think this is meant with "access to servers")?
If yes it's 100% your fault

so you're saying an other person had access to your spigotmc account (because I think this is meant with "access to servers")?
If yes it's 100% your fault

Botnets are usually controlled by one or more master servers. This is probably what he is referring to. Either way, he coded the botnet and admitted to boundle it on the jar.

yeah, but how did the update got published on spigotmc?

yeah, but how did the update got published on spigotmc?

He obviously published it, he is obviously lying about doing it by accident - changing a jar boundle is not something that can be done accidentally, so he willingly coded, added and released the botnet. Pretty straightforward. Just never again trust this author and leave his media (including his Discord), he doesn't deserve any form of attention. There are plenty of similar plugins, look for another one :)

yeah, I recommend using NickAPI + HaoNick. Pretty good support and also a really kind moderator on their discord :)

Did you even read his Statement? He wrote that others persons had acces to his server were they changed the jar, they didn't had access to his spigot account, the spigot download redircted to his website and on this server were the jars are hosted the person which had access to his server replaced his jar... There stands nothing from that this happpend accidentally or that HE published the jar with the botnet, he says after releasing it, someone who had access to his server changed the jar on the server, spigot just redirected to his website

I think, the methode to download it here from  GitHub from the build with actions is secure

should be as the jar is only built when a new release is created, or am I wrong?

The jars in the release are build if the workflow manually started, then it will be built with exact the source code of the branch selected or if the .version file gets edited
And on every commit it gets also build you can download this under "actions > Build with maven > select the commit > download the artifacty.zip"

@2020Sanoj What @JustixDevelopment said is not true. @quiquelhappy is telling the truth. The botnet was in there for weeks if not MONTHS!
If you look at this capture of this repo you can see that the buildfiles are not public. Additionally there are no releases. AND nothing proves that the uploaded files on his server were from said workflow. You probably worked with Justus G. and don't want this skid to be exposed.
Please. Stop using the internet.
The world will be better.
BTW You added the workflows yourself.  (This was added 18 Days ago!! The Botnet was in there for WAAAY longer.)
BTW BTW His server has been seized by the German police lol

Yes I added the files, because then we have files/jars, which aren't affected, because they got built through GitHub actions, if you want to trust the files on his (deleted) website is another question. (I simply wanted a clean file) And “my work” was only creating these workflows and telling him how to use them. I don't even know how to develop using java, I know how to use GitHub actions / docker files / batch scripting and a bit shell scripting.
If the botnet got injected by him or someone else is determined by the court.

To make it more secure we also has make a PR that Change the Auto Updater to GitHub (#19)


fix num_classes not found in repvit

can't fuse due to the the missing attributed num_classes , this PR fixed this bug.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Swap out num_cpus for std::thread::available_parallelism

Objective
As of Rust 1.59, std::thread::available_parallelism has been stabilized. As of Rust 1.61, the API matches num_cpus::get by properly handling Linux's cgroups and other sandboxing mechanisms.
As bevy does not have an established MSRV, we can replace num_cpus in bevy_tasks and reduce our dependency tree by one dep.
Solution
Replace num_cpus with std::thread::available_parallelism. Wrap it to have a fallback in the case it errors out and have it operate in the same manner as num_cpus did.
This however removes physical_core_count from the API, though we are currently not using it in any way in first-party crates.

Changelog
Changed: bevy_tasks::logical_core_count -> bevy_tasks::available_parallelism.
Removed: bevy_tasks::physical_core_count.
Migration Guide
TODO

I don't know how important this is for Bevy, but std::thread::available_parallelism is erroneous for "environments where the available parallelism is controlled by cgroupv1" (https://github.com/rust-lang/rust/pull/97911), leading to significantly higher memory usage in such environments. num_cpus doesn't have this issue.

games don't, but a game server using Bevy could

Maybe we should just wait to see how https://github.com/rust-lang/rust/pull/97925 plays out?

Seems like https://github.com/rust-lang/rust/pull/97925 has been merged and was released as a part of 1.63, so I think the issues there have been addressed.

bors r+


I've created an Angular Formly input based on cleave.js

Hi!
I love cleave.js and i use it in my Angular projects, so i spent a bit of time writing a custom input type for angular formly.
You can check it here: https://www.npmjs.com/package/angular-formly-cleavejs.

Thanks, @eliagentili I will keep it open.
BTW, we are working on Angular component as well :)


sbt console became stuck when ".par" is used

(See the guidelines for contributing, linked above)
steps
start sbt (0.13.16) (for an arbitrary project using scala 2.12.4)
start console
paste List(1,2,3).par.foreach(println)
problem
the console hangs and makes no progress at all; when you remove ".par" everything works as expected

I realized that this issue is most likely a Scala issue (https://github.com/scala/bug/issues/10566) and as such does not belong here.


[capi] add identity layer to capi

Added identity layer enum to capi

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2187. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


Flatcar integration

Modify openstack-cluster templates to integrate ignition components for Flatcar
Smaller changes related to addon defaults

I don't like how Flatcar feels like a bolt-on here. If we are going to support it, I feel we should refactor the charts so that there is an OS abstraction that Ubuntu and Flatcar both use.

I think there is a nice way to do it by utilising template definitions and passing around the name of a template to use, but I haven't got it fully figured out yet.

I think there is a nice way to do it by utilising template definitions and passing around the name of a template to use, but I haven't got it fully figured out yet.

I wonder if something similar could be done for #91. Seems like some sort of abstraction for adding patches to the kube-apiserver config could also be useful.

@heytrav I was thinking the same. Let me have a bit of a think about how it would work.

@mkjpryor based the changes you made in #130 it looks like I can just override controlPlane.kubeadmConfigSpec and nodeGroupDefaults.kubeadmConfigSpec to add the necessary ignition components in a user defined -f values.yaml.  I'm still experimenting with it to be sure.
For the purpose of this PR I'm wondering if you want to

Provide any sort of conditional blocks in charts/openstack-cluster/values.yaml to switch between cloud-init or ignition based systems OR
Leave that out completely and leave it up to the user to override with the ignition components?

For the latter case I would probably just close this PR. We'll just use our own with the ignition setup regardless.

I've refactored the original PR to remove most of the changes I had made. In the current state it is possible to build Flatcar clusters with this code and providing customised values.yaml.
However as mentioned in #138  it was necessary to change the last command added to preKubeadmCommands because it references a folder that does not exist on Flatcar and causes the build to fail. Rather than remove it completely I added a separate definition that uses a different path when ignitionBasedOS: true.
To resolve #139 I changed the destination of the additional containerd config to create a new file under /etc/containerd/config.d/. Not sure if this is best approach but for now it at least doesn't clobber the containerd configuration

@heytrav
I think in the short- to medium-term it would be nice to have the Flatcar support be native to the charts, so that we only require the user to flip a value in the charts between flatcar and ubuntu. However if you think this is the minimum set of changes that enable the use of Flatcar and you don't have the time or inclination to look at the required changes for that, I am happy to merge (subject to a full review and passing the test suite).
Let me know what you prefer.

I actually would like to have ignition based OS (i.e. flatcar) be completely handled by the chart as you suggest. However I wasn't sure how you preferred this to work.
I will need to experiment a bit to add this into the chart. If you have any suggestions, I'm happy to follow your lead.

Most recent commit works for me locally (I can build a Flatcar cluster).
@mkjpryor please let me know if this is more in line with what you were thinking.

@heytrav
I added my thoughts in the form of review comments. Since we are adding support for a second OS, I would like to make sure that we can actually support N OSs going forward, just in case, so the suggestions I made reflect that.

pushed up some changes


MINOR: add quick start for tiered storage feature

Some users complained they don't have a way to determine if there is something wrong in the RSM plug-in they implemented, or there's something wrong in Kafka itself. Also, if there are users who just want to try the tiered storage feature out before implementing anything, it would be good we have an RSM implementation by default.
Per the discussion in the KIP, there will be no default RSM implementation in Kafka, but we can use the LocalTieredStorage implemented for integration test, to resolve the issues above.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@kamalcph @divijvaidya @satishd , call for review.

Apologies for the delay, I ran the commands in the guide and they work! My only question is whether it is worthwhile directly adding the necessary configurations to the server.properties which comes with Kafka and commenting out the ones which will activate the sub-system? One way or another people will have to add those configurations and this might save them a bit of effort?

@clolov @divijvaidya @satishd @kamalcph , I've addressed all your comments and updated the screenshot in the PR description. Please take a look again. Thanks.

whether it is worthwhile directly adding the necessary configurations to the server.properties which comes with Kafka and commenting out the ones which will activate the sub-system? One way or another people will have to add those configurations and this might save them a bit of effort?

@clolov , I'll work on that in a separate PR. Let's update the docs soon to let users try the tiered storage feature first.


Add Xcode project [to add-framework-support branch]

This is equivalent to, and supersedes‚ #151 but instead targets the add-framework-support branch.
Todo

[x] Integrate framework with the ACME Browser demo app.

I looks great. Thanks @rastersize :+1:
We should change the bundle identifiers or both ACME and ACME Browser in this branch. This way we can run and test the demo apps side by side. We appended low-level to com.agilebits. in the Low Level API branch. We should append framework or something like this for this branch.
The bundle identifiers should be com.agilebits.framework.$(PRODUCT_NAME:rfc1034identifier)

I’ve changed the bundle ids of the demo apps :smiley_cat:

Thanks so much for the awesome work @rastersize!
I just tested your PR with both the stable and the beta versions of 1Password 5 for iOS and it all seems to work fine.
I'll be merging this PR and PR #153.
Cheers!


Folders prevent Gecko from detecting any videos

I've noticed that whenever a class has a folder within a set of lectures, Gecko is unable to "Load lectures on page", meaning that when I click that button, none of the lectures on the page get listed under the "Select lecture(s) to download" table.
In case you're not sure what I mean by a "folder," the first two sections below are both examples of a folder, whereas the third row is a video that's just in the main class list.

I'm pretty certain that the problem only occurs when there is a folder. I tried to load lectures on 10 different classes, 4 of which had folders. It always worked for the classes that didn't have any folders and never worked for the classes that did have folders.
Please let me know if you need anything else from me. Thanks!

Hi @sethb3744,
Thanks for submitting an issue! Is it possible to send us the Chrome extensions logs?
You can view how to access the logs here
Thanks

Also, for what it's worth, I don't currently need any of the videos that are in folders, so they can be completely ignored if you have trouble including those in the download list. Thanks again!

Can you expanded the object that days Object ?

Hi, I wanted to check in to see if you need any more information. Totally cool if you're busy, but I can give more screenshots or info if you need it.

Hello, is there a solution?
I really have to download the lectures from my university because the exam is getting closer.
Link to my lectures: https://echo360.org.uk/section/6ebce753-ab28-49b7-85c0-ed5979e3be01/home
If someone could help me please.
Thanks in advance

@hugobene
@sethb3744
@imaginebreake
that was been resolved in the merge above

Amazing! I just tried it out and it worked on my end. Is there any way to donate?

Thanks for confirming that it's been fixed 😊


remote_image in table cell broken

# rubymotion 2.31
# ProMotion 2.0.0

def table_data
  [{
    cells: @posts.map do |p|
      {
        title: p["title"].kv_decodeHTMLCharacterEntities,
        action: :tap_post,
        arguments: { id: p["id"] },
        remote_image: {  # remote image, requires JMImageCache CocoaPod
          url: "http://placekitten.com/200/300",
          placeholder: "140.jpg", # NOTE: this is required!
          size: 50,
          radius: 15,
          content_mode: :scale_aspect_fill
        }
      }
    end
  }]
end

When running rake:
imageForURL:completionBlock:' type `v@:@@?' not precompiled

Seems related to this: https://github.com/jakemarsh/JMImageCache/issues/26
As this is in the v2 docs, how do you get it to work?

@chrise86 Is this one still an issue?

@jamonholmgren it was still causing a problem for me recently, however, for some reason I believe it was linked to something else (another gem/pod possibly).
Closing for now, if I come across it again I'll dig more into it :)

:+1: Thanks @chrise86 !


TFC Token not being propagated through .terraformrc

What happened?

Trying to use .terraformrc to use modules from terraform cloud registry
getting the below error
    Namespace:  default
Status:
  At Provider:
  Conditions:
    Last Transition Time:  2023-11-24T18:02:24Z
    Message:               connect failed: cannot select Terraform workspace: Terraform encountered an error. Summary: Required token could not be found. To see the full error run: echo "H4sIAAAAAAAA/zyMwa3DMAzF7priTZABcv8LZAP9WHaN2nqpIKPrFwGKHkmAlL8Ixo7DXquHFSSf5ji5RoEz8W+oXF5EjuXIx41j8N294eSc6neDZm6hadDvoTKg17WlRWhlzK1zFwD4GQy27iIfAAAA//8BAAD//8xxXZSEAAAA" | base64 -d | gunzip
    Reason:                ReconcileError
    Status:                False
    Type:                  Synced
Events:
  Type     Reason                   Age   From                             Message
  ----     ------                   ----  ----                             -------
  Warning  CannotConnectToProvider  9s    managed/workspace.tf.upbound.io  cannot select Terraform workspace: Terraform encountered an error. Summary: Required token could not be found. To see the full error run: echo "H4sIAAAAAAAA/zyMwa3DMAzF7priTZABcv8LZAP9WHaN2nqpIKPrFwGKHkmAlL8Ixo7DXquHFSSf5ji5RoEz8W+oXF5EjuXIx41j8N294eSc6neDZm6hadDvoTKg17WlRWhlzK1zFwD4GQy27iIfAAAA//8BAAD//8xxXZSEAAAA" | base64 -d | gunzip

$ echo "H4sIAAAAAAAA/zyMwa3DMAzF7priTZABcv8LZAP9WHaN2nqpIKPrFwGKHkmAlL8Ixo7DXquHFSSf5ji5RoEz8W+oXF5EjuXIx41j8N294eSc6neDZm6hadDvoTKg17WlRWhlzK1zFwD4GQy27iIfAAAA//8BAAD//8xxXZSEAAAA" | base64 -d | gunzip

Error: Required token could not be found

Run the following command to generate a token for app.terraform.io:
    terraform login

More details here
How can we reproduce it?

Deploy a terraform provider and try to use a module from a private registry in a provider-terraform workspace
ProviderConfig
apiVersion: tf.upbound.io/v1beta1
kind: ProviderConfig
metadata:
    name: terraform
spec:
  credentials:
  - filename: .terraformrc
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: terraformrc
      key: .terraformrc
  configuration: |
    terraform {
      required_providers {
        aws = {
          source  = "hashicorp/aws"
          version = "~> 4"
        }
      }
      backend "remote" {
        organization = "ORG"
        hostname     = "app.terraform.io"
        workspaces {
          name = "dev-us-west-2-p01-crossplane"
        }
      }
    }
    provider "aws" {
      region = us-west-2

      assume_role {
        role_arn = format("arn:aws:iam::%s:role/crossplane", xxxxxxxxxxxxx)
      }

      default_tags {
        tags = {
          Source             = format("ORG/infra/terraform/%s/%s/%s/foundation", dev, us-west-2, p01-crossplane)
          Team               = "tag1"
          CostOrg            = "tag2"
          ProductLine        = "tag3"
          CrossplaneResource = "True"
          Env                = dev
        }
      }
    }

Workaround
I managed to make it work by adding the token in the providerconfig, but it seems that terraform workspaces as a backend are not supported right?
  configuration: |
    terraform {
      required_providers {
        aws = {
          source  = "hashicorp/aws"
          version = "~> 4"
        }
      }
      backend "remote" {
        organization = "ORG"
        hostname     = "app.terraform.io"
        token = "XXXXXXXXXTOKENXXXXXXXXXXXX"
        workspaces {
          name = "p01-crossplane-foundation"
        }
      }

  Type     Reason                   Age                   From                             Message
  ----     ------                   ----                  ----                             -------
  Warning  CannotConnectToProvider  3m56s (x45 over 54m)  managed/workspace.tf.upbound.io  cannot select Terraform workspace: Terraform encountered an error. Summary: . To see the full error run: echo "H4sIAAAAAAAA/wTA0Q2EMAwD0P+bwnPcAOwRNaaqgKZKXLE+77Bx06FAp9BinqPvpGPaQ0fJxPrjjbxqWWNhhlB7rUjRfx8AAAD//wEAAP//Bc+iCkAAAAA=" | base64 -d | gunzip

$echo "H4sIAAAAAAAA/wTA0Q2EMAwD0P+bwnPcAOwRNaaqgKZKXLE+77Bx06FAp9BinqPvpGPaQ0fJxPrjjbxqWWNhhlB7rUjRfx8AAAD//wEAAP//Bc+iCkAAAAA=" | base64 -d | gunzip
Failed to get configured named states: workspaces not supported

What environment did it happen in?

Crossplane Version: v1.14.0
Provider Version: provider-terraform:v0.11.0
Kubernetes Version: Client Version: v1.28.3 / Server Version: v1.25.15-eks-4f4795d
Kubernetes Distribution: EKS

Can you show the redacted contents of secret from?
   secretRef:
      namespace: crossplane-system
      name: terraformrc
      key: .terraformrc

Is it configured according to https://developer.hashicorp.com/terraform/cli/config/config-file#credentials ?

@ytsarev  yes and yes. I'm using this format for TF Cloud when using it via CLI and it works.
credentials "app.terraform.io" {
  token = "XXXXXXXTOKENXXXXXXXX"
}


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>
.travis.yml

chore(travis): remove node versions 10.10.0
chore(travis): add node versions 10.11

Codecov Report

Merging #393 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #393   +/-   ##
=======================================
  Coverage   33.33%   33.33%
=======================================
  Files           5        5
  Lines          93       93
=======================================
  Hits           31       31
  Misses         62       62

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 457422c...9fca53f. Read the comment docs.

Coverage remained the same at 29.204% when pulling 9fca53f05f0d3f3b7af66d193379d86d297f9af6 on template-sync-1 into 457422c5e4fbe76c3f739d9e10395241caffa509 on master.


feat: reauth on expired accessToken

DCMAW-9511: iOS | User sees 'You have been signed out' re-auth page when user's access token expires (whilst in-app)
When a user’s access token has expired and they call the hello-world API, they will need to re-authenticate using the One Login WebView in order to get a new access token. Once the user has successfully re-authenticated, they will be returned to their current place in-app.
Additionally, when a user returns to the app with an expired access token, the same behaviour should occur but infront of the intro screen.
Checklist
Before raising your pull request:

[x] Commit messages that conform to conventional commit messages
[x] Ran the app locally ensuring it builds
[x] Ran the tests locally ensuring they pass on Build
[x] Pull request has a clear title with a short description about the feature or update
[x] Created a draft pull request if it is not yet ready for review

Before your pull request can be reviewed:

[x] Met all of the acceptance criteria specified in the user story on Jira

[x] Reviewed your own code to ensure you are following the style guidelines

[x] Ran the app and tested the feature on a range of device sizes
Please include iPod Touch, iPhone SE and iPhone 11 as a minimum.

[x] Written Unit and Integration tests if needed

[x] Met all accessibility requirements?

[x] Checked dynamic type sizes are applied
[x] Checked VoiceOver can navigate your new code
[x] Checked a user can navigate only using a keyboard around your new code

Before merging your pull request:

[x] Ensure that the code coverage and SonarCloud checks have passed
[ ] Actioned and resolved all comments, reaching out to reviewers for clarifications if necessary.
[x] Ran the app to ensure that no regressions have been caused by changes during code review.

This is a pretty large PR so going to leave some code comments to highlight the most critical parts of the implementation.