SIFT CLI - Error: Update returned exit code not zero

Hi,
When running sift-cli I get exit code not zero when the install hits "Running: sift-scripts":

Running: sift-scripts
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/sift-cli/sift-cli.js:547:23)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)

/etc/os-release output:
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
Full output when trying to install is attached in sift-cli output. Saltstack log also attached.
Any help is appreciated.
saltstack.log
sift-cli output.txt

I am having the exact same issue with the small difference that mine starts at ">> Running: sift-config".

Please provide logs. I’m looking Into it

Just reverted snapshot. I'll rerun. Which logs will you need me to attach to best assist you?

Hi @J-a-s-o-n-P and @timmyg558 ,
I've reviewed your saltstack logs and you both appear to have two different errors.
@J-a-s-o-n-P , your error appears to be connection / apt related. The errors indicate that you were unable to download packages from the apt-repo, and the retcode: 100 indicates that your apt database was not updated (sudo apt update).
By running the sudo apt update command and running the installer again, you should have no issues.
@timmyg558 , your issue appears to be a temporary one. The issue listed in your saltstack log was that you were unable to download densityscout from the source homepage. Now, this could be representative of either a temporary drop in connection (source could have been down, or your connection lost), or if you're installing SIFT from within an enterprise environment, your firewall may be blocking the download. Your error indicates:
archive_|-sift-tool-densityscout-archive_|-/usr/local/src/densityscout/densityscout_build_45_linux_|-extracted:
    __id__: sift-tool-densityscout-archive
    __run_num__: 348
    __sls__: sift.scripts.densityscout
    changes: {}
    comment: 'Error: [Errno 111] Connection refused reading https://cert.at/media/files/downloads/software/densityscout/files/densityscout_build_45_linux.zip'
    duration: 11.784
    name: https://cert.at/media/files/downloads/software/densityscout/files/densityscout_build_45_linux.zip
    result: false
    start_time: '15:17:54.143476'

Since this state could not complete, other states which depended on it could not complete either. You could try first to download the file directly from the URL listed in the error and see if you're able to download it. If you are, then running the CLI installer again should work. If it does not, please let us know.

Hi @J-a-s-o-n-P and @timmyg558 ,
I've reviewed your saltstack logs and you both appear to have two different errors.
@J-a-s-o-n-P , your error appears to be connection / apt related. The errors indicate that you were unable to download packages from the apt-repo, and the retcode: 100 indicates that your apt database was not updated (sudo apt update).
By running the sudo apt update command and running the installer again, you should have no issues.
@timmyg558 , your issue appears to be a temporary one. The issue listed in your saltstack log was that you were unable to download densityscout from the source homepage. Now, this could be representative of either a temporary drop in connection (source could have been down, or your connection lost), or if you're installing SIFT from within an enterprise environment, your firewall may be blocking the download. Your error indicates:
archive_|-sift-tool-densityscout-archive_|-/usr/local/src/densityscout/densityscout_build_45_linux_|-extracted:
    __id__: sift-tool-densityscout-archive
    __run_num__: 348
    __sls__: sift.scripts.densityscout
    changes: {}
    comment: 'Error: [Errno 111] Connection refused reading https://cert.at/media/files/downloads/software/densityscout/files/densityscout_build_45_linux.zip'
    duration: 11.784
    name: https://cert.at/media/files/downloads/software/densityscout/files/densityscout_build_45_linux.zip
    result: false
    start_time: '15:17:54.143476'

Since this state could not complete, other states which depended on it could not complete either. You could try first to download the file directly from the URL listed in the error and see if you're able to download it. If you are, then running the CLI installer again should work. If it does not, please let us know.

@digitalsleuth Thank you for catching that since I completely missed it. Kicking myself. Modifications to my setup allowed successful install. Thanks again!

@digitalsleuth Thank you for catching that since I completely missed it. Kicking myself. Modifications to my setup allowed successful install. Thanks again!

I had this as well, I was running as sudo, not root, I had a strong internet connection and had done the apt cleanup. I am using ubuntu 20.04. I tried the --pre-release command line parameter and it seems to be off and running.

I had this as well, I was running as sudo, not root, I had a strong internet connection and had done the apt cleanup. I am using ubuntu 20.04. I tried the --pre-release command line parameter and it seems to be off and running.

Hi. Crazy: Same error as @J-a-s-o-n-P . Did fix as specified by @digitalsleuth then ran sudo sift install --mode=server and same issue appears. Any idea? /etc/os-release output same as @J-a-s-o-n-P . running ubuntu 18.04 LXC... on proxmox

Hi. Crazy: Same error as @J-a-s-o-n-P . Did fix as specified by @digitalsleuth then ran sudo sift install --mode=server and same issue appears. Any idea? /etc/os-release output same as @J-a-s-o-n-P . running ubuntu 18.04 LXC... on proxmox

Hi @Coding4Sec , any chance you can upload your saltstack.log file so we can take a look? There may be other items impacting your setup besides the issue which @J-a-s-o-n-P was having.

Hi @Coding4Sec , any chance you can upload your saltstack.log file so we can take a look? There may be other items impacting your setup besides the issue which @J-a-s-o-n-P was having.

@Coding4Sec , any chance you could provide a progress update on this? If you're still experiencing the issue, please upload your saltstack.log file so we can take a look.

@Coding4Sec , any chance you could provide a progress update on this? If you're still experiencing the issue, please upload your saltstack.log file so we can take a look.

Sorry for being late. I was busy with exams.... So i dropped the ubuntu lxc and set up a an ubuntu VM on proxmox. I now run into the same error reported here: https://github.com/teamdfir/sift/issues/507

The CLI output:

Hi @Coding4Sec , can you also attach the saltstack.log file, and the output of salt-common -V?

Hi @Coding4Sec , can you also attach the saltstack.log file, and the output of salt-common -V?

No success: command not found

Try salt-call -V or salt-minion -V. One of those should provide an output.

ok.
Strange, I did reboot, now my prompt changed to @siftworkstation...
Here is output form sat-call -V
secfor@siftworkstation: ~
$ salt-call -V
Salt Version:
Salt: 3001.4
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 2.10
libgit2: Not Installed
M2Crypto: Not Installed
Mako: 1.0.7
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: 2.6.1
pycryptodome: 3.4.7
pygit2: Not Installed
Python: 3.6.9 (default, Oct  8 2020, 12:12:24)
python-gnupg: 0.4.1
PyYAML: 3.12
PyZMQ: 20.0.0
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.3
System Versions:
dist: ubuntu 18.04 Bionic Beaver
locale: UTF-8
machine: x86_64
release: 5.4.0-65-generic
system: Linux
version: Ubuntu 18.04 Bionic Beaver

Can you run ls -la in your home directory and check to see that all of the folders there are owned by your user?

Can you run ls -la in your home directory and check to see that all of the folders there are owned by your user?

sure, all but two are not:
.kde
and
.cpanm
they are owned by root

Change those to be owned by your user (to match the rest) using chown -R <user>:<user> and try running your sift install again. That should do it.

Ok, Thanks. I will do and come back for feedback...

Change those to be owned by your user (to match the rest) using chown -R <user>:<user> and try running your sift install again. That should do it.

Uhh, no success, same as before...
Anything else to do?

Can you upload the saltstack.log from this attempt?

Can you upload the saltstack.log from this attempt?

Here we go
saltstack.log

Potentially looks like some unicode errors. Anything unique about your install? Foreign language?

German... do we need english installation?

Can you share the output of locale here, and try running your sift install like this: LANGUAGE=en_US.UTF-8 sudo sift install
If that doesn't work, change LANGUAGE to LC_ALL.

You read my mind @ekristen

yes, will do so. Let me try tomorrow morning. Will come back then. Locale: all entries are de_DE.UTF-8

ok, tried

en_US.UTF-8 sudo sift install
returned exit code not zero....

ok, tried LC_ALL no success. I did a fresh VM ubuntu 18.04 in en. except timezone and layout in de. no success: exit code not zero... although sift-config throws error, the prompt changes to @siftworkstation

Can you post the saltstack.log for this as well? It's possible that another error may have been introduced besides the original which will help narrow things down. And can you share the exact command you're using as well?

$ LANGUAGE=en_US.UTF-8 sudo sift install
-> not zero

$ LANGUAGE=LC_ALL sudo sift install
and log:
saltstack.log

log for try#1 isn't available anymore

this is from 2nd VM in en_US.... except timezone and keyb.-
saltstack.log
layout

Just to clarify, the second attempt should have been LC_ALL=en_US.UTF-8 sudo sift install> I'm looking at the log now.

uupps, ok, running this command... last thing to do for today... will upload log

Actually your last install worked but with one separate error with pyhindsight. I'll take a look at this tonight, but I'm pretty sure I know the issue, related to setuptools_rust.

ok, this is for
LC_ALL=en_US.UTF-8 sudo sift install
saltstack.log

That one installed fine except for pyhindsight due to the setuptools_rust error I mentioned earlier. I'll submit a pull for that tonight to fix it.

Issue found and resolved, but identifies a larger issue. Requires setuptools_rust and a newer pip version. I have the necessary changes ready for a pull request, but I'm in the midst of testing in both a Bionic and Focal docker (for a full fresh install), and a VM for an upgrade scenario. You can expect a pull request before EOD tomorrow.

@digitalsleuth Any updates on how to proceed?

Well the easiest way would be first to upgrade pip using sudo python3 -m pip install --upgrade pip, then install setuptools_rust with sudo python3 -m pip install setuptools_rust, and finally run sudo python3 -m pip install pyhindsight.
This will complete your latest install and, once the pull request is approved, you can try your install again.

Hi gents. same case as the others.
I am running a pretty old version of sift ws but with the latest cli and a brand new ubuntu 18.04.
I did the apt updates and so forth. I ran sift update and sift upgrade that both failed.
attached the log from the upgrade.
sift version ( i have updated the cli to 1.9.2 just before the upgrade and just after i am back in 1.5.1)

<EMAIL_ADDRESS>sift-version: v2017.27.0

the error message:
Running: sift-config
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess.update.on (/snapshot/sift-cli/sift-cli.js:488:23)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:194:7)
at maybeClose (internal/child_process.js:899:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
saltstack.log

I am having trouble with my install dropping while running: sift-config-tools....it also changes my hwclock even doing the update this: LC_ALL=en_US.UTF-4 sift update
I am including my output for salt-call -V
salt-call -V
Salt Version:
Salt: 3001.7
Dependency Versions:
cffi: Not Installed
cherrypy: Not Installed
dateutil: 2.8.1
docker-py: Not Installed
gitdb: Not Installed
gitpython: Not Installed
Jinja2: 2.10
libgit2: Not Installed
M2Crypto: Not Installed
Mako: 1.0.7
msgpack-pure: Not Installed
msgpack-python: 0.5.6
mysql-python: Not Installed
pycparser: Not Installed
pycrypto: Not Installed
pycryptodome: 3.10.1
pygit2: Not Installed
Python: 3.6.9 (default, Jan 26 2021, 15:33:00)
python-gnupg: 0.4.1
PyYAML: 3.12
PyZMQ: 22.0.3
smmap: Not Installed
timelib: Not Installed
Tornado: 4.5.3
ZMQ: 4.3.4
System Versions:
dist: ubuntu 18.04 Bionic Beaver
locale: UTF-8
machine: x86_64
release: 4.15.0-143-generic
system: Linux
version: Ubuntu 18.04 Bionic Beaver
and my saltstack log
saltstack.log

This is where it drops:

Running: /etc/foremost.conf
Running: /usr/local/etc/foremost.conf
Running: sift-config-tools
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/sift-cli/sift-cli.js:542:23)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1051:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)

----- PLEASE READ ----------------------
A lot of failures are caused by the apt system being locked
or unhealthy.
Before opening an issue in GitHub, please check to see if
your apt system is healthy.
Try running 'apt-get update' then remove any packages that
aren't used by running 'apt-get autoremove'

Hi @codifiedlikenessutility1970 , can you check the permissions on the /home/timelord/.dbus directory, and confirm that it has the proper permissions (should be set to timelord:timelord or permissions specific to the timelord user)?
The error is coming from the dconf command, which is modifying the contents of the .dbus dir.

Hmmm. It's root.

I started the dl/install process in timelord.

If you haven't already, please change the permissions to the proper permissions and try running the install command again.

I’ll review permissions tonight. I just did a fresh install though with no problems.

Thanks, @digitalsleuth! That did it!!!....two things that were odd, but I don't think were related to this was it switching my timezone and it also moved my dock from the left side to the bottom...both happened at the end of the where it kept cutting out. Thanks again!!!

Hi,
Dear @digitalsleuth, I have the same issue (exit code, not zero). Could you please check my logs?
Ubuntu 18:
saltstack-18.log
Ubuntu 20:
saltstack-20.log

Hi @Nima-pw, It looks like the issue is with pefile. I encountered this recently with REMnux, and we created a temporary fix while we await the permanent fix being merged by the original author. The issue is covered here.
I'll submit a pull request to change the state temporarily, and once the issue is fixed by the author, return it to its original state.

Thanks, @digitalsleuth, for your reply.
Unfortunately, I did not fully understand the temporary solution.
The temp fix is this?
"modifying lines 3789 and 3790 to replace the f' string formatting with .format() then everything works as it should."
Where should this edit be done?

Hi @Nima-pw, the reference shows you where the issue was caused, I am submitting a fix shortly for this. Once merged, the issue will be resolved.

Pull request 53 has been submitted to provide a temporary fix. For the time being, you may be able to install pefile manually first, then running the sift-cli installer to complete the install.
To install the 'temporary fix' version of pefile, you can run the following:
python2 -m pip install git+https://github.com/digitalsleuth/pefile.git
Then run the sift installer.

Thanks, @digitalsleuth,
I will do it and come back for feedback.

The result of installing the 'temporary fix' version:
Requirement already satisfied: future in /usr/local/lib/python2.7/dist-packages (from pefile==2021.5.13) (0.18.2)
Building wheels for collected packages: pefile
  Building wheel for pefile (setup.py) ... done
  Created wheel for pefile: filename=pefile-2021.5.13-py2-none-any.whl size=62568 sha256=5ce9b7fb8f0f03a1070a01e4c69e4512547d07b170ce03c77db1a383299c7da9
  Stored in directory: /tmp/pip-ephem-wheel-cache-4lWkzU/wheels/22/58/a0/33128d215f3adebb7b7d035f4d7a06f567bfa793af8b1cc630
Successfully built pefile
Installing collected packages: pefile
Successfully installed pefile-2021.5.13

But the saltstack.log (ubuntu 20):
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/sift-cli/sift-cli.js:547:23)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
----- PLEASE READ ----------------------
A lot of failures are caused by the apt system being locked
or unhealthy.
saltstack.log

@Nima-pw , the errors seen in the saltstack.log you provided indicate that there was an issue downloading some files, not related to pefile:
# [ERROR   ] Error: HTTP 599: Timeout while connecting reading https://didierstevens.com/files/software/virustotal-submit_V0_0_3.zip
# [ERROR   ] Error: HTTP 599: Timeout while connecting reading https://didierstevens.com/files/software/virustotal-search_V0_1_4.zip
You can try reaching these sites directly to see if there is an issue with your internet connectivity or if these files are specifically blocked by your firewall. Since these are the only errors in the log, it's likely that once this connection issue is resolved, you won't have any further problems with the installation.

@digitalsleuth you are great!
Thank you, man!

@digitalsleuth you are great!
Thank you, man!
OMPLETED SUCCESSFULLY -- Success: 654, Failure: 0

@digitalsleuth  Thank you so much for the fix regarding pefiile. I was having issues with this for a few days and this resolved it.

Hello,
My SIFT install is failing too, with the below message:

Running: /etc/foremost.conf
Running: /usr/local/etc/foremost.conf
Running: sift-config-tools
Running: sift-config
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/sift-cli/sift-cli.js:542:23)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1051:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
----- PLEASE READ ----------------------

A lot of failures are caused by the apt system being locked
or unhealthy.
Before opening an issue in GitHub, please check to see if
your apt system is healthy.
Try running 'apt-get update' then remove any packages that
aren't used by running 'apt-get autoremove'

I am attempting to install SIFT v2021.4.4 using sift-cli v1.10.0 on an Ubuntu 20.04 VirtualBox VM.
The exact command I am running for the install is: sudo sift install --version=v2021.4.4 --user=test
I am doing it this way as my aim is to script the SIFT install with some other components, but the script will be run with sudo privileges, hence me using sudo for the SIFT install while testing this new version.
I have attached the saltstack.log of the failed attempt here.
I also attempted the pefile fix mentioned above and it failed again.
I have attached the saltstack.log for that attempt here.
Hope you can help.
I am aware that the install is mainly complete, but it would be great to see the 'SUCCESS' message and have SIFT displaying as installed rather than 'notinstalled' for my work's strict versioning control.

Hi @jackdyson1399 , looking at your log files, the first one shows that you had a connectivity issue, which is why it errored out (the one called PREfix). The one called POSTfix is failing due to the same pefile issue we mentioned earlier, and can be fixed temporarily by following the steps here prior to running the sift-cli.
A pull request has been merged which will see this issue fixed in the next release, but for the time being, you should be able to install pefile manually (the link above) and then SIFT will complete its install.

I need to go to new release for the CLI to pick up the PE file fix.￼
However if you are wanting to programmatically install sift I would suggest you look at using salt directly in the salt stack repository versus trying to use the CLI￼

Just completed the SIFT update now. Thank you for your help!
I recon my issue was I did not run your pefile fix with sudo.
Interestingly though, the Desktop and the tool bar has not changed, but it did when the install failed. This is only minor but don't want to be missing anything. The saltstack.log for the successful attempt without the correct Desktop wallpaper and reorientation of the tool bar is here. And I have attached a photo of the Desktop so you can see what I mean.

I have tried rebooting the VM with no luck.
@ekristen thank you for your advice, I will investigate using salt stack instead, but the script I am using is not hugely complicated, it mainly just clones some extra work specific repositories on top of the SIFT install.

Hi everyone,
I am trying to update and I am getting this error:
Running: sift-config-tools
Update returned exit code not zero
Error: Update returned exit code not zero
at ChildProcess. (/snapshot/sift-cli/sift-cli.js:545:23)
at ChildProcess.emit (events.js:315:20)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
I have tested that the home folder has the right owner (sansforensics) as it was mentioned in a previous comment, but I get the same result.
the saltstack log is attached here
saltstack.log
I'd appreciate any help.
Thanks

Hi @tompolth , There are a few different errors there. The easiest one to fix is to follow the steps here, as this will resolve the pefile issue found in the log.
The other errors center around the sha256 hash being different from some of the PDF's that are being downloaded. I'll take a look at those later today and see if the hashes need to be updated, but these won't affect the function of the SIFT environment.
Give the fix above a try, then run the installer again. You can also visit the teamdfir/sift-saltstack repo and install SIFT using the instructions there for the up-to-date fix.

Hi @digitalsleuth
I am very sorry for my late answer. Work kept me very busy. Just thank you for your help, your solution fixed the problem

This issue got very long, I'm going to close and lock, if you have similar issues in the future please open a new issue.


feat: github stars

Looking to modernize some of my doc sites and I really hate the GitHub star button I've been using. It's currently using vue-github-button, which is also buggy on SSR.

So I built a new component and Nuxt Lego seems to be the perfect place for it to live :)

Thanks for this new feature @harlan-zw !! Nicely done! 🚀✨


only create admin user for activemq

what

only create admin user for activemq

why

Rabbitmq does not support admin user with console access and groups at this time

references

closes #21

FYI @gberenice, half your work is done!


Is the effect of using SeqVLAD for single photo VPR not good?

Is the effect of using SeqVLAD for single photo VPR not good? SeqVLAD is designed so ingeniously that it can achieve such good performance with so few parameters! I wanted to use SeqVLAD for single image VPR, but found that the effect was not good, with recal@1 less than 50. Why is this? My approach involves processing a single image with backbone and then converting the dimensions to (B,C,N), followed by aggregation with SeqVLAD. This shouldn't be the case, as single image VPR should be simpler than frame sequence VPR. SeqVLAD performs well on complex tasks, but not on simple tasks?2023/5/5 14:16:22

Hello,
I am not sure I understand how you are trying to apply seqvlad. If you use our code, it is possible to use seq_length = 1, thus resorting to single image vpr. when fed with single images, the SeqVLAD layer behaves exactly in the same way as a standard netvlad layer. We also have reported in our paper results with seq len = 1.
It could be that there are some problems in your implementation, perhaps you can use our code


retina not acurate

How to reproduce

Leaflet version I'm using: 1.3.1 but also on http://leaflet-extras.github.io/leaflet-providers/preview/
Browser (with version) I'm using: Firefox 60.0.2 or Chromium  66.0.3359.181
OS/Platform (with version) I'm using: Ubuntu 17.10

What behaviour I'm expecting and which behaviour I'm seeing
Documentation says "detectRetina : If true and user is on a retina display, it will request four tiles of half the specified size and a bigger zoom level in place of one to utilize the high resolution."
But it's not used to compute L.Browser.retina (true for browsers on a high-resolution "retina" screen.)
var retina = (window.devicePixelRatio || (window.screen.deviceXDPI / window.screen.logicalXDPI)) > 1;
On my screen, window.devicePixelRatio is 2 when browser display is zoomed to 200%
so L.Browser.retina is true as soon as display zoom is > 100% and false when browser zoom is < 100%
That is not what "retina" is meant to be.
Minimal example reproducing the issue

Open browser, zoom display to 150% (this is browser display, not map zoom)
Browse to http://leaflet-extras.github.io/leaflet-providers/preview/
Choose Stamen toner or another provider with retina tiles
Open developer 's javascript console
See the value for L.Browser.retina
See the value for window.devicePixelRatio
Open "Network" tab and see the uploaded tiles : they are @2x version
Unzoom browser (dont unzoom the map, but the browser display, using its menu)
See values...

Window has to be refreshed CTRL+F5 after browser display zoom has changed; so retina value is computed anew

Hi,
You might confuse the Tile Layer detectRetina option and the {r} in Tile Layer urlTemplate argument, which adds @2x when L.Browser.retina flag is true, as you have noticed.
While these 2 features target "retina" / high DPI devices (or when a user has increased their browser native zoom display as you noticed), they provide 2 different mechanisms (which can be combined, even though it might not be desirable):

detectRetina is a simple workaround for tile sources that do not offer the @2x alternative tiles. The drawback is that lines and text is also decreased. It is false by default, i.e. it does not play any role in http://leaflet-extras.github.io/leaflet-providers/preview/ examples.
{r} in urlTemplate takes advantage of tile sources that do offer the @2x alternative tiles, like Stamen in your case. If you pay close attention, Stamen toner and Stamen toner lite are almost the only one listed in http://leaflet-extras.github.io/leaflet-providers/preview/ that make use of this {r} feature, hence which offer these alternative tiles for high DPI devices.

Hope this helps.

Hum if I understand correctly, this probably follows your issue https://github.com/Leaflet/Leaflet/issues/6193.
What do you mean by "That is not what "retina" is meant to be."?

#6193 has been fixed with  https://github.com/leaflet-extras/leaflet-providers/commit/975977fe0146b4c84ecb861c2d848aa01ef254aa
BUT there there is an issue with L.Browser.retina since my screen is not retina and retina tiles should never have been requested.
As the documentation states it, L.Browser.retina is supposed to reflect a high-resolution "retina" screen
but AMOF it doesnt : it only reflects when the browser display zoom > 100%.
i suggest to reopen this issue
Did you try the reproduce-steps ?

The steps and result you describe are the expected behaviour.
Although the flag is called "retina", it targets high DPI, and the case of a natively zoomed browser window is also considered in that category. Now this may be argued upon, but it seems to me that this is for a reason and it does not harm much in any case: why do you absolutely want not to load @2x tiles when your browser window is zoomed? That provides with crisper graphics, instead of blurry zoomed images.

Ok I understand. You're right about avoiding blurry images.
What now might be improved is the wording and the explanation : both "retina screen" and "high DPI" (dot per inch = screen property) are not fit to describe what L.Browser.retina realy is.
I propose https://github.com/Leaflet/Leaflet/pull/6203


Documentation of the new PSN API?

First, truly great and detailed documentation of the API used by https://my.playstation.com
With the release of the new PSN app so is there a new base URL to access information with support for PS5 titles and other updated information as well, https://m.np.playstation.net/api/
So I simply wonder if you will take on the task to document this as well? At the time of this writing so does https://my.playstation.com still uses the old API and can't display PS5 titles.

Hi @Ragowit, thanks for the feedback I appreciate that.
I'm interested in looking in to the new APIs but it might have to wait until they update https://my.playstation.com to use them as I have not found a way to be able to successfully capture the traffic of the app to see the calls it's making. It seems to communicate entirely over HTTPS and even when using a proxy so that I can do SSL inspection the app doesn't seem to use it properly.

There was a comment here that might help you, if you want to investigate further: https://github.com/Tustin/psn-php/issues/146#issuecomment-727098493
Otherwise it might be easiest to wait until they update the site, as you said.

Just to let you know I've uploaded some initial documentation for the new API now.
Thanks for that link, it helped in understanding how to authenticate to the new API.

Looking good! Thanks for the update. I have found a "reward" attribute for trophies, and I have so far only encountered it with the game "Destruction AllStars". Easy to miss since its hard to find.

Nice spot on that, I'll add in over the next few days.


Pass parameter with composite key columns to DB sink.

One example for a use case where we would have multiple columns for a sink upsert on composite key. The sink in this case is specifically a DB table and the primary keys are passed as a parameter string  e.g. say parameter is $dmPKcol and somewhere in the mapping we've set the value to  "cust_id, cust_seq_id".
This is similar to update dim_cust set cust_name = "foo" where cust_id = 123 and cust_seq_id = 10.1
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 09dd1d03-ae28-c5a2-7c64-2f51675f6b09
Version Independent ID: dac74d68-2105-a029-1f49-d444c0a252f4
Content: Copy and transform data in Azure SQL Database - Azure Data Factory
Content Source: articles/data-factory/connector-azure-sql-database.md
Service: data-factory
GitHub Login: @linda33wj
Microsoft Alias: jingwang

@tsaru72 Thank you for the detailed feedback.
We are actively investigating and will get back to you soon.

@tsaru72
Thanks for leveraging Azure docs feedback channel to raise this question. This channel is reserved for ‘Azure docs’ feedback- for sharing doc feedback and suggesting content improvements. We didn't determine any changes for this documentation upon reviewing this feedback.
If your issue is specific to a use case, we request you to please reach out in forums like Microsoft Q&A or Stackoverflow. We have our engineers and other community members who will be happy to assist. Forums have a better suited audience for such queries. Once your issue is posted in forum, please do share the forum thread link here for tracking.
If you have a document which you are following and if you think it needs an update, please let us know about that here.
Thank you

@tsaru72
We will now proceed to close this thread as we have not heard back from you. Please do share the forum thread link here for reference, If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.
Thank you

This was a doc feedback to elaborate the document  on that specific
section. Take a look at this issue
https://stackoverflow.com/questions/61329833/how-to-pass-a-data-flow-parameter-in-key-column-in-sink-tanformation-while-updat
Anyways, you can close it but I had to give my feedback.
On Thu, Feb 18, 2021 at 1:07 PM Kranthi Pakala<EMAIL_ADDRESS>wrote:

@tsaru72 https://github.com/tsaru72
We will now proceed to close this thread as we have not heard back from
you. Please do share the forum thread link here for reference, If there are
further questions regarding this matter, please tag me in your reply and
reopen the issue. We will gladly continue the discussion.
Thank you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/70704#issuecomment-781534837,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAI66EXNF3RG7W427EEZNTTS7VJPXANCNFSM4XXWJUTA
.


Removes an instance of signed integer overflow undefined behaviour.

The UB is benign but may interact badly with optimization and is
flagged by UB sanitizers.

Values that are used as array indices become size_t.
TCCMap::hash can be private, as the usage of the hash value is
an internal implementation detail.
Use std::hash for hashing the elements of TCCRecord. Double hash
the first element so that {a,b} hashes differently to {b,a}

Reference an existing issue

@folded Many thanks for the PR! Are there any other instances of UB or other issues flagged by static analysis that you're presently aware of, or is the issue addressed in this PR the only one?

Also, do you have guidelines for running the analysis to check what the analysis output is before / after this PR?

This was brought to my attention by another team whose tests were failing when run under asan. It's the only case that I'm aware of currently, but I haven't tried running the numba test suite with asan yet. I would pessimistically assume that there are other cases.

I'm not sure how you would reproduce this outside of our internal environment. I've landed the patch internally, and it's also possible to inspect the patch to see that it removes the multiply. The error that we intially saw was:
numba/core/typeconv/typeconv.cpp:19:25: runtime error: signed integer overflow: 3430005 * 1000003 cannot be represented in type 'int'
Which overflows 32 bits (but not 64)

Many thanks for the details! I'll add this to the review queue.

Found one more trivial instance of UB and filed an issue for one that is less so. After that there's an unaligned access from numba (which seems intended).

@gmarkall @sklam this patch looks good to me. The key space is now size_t which is still massive in comparison to what is ever going to be feasible in a program. The use of std::hash seems like a reasonable and maintenance free alternative to the existing python-hash based alg. Any thoughts/objections to merging this?

This looks good to me.

Thanks for taking a look @gmarkall .

@stuartarchibald The double-hash question seems to be resolved now (as in comment on the line of code).
@stuartarchibald / @esc Could this have a full buildfarm run please?

Build numba_smoketest_cpu_yaml_101 has started

Was green. 🟢


Update License - Mapbox to MapLibre / Update Copyright

Update the license files. This is something I found while I was trying to update TileServer-GL license, which included the mapox-gl-native license and dependencies.
1.) Update LICENSE.mbgl-core.md from Mapbox to MapLibre.
2.) Update Copyright terms to match in LICENSE.mbgl-core.md and LICENSE.md
3.) Update to 2023 copyright date.

Should these files be merged into one?

Updated it.


Handle temporary directory ending with slash on windows

@pascalgrimaud Can you check if it is OK for you?
Before:
 .../Temp//jhlite-test/...

After:
 .../Temp/jhlite-test/...

yes looks fine !

Anyway, I predict you won't pass the CI. We'll see it, in few minutes ;)

Probably because I do not have tests for it ;)

@pascalgrimaud This is now ready :)


Allow re-ordering of VS Code context menu item

I really love this extension, so thank you.
I think it would be helpful to be able to configure the order of where "Open Code Here" appears in the context menu.
This may not be possible at all with Nautilus.  However, if it is possible to modify the order, I think since the number of context menu items that appears is influenced by what kind of item you are clicking on, adding a "always appear at bottom" or "always appear at top" would be useful as regardless of what you are clicking on, you will always know where the VS Code context menu item will be.

Nautilus does not allow ordering of extensions, the best you can do is trick it by naming an extension in a certain way I think.

darn, thanks


Practice Plan

Every player / every practice:

Checkin on something not basketball
notice progress

Philosophy Stack

Improve/ Get better as a player/person
Learn what it means to Compete
Play Around & Have Fun

Stretch
Adding

Higher goals
No wristbands
stealing
Back court press

How many buckets in 5 minutes
Shoot around the world
Basic Dribbling

Stay inbounds
1 hand (basic)
Switch hands (cross overs)
Partner holds numbers

Ball switch pass

Water break

Tag

Big Picture
Tuesdays:

1 player drops for scheduling conflict
moves us from 9 to 8
aka 3x3 to 4x2 for back half

Fridays stays 9 at (full cap)
Worked Well

Tree Tag
Skip To The Loop Shooting
Conga Line

For Future Time

Tree Tag (Two Trees)
4 person x2 groups
Dribbling

Conga Line - Do better use of the individiual call out

Did not Work

3 team mayhem


tableClass values

Hey. I really like the module, thank you for your work! Would it be possible to add all possible values of tableClass to the README? That would be awesome!

Hello @maxalexger, the tableClass refers to the css file, you are using. The corresponding comment is added to the readme.


Allow parquet column chunks to be deserialized to multiple arrays (e.g. iterator)

As described by @tusvold here, there are important cases where it is more advantageous to deserialize a column chunk into more than one array.
Specifically, the main issue is that a decompressed parquet column chunk is still much smaller than its corresponding arrow array. Therefore, on large column chunks, the user may prefer to deserialize only part of the decompressed column chunk into arrow while still holding the chunk in memory.
The equation is something along the lines of
size(decompressed parquet column chunk) + size(partial arrow array) <  size(complete chunk as arrow array)

To allow users to tradeoff memory usage and data fragmentation (of each array), we should offer something like
fn column_chunk_to_array(chunk, column_meta, length: Option<usize>) -> impl Iterator<Arc<dyn Array>>

that when length: None we recover our single array, when length: Some(n), we iterate over the chunk and output n items at the time.
Thanks again to @tusvold for this important insight.

It isn't so much decompressed column chunks being smaller than a corresponding array, as a single decompressed page within a column chunk being smaller than an array of the entire column chunk.
Ideally you would stream pages from the column chunk, decompressing them as needed, and only keeping them around until all the values have been yielded from that page.

I have been thinking about this. I haven't found this analysis anywhere else before, so will just leave it here for posterity.
data is split in row groups to allow for group pruning at the expense of lower compression - larger groups allow higher compression but less possible prunes, smaller groups allow for more pruning but can't be compressed as much.
We could separate this analysis between dict-encoded and non-dict encoded, but the overall conclusion is the same: the more values we pack to an compressor, the higher the maximum possible compression gains. For dict-encoded this is because dicts aren't shared between row groups.
The potential benefit to use more pages would be to allow page pruning. However, parquet itself deprecated writing page statistics since 2018. Thus, I do not really see how more pages per column chunk help us.
From this perspective, imo we should assume the optimal storage conditions: reading a column chunk with a single page (non-dict-encoded) or a column chunk with 2-3 pages (dict page + indices page + fallback page for groups with more than i32::MAX items).
Strategy 1
One strategy is to load a parquet row group in "mini-batches" of size n < N where N is the length of a row group. For this to happen, we need to:

read M compressed parquet columns to memory (for a total of M x N compressed items)
decompress the (usually single) pages on it
deserializen < N items
repeat 3. until we read all items

Strategy 2
An alternative load strategy is to load column by column:

read one compressed column to memory
decompress the (usually single) pages on it
deserialize N items
repeat 1-3 until we read all columns

Consequences of each
Let's now see how this pans out in two different data carrier patterns, "stream of chunks", Stream<Vec<Array>> (like datafusion) and "vector of streams", Vec<Stream<Array>> (like the chunked array in pyarrow).
Strategy 1 on stream of chunks

After step 1, we peak at M compressed columns
After step 2, we peak at M decompressed columns
During step 3-4, we peak at M decompressed columns + n * M deserialized items

Strategy 1 on vector of streams

After step 1, we peak at 1 compressed column
After step 2, we peak at 1 decompressed column
During step 3-4, we peak at 1 decompressed column + n deserialized items

Strategy 2 on stream of chunks

After step 1, we peak at 1 compressed columns
After step 2, we peak at 1 decompressed columns
During step 3-4, we peak at 1 decompressed column  + N * M deserialized items

Strategy 2 on vector of streams

After step 1, we peak at 1 compressed column
After step 2, we peak at 1 decompressed column
During step 3-4, we peak at 1 decompressed column + N deserialized items

Analysis
From this, my understanding is that the core difference here is between

Strategy 1: M decompressed columns + n * M deserialized items
Strategy 2: 1 decompressed column  + N * M deserialized items

Let's do some math and see the difference. Defining

b = n/N to be our batch size n relative to the row group size N.
s_e the average size of an individual encoded item in parquet
s_d the average size of an individual deserialized item in arrow
r as the ratio of s_d / s_e (the average ratio between the deserialized arrow and encoded parquet). For PLAIN, this equals 1 - ratio of nulls (since null values do not take space in parquet).

Defining S1 and S2 as the peak memory usage of Strategy 1 and Strategy 2 respectively, we can write the above as:
S1 = M * N * s_e + M * n * s_d
S2 = N * s_e + M * N * s_d

The ratio S1/S2 can be written as (divide both sides by M*N*s_e):
S1/S2 = (1 + b * r) / (1/M + r)

which is the important formula here.
We can now take two limits: M = 1 (load one column) and M = infinity (load many columns).
Low number of columns
For M = 1, we have
S1/S2 = (1 + b * r) / (1 + r)

For highly-encoded columns, say r = 4, and a batch size of 0.1 (10% of the row group), the above yields
S1/S2 = (1 + 0.4) / (1 + 4) = 0.35

For low-encoded columns, say r = 0.9, and a batch size of 0.1 (10% of the row group), the above yields
S1/S2 = (1 + 0.09) / (1 + 0.9) = 0.57

showing that S1 requires less memory (~40%)
Loading high number of columns
For M = inf, we have
S1/S2 = (1 + b * r) / r

For highly-encoded columns, say r = 4, and a batch size of 0.1 (10% of the row group), the above yields
S1/S2 = (1 + 0.4) / 4 = 0.35

I.e. S1 requires less memory (~66%)
For low-encoded columns, say r = 0.9, and a batch size of 0.1 (10% of the row group), the above yields
S1/S2 = (1 + 0.09) / 0.9 = 1.2

I.e. S1 requires more memory (~20%)
Conclusions
My conclusion atm is that Strategy 1 dominates in most cases and it should be the default (i.e. the goal of this PR). IMO this is interesting because it just shows that it is better to read the whole (after projection pushdown) row group into memory, decompress it, and then iterate on its individual columns.

data is split in row groups to allow for group pruning at the expense of lower compression

This is only partly true, the other motivator is that the row group is typically unit of IO and distributed parallelism. Separate row groups are not all that dissimilar from separate files, with all the costs and benefits thereof.

The potential benefit to use more pages would be to allow page pruning.

Pages are significantly smaller than column chunks, row groups may be up to a GB compressed, whereas pages (other than dictionary pages) are typically closer to 8KB compressed. See the end of this document. So another benefit is reducing the amount of uncompressed data that must be buffered in the read path at any point in time.

However, parquet itself deprecated writing page statistics since 2018.

That is because it now writes them into a different data structure called PageIndex that is slightly less useless. That being said I'm not aware of many systems that make use of this...

Thus, I do not really see how more pages per column chunk help us.

Regardless of the utility of multiple pages per column chunk, if interoperability with other tooling is important, multiple small pages per column chunk is likely to be an assumption of other tooling.
FWIW I agree that page pruning based on statistics is not particularly effective for most use-cases, I have a proposal for selection masks in parquet that I hope to start work on in the latter half of this week - https://github.com/apache/arrow-rs/issues/1191.

I now have a fix for this on my local, I am just cleaning it up before a PR. It reads the pages as they are needed.


"WifiController" missing "set_configuration" method?

Hey All,
Having issues with the .set_configuration method where it can't be found within the esp_wifi::wifi::WifiController.
However it is recognizing that the method is available wifi.rs(338, 8): the method is available for 'esp_wifi::wifi::WifiController<'static>' here
Am I missing something?

Never mind, did an update and found it.


Fixed broken set time with http feature.

Bug fix
Installation output:
Configuring eth0 with static ip <IP_ADDRESS>... OK
Set time using ntpdate... Failed to set time via ntpdate. Switched to rdate.
Set time using timeserver 'time.nist.gov'... 'time.nist.gov'... 'nist1.symmetricom.com'... 'nist-time-server.eoni.com'... 'utcnist.colorado.edu'... 'nist1-pa.ustiming.org'... 'nist.expertsmi.com'... 'nist1-macon.macon.ga.us'... 'wolfnisttime.com'... 'nist.time.nosc.us'... 'nist.netservicesgroup.com'... 'nisttime.carsoncity.k12.mi.us'... 'nist1-lnk.binary.net'... 'ntp-nist.ldsbc.edu'... 'utcnist2.colorado.edu'... 'nist1-ny2.ustiming.org'... 'wwv.nist.gov'... Failed to set time via rdate. Switched to HTTP.
Set time using HTTP timeserver 'http://chronic.herokuapp.com/utc/now?format=%25F+%25T'... Fri Sep 30 14:18:25 UTC 2016
OK
Time (UTC): Fri Sep 30 14:18:25 UTC 2016

Installation started at Fri Sep 30 14:18:12 UTC 2016.

Introduced with 718474d38d30c4df6c4a34e17685e980daf96716.
Thanks for fixing! Nice to see the new, cleaner output including your enhancement.


DUPLO-25452: Added support for GCP Redis Instance Resource

Overview
Added support for GCP Redis Instance Resource.
Summary of changes
This PR does the following:

Introduced GCP Redis Instance resource and data sources for managing GCP Redis Instance in DuploCloud.
Added CRUD operations and data retrieval for GCP Redis Instance resources.

Testing performed

[ ] Using unit tests
[ ] Manually, on my local system
[ ] Manually, on a remote test system

Task linked: DUPLO-25452 Support of google Memorystore (Redis) in duplo tf provider


Example 7 seem to send file twice

Example 7 with separate "start upload" button at hayageek.com seem to send file twice

Twice means, is it sending two requests ? It is expected. If you select N
files, it will send N requests, to get the progress for each file
On Sunday, 26 July 2015, Alexey Torkhov<EMAIL_ADDRESS>wrote:

Example 7 with separate "start upload" button at hayageek.com seem to
send file twice
—
Reply to this email directly or view it on GitHub
https://github.com/hayageek/jquery-upload-file/issues/61.

Yes, two requests. But for one file.

But i have checked just now. I am seing only one request. Which browser did
you try ? can you share your UR ?
On 27 July 2015 at 14:13, Alexey Torkhov<EMAIL_ADDRESS>wrote:

Yes, two requests. But for one file.
—
Reply to this email directly or view it on GitHub
https://github.com/hayageek/jquery-upload-file/issues/61#issuecomment-125099166
.

I'm using Firefox 39. I've attached screenshots with firebug and details of requests. What is UR btw?

Fixed down. V 4.0.2


net/http, x/net/http2: client loses the request body when retrying after HTTP2 server close connection gracefully(GOAWAY)

What version of Go are you using (go version)?

$ go version
go version go1.13.7 darwin/amd64

Does this issue reproduce with the latest release?
YES, I run the reproduce code in golang docker container with latest image(golang:1.14.2-buster), still occur this bug.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/Joe/Library/Caches/go-build"
GOENV="/Users/Joe/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/Joe/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/Joe/go/src/golang.org/x/net/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/vk/bngnkbgj09v1cn56dsbrvs540000gn/T/go-build201607743=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

Set up a HTTP2 server with a handler which will send GOAWAY frame
Use a HTTP client to request HTTP2 server in multi goroutine in concurrency
HTTP client may got a 500 HTTP response code with error request declared a Content-Length of N but only wrote 0 bytes

Example codes in Go Playground: https://play.golang.org/p/8eiVRYqRyc6
Already known after I debug

HTTP2 RoundTrip received the request which body has no content, after I re-set req.body = req.GetBody() in HTTP2 RoundTrip, the bug will not occur again. codes like:

// RoundTripOpt is like RoundTrip, but takes options.
func (t *Transport) RoundTripOpt(req *http.Request, opt RoundTripOpt) (*http.Response, error) {
	if !(req.URL.Scheme == "https" || (req.URL.Scheme == "http" && t.AllowHTTP)) {
		return nil, errors.New("http2: unsupported scheme")
	}

	if req.GetBody != nil {
		var ierr error
		req.Body, ierr = req.GetBody()
		if ierr != nil {
			return nil, ierr
		}
	}

Based 1., the higher RoundTrip(golang net/http RoundTrip) lost request body when retry, BUT I found the the RoundTrip has re-wind body when re-try:
https://github.com/golang/go/blob/881d5405402d6e8c54f83eed6216a9ed29778006/src/net/http/transport.go#L586-L596

What did you expect to see?
HTTP client should not got error after received GOAWAY when re-try the request
What did you see instead?

cc @bradfitz
Need your help, I had already debug with many days but did not found the root cause.

/cc

I ran the reproducer locally and reproduced it.

I haven't found where the issue is but I do know we are reusing a req.Body on the http2 transport side. What I have determined is that we read the data once and then we reuse the body which has no more data.

we are reusing a req.Body on the http2 transport side

I found http2 transport entrypoint get the request which has no data, and base that I think we are reusing a req.Body on http transport but not http2 transport.  I test with adding the following codes in http2 transport entrypoint and got panic:
// RoundTripOpt is like RoundTrip, but takes options.
func (t *Transport) RoundTripOpt(req *http.Request, opt RoundTripOpt) (*http.Response, error) {
	if !(req.URL.Scheme == "https" || (req.URL.Scheme == "http" && t.AllowHTTP)) {
		return nil, errors.New("http2: unsupported scheme")
	}

	// check request body has data, panic if it's no data
	if req.Body != nil || req.GetBody != nil {
		body, err := ioutil.ReadAll(req.Body)
		if err != nil {
			return nil, err
		}

		if len(body) == 0 {
			panic("http2 roundtrip get a requst which body has no data")
		}

		var ierr error
		req.Body, ierr = req.GetBody()
		if ierr != nil {
			return nil, ierr
		}
	}

I found the issue and I have a solution but I need to better understand the flow.
The failure occurs in the http transport when the altRT.RoundTrip is taken. Later on a second RoundTrip occurs, but a new request & body wasn't created.

Took a bit of time but I figured out the problem.
An http2 request is attempted via altRT.RoundTrip. The first attempt writes the body but fails because the connection gets a GOAWAY. The http2 side retries but gets a no cached connection error which bubbles up as a ErrSkipAltProtocol.
The http side takes over and tries again but this time the body is already read.
Given we never reset the body in the existing request, I am not certain how to solve this other than no returning the ErrSkipAltProtocol if we have already written the body.

(There was work in this area recently in ea1437a8cdf6bb3c2d2447833a5d06dbd75f7ae4 for #34978 and #35113 but I haven't read this bug or those ones enough to know whether they're related.)

@bradfitz It doesn't look like it. Its a corner case that has always been broken.
Retrying on the http2 side and then returning an ErrSkipAltProtocol after a failed attempt seems odd.
I just don't know how to fix the implicit constraint that a req's body is only read once given we are allowing the http side to use a request that has already been processed.
One answer would be to always make a new request if the altRT path is taken since we can't tell what if anything has been touched.

I do have a fix that returns Get "https://<IP_ADDRESS>:45927/put/0": http2: Transport received Server's graceful shutdown GOAWAY rather than the status code: 500, body: request declared a Content-Length of 5 but only wrote 0 bytes. Normally one might see http2: no cached connection was available but that would normally be replaced by the ErrSkipAltProtocol.
The other option would be to always create a new request to allow this request to be reused later if necessary.

I misunderstood that http2 request will never take altRT.RoundTrip before.
What about we fix http roundtrip altRT.RoundTrip error process like:
	if altRT := t.alternateRoundTripper(req); altRT != nil {
		if resp, err := altRT.RoundTrip(req); err != ErrSkipAltProtocol {
			return resp, err
		}

		if req.GetBody != nil {
			var ierr error
			req.Body, ierr = req.GetBody()
			if ierr != nil {
				return nil, ierr
			}
		}
	}

I do have a fix that returns Get "https://<IP_ADDRESS>:45927/put/0": http2: Transport received Server's graceful shutdown GOAWAY rather than the status code: 500, body: request declared a Content-Length of 5 but only wrote 0 bytes.

I don't think return an error is acceptable.

I think I had figured out what happening:

Alternate RoundTrip is configured "https" with golang.org/x/net/http2 by us.
http2 RoundTrip("https" Alternate RoundTrip) has sent request body but received a HTTP2 GOAWAY frame, and then failed re-try to get connection from connection pool. The error is wrapper as ErrSkipAltProtocol.
Then http RoundTrip take over request, and we do not re-set request body here:

https://github.com/golang/go/blob/bb59a1360a9e6c2d32a59461da56e9bc3a5703ef/src/net/http/transport.go#L514-L518
And I think https://github.com/golang/go/issues/39086#issuecomment-629921722 would be a good solution.

/cc @bcmills

Is this a duplicate of #32441?

@bcmills yes it is.

Duplicate of  #32441

Thanks @fraenkel @bcmills


Rendering artefacts with enabled animations

When using the latest version on master with a ui-layout that fills the whole screen, there are scrollbars spontaneously appearing/disappearing and also the ui-layout's overall size is not always right.
See the following plunker
Just move the slider around to see the issues.

As a quick fix, I would suggest to make animations a configurable (optional) feature.

was this ever fixed ? If I toggle the visiblity of the left hand pane , I get scrollbars on the middle during the animation


Custom menu bar mnemonics take over when using keyboard.dispatch

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.69
OS Version: Ubuntu 22.04

While testing the new titleBarStyle on custom mode, I noticed the keyboard behavior changes and breaks my shortcuts. Most "alt" based shortcuts stop working. Setting the titleBar back to native fixes everything
Is there any reason for titleBarStyle to modify the keyboard?
Steps to Reproduce:

Set keyboard copy/paste to Alt-C and Alt-V

Settings
"keyboard.dispatch": "keyCode"
"window.titleBarStyle": "custom"

Try to copy paste

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.69.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

There are a few settings that might work as a workaround for you:
window.customMenuBarAltFocus and window.enableMenuBarMnemonics
but it does seem like a bug that we don't recognize the conflict of mnemonics and shortcuts with the keyboard.dispatch setting.

@fgarcia I am having trouble reproing this issue. Can you let me know if you are able successfully paste with Alt+V using window.enableMenuBarMnemonics set to false

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


refactor: nmf resolve for scheme hook

Summary

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

!bench

!eco-ci


NotifySetpointsStop service for re-enabling high-level command after low-level setpoints have been used

See https://github.com/bitcraze/crazyflie-firmware/pull/560

This will start building correctly after https://github.com/whoenig/crazyflie_cpp/pull/14 is accepted and we can update the submodule.

Merged the crazyflie_cpp changes. Please update the submodule so that the build is passing. Thanks!


Start-HistoricalSearch topic updates

The updates here are made as per task: https://office.visualstudio.com/MAX/_workitems/edit/8930046/

Closing this PR as the updates were completed in #11820.


Terminal dropdown doesn't appear on first click after window reload

VSCode Version: 1.17.1
OS Version: Windows 7

The first time that I click on the terminal selector dropdown after reloading the vscode window, the list of terminals does not appear (It is just black)

Steps to Reproduce:

Open a new VSCode window
Open the integrated terminal
Reload the window ctrl+shift+p, then Reload Window
Click on terminal selector dropdown

Reproduces without extensions: Yes

https://github.com/Microsoft/vscode/issues/25700


Fix Address Balance API to Support Testnet and Signet

Fixed an issue where the service failed to fetch the BTC balance for testnet addresses due to the Blockchain.info API not supporting testnet addresses. Updated the implementation to use an alternative API that supports testnet addresses.
This is a response to this issue #38
Changes:

Replaced the Blockchain.info API endpoint with a suitable alternative for testnet support mempool.
Ensured the solution handles both mainnet and testnet addresses correctly.

This fix resolves the error encountered when connected to testnet and ensures compatibility with testnet address queries. Please review the changes and provide feedback if further adjustments are required.

great work on this @JoE11-y sorry i totally missed it. ended up fixing the testnet stuff and added a few more networks / wallets. ill be sure to keep my eyes on my notis next time.

closing for #40


Command not found in Manjaro Linux VSCode when open project from context menu

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.85.0
OS Version: Manjaro Linux

Steps to Reproduce:
Here is a demo to repro this issue.
ManjaroIssueSample.zip

Install latest vscode in Manjaro Linux Desktop
Open file explorer, navigate to project folder, right click to open context menu -> open folder with -> visual studio code (if no vscode in list, go to other application -> development -> vscode)
Execute Launch via NPM
VSCode throw error: command not found
Execute npm run debug in vscode terminal, working well
Open system terminal and launch vscode by code command, open project and execute script, working well

Expected Result:
Script should work well when open project from context menu

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.85.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Works for me. Is it possible that npm is not on your PATH? Can you share the exact error message?

Hey @roblourens , thanks for the response. I have used nvm to install node and npm before.
Now I have tried to uninstall my nvm managed node and re-install node and npm directly, it works well now. It should be the variable path issue.
But actually I'm not familiar with Manjaro Linux, could you please let me know why vscode had different behavior by context open and command open?

Hey @roblourens, this issue might need further attention.
@EzioLi01, you can help us out by closing this issue if the problem no longer exists, or adding more information.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Display "accepted" on finalized bounties

On the current site there is an "accepted" bar that displays at the top of finalized bounty pages to make it clear it is completed:

This is currently not done on the staging site:

Need to update to match the original styling with an "accepted" banner above the fold.

Almost perfect but on mobile the bar stretches across the entire screen. Would like it to be the same size as the desktop button instead.


Configure Mocha to prevent stubbing non-existent methods

I wanted to enable this option in the tests I'm adding for a new smart answer, but it seems more sensible to enable it for all tests rather than just the ones I'm working on.
The commits in this PR fix a few tests that failed when I enabled the option. The final commit enables the option.

This is great :+1:


Doesn't work in tmux 3.3_a with tmux term type

Environment:

Distro: Arch Linux
Terminal: foot 1.13.1
tmux 3.3_a
tty-copy 0.2.2

Running in a new tmux session with the following config
tmux.conf
set-option -ga terminal-features ',foot:clipboard'
set-option -g set-clipboard on

Setting are applied correctly as can be seen in the following commands executed in the tmux session
$ tmux show -s set-clipboard
set-clipboard on

$ tmux info | grep Ms:
 192: Ms: (string) \033]52;%p1%s;%p2%s\a   # <- for this to be correct, TERM should be set to foot before entrying the tmux session

$ tmux show -s terminal-features
terminal-features[0] xterm*:clipboard:ccolour:cstyle:focus:title
terminal-features[1] screen*:title
terminal-features[2] foot:clipboard

When tty-copy detects that term type is tmux, or when manually forcing this with --term tmux option, then it doesn't copy to the clipboard correctly.
The issue resolves when forcing screen as term type, or when setting TERM to a different value than screen.
No such problem when not in tmux session.
My current solution is to force screen term type using an environment variable.
diff --git a/tty-copy.c b/tty-copy.c
index 8dca4ca..d8ecd0d 100644
--- a/tty-copy.c
+++ b/tty-copy.c
@@ -145,7 +145,7 @@ static void parse_opts (int argc, char * const *argv) {
                opts.tty_path = _PATH_TTY;
        }

-       const char *term = NULL;
+       const char *term = NULL, *tmux_override = NULL;
        if (term_type != NULL) {
                opts.is_screen = str_equal(term_type, "screen");
                opts.is_tmux = str_equal(term_type, "tmux");
@@ -154,8 +154,11 @@ static void parse_opts (int argc, char * const *argv) {
                if (str_startswith(term, "screen")) {
                        // Since tmux defaults to setting TERM=screen (ugh), we need to detect
                        // it here specially.
-                       if (getenv("TMUX") != NULL) {
-                               opts.is_tmux = true;
+                       tmux_override = getenv("TTYCOPY_TMUX_OVERRIDE");
+                       if (getenv("TMUX") != NULL &&
+                               (tmux_override == NULL ||
+                               strcmp(tmux_override, "1") != 0 )) {
+                                       opts.is_tmux = true;
                        } else {
                                opts.is_screen = true;
                        }

Oh! The solution is to enable passthrough of escape sequences in tmux.
set-option -g allow-passthrough on

This is not documented in tmux's Clipboard wiki page.
Maybe document this here?


fix: upgraded to now use husky 2.0.0, fixed vulnerability

:tada: This PR is included in version 1.2.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Enhancements to reduce trend worries

Because we talk a lot about this on Slack, but it's not documented here:
Is there enough concern about the seasonal trends to:
(a) take off the triangles? (small task)
(b) overlay last year/month/week (large task)
(c) do something else?
I think the question boils down to...are the triangles more helpful than hurtful? We have many applications with seasonal trends where the triangles aren't useful and possibly misleading...unless it's to see that we're hitting a new season. We also have applications that we do want to know if the traffic is going up/down right now (so in those cases, the triangles are useful).
The reason I think (b) is a "large" task is because we have not currently explored  GA further than 1 year out. That would require us using the data that we've been collecting via Jenkins. I won't call it an XL task, because I do think it'll be pretty straightforward, but just to be safe, calling it "large".

We have a disclaimer in the caption now, so there is at least more information about what the trends represent.


Error: Can't add new command when connection is in closed stat

Describe the bug
Error with reestablishing connection to mysql.
[2020-06-12 21:30:21.465 +0000] ESC[31mERRORESC[39m (MySqlDriver/1 on kubevious-6f59b8958f-4cz2p): ESC[36m[executeStatement] ERROR IN RULE_QESC[36m    at Connection._addCommandClosedState (/app/node_modules/mysql2/lib/connection.js:137:17)ESC[39m
ESC[36m    at PreparedStatementInfo.execute (/app/node_modules/mysql2/lib/commands/prepare.js:27:29)ESC[39m
ESC[36m    at /app/node_modules/kubevious-helpers/lib/mysql-driver.js:116:31ESC[39m
ESC[36m    at Promise._execute (/app/node_modules/bluebird/js/release/debuggability.js:384:9)ESC[39m
ESC[36m    at Promise._resolveFromExecutor (/app/node_modules/bluebird/js/release/promise.js:518:18)ESC[39m
ESC[36m    at new Promise (/app/node_modules/bluebird/js/release/promise.js:103:10)ESC[39m
ESC[36m    at /app/node_modules/kubevious-helpers/lib/mysql-driver.js:113:24ESC[39m
ESC[36m    at tryCatcher (/app/node_modules/bluebird/js/release/util.js:16:23)ESC[39m
ESC[36m    at Promise._settlePromiseFromHandler (/app/node_modules/bluebird/js/release/promise.js:547:31)ESC[39m
ESC[36m    at Promise._settlePromise (/app/node_modules/bluebird/js/release/promise.js:604:18)ESC[39m
ESC[36m    at Promise._settlePromiseCtx (/app/node_modules/bluebird/js/release/promise.js:641:10)ESC[39m
ESC[36m    at _drainQueueStep (/app/node_modules/bluebird/js/release/async.js:97:12)ESC[39m
ESC[36m    at _drainQueue (/app/node_modules/bluebird/js/release/async.js:86:9)ESC[39m
ESC[36m    at Async._drainQueues (/app/node_modules/bluebird/js/release/async.js:102:5)ESC[39m
ESC[36m    at Immediate.Async.drainQueues [as _onImmediate] (/app/node_modules/bluebird/js/release/async.js:15:14)ESC[39m
ESC[36m    at processImmediate (internal/timers.js:456:21)ESC[39m
Unhandled rejection Error: Can't add new command when connection is in closed state
    at Connection._addCommandClosedState (/app/node_modules/mysql2/lib/connection.js:137:17)
    at PreparedStatementInfo.execute (/app/node_modules/mysql2/lib/commands/prepare.js:27:29)
    at /app/node_modules/kubevious-helpers/lib/mysql-driver.js:116:31
    at Promise._execute (/app/node_modules/bluebird/js/release/debuggability.js:384:9)
    at Promise._resolveFromExecutor (/app/node_modules/bluebird/js/release/promise.js:518:18)
    at new Promise (/app/node_modules/bluebird/js/release/promise.js:103:10)
    at /app/node_modules/kubevious-helpers/lib/mysql-driver.js:113:24
    at tryCatcher (/app/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/app/node_modules/bluebird/js/release/promise.js:547:31)
    at Promise._settlePromise (/app/node_modules/bluebird/js/release/promise.js:604:18)
    at Promise._settlePromiseCtx (/app/node_modules/bluebird/js/release/promise.js:641:10)
    at _drainQueueStep (/app/node_modules/bluebird/js/release/async.js:97:12)
    at _drainQueue (/app/node_modules/bluebird/js/release/async.js:86:9)
    at Async._drainQueues (/app/node_modules/bluebird/js/release/async.js:102:5)
    at Immediate.Async.drainQueues [as _onImmediate] (/app/node_modules/bluebird/js/release/async.js:15:14)
    at processImmediate (internal/timers.js:456:21)

Same as https://github.com/kubevious/kubevious/issues/12

duplicate

Resolved in v0.7.


feat: ADD LICENSE SECTION TO README.MD

Is your feature request related to a problem? Please describe.
No,
Describe the solution you'd like to see
Adding a License section to README.md file
Describe alternate solutions
ADDING A HYPERLINK TEXT IN README TO REDIRECT TO LICENSE FILE
Additional information
I would like to work on this issue , kindly assign me this

Hi @shelar1423 and thanks for your contribution! Sadly, we won't be accepting any unrequested changes to the README file for the time being.


operator: allow configurable K8s client rate limit with higher defaults

The rate limit for K8s client(s) for Cilium Operator can now be
configured separately from that of Cilium Agent with the new
--operator-k8s-client-qps and --operator-k8s-client-burst flags.
To facilitate sharing a set of default configuration options for all
clients, the Config struct was split into SharedConfig and
ClientParams, the latter of which contains options expected to differ.
With K8s 1.26 reaching EOL, the default rate limit for Cilium Agent K8s
clients is now determined by the default config, rather than relying on
the upstream client library.
Since the Operator is a Deployment and does not scale linearly with
cluster size like the Agent DaemonSet, the rate limit can be increased
to improve performance at scale without heavily impacting control plane
resources. The default rate limit for Operator clients has been increased
to 100 QPS and 200 Burst.
Add options to configure rate limit of Cilium Operator's K8s client.
Increase default rate limit of Cilium Operator's K8s client to 100 QPS.

/test

@pippolo84 @squeed thanks for the feedback! I took a bit of both and reworked the implementation. The Config is now modular, with Operator providing its own defaults and flags for rate limit options. LMK what you think about this approach

/test

Force pushed to add a header to a new file

/test

Do we want to keep the old flags around (maybe as a no-op), similar to --ces-write-qps-*?
ERROR 2024-08-30T22:58:27.189420924Z {"level":"error","msg":"You are using deprecated rate limit option(s) that have no effect. To configure custom rate limits please use --ces-rate-limits","subsys":"k8s-ces-controller"}


Refactor calculations

Refactored calculations::extract_coordinates and calculations::coordinates_present?
coordinates_present? Checks whether an argument matches validating criteria (numeric, not NaN), rather than returning false when matching invalidating criteria.
Also replaced .to_s == NaN with.to_f..nan?
extract_coordinates
Now calls coordinates_present? to validate the array, instead of comparing four booleans and initialising extra vars.

Just a heads-up that this caused some problems and had to be reverted. See #1130 for details.


Added debugging code to look at stack. There are two places where the…

… stack is empty and do not know why.

I had to add #include  then your code did work.
Thanks for your help.


Can Vorms provide pass/fail results for each validation specification?

Describe the bug
Can the value of Error return the correctness or error of each verification rule? When I meet the need to dynamically match each rule, I find that when Vorms verifies an error in yupResolver, it will stop at the first error. The subsequent verification will not continue. If I can get the results of multiple verification rules verification, it will provide me with great convenience.
thank you for your dedication

Reproduction
https://stackblitz.com/edit/vorms-validate-with-yup-12529w?file=src/App.vue
Steps to reproduce
Fill capital AA in the password field and press send, the following two rules will not pass:
min(8)
lowercase()
Expect to get two errors, and error messages.
eachErrors: {
   min: {
     ok: false,
     message: `password must be at least 8 characters`,
    },
   lowercase: {
     ok: false,
     message: `password must be a lowercase string`,
   }
}

Or other data formats that can get multiple validation errors.

Thank you.
This is a great idea to make error messages more flexible, but it conflicts with the current error object structure, and it will breaks the simple and clear DX, so may not be supported in this major version.


🐞 fixed a typo

I've added a missing been.
Note: The GitHub web editor found mixed line ending and converted them all unix-style.

:)


Duplicate decorator validation

There is many decorators where you shouldn't really be specifying it twice on the same node. A naive approach is to check when running the decorator that the value has already been set and fail if it has. The problem with this approach is when composing types with is or with decorators being called from other decorators you might end up in this scenario where something else set the value and you want to override it.
In that case we need to remove the original validation but I think it would still be good to be able to emit a warning if calling the same decorator twice on the same node. (Or even maybe cases where there is multiple decorators that could conflict) This would most likely be a per decorator rule.
// Bad

@get
@get
op foo: string()

// Ok
@get
op Getter<T>(): T

@get // respecify get (noop
op foo is Getter<string>;

// Bad

@get
@post
op foo: string()

// Ok
@get
op Getter<T>(): T

@post // override get with post
op foo is Getter<string>;

Other decorators where this would be good:

@service
@route

helper for decorators to opt in to this validation

pri: 1
est: 5


Bluetooth: controller: Support user defined CPR intervals

Some proprietary protocols that reuse the Bluetooth LLCP logic requires that the CPR interval has a valid range that differs from the Bluetooth specification defined.
Vendor must implement the function (ull_vendor.h)
u16_t ull_get_cpr_interval_min_limit(struct ll_conn *conn)
that returns the valid limit for the given connection.

There is an unrelated build error in CI due to ull_sched.c missing to include a dependency for lll.h to able to work.

There is an unrelated build error in CI due to ull_sched.c missing to include a dependency for lll.h to able to work.


zchunk: 1.1.8 -> 1.1.9

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

Result of nixpkgs-review pr 117396 at ad8aaa1e run on x86_64-linux 1

1 package skipped due to time constraints:

librepo

6 packages built successfully:

libdnf
microdnf
python38Packages.librepo
python39Packages.librepo
rpm-ostree
zchunk


Db 319 update submission

@bsweger, @nmonga91: This allows existing submissions to be updated, in which case new information overwrites the old submission, and any affected jobs have their status reset.

@jworcestBAH done reviewing this


Questions about evaluating code

Dear author, hello. While running the evaluation of your pre trained code, the following issue occurred. After searching, I found that it was a call to timm's creat_madel. Do you have this problem during the evaluation? Also, what are the metrics for pretraining your Large model? Can you please provide it? I don't have that many graphics cards, so I want to observe the pretraining results based on the indicators. Looking forward to your reply, thank you!
Traceback (most recent call last): File "D:\zc\RGBD-Pretrain-main\validate.py", line 374, in < module> main() File "D:\zc\RGBD-Pretrain-main\validate.py", line 361, in main validate(args) File "D:\zc\RGBD-Pretrain-main\validate.py", line 144, in validate model = create_model( File "D:\Anaconda3\envs\RGBD_Pretrain\lib\site-packages\timm\models\_factory.py", line 113, in create_model raise RuntimeError('Unknown model (%s)' % model_name) RuntimeError: Unknown model (DFormer_Large)

This issue not appears on my device (3090 and ubuntu). Your device did not recognize the local models. It may be caused by the system difference between the Linux and Window. On your device, it only support the offical models in TIMM. You need to let the device recognize the local models.


Set release managers as CODEOWNERS for release-1.9

Part of https://github.com/istio/istio/issues/29490

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
77e39177c8a4be579d7927dec2b1bc8f31f8ec45
link
/test release-notes_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@shamsher31: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio_release-1.9
77e39177c8a4be579d7927dec2b1bc8f31f8ec45
link
/test release-notes_istio_release-1.9

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test release-notes_istio_release-1.9

/test release-notes_istio_release-1.9


WN: Override InputNumber type attribute

Description
See https://github.com/dotnet/AspNetCore.Docs/issues/33442#issuecomment-2330249873
Page URL
https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-9.0?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-9.0.md
Document ID
4e75ad25-2c3f-b28e-6a91-ac79a9c683b6
Article author
@Rick-Anderson

Is this Blazor related? @guardrex

It is ... moving to #33556.


Application doesn't launch[BUG]

Office Tool Plus Version, e.g. <IP_ADDRESS>:

<IP_ADDRESS>

Operating System, e.g. Windows 10 20H2 or Windows 7 SP1:

Windows 7 SP1 x64 [MBR]

Error description (required):

Application isn't launching at all. I've tried both packages (the one with no runtime, and with runtime). The required .NET framework software is already installed in the system.
Tried launching after disabling antivirus but no luck, same case in safe mode as well.

Anyway, to check what's the issue with some log or tracking method?
Reproduction steps (suggested):
Nothing, just trying to open application but it doesn't.
Screenshot (suggested):
https://youtu.be/Cc_W3RlGLwk [Video - 30 Seconds]
Additional information (optional):

To run Office Tool Plus, please make sure you have upgraded your Windows 7 to the latest version.
Download update pack here: https://download.coolhub.top/Extensions/Win7_UpdatePack/UpdatePack7R2-22.8.10.exe

To run Office Tool Plus, please make sure you have upgraded your Windows 7 to the latest version.
Download update pack here: https://download.coolhub.top/Extensions/Win7_UpdatePack/UpdatePack7R2-22.8.10.exe

Thanks a lot sir, upon installing this update, it started working as usual.
Thank you so much!


Correct 'cases by date' report wrt. save & return

The report was counting cases as submitted on the date they
were created, but with save and return, that's not always
the case. This commit fixes that, counting start and
submission dates separately.

This is a test. Please ignore

| No | Sadly        | There is none              |

Except this, which is a poor alternative

There really


The registry read access problem.

When I cuber deploy, I got this:
Cloning Git repository
正克隆到 '.cuber/repo'...
remote: Enumerating objects: 94, done.
remote: Counting objects: 100% (94/94), done.
remote: Compressing objects: 100% (75/75), done.
remote: Total 94 (delta 2), reused 92 (delta 2), pack-reused 0
接收对象中: 100% (94/94), 42.71 KiB | 247.00 KiB/s, 完成.
处理 delta 中: 100% (2/2), 完成.

-----> Building image using buildpacks
20: Pulling from heroku/buildpacks
Digest: sha256:08688e88e6e0debc7f4df556fd2d5a71fee1ab501715ae1f54b9792e9f7708a1
Status: Image is up to date for heroku/buildpacks:20
ERROR: failed to : ensure registry read access to linusef/docker-demo:2a63d19-20220624174615
ERROR: failed to build: executing lifecycle: failed with status code: 1
Cuber: pack build failed

I spent whole night to figure it out, but failed. Can't find a solution. 😂
This is a really cool deploy tool, better than kuby, but maybe we need a more detailed document.

OK, Thanks. I'll make more research on it.
Is there any problem with my Cuberfile? I've tried many versions.
app 'docker-demo'
repo 'https://github.com/szluyufeng/docker-demo.git'
buildpacks 'heroku/buildpacks:20'
image 'linusef/docker-demo'
dockerconfig 'dockerconfig.json'
kubeconfig 'kubeconfig.yml'
proc :web, 'bundle exec puma', scale: 4
cache false

env 'RAILS_ENV', 'production'
env 'RAILS_MASTER_KEY', File.read('config/master.key'), secret: true

# Migrations
migrate 'rails db:migrate'

{
  "auths": {
    "https://index.docker.io/v1/": {
      "Username": "linusef",
      "Secret": "my_token"
  }
}

image 'linusef/docker-demo'

I see now that linusef/docker-demo is the name of your personal repo... So probably the error above, raised by pack, means that you don't have access to that Docker repository or that it doesn't exist.
If you try a normal docker push of any image to that Docker repo, does it work?
Please note that in the current version of Cuber the dockerconfig 'dockerconfig.json' is only used by Kubernetes... Your local machine needs to have access to the Docker repo. i.e. the docker build / docker push do not read that dockerconfig file, but the general configuration of Docker on your local machine.
migrate 'rails db:migrate'

A complete example of Cuberfile for Rails is available here:
https://discuss.rubyonrails.org/t/cuber-a-new-simple-way-to-deploy-rails-apps/80156

docker push is working fine. Still can't figure out the problem, it's wired. 😂
Really appreciate your answer. If I can fix this I will post it here.

@szluyufeng I made a quick search and I find this post on StackOverflow with the same error:
https://stackoverflow.com/a/71628784/51387
Point (1) is the solution in my opinion... As I already said you first need to login to Docker using docker login or the Docker Desktop UI.
Point (2) can be ignored in our case, since Cuber automatically adds the tag to the image for you.

@collimarco Yes, "docker login" works, and so does "docker push". I think you are right, it's a buildpack issue, maybe a cache issue.

@szluyufeng Sorry for the late reply, I just saw this. I never solved the issue(which I really want). Finally I got back to the old solution, deploying with capistrano. But I am still interested in Cuber, and will put much more effort to make it running in the future.


Bug fix: do not mutate the offset in the LimitExecutor

The mutation could not be reset during initializeCursor, thus the offset was broken in subsequent iterations of a subquery.

http://jenkins01.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/2963/


Bumped kpi tracker

Purpose
Add manual run step
Changes
Add manual run
Reuse environment variable across the entire file
Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

Oh, can you change the version in the changelog? Also for the 1.2.3 for the chain-prometheus-exporter.


How to uninstall h-encore?

My PSVita has some problems and I want to uninstall h-encore completely.
I want to delete all my files, format memory to make my PSVita fresh clean and then reinstall h-encore.
So how to uninstall h-encore or can I just format with h-encore installed ? Won’t it cause any issues formatting with h-encore installed?
Sent from PPHub For GitHub

Yeah. Not sure why you still use that when you can do enzo.

I want to delete all my files, format memory to make my PSVita fresh clean
and the reinstall h-encore.
So how to uninstall h-encore or can I just format with h-encore installed
? Won’t it case any issues formatting with h-encore installed?
Sent from PPHub For GitHub https://itunes.apple.com/cn/app/id1314212521
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TheOfficialFloW/h-encore/issues/85?email_source=notifications&email_token=AJ2UATERIO3CTFXUY6EHKWTP3CX2FA5CNFSM4HY6NP52YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G2DCJMQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ2UATHFKHV4EXW4G4TQR3LP3CX2FANCNFSM4HY6NP5Q
.

I have lots of problems on my device.
I just want to do it over.

Its closed now. Because this isn't the place to ask noob questions
On Tue, 18 Jun 2019, 16:54 Licardo<EMAIL_ADDRESS>wrote:

I have lots of problems on my device.
I just want to do it over.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TheOfficialFloW/h-encore/issues/85?email_source=notifications&email_token=AJ2UATAMSLDUCQHF7EF3TL3P3EALJA5CNFSM4HY6NP52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7DGKI#issuecomment-503198505,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ2UATHY5DCDDLHHFI2FUSDP3EALJANCNFSM4HY6NP5Q
.

Noob？
Are you expecting everyone an expert?
Funny that whether restoring a device with a hack would cause problems or not is a noob question.
Sorry that I am not an expert, it is my bad not being an expert.

Its thefloWs rules not mine.
On Wed, 19 Jun 2019, 01:01 Licardo<EMAIL_ADDRESS>wrote:

Noob？
Are you expecting everyone an expert?
Funny that whether restoring a device with a hack would cause problems or
not is a noob question.
Sorry that I am not an expert, it is my bad not being an expert.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/TheOfficialFloW/h-encore/issues/85?email_source=notifications&email_token=AJ2UATHLEJ66AITVS2N4K2DP3FZN7A5CNFSM4HY6NP52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYAJNEA#issuecomment-503355024,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ2UATBSKJ6IIQS52UNUHF3P3FZN7ANCNFSM4HY6NP5Q
.


Qtimappershim Newer Vulkan issue

Hello, this is my first time writing an issue so please bear with me. I am currently using qtimappershim on the snapdragon 845 (XZ2) with blobs from @690. Everything works fine, surprisingly, except for one problem. For some reason whenever I try to run an app that uses vulkan, the graphic glitches to the point where it's unusable.

Gralloc.txt
BufferLog.txt
AdrenoVK.txt

Does driver 615 work, there's a newer ones have broken support

I have tried with v615 but it has the same issue aswell.

Ah, I should clarify the one I used was 615.37

Hmm, do the ones on the releases page work?

I tried the shims from the release page and still has the same graphical bug

Any update on this issue? I've been facing similar issues on my sdm712 that uses sdm845 display hal along with any new adreno blobs. I've tried 530, 600, 615, 728, 757 drivers and all of them seem to have the issue when used with the shim.


Streamflow - Cancel vesting itx

Fix bug with period in create vesting itx
Add Cancel vesting itx

Hi there was small change in proposal/new.tsx please adjust pr reset looks good.
ref: https://github.com/solana-labs/governance-ui/pull/1189


Tutorials start in a different pane

If you go to https://maker.makecode.com, the tutorial popout a new page.
Regression from https://github.com/Microsoft/pxt/commit/1e281b0ee2928d0695f8d83056ec495ba642dc0d

Accidentally committed instead of PR'd. Here's the fix: https://github.com/Microsoft/pxt/commit/fa5e38e2dce5505a3351ff5169c337d4f3f5487b

Cool thanks


Question: is it possible to differentiate between different unstable channels?

Maybe I'm just a hydra Noob, but sometimes I'd like to hydra-check a package from nixos-unstable vs nixpkgs-unstable vs nixos-unstable-small. Is there an argument --channel can get that will bring me there? I tried:
$ hydra-check --channel=nixos/unstable vdirsyncer
$ hydra-check --channel=unstable-small vdirsyncer

If there is, perhaps this text:
Other channels can be:
    master
    unstable (Default)
    19.03 19.09 20.03
    nixos/release-19.09

From --help, would be even more helpful if it'll include the examples I'm looking for.
Thanks again for creating this tool :heart: .

Found it!
hydra-check --channel=nixos/trunk-combined vdirsyncer

It'll still be nice to have this in the examples from --help.


mapviz fails to build on armhf

We're spinning up arm builds armhf at the moment aarch64 coming soon. mapviz makes assumptions about the architecture which fail to build.
http://<IP_ADDRESS>:8080/job/Ibin_arm_uThf__mapviz__ubuntu_trusty_armhf__binary/2/console
01:16:21.995 [ 25%] Building CXX object CMakeFiles/mapviz.dir/src/mapviz.cpp.o
01:16:22.136 /usr/lib/ccache/arm-linux-gnueabihf-g++   -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_KEYWORDS -DQT_OPENGL_LIB -DROSCONSOLE_BACKEND_LOG4CXX -DROS_PACKAGE_NAME=\"mapviz\" -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -DNDEBUG -D_FORTIFY_SOURCE=2  -I/usr/include/opencv -isystem /usr/include/qt4 -isystem /usr/include/qt4/QtOpenGL -isystem /usr/include/qt4/QtGui -isystem /usr/include/qt4/QtCore -I/tmp/binarydeb/ros-indigo-mapviz-0.0.3/include -I/opt/ros/indigo/include -I/tmp/binarydeb/ros-indigo-mapviz-0.0.3/obj-arm-linux-gnueabihf -I/tmp/binarydeb/ros-indigo-mapviz-0.0.3 -I/tmp/binarydeb/ros-indigo-mapviz-0.0.3/src    -o CMakeFiles/mapviz.dir/src/mapviz.cpp.o -c /tmp/binarydeb/ros-indigo-mapviz-0.0.3/src/mapviz.cpp
01:18:44.180 In file included from /usr/include/qt4/QtOpenGL/QGLWidget:1:0,
01:18:44.180                  from /tmp/binarydeb/ros-indigo-mapviz-0.0.3/include/mapviz/mapviz_plugin.h:43,
01:18:44.180                  from /tmp/binarydeb/ros-indigo-mapviz-0.0.3/include/mapviz/mapviz.h:71,
01:18:44.180                  from /tmp/binarydeb/ros-indigo-mapviz-0.0.3/src/mapviz.cpp:30:
01:18:44.180 /usr/include/qt4/QtOpenGL/qgl.h:85:17: error: conflicting declaration ‘typedef GLfloat GLdouble’
01:18:44.180  typedef GLfloat GLdouble;
01:18:44.180                  ^
01:18:44.180 In file included from /tmp/binarydeb/ros-indigo-mapviz-0.0.3/include/mapviz/mapviz.h:40:0,
01:18:44.180                  from /tmp/binarydeb/ros-indigo-mapviz-0.0.3/src/mapviz.cpp:30:
01:18:44.180 /usr/include/GL/glew.h:283:16: error: ‘GLdouble’ has a previous declaration as ‘typedef double GLdouble’
01:18:44.180  typedef double GLdouble;

I propose we close this as a wontfix unless someone comes forward wanting to run mapviz on an ARM. Thoughts?

I would like to fix this, but unfortunately this appears to be the result of an incompatibility between the QT OpenGL bindings and the OpenGL library on the ARM version of Ubuntu.
Fixing it will probably require replacing the use of the QOpenGLWidget canvas with something else so it doesn't have to depend on the broken QT OpenGL bindings.

I spent a while digging into this -- I've actually got a branch where I rewrote MapCavas to use QOpenGLWidget rather than QGLWidget on Kinetic (https://github.com/pjreed/mapviz/tree/kinetic-opengl-update) -- and I think it'd make sense to mark this as wontfix.
Basically, libQt5OpenGL.so on armhf is linked against libGLESv2.so rather than libGL.so, so it only has the GL ES 2.0 API available to it.  The ES API does not include any of the immediate mode rendering commands (glPushMatrix, glPopMatrix, glOrtho, etc.) that we use in all of the Mapviz plugins that do GL drawing.
That means that in order to make Mapviz build on armhf, we need to do one of two things:

Rewrite every plugin to use retained mode for drawing, which is both a pain and would prevent Mapviz from working properly over a forwarded X11 display
Directly link in libGL.so, strip out references to QGLWidget, and figure out how to do GL drawing directly on a surface that isn't managed by Qt, which would probably have the side effect of being incompatible with the QPainter drawing that some plugins do

Both of those have significant drawbacks and are a lot of work, and there hasn't really been any demand for mapviz on armhf.

I think this is the same as reported here: https://github.com/swri-robotics/mapviz/issues/660. I'm going to close this one out to remove the duplicate issue. I'm not sure that we'll support Arm builds, because typically those are running as a headless embedded device on the robots, and aren't usually where users are running Mapviz from.


create egress proposal with SMI community based on our implementation

dependent on #354

Proof of concept GitHub issue:  egress: Prototype, design, and implement a fine-grained egress policy #3045


Local Dev Server Crashes - Pinecode React

Thanks for putting these examples together.
The local development server crashes with errors like Cannot read properties of undefined (reading 'stubs'). Looks like global.iw is not defined in local. Please let me know if you need further information.
Steps to reproduce:

Clone the repo
Switch to PINECODE_REACT
npm run start

Hi @safal07 ,
Please initialize
global.iw = {};
within iw_module_stubs.js and run again using "npm run start"
Please let us know if you need more details
Thanks.


[System] Fix Registrar: Admission

nung pinalitan ko yungnew student ng transferee lumabas siya. baka sa db ko nanaman toh pa check na lang po @hibari18 @SeptemberFirst

hindi pa yan ayos nakaWIP pa yung commit ko lol

Please refer to issue #10 for the update. I've listed the things I still need to fix.


[release-0.26] Fix the latest_version function (#101)

Cherry-pick of: https://github.com/knative/hack/pull/101
/cc @dprotaso

#101 was actually broken and had subsequent follow up PRs
What's in release-0.26 is the same as release-1.0 and HEAD. So this PR is reverting to a buggier version. What issue are you seeing?
ie. https://github.com/knative/hack/blob/e11ac125e70709d1beec59d81116b392193c01fb/library.sh#L865-L915

Thanks!


do you plan to upgrade to bootstrap4

do you plan to upgrade to bootstrap4
if yes, then when do you do that?
thks.

Yes its planned with AdminLTE v3, see #710.


IRGen: Add the swiftasync attribute to the resume function call for await_async_continuation

Without this we are going to crash (timing dependent) in
withUnsafeContinuation and bridged async objective c calls.
rdar://78031499

@swift-ci Please test


Crash in calibration w/ custom mod without chem formula

Katie reported this one
She attempted to calibrate a file where the peptides had a fixed mod that did not have a chemical formula (i.e., only a mass). Calibration crashed. The crash message was a null exception. Some error in getting the chemical formula of the peptide. I assume this has to do with the mod not having a chemical formula. She replaced the mass with a chem formula and it calibrated successfully.

fixed in #1549 . Peptides with mods without a chemical formula are skipped in calibration.