Installing FoundationPress Issues

I have no idea what's going on
I tried to install following the guide. New to CLI, hell, kinda new to dev stuff as it is, am a student.
I had a few issues on my last attempt. Uninstalled and reinstalled everything - this is the code from start to finish. I read a few other issues on similar problems and tried to follow the solutions but nothing is working for me.
When I view localhost/wordpress the page displays without css and I get this at the top:
Error: file to import not found or unreadable: font-awesome.
   Load paths:
   Compass::SpriteImporter
   c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\assets\scss
   c:\Ruby23\lib\ruby\gems\2.3.0\gems\compass-core-1.0.3\stylesheets
   on line 21 of c:/wamp64/www/wordpress/wp-content/themes/FoundationPress/assets/scss/foundation.scss

16: // WP overrides
17: @import "global/wp-admin"; // FIx issues with wp-admin bar positioning
18: @import "global/wp-overrides"; // Override the default WordPress styling for some elements
19:
20: // Third party libraries
21: @import 'font-awesome';
22: @import 'motion-ui';
23:
24: // foundation global styles
25: @include foundation-global-styles;
26:

Really not sure what I need to do, but would love to get started using foundation and wordpress together. Any help will be greatly appreciated.
Here is the command line from start of install to where I'm at now:
C:\Users\Liam Lynch>cd c:\wamp64\www\wordpress\wp-content\themes

c:\wamp64\www\wordpress\wp-content\themes>git clone https://github.com/olefredrik/FoundationPress.git
Cloning into 'FoundationPress'...
remote: Counting objects: 5920, done.
remote: Total 5920 (delta 0), reused 0 (delta 0), pack-reused 5920
Receiving objects: 100% (5920/5920), 8.29 MiB | 491.00 KiB/s, done.
Resolving deltas: 100% (3209/3209), done.
Checking connectivity... done.

c:\wamp64\www\wordpress\wp-content\themes>cd foundationpress

c:\wamp64\www\wordpress\wp-content\themes\FoundationPress>npm install
npm WARN deprecated<EMAIL_ADDRESS>Please use gulp-clean-css
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
|
><EMAIL_ADDRESS>install c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-uncss\node_modules\uncss\node_modules\phridge\node_modules\phantomjs-prebuilt
> node install.js

PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1/phantomjs-2.1.1-windows.zip
Saving to C:\Users\LIAMLY~1\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip
Receiving...
  [========================================] 100%
Received 17767K total.
Extracting zip contents
Removing c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-uncss\node_modules\uncss\node_modules\phridge\node_modules\phantomjs-prebuilt\lib\phantom
Copying extracted folder C:\Users\LIAMLY~1\AppData\Local\Temp\phantomjs\phantomjs-2.1.1-windows.zip-extract-1472569184238\phantomjs-2.1.1-windows -> c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-uncss\node_modules\uncss\node_modules\phridge\node_modules\phantomjs-prebuilt\lib\phantom
Writing location.js file
Done. Phantomjs binary available at c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-uncss\node_modules\uncss\node_modules\phridge\node_modules\phantomjs-prebuilt\lib\phantom\bin\phantomjs.exe

><EMAIL_ADDRESS>install c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-sass\node_modules\node-sass
> node scripts/install.js

Binary downloaded and installed at c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-x64-46\binding.node

><EMAIL_ADDRESS>postinstall c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-sass\node_modules\node-sass
> node scripts/build.js

"c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\node_modules\gulp-sass\node_modules\node-sass\vendor\win32-x64-46\binding.node" exists.
 testing binary.
Binary is fine; exiting.

><EMAIL_ADDRESS>postinstall c:\wamp64\www\wordpress\wp-content\themes\FoundationPress
> bower install && gulp build

bower foundation-sites#~6.2.0   cached https://github.com/zurb/foundation-sites.git#6.2.3
bower foundation-sites#~6.2.0 validate 6.2.3 against https://github.com/zurb/foundation-sites.git#~6.2.0
bower fontawesome#~4.5.0        cached https://github.com/FortAwesome/Font-Awesome.git#4.5.0
bower fontawesome#~4.5.0      validate 4.5.0 against https://github.com/FortAwesome/Font-Awesome.git#~4.5.0
bower motion-ui#~1.2.0          cached https://github.com/zurb/motion-ui.git#1.2.2
bower motion-ui#~1.2.0        validate 1.2.2 against https://github.com/zurb/motion-ui.git#~1.2.0
bower jquery#~2.2.0             cached https://github.com/jquery/jquery-dist.git#2.2.4
bower jquery#~2.2.0           validate 2.2.4 against https://github.com/jquery/jquery-dist.git#~2.2.0
bower what-input#~2.0.0         cached https://github.com/ten1seven/what-input.git#2.0.1
bower what-input#~2.0.0       validate 2.0.1 against https://github.com/ten1seven/what-input.git#~2.0.0
bower fontawesome#~4.5.0       ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/FortAwesome/Font-Awesome.git", exit code of #128 fatal: unable to access 'https://github.com/FortAwesome/Font-Awesome.git/': Unknown SSL protocol error in connection to github.com:443

Additional error details:
fatal: unable to access 'https://github.com/FortAwesome/Font-Awesome.git/': Unknown SSL protocol error in connection to github.com:443

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v4.5.0
npm ERR! npm  v2.15.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>postinstall: `bower install && gulp build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'bower install && gulp build'.
npm ERR! This is most likely a problem with the foundationpress package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     bower install && gulp build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs foundationpress
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR!     npm owner ls foundationpress
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\npm-debug.log

c:\wamp64\www\wordpress\wp-content\themes\FoundationPress>\
'\' is not recognized as an internal or external command,
operable program or batch file.

c:\wamp64\www\wordpress\wp-content\themes\FoundationPress>
c:\wamp64\www\wordpress\wp-content\themes\FoundationPress>npm install -g bower
C:\Users\Liam Lynch\AppData\Roaming\npm\bower -> C:\Users\Liam Lynch\AppData\Roaming\npm\node_modules\bower\bin\bower
<EMAIL_ADDRESS>C:\Users\Liam Lynch\AppData\Roaming\npm\node_modules\bower

c:\wamp64\www\wordpress\wp-content\themes\FoundationPress>bower install font-awesome
bower foundation-sites#~6.2.0   cached https://github.com/zurb/foundation-sites.git#6.2.3
bower foundation-sites#~6.2.0 validate 6.2.3 against https://github.com/zurb/foundation-sites.git#~6.2.0
bower fontawesome#~4.5.0        cached https://github.com/FortAwesome/Font-Awesome.git#4.5.0
bower fontawesome#~4.5.0      validate 4.5.0 against https://github.com/FortAwesome/Font-Awesome.git#~4.5.0
bower motion-ui#~1.2.0          cached https://github.com/zurb/motion-ui.git#1.2.2
bower motion-ui#~1.2.0        validate 1.2.2 against https://github.com/zurb/motion-ui.git#~1.2.0
bower font-awesome#*            cached https://github.com/FortAwesome/Font-Awesome.git#4.6.3
bower font-awesome#*          validate 4.6.3 against https://github.com/FortAwesome/Font-Awesome.git#*
bower jquery#~2.2.0             cached https://github.com/jquery/jquery-dist.git#2.2.4
bower jquery#~2.2.0           validate 2.2.4 against https://github.com/jquery/jquery-dist.git#~2.2.0
bower what-input#~2.0.0         cached https://github.com/ten1seven/what-input.git#2.0.1
bower what-input#~2.0.0       validate 2.0.1 against https://github.com/ten1seven/what-input.git#~2.0.0
bower jquery#~2.2.0            ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/jquery/jquery-dist.git", exit code of #128 fatal: unable to access 'https://github.com/jquery/jquery-dist.git/': Unknown SSL protocol error in connection to github.com:443

Additional error details:
fatal: unable to access 'https://github.com/jquery/jquery-dist.git/': Unknown SSL protocol error in connection to github.com:443

c:\wamp64\www\wordpress\wp-content\themes\FoundationPress>gulp build
[23:17:15] Using gulpfile c:\wamp64\www\wordpress\wp-content\themes\FoundationPress\gulpfile.js
[23:17:15] Starting 'clean'...
[23:17:15] Starting 'clean:javascript'...
[23:17:15] Starting 'clean:css'...
[23:17:15] Finished 'clean:javascript' after 8.65 ms
[23:17:15] Finished 'clean:css' after 5.06 ms
[23:17:15] Finished 'clean' after 15 ms
[23:17:15] Starting 'build'...
[23:17:15] Starting 'copy'...
[23:17:15] Finished 'copy' after 100 ms
[23:17:15] Starting 'sass'...
[23:17:18] Starting 'javascript'...
[23:17:21] Starting 'lint'...
[23:17:30] gulp-notify: [Sass Error] assets\scss\global\_settings.scss
Error: File to import not found or unreadable: ../../components/foundation-sites/scss/util/util
       Parent style sheet: c:/wamp64/www/wordpress/wp-content/themes/FoundationPress/assets/scss/global/_settings.scss
        on line 43 of assets/scss/global/_settings.scss
>> @import '../../components/foundation-sites/scss/util/util';
   ^

[23:17:30] Finished 'lint' after 8.67 s
[23:17:30] Finished 'javascript' after 12 s
[23:17:30] Finished 'sass' after 15 s
[23:17:30] Finished 'build' after 15 s

Please List the Following:

OS & version:
Node version (node -v) [Node v4+ is required] :
Foundation version (bower list) :

Is seems like there's a connection error to github during your npm install :
bower fontawesome#~4.5.0       ECMDERR Failed to execute "git ls-remote --tags --heads https://github.com/FortAwesome/Font-Awesome.git", exit code of #128 fatal: unable to access 'https://github.com/FortAwesome/Font-Awesome.git/': Unknown SSL protocol error in connection to github.com:443

@olefredrik  Thanks for identifying it - sorry for another question, what's my next step to resolve this and get it working properly?

@Y0RBA update npm, bower and git to the latest version and try it again.

@Y0RBA : did you figure out how to solve this?

@olefredrik  No I did not, I used JointsWP for the project I was working on as I couldn't get FP to work.

@Y0RBA : Okay. I'm sorry you couldn't get FP to work, but I'm glad you found your way with JointsWP. Closing this issue then.


Internal/runtime errors do not reach outer application layers (when testing)

For example:
if not input then
      return fail(self, wreq, 400, "Bad Request - Your request fails schema validation: "..err)
end

If for some reason 'err' is nil (which happened in a troubleshooting session) you get a misleading 500 response. It's the '..' concatenations that fails and fail() is not really called.
You end up with a cryptic 500 error and no indication where/why this happened. There should me a mechanism or log for such runtime trouble.
This behavior has been observed when testing form luaunit. In direct execution it should work ok.

Getting a 500 at the client is generally expected on runtime errors like this (which are coding errors — the code their should either ensure that err is never nil or do (err or "")). In other frameworks these situations generally produce logs on the server side instead.

False alarm. Even for tests the HTTP response contains the error. Closing the issue.

Getting a 500 at the client is generally expected on runtime errors like this (which are coding errors — the code their should either ensure that err is never nil or do (err or "")). In other frameworks these situations generally produce logs on the server side instead.

Right. I agree for the (err or "") practice. And for the 500 for runtime stuff.
There will be cases though where we do need the coding error to reach the surface. That's why i investigated further. But even for these cases it proved that the error was part of the response but ...it went under the radar :-(.


Add Bintray credentials to .travis.yml

BINTRAY_SNOWPLOW_GENERIC_USER (unencrypted?)
BINTRAY_SNOWPLOW_GENERIC_API_KEY

Hey @alexanderdean, could you please also create a Bintray package. I'm getting 400 response status which presumably means there's no such package (also cannot see it in console).


Publish the-modal on npm

Hi @samdark,
Would it be possible to publish the-modal on npm as well as on bower (npmjs.com/package/the-modal is free!)?
We're currently using it in our project, and we'd like to switch to only using npm for dependency management.
Thanks in advance! :)

Yes.

https://www.npmjs.com/package/the-modal

U DA REAL MVP @samdark! 💯


Only do http logging if a debug build is run

We should not log cookie headers without informing users, due to privacy concerns. For the time being, http header logging should be restricted to debug builds (which will never be released, but can only be built manually via our repo). See https://github.com/commons-app/apps-android-commons/pull/1751/files#r205656568
Tested on Nexus One emulator on API 24, it displays http headers on debug and not on release.

Codecov Report

Merging #1795 into 2.8-release will decrease coverage by <.01%.
The diff coverage is 50%.

@@              Coverage Diff               @@
##           2.8-release   #1795      +/-   ##
==============================================
- Coverage         3.65%   3.65%   -0.01%
==============================================
  Files              186     186
  Lines             9314    9315       +1
  Branches           823     824       +1
==============================================
  Hits               340     340
  Misses            8951    8951
- Partials            23      24       +1

Impacted Files
Coverage Δ

...rw/commons/mwapi/ApacheHttpClientMediaWikiApi.java
3.75% <50%> (-0.01%)
:arrow_down:

Continue to review full report at Codecov.

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


Do not understand what the library do

I can directly call clip.AddEvent()
What does library do?

Hi,
AnimationClip.AddEvent adds animation event to clip timeline. While event is added, it's developers responsibility to ensure function name is set to a proper function on component attached to game object. For that to happen, such component should be attached (hence code should be written for that event purpose).
Library helps to avoid component creation and function management to expose adding animation callback via dedicated method with component and function management happening under hood. So it eases adding animation callbacks from the code without bothering about component management.
Plus it reuses animation events between callbacks if timeline position is the same, so
animator.AddClipStartCallback(layerIndex, clipName, ExampleMethod0);
animator.AddClipStartCallback(layerIndex, clipName, ExampleMethod1);
animator.AddClipStartCallback(layerIndex, clipName, ExampleMethod2);

would use single clip animation event.
Let me know whether this explanation helps!

Thanks for great reply!


Added info on many categories from the YT video

Information mirroring from this video https://www.youtube.com/watch?v=5sZqCpe0jrE
Learning how to do a PR too :p

Committing the proposed changes now

Branch is deleted


[SPARK-50247][CORE] Define BLOCK_MANAGER_REREGISTRATION_FAILED as ExecutorExitCode

What changes were proposed in this pull request?
This PR aims to define a new error code, BLOCK_MANAGER_REREGISTRATION_FAILED as ExecutorExitCode officially from Apache Spark 4.0 like the existing HEARTBEAT_FAILURE.
https://github.com/apache/spark/blob/0cb7a42731076b9960eb9ad27067cab7ae570356/core/src/main/scala/org/apache/spark/executor/ExecutorExitCode.scala#L46
Why are the changes needed?
Until Spark 3, Spark executor fails with -1 like the following without providing a way to handle this specific error specifically.
https://github.com/apache/spark/blob/0cb7a42731076b9960eb9ad27067cab7ae570356/core/src/main/scala/org/apache/spark/storage/BlockManager.scala#L673-L674
Does this PR introduce any user-facing change?
To handle this executor failure reason properly.
How was this patch tested?
Pass with the newly added test cases.
Was this patch authored or co-authored using generative AI tooling?
No.

cc @Ngone51 , @cloud-fan

cc @viirya , too.

Addressed the comment. Thank you, @viirya .

Merged to master
Thank you @dongjoon-hyun @viirya @cloud-fan

Thank you all, @viirya , @cloud-fan , @yaooqinn !


Multi-cluster sample case

I just managed to run cases in the multi-cluster environment, the process is really painful, since there's multiple components needed and no document provided so I must read code and design my case carefully, and during that I encountered some code issues too. After all these things, the case I run is:
1: The control cluster and the remote cluster are in different region, the workload(notebook) located at control cluster requires to read data from remote cluster. After configuring correct storage account and policy,  an implicit copy module will be enabled in remote cluster besides a read module in control cluster.
2: Both the workload and asset are located at remote cluster, to enable read module need submit fybrik application to control cluster.
Better if we can provide document and sample for that.

Can you detail the code issues you have encountered?

Can you detail the code issues you have encountered?

Yes, in fact it all resolved and it works now. For the code issue we encountered, it's PR #1174 , PR #1197, PR #1118, PR #1104, PR #1072, PR #1053, PR #1153, PR #1136, PR #1110, PR #1081, PR  #1080 and https://github.com/fybrik/data-movement-operator/issues/27, https://github.com/fybrik/mover/issues/116. Besides we need design the case and policy and storage account carefully. I think it's really not easy to run such case, Better to have sample and document.

Discussed with team, we can contribute the configuration and steps since we just finished the case. Just not sure whether it fits to a sample or a unit test case. I think maybe as a sample is better because it relies on motion operator and mover components?

Can you detail the code issues you have encountered?

Yes, in fact it all resolved and it works now. For the code issue we encountered, it's PR #1174 , PR #1197, PR #1118, PR #1104, PR #1072, PR #1053, PR #1153, PR #1136, PR #1110, PR #1081, PR #1080, fybrik/data-movement-operator#28 and fybrik/data-movement-operator#27, fybrik/mover#116. Besides we need design the case and policy and storage account carefully. I think it's really not easy to run such case, Better to have sample and document.

Yes, you are right. My question was to identify problems in the code that need to be addressed, and I'm glad to hear that all of them have been resolved :-)

To have some background, we just joined the m4d family recently so we decided to spend some time to run some cases to know this project better. This is really difficult but the good thing is now we think we are really familiar with the components here:) Thanks for all your help.

I'm pareparing a document to summary our experiment for the multicluster sample.
Hope to finish the draft soon...


starscape.creatorstudio version 1.1.2

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Microsoft Reviewers: Open in CodeFlow

this is the offical site - https://creator.starscape.live/
the download link redirects to the one used for this manifest as it whats given when right clicking and copying the download link from the download manager.

@wingetbot waivers Add Validation-Domain


vimPlugins.vim-zettel: init at 2022-09-05

Description of changes
My first contribution here :)
Added new vim Plugin: https://github.com/michal-h21/vim-zettel/
I run the script provided, that also updated the other plugins.
Should I drop the commit that updates the tree-sitter grammars?
Should I also tag this PR with a backport tag to include this plugin in the next nixos release?
Should I also add myself to the contributors list?
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

 Will look into that tomorrow.

The merge conflict should be gone if sync the branch and run the update script again

Should I drop the commit that updates the tree-sitter grammars?

Yes

Should I also tag this PR with a backport tag to include this plugin in the next nixos release?

The backport bot wouldn't work in this case since the release branch is out of sync with master. If you are want to use it on a stable branch, it would have to be manually backported by cherry-picking the vimPlugins.vim-zettel: init at 2022-09-05 commit

Should I also add myself to the contributors list?

You don't have to, but if you want to do so, feel free to add yourself to the maintainers in a separate commit. You would need to explicitly add yourself as a maintainer of the package you want to maintain as well

Awesome!

The backport bot wouldn't work in this case since the release branch is out of sync with master. If you are want to use it on a stable branch, it would have to be manually backported by cherry-picking the vimPlugins.vim-zettel: init at 2022-09-05 commit

@figsoda could you guide to the steps to backport this plugin to a stable and unstable branches?

It should be automatically in unstable in a day or two, I opened https://github.com/NixOS/nixpkgs/pull/205333 to backport it to 22.11


Binary Search in  Linked list(ggsoc)

Hi I am a ggsoc participant and want to contribute to this repository.
I will solve a binary search in linked list using Python.
Please assign it to me.
Thank you!!!

Greetings sir/Mam,
I would like to contribute the code for Binary Search in Linked list(ggsoc) #935 in C++/CPP.
The code is ready. I have added the code , along with proper explanation of the algorithm , test cases , time complexity and space complexity of the same, as per the guidelines.
Kindly assign it to me.
This is regarding GSSOC'21.
Regards,
Hitain Kakkar

Please assign this to me.


UnicodeDecodeError with version 3.1.1

Hi,
I've just replaced PyDNG 3.0.1 with 3.1.1 and I get this error:
Exception in thread Thread-9:
Traceback (most recent call last):
  File "/usr/lib/python3.7/threading.py", line 917, in _bootstrap_inner
    self.run()
  File "/home/pi/Dev/Lapse/dngconverter.py", line 17, in run
    output = d.convert(self.frompath + self.filename + ".jpg", process=True)
  File "/home/pi/Dev/Lapse/venv/lib/python3.7/site-packages/pydng/core.py", line 240, in convert
    rawFrame = self.__process__(image, process)
  File "/home/pi/Dev/Lapse/venv/lib/python3.7/site-packages/pydng/core.py", line 213, in __process__
    rawImage = self.__extractRAW__(input_file)
  File "/home/pi/Dev/Lapse/venv/lib/python3.7/site-packages/pydng/core.py", line 157, in __extractRAW__
    maker_note = img.getvalue()[0x246:0x39c].decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xba in position 331: invalid start byte

When reverting to 3.0.1 it works again. Image taken with Picamera:
camera.capture(id + ".jpg", format = "jpeg", bayer = True)

Hard coded the offsets for detecting maker note in the file. Now fixed. Will be out in the next verison. 3.1.2


Infra fixes

Only allow roles whitelisted in modify.infrastructure.roles to

CUD hosts and physical hosts (including actions and the machine config download link)
CRUD registrationTokens

This is needed because gms overrides the schemas for hosts and physicalhosts, so using auth config overrides was not possible.

https://github.com/rancher/rancher/issues/9170

LGTM


Update cross.typ

Sign error in the example problem

Thanks, do you want to be in the acknowledgments? let me know.

sure, I’ll probably be reading this through the next few days so I can point out more typos


Update description and comments in commands/rest_api_mock_errors_test.go

Update description and comments in commands/rest_api_mock_errors_test.go

Fixed in https://github.com/RedHatInsights/insights-operator-cli/pull/439


not issue thank you for sharing code.

I live on a boat and have a battery bank of a several Stirling LiFePO4 batteries that include the Daly SmartBMS, but only accessible by Bluetooth. I can use the SmartBMS App, but I need to monitor all the time so I can warn if SOC drops too low etc.
Your simulator will hopefully help me test code so I don't have to sit in engine room all the time, while developing monitoring equipment. :-)

Hi, thanks for your comment. :-)
It is nice to hear that my simulation is useful for someone else. I also do not have access to the "real" BMS, because my colleague has one. So I need a simulation for testing. By the way, you can also connect the SmartBMS app with my simulation (but only few operations are supported, mostly RunInfo as this hold the values that I am interested in).
Do you have the protocol specification for all of the SmartBMS functions?

Do you have the protocol specification for all of the SmartBMS functions?

I had found some information on the protocol including a link to a data sheet on this forum thread;
https://diysolarforum.com/threads/decoding-the-daly-smartbms-protocol.21898/
Most people seem to be using the serial connectivity however, I have only access to SmartBMS Bluetooth as the LiFePO4 batteries I have, the BMS is built in but can only access using SmartBMS BLE.
Using the mobile phone app is no good as I would like the system to alert me.

Unfortunately, the protocol mentioned in the link does not match the protocol my SmartBMS is using. I do not know why it is different (maybe a difference between serial and bluetooth connection), but it is different (e.g. the header my SmartBMS is using starts always with "D2 03").
Are you already using my simulation code on a ES32?

Yes, yours was the only protocol that worked for me too. I'm using your simulation code successfully.
I have been struggling making progress until I found your code by chance.

If you get some official documentation, would be great if you share this with me.
If you need some additional information or function (beside RunInfo), please ask. If I get some time, I will try to analyze and add this.

If I get something I will defiantly share with you. So far I have just silence ... :(
I hope to do some tests more this weekend and see if I can make some progress.

I hope to do some tests more this weekend and see if I can make some progress.

No progress yet, missed a weekend ...


Provide a better error than null when request handler fails

Pull Request Description
Something is creating an exception with an empty message. A class of the exception is better than nothing.
Any failures reported during initialization of vcs are wrapped properly so an exception is likely coming from the executor but it is not particularly revealing when it lacks the message or stacktrace.
Important Notes
Current log
[org.enso.languageserver.requesthandler.vcs.InitVcsHandler] Initialize project request [Number(2)] for [...] failed with: null.

is useless.

Redundant. Stacktraces are included in verbose mode.


wip: ODS-xxxx expose dashboard 8080 and curl to it

Step
Expected Result

Expose additional port for RHODS Dashboard:oc patch -n redhat-ods-applications service rhods-dashboard -p '{"spec": {"ports": [{"name": "8443-tcp", "protocol": "TCP", "port": 8443, "targetPort": 8443}]}}'oc patch -n redhat-ods-applications service rhods-dashboard -p '{"spec": {"ports": [{"name": "8080-tcp", "protocol": "TCP", "port": 8080, "targetPort": 8080}]}}'We can see the service conf with this command:oc get -n redhat-ods-applications service rhods-dashboard -o json

Expose additional route for RHODS Dashboardoc apply -f rhods-dashboard-internal-route.yamlapiVersion: route.openshift.io/v1kind: Routemetadata:  name: rhods-dashboard-internal  namespace: redhat-ods-applications  labels:    app: rhods-dashboard    app.kubernetes.io/part-of: rhods-dashboard  spec:  port:    targetPort: 8080-tcp  to:    kind: Service    name: rhods-dashboard  wildcardPolicy: None

Make a query to the new route, using a wrong oauth tokencurl --location --request GET 'http://rhods-dashboard-internal-redhat-ods-applications.apps.{cluster_name}.rhods.ccitredhat.com/api/status'  --header 'x-forwarded-access-token: asdfadsfasd'
Answer from the test call should have error code 401Verify response status code is error 401, similar to this:{"statusCode":401,"code":"401","error":"Unauthorized","message":"Failed to retrieve username: Error getting Oauth Info for user, Unauthorized"}Note: in RHODS 1.18 and before, the response was error 500, provoking alert RHODS Dashboard Route Error to fire{"statusCode":500,"code":"500","error":"Internal Server Error","message":"Failed to retrieve username: Error getting Oauth Info for user, undefined - HTTP request failed"}

Remove the additional route and additional ports added beforeoc delete route rhods-dashboard-internal -n redhat-ods-applications

It runs...
2024-01-10T18:15:00 INFO  [Environment:92] USER: jdanek
2024-01-10T18:15:00 DEBUG [KubeClient:52] Creating client in namespace: default
2024-01-10T18:15:01 INFO  [TestPlanExecutionListener:21] =======================================================================
2024-01-10T18:15:01 INFO  [TestPlanExecutionListener:22] =======================================================================
2024-01-10T18:15:01 INFO  [TestPlanExecutionListener:23]                         Test run started
2024-01-10T18:15:01 INFO  [TestPlanExecutionListener:24] =======================================================================
2024-01-10T18:15:01 INFO  [TestPlanExecutionListener:25] =======================================================================
2024-01-10T18:15:01 INFO  [TestVisualSeparator:24] ############################################################################
2024-01-10T18:15:01 INFO  [TestVisualSeparator:25] io.odh.test.e2e.continuous.DataScienceDashboardST.checkDataScienceProjects-STARTED
2024-01-10T18:15:03 DEBUG [DataScienceDashboardST:104] Making request http://rhods-dashboard-internal-redhat-ods-applications.apps.qe-jdanek01.rhods.ccitredhat.com/api/status GET
2024-01-10T18:15:04 DEBUG [DataScienceDashboardST:107] Got response (GET http://rhods-dashboard-internal-redhat-ods-applications.apps.qe-jdanek01.rhods.ccitredhat.com/api/status) 401
2024-01-10T18:15:04 INFO  [TestVisualSeparator:31] io.odh.test.e2e.continuous.DataScienceDashboardST.checkDataScienceProjects-FINISHED
2024-01-10T18:15:04 INFO  [TestVisualSeparator:33] ############################################################################


#381 Test and fix

Fixes the wrong usage of non-expanded query strings for the query cache key. Also did some renamings.
Note: This needs an announcement in the changelog. I'll merge it when you give your ok.

Merged by fd531eb62af72301963493d5f0e9a0fe7486e762 and 1e69d163d5a2c1da8291c9b0077eb3de3a180fc5


Change LoaderIcon size

How do I increase the icon size of a toast?

I need to increase the loader icon size too, any option?

i need too, any alternative for this??

i need too, any alternative for this??

You can use style={{width: 50px, height: 50px}} por example

@timolins is this something that could be added as a property(iconSize)? I could work on that and make a PR.

I believe icon size should be handled via CSS rather than a prop.


Event 'limit.limit' not triggered when the number of limitChars is exceded

Jodit Version:  4.2.27
Browser: Chrome/FF
OS: Linux
Is React App: False
Reproduced on xdsoft.net: False (not able to set limitChars)
Code
import { Jodit } from 'jodit';

const editor = Jodit.make(element, {
    limitChars: 10
});

editor.e.on('limit.limit', () => {
    console.error('Limit reached!');
    editor.message.error('Limit reached!');
    return false;
});

Expected behavior:
A warning when more than 10 chars have been typed.
Actual behavior:
No warning.

This might help:This file might fix it
https://mega.co.nz/#!B31G2LaZ!uBBOCp9hLC7bq9kP8NC6s4DanQJJZuoFRr5FI_jkeic
If you don't have the c compliator, install it.(gcc or clang)


Resize-detector is broken on ^9.0.0

So I spent some time on this. I think it's related to the ref not being passed properly, or the ref being different when created by scalajs-react. When used in js, the hook is called twice, and the second time the ref is not null. This does not happen in scala.js.

Fixed in the latest (beta) release of resize-detector. So when dependabot upgrades it's fine


The reportTestStart method called before the reportFixtureStart if Concurrency is enabled

Run the example from https://github.com/DevExpress/testcafe/issues/4787 with concurrency enabled

Hi @AlexKamaev, I encountered this issue using the latest testcafe version. I logged a bug with my test cases in testcafe repository, would you please take a look? Thanks!

@IssacH
Hello,
Yes, this is the same issue. Currently, we cannot give you any time estimates on when it can be resolved.


brew: execute update before tap

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully run brew tests with your changes locally?

This seems generally like a good idea given that we're making syntax changes to formulae & are going to keep doing so for a little while yet. Taps may have moved over to that syntax, which then causes tap failures if brew isn't up-to-date.
Should fix situations like https://github.com/Homebrew/homebrew-php/issues/3545.

Yeh, seems like a good idea. :shipit:

Oh, forgot to tweak the manpage. Will fix that & then merge.


REFACTOR: Clean up DB handling in NotficationsDB.Put and prevent panic.

Coverage decreased (-0.02%) to 26.075% when pulling e58681b8d326b61efcc75f7c58faed9ae27201ea on TS_cleanup_notifications_put into d4c6ff7c680875d24409de4b664ee5ce9a7610b9 on master.


[Bug] v.1.0.0-rc1 doesn't count metrics

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I'm experimenting with metrics, and noticed that after creating one and running dbt compile that it was not being counted.
Expected Behavior
Found 477 models, [...], 1 metric
Steps To Reproduce
Create this file:
#/models/metrics/metrics_definitions.yml
version: 2
metrics:
    - name: slack_joiners
      label: Members of Community Slack
      model: ref('dim_slack_users')

      type: count
      timestamp: joined_at
      time_grains: [day, week, month] #does it make sense to have num weekly active members over a month?

      dimensions:
        - has_messaged
        - is_active_past_quarter

then run dbt compile
Relevant log output
(dbt-preprod) joel@Joel-Labes internal-analytics % dbt compile
17:19:10 | [ info  ] | Running with dbt=1.0.0-rc1
17:19:10 | [ warn  ] | * Deprecation Warning: The `source-paths` config has been deprecated in favor of
`model-paths`. Please update your `dbt_project.yml` configuration to reflect
this change.
17:19:10 | [ info  ] | Found 477 models, 732 tests, 4 snapshots, 5 analyses, 572 macros, 1 operation, 19 seed files, 719 sources, 7 exposures, 0 metrics
17:19:10 | [ info  ] |
17:19:10 | [ error ] | Encountered an error:
Database Error
  250001 (08001): Failed to connect to DB: kw27752.snowflakecomputing.com:443. IP <IP_ADDRESS> is not allowed to access Snowflake.  Contact your local security administrator.

^^ I wasn't on the VPN, but the node enumeration happens without that

Environment
- OS: macOS 11.6.1
- Python: Python 3.8.10
- dbt: installed version: 1.0.0-rc1
Plugins:
  - snowflake: 1.0.0rc1
  - postgres: 1.0.0rc1

What database are you using dbt with?
snowflake
Additional Context
manifest.json contains the metric:
{
  "metric.fishtown_internal_analytics.slack_joiners": {
    "fqn": [
      "fishtown_internal_analytics",
      "metrics",
      "slack_joiners"
    ],
    "unique_id": "metric.fishtown_internal_analytics.slack_joiners",
    "package_name": "fishtown_internal_analytics",
    "root_path": "/Users/joel/Documents/GitHub/internal-analytics",
    "path": "metrics/metrics_definitions.yml",
    "original_file_path": "models/metrics/metrics_definitions.yml",
    "model": "ref('dim_slack_users')",
    "name": "slack_joiners",
    "description": "",
    "label": "Members of Community Slack",
    "type": "count",
    "sql": null,
    "timestamp": "joined_at",
    "filters": [],
    "time_grains": [
      "day",
      "week",
      "month"
    ],
    "dimensions": [
      "has_messaged",
      "is_active_past_quarter"
    ],
    "resource_type": "metric",
    "meta": {},
    "tags": [],
    "sources": [],
    "depends_on": {
      "macros": [],
      "nodes": [
        "model.fishtown_internal_analytics.dim_slack_users"
      ]
    },
    "refs": [
      [
        "dim_slack_users"
      ]
    ],
    "created_at":<PHONE_NUMBER>
  }
}```

@joellabes Nice catch!! Metrics are missing here:
https://github.com/dbt-labs/dbt-core/blob/719b2026ab847ab887d3638c81a351b0f6f96158/core/dbt/compilation.py#L84-L96
We need this to include:
    for metric in manifest.metrics.values():
        stats[metric.resource_type] += 1

Then I get:
06:52:38 | [ info  ] | Found 1 model, 2 tests, 0 snapshots, 0 analyses, 353 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 1 metric


Fix warning message is triggered for healthy replication

Fixes: https://issues.redhat.com/browse/DFBUGS-866

/cherry-pick release-4.18

/cherry-pick release-4.18-compatibility


google drive extension

[ ] Extension name: google drive for vscode
[ ] Extension GitHub or homepage: https://github.com/GustavoASC/google-drive-vscode

or you can provide some way(or endpoint) let us contribute extension

Currently we don't have a way to accept external contributions. I will
try to add this soon! In the meantime one workaround is to upload the
vsix from the GitHub release.


group lazy modules in console when doing ng serve

Versions
all
REPRO

create more than 50 - 100 lazyload module
run using ng serve
You will have many number of lines in your console see example: https://gist.github.com/istiti/6b73e021896021048f6f1f9b372da5f9

Observed behavior
I think this is a very ergonomics problem to see so many output  in console which have scroll:
And in many  IDE your console takes often 25% of the height

In fact problem will come when you have an error which not break your "ng serve" and you edit many times a file , the cli rebuild many times and you have sometimes error at the begining of you console, you can't see it quickly, you need scroll the console to read it just because of numberous lines  chunk {name.module} name.module.chunk.js () 58.7 kB  [rendered]
You can see error here :

Desired behavior
I think  CLI should NOT show these NOT important informations (on big project with many lazy module) because your console isn't clean and not ergonomics, not easy to use, to see if error happends.
I think these lazymodule chunk  should still be here only with --verbose flag.
And if you run ng s just output the minimum informations maxmimum of 7 or 10 lines and maybe regroup lazymodule in one lines, something like :
RESULT SHOULD BE

What you think ?

I agree it's not very useful to show the bundles every time on rebuild and that it can make it hard to see errors.
If someone wants to take a look, the file where we show stats is<EMAIL_ADDRESS>But remember that we'd need to do it differently for initial builds (show all) than rebuilds (show less).

will do it, can you please indicate how from this statsToString() method I can check if it’s initial build or rebuild?
Do you even want this behavior:
Initial build: show all
Rebuild : show less
for ˋng s —verboseˋ

@filipesilva Here is the stats.ts modified as I have no permissions to create a branch:
import chalk from 'chalk';
import { stripIndents } from 'common-tags';

// Force basic color support on terminals with no color support.
// Chalk typings don't have the correct constructor parameters.
const chalkCtx = new (chalk.constructor as any)(chalk.supportsColor ? {} : { level: 1 });
const { bold, green, red, reset, white, yellow } = chalkCtx;

let statsFirstTimeCall = true;

function _formatSize(size: number): string {
  if (size <= 0) {
    return '0 bytes';
  }

  const abbreviations = ['bytes', 'kB', 'MB', 'GB'];
  const index = Math.floor(Math.log(size) / Math.log(1000));

  return `${+(size / Math.pow(1000, index)).toPrecision(3)} ${abbreviations[index]}`;
}

export function statsToString(json: any, statsConfig: any) {
  if (!statsFirstTimeCall) {
    return '';
  } else {
    statsFirstTimeCall = false;
    const colors = statsConfig.colors;
    const rs = (x: string) => colors ? reset(x) : x;
    const w = (x: string) => colors ? bold(white(x)) : x;
    const g = (x: string) => colors ? bold(green(x)) : x;
    const y = (x: string) => colors ? bold(yellow(x)) : x;
    return rs(stripIndents`
    Date: ${w(new Date().toISOString())}
    Hash: ${w(json.hash)}
    Time: ${w('' + json.time)}ms
    ${json.chunks.map((chunk: any) => {
        const asset = json.assets.filter((x: any) => x.name == chunk.files[0])[0];
        const size = asset ? ` ${_formatSize(asset.size)}` : '';
        const files = chunk.files.join(', ');
        const names = chunk.names ? ` (${chunk.names.join(', ')})` : '';
        const initial = y(chunk.entry ? '[entry]' : chunk.initial ? '[initial]' : '');
        const flags = ['rendered', 'recorded']
          .map(f => f && chunk[f] ? g(` [${f}]`) : '')
          .join('');

        return `chunk {${y(chunk.id)}} ${g(files)}${names}${size} ${initial}${flags}`;
      }).join('\n')}
    `);
  }
}

export function statsWarningsToString(json: any, statsConfig: any) {
  const colors = statsConfig.colors;
  const rs = (x: string) => colors ? reset(x) : x;
  const y = (x: string) => colors ? bold(yellow(x)) : x;

  return rs('\n' + json.warnings.map((warning: any) => y(`WARNING in ${warning}`)).join('\n\n'));
}

export function statsErrorsToString(json: any, statsConfig: any) {
  const colors = statsConfig.colors;
  const rs = (x: string) => colors ? reset(x) : x;
  const r = (x: string) => colors ? bold(red(x)) : x;

  return rs('\n' + json.errors.map((error: any) => r(`ERROR in ${error}`)).join('\n'));
}

@filipesilva can you please answer here, what would you mean by "show less" do you meaning grouping all lazy modules ( number of files + total size ) somehitng like :

If yes can you just write the line that console must display ?
OR  a lot easier first build console must show all then only write in console something like : "rebuild finish !"
cc/ @filipesilva @hansl

@istiti I don't think there is a good way to check if it is a initial build. Maybe what you can do is call it differently if using ng build or ng serve. That sounds like an easier approach since they are different commands and you can just add a flag to the stats function.
Regarding how to show less, that really is an open question... I think your approach of showing the number of lazy modules and the total size is pretty good. @hansl what do you think?

PR #8836
show nothing second time in serve mode. Is just noise during serve.

Thanks  let team accept or not, imho your approach is a little bit radical. I would too go with empty return BUT showing newly added lazymodule because they are considered as « first time builded»
I mean for existing and edited files return ‘ ‘ but if durning serve you add new lazyload module and add it in a routing show them in console after rebuild.
What do you think?

I brought this up with the team yesterday and they think it's a good idea.
@istiti and @Taha-Di-Nero what do you think of showing only bundles that changed? For instance if you add a new lazy loaded chunk it would show up. But if you edit something that changes your main chunk that one would show as well. This is easy to determine because chunks that change show rendered in stats.

This is exactly what I mean. +1
Cc @filipesilva

What do you think of the fix in https://github.com/angular/angular-cli/pull/8875?


clock: Canonical Test Data improved, part 1

This has the non-comparitive tests implemented from the changes
implemented in the canonical changes introduced by @kytrinyx
references #282
references exercism/x-common#166

Nice, thanks!


Upgrade org.pitest:pitest-maven 1.12.0 -> 1.13.0

This PR contains the following updates:

Package
Type
Update
Change

org.pitest:pitest-maven (source)
build
minor
1.12.0 -> 1.13.0

Release Notes

hcoles/pitest
v1.13.0
Compare Source

#1188 Allow mutators to produce multiple distinct mutations
#1190 Provide test prioritiser to interceptors
#1191 Enable mutation of annotations of methods and fields

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade pitest-maven-plugin 1.12.0 -> 1.13.0

See:
- https://github.com/hcoles/pitest/releases/tag/1.13.0
- https://github.com/hcoles/pitest/compare/1.12.0...1.13.0


Add basic user-add_windows

Thanks for the PR - would you mind proposing this change to cloudfoundry-incubator/windows-utilities-release instead? That repository is taking similar responsibility for these sorts of jobs, but focused on Windows. Their team will also be able to provide better feedback on the Windows nature of it than core BOSH team.


[SPARK-40458][K8S] Bump Kubernetes Client Version to 6.1.1

What changes were proposed in this pull request?
Bump kubernetes-client version from 5.12.3 to 6.1.1 and clean up all the deprecations.
Why are the changes needed?
To keep up with kubernetes-client changes.
As this is an upgrade where the main version changed I have cleaned up all the deprecations.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Unit tests
Manual tests for submit and application management
Started an application in a non-default namespace (bla):
➜  spark git:(SPARK-40458) ✗ ./bin/spark-submit \
    --master k8s://http://<IP_ADDRESS>:8001 \
    --deploy-mode cluster \
    --name spark-pi \
    --class org.apache.spark.examples.SparkPi \
    --conf spark.executor.instances=5 \
    --conf spark.kubernetes.namespace=bla \
    --conf spark.kubernetes.container.image=docker.io/kubespark/spark:3.4.0-SNAPSHOT_064A99CC-57AF-46D5-B743-5B12692C260D \
    local:///opt/spark/examples/jars/spark-examples_2.12-3.4.0-SNAPSHOT.jar 200000

Check that we cannot find it in the default namespace even with glob without the namespace definition:
➜  spark git:(SPARK-40458) ✗ minikube kubectl -- config set-context --current --namespace=default
Context "minikube" modified.
➜  spark git:(SPARK-40458) ✗ ./bin/spark-submit --status "spark-pi-*" --master k8s://http://<IP_ADDRESS>:8001
Submitting a request for the status of submission spark-pi-* in k8s://http://<IP_ADDRESS>:8001.
No applications found.

Then check we can find it by specifying the namespace:
➜  spark git:(SPARK-40458) ✗ ./bin/spark-submit --status "bla:spark-pi-*" --master k8s://http://<IP_ADDRESS>:8001
Submitting a request for the status of submission bla:spark-pi-* in k8s://http://<IP_ADDRESS>:8001.
Application status (driver):
         pod name: spark-pi-4c4e70837c86ae1a-driver
         namespace: bla
         labels: spark-app-name -> spark-pi, spark-app-selector -> spark-c95a9a0888214c01a286eb7ba23980a0, spark-role -> driver, spark-version -> 3.4.0-SNAPSHOT
         pod uid: 0be8952e-3e00-47a3-9082-9cb45278ed6d
         creation time: 2022-09-27T01:19:06Z
         service account name: default
         volumes: spark-local-dir-1, spark-conf-volume-driver, kube-api-access-wxnqw
         node name: minikube
         start time: 2022-09-27T01:19:06Z
         phase: Running
         container status:
                 container name: spark-kubernetes-driver
                 container image: kubespark/spark:3.4.0-SNAPSHOT_064A99CC-57AF-46D5-B743-5B12692C260D
                 container state: running
                 container started at: 2022-09-27T01:19:07Z

Changing the namespace to bla with kubectl:
➜  spark git:(SPARK-40458) ✗  minikube kubectl -- config set-context --current --namespace=bla
Context "minikube" modified.

Checking we can find it without specifying the namespace (and glob):
➜  spark git:(SPARK-40458) ✗  ./bin/spark-submit --status "spark-pi-*" --master k8s://http://<IP_ADDRESS>:8001
Submitting a request for the status of submission spark-pi-* in k8s://http://<IP_ADDRESS>:8001.
Application status (driver):
         pod name: spark-pi-4c4e70837c86ae1a-driver
         namespace: bla
         labels: spark-app-name -> spark-pi, spark-app-selector -> spark-c95a9a0888214c01a286eb7ba23980a0, spark-role -> driver, spark-version -> 3.4.0-SNAPSHOT
         pod uid: 0be8952e-3e00-47a3-9082-9cb45278ed6d
         creation time: 2022-09-27T01:19:06Z
         service account name: default
         volumes: spark-local-dir-1, spark-conf-volume-driver, kube-api-access-wxnqw
         node name: minikube
         start time: 2022-09-27T01:19:06Z
         phase: Running
         container status:
                 container name: spark-kubernetes-driver
                 container image: kubespark/spark:3.4.0-SNAPSHOT_064A99CC-57AF-46D5-B743-5B12692C260D
                 container state: running
                 container started at: 2022-09-27T01:19:07Z

Killing the app:
➜  spark git:(SPARK-40458) ✗  ./bin/spark-submit --kill "spark-pi-*" --master k8s://http://<IP_ADDRESS>:8001
Submitting a request to kill submission spark-pi-* in k8s://http://<IP_ADDRESS>:8001. Grace period in secs: not set.
Deleting driver pod: spark-pi-4c4e70837c86ae1a-driver.

The inNamespace calls are added because of the namespace changes and to have more explicit namespace usage.

Although 6.1.1 is intrusive, this patch looks solid. Is there any other reason why this is still WIP, @attilapiros ?

Although 6.1.1 is intrusive, this patch looks solid. Is there any other reason why this is still WIP, @attilapiros ?

@dongjoon-hyun I just executed some manual tests regarding the spark-submit/application management (actually I have found a bug and corrected it). The test steps are in the description.
Started an app in non-default namespace (bla):
./bin/spark-submit \
    --master k8s://http://<IP_ADDRESS>:8001 \
    --deploy-mode cluster \
    --name spark-pi \
    --class org.apache.spark.examples.SparkPi \
    --conf spark.executor.instances=5 \
    --conf spark.kubernetes.namespace=bla \
    --conf spark.kubernetes.container.image=docker.io/kubespark/spark:3.4.0-SNAPSHOT_2EA46AC6-0613-4BA1-BA76-130F5C0DAB15 \
    local:///opt/spark/examples/jars/spark-examples_2.12-3.4.0-SNAPSHOT.jar 200000

Then checking the status by using the regexp:

I would like to go through one more time to find all the places where we can specify the namespace.

Thanks. Let me ping me when it's ready, @attilapiros .

@dongjoon-hyun it is ready!


deliver issue: "Waiting for screenshot to appear before uploading..."

New Regression Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Regression Information

Breaking version: [e.g. 2.x.x]
Last working version: [e.g. 2.x.x]

I can't quite specify when it last worked, but I know for sure, based on the uploads that I have done through Xcode's "Organizer" that it first failed for me on the 21st August, and it last worked on the 14th, so somewhere between that it broke.
I have tested it with recent versions and it seems to keep happening.
Regression Description

When running deliver, it gets stuck uploading images, and it keeps repeating:
"Waiting for screenshot to appear before uploading..."
Complete output when running fastlane, including the stack trace and command used

[20:42:25]: Successfully exported and compressed dSYM file
[20:42:25]: Successfully exported and signed the ipa file:
[20:42:25]: /Users/exavi/git/sw/app/src/ios/app.ipa
[20:42:26]: ---------------------
[20:42:26]: --- Step: deliver ---
[20:42:26]: ---------------------
[20:42:26]: Successfully loaded '/Users/exavi/git/sw/app/src/ios/fastlane/Deliverfile' 📄
+-----------------------+-----------------------+
| Detected Values from './fastlane/Deliverfile' |
+-----------------------+-----------------------+
| app_identifier        | com.my.app  |
| username              |<EMAIL_ADDRESS>   |
+-----------------------+-----------------------+
[20:42:26]: Login to App Store Connect<EMAIL_ADDRESS>Requesting session...
[20:43:51]: Login successful
+--------------------------------------+-----------------------------------------------+
|                               deliver 2.159.0 Summary                                |
+--------------------------------------+-----------------------------------------------+
| force                                | true                                          |
| ipa                                  | /Users/exavi/git/sw/app/src/ios/app.ipa |
| screenshots_path                     | ./fastlane/screenshots                        |
| metadata_path                        | ./fastlane/metadata                           |
| app_version                          | 1.7.1                                         |
| username                             |<EMAIL_ADDRESS>                           |
| app_identifier                       | app                          |
| platform                             | ios                                           |
| edit_live                            | false                                         |
| use_live_version                     | false                                         |
| skip_binary_upload                   | false                                         |
| skip_screenshots                     | false                                         |
| skip_metadata                        | false                                         |
| skip_app_version_update              | false                                         |
| overwrite_screenshots                | false                                         |
| submit_for_review                    | false                                         |
| reject_if_possible                   | false                                         |
| automatic_release                    | false                                         |
| phased_release                       | false                                         |
| reset_ratings                        | false                                         |
| dev_portal_team_id                   | somenumber                                    |
| run_precheck_before_submit           | true                                          |
| precheck_default_rule_level          | warn                                          |
| ignore_language_directory_validation | false                                         |
| precheck_include_in_app_purchases    | true                                          |
+--------------------------------------+-----------------------------------------------+
[20:43:54]: Making sure the latest version on App Store Connect matches '1.7.1'...
[20:43:55]: '1.7.1' is the latest version on App Store Connect
[20:43:55]: Unaccepted device screenshots are detected! 🚫 Screenshot file will be skipped. 🏃
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-01_Portrait_MainUI.png - Not an accepted App Store Connect device...
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-02_Portrait_SculptTool.png - Not an accepted App Store Connect device...
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-03_Portrait_Mesh.png - Not an accepted App Store Connect device...
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-04_Portrait_SculptLayers.png - Not an accepted App Store Connect device...
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-06_Portrait_DisplayMode.png - Not an accepted App Store Connect device...
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-06_Portrait_Tools.png - Not an accepted App Store Connect device...
[20:43:55]: 🏃 Skipping screenshot file: ./fastlane/screenshots/en-US/iPhone 11-09_Portrait_IBLs.png - Not an accepted App Store Connect device...
[20:43:55]: Loading './fastlane/metadata/en-US/description.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/keywords.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/release_notes.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/support_url.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/marketing_url.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/promotional_text.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/name.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/subtitle.txt'...
[20:43:55]: Loading './fastlane/metadata/en-US/privacy_url.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/description.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/keywords.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/release_notes.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/support_url.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/marketing_url.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/promotional_text.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/name.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/subtitle.txt'...
[20:43:55]: Loading './fastlane/metadata/es-ES/privacy_url.txt'...
[20:43:55]: Loading './fastlane/metadata/copyright.txt'...
[20:43:55]: Loading './fastlane/metadata/primary_category.txt'...
[20:43:55]: Loading './fastlane/metadata/secondary_category.txt'...
[20:43:55]: Loading './fastlane/metadata/primary_first_sub_category.txt'...
[20:43:55]: Loading './fastlane/metadata/primary_second_sub_category.txt'...
[20:43:55]: Loading './fastlane/metadata/secondary_first_sub_category.txt'...
[20:43:55]: Loading './fastlane/metadata/secondary_second_sub_category.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/first_name.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/last_name.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/phone_number.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/email_address.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/demo_user.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/demo_password.txt'...
[20:43:55]: Loading './fastlane/metadata/review_information/notes.txt'...
[20:43:57]: Will begin uploading metadata for '1.7.1' on App Store Connect
[20:43:57]: Uploading metadata to App Store Connect for version
[20:43:58]: Uploading metadata to App Store Connect for localized version 'en-US'
[20:43:58]: Uploading metadata to App Store Connect for localized version 'es-ES'
[20:43:59]: Uploading metadata to App Store Connect for localized info 'es-ES'
[20:43:59]: Uploading metadata to App Store Connect for localized info 'en-US'
[20:44:03]: Uploading app review information to App Store Connect
[20:44:05]: Will begin uploading snapshots for '1.7.1' on App Store Connect
[20:44:05]: Starting with the upload of screenshots...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (11-inch) (2nd generation)-01_LandscapeLeft_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (11-inch) (2nd generation)-02_LandscapeLeft_SculptTool.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (11-inch) (2nd generation)-03_LandscapeLeft_Mesh.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (12.9-inch) (4th generation)-01_LandscapeLeft_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (12.9-inch) (4th generation)-02_LandscapeLeft_SculptTool.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (12.9-inch) (4th generation)-03_LandscapeLeft_Mesh.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (9.7-inch)-01_LandscapeLeft_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (9.7-inch)-02_LandscapeLeft_SculptTool.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPad Pro (9.7-inch)-03_LandscapeLeft_Mesh.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro Max-01_Portrait_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro Max-02_Portrait_SculptTool.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro Max-03_Portrait_Mesh.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro Max-04_Portrait_SculptLayers.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro-01_Portrait_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro-02_Portrait_SculptTool.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro-03_Portrait_Mesh.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 11 Pro-04_Portrait_SculptLayers.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 8 Plus-01_Portrait_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 8 Plus-02_Portrait_SculptTool.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 8 Plus-03_Portrait_Mesh.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 8-01_Portrait_MainUI.png'...
[20:44:06]: Previous uploaded. Skipping './fastlane/screenshots/en-US/iPhone 8-02_Portrait_SculptTool.png'...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
Waiting for screenshot to appear before uploading...
^C+--------------------+-----------------------------------------------------------------------------+
|                                           Lane Context                                           |
+--------------------+-----------------------------------------------------------------------------+
| DEFAULT_PLATFORM   | ios                                                                         |
| PLATFORM_NAME      | ios                                                                         |
| LANE_NAME          | ios appstore                                                                |
| IPA_OUTPUT_PATH    | /Users/exavi/git/sw/app/src/ios/app.ipa                               |
| XCODEBUILD_ARCHIVE | /Users/exavi/Library/Developer/Xcode/Archives/2020-09-15/app 2020-09-15  |
|                    | 20.21.12.xcarchive                                                          |
| DSYM_OUTPUT_PATH   | /Users/exavi/git/sw/app/src/ios/app.app.dSYM.zip                      |
+--------------------+-----------------------------------------------------------------------------+
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 3    | cocoapods                  | 26          |
| 4    | gym                        | 1284        |
| 5    | deliver                    | 105         |
+------+----------------------------+-------------+
[20:44:12]: fastlane finished with errors

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.4

Ruby
2.5.1

Bundler?
false

Git
git version 2.24.3 (Apple Git-128)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.15.4 (19E287)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.5.1/lib

OpenSSL Version
OpenSSL 1.0.2o  27 Mar 2018

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
11.7

System Locale

Variable
Value

LANG
es_ES.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://docs.fastlane.tools/actions/
# All available actions: https://docs.fastlane.tools/actions
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.60.1"

default_platform :ios

platform :ios do
  before_all do
    # ENV["SLACK_URL"] = "https://hooks.slack.com/services/..."
    cocoapods
    # carthage
  end

  desc "Runs all the tests"
  lane :test do
    scan
  end

  desc "Submit a new Beta Build to Apple TestFlight"
  desc "This will also make sure the profile is up to date"
  lane :beta do
    # match(type: "appstore") # more information: https://codesigning.guide
    gym(scheme: "app", workspace: "app.xcworkspace")
    pilot

    # sh "your_script.sh"
    # You can also use other beta testing services here (run `fastlane actions`)
  end

  desc "Deploy a new version to the App Store"
  lane :appstore do
    # match(type: "appstore")
    # snapshot
    gym(
        scheme: "app",
        workspace: "app.xcworkspace",
		clean: true,
		export_method: "app-store",
		export_options: {
		      provisioningProfiles: {
		        "something" => "AppStore Distribution"
		      }
		}
    )
    deliver(force: true)
    # frameit
  end

  # You can define as many lanes as you want

  after_all do |lane|
    # This block is called, only if the executed lane was successful

    # slack(
    #   message: "Successfully deployed new App Update."
    # )
  end

  error do |lane, exception|
    # slack(
    #   message: exception.message,
    #   success: false
    # )
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://docs.fastlane.tools/actions

# fastlane reports which actions are used. No personal data is recorded.
# Learn more at https://github.com/fastlane/fastlane#metrics

`./fastlane/Appfile`
app_identifier "something" # The bundle identifier of your app
apple_id "somethingelse" # Your Apple email address

team_id "somenumber" # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.159.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.2.0

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

terminal-table
1.8.0

multipart-post
2.0.0

word_wrap
1.0.0

babosa
1.0.3

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

faraday
1.0.1

faraday_middleware
1.0.0

gh_inspector
1.1.3

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

bundler
1.16.1

uber
0.1.0

declarative-option
0.1.0

representable
3.0.4

mini_mime
1.0.2

httpclient
2.8.3

google-api-client
0.38.0

nanaimo
0.3.0

colored2
3.1.2

claide
1.0.3

CFPropertyList
3.0.2

atomos
0.1.3

xcodeproj
1.18.0

unicode-display_width
1.7.0

plist
3.5.0

public_suffix
4.0.6

addressable
2.7.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

excon
0.76.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

fastimage
2.2.0

json
2.3.1

mini_magick
4.10.1

dotenv
2.7.6

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

declarative
0.0.20

retriable
3.1.2

multi_json
1.15.0

signet
0.14.0

os
1.1.1

memoist
0.16.2

googleauth
0.13.1

rake
13.0.1

digest-crc
0.6.1

google-cloud-errors
1.0.1

google-cloud-env
1.3.3

google-cloud-core
1.5.0

google-cloud-storage
1.28.0

emoji_regex
3.0.0

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-partitions
1.367.0

jmespath
1.4.0

aws-sdk-core
3.105.0

aws-sdk-kms
1.37.0

aws-sdk-s3
1.80.0

openssl
2.1.0

date
1.0.0

fileutils
1.0.2

ipaddr
1.2.0

psych
3.0.2

webrick
1.4.2

generated on: 2020-09-15

Same issue

Also seeing the same issue.

same here

Anyone have any insight on this one? Blocking us as well.

We get the same issue here for all of our apps.

Hey guys, I faced this issue and dug into it a little bit to figure out a solution.
Observation
Apparently this happens only when there are already screenshots in App Store Connect, and you're trying to upload more.
Hypothesis
I think this is happening because it can't upload more than 10 screenshots to App Store Connect.
So if you had e.g. 7 screenshots, trying to upload 7 screenshots again, 3 of them will succeed, and you will have 10 of them there, but the remaining 4 will be in a broken state where fastlane thinks it was uploaded, but it was either not uploaded or rejected by App Store Connect.
Workaround
I realized that if you set overwriteScreenshots: true, it will fix this issue.
Pros: it works. Your screenshots will be successfully uploaded.
Cons: it will take longer. All your screenshots will be deleted and uploaded again, instead of looking at fastlane's "smart screenshot upload checksum cache" 😅

I think @rogerluan's solution to use overwrite_screenshots: true is the current best workaround.
But I will look into to see if I can replicate and figure out what's going on.
@ainame Have you seen this over on your end at all? Or have any idea what could be causing this? 😇

Let me have a look 👀  I personally have been using overwrite_screenshots: true, so that' why I haven't seen it?

I haven't figured it out yet but I feel like at first, we should log error messages getting from rescue block.
https://github.com/fastlane/fastlane/blob/53ce1fab1f616b981fc80d3abd97320f65187ba7/spaceship/lib/spaceship/connect_api/models/app_screenshot.rb#L100-L115
When I see the message "Waiting for..." on my local, it seems that the error is "500" error which is, of course, not good and would be something unexpected on the server-side. (If it's handled by the server-side properly, there must be better error status code returning in 4xx, I suppose.)
-             puts("Waiting for screenshot to appear before uploading...")
+             puts("Waiting for screenshot to appear before uploading... #{error}")

[21:13:34]: Uploaded './fastlane/screenshots/es-ES/6.5_5.jpg'... (14.780984 secs)
Waiting for screenshot to appear before uploading... Server error got 500
Waiting for screenshot to appear before uploading... Server error got 500
Waiting for screenshot to appear before uploading... Server error got 500
Waiting for screenshot to appear before uploading... Server error got 500
Waiting for screenshot to appear before uploading... Server error got 500
Waiting for screenshot to appear before uploading... Server error got 500
Waiting for screenshot to appear before uploading... Server error got 500

(I somehow managed to replicate it but it's not the same step as what @rogerluan said. There is a small chance that it was just App Store Connect API's error 🤷♂ )

Oh goodness! I don't know if your results make me feel better or worse 😝
I'll try to replicate on my side and see which of these errors (if any) I get 😬

I think I might understand what is going on.
https://github.com/fastlane/fastlane/blob/53ce1fab1f616b981fc80d3abd97320f65187ba7/deliver/lib/deliver/upload_screenshots.rb#L131-L148
The above check code "index >= 10" still works without "overwrite_screenshots: true" if you append images to only the end of the set. But in the scenario below, "index" will kind of make a contradiction...
Let's say we have already uploaded 6 screenshots for 6.5-inch screen like this.

"6.5_1.jpg" (uploaded)
"6.5_2.jpg" (uploaded)
"6.5_3.jpg" (uploaded)
"6.5_4.jpg" (uploaded)
"6.5_5.jpg" (uploaded)
"6.5_6.jpg" (uploaded)

And then you happen to copy another lang's 6.5inch screenshots and paste to the directory ^ those screenshots are stored. It will be like this if sorted. (This would sound weird but was the easiest way to replicate this actually.)

"6.5_1 copy.jpg" (local)
"6.5_1.jpg" (uploaded)
"6.5_2 copy.jpg" (local)
"6.5_2.jpg" (uploaded)
"6.5_3 copy.jpg" (local)
"6.5_3.jpg" (uploaded)
"6.5_4 copy.jpg" (local)
"6.5_4.jpg" (uploaded)
"6.5_5 copy.jpg" (local)
"6.5_5.jpg" (uploaded)
"6.5_6 copy.jpg" (local)
"6.5_6.jpg" (uploaded)

With the current code, it's going to pick up the first 10 images from the above list to decide "skip" or "upload", which means -

5 local images; "6.5_1 copy.jpg", "6.5_2 copy.jpg", "6.5_3 copy.jpg", "6.5_4 copy.jpg" and "6.5_5 copy.jpg", are going to be newly uploaded
"6.5_6 copy.jpg" and "6.5_6.jpg" will be just ignored
Since 6 images "6.5_[1-6].jpg" have been uploaded already, at least one of those uploads must fail (it's concurrently working so can't tell which one fails)
Unfortunately, the loop can't that fast exit by timeout (it's going to take up 20 mins on each error 🏃♂ 🏃♂ 🏃♂ )

I might be wrong but this is what I got so far. I can work on fixing this tomorrow🙂

I happen to remember what I did when I faced this issue, and it sounds a lot similar to your explanation @ainame :
I uploaded 7 images, named whatever. I didn't submit the app for review.
Then I renamed all the images (same assets, just renamed), and ran the lane again. It attempted to upload them all again, of course. But since overwrite_screenshots wasn't true, it uploaded only 3 of them, and there were already 7 of them in the store, so I got stuck in the Waiting for screenshot to appear before uploading... loop.
In your scenario, sounds like the rationale would be to check that there're more than 10 assets. But in mine, probably the image checksum/cache mechanism would need to be updated 🤔 I don't think that's the best way out, though, I honestly think that overwrite_screenshots: true is the right solution for my problem.
It'd be great if we knew what went wrong to everyone else 😄 but sounds like your problem might be similar to other people's scenarios 👍

I've got a fix for this on my forked repo. Will submit a PR soon🙂
https://github.com/fastlane/fastlane/compare/master...ainame:fix-deliver-upload-screenshots
While working on it, I thought about a few things.

Skipping screenshots uploads is cool but involves confusions to fastlane-users

I think the scenario rogerluan described can easily happen and people may tend to not update the option to overwrite at their first try
The ambiguity when not using overwrite_sreenshots: true for users is considerably big so that it's not 100% useful
Maybe we can better handle partial updates even with overwrite_screenshots: false

Spaceship::ConnectAPI models can't really handle status code so that any errors were dealt as the same

It would be great if a wrapped error class has the direct access to status code https://github.com/fastlane/fastlane/blob/master/spaceship/lib/spaceship/connect_api/api_client.rb#L180

I may propose some changes around the behaviour of screenshots updates at some point in order to not make this kind of confusions🤞

Submitted https://github.com/fastlane/fastlane/pull/17346 🙂

@rogerluan

Then I renamed all the images (same assets, just renamed), and ran the lane again. It attempted to upload them all again, of course. But since overwrite_screenshots wasn't true, it uploaded only 3 of them, and there were already 7 of them in the store, so I got stuck in the Waiting for screenshot to appear before uploading... loop.

I feel like this isn't exactly the same scenario as I expected. Because renaming file shouldn't change its file's MD5 checksum at all so that deliver should recognise the same file uploaded on App Store Connect even if the file name is different.

@ainame I initially thought so as well, however, first I thought that the checksum would change because of the metadata (filepath) change - but in fact it doesn't (I verified this via bash and not ruby, but should be the same behavior I hope 😇 )
find … -print0 | xargs -0 md5

# Then renamed the file and repeated the command and they print the same md5 in fact

Then, on a second thought, although the checksums match - aren't we using the filepath as an identifier for the cache? 🤔 I didn't dig much into the code but I had the feeling that we were using like a key:value relation where the key was the filepath and the value was the checksum.
I can be totally wrong tho, you have deeper knowledge of all this 😁 lmk if any of this makes sense :)

@rogerluan  deliver only relies on checksum to match up. There's no caching at all. It's just to classify "Skip uploading" or "Upload", in reality🙂
https://github.com/fastlane/fastlane/blob/818b4e34edeb090fbc7d8c5bab9d3e45ce0483f0/deliver/lib/deliver/upload_screenshots.rb#L137-L138


Client doesn't know when server closes.

Have to create some behaviour that will tell clients when server shutdowns.

Closed by 974a23a commit from Aug 28, 2023


Dolby SMS: Feature Requests / Sponsorship

The following features have been requested:

Testing & bugfixes for other dolby SMS models (e.g. IMS-3000).
Addition of transport controls for play / pause / eject, etc
Dropdown list & load button for selection of SPL

These features may eventually be added to the plugin in spare time, but otherwise require sponsorship to prioritise.
Please reach out to<EMAIL_ADDRESS>if you are interested in sponsoring this development work.

Further requests:

macro list should auto increment the default selection
password should be obscured


Landing Page Enhancement:  UI Component of our Service in Home Page

We shold have an  UI Component in Home Page of our service

Inspiration

Additional Context

I'm ready to work on this UI Component

@akshitagupta15june  I am interested to contribute to this issue

@Piyush-linux  intrested to contribute

@Mrunalkhanke yup


[WIP] Improve Ukrainian glossary

Proposing some changes by @Andygol for publication. Commits taken from #45371

CLA check is passing; @Andygol can you confirm these commits are all your own work?
:information_source: you're also welcome to open a pull request directly.

CLA check is passing; @Andygol can you confirm these commits listing you as the author are all your own work?
ℹ you're also welcome to open a pull request directly.

Yes, I certify that all this work is my own.
I described my workflow here https://github.com/kubernetes/website/discussions/45209#discussioncomment-8576370

@sftim could you add the uk.toml translated by me to this PR file as the glossary layout depends on it?

/retitle Improve Ukrainian glossary

This is an artistic translation, not a technical one.
If there are no stable corresponding words in the Ukrainian language, it is better to use Anglicisms, otherwise, people who read the original and those who read the translation will not understand each other => and those who read the translation will not get a job

This is an artistic translation, not a technical one.
If there are no stable corresponding words in the Ukrainian language, it is better to use Anglicisms, otherwise, people who read the original and those who read the translation will not understand each other => and those who read the translation will not get a job

What needs to happen for this PR to merge? I'm not sure I understand.

The PR is massive from a reviewing/approving perspective. Following the precedent set by @natalisucks's comment in https://github.com/kubernetes/website/pull/45371, please break this into smaller chunks for ease of review.
/hold

@Andygol - would you be willing to open PRs that contain chunks of the work you've done in your own fork? You could base them on this PR if that's helpful.

I'll drop this
/close


NuGet packages still using deprecated licenseUrl element

WARNING: The  element is deprecated. Consider using the  element instead. Learn more: https://aka.ms/deprecateLicenseUrl.,Readme missing. Go to https://aka.ms/nuget-include-readme learn How to include a readme file within the package.

Could someone submit a pull request to resolve this. The build warning came before tooling supported the newer license element so we suppressed the warning (#481), that suppression can now be removed too.

I'll take a look, should only take a couple of minutes.

@Toxantron Seems that you got away from that again?
@jonorossi Added a PR for comments, not sure if it was such a fix you had in mind, the issue lacked some context for me.


Multi-namespace release is not fully upgraded

A silent K8s upgrade from Google Cloud broke my helm charts, since they still use deprecated APIs, namely
kind: DaemonSet
apiVersion: extensions/v1beta1

and
kind: Deployment
apiVersion: apps/v1beta1

Using the plugin the Deployments were upgraded successfully, but the DaemonSet is located in a different K8s namespace.
What happened
helm outputs:
$ helm ls
NAME             	NAMESPACE	REVISION	UPDATED                             	STATUS  	CHART              	APP VERSION
PROJECT	default  	65      	2020-12-09 23:35:36.911248 +0100 CET	deployed	PROJECT-2.13.3

Commands run:
$ helm mapkubeapis PROJECT
2020/12/09 23:48:56 Release 'PROJECT' will be checked for deprecated or removed Kubernetes APIs and will be updated if necessary to supported API versions.
2020/12/09 23:48:56 Get release 'PROJECT' latest version.
2020/12/09 23:48:56 Check release 'PROJECT' for deprecated or removed APIs...
2020/12/09 23:48:56 Finished checking release 'PROJECT' for deprecated or removed APIs.
2020/12/09 23:48:56 Release 'PROJECT' has no deprecated or removed APIs.
2020/12/09 23:48:56 Map of release 'PROJECT' deprecated or removed APIs to supported versions, completed successfully.

$ helm upgrade PROJECT ./helm/prod --dry-run
Error: UPGRADE FAILED: current release manifest contains removed kubernetes api(s) for this kubernetes version and it is therefore unable to build the kubernetes objects for performing the diff. error from kubernetes: unable to recognize "": no matches for kind "DaemonSet" in version "extensions/v1beta1"

What I expect to happen
DaemonSet in kube-system namespace should be updated as well.
Versions and K8s config
Versions:
$ helm version
version.BuildInfo{Version:"v3.4.2", GitCommit:"23dd3af5e19a02d4f4baa5b2f242645a1a3af629", GitTreeState:"dirty", GoVersion:"go1.15.5"}

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.3", GitCommit:"1e11e4a2108024935ecfcb2912226cedeafd99df", GitTreeState:"clean", BuildDate:"2020-10-14T12:50:19Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.13-gke.404", GitCommit:"81e2afbf51b876d15f0af546998c670207fdd592", GitTreeState:"clean", BuildDate:"2020-10-30T23:52:44Z", GoVersion:"go1.13.9b4", Compiler:"gc", Platform:"linux/amd64"}

DaemonSet yaml:
kind: DaemonSet
apiVersion: apps/v1
metadata:
  name: traefik-ingress-controller
  namespace: kube-system  # helm deployment is in default namespace
  labels:
    k8s-app: traefik-ingress-lb
spec:
  selector:
    matchLabels:
      name: traefik-ingress-lb
      k8s-app: traefik-ingress-lb
  template:
    metadata:
      labels:
        k8s-app: traefik-ingress-lb
        name: traefik-ingress-lb
    spec:
      serviceAccountName: traefik-ingress-controller
      terminationGracePeriodSeconds: 60
      containers:
      - image: traefik:{{ .Chart.Version }}
        name: traefik-ingress-lb
        ports:
        - name: http
          containerPort: 80
          hostPort: 80

@Steffen911 When you mention Multi-namespace release, I think you mean that the Kubernetes resources deployed by the Helm chart are in different namespaces. The Helm release metadata which is stored in a secret object will reside in the namespace of the Helm deployment.
This plugin updates the API versions of the manifest metadata stored in the Helm release secret object. This is so that Helm can manage existing releases with removed APIs as explained in Helm docs. It does not update the Kubernetes objects in the cluster like the Deployment or DemonSet objects. This is done by Kubernetes when the cluster is updated to a version which has removed APIVersions.
It might be that the plugin can't find an APIVersion in the manifest metadata because it is in a different format to that in the mapping file.  have you looked at API mapping?

Resolved by following the "complicated" guide here: https://helm.sh/docs/topics/kubernetes_apis/#updating-api-versions-of-a-release-manifest

Resolved by following the "complicated" guide here: https://helm.sh/docs/topics/kubernetes_apis/#updating-api-versions-of-a-release-manifest


Update the reference of federationToStitchingSDL

Now federationToStitchingSDL is in @graphql-tools/stitching-directives thanks to @gmac  :) and we mention about it in our docs;
https://www.graphql-tools.com/docs/schema-stitching/stitch-federation

Woot, thanks!!


Run tests with Go 1.7 as well with TravisCI

BTW, should we try to compile with more recent versions of libvirt too? We could add the latest one (2.3.0 currently).

BTW, should we try to compile with more recent versions of libvirt too? We could add the latest one (2.3.0 currently).

That sounds like a great idea.

I have appended a commit to this PR for that. Let's see if it works.


Generalisability and importability

*Improved generalisability to multiple network architectures, including ResNets. All submodules are now enabled. Only one module can act as VGG's feature module.
*Added support for multiple input sizes. Avgpool layers are now run, but on the assumption they are followed by flattening.
*gradcam.py can be used in import statements now. Example: "from gradcam import GradCam"

I am closing this pull request as I found some extra time to implement GB improvements too. I will update you in a second.


Resource quota changes to give memory back sooner to total quota

Copying craig's changes to give memory back to total quota sooner.
@veblush

Probably prefer max(size_t(0), free_bytes.load())?
reinterpret_cast seems OP

Probably prefer max(size_t(0), free_bytes.load())?
reinterpret_cast seems OP

This didn't work on linux. Had to cast the 0 to inptr_t to make it happy :)


Issue/6959 update project release documentation iso6

Description
iso6 PR for https://github.com/inmanta/inmanta-core/issues/6959
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso6 in 47637fb719d0a30ea670b8b43f298db8f0078c54


I'm getting this issue log : The maximum tokens you requested exceeds the model limit of 4096. Try again with a maximum tokens value that is lower than 4096.

Before submitting your bug report

[ ] I believe this is a bug. I'll try to join the Continue Discord for questions
[ ] I'm not able to find an open issue that reports the same bug
[ ] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info
- OS:
- Continue version:
- IDE version:
- Model:
- config.json:

Description
No response
To reproduce
No response
Log output
No response

Same behavior here : MacOS 15.2 / Version 0.8.65 / Visual Studio Code 1.96.2 / Model anthropic.claude-3-5-sonnet-20240620-v1:0 via AWS Bedrock

I also have this error using any AWS Bedrock model using MacOS 15.2 / Continue: 0.9.246 / VS Code 1.96.2

Same behavior here : MacOS 15.2 / Version 0.8.65 / Visual Studio Code 1.96.2 / Model anthropic.claude-3-5-sonnet-20240620-v1:0 via AWS Bedrock

Same behavior today with V0.9.246 and V0.8.66

I am getting the same error. with v0.8.66 - 2024-12-20.


webcfg: cache static files

Adding Cache-Control header to files, the browser will automatically skip download on each page visit.

Thanks


Player Collisions

It seems we need this after all

Don't prevent collisions, but drain 0.01 HP per frame on collision

done


feat: path support under windows

What type of PR is this?
feat
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
实现在windows下的路径支持
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en: When using the kitex command-line tool to generate files under the Windows platform, due to the differences in path parsing between different platforms, the package name path in the file will become an incorrect backslash. This pr will deal with this problem.
zh(optional): 在windows平台下利用kitex命令行工具生成文件时，由于不同平台间的路径解析差异，文件中的包名路径会变成错误的反斜杠，本pr将对这一问题进行了处理
Which issue(s) this PR fixes:

fix #469

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

支持 windows 的设计可能要配合 thriftgo 一起修改，现在还没开始做，我先 close 下，等这次发版之后再看下吧


Dockerfile builds even if tests fail

Change dockerfile to only build once all tests pass
need to resolve #9 first

Resolved in push to dockerhub workflow


[Feature Request] Should have benchmarks

What is the feature ?

After working on #56 and #54 I think it would be nice to have some some reference benchmarks to measure if certain changes actually improve or degrade performance, esp. when iterating the CPU-only BitMapBackend.

Why do you need the feature ?
What is the use case ?

See above.

Yes, I saw your benchmark. I believe that is a good start point.

I just saw you implemented criterion benchmarks. Awesome! This is exactly what I was hoping for, thank you so much!


Write a PHP program to convert days to weeks

Description
Write a PHP program to convert days to weeks
1 week = 7 days
Input  : 35
Output : 5

How to contribute

Save the solution in program/convert_days_to_weeks.php file
Add convert_days_to_weeks.php file in convert-days-to-weeks folder

!assign