az storage blob upload-batch: incorrect usage: source must be an existing directory

Describe the bug
I want to copy all files and sub-folder files in the Build Artifacts Folder to the Azure Storage Container.
I have attempted to copy one single file from the Build Artifacts Folder to the Azure Storage Container with success, using the command:
az storage blob upload --account-name $(accountName) --container-name $(storageContainer) --name dummyfile --file "$(Build.ArtifactStagingDirectory)/Folder/dummy.txt" --overwrite
However, when I attempt to copy all files using the az storage blob upload-batch command, I get the following error:
ERROR: incorrect usage: source must be an existing directory
The command I am using:
az storage blob upload-batch -s $(Build.ArtifactStagingDirectory)/Folder/ -d $(storageContainer)
I have also tried with:
az storage blob upload-batch -s $(Build.ArtifactStagingDirectory)/Folder/ --account-name $(accountName) -d $(storageContainer)
I am sure that the artifact's contents of the Folder are correct as I have outputed/listed them and confirmed.
Related command
az storage blob upload-batch
Errors
ERROR: incorrect usage: source must be an existing directory
Issue script & Debug output
ERROR: incorrect usage: source must be an existing directory
##[debug]Exit code 2 received from tool 'C:\Program Files\Git\bin\bash.exe'
##[debug]STDIO streams have closed for tool 'C:\Program Files\Git\bin\bash.exe'
##[debug]task result: Failed
##[error]Script failed with exit code: 2
##[debug]Processed: ##vso[task.issue type=error;]Script failed with exit code: 2
##[debug]Processed: ##vso[task.complete result=Failed;]Script failed with exit code: 2
##[debug]which 'az'
##[debug]found: 'C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd'
##[debug]C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd arg:  account clear
##[debug]C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd arg:  account clear
##[debug]exec tool: C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd
##[debug]exec tool: C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd
##[debug]arguments:
##[debug]arguments:
##[debug]   account
##[debug]   account
##[debug]   clear
##[debug]   clear
C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\Microsoft SDKs\Azure\CLI2\wbin\az.cmd" account clear"
Finishing: Deploy to Azure Blob Storage

Expected behavior
Copying all files and sub-folder files in the Build Artifacts Folder to the Azure Storage Container.
Environment Summary
azure-cli                         2.53.0
core                              2.53.0
telemetry                          1.1.0
Extensions:
azure-devops                      0.26.0
Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2
Python location 'C:\Program Files\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Program Files\Common Files\AzureCliExtensionDirectory'
Python (Windows) 3.10.10 (tags/v3.10.10:aad5f6a, Feb  7 2023, 17:20:36) [MSC v.1929 64 bit (AMD64)]
Additional context
Could be useful to provide the listing of files I'm trying to copy:
Your CLI is up-to-date.
Artifact Staging Directory: D:\a\1\a
D:\a\1\a:
Folder

D:\a\1\a/Folder:
Auth0.Core.dll
Auth0.OidcClient.Core.dll
Auth0.OidcClient.dll
IdentityModel.OidcClient.dll
IdentityModel.dll
IdentityModel.pdb
LanguageSupport
LiveCharts.Wpf.dll
LiveCharts.Wpf.pdb
LiveCharts.dll
LiveCharts.pdb
Microsoft.Bcl.AsyncInterfaces.dll
Microsoft.Extensions.DependencyInjection.Abstractions.dll
Microsoft.Extensions.DependencyInjection.dll
Microsoft.Extensions.Logging.Abstractions.dll
Microsoft.Extensions.Logging.dll
Microsoft.Extensions.Options.dll
Microsoft.Extensions.Primitives.dll
Microsoft.IdentityModel.JsonWebTokens.dll
Microsoft.IdentityModel.Logging.dll
Microsoft.IdentityModel.Protocols.OpenIdConnect.dll
Microsoft.IdentityModel.Protocols.dll
Microsoft.IdentityModel.Tokens.dll
Microsoft.Toolkit.Wpf.UI.Controls.WebView.dll
Microsoft.Toolkit.Wpf.UI.Controls.WebView.pdb
Newtonsoft.Json.dll
Prism.dll
Prism.pdb
Revit.Async.dll
RevitAPI.dll
RevitAPIUI.dll
RevitTemplate.dll
RevitTemplate.dll.config
RevitTemplate.pdb
System.Buffers.dll
System.Diagnostics.DiagnosticSource.dll
System.IdentityModel.Tokens.Jwt.dll
System.Memory.dll
System.Numerics.Vectors.dll
System.Runtime.CompilerServices.Unsafe.dll
System.Text.Encodings.Web.dll
System.Text.Json.dll
System.Threading.Tasks.Extensions.dll
System.ValueTuple.dll
SomeFile.addin
en
no

D:\a\1\a/Folder/LanguageSupport:
Resources.en.resx
Resources.no.resx
Resources.resx

D:\a\1\a/Folder/en:
SomeFile.resources.dll

D:\a\1\a/Folder/no:
SomeFile.resources.dll
ERROR: incorrect usage: source must be an existing directory

Thank you for opening this issue, we will look into it.

I'm very embarrassed to say that the error I was experienced was because I had to input solution with double quotes. Oh syntax 😅


Android Crash

Android 4.4.2 stock here. I created a widget to toggle the lockscreen (thanks to your tasker plugin) in order to unlock my sim cards (see #37 ).
But after enabling then disabling lockscreen, device becomes to becoma laggish, keyboard takes much longer to load, then it reaches a state where I've got a 1s total freeze every 10s, then apps all start to crash and android.systemui too (needless to say, I'm forced to reboot).
Any idea how to fix this?

My bad, I found the cause of my crashes which is an other Xposed module that I installed at the same time and completely forgot about when testing if LockScreen disabler was the cause of my crash. I can now confirm this is working flawlessly!


Navigating to page with non-successful response seems to reload javascript

We are using Turbo Drive 7.3.0, but is also happens on our 8.0.2 branch that we are working on.
In some cases, when navigating with Turbo Drive, we can navigate to a page returning a non-successful error response, such as a error 403 because the user has no permission to that page.
When this happens, Turbo does not seem to keep track of the script tags in the header correctly. They seem to be evaluated on top of the existing JavaScript, causing all kinds of issues, such as: Uncaught SyntaxError: redeclaration of const ...
We are using data-turbo-track="reload" on our scripts, however, the assets have not been changed between the requests. So we do not expect a reload at all.
The problem does not seem to occur once we return the forbidden page with a successful response code (200). Once we change it back to 403, or even 404, 400 or 500, the problem returns.

@RemcodM can you provide a minimal rails app showcasing the problem?

I've also been seeing the same re-evaluation of scripts on our Drupal site: you can trigger the re-evaluation by going to any article (e.g. the Omnipedia article) and clicking the Edit tab which gives you a 403 error; after navigating to one or two other 200 response links, you'll start seeing the console debug messages duplicate. I can try and put together a reduced test case when I have some time.

I just poked around in the Firefox dev tools a bit to try and see what's going on, and what I noticed is that the <head> element in the 200 response pages is no longer in the DOM after a visit to the 4xx page, where a different <head> element is present - I have no idea why this would be happening, but it would certainly explain the re-evaluation of scripts if it is indeed a new <head> element being added to the DOM with the <script> elements from the previous visit already present.

Yes, Turbo does this intentionally when you mark a script tag with data-turbo-track="reload". It's the only way to ensure the client runs the latest JS after a deploy.

I'm going to close this, since it seems expected behavior. But feel free to reopen with a test case if you find a bug.

Seems that you have a meta tag with data-turbo-track="reload"?

I'd try removing it and see if that helps. But, also, as I said, happy to reopen the issue if you can provide a minimal reproduction.

@afcapel I just tried removing it but it had no effect. That meta tag only ever changes when navigating between the site front-end and admin sections, where the Drupal theme changes and it does force a full page load as it's supposed to, so I would have been surprised if it had an effect. I appreciate you getting back to me, and I'll see if I can throw together a minimal reproduction.

So I did some debugging in dev tools and discovered that the ErrorRenderer class always replaces the <head> outright:
https://github.com/hotwired/turbo/blob/861fcca4eed3b2d97240284e99eafeb43d55fca5/src/core/drive/error_renderer.js#L18
This probably makes sense for some apps, but in our cases it seems like it's creating a weird in between state where a full page load has not occurred so scripts executed previously still linger in the JavaScript environment but the scripts get re-evaluated by ErrorRenderer:
https://github.com/hotwired/turbo/blob/861fcca4eed3b2d97240284e99eafeb43d55fca5/src/core/drive/error_renderer.js#L13
In our Drupal app, the 4xx pages contain the same linked JavaScript files as most other pages, so this means Turbo re-evaluates all the same JavaScript files on an error response.
The full stack trace:
replaceHeadAndBody (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#3719)
render (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#3713)
renderSnapshot (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#1535)
render (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#1495)
renderError (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#4985)
loadResponse (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2506)
render (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2710)
loadResponse (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2495)
visitRequestFailedWithStatusCode (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2780)
recordResponse (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2482)
requestFailedWithResponse (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2616)
receive (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#856)
perform (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#831)
issueRequest (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2458)
visitStarted (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2751)
start (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2408)
startVisit (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#3290)
visitProposedToLocation (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#2742)
visitProposedToLocation (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#5337)
proposeVisit (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#3280)
visit (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#5201)
followedLinkToLocation (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#5326)
clickBubbled (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#1635)
clickCaptured (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#1624)
start (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#1610)
start (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#5155)
start (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#5602)
<anonymous> (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#6573)
<anonymous> (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#8)
<anonymous> (https://omnipedia.ddev.site/modules/contrib/refreshless/modules/refreshless_turbo/vendor/%40hotwired/turbo/dist/turbo.es2017-umd.js?v=8.0.2#9)

Using that clue, I took a look at Visit.loadResponse():
https://github.com/hotwired/turbo/blob/861fcca4eed3b2d97240284e99eafeb43d55fca5/src/core/drive/visit.js#L219
and replaced that line with:
const snapshot = PageSnapshot.fromHTMLString(responseHTML);
await this.renderPageSnapshot(snapshot, false);

reloaded the page, and bingo, it no longer re-evaluates all of our JavaScript no matter how many 4xx error pages I visit.

Given that, is there a way to configure Turbo to use the normal renderer rather than the error renderer?

@afcapel we are running into the same issue: we are rendering our error pages in the full application layout (ie. also the complete <head> with all javascript files) from our normal pages. This leads to our entire javascript being loaded twice (eg. all click handlers are there 2 times, etc.)
I tried following your advice and removed all data-turbo-track attributes, but this does not make a difference. It still double loads the Javascript code:

I don't think this problem is related to data-turbo-track. Do you have any pointers how to create a minimal test case? I believe it should be simple (just a JS file which is loaded in both the normal visit and the error visit which sets a global const should be sufficient).
I looked if I can somehow force a hard-reload on error pages, but I couldn't find a solution which worked in all cases:

<meta name="turbo-visit-control" content="reload"> does not seem to work as the ErrorRenderer does not seem to pick it up
using turbo:before-fetch-response-event was tricky due to prefetching

It would be great if I could indicate in a response header that a full page visit should happen, but I haven't found such a thing.


Ver 1.4.7 CRC does not match on arduino IDE v1.6.9

When trying to update or install the DueTimer library via the libraries manager in the arduino IDE I get the following error:
CRC doesn't match. File is corrupted. java.lang.RuntimeException: java.lang.Exception: CRC doesn't match. File is corrupted.     at cc.arduino.contributions.libraries.ui.LibraryManagerUI.lambda$onInstallPressed$12(LibraryManagerUI.java:231)     at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.Exception: CRC doesn't match. File is corrupted.     at cc.arduino.contributions.DownloadableContributionsDownloader.download(DownloadableContributionsDownloader.java:77)     at cc.arduino.contributions.libraries.LibraryInstaller.install(LibraryInstaller.java:97)     at cc.arduino.contributions.libraries.ui.LibraryManagerUI.lambda$onInstallPressed$12(LibraryManagerUI.java:227)     ... 1 more
Is this a problem on my side or of the library?

Problem seems to be resolved in 1.8.5


chore: upgrade angular version to 7.2.1

Upgrade angular libs.
Related issues
Fixed #11

Thanks for your work

@gioboa  Thanks for your work


Dev

Proposed change

Multiple bugfixes for issues that have been reported.

fixes #371
fixes #373
should give more insights into #353, #372, https://github.com/bimmerconnected/ha_custom_component/issues/12
more logging to understand https://github.com/bimmerconnected/ha_custom_component/issues/16 better

Type of change

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality to this library)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR fixes or closes issue: fixes #
This PR is related to issue:

Checklist

[x] The code change is tested and works locally.
[X] Tests have been added to verify that the new code works.

Codecov Report

Merging #374 (ac12787) into master (39213b8) will decrease coverage by 0.27%.
The diff coverage is 92.00%.

@@            Coverage Diff             @@
##           master     #374      +/-   ##
==========================================
- Coverage   96.43%   96.16%   -0.28%
==========================================
  Files           8        8
  Lines         897      912      +15
==========================================
+ Hits          865      877      +12
- Misses         32       35       +3

Flag
Coverage Δ

3.10.x
96.16% <92.00%> (-0.16%)
:arrow_down:

3.6
?

3.7
?

3.8
?

3.9
96.15% <92.00%> (-0.16%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

bimmer_connected/vehicle.py
97.47% <83.33%> (-0.82%)
:arrow_down:

bimmer_connected/vehicle_status.py
97.66% <92.85%> (-0.28%)
:arrow_down:

bimmer_connected/account.py
94.73% <100.00%> (+0.10%)
:arrow_up:

bimmer_connected/utils.py
97.05% <0.00%> (-2.95%)
: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 39213b8...ac12787. Read the comment docs.


Setup community

Setup the community part of the repo so that there is somewhere to discuss the project.

First announcement  made


Wrong location in example

This is a small issue. The following command has the location "East US" instead of "EastUS":
New-AzureRmVm     -ResourceGroupName "myResourceGroupVM"
-Name "myVM2"     -Location "East US"
-VirtualNetworkName "myVnet"     -SubnetName "mySubnet"
-SecurityGroupName "myNetworkSecurityGroup"     -PublicIpAddressName "myPublicIpAddress2"
-ImageName "MicrosoftWindowsServer:WindowsServer:2016-Datacenter-with-Containers:latest"     -Credential $cred
-AsJob

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

ID: 55e23176-40c4-39bd-4f6f-cc48e518cf96
Version Independent ID: 370fcf36-dce0-6718-4566-34a71cd0314e
Content: Tutorial - Create and manage Windows VMs with Azure PowerShell
Content Source: articles/virtual-machines/windows/tutorial-manage-vm.md
Service: virtual-machines-windows
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@miguel-vega is this causing an error? I believe since we have the location in quotes the string is formatted correctly.

I believe the location parameter expects the name of the location and not the display name right? When I use "eastus" it works, but "East US" doesn't.
This is the error I get:
New-AzureRmVm : Location in request URI 'East US' does not match location of the service 'eastus'
At line:1 char:1


Bump query-string to v8

Description

Supersedes #2734, fixing its breaking changes.
Also updates our tsconfig.json to target ES2016 → ES2020.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Code quality improvements

How to test

Checklist

[ ] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 37.396%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5739

Relevant Lines:
14438

💛  - Coveralls


[MINOR][TESTS] Add a helper function for spark.table in dsl

What changes were proposed in this pull request?
Add a helper function for spark.table in dsl
Why are the changes needed?
to be used in tests
Does this PR introduce any user-facing change?
no, test only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

merged to master


[Bug] Not picking option from the option group during registration causes errors

Require or force selection on the option group

Issue solved by adding the required attribute to single-option groups and additional form validation for the (optional) multi-option groups


Updated docs, readme and docs infra

Codecov Report

Merging #95 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev      #95   +/-   ##
=======================================
  Coverage   15.92%   15.92%
=======================================
  Files          10       10
  Lines         854      854
  Branches      116      116
=======================================
  Hits          136      136
  Misses        712      712
  Partials        6        6

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 314ff64...4b5d4a8. Read the comment docs.


Split out findStatus() to separate file (for browserify)

...so that it can be aliased to always return "valid" for lighter browser builds. I can PR this if you agree with the decision.

That doesn't really make any sense, I think? At that point the processing function deteriorates to a string.normalize(), the toUnicode function is basically a no-op otherwise and you can shim the toASCII method really easily by just splitting the string into labels and applying punycode manually.

toASCII() uses punycode.toASCII()
toUnicode() appears to use punycode.toUnicode()

toUnicode() appears to use punycode.toUnicode()

It doesn't.

toASCII() uses punycode.toASCII()

Yeah, and that's (basically) the only thing it does if you always return valid from findStatus. You might as well use a shim js file which just calls into punycode yourself to remove the whole need for tr46 then.

That doesn't make sense to me. toASCII() converts to punycode and toUnicode() never converts back?
What does this do?: https://github.com/Sebmaster/tr46.js/blob/master/index.js#L109
(my npm installed file uses toUnicode() instead, by the way)

Ah yeah, I overlooked that. Point still stands though. Just shim both methods with a split('.').map(l => punycode.en/decode(l))?

I end up with strange results.. suffixed "-" characters and missing "xn--" prefix.

Hmm, when switching back from encode/decode to toASCII/toUnicode, it works.

How different would toLowerCase() and punycode's toASCII() be from the TR46 spec? I'm looking for specific examples to document. The spec mentions that case-folding is different than lowercasing, "particularly for Cherokee characters". What would be an example of this, and are there other particulars besides Cherokee?

Check out the actual mapping table. Anything that has mapped as it's type is transformed to another character (there are some special cases for std3/transitional processing, but mapped is a safe bet). You gotta figure out when it does not match up with toLowerCase though.

Awesome. There're only 86 mappings that don't correspond to lowercasing. We could maybe lighten this library by using a memoized map of characters. Iterating through a long array wouldn't be necessary.

We will also need to check if there are any uppercase chars which should not be mapped and we'll have to think about the std3 and transitional processing as well.

Oops, I had the numbers wrong. There're 992 lowercasings, 86 uppercasings and 4513 other-casings.


libc: thread-safe newlib

The aim of this PR is to utilize the functionalty provided by newlib for thread-safety.
RFC #21519
Relevant Links
Documentation
Newlib Documentation on __malloc_lock
Newlib Documentation on Reentrancy
Mailing Lists
Newlib discussion on --enable-newlib-retargetable-locking
[PATCH, newlib] Allow locking routine to be retargeted
What are the __retarget_lock functions?

RFC #21519

@stephanosio @andyross @andrewboie

do we need to make this change in the context switch code for all arches or is there something special about ARM that _impure_ptr needs to be updated like this?
also what about SMP?

This has an impact on all architectures. As described within the RFC, I've only added ARM (checkpatch shall complain until all others are there too, to avoid having a partial implementation going into Zephyr).
My main intent was to bring up the issue, perhaps it wasn't a good idea to support the RFC with a PR as it draws more attention to the implementation than the feature.
Let's get one step back:

Do you agree that it would be great to have a thread-safe newlib?
If so, do you want me to work on this PR, or do you rather prefer to work on it yourself on your own fork/branch? I don't mind working on it - got a few days off and want to have this feature, but I think it is way more efficient if you guys take over and make something neat (instead of having to point some novice to the coding guidelines) - no worries to drop this PR in favour of something better.

Now that I have your attention ;), @stephanosio mentioned to patch newlib. That's partially what I considered when mentioning the alternative RTEMS route to go. Having a OS dependend toolchain and droping the support for GNU ARM embedded. Why dropping the support? Well, the next issue that will arise is within libstdc++:

The C++ library string functionality requires a couple of atomic operations to provide thread-safety. If you don't take any special action, the library will use stub versions of these functions that are not thread-safe. They will work fine, unless your applications are multi-threaded.

If you want to provide custom, safe, versions of these functions, there are two distinct approaches. One is to provide a version for your CPU, using assembly language constructs. The other is to use  the thread-safety primitives in your operating system.

https://gcc.gnu.org/onlinedocs/libstdc++/manual/internals.html#internals.thread_safety
No strings == no go to me.
Those functions go in libstdc++ there are no simple hooks - one has to either add a full OS / thread model to GCC / libstdc++, or tweak the single thread implementation by adding hooks which we can use like the newlib stuff.

Do you agree that it would be great to have a thread-safe newlib?

Not just great, it is absolutely imperative if we are going to do anything useful with the newlib.
Maybe #21519 should be labeled a "bug" and "high priority" since this issue practically renders the newlib useless?
I can see that there are many projects that require the newlib (e.g. net and gui) and this means that there is the possibility of them "randomly" crashing from the thread safety issues at any moment.

Those functions go in libstdc++ there are no simple hooks - one has to either add a full OS / thread model to GCC / libstdc++, or tweak the single thread implementation by adding hooks which we can use like the newlib stuff.

@pabigot This sounds like something that must be addressed before we can say C++ is supported in the Zephyr, alongside many other issues.

@pabigot This sounds like something that must be addressed before we can say C++ is supported in the Zephyr, alongside many other issues.

Agreed, added to #18554.
Zephyr has some features that make it difficult to guarantee mutex/thread-safety, regardless of language: ZLIs and meta-IRQs.  For the purposes of newlib support we can ignore them.

@pabigot Documentation (at least what exists and is not in source), even the newlib discussions are linked in the RFC - and the first thing I did, was to interlink RFC and PR. I've now added a textual link. Shall I simply copy over the RFC? Yes we require a better documentation as soon as it is clear which way to pursue.  Regarding the libstdc++ which came up during the discussion here - shouldn't we open a separate issue for that?

@pabigot Documentation (at least what exists and is not in source), even the newlib discussions are linked in the RFC - and the first thing I did, was to interlink RFC and PR. I've now added a textual link and copied over the links to the documentation.

It's nice to have it in the github issue, but when we come back to this in six months for maintenance it'd be nice to have something in the code or commit message.  Going back to the issue and PR given a commit SHA1 is not particularly difficult, but it's not trivial either.  Mentioning the RFC issue number as #21519 in the commit message would make it easier; a short sentence in the code explaining things might even make it unnecessary.

Regarding the libstdc++ issue which came up during the discussion here - shouldn't we open a separate issue for that?

Perhaps.  There is a tie to this issue in #18554.  I'm not clear on exactly what else needs to be done for C++ support.  I don't believe we're ever going to get C++ threads to be supported by Zephyr: there's too much resistance to C++ at the project level, and I don't believe the thread model is compatible.

@stephanosio @andyross @andrewboie @carlescufi @pabigot.
It seems that this PR is still relevant for newlib support. How do we proceed with that?

@stephanosio @andyross @andrewboie @carlescufi @pabigot.
It seems that this PR is still relevant for newlib support. How do we proceed with that?

The issue tracking this is currently tracked as "enhancement" and not "bug", and there isn't pressure applied at release time to resolve it since it doesn't contribute to the release bug count requirements. We rely solely on the motivation of the reporter/author to move it along.
I think it should be promoted to "bug", but agree to scope it for 2.5 and find a dedicate owner to see it through if @kaidoho isn't working on it.


x64: Add pre-SSE4.1 compatible lowerings for misc instructions

This commit updates some lowerings using SSE4.1 instructions in miscellaneous locations to compatible versions not using these instructions. This primarily worked by extracting some rules to helpers and delegating to the helpers instead of specific instructions.
One large-ish instruction updated here is the unarrow instruction which lowers to packusdw and doesn't seem to have any "easy" lowering so I took a look at LLVM and tried to simplify it for ISLE.

It's worth noting that this is the last set of SSE4.1 lowerings, yay! I'll have a follow-up PR to this which actually disables the requirement for SSE4.1 and enables fuzzing all the previously added lowerings.


"FakeData" term used

Is your feature request related to a problem? Please describe.
The queries use the term "FakeData"

Ah, Great question.
The FakeData table is to allow cross-table correlation even if it doesn't exist. These queries are dependent on 3 different work streams. Meaning if you've only enabled 1 out of the 3, you'll be missing the references when running the query. As a result, 'FakeData' was added to make it look like the tables do exist even if they don't currently in your Log Analytics workspace.

@hctrr , please let me know if this answered your question.

thank you @chboeh for the explanation.
Would you consider changing the term away from the prefix of "fake"? The current term has a bad connotation that doesn't/wouldn't sit well for people that see these queries.
common statement when showing these queries is - "why does it say fakedata?"
at that point people start questioning the results and content being displayed.


[YUNIKORN-2695] remove core dependency pkg/common

What is this PR for?
This PR modifies the dependency between yunikorn-k8shim and yunikorn-core. In this PR, the common.WaitForCondition method can be called within yunikorn-k8shim, allowing yunikorn-k8shim to function without relying on yunikorn-core. Consequently, this reduces the dependency of YUNIKORN-shim on YUNIKORN-core.
What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos

[ ] - Task

What is the Jira issue?
[YUNIKORN-2695]
How should this be tested?
make test
Screenshots (if appropriate)

No problem.I will fix it as soon as possible .


v3.0 release includes outdated vendors directory

Describe the bug
When installing from zip, the included vendors directory includes the old League/Flysystem S3 Adapter. The classnames have changed, and the source code was correctly updated, however the vendors directory embedded in the released zipfile is outdated.
To Reproduce
Steps to reproduce the behavior:

Create a new omeka install
Install the v3.0 AnyCloud module from zip.
Configure it for Amazon S3
Attempt to upload or view a media.

Expected behavior
Uploading or viewing work.
Screenshots
White screen, 500. Logs attached below. AnyCloud is attempting to reference a classname that is not present in the vendors directory.
Desktop (please complete the following information):

OS: [e.g. iOS] Linux, dockerized debian.
Browser [e.g. chrome, safari] Chrome
Version [e.g. 22] v.3.0

Additional context
relevant log:
2023-07-31T19:04:08+00:00 ERR (3): Error: Class "League\Flysystem\AwsS3V3\AwsS3V3Adapter" not found in /var/www/omeka/modules/AnyCloud/src/Service/File/Adapter/AwsAdapter.php:25
Stack trace:
#0 /var/www/omeka/modules/AnyCloud/src/Service/File/Store/AnyCloudFactory.php(60): AnyCloud\Service\File\Adapter\AwsAdapter->createAdapter(Object(Omeka\Settings\Settings))
#1 /var/www/omeka/modules/AnyCloud/src/Service/File/Store/AnyCloudFactory.php(79): AnyCloud\Service\File\Store\AnyCloudFactory->createAdapter(Object(AnyCloud\Service\File\Adapter\AwsAdapter))
#2 /var/www/omeka/modules/AnyCloud/src/Service/File/Store/AnyCloudFactory.php(45): AnyCloud\Service\File\Store\AnyCloudFactory->createAwsAdapter()
#3 /var/www/omeka/modules/AnyCloud/src/Service/File/Store/AnyCloudFactory.php(34): AnyCloud\Service\File\Store\AnyCloudFactory->createFilesystem()
#4 /var/www/omeka/vendor/laminas/laminas-servicemanager/src/ServiceManager.php(615): AnyCloud\Service\File\Store\AnyCloudFactory->__invoke(Object(Laminas\ServiceManager\ServiceManager), 'AnyCloud\\File\\S...', NULL)
#5 /var/www/omeka/vendor/laminas/laminas-servicemanager/src/ServiceManager.php(234): Laminas\ServiceManager\ServiceManager->doCreate('AnyCloud\\File\\S...')
#6 /var/www/omeka/application/src/Api/Representation/AbstractResourceRepresentation.php(262): Laminas\ServiceManager\ServiceManager->get('Omeka\\File\\Stor...')
#7 /var/www/omeka/application/src/Api/Representation/MediaRepresentation.php(86): Omeka\Api\Representation\AbstractResourceRepresentation->getFileUrl('square', '329916a74248e77...', 'jpg')
#8 /var/www/omeka/application/src/Api/Representation/AbstractRepresentation.php(122): Omeka\Api\Representation\MediaRepresentation->thumbnailUrl('square')
#9 /var/www/omeka/application/src/View/Helper/Thumbnail.php(21): Omeka\Api\Representation\AbstractRepresentation->thumbnailDisplayUrl('square')
#10 /var/www/omeka/application/src/Api/Representation/AbstractResourceEntityRepresentation.php(691): Omeka\View\Helper\Thumbnail->__invoke(Object(Omeka\Api\Representation\MediaRepresentation), 'square')
#11 /var/www/omeka/application/view/omeka/admin/media/browse.phtml(61): Omeka\Api\Representation\AbstractResourceEntityRepresentation->linkPretty()
#12 /var/www/omeka/vendor/laminas/laminas-view/src/Renderer/PhpRenderer.php(519): include('/var/www/omeka/...')
#13 /var/www/omeka/vendor/laminas/laminas-view/src/View.php(194): Laminas\View\Renderer\PhpRenderer->render(NULL)
#14 /var/www/omeka/vendor/laminas/laminas-view/src/View.php(222): Laminas\View\View->render(Object(Laminas\View\Model\ViewModel))
#15 /var/www/omeka/vendor/laminas/laminas-view/src/View.php(187): Laminas\View\View->renderChildren(Object(Laminas\View\Model\ViewModel))
#16 /var/www/omeka/vendor/laminas/laminas-mvc/src/View/Http/DefaultRenderingStrategy.php(98): Laminas\View\View->render(Object(Laminas\View\Model\ViewModel))
#17 /var/www/omeka/vendor/laminas/laminas-eventmanager/src/EventManager.php(319): Laminas\Mvc\View\Http\DefaultRenderingStrategy->render(Object(Laminas\Mvc\MvcEvent))
#18 /var/www/omeka/vendor/laminas/laminas-eventmanager/src/EventManager.php(171): Laminas\EventManager\EventManager->triggerListeners(Object(Laminas\Mvc\MvcEvent))
#19 /var/www/omeka/vendor/laminas/laminas-mvc/src/Application.php(360): Laminas\EventManager\EventManager->triggerEvent(Object(Laminas\Mvc\MvcEvent))
#20 /var/www/omeka/vendor/laminas/laminas-mvc/src/Application.php(341): Laminas\Mvc\Application->completeRequest(Object(Laminas\Mvc\MvcEvent))
#21 /var/www/omeka/index.php(21): Laminas\Mvc\Application->run()
#22 {main}

Recommended solution
Just make sure you delete the vendors directory and reinstall before releasing a fix to this. It doesn't look like you're using build / release automation, so I suspect it was just a manual error, and not a caching issue.
Delete vendors, run composer install and rerelease.

We're having the same error. We are unable to update our current instance to Omeka 4  using AnyCloud 3.0.0 Amazon Storage.

While we're waiting for an official fix released from the developer, is there an easy way to manually fix the issue here? In the AwsAdaptor.php file, it says to use the old directory of use League\Flysystem\AwsS3V3\AwsS3V3Adapter; ... do we just change that line to another directory, or is it more systemic than that?

While we're waiting for an official fix released from the developer, is there an easy way to manually fix the issue here? In the AwsAdaptor.php file, it says to use the old directory of use League\Flysystem\AwsS3V3\AwsS3V3Adapter; ... do we just change that line to another directory, or is it more systemic than that?

If you're familiar with composer, you can reinstall the modules dependencies via the command line. This is what I did to get this functional.

Extract the release zip
Delete the vendors folder from the newly extracted directory
Run composer install in that directory.

You should see your vendors directory reappear. Try installing this version of the module instead.

Thank you for your prompt response, I will give that a try.

@GitByrd I'm updating the module package now and will upload it with the correct dependencies.

@GitByrd will you try v3.0.1 and let me know if works now? I ran composer install and included the new vendor folder in the zip file.

I appreciate your quick turn-around in providing a version 3.0.1...however,
unfortunately, once I tried upgrading the module in Omeka, I received this
following error across my site: dev.schafferlibrarycollections.org
Fatal error: Uncaught Error: Class
'ComposerAutoloaderInit66584b4b8f72f95b94c3a6c1a95dafe7' not found in
/home/schaffer/
dev.schafferlibrarycollections.org/modules/AnyCloud/vendor/autoload.php:7
Stack trace: #0 /home/schaffer/
dev.schafferlibrarycollections.org/modules/AnyCloud/Module.php(37):
require() #1 /home/schaffer/
dev.schafferlibrarycollections.org/vendor/laminas/laminas-eventmanager/src/EventManager.php(319):
AnyCloud\Module->onBootstrap(Object(Laminas\Mvc\MvcEvent)) #2
/home/schaffer/
dev.schafferlibrarycollections.org/vendor/laminas/laminas-eventmanager/src/EventManager.php(171):
Laminas\EventManager\EventManager->triggerListeners(Object(Laminas\Mvc\MvcEvent))
#3 /home/schaffer/
dev.schafferlibrarycollections.org/vendor/laminas/laminas-mvc/src/Application.php(154):
Laminas\EventManager\EventManager->triggerEvent(Object(Laminas\Mvc\MvcEvent))
#4 /home/schaffer/
dev.schafferlibrarycollections.org/application/src/Mvc/Application.php(40):
Laminas\Mvc\Application->bootstrap(Array) #5
/home/schaffer/dev.schafferlibrarycoll in
/home/schaffer/dev.schafferlibrarycollections.org/modules/AnyCloud/vendor/autoload.php
http://dev.schafferlibrarycollections.org/modules/AnyCloud/vendor/autoload.php
on
line 7
Jenn G. Byrd
Web Developer
Schaffer Library,
Union College
@.***
518.388.6063
On Mon, Aug 21, 2023 at 5:14 PM Jon Fackrell @.***>
wrote:

@GitByrd https://github.com/GitByrd will you try v3.0.1 and let me know
if works now? I ran composer install and included the new vendor folder
in the zip file.
—
Reply to this email directly, view it on GitHub
https://github.com/HBLL-Collection-Development/omeka-s-any-cloud/issues/39#issuecomment-1687053248,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLHTK2Q4542SLKAJQHOGSLXWPFSPANCNFSM6AAAAAA26XMLLU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

Maybe needs a composer dump autoload in the anycloud directory?

I would try composer dump auto load or even the original suggestion of
deleting the vendor directory and running composer install.
I am curious what version of PHP you’re running - perhaps that might be the
issue.
On Mon, Aug 21, 2023 at 10:36 PM Conlan Patrek Craft <
@.***> wrote:

Maybe needs a composer dump autoload in the anycloud directory?
—
Reply to this email directly, view it on GitHub
https://github.com/HBLL-Collection-Development/omeka-s-any-cloud/issues/39#issuecomment-1687404266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2QZQ6JWLMHLLMPQE5ED3XWQZORANCNFSM6AAAAAA26XMLLU
.
You are receiving this because you commented.Message ID:
@.***
.com>

We are currently running on php 8.0. What I did was delete the entire
AnyCloud module folder on our site and reuploaded the unzipped 3.0.1 folder
via sftp.
On Tue, Aug 22, 2023, 12:52 AM Jon Fackrell @.***>
wrote:

I would try composer dump auto load or even the original suggestion of
deleting the vendor directory and running composer install.
I am curious what version of PHP you’re running - perhaps that might be
the
issue.
On Mon, Aug 21, 2023 at 10:36 PM Conlan Patrek Craft <
@.***> wrote:

Maybe needs a composer dump autoload in the anycloud directory?
—
Reply to this email directly, view it on GitHub
<
https://github.com/HBLL-Collection-Development/omeka-s-any-cloud/issues/39#issuecomment-1687404266>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAW2QZQ6JWLMHLLMPQE5ED3XWQZORANCNFSM6AAAAAA26XMLLU>

.
You are receiving this because you commented.Message ID:
@.***
.com>

—
Reply to this email directly, view it on GitHub
https://github.com/HBLL-Collection-Development/omeka-s-any-cloud/issues/39#issuecomment-1687416694,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APLHTK2E4J5HN77T7DKLLCTXWQ3JZANCNFSM6AAAAAA26XMLLU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

If you'll forgive my blind hand waving.
🤔 I'm also suspicious maybe this error has to do with updating an installed module without uninstalling and reinstalling through the ui. I know Omeka does some interesting things with autoloading module dependencies and I have to wonder from this error if they're maybe caching the autoload classname in the database.
If that was the case, try toggling this module on and off on the modules page. (Install / uninstall, not enable / disable) If this theory has legs I'd suspect that would clear your error.

@jonfackrell I just installed your update and confirmed it's functional. Thanks for the turnaround on this.
@GitByrd I'm not able to reproduce your issue actually. I attempted to test my theory above just now, and the upgrade worked just fine. I do notice that the autoload classname(ComposerAutoloaderInit66584b4b8f72f95b94c3a6c1a95dafe7 ) provided in the error is not the one that's bundled in the 3.0.1 zip (ComposerAutoloaderInit31acc590a62c220067abe45844012b1c), so I feel like that's a hint.

Hmm, I deleted everything and re-uploaded 3.0.1 and I'm still getting this error when I configure the AWS credentials:
/home/schaffer/dev.schafferlibrarycollections.org/vendor/laminas/laminas-form/src/Element.php on line 56

Did the values save or does it not let you save the credentials?
On Tue, Aug 22, 2023 at 4:23 PM CSSSchaffer @.***>
wrote:

Hmm, I deleted everything and re-uploaded 3.0.1 and I'm still getting this
error when I configure the AWS credentials:
/home/schaffer/
dev.schafferlibrarycollections.org/vendor/laminas/laminas-form/src/Element.php
on line 56
—
Reply to this email directly, view it on GitHub
https://github.com/HBLL-Collection-Development/omeka-s-any-cloud/issues/39#issuecomment-1689005822,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2QZTB7VBCDFGTDC3ODSLXWUWNVANCNFSM6AAAAAA26XMLLU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

@jonfackrell The values saved.

Ok, I’ll take a look and see if I can reproduce that error.
On Tue, Aug 22, 2023 at 5:11 PM GitByrd @.***> wrote:

@jonfackrell https://github.com/jonfackrell The values saved.
—
Reply to this email directly, view it on GitHub
https://github.com/HBLL-Collection-Development/omeka-s-any-cloud/issues/39#issuecomment-1689040954,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW2QZVUFSJIWKKX7IFRHU3XWU4D5ANCNFSM6AAAAAA26XMLLU
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

@jonfackrell the good news is that the module actually seems to be working. I refreshed that page with the error and I got the green "this module has been successfully configured" and all our images seem to be showing up correctly on the site.

This appears to be resolved. Thank you @jonfackrell


Question re twitter

Hi this looks amazing about to try and and get it running. Can I ask what level of  Twatter paid account is needed.
And any place to have discussions on this project
Thanks

hi @mynumu , thank you for raising the question.

Can I ask what level of Twatter paid account is needed.

From the current Twitter/X's API plan https://developer.x.com/en , to get it working, the minimal needs is a Basic plan (as the Free plan is write-only), but I still believe that's too expensive compared with other products.

And any place to have discussions on this project

Currently we discuss issues/ideas for opening a new issue, feel free to open a new one for other topics, cheers!

Hey thanks for the reply..yes it’s a rip off price 😄……i will see if I can access your cloud service via VPN as I’m in the eu…unless you have a way to access it directly via login and not the app stores as would love to test it.


Feature Requests

Thanks for the script as this saved me a lot of time! There are two features that I would like to see added:

Built-in support for Windows VMs that contain TPMs. Currently, you have to manually rename the image files.
Built-in support for non-img image files (i.e. qcow2)

Thanks!
Jon

Hi @servebeer.
I currently don't own any Unraid servers, so I don't have the option of testing the script if I make any changes.
The modification to rename files is quite simple, so I'll add it as soon as I have a moment.
On the other hand, the modification to manage qcow2 images is perhaps a little more complex.
I have no idea whether the restoration process is the same for qcow2 images.
The simplest thing would be for you to modify the condition in the script to add, accept .qcow2 and if your restore works well, then I'll add this possibility to the script.
https://github.com/Emilien-Lambert/Unraid-VM-Backup-Plugin-Restoration-Script/blob/c88eee15866a5d8cf8b36372f8f2878adf474ece/vm_backup_restoration.sh#L107

Thanks for the quick response! I have verified that simply changing .img to .qcow2 works in my environment.v/rJonOn Aug 14, 2023, at 14:08, Emilien Lambert @.***> wrote:
Hi @servebeer.
I currently don't own any Unraid servers, so I don't have the option of testing the script if I make any changes.
The modification to rename files is quite simple, so I'll add it as soon as I have a moment.
On the other hand, the modification to manage qcow2 images is perhaps a little more complex.
I have no idea whether the restoration process is the same for qcow2 images.
The simplest thing would be for you to modify the condition in the script to add, accept .qcow2 and if your restore works well, then I'll add this possibility to the script.
https://github.com/Emilien-Lambert/Unraid-VM-Backup-Plugin-Restoration-Script/blob/c88eee15866a5d8cf8b36372f8f2878adf474ece/vm_backup_restoration.sh#L107
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

I've added the 2 improvements, but I can't test it.
Please try the script from this branch:
feature-qcow2
If you confirm that it restores "-tpm" files without errors and that it works correctly with ".qcow2" files, I'll put the improvement on the main branch.

Hi @servebeer did you have time to try the modification I made for you?

@Emilien-Lambert , sorry for the delay. I have been battling AT&T over Internet issues recently. They are supposed to come on-prem today and fix it. If so, I will look into this tomorrow and let you know how it works out.

I believe that it is now working. Here are the latest logs...
2023-09-10 04:33:48 information: skip_vm_shutdown is false and use_snapshots is 1. skipping vm shutdown procedure. OpenManage is shut off. can_backup_vm set to y.
2023-09-10 04:33:48 information: actually_copy_files is 1.
2023-09-10 04:33:48 information: can_backup_vm flag is y. starting backup of OpenManage configuration, nvram, and vdisk(s).
2023-09-10 04:33:48 information: copy of OpenManage.xml to /mnt/user/vmbackup/OpenManage/20230910_0300_OpenManage.xml complete.
2023-09-10 04:33:48 information: OpenManage does not appear to have an nvram file. skipping.
2023-09-10 04:33:48 information: unable to perform snapshot for disk /mnt/user/domains/OpenManage/20230730_0300_openmanage_enterprise.qcow2 on OpenManage. falling back to traditional backup. use_snapshots is 1. vm_state is shut off. vdisk_type is qcow2.
2023-09-10 04:39:37 information: copy of /mnt/user/domains/OpenManage/20230730_0300_openmanage_enterprise.qcow2 to /mnt/user/vmbackup/OpenManage/20230910_0300_20230730_0300_openmanage_enterprise.qcow2.zst complete.
2023-09-10 04:39:37 information: backup of /mnt/user/domains/OpenManage/20230730_0300_openmanage_enterprise.qcow2 vdisk to /mnt/user/vmbackup/OpenManage/20230910_0300_20230730_0300_openmanage_enterprise.qcow2.zst complete.
2023-09-10 04:39:37 information: beginning copy of extra files in path: /mnt/user/domains/OpenManage for VM OpenManage.
2023-09-10 04:39:37 information: copy of backup of /mnt/user/domains/OpenManage//20230730_0300_OpenManage.xml file to /mnt/user/vmbackup/OpenManage//20230910_0300_20230730_0300_OpenManage.xml starting.
2023-09-10 04:39:37 information: copy of /mnt/user/domains/OpenManage//20230730_0300_OpenManage.xml to /mnt/user/vmbackup/OpenManage//20230910_0300_20230730_0300_OpenManage.xml complete.
2023-09-10 04:39:37 information: /mnt/user/domains/OpenManage/20230730_0300_openmanage_enterprise.qcow2 on OpenManage is a vdisk. skipping file.
2023-09-10 04:39:37 information: the extensions of the vdisks that were backed up are qcow2.
2023-09-10 04:39:37 information: vm_state is shut off. vm_original_state is shut off. not starting OpenManage.
2023-09-10 04:39:37 information: backup of OpenManage to /mnt/user/vmbackup/OpenManage completed.
2023-09-10 04:39:37 information: cleaning out backups older than 180 days in location ONLY if newer files exist in /mnt/user/vmbackup/OpenManage/
2023-09-10 04:39:37 information: did not find any config files to remove.
2023-09-10 04:39:38 information: did not find any nvram files to remove.
2023-09-10 04:39:38 information: did not find any vdisk image files to remove.
2023-09-10 04:39:38 information: did not find any vm log files to remove.
2023-09-10 04:39:38 information: cleaning out backups over 2 in location /mnt/user/vmbackup/OpenManage/
2023-09-10 04:39:38 information: removed '/mnt/user/vmbackup/OpenManage/20230903_0300_20230730_0300_OpenManage.xml' config file.
2023-09-10 04:39:38 information: removed '/mnt/user/vmbackup/OpenManage/20230903_0300_OpenManage.xml' config file.
2023-09-10 04:39:38 information: did not find any nvram files to remove.
2023-09-10 04:39:39 information: removed '/mnt/user/vmbackup/OpenManage/20230827_0300_20230730_0300_openmanage_enterprise.qcow2.zst' vdisk image file.
2023-09-10 04:39:39 information: removed '/mnt/user/vmbackup/OpenManage/20230827_0300_unraid-vmbackup.log' vm log file.

Uh, what are the logs for? Because my script doesn't write those kind of logs.
When you run the script, does it finish correctly, with no errors?

I think I have. In fact, I'm not the author of the plugin that lets you create backups from the Unraid interface. In fact, the person(s) who made the backup plugin created the tools that allow you to back up, but not to restore the backup. (No idea why this wasn't done.) Anyway, the normal way to restore a backup is to execute a number of commands and move, rename etc, the backup files manualy.
I simply created a script that automates this. Now, it seems that your backup isn't working for a configuration reason unknown to me.
If you didn't get an error log in the terminal or you ran ./vm_backup_restoration.sh
This means that the backup files have been correctly moved. Now if the VM etc doesn't start, the problem is probably with the plugin itself.
To do this, I suggest you ask your question in the forum dedicated to the plugin. The people in charge of the plugin will certainly have some solutions to suggest, concerning your configuration with .qcow2 files. Here

Thanks for the follow-up. I was afraid that I had confused two different things :-( As soon as I get back home (I am traveling on business right now), I will look at this some more.
V/r
Jon

On Sep 19, 2023, at 11:36, Emilien Lambert @.***> wrote:
I think I have. In fact, I'm not the author of the plugin that lets you create backups from the Unraid interface. In fact, the person(s) who made the backup plugin created the tools that allow you to back up, but not to restore the backup. (No idea why this wasn't done.) Anyway, the normal way to restore a backup is to execute a number of commands and move, rename etc, the backup files manualy.
I simply created a script that automates this. Now, it seems that your backup isn't working for a configuration reason unknown to me.
If you didn't get an error log in the terminal or you ran ./vm_backup_restoration.sh https://github.com/Emilien-Lambert/Unraid-VM-Backup-Plugin-Restoration-Script/blob/main/vm_backup_restoration.sh
This means that the backup files have been correctly moved. Now if the VM etc doesn't start, the problem is probably with the plugin itself.
To do this, I suggest you ask your question in the forum dedicated to the plugin. The people in charge of the plugin will certainly have some solutions to suggest, concerning your configuration with .qcow2 files. Here https://forums.unraid.net/topic/86303-vm-backup-plugin/page/17/#comment-1277331
—
Reply to this email directly, view it on GitHub https://github.com/Emilien-Lambert/Unraid-VM-Backup-Plugin-Restoration-Script/issues/6#issuecomment-1726054120, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACA6WJPD4IL6BTEJNPREWODX3HCZ7ANCNFSM6AAAAAA3QA7V24.
You are receiving this because you were mentioned.


Small change in migration doc

Change Summary
Small change to migration doc, clean up table with field types.
Checklist

[X] The pull request title is a good summary of the changes - it will be used in the changelog
[X] Unit tests for the changes exist
[X] Tests pass on CI and coverage remains at 100%
[X] Documentation reflects the changes where applicable
[X] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @Kludex

Please review

Is duplicated by https://github.com/pydantic/pydantic/pull/6676


Update dependencies

Update:

eslint
axios
axios-mock-adapter

Coverage remained the same at 100.0% when pulling eb43de0ae34a731eaa2bb325181159d280b53caa on update-deps into 9622f974955795f26ad7ae45bfabaa18c25a59e5 on master.


Drop feature support in DeltaTable API

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description

This PR adds drop feature support in the DeltaTable API  for both scala and python APIs.
How was this patch tested?

Added UTs.
Does this PR introduce any user-facing changes?

Yes. See description.

Could we add "[Spark]" to the description and also specify that this is for Spark Classic in the title and description as well?


Incorrect filename after uploading to (Linode) S3 disk

Package
filament/forms
Package Version
v2.11.12
Laravel Version
v9.11.0
Livewire Version
v2.10.5
PHP Version
PHP 8.1.5
Bug description
Using the FileUpload component, with an S3 disk (configured for Linode Object Storage), the path stored in the database by Forms is different to that for the uploaded object found at Linode.
I have tried various things e.g. setting visibility to public (but noting this is default, removed it below).
Jetstream's profile photo disk is the same disk, and works fine which rules out a number of issues. This appears to be a FileUpload bug.
FileUpload::make('photo_path')
                        ->image()
                        ->directory('photos'),

Steps to reproduce

Create a form with a FormUpload component.
Set the (default) disk to be an S3 (might be a Linode S3 specific) disk
Upload file and save.
File cannot be found at the location saved by Forms.

Disk config options are as follows (in my case verified by Jetstream working as expected):
'linode' => [
            'driver' => 's3',
            'key' => env('LINODE_KEY'),
            'secret' => env('LINODE_SECRET'),
            'endpoint' => env('LINODE_ENDPOINT'),
            'region' => env('LINODE_REGION'),
            'bucket' => env('LINODE_BUCKET'),
        ],

Relevant log output
Browser finds a 403 because the object doesn't exist and listing is not allowed.
Inspection of the bucket sees a new object with the right content, but a different name to that provided and saved by Forms.

@kurucu ->preserveFilenames()?

I'm not sure that's it, I don't want to keep the users file name.
The upload seems to generate one random filename, and then somewhere along the route another one is generated and stored to the database?

I don't think it's Filament's responsibility to ensure compatibility with every single possible S3-"compatible" filesystem, and this is very likely to actually be a Livewire issue rather than Filament.
We don't have the resources to purchase storage on a platform for testing purposes, like Linode. If you'd like to see this fixed, you're gonna need to do some debugging yourself. Visit the BaseFileUpload class and check out the code that stores the file. Is the filename correct in TemporaryFileUpload? Is it returned correctly from the store() method?

ok @danharrin, I'll see what I can do!

OK
It has nothing to do with Linode, S3 or the disk type at all. Moving to from local to Linode, I invalidated (staging) file paths in the DB. I didn't think this would be an issue, but it was the root of the problem.
There's now an invalid path in the db. I visit the edit form, where Filament Forms is, and it just says "upload a file" (rather than showing one). Seems fine, so I click a new file hit upload and all seems good until I have my mismatched filenames.
Except I now see that all I'm getting is the same, invalid filename over and over. It's not generating two and storing a random one, it's just the same old one.
Looking at the network inspector, Livewire thinks there's a valid file. Even though file pond shows nothing, and allows me to upload a new file as if from scratch, it appears to be appending that to the old, invalid file. So I now have an array of files, except it's a single-file uploader. So the first (old one) gets stored and not the new one. I think.
Setting the path to null in the database, everything works as it should, no matter what filesystem I use.
Now it is an edge case. But it appears to be a Filament issue - in combination with Filepond - that when a "new" file is uploaded for a single file upload, on top of an incorrect old file, the old one gets persisted instead of the new one because it just takes the first in the array (filepond didn't know it was invalid, found nothing so showed an upload screen, and then Filament/Livewire saw a new file get uploaded and just appended it rather than replacing it).
Is that enough to get you rolling? I could try to look further, but I will be much slower and worse than you guys!

So it's a duplicate of #2419 ?

🤦♂ Yep, it's a duplicate of #2419

No worries :)

Fixed by #2487.


Tests for JSON and Text with returnRawBody

Thought I'd help out with dlau/koa-body #113 since I need raw body access in the project I'm working on and they're waiting for tests
You should be able to merge this here, then it'll update the base PR and @MarkHerhold can merge your original PR

This looks good. If the original author, @thuitaw does not merge this in, I can manually add the tests.

Ok, no response so far. @zevisert  do you want me to just manually add the changes?

Feel free. I'm not doing anything right now, would it help if I send it as a PR on your master?

That would be so much better. Thanks @zevisert


Pick contracts from local (contractDirectory) and from Remote (contractDependency) at the same time

Question
I am implementing an application that needs to verify several contracts, some of them are defined inside the application itself (under src/test/contracts) and other are defined in an external project and are accessible by the generated jar. Is there a way that I can configure the maven plugin spring-cloud-contract-maven-plugin to get all contracts from both sources at the same time and treat them like if they were coming from the same. (define contractDirectory and contractDependency in the configuration section at the same time)

You can:

create 2 maven profiles and run the build twice
you can first download and unzip the stubs, put them into some folder, strip those that you don't need, copy your src/test/resources/contracts there too and then in the contract tests point to that folder

Thanks for the help. Your approaches are valid as solutions, although finally we decided to include a task to move all contracts to the same place and avoid the problem.


Deposit of NEAR issue

The deposit UI of NEAR doesn't display the correct balance. It only displays the native account balance, but doesn't take into account the balance of wrap.near token. Ideally we should sum the two balances together and present it to a user.
Once user selects the amount, figure out whether some part of the amount has to be wrapped first before deposit.

Closing. Duplicate of #228.


chore: bump version to 0.11.0

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/about.md
100
100
100
link
:white_check_mark:

website/docs/getting_started/dotnet_example.md
81
100
54
link
:white_check_mark:

website/docs/getting_started/installation.md
97
100
100
link
:white_check_mark:

website/docs/reference/R-setup.md
85
100
100
link
:white_check_mark:

website/docs/reference/cyber.md
92
100
88
link
:white_check_mark:

website/docs/reference/docker.md
87
100
88
link
:white_check_mark:

website/docs/reference/dotnet-setup.md
91
100
67
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx


fails to be be launched

System Configuration
Please complete Your Configuration detail below. Refer to the BKC at Configuration.

Version
Your Configuration

Operating System
Ubuntu 16.04.1 LTS

Kernel
4.4.0-31-generic

Backend
video4linux

ROS
kinetic

ROS RealSense
1.6.0

librealsense
1.11.0

Camera Type-Firmware
Name: Intel RealSense ZR300, Camera FW: <IP_ADDRESS>, Adapter FW: <IP_ADDRESS>

Expected Behavior
launched
Actual Behavior
https://gist.github.com/robotpilot/0328100922b33df481c964282d3ab721
Steps to Reproduce
I try to find the Depth camera manager for ZR300 for firmware update, but I can't.

@robotpilot It looks like your firmware is old; see https://github.com/IntelRealSense/librealsense/#compatible-devices
I would direct you to the contact that supplied the camera for updated firmware.

RealSense ZR300
Camera Firmware <IP_ADDRESS> and up
USB Adapter Board Firmware <IP_ADDRESS> and up
Motion Module Firmware <IP_ADDRESS> and up

Thanks, @mdhorn
My email address is "pyo at robotis.com".

The problem you reported was a known error using that old firmware.
Once you have updated firmware and the camera is calibrated, please open a new Issue if you continue to have issues.
thank you.


'LeafletMap' object has no attribute 'base_url' in JupyterLab

It seems that inferring the base URL is failing for me in JupyterLab 3.0.12.
The .window_url of my map is 'http://localhost:8888/lab/workspaces/auto-s/tree/nb/leaflet.ipynb', which doesn't match the .endswith("lab") logic trying to identify JupyterLab. Maybe the URL scheme has changed recently?
I'm imagine missing something here, but is the goal of the "find the base URL" logic to figure out the URL of the Jupyter server? In that case, would something like
url = urllib.parse.urlparse(m.window_url)
self.base_url = f"{url.scheme}://{url.netloc}"

work for all the cases in general?

Following @gjoseph92 's suggestion, I changed the relevant code in the xarray_leaflet.py and it is now finally working in my Jupyterlab (3.0.16).
Thank you @gjoseph92. Saved my day trying to figure out what went wrong in my conda environment.

I'm imagine missing something here, but is the goal of the "find the base URL" logic to figure out the URL of the Jupyter server? In that case, would something like
url = urllib.parse.urlparse(m.window_url)
self.base_url = f"{url.scheme}://{url.netloc}"

work for all the cases in general?

Sorry for not replying earlier @gjoseph92, in your particular case self.base_url would be http://localhost:8888 if I use your logic. What we need is the Jupyter Server base URL, because the tiles are served by the Server. So your suggestion wouldn't work when used through Binder for instance, because it adds a prefix to the URL.
The current implementation is wrong, but I couldn't come up with an acceptable solution yet. If you have ideas, please don't hesitate to share.

Correct, what I posted doesn't work in generality (particularly Binder). For stackstac, I ended up going with this regex which works fine, though I don't love that it's specific to lab/notebook/voila. Seems like the most correct approach would be to pull it from the NotebookApp.base_config option, or from the frontend.
Also @davidbrochart you might be interested in stackstac.show. I took a bit of inspiration from xarray-leaflet, though the implementation is more optimized for concurrency with dask. At some point I'd like to pull this into a separate package and maybe combine with xarray-leaflet, but that's not realistic until there's some package to put common xarray geospatial operations in (xref https://github.com/gjoseph92/stackstac/issues/50, maybe geoxarray someday)—currently, there's too much shared code between stackstac.show and core stackstac to really pull it out.

Thanks for sharing your work on stackstac, it looks interesting!
Looking at the limitations about visualization, I can see that "resolution doesn’t change as you zoom in or out". I'm not sure what this means, isn't the data somehow aggregated, as it is in xarray-leaflet?

Ah no, all I meant is that

zooming in and out will not load underlying data at different resolutions. Assets will be loaded at whatever resolution you initially got from stack. If your array is large and high-resolution, zooming out could trigger very slow (and expensive) computations.
https://stackstac.readthedocs.io/en/latest/api/main.html#visualization

This is a limitation of xarray-leaflet as well. It should be possible to get around with some clever dask graph rewriting, but I won't get to that for a while.

See #45


FileNotFoundError on Dashboard when deployed on Heroku

(Please take the time and describe the problem you're having before you propose a solution.)
What I'm trying to achieve
I wish to deploy my Saleor store on Heroku and load data from a DB dump with python manage.py loaddata db.json and that it works fine showing the products and the associated images.
Steps to reproduce the problem

Deploy to Heroku with Git on the command line
Load data from a database dump
View store but it shows placeholder images

What I expected to happen

Deploy to Heroku with Git on the command line
Load data from a database dump
View store showing product catalog with the right images

What happened instead/how it failed

After loading database dump, images do not show despite python manage.py collectstatic shows that the images are there but they are probably not being referenced right.

When I attempt to edit the products to change images on the dashboard, I get the following error:

The settings for the STATIC and Whitenoise look as follows:
STATIC_ROOT = os.path.join(PROJECT_ROOT, 'static')
STATIC_URL = '/static/'
STATICFILES_DIRS = [
    ('assets', os.path.join(PROJECT_ROOT, 'saleor', 'static', 'assets')),
    ('images', os.path.join(PROJECT_ROOT, 'saleor', 'static', 'images')),
    ('dashboard', os.path.join(PROJECT_ROOT, 'saleor', 'static', 'dashboard'))]
STATICFILES_FINDERS = [
    'django.contrib.staticfiles.finders.FileSystemFinder',
    'django.contrib.staticfiles.finders.AppDirectoriesFinder']

MIDDLEWARE = [
    'django.contrib.sessions.middleware.SessionMiddleware',
    'django.middleware.common.CommonMiddleware',
    'django.middleware.csrf.CsrfViewMiddleware',
    'django.contrib.auth.middleware.AuthenticationMiddleware',
    'django.contrib.messages.middleware.MessageMiddleware',
    'django.middleware.locale.LocaleMiddleware',
    'django_babel.middleware.LocaleMiddleware',
    'saleor.core.middleware.discounts',
    'saleor.core.middleware.google_analytics',
    'saleor.core.middleware.country',
    'saleor.core.middleware.currency',
    'saleor.core.middleware.site',
    'whitenoise.middleware.WhiteNoiseMiddleware',
    'social_django.middleware.SocialAuthExceptionMiddleware',
    'impersonate.middleware.ImpersonateMiddleware']

INSTALLED_APPS = [
    # External apps that need to go before django's
    'storages',

    # Django modules
    'django.contrib.contenttypes',
    'django.contrib.sessions',
    'django.contrib.messages',
    'django.contrib.sitemaps',
    'django.contrib.sites',
    'django.contrib.staticfiles',
    'django.contrib.auth',
    'django.contrib.postgres',
    'django.forms',

    # Local apps
    'saleor.account',
    'saleor.discount',
    'saleor.product',
    'saleor.cart',
    'saleor.checkout',
    'saleor.core',
    'saleor.graphql',
    'saleor.order.OrderAppConfig',
    'saleor.dashboard',
    'saleor.shipping',
    'saleor.search',
    'saleor.site',
    'saleor.data_feeds',

    # External apps
    'versatileimagefield',
    'django_babel',
    'bootstrap4',
    'django_fsm',
    'django_prices',
    'django_prices_openexchangerates',
    'graphene_django',
    'mptt',
    'payments',
    'webpack_loader',
    'social_django',
    'django_countries',
    'django_filters',
    'django_celery_results',
    'impersonate',
    'phonenumber_field']

Is there something I am missing? A WhiteNoise setting? Wrong way to load static files to Heroku due to differences between STATIC settings in Saleor and those in Whitenoise? What might I be doing wrong? Please help.

As far as I remember Whitenoise is not suitable for serving media files. For security and performance reasons, it scans files only at the startup, can’t really serve user-generated content.
However Saleor works out of the box with AWS S3, we have integration guide for It which I’d strongly recommend to pair with Heroku App.

Saleor does work with S3 but requires to disable the image creation on demand from versatile otherwise it's slow and will spam requests to S3 (which means it may cost you a few bucks).
I'm not quite sure, if someone could verify that... But I think versatile does not upload to the S3 media bucket at least Saleor does not upload to the S3 bucket when we disable the on demand creation and upload images from the dashboard.
Which means Versatile requires a manual warm up which is easily implementable from Saleor side.
Please tell me if I'm wrong. At least if was the issues I ran into with S3 on the January release of Saleor. Then I did some changes to the Saleor code to warm up on image upload which uploads to S3, everything is awesome now.

@NyanKiyoshi
You’re right, there’s no prewarmer for Versatileimagefield in Saleor, so disabling on demand image creation will stop thumbnails/crops from being created.
I think images should be created on demand only if ‘not DEBUG’.
We should address this problem soon.

Thanks guys! @NyanKiyoshi I am going to try and copy the folder to Heroku. Fingers crossed I can actually do that.. I do not have much experience with S3 so I will have to invest more time to learn about how to get that working, especially with the Versatile Images.

@Pacu2 do you have a link to the detailed integration guide for AWS? The documentation only has this:
Set the following environment variables to use S3 to store and serve media files:

`AWS_ACCESS_KEY_ID`
Your AWS access key.
`AWS_SECRET_ACCESS_KEY`
Your AWS secret access key.
`AWS_MEDIA_BUCKET_NAME`
The S3 bucket name to use for media files.
By default static files (such as CSS and JS files required to display your pages) will be served by the application server.

If you intend to use S3 for your static files as well, set an additional environment variable:

`AWS_STORAGE_BUCKET_NAME`
The S3 bucket name to use for static files.

@raybesiga That's the one I was talking about, Saleor wise, that's all you need.
Apart from that, you'll need to sign up and create buckets on AWS S3

Thanks @Pacu2. Do I then move the stuff in my media folder into the bucket? Also, that said, I cannot edit/delete the products due to the error I am having. Do you suggest that I delete the Heroku app and wipe my database? What do you recommend I do to get things working again?

How do I link the product images in a bucket to the actual products in the Saleor backend dashboard?

Copy your media files to s3 bucket, add appropriate settings in Saleor. Apart from that, remember about setting proper CORS policy on the buckets and permissions.
Answering second question, your files should have same structure as on your local instance.
If you want to move your static files to AWS S3 as well, you'll need STATIC_URL env variable set, equal to your bucket's url, take a look at https://github.com/mirumee/saleor/blob/master/webpack.config.js#L13-L18

I think this is already resolved


Come up with a name for our testing/development headless pipeline

We need a development/testing pipeline.
Purpose:

Work out publishing system integration tasks & features without impacting production sites
Have a reference of the default installations for our services.
Cross-train engineers on setting up different systems & independently review our services (trying technical documentation & raising issues)

Publishing pipeline components:

CMS: Currently WordPress, have plans to use others
Repo: @cagov/odi-publishing-pantheon (installer)
Children:

@cagov/ca-design-system-gutenberg-blocks
... (there are more, will fill in)
Editor instance:
dev - wipeable sandbox instance - and development versions of plugins and features
live - production - has our sample content & main released versions

dev version needed for building preview feature without negatively impacting production sites

Data models (Need to work on this)
Design system components (repo is @cagov/design-system, main branch is the source)
Microservices - endpoints on FaaS (currently Azure, could be Lambda) to sync API data to github
11ty build (we need this, also preview feature needs this) - projects needs a reference - reference can be the main branch - and new features in development branch which can deploy to appropriate s3 buckets
s3 buckets
optional - CloudFront configs & custom domains. Chad & Chach will go over service documentation & tracking requirements.

Docs: live in wiki in ___ (which repo? currently odi-engineering -- -does odi-publishing need a repo)
Note: odi-publishing is our working name so we can sync up our work.

Done!


Mobile chat has serious bugs

Right now, clicking on the chat icon in the top-right on a xs display causes the chat popup to open. This is problematic, as the pop-up chat does not function on mobile at all, causing issues such as overflow and text below the visible area.
However, the full chat functions perfectly for mobile.
I suggest that when in a xs view, the chat bubble becomes a link to /chats

chat popup works fine for me on mobile at pichalite.com
What issues are you seeing? screenshots?

This is not the best experience on mobile. Had to really guide my community users to get them to be able to use this.
A better experience on mobile would be to lock the scrolling, and have it extend to all edges of the screen. Possibly still showing the menu, but any navigation would need to close or minimize the chat. Also, a link to go to the all chats page, opening this conversation might also be good. If this is something you would be interested in, I can make a PR.

@pichalite I'd checkout my solution in my pull requests. There's a couple of other issues your changes don't fix:

The chatbox is not at the bottom, giving a weird feeling of empty space:

There is also the issue that the chatbox doesn't expand as you type multiple lines of text in. My changes take account of this and expand the textarea as multiple lines are added.

Plus, the border radius at the top looks funky when going full screen

I will take a look at these. Not sure if I want to add another library just to resize textbox.

@pichalite Well, it's a very small library. NodeBB actually already has it loaded, but it's an older version that doesn't seem to work on this. That being said, it's lazy loaded and small. Probably should have minified it though

@pichalite (Deeply sorry for never replying, I now have github set up to email me when I get a reply! Issue seems fixed, though.)


Fix compilation of xtensa_hifi activations kernel

Update the activations kernel to latest reference implementation.
Use the new TfLiteEvalTensor API.
This is an incremental change towards fixing Issue #43912.
Issue #43912

@pnikam-cad  Can you please resolve conflicts? Thanks!

We are switched over to using the common xtensa directory and the xtensa_hifi directory was deleted with https://github.com/tensorflow/tensorflow/pull/47096.
This PR can be closed.


Demo app

[x] Load and save Swift files
[ ] At the bottom form to add messages

It's in a separate repo: https://github.com/mchakravarty/CodeEditorDemo


No Results depends on Recommendations

src/components/searchresultpage/srpLaptop/Noresult.jsx
line 85
a recommend carousel is called without checking if recommend is enabled in featuresConfig.js

possible duplicated of https://github.com/algolia/algolia-react-boilerplate/issues/371


Turn :: into .. code::

Fixes conversion issues.

Fixes conversion issues.

This is a painful task! thanks for making these changes :)


New Website Logo: Unsplash

Please fill the following out:

Name: Unsplash
Homepage url: https://unsplash.com/
Brand Guidelines/Licensing:
Logo: https://jsbin.com/kofahe/2

<svg class="_2m4hn" version="1.1" viewBox="0 0 32 32" aria-labelledby="unsplash-home" aria-hidden="false"><title id="unsplash-home">Unsplash Home</title><path d="M10 9V0h12v9H10zm12 5h10v18H0V14h10v9h12v-9z"></path></svg>

Example:
Name: Microsoft
Homepage url: https://microsoft.com
Brand Guidelines/Licensing: https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/logo.aspx
Logo: https://news.microsoft.com/microsoft-news-center-photos/msft_logo_rgb_c-gray/

Hey folks -we're looking at a new website and it's likely that the friends of TypeScript page isn't going to make it to the new site. This is mainly because close to everyone is a friend of TypeScript now and listing folks kinda feels a bit un-inclusive to everyone else.
So I'm going to close this issue - thanks for posting to apply


Entering text into a keyboard when viewing a project in fullscreen kicks you out of fullscreen

Describe the bug
Entering text into keyboard when viewing a project in fullscreen kicks you out of fullscreen.
To Reproduce
Steps to reproduce the behaviour:

View a project
Enter fullscreen
Click on a keyboard
Enter text
Get kicked out of fullscreen

This can be avoided by viewing another subcircuit first.
Expected behaviour
Entering text in a keyboard does not kick you out of fullscreen whether you've viewed other subcircuits or not.
Device Information [optional]:

OS: Windows 10
Browser: Chrome

Are you working on this issue? No

Can I work on this issue?

I would like to work on this issue.


fix issue with store_code in URL

@6ui11em,
I've released v1.1.0 yesterday, does this solve your issues?
Have a good weekend


Run encoder on batches

Allows the encoder to process multiple images in batches when doing variational_mode, which is required for doing inference on multiple images of simulated blends simultaneously.
If I tried to do this before on 10k galsim blends, the GPU would run out of memory.

Hi @dereklhansen - I took your suggestion on how to improve the encoder to process multiple images in this PR. I'm merging now since I know you are in vacation, but if at some point you have additional suggestions on this PR and you could give me a quick review that would be great. Thanks!

Thanks!


Update PyTorch THPVariable_Wrap to use const ref

What does this PR do? Please describe:
This comes from a change from PyTorch https://github.com/pytorch/pytorch/pull/138880 in which the signature of THPVariable_Wrap changes to
TORCH_PYTHON_API PyObject * THPVariable_Wrap(const at::TensorBase& var);

A build failure happens when importing the change to fbcode D65031075 for one project that is using fairseq2
Does your PR introduce any breaking changes? If yes, please list them:
This makes fairseq2 compatible with latest PyTorch, so I don't think there is any breaking change here.
Check list:

[ ] Was the content of this PR discussed and approved via a GitHub issue? (no need for typos or documentation improvements)
[x] Did you read the contributor guideline?
[x] Did you make sure that your PR does only one thing instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (no need for typos, documentation, or minor internal changes)

I think we have a chick-and-egg issue here.  So here is the current interlocking setup:

Some Meta-internal code uses pytorch (latest) and fairseq2 (imported from this repo).  They fails because these twos are not compatible anymore w.r.t THPVariable_Wrap
fairseq2 is open source and it tests against stable PyTorch >= 2.2.0 https://github.com/facebookresearch/fairseq2/blob/main/.github/workflows/ci_build_wheels.yaml#L33-L52.  This is not latest PyTorch.

I think I need to try writing an internal patch instead of waiting for this PR.

I will close this for now as the internal patch works (but brittle).  I'll leave it to fairseq2 maintainers to decide when and how they want to make fairseq2 compatible with PT when it comes to this public function


initial version of lockup custom element

Alaska Airlines Pull Request
Summary:
The initial build of a new auro-lockup custom element.
See demo page: http://auro-lockup.surge.sh/components/auro/lockup
Note: updates to gitignore and npmignore have been ported over to WC-Generator
Type of change:
Please delete options that are not relevant.

[x] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to upgrade to Vite 3? Vite errors due to this plugin

Hi, I'm trying to upgrade Vite to 3.0.1 and this plugin to 3.1.1. When I try to start the dev server, Vite complains about a require() in the plugin:
failed to load config from vite.config.js
error when starting dev server:
Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from<EMAIL_ADDRESS>not supported.
Instead change the require of index.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
at Object.require.extensions.<computed> [as .js] (node_modules/vite/dist/node/chunks/dep-c9998dc6.js:62001:13)
...
error Command failed with exit code 1.

Is there something else I need to do to upgrade to Vite 3?
Thanks!

A bit unfortunate but you can work around this with a dynamic import in vite.config.ts.
export default async () => {
  const reScript = (await import("@jihchi/vite-plugin-rescript")).default;

  return defineConfig({
    ...,
    plugins: [reScript(), ...]
  });
};

I've published a new version: 4.1.0, hope it can fix/mitigate the problem.
Please use following code if you want to keep using require syntax:
const { default: createReScriptPlugin } = require('@jihchi/vite-plugin-rescript');

Thanks, 4.1.0 seems to be working for me.

That fixed it for me too!
Just a note for others: something changed with Vite, and I had to add the port to my config to continue using 3000:
server: { port: 3000 },

Just a note for others: something changed with Vite, and I had to add the port to my config to continue using 3000

If port 3000 is in use (e.g. you already have Vite running in the background somewhere) then Vite will automatically use a different port.

> If port 3000 is in use (e.g. you already have Vite running in the background somewhere) then Vite will automatically use a different port.
For some reason Vite refuses to use port 3000 for me even though the port's open (double-checked with netstat). Specifying it in the config works though, no failure on launch because the port's already in use.


Upgrade Segment snippet to 4.1.0

Previous version was 2.0.9
This unlocks some Segment methods, reset for example.

👋 hello ! Some work here. Do you think it could be merged?

@poteto @mike-north do you think we could merge it?


Enumerable::ENUMERABLE_SIZE

Associated constant for the number of values in this enumerable. If the number exceeds usize::MAX, accessing the constant fails at compile time.
This is useful to create a compact storage to map all the values:
let mut data: [None; MyEnum::ENUMERABLE_SIZE];

I chose name ENUMERABLE_SIZE not SIZE to avoid confusion with possible other meaning of SIZE (for example, for u32 SIZE` could also mean size in bytes).
Follow-up to this PR would be implementing:

Enumerable::enumerable_index to map enumerable value to usize index
Enumerable::enumerable_from_index for the opposite operation

Would you please create a issue about these features? I agree that these features given/proposed in this PR are very useful and sometimes critical, but I have several questions.

For Enumerable::ENUMERABLE_SIZE, can you come up with a better name? I think ENUMERABLE_SIZE is OK and acceptable but I'm also wondering is there a clearer name.
For Enumerable::enumerable_index/Enumerable::enumerable_from_index, maybe we should call them Enumerable::enumerable_until_index and Enumerable::enumerable_from_index? Also I think we should give them default implementations.

Thank you for your contribution! Very happy to see you in this repo again.

I've created issue #26 for this PR.
For Enumerable::enumerable_index and Enumerable::enumerable_from_index, I misunderstood their purpose in my last comment. I'll discuss them in #26.


Need help for improve README without grammar mistakes.

Need help for improve README and other documentations without grammar mistakes.

Hi, I can help you out with that.


Profiler doesn't sort by time

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
The profiler doesn't sort the functions calls by time:

What steps reproduce the problem?

Profile a script
Try to sort by "Total Time"

What is the expected output? What do you see instead?
I would expect the calls to be sorted
Versions

Spyder version: 4.2.0.dev0 b12e8a3bc
Python version: 3.7.6 64-bit
Qt version: 5.12.8
PyQt5 version: 5.12.3
Operating System: Windows 10

Dependencies

# Mandatory:
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.3.0 (OK)
diff_match_patch >=20181111    :  20181111 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.16.1 (OK)
jedi =0.17.1                   :  0.17.1 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  0.9.2 (OK)
paramiko >=2.4.0               :  2.7.1 (OK)
parso =0.7.0                   :  0.7.0 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=1.0                   :  2.5.2 (OK)
pyls >=0.34.0;<1.0.0           :  0.34.1 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.0 (OK)
qtconsole >=4.6.0              :  4.7.4 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.4 (OK)
sphinx >=0.6.6                 :  3.0.4 (OK)
spyder_kernels >=1.9.2;<1.10.0 :  1.10.0.dev0 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  19.0.1 (OK)

# Optional:
cython >=0.21                  :  0.29.21 (OK)
matplotlib >=2.0.0             :  3.2.2 (OK)
numpy >=1.7                    :  1.18.5 (OK)
pandas >=0.13.1                :  1.0.5 (OK)
scipy >=0.17.0                 :  1.5.0 (OK)
sympy >=0.7.3                  :  1.6.1 (OK)

I think this was caused by @juanis2112 changing the symbol for microseconds in 4.1.4.
@juanis2112, please take a look at this one.

Thanks for opening this @impact27.
@ccordoba12  is right, apparently when changing the units I messed up the sorting. I opened a PR to fix it, so hopefully it works. I assigned you both @ccordoba12 and @impact27 as reviewers for it.