fix: redo conversion for multi-arch with s390x

Reapplies the cast from 70b37b16075bfd5af3c4cf9d4373c3bd1a19138f that was removed by 5e84659232096f23e73b18c7753817b4a09b3f0a by accident
In downstream we use this to build TopoLVM for s390x and it should not interfere with other architectures

Another thought, we will be able to build s390x on the multi-platform docker image, but I think it is not a good idea because the build time is already too long, and I assume users who want to use s390x tend to use vendor build binaries.

I support that idea, s390x should not be the default compile target as its user base is extremely limited, even for us, but if someone uses it, its fundamental in their architecture.
Regarding where to add it, im open to add it to the tests, but that will increase the test. In general, on the image build time, I think it has been mentioned before but TopoLVM disables the docker build cache and could be optimized a bit, maybe that is worth targeting?

@jakobmoellerdev
Do you mean you want to add s390x support to our multi-platform build target?
https://github.com/topolvm/topolvm/blob/main/Makefile#L207
I thought that simply adding compilation tests to the main workflow would be sufficient.
We use apt in Dockerfile, the upstream repository may be updated even if we change nothing, so we used --no-cache. But it is ok to add an option to enable caching, IMO.

Sorry, I misunderstood what you said.
I think we should ensure to build the binary but do not have to provide official images for the architectures because they don't use our binaries (I assume they use enterprise-supported binaries).

Check uncommited is showing a failure in lvmd.pb.go but im 99% certain that this is a cache issue since the last k8s version bump PR. @toshipp do you mind taking a look and telling me what to do with that?

I updated protoc version on https://github.com/topolvm/topolvm/pull/910, but I missed updating pkg/lvmd/proto/lvmd.pb.go and pkg/lvmd/proto/lvmd_grpc.pb.go
Could you generate them as follows?
rm pkg/lvmd/proto/lvmd.pb.go
rm pkg/lvmd/proto/lvmd_grpc.pb.go
make generate


Swap Docker registry upload order

Swap the upload order so that newly generated images are uploaded to ghcr.io first, then registry-1.docker.io.

Fixed per #721.


HOPR package

Tracking issue for the readiness of the package.

We started adapting the current status and testing the package itself based on the recent changes in hoprd. What is your preferred way to sync our progress? One big PR?
cc @NumberFour8

Pushed PR for our release #54


Dark theme

Hello, I'm trying to implement a dark theme for my form app that use this awesome ribbon.
I tried using the "ThemeColor = RibbonTheme.Black" property but without success.
Is there a workaround or is it possible to create a custom theme and how? Thank you

I solved it by inheriting the RibbonProfesionalRendererColorTable class.


Synchronization issue with Google Drive

Synchronization is not happening automatically. Probably, on the first time when I create the file. I didn't check. Manually, it works fine.
Since there are many files I was supposed to sync, I signed in using my google cred to Stackedit. Today, I noticed that I can find no file in my google drive that I created using Stackedit (md files). But I can see all the files on Stackedit.io. It says that " Main workspace synced with your Google Drive app data folder. ". Does it mean that all the files are still in my google drive, but I can't search them because they are inside some hidden app folder?

If yes, then how can I disable it? I wanted the files to be in their respective folders only. So they are easy to find, categorize, share with my friends, download etc. Now I need to open Stackedit first where I see a long list of files.

The data is synchronized in a hidden folder, you can not view the file but can see the change of storage in Google Drive > Settings > Manage apps
I found the only way is to connect your stackedit with Google Drive workspace:
Menu > Workspaces > Add a Google Drive workspaces
You should enter the Folder Id or click Choose Folder.

You should enter the Folder Id or click Choose Folder.

I found that if there are already some markdown files in a folder, after setting the folder as a stackedit workspace, existing markdown files will not shown in this workspace. Is this an expected behavior?


Missing / in Azure CLI command to command to create a subscription rule in All-active replication

Hello
It looks like a \ is missing in this command after "mytopic"
az servicebus topic subscription rule create --resource-group myresourcegroup
--namespace mynamespace --topic-name mytopic
--subscription-name replication --name replication
--action-sql-expression "set replication = 1"
--filter-sql-expression "replication IS NULL"
it causes an error and the rule is not created.
marco [ ~ ]$ az servicebus topic subscription rule create --resource-group ara97
--namespace ara97repns01 --topic-name topic01
--subscription-name replication --name replication
--action-sql-expression "set replication = 1"
--filter-sql-expression "replication IS NULL"
the following arguments are required: --subscription-name, --name/-n
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 644f7571-ec3c-b3e1-8a91-af48f6d84a3a
Version Independent ID: b8bdf221-acfc-c2f5-37e4-fb3ad14e0d46
Content: Message replication and cross-region federation - Azure Service Bus - Azure Service Bus
Content Source: articles/service-bus-messaging/service-bus-federation-overview.md
Service: service-bus-messaging
GitHub Login: @spelluru
Microsoft Alias: spelluru

The issue is fixed. The update will go live in a few hours. Thanks @marccamp !!
#please-close

@spelluru
Thank you for your response.

@marccamp
It looks like your issue is resolved since this thread is closed.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion. Thanks!!!


Not really an issue but a request for improvement.

Hi,
It would have been great to have only one column with the current
line number displayed and the others lines numbers relative to
the current one. It would save space and bring two features into one.
Nice work anyway.
Rgds,

Agreed (watching)


Search SDK: Confusing error message in azure .net SDK (Object must implement IConvertible)

(This issue was originally reported via User Voice; Copying it here since it's a bug report, not a feature request.)
Confusing error message in azure .net SDK (Object must implement IConvertible)
When we search with the page size 1000+ and the response content length exceeds Azure response limit of 16MB , we are getting 'Object must implement IConvertible; instead of the actual problem. This error occurs in IndexCleint class SearchAsync method
_indexClient.Documents.SearchAsync(searchText, sp);

Some questions for the person who reported this bug:

How do you know that the response is larger than 16 MB? How are you measuring this?
What HTTP status code is returned with the "Object must implement IConvertible"? Is it 400?

Thank you for your response. It's not 400 , it's  a 200 response. We used fiddler and get all the raw data and saved the content to a file.  It seems like this is not 16MB limitation issue. it seems like serialization issue... here is the inner exception details . Please let us know if you need more information from us.
at System.Convert.ChangeType(Object value, Type conversionType, IFormatProvider provider)
at Newtonsoft.Json.Linq.Extensions.Convert[T,U](T token)
at Microsoft.Azure.Search.Serialization.DocumentConverter.<>c.b__6_0(JToken t)
at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext()    at System.Linq.Buffer1..ctor(IEnumerable1 source)    at System.Linq.Enumerable.ToArray[TSource](IEnumerable1 source)
at Microsoft.Azure.Search.Serialization.DocumentConverter.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.Deserialize[T](JsonReader reader)
at Microsoft.Azure.Search.Serialization.SearchResultConverter2.ReadJson(JsonReader reader, Type objectType, Object existingValue, JsonSerializer serializer)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.DeserializeConvertable(JsonConverter converter, JsonReader reader, Type objectType, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateList(IList list, JsonReader reader, JsonArrayContract contract, JsonProperty containerProperty, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateList(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, Object existingValue, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.SetPropertyValue(JsonProperty property, JsonConverter propertyConverter, JsonContainerContract containerContract, JsonProperty containerProperty, JsonReader reader, Object target)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)    at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)    at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)    at Microsoft.Rest.Serialization.SafeJsonConvert.DeserializeObject[T](String json, JsonSerializerSettings settings)    at Microsoft.Azure.Search.DocumentsOperations.<DoContinueSearchWithHttpMessagesAsync>d__153.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Search.DocumentsOperationsExtensions.d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()    at Alden.FacetSearchBase.SearchBase.<SearchAsync>d__10.MoveNext() in E:\AgileDevelopment\Common\Alden.FacetSearch\Main\Alden.FacetSearchBase\SearchBase.cs:line 228 --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at System.Runtime.CompilerServices.TaskAwaiter1.GetResult()
at Alden.FacetSearchBase.SearchBase.d__7.MoveNext() in E:\AgileDevelopment\Common\Alden.FacetSearch\Main\Alden.FacetSearchBase\SearchBase.cs:line 130

When we set the page size to 1000 and retrieve all the retrievable fields we get this exception. On the other hand if we reduce the number of fields return to 3 or 4 basic fields ,we get a perfect response with no exception.

Thanks for the details. We'll investigate.

@cbaski I have a few follow-up questions.
What is the smallest response payload size for which you can reproduce this issue?
Would you be able to share the Fiddler trace for such a repro? You can email it to me (bruce dot johnston at the usual domain).
Thanks!

Fiddler response content is emailed to your usual domain email. Please let me know , if you need anything else from me.

The fix is now available in the latest preview SDK on NuGet. I'm still working on backporting it to the GA SDK.

The fix is now available in the latest stable SDK on NuGet. Closing this issue.


HOTFIX: fix FAQs

To update "How do I make folders?" answer, now that there are folders.

updated


Config says all supported, but multiply connection not works

Hello!
Please help, some days ago, after montly windows update, RDP wrapper stopped working (not supported message). As usualy, I updated ini file, after that - Fully supported, But multiply connetion does not works.
My termsrv.dll and rdpwrap.ini in attached archive.
Window 10 Pro 2009
RDP ver. 10.0.14393.0
RDP Wrap.zip

https://github.com/Octanium91/rdpwupDownloads/blob/master/rdpwup_8.zip

Thanks, but it did not helped me.
There is solution that helped me:

Put new rdpwrap.ini in the same folder as rdpwinst.exe
Open command line
rdpwinst -u -k
rdpwinst -i


Fix<EMAIL_ADDRESS>deprecation warning

There is npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs message while installing v8-profiler-next package.
The warning originates from @xprofiler/node-pre-gyp package, because it still uses<EMAIL_ADDRESS>If we update node-gyp to v9 this warning will be fixed. The main question is if @xprofiler/node-pre-gyp supports node-gyp v9.

Thank you for your feedback, I will fix this :)

Thank you for updating node-gyp package in @xprofiler/node-pre-gyp 🎉  But, unfortunately, the warning didn't go away, it just changed to:
npm WARN deprecated<EMAIL_ADDRESS>This functionality has been moved to @npmcli/fs 😢
It turned out that to fix the warning node-gyp package needs to be updated to the latest version -- v9.4.0 (currently it's pinned to v9.3.1 in @xprofiler/node-pre-gyp). node-gyp v9.4.0 updates make-fetch-happen to v11.0.3 (https://github.com/nodejs/node-gyp/commit/02480f6b6894a6bb81dd3e1365bc4df6d5336f7c) which updates cacache to v^17.0.0 (https://github.com/npm/make-fetch-happen/releases/tag/v11.0.0) which finally replaces @npmcli/move-file with @npmcli/fs (https://github.com/npm/cacache/commit/4a7382f5e6c72c59587d45167346c1b6e81a3cde). There are breaking changes in make-fetch-happen v11.0.0 though (e.g. the drop of support for Node.js < v14.17.0 (the previous version still supports v12).
Do you think you can update node-gyp to v9.4.0?

Consider switching back to the official node-pre-gyp; I need to check for compatibility.
Actually, the reason for using @xprofiler/node-pre-gyp before was to ensure compatibility with pre-built binaries for node-v8.x. But it seems that it's no longer necessary now, as pre-built binaries are provided starting from v12.x.


updates

added category and accounts urls
added the templates for login , logged out, e.t.c

update


Boot Stage 3

I've been trying to create a flashed program that loads and boots an ELF file off of an SD card.
I've been able to write linker scripts to split the flash memory into a boot2+3 partition and an external program partition, load all segments (both flash and RAM), and even call a dynamically loaded function, but as soon as I try to do anything from within the loaded code (eg: puts or even call a function from a provided object's vtable) I get a hard fault. If I instead jump to the start of .text (boot2 of the loaded file) it ends up going back to my boot3's main. If I instead jump to the reset vector of the loaded file, I get a hard fault when the SDK tries to execute it's list of pre-main initialization functions.
I can try to provide a repository later today, but I'm wondering if anyone's tried this before and might know something I'm missing.

I ran into that repository before and couldn't manage to adapt it to my use case, but it's always worth another shot.

I finally figured out the problem. If flash_range_erase is not called before flash_range_program, then flash_range_program will silently fail, leaving whatever preexisting data where it was. At some point I commented out my call to flash_range_erase because it was taking a while and I wasn't recompiling the program I was trying to launch, but forgot to uncomment it since I didn't realize invalidating the flash sector was necessary to reprogram pages within it.
Maybe the rp2040 datasheet should be updated with that information? I don't think it's stated anywhere.


Added reference to old DocumentNode within NodeRemovedEvent (Resolves #1181)

Added reference to old DocumentNode within NodeRemovedEvent (Resolves #1181)
This change was made so that editor reactions can base their decisions on content in a removed node.
This addition isn't ideal because we're passing a reference to a now-deleted, mutable DocumentNode, but it's unclear what else we should do. We'll probably revisit issues like this later.

@matthew-carroll
It would also be helpful if NodeChangedEvent also references to the old document node as well, for the same reasons that NodeRemovedEvent. What do you think?


Typeahead with typeahead-min-length="0" does not appear when clearing the text box.

In a typeahead with minimum length configured to zero, if the user selects a value, then returns to the input and taps the browser-provided X to clear the box, the input is now focused and empty; however, the list box is hidden.
Typing and deleting a character at this point opens the box. Leaving and re-entering the input field also opens the box.
I observed the behavior in IE11, in a typeahead using the custom popup template from the demos. I have not verified other browsers or without templates.
<input type="text"
       ng-model="model"
       placeholder="Select an item"
       uib-typeahead="item.Name for item in items | filter:{Name:$viewValue}"
       typeahead-editable="false"
       typeahead-popup-template-url="customPopupTemplate.html"
       typeahead-min-length="0" />

@kbrimington thnx for bringing this in. Could you please clarify what you mean by "taps the browser-provided X to clear the box"? A screenshot would be ideal. I presume that you talk about a clear button on the right added by some browsers but would like to confirm.
Depending on what we are talking about we would have to see if an appropriate DOM event is fired in that case or not. If not we are kind of blind to that user action...

Thanks for your response. Your presumption was correct. I was referring to the clear button on the right added by many browsers.
For instance:

After tapping the browser-provided X, the input remains focused (note the cursor, below), but the typeahead is not visible.


Specify Max Context Length for Llama 3 Queries in Payload Configuration

this is only for Ollama queries
When using the default context length settings, each query to the Llama model is limited to approximately 2,000 tokens. To effectively utilize the full potential of the Llama 3 model, especially for more complex tasks requiring a larger context, it is necessary to explicitly set the maximum context length.
Below is an example payload configuration that sets the maximum context length to 8,192 tokens, which is not currently the default behavior:
payload = {
    "model": self.model,
    "prompt": user,
    "system": system,
    "stream": False,
    "temperature": 0,
    "options": {"num_ctx": 8192}
}

Expected Behavior:
Allow the context length to be configurable up to the maximum supported by the model directly through the payload options.
Actual Behavior:
The context length defaults to around 2,000 tokens, which may not suffice for more in-depth analyses or larger data contexts required by users.
Suggested Fix:
Include an option within the model configuration to easily specify and adjust the maximum context length according to user needs or specific tasks.

Thanks for raising this, I'll look to add it if I have time.


Switch counter metrics to use CUMULATIVE

fixes #18

@tam7t let me know what are your findings when you do simple backwards compatibility testing

So I tested this and I'm getting this error
Failed to write time series data: rpc error: code = InvalidArgument desc = Field timeSeries[0].points[0].interval.start_time had an invalid value of "2021-08-31T14:19:47-07:00": The start time must be before the end time (2021-08-31T14:19:47-07:00) for the non-gauge metric 'custom.googleapis.com/go-metrics/my-metric-id
and yes, this is a backwards incompatible change -- I had to manually delete the old metric since the type changed.

The correct MetricKind may actually be DELTA.

@rf thanks for your effort.
@tam7t would you accept PR afte changing MetricKind to DELTA?

https://github.com/google/go-metrics-stackdriver/pull/19#discussion_r686977500 is the reason for the error there. I'm still evaluating the effects of changing the metric types at all but i do not suspect that DELTA will make it more difficult as additional time periods would need to be accounted for

It turns out DELTA metrics are not supported in Stackdriver for custom metrics.
I'm not sure that counters in go-metrics are intended to be treated like a statsd counter (i.e. something that resets after an interval). It's not clear if other sinks treat it this way.

@rf I believe that what you are describing is how to implement and report a DELTA metric (clearing each interval and reporting the start/end time of the interval) because you are reporting the change of the counter over a specific time interval. To report a counter as CUMULATIVE you need to report the start time of the accumulation in the report to stackdriver, as the histogram metrics do.

I did have some trouble getting CUMULATIVE to work -- I was also trying to use a StartTime that was basically the end of the last reporting interval. Not sure if that was right, should I be using the same start time as for histograms?
I was able to get this to work, however, by using GAUGE and just resetting the counters every time we do the deep copy in order to flush. It has the benefit of being somewhat backwards incompatible (because the metrics don't need to be re-created) but will end up reporting very different values.


how to disable smooth scrolling to anchor links? aka make anchor links work twice++

Problem:  Anchor links only work on the 1st visit.   Reloading the page always takes you to the top.
Easy example, with the local server running, click an anchor link.   now edit something and watch it return to the top, even though the url is still /#anchor
This is symptomatic of the behavior of javascript's scrollTo, and probably others - but I'm not an expert in this area.
I'd like to be able to disable the smooth scrolling behavior (it's not something I care for anyway, regardless of breaking of anchors), but I can't figure out where in the theme this comes from....
If there's a flag to disable it already, excellent - if not, I'll either update my local copy, or submit a PR for such a flag if I can find a way to safely toggle it.
Can you offer any pointers?
thanks.

We used to use scrollTo, but no longer do. You can update or override your Sass files to change the behavior here:
https://github.com/victoriadrake/hugo-theme-introduction/blob/2932037152a30e5542e947122ece0a26f148091b/assets/sass/_base.sass#L4-L5
I can't replicate your described behavior on the rendered demo site (https://hugo-introduction.netlify.com/). Does it only occur with live reload when using the Hugo server?

We used to use scrollTo, but no longer do. You can update or override your Sass files to change the behavior here:
https://github.com/victoriadrake/hugo-theme-introduction/blob/2932037152a30e5542e947122ece0a26f148091b/assets/sass/_base.sass#L4-L5
I can't replicate your described behavior on the rendered demo site (https://hugo-introduction.netlify.com/). Does it only occur with live reload when using the Hugo server?

interesting, I can't repro on the demo either.
it's consistent across all of my stacks - local server, and netlify -
here's my prod environment where it's reproed:
https://www.brasstack.net/#about
so far I haven't been able to effect anything after changing my _base.sass
scroll-behavior, but I'll keep digging when I get a chance, thanks for the
pointer!
On Sun, Jan 17, 2021 at 9:59 AM Victoria Drake<EMAIL_ADDRESS>wrote:

We used to use scrollTo, but no longer do. You can update or override
your Sass files to change the behavior here:
https://github.com/victoriadrake/hugo-theme-introduction/blob/2932037152a30e5542e947122ece0a26f148091b/assets/sass/_base.sass#L4-L5
I can't replicate your described behavior on the rendered demo site (
https://hugo-introduction.netlify.com/). Does it only occur with live
reload when using the Hugo server?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/victoriadrake/hugo-theme-introduction/issues/280#issuecomment-761825928,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIOW3G7JGUXSXPCILZDTBDS2L3N7ANCNFSM4VUDTKVQ
.

interesting, I can't repro on the demo either.
it's consistent across all of my stacks - local server, and netlify -
here's my prod environment where it's reproed:
https://www.brasstack.net/#about
so far I haven't been able to effect anything after changing my _base.sass
scroll-behavior, but I'll keep digging when I get a chance, thanks for the
pointer!
On Sun, Jan 17, 2021 at 9:59 AM Victoria Drake<EMAIL_ADDRESS>wrote:

We used to use scrollTo, but no longer do. You can update or override
your Sass files to change the behavior here:
https://github.com/victoriadrake/hugo-theme-introduction/blob/2932037152a30e5542e947122ece0a26f148091b/assets/sass/_base.sass#L4-L5
I can't replicate your described behavior on the rendered demo site (
https://hugo-introduction.netlify.com/). Does it only occur with live
reload when using the Hugo server?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/victoriadrake/hugo-theme-introduction/issues/280#issuecomment-761825928,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIOW3G7JGUXSXPCILZDTBDS2L3N7ANCNFSM4VUDTKVQ
.


Not an issue, just a note - tests fail

PHPUnit seems to fail when using the currently newest phpsec/prophecy version 1.10.0.
See https://github.com/phpspec/prophecy/issues/457

Do you have a log of the failures? We should probably address that

Sure, here it is.
Composer output:
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 65 installs, 0 updates, 0 removals
  - Installing ocramius/package-versions (1.4.2): Loading from cache
  - Installing nikic/fast-route (v1.3.0): Loading from cache
  - Installing ralouphie/getallheaders (3.0.3): Loading from cache
  - Installing psr/http-message (1.0.1): Loading from cache
  - Installing guzzlehttp/psr7 (1.6.1): Loading from cache
  - Installing psr/http-factory (1.0.1): Loading from cache
  - Installing http-interop/http-factory-guzzle (1.0.0): Loading from cache
  - Installing nyholm/psr7-server (0.3.0): Loading from cache
  - Installing slim/http (0.7): Loading from cache
  - Installing fig/http-message-util (1.1.3): Loading from cache
  - Installing slim/psr7 (0.3.0): Loading from cache
  - Installing psr/http-server-handler (1.0.1): Loading from cache
  - Installing psr/http-server-middleware (1.0.1): Loading from cache
  - Installing php-http/message-factory (v1.0.2): Loading from cache
  - Installing nyholm/psr7 (1.2.1): Loading from cache
  - Installing sebastian/version (2.0.1): Loading from cache
  - Installing sebastian/resource-operations (2.0.1): Loading from cache
  - Installing sebastian/recursion-context (3.0.0): Loading from cache
  - Installing sebastian/object-reflector (1.1.1): Loading from cache
  - Installing sebastian/object-enumerator (3.0.3): Loading from cache
  - Installing sebastian/global-state (2.0.0): Loading from cache
  - Installing sebastian/exporter (3.1.2): Loading from cache
  - Installing sebastian/environment (4.2.3): Loading from cache
  - Installing sebastian/diff (3.0.2): Loading from cache
  - Installing sebastian/comparator (3.0.2): Loading from cache
  - Installing phpunit/php-timer (2.1.2): Loading from cache
  - Installing phpunit/php-text-template (1.2.1): Loading from cache
  - Installing phpunit/php-file-iterator (2.0.2): Loading from cache
  - Installing theseer/tokenizer (1.1.3): Loading from cache
  - Installing sebastian/code-unit-reverse-lookup (1.0.1): Loading from cache
  - Installing phpunit/php-token-stream (3.1.1): Loading from cache
  - Installing phpunit/php-code-coverage (6.1.4): Loading from cache
  - Installing doctrine/instantiator (1.3.0): Loading from cache
  - Installing symfony/polyfill-ctype (v1.13.1): Loading from cache
  - Installing webmozart/assert (1.6.0): Loading from cache
  - Installing phpdocumentor/reflection-common (2.0.0): Loading from cache
  - Installing phpdocumentor/type-resolver (1.0.1): Loading from cache
  - Installing phpdocumentor/reflection-docblock (4.3.2): Loading from cache
  - Installing phpspec/prophecy (1.10.0): Loading from cache
  - Installing phar-io/version (2.0.1): Loading from cache
  - Installing phar-io/manifest (1.0.3): Loading from cache
  - Installing myclabs/deep-copy (1.9.4): Loading from cache
  - Installing phpunit/phpunit (7.5.18): Loading from cache
  - Installing symfony/finder (v4.4.1): Loading from cache
  - Installing psr/container (1.0.0): Loading from cache
  - Installing symfony/service-contracts (v1.1.8): Loading from cache
  - Installing symfony/polyfill-php73 (v1.13.1): Loading from cache
  - Installing symfony/polyfill-mbstring (v1.13.1): Loading from cache
  - Installing symfony/console (v4.4.1): Loading from cache
  - Installing psr/log (1.1.2): Loading from cache
  - Installing phpstan/phpdoc-parser (0.3.5): Loading from cache
  - Installing nikic/php-parser (v4.3.0): Loading from cache
  - Installing nette/utils (v3.0.2): Loading from cache
  - Installing nette/schema (v1.0.1): Loading from cache
  - Installing nette/finder (v2.5.1): Loading from cache
  - Installing nette/robot-loader (v3.2.0): Loading from cache
  - Installing nette/neon (v3.0.0): Loading from cache
  - Installing nette/php-generator (v3.3.1): Loading from cache
  - Installing nette/di (v3.0.1): Loading from cache
  - Installing nette/bootstrap (v3.0.1): Loading from cache
  - Installing jean85/pretty-package-versions (1.2): Loading from cache
  - Installing composer/xdebug-handler (1.4.0): Loading from cache
  - Installing phpstan/phpstan (0.11.19): Loading from cache
  - Installing squizlabs/php_codesniffer (3.5.3): Loading from cache
  - Installing zendframework/zend-diactoros (2.2.1): Loading from cache
guzzlehttp/psr7 suggests installing zendframework/zend-httphandlerrunner (Emit PSR-7 responses)
sebastian/global-state suggests installing ext-uopz (*)
sebastian/environment suggests installing ext-posix (*)
phpunit/phpunit suggests installing phpunit/php-invoker (^2.0)
symfony/service-contracts suggests installing symfony/service-implementation
symfony/console suggests installing symfony/event-dispatcher
symfony/console suggests installing symfony/lock
symfony/console suggests installing symfony/process
nette/bootstrap suggests installing tracy/tracy (to use Configurator::enableTracy())
Writing lock file
Generating autoload files
ocramius/package-versions:  Generating version class...
ocramius/package-versions: ...done generating version class

PHPUnit output
PHPUnit 7.5.18 by Sebastian Bergmann and contributors.

...............................................................  63 / 411 ( 15%)
..........................F.................................... 126 / 411 ( 30%)
............................................................... 189 / 411 ( 45%)
............................................................... 252 / 411 ( 61%)
............................................................... 315 / 411 ( 76%)
......................EEEEEEEE.E..E............................ 378 / 411 ( 91%)
...........EEEE....EEEEF.........                               411 / 411 (100%)

Time: 10.37 seconds, Memory: 22.00 MB

There were 18 errors:

1) Slim\Tests\Routing\RouteCollectorProxyTest::testGet
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:123
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:148

2) Slim\Tests\Routing\RouteCollectorProxyTest::testPost
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:131
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:181

3) Slim\Tests\Routing\RouteCollectorProxyTest::testPut
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:139
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:214

4) Slim\Tests\Routing\RouteCollectorProxyTest::testPatch
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:147
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:247

5) Slim\Tests\Routing\RouteCollectorProxyTest::testDelete
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:155
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:280

6) Slim\Tests\Routing\RouteCollectorProxyTest::testOptions
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:163
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:313

7) Slim\Tests\Routing\RouteCollectorProxyTest::testAny
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:171
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:346

8) Slim\Tests\Routing\RouteCollectorProxyTest::testMap
TypeError: Return value of Double\RouteCollectorInterface\P4::map() must implement interface Slim\Interfaces\RouteInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:181
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:380

9) Slim\Tests\Routing\RouteCollectorProxyTest::testGroup
TypeError: Return value of Double\RouteCollectorInterface\P4::group() must implement interface Slim\Interfaces\RouteGroupInterface, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteCollectorProxy.php:191
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorProxyTest.php:454

10) Slim\Tests\Routing\RouteCollectorTest::testMapPrependsGroupPattern
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\RouteGroup.php:72
D:\Documents\GitHub\Slim\Slim\Routing\RouteCollector.php:253
D:\Documents\GitHub\Slim\tests\Routing\RouteCollectorTest.php:81

11) Slim\Tests\RouteTest::testAddMiddleware
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:265
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:275
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:270

12) Slim\Tests\RouteTest::testAddMiddlewareOnGroup
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:301
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:275
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:325

13) Slim\Tests\RouteTest::testAddClosureMiddleware
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:337
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:275
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:341

14) Slim\Tests\RouteTest::testAddMiddlewareUsingDeferredResolution
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:187
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:356

15) Slim\Tests\RouteTest::testControllerMethodAsStringResolvesWithContainer
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:446

16) Slim\Tests\RouteTest::testProcessWhenReturningAResponse
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:465

17) Slim\Tests\RouteTest::testRouteCallableDoesNotAppendEchoedOutput
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:486

18) Slim\Tests\RouteTest::testRouteCallableAppendsCorrectOutputToResponse
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:507

--

There were 2 failures:

1) Slim\Tests\AppTest::testInvokeWithNonExistentMethodOnCallableRegisteredInContainer
Failed asserting that exception of type "Error" matches expected exception "RuntimeException". Message was: "Call to a member function withAttribute() on null" at
D:\Documents\GitHub\Slim\Slim\Middleware\RoutingMiddleware.php:89
D:\Documents\GitHub\Slim\Slim\Routing\RouteRunner.php:71
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\App.php:208
D:\Documents\GitHub\Slim\tests\AppTest.php:1433
.

2) Slim\Tests\RouteTest::testInvokeWithException
Failed asserting that exception of type "TypeError" matches expected exception "\Exception". Message was: "Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned" at
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:360
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:523
.

ERRORS!
Tests: 411, Assertions: 714, Errors: 18, Failures: 2.

Generating code coverage report in HTML format ... done

The problem might be, that the developers of the prophecy library have modified \Prophecy\Argument\Token\ExactValueToken::scoreArgument(). It returns false in case the argument is an object and the comparator fails, see
https://github.com/phpspec/prophecy/blob/d638ebbb58daba25a6a0dc7969e1358a0e3c6682/src/Prophecy/Argument/Token/ExactValueToken.php#L63
Unforunately, this is the case for the \Prophecy\Comparator\ClosureComparator. Because its assertEquals() throws an exception for all cases, see
https://github.com/phpspec/prophecy/blob/d638ebbb58daba25a6a0dc7969e1358a0e3c6682/src/Prophecy/Comparator/ClosureComparator.php#L30-L41
Back to Slim
Maybe, we should change the method prophecies containing a closure as expected argument.
I tried to change the line
https://github.com/slimphp/Slim/blob/941828c85cf323462271d5cde08f186c3dec016b/tests/Routing/RouteCollectorProxyTest.php#L137
into
            ->map(['GET'], $pattern, Argument::is($callable))

which seems to work. Not sure if that is the intended way to go, though.
By the way, Argument::is() returns a \Prophecy\Argument\Token\IdenticalValueToken which compares using a ===.

I brought it down to one failure and one error. See https://github.com/adriansuter/Slim/tree/patch-prophecies, Commit https://github.com/adriansuter/Slim/commit/c853037f6bc3039cc66e89ee67fe1301bb87de8f
There was 1 error:

1) Slim\Tests\RouteTest::testAddMiddlewareUsingDeferredResolution
TypeError: Return value of Double\CallableResolverInterface\P3::resolve() must be callable, null returned

D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:187
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\Routing\Route.php:333
D:\Documents\GitHub\Slim\tests\Routing\RouteTest.php:356

--

There was 1 failure:

1) Slim\Tests\AppTest::testInvokeWithNonExistentMethodOnCallableRegisteredInContainer
Failed asserting that exception of type "Error" matches expected exception "RuntimeException". Message was: "Call to a member function withAttribute() on null" at
D:\Documents\GitHub\Slim\Slim\Middleware\RoutingMiddleware.php:89
D:\Documents\GitHub\Slim\Slim\Routing\RouteRunner.php:71
D:\Documents\GitHub\Slim\Slim\MiddlewareDispatcher.php:73
D:\Documents\GitHub\Slim\Slim\App.php:208
D:\Documents\GitHub\Slim\tests\AppTest.php:1433
.

ERRORS!
Tests: 411, Assertions: 755, Errors: 1, Failures: 1.

That's so weird that they introduced such a breaking change on a minor version.. Well we definitely will need to fix all the repos. Ugh


expressJWT - algorithms should be set

When I got to the 'Checking the standalone backend' section, I ran npm run development and received the following error:
Error: algorithms should be set     at module.exports (D:\react\mern-skeleton\node_modules\express-jwt\lib\index.js:22:34)     at eval (webpack:///./server/controllers/auth.controller.js?:56:73)
After googling, I found a suggestion for adding algorithms: ['RS256'] to the requireSignin declaration and it solved the error.
const requireSignin = expressJwt({   secret: config.jwtSecret,   userProperty: 'auth',   algorithms: ['RS256'], });
I don't know that RS256 is the correct algorithm. I was wondering if I failed to include something from the example.

You didn't miss anything from the example. This algorithms requirement was added in a later version of the expressJWT package. The book example uses a previous version which didn't have this requirement.
RS256 seems to be a standard option for basic login authentication. It will get the job done for these examples.

In testing the API routes, I found that /auth/signin won't work with RS256 but it does work with HS256. Thanks for your help. I was able to get through all the API Routes testing. I'm going to close this issue.  Learning a lot, thanks again.


November 2019 PBIX file currupted

Hi there ,
Please check the file for November 2019, the file cannot be opened, "corrupted or invalid"
Thanks.
Fowmy

closing - old issue and cannot reproduce. just tried.


add laChain and laTestnet networks

Description
Build in LatAm for LatAm
Add lachain and latestnet to chains.
lachain.network
Additional Information

[x] I read the contributing docs (if this is your first contribution)

Your ENS/address: diosplan.eth

Chains should now be edited/added on the Viem repository.


Fix #8637: Null added if str.sub(Hash) match last char

Example:
"helloC".sub({'C' => 'G'}) # => "helloG\u0000"
This is my first pull request to Crystal
I hope to be useful

Thank you for this contribution, it's very welcome!
There should also be specs for all the other sub overloads not only for char hash. Maybe it would be best to add a new sample to string_spec.cr for testing last-character behaviour.

Thanks so much @straight-shoota  for the feedback
I've done it in another commit so it's ready to be reviewed and for squash them
Don't hesitate to continue to demand more changes

These are actually quite a lot of test cases. But I guess we just have that many overloads for sub.


Support TLS

I have this extension working with plain HTTP, but I'm hosting Ollama in the cloud and I'd like to use TLS to communicate with it. Is there any way to do this?
Setting the hostname and port to my Ollama's TLS endpoint results in a 400 response, so I assume it's sending an HTTP request to an HTTPS port. LMK if I'm wrong.

Horrible workaround:

open ~/.vscode/extensions/rjmacarthy.twinny-2.4.0/out/extension.js
change e.exports = require("http"); to e.exports = require("https");
reload window

It works, until you reinstall the extension.
I'm not sure if that forces TLS and breaks plain HTTP, but that works for me with an HTTPS endpoint.

Hey thanks for subbing this issue. I think I the best way to be to add a boolean option in the config to support https and have some logic to use TLS if enabled. Would that work @rcgtnick?
Many thanks

That would be a great solution, thanks!

Fixed in #30 release v2.5.1

FYI, working well with TLS and 2.5.11.


Use a custom implicitNotFound error for CSS transforms

Mailing List thread:
N/A
This adds a custom error message that provides a bit more direction when we can't find an implicit converter for a CSS transform. Tested it out by creating an error in a spec... it looks like this!
[error] /Users/matt/Projects/framework/core/util/src/test/scala/net/liftweb/util/CssSelectorSpec.scala:502: The value you're attempting to use on the right hand side of the #> operator can't be automatically converted to a (NodeSeq)=>NodeSeq function. Consider binding the individual members of the class you're trying to use, or define an implicit CanBind[T] that tells Lift how to convert this to a (NodeSeq)=>NodeSeq.
[error]       ".foo" #> Bacon("boo!")
[error]              ^
[error] one error found

Fixes #930

This fixes #930, right?

Yes, updated the PR description to mention that.
I can haz merge? :D

Ya okay :shipit:


Social media embeds do not show in third party services

I have noticed that if a feed article has social media embeds like X or Instagram, and the feed is in a third party service (Feedly, FreshRSS, etc.), the embed shows as text. However, if I use the iCloud option, it shows properly. Is this a bug?

Some third party services strip out all JavaScript, and JavaScript is required for social media embeds to work correctly.


GraphQL InputType argument parsing error & workaround

The following gives me what seems to be a parsing error:

Error: line 2:45 no viable alternative at input '['

mutation BrokenNestedInput {
  nestedArgumentQuery(dryRun: true, filters: [{field: itemId, equals: "1234"}]) {
    itemId
    itemName
  }
}

As far as I can tell, this happens any time I try to pass an input type within an input type, and a similar error occurs with '{' when I change filters to only accept a single element.
I discovered a workaround where I pass filters the following query variable:
## Query Variables
{
  "filter":
  [
    {
      "field": "itemId",
      "equals": "1234"
    },
    {
      "field": "itemId",
      "equals": "4321",
      "conjunction": "OR"
    }
  ]
}
----------
##"Query"
mutation NestedInputTypeTest($filter: [FilterInput]) {
  nestedArgumentQuery(filters: $filter) {
    itemId
    itemName
  }
}

This gives me the results I want with no parsing errors.
Also, just for clarification, I'm using mutation methods as makeshift queries to test a filtering system.

Fix coming in next release

Fixed in 1.0.x


Fix behavior of last 3 hours test mode switch (DEV)

Previously the days for which the last 3 hours were fetched, was the latest day in the servers index for a country, but if a day is not complete, the day will not be visible in the index. This PR fixes this behavior by artificially adding the one additional date (LATEST_DAY_IN_INDEX+1DAY).
Testing

Try it without this PR, check in the logs what the KeyFileDownloader downloads.
Try with this PR, check that the actual last 3 hours are downloaded.

What if there are less than 3 hour packages available for the given date?

Just for the record: I think it's not required to fix this, as the 3 Hour mode is only used for testing, and it wouldn't work as the name suggests only between midnight and 2 am or so. I can live with that 😉


Reduce calls to Alma API

Due to the concurrent hit limit of 25 hits/second, and depending on what we learn from #871 we need to find way to reduce calls to the Alma API. Likely by querying solr instead of hitting the API where possible, but also by creating new endpoints that can combine API calls and changing endpoints to return less data. Another option would be to move calls to javascript in places where we can hide the call behind a user action requirement.
This issue will act as an epic to collect specific tasks we can perform toward this goal as we discover them.
Ticketed:

[x] new availability endpoint that accepts multiple bibs: #1118
[x] new availability endpoint for show page #1145
[x] orangelight use of these new endpoints pulibrary/orangelight#2382
[x] Update the barcode#scsb endpoint to use the solr index where possible instead of the api #1185

The issues specified here were all explored and either completed or not feasible. Closing and we can open new tickets if new opportunities to reduce API calls become clear.


fiber sparameters

this PR calculates the Sparameters for an arbitrary grating coupler
it still needs some work to match the same grating simulation in lumerical 2D FDTD results with an efficiency of 3dB

Thanks for the organizational updates -- this is a good way forward.
While I haven't been able to get the plot you show (is that using the default parameters you added in fiber.py?), and therefore cannot confirm this, the results seem to be close to what you expect near the center of the wavelength band, and drop away. This is known to occur when frequencies are requested in the mode monitors that are poorly-represented in the source pulse. Try playing with the bandwidth of the GaussianSource. Right now it's 0.1*fcen. With fcen = c/1.55E-6 = 193THz, this means the pulse FWHM extends from ~184 THz to 202 THz. You are requesting frequencies to be sampled from c/1.6E-6 = 187 THz to c/1.5E-6 = 200 THz, which may be cutting it close. You could also repeat the FDTD simulation with different center frequencies to see how well the off-center frequencies are doing in the "broadband" simulation.
There is also the question as to whether there is something setup differently between the MEEP and Lumerical sims. In the past I've been able to get sensibly the same results from MEEP and Lumerical at the center frequency I was studying.
Aside: Also while mpirun is not enabled from Python per say as of now, from the terminal doing mpirun -np 10 python fiber.py instead of just python fiber.py does work. Might save you some time!

Hi Simon,
the plot was done using lumerical
The transmission for this script does match

Oh that makes sense. Glad it works now!

sorry, i meant that the transmission for this script does not match

FYI Meep's GaussianBeamSource source object implements the Green's function of a 3D Gaussian beam for both 2D and 3D, which isn't correct (the two are very different). In 2D, it's a good enough approximation, but still introduces error.
Eventually we want to implement the proper Green's function, but that will take time (and effort).
In other words, Lumerical and Meep should differ significantly if you are using a GaussianBeamSource in 2D.

Also Meep's Greene's function is computed at a single frequency. Ideally, you would compute the Green's function at multiple frequencies (if you were looking at a broadband result) and fit the frequency profile to a time-domain source at each spatial point. I'm pretty sure Lumerical does this fitting (I know they do it for their mode sources).

Thanks for chiming in Alec. This could explain why I thought I had a match, since in my case I was looking at a single frequency with only the waveguide as the source and fiber a monitor port.

with the current sim setup there is a 17dB difference in the meet Sparameter results compared to Lumerical


Documentation link is broken in README

This link is broken:

Full documentation is available at polymer.github.io/lit-html.

Fixed by #637


Doesn't show Movies or TV Series data after deploying

I have followed the guide and deployed, everything seems to be right but it doesn't show any data on the web.
Here is the SS

I have enabled gdrive api too
https://tinyurl.com/yhscb2wm

On your server, could you go to this URL
https://EXAMPLE.COM/api/v1/debug/metadata.json?secret=YOUR_SECRET_KEY
It'll download a file name metadata.json, could you share it here?

https://EXAMPLE.COM/api/v1/debug/metadata.json?secret=YOUR_SECRET_KEY

here is the response i got
{"code":404,"message":"The file/folder doesn't exist.","success":false}


OWNERS: update per repo migration issue

Refer to https://github.com/kubernetes/org/issues/3279, to facilitate repo migration we can start with a limited set of owners that we can grow over time post-migration. I've raised this issue with the org https://github.com/kubernetes/org/issues/3312

Raised an issue for me as well
https://github.com/kubernetes/org/issues/3319

/approve

/lgtm

/approve

/assign davidjumani

/approve

Guessing this will need to be approved by someone here https://github.com/kubernetes-sigs/cluster-api-provider-cloudstack/blob/main/OWNERS
@pmotyka @maxdrib @vignesh-goutham @jweite-amazon @mrog @rejoshed @wongni

/approve

/lgtm

/verify-owners

/approve

/ok-to-test


Disable CC effects when NumberOfEnemies is 1

When NumberOfEnemies is 1 we're probably trying to sim a boss fight, and bosses can't be crowd controlled. There's another issue to model the Stagger mechanic, but first we should make CC effects disabled for bosses (which will be a big damage nerf).

duplicate


Restructuring pairings

By now the pairing engines for different types of pairing-friendly curves are implemented independently, resulting in five pieces of very similar code for the Ate pairing evaluation:

algebra/src/curves/models/bls12/mod.rs, ZEXE's generic implementation  for BLS12 curves in affine coordinates,
algebra/src/curves/mnt6/mod.rs, ZEXE's specific implementation for the MNT6-298,
algebra/src/curves/sw6/mod.rs, another implementation for the Cocks-Pinch curve-782 of embedding degree 6 (ZEXE's outer curve with respect to the BLS12-377),
and our recent implementations for generic MNT4 curves, algebra/src/curves/models/mnt4/mod.rs, and MNT6 curves, algebra/src/curves/models/mnt6/mod.rs.

I propose a different level of abstraction, introducing twist2Ate and twist6Ate as pairing types according to the two representations of G2 as found in the above implementations: either as a subgroup of a quadratic twist (as for MNT4/6, mnt6, sw6) or sextic twist (BLS12) of the curve.
Both twist2Ate and twist6Ate need to allow the base field for the twist E' to be a general extension field of the same characteristic as the one for E - but the operations for the evaluation of the Ate paring are generic, i.e. independent of the degree of the base field for E'.
Such abstraction makes it possible to reuse these two types of pairing types, and to aggregate pairing evaluation code in an own folder (e.g. algebra/src/pairings/ ) separated from algebra/src/curves, which contain also non-pairing-friendly curves such as the JubJub.
In my opinion such a structure is more clear than the present. Moreover, it makes it is easier to find all the pairing code when extending the lib by further pairing types (which use cubic twists, e.g.).

Not needed anymore after #144


Crash after entering the first character

I am running Fedora and installed dotnet core using the official repository. I downloaded the source code of roslynpad since dotnet core is installed in a location currently unknown to the app.
I can compile the app successfully and it starts but after entering the first character in the main text box the app crashes with the following stack trace:
Unhandled exception. System.MethodAccessException: Attempt by method 'AvaloniaEdit.CodeCompletion.CompletionWindowBase+InputHandler.OnPreviewKeyUp(Avalonia.Input.KeyEventArgs)' to access method 'Avalonia.Input.KeyEventArgs..ctor()' failed.
   at AvaloniaEdit.CodeCompletion.CompletionWindowBase.InputHandler.OnPreviewKeyUp(KeyEventArgs e)
   at AvaloniaEdit.Editing.TextArea.OnPreviewKeyUp(Object sender, KeyEventArgs e)
   at Avalonia.Interactivity.EventRoute.RaiseEventImpl(RoutedEventArgs e) in /_/src/Avalonia.Base/Interactivity/EventRoute.cs:line 118
   at Avalonia.Interactivity.EventRoute.RaiseEvent(IInteractive source, RoutedEventArgs e) in /_/src/Avalonia.Base/Interactivity/EventRoute.cs:line 79
   at Avalonia.Interactivity.Interactive.RaiseEvent(RoutedEventArgs e) in /_/src/Avalonia.Base/Interactivity/Interactive.cs:line 126
   at Avalonia.Input.KeyboardDevice.ProcessRawEvent(RawInputEventArgs e) in /_/src/Avalonia.Base/Input/KeyboardDevice.cs:line 228
   at Avalonia.Input.InputManager.ProcessInput(RawInputEventArgs e) in /_/src/Avalonia.Base/Input/InputManager.cs:line 37
   at Avalonia.RawEventGrouper.DispatchFromQueue() in /_/src/Shared/RawEventGrouping.cs:line 59
   at Avalonia.Threading.JobRunner.RunJobs(Nullable`1 priority) in /_/src/Avalonia.Base/Threading/JobRunner.cs:line 38
   at Avalonia.X11.X11PlatformThreading.HandleX11(CancellationToken cancellationToken) in /_/src/Avalonia.X11/X11PlatformThreading.cs:line 199
   at Avalonia.X11.X11PlatformThreading.RunLoop(CancellationToken cancellationToken) in /_/src/Avalonia.X11/X11PlatformThreading.cs:line 245
   at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken) in /_/src/Avalonia.Base/Threading/Dispatcher.cs:line 61
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args) in /_/src/Avalonia.Controls/ApplicationLifetimes/ClassicDesktopStyleApplicationLifetime.cs:line 120
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime[T](T builder, String[] args, ShutdownMode shutdownMode) in /_/src/Avalonia.Controls/ApplicationLifetimes/ClassicDesktopStyleApplicationLifetime.cs:line 209
   at RoslynPad.Program.Main(String[] args) in /home/b0wter/work/roslynpad/src/RoslynPad.Avalonia/Program.cs:line 13

Other app features (like adding nugets) work fine.
Version

OS: Fedora 38
commit ID: 1958cfbc796a42e64013e86426e290adc4272bbb

I've cloned the latest version ( 67481b87017ee6b7b125f93f0a499c0b8d72937a). Running the app makes it briefly visible and results in a crash:
.../RoslynPad.Avalonia on  main
❯ dotnet run                                                                                21:57:18
Unhandled exception. System.InvalidOperationException: Operation is not valid due to the current state of the object.
   at RoslynPad.UI.OpenDocumentViewModel.set_Platform(ExecutionPlatform value) in /home/b0wter/work/roslynpad2/src/RoslynPad.Common.UI/ViewModels/OpenDocumentViewModel.cs:line 451
   at RoslynPad.UI.OpenDocumentViewModel.Initialize(DocumentId documentId, Action`1 onError, Func`1 getSelection, IDisposable viewDisposable) in /home/b0wter/work/roslynpad2/src/RoslynPad.Common.UI/ViewModels/OpenDocumentViewModel.cs:line 613
   at RoslynPad.DocumentView.OnDataContextChanged(Object sender, EventArgs args) in /home/b0wter/work/roslynpad2/src/RoslynPad.Avalonia/DocumentView.axaml.cs:line 59
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_0(Object state)
   at Avalonia.Threading.SendOrPostCallbackDispatcherOperation.InvokeCore()
   at Avalonia.Threading.DispatcherOperation.Execute()
   at Avalonia.Threading.Dispatcher.ExecuteJob(DispatcherOperation job)
   at Avalonia.Threading.Dispatcher.ExecuteJobsCore(Boolean fromExplicitBackgroundProcessingCallback)
   at Avalonia.Threading.Dispatcher.Signaled()
   at Avalonia.X11.X11PlatformThreading.CheckSignaled()
   at Avalonia.X11.X11PlatformThreading.RunLoop(CancellationToken cancellationToken)
   at Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)
   at Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken)
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args)
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime(AppBuilder builder, String[] args, ShutdownMode shutdownMode)
   at RoslynPad.Program.Main(String[] args) in /home/b0wter/work/roslynpad2/src/RoslynPad.Avalonia/Program.cs:line 13

I've opened the Avalonia-Solution in Rider and tried running Roslynpad.Avalonia to get more details and get this:


[SPARK-32832][SS][2.4] Use CaseInsensitiveMap for DataStreamReader/Writer options

What changes were proposed in this pull request?
This is a backport of https://github.com/apache/spark/pull/29702 .
This PR aims to fix indeterministic behavior on DataStreamReader/Writer options like the following.
scala> spark.readStream.format("parquet").option("paTh", "1").option("PATH", "2").option("Path", "3").option("patH", "4").option("path", "5").load()
org.apache.spark.sql.AnalysisException: Path does not exist: 1;

Why are the changes needed?
This will make the behavior deterministic.
Does this PR introduce any user-facing change?
Yes, but the previous behavior is indeterministic.
How was this patch tested?
Pass the newly test cases.

cc @cloud-fan and @HeartSaVioR .

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/33117/
Test PASSed.

Test build #128493 has started for PR 29707 at commit 58a1861.

Test build #128493 has finished for PR 29707 at commit 58a1861.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128493/
Test FAILed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/33158/
Test PASSed.

Retest this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/33159/
Test PASSed.

Test build #128534 has started for PR 29707 at commit 58a1861.

Test build #128534 has finished for PR 29707 at commit 58a1861.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128534/
Test FAILed.

retest this, please

Test build #128537 has started for PR 29707 at commit 58a1861.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/33162/
Test PASSed.

Thank you for review, approval, and retrigger, @HeartSaVioR .

Test build #128537 has finished for PR 29707 at commit 58a1861.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/128537/
Test PASSed.

Thank you all. Merged to branch-2.4.


[bug] 'compiled-objects-have-debug-symbols' check fails with a decoding error on numpy windows amd64 wheel

What did you expect to happen?
For pydistcheck to only print output it controls, not a Python stacktrace.
What actually happened?
Ran the following on my mac (macOS 12.2.1, intel chip)
curl -O https://files.pythonhosted.org/packages/be/b0/611101990ddac767e54e2d27d1f4576ae1662cca64e2d55ef0e62558ec26/numpy-1.26.3-cp310-cp310-win_amd64.whl

pydistcheck ./numpy-1.26.3-cp310-cp310-win_amd64.whl

yields the following:
==================== running pydistcheck ====================

checking './numpy-1.26.3-cp310-cp310-win_amd64.whl'
------------ check results -----------
Traceback (most recent call last):
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/bin/pydistcheck", line 8, in <module>
    sys.exit(check())
             ^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
         ^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/pydistcheck/cli.py", line 214, in check
    errors += this_check(distro_summary=summary)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/pydistcheck/checks.py", line 43, in __call__
    has_debug_symbols, cmd_str = _archive_member_has_debug_symbols(
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/pydistcheck/shared_lib_utils.py", line 79, in _archive_member_has_debug_symbols
    has_debug_symbols, cmd_str = _look_for_debug_symbols(lib_file=full_path)
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/pydistcheck/shared_lib_utils.py", line 53, in _look_for_debug_symbols
    stdout = _run_command(args=[*cmd_args, lib_file])
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/jlamb/mambaforge/envs/pydistcheck-dev/lib/python3.11/site-packages/pydistcheck/shared_lib_utils.py", line 22, in _run_command
    return stdout.decode("utf-8")
           ^^^^^^^^^^^^^^^^^^^^^^
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd7 in position 1749588: invalid continuation byte

How can someone else reproduce this problem?
see above
What version of pydistcheck are you using?
0.5.1
Notes
output of 'conda info' (click me)

     active environment : pydistcheck-dev
    active env location : /Users/jlamb/mambaforge/envs/pydistcheck-dev
            shell level : 1
       user config file : /Users/jlamb/.condarc
 populated config files : /Users/jlamb/mambaforge/.condarc
                          /Users/jlamb/.condarc
          conda version : 23.11.0
    conda-build version : 3.27.0
         python version : 3.9.9.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=skylake
                          __conda=23.11.0=0
                          __osx=12.2.1=0
                          __unix=0=0
       base environment : /Users/jlamb/mambaforge  (writable)
      conda av data dir : /Users/jlamb/mambaforge/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /Users/jlamb/mambaforge/pkgs
                          /Users/jlamb/.conda/pkgs
       envs directories : /Users/jlamb/mambaforge/envs
                          /Users/jlamb/.conda/envs
               platform : osx-64
             user-agent : conda/23.11.0 requests/2.31.0 CPython/3.9.9 Darwin/21.3.0 OSX/12.2.1 solver/libmamba conda-libmamba-solver/23.12.0 libmambapy/1.5.4
                UID:GID : 501:20
             netrc file : None
           offline mode : False

output of 'conda env export'
name: pydistcheck-dev
channels:
  - conda-forge
  - defaults
dependencies:
  - black=23.7.0=py311h6eed73b_1
  - brotli-python=1.1.0=py311hdf8f085_1
  - bzip2=1.0.8=h0d85af4_4
  - ca-certificates=2023.11.17=h8857fd0_0
  - certifi=2023.11.17=pyhd8ed1ab_0
  - charset-normalizer=3.3.2=pyhd8ed1ab_0
  - click=8.1.7=unix_pyh707e725_0
  - cmakelint=1.4.2=pyhd8ed1ab_0
  - colorama=0.4.6=pyhd8ed1ab_0
  - coverage=7.3.0=py311h2725bcf_0
  - exceptiongroup=1.1.3=pyhd8ed1ab_0
  - idna=3.6=pyhd8ed1ab_0
  - iniconfig=2.0.0=pyhd8ed1ab_0
  - isort=5.12.0=pyhd8ed1ab_1
  - libcxx=16.0.6=hd57cbcb_0
  - libexpat=2.5.0=hf0c8a7f_1
  - libffi=3.4.2=h0d85af4_5
  - libsqlite=3.43.0=h58db7d2_0
  - libzlib=1.2.13=h8a1eda9_5
  - mypy=1.5.1=py311h2725bcf_0
  - mypy_extensions=1.0.0=pyha770c72_0
  - ncurses=6.4=hf0c8a7f_0
  - openssl=3.2.0=hd75f5a5_1
  - packaging=23.1=pyhd8ed1ab_0
  - pathspec=0.11.2=pyhd8ed1ab_0
  - pip=23.2.1=pyhd8ed1ab_0
  - platformdirs=3.10.0=pyhd8ed1ab_0
  - pluggy=1.3.0=pyhd8ed1ab_0
  - psutil=5.9.5=py311h5547dcb_0
  - pysocks=1.7.1=pyha2e5f31_6
  - pytest=7.4.1=pyhd8ed1ab_0
  - pytest-cov=4.1.0=pyhd8ed1ab_0
  - python=3.11.5=h30d4d87_0_cpython
  - python_abi=3.11=3_cp311
  - pyyaml=6.0.1=py311h2725bcf_1
  - readline=8.2=h9e318b2_1
  - requests=2.31.0=pyhd8ed1ab_0
  - ruff=0.1.3=py311hec6fdf1_0
  - setuptools=68.1.2=pyhd8ed1ab_0
  - tk=8.6.12=h5dbffcc_0
  - toml=0.10.2=pyhd8ed1ab_0
  - tomli=2.0.1=pyhd8ed1ab_0
  - typing-extensions=4.7.1=hd8ed1ab_0
  - typing_extensions=4.7.1=pyha770c72_0
  - tzdata=2023c=h71feb2d_0
  - urllib3=2.1.0=pyhd8ed1ab_0
  - wheel=0.41.2=pyhd8ed1ab_0
  - xz=5.2.6=h775f41a_0
  - yaml=0.2.5=h0d85af4_2
  - yamllint=1.32.0=pyhd8ed1ab_0
  - pip:
      - pydistcheck==0.5.1
      - types-requests==<IP_ADDRESS>
      - types-urllib3==<IP_ADDRESS>
prefix: /Users/jlamb/mambaforge/envs/pydistcheck-dev

Initially, I assumed that this was because Windows (and therefore, a Windows-specific NumPy wheel) needs CP1252 encoding by default, but that didn't work, so I switched decoding with latin1. I think latin1 might be better suited for analysing binary data since it can decode any byte value from 0x00 to 0xFF, and every possible byte has a valid mapping, unlike UTF-8 or CP1252 – so it would be more robust in these cases, even across different platforms and architectures.
In short, it would perfectly preserve ASCII text (0x00-0x7F range) and can represent any byte value without data loss (0x80-0xFF range):
==================== running pydistcheck ====================

checking 'numpy-1.26.3-cp310-cp310-win_amd64.whl'
------------ check results -----------
1. [compiled-objects-have-debug-symbols] Found compiled object containing debug symbols.
2. For details, extract the distribution contents and run 'objdump --all-headers "numpy.libs/libopenblas64__v0.3.23-293-gc2f4bdbb-gcc_10_3_0-2bde3a66a51006b2b53eb373ff767a3f.dll"'.
errors found while checking: 1

==================== done running pydistcheck ===============

and I confirmed via running the llvm-readobj --sections numpy-1.26.3-cp310-cp310-win_amd64/numpy.libs/libopenblas64__v0.3.23-293-gc2f4bdbb-gcc_10_3_0-2bde3a66a51006b2b53eb373ff767a3f.dll | grep .debug and llvm-objdump -h numpy-1.26.3-cp310-cp310-win_amd64/numpy.libs/libopenblas64__v0.3.23-293-gc2f4bdbb-gcc_10_3_0-2bde3a66a51006b2b53eb373ff767a3f.dll commands on my macOS M-series machine that the debug symbols do exist indeed.

Output from dumping NumPy 1.26.3's headers
numpy-1.26.3-cp310-cp310-win_amd64/numpy.libs/libopenblas64__v0.3.23-293-gc2f4bdbb-gcc_10_3_0-2bde3a66a51006b2b53eb373ff767a3f.dll:     file format coff-x86-64

Sections:
Idx Name           Size     VMA              Type
  0 .text          01efd5c8 00000003a07b1000 TEXT, DATA
  1 .data          00012cd0 00000003a26af000 DATA
  2 .rdata         000f4cc0 00000003a26c2000 DATA
  3 .pdata         000024a8 00000003a27b7000 DATA
  4 .xdata         00002370 00000003a27ba000 DATA
  5 .bss           00000000 00000003a27bd000 BSS
  6 .edata         00036558 00000003a27c5000 DATA
  7 .idata         00001990 00000003a27fc000 DATA
  8 .CRT           00000060 00000003a27fe000 DATA
  9 .tls           00000010 00000003a27ff000 DATA
 10 .reloc         000056b0 00000003a2800000 DATA
 11 .debug_aranges 00000e20 00000003a2806000 DATA, DEBUG
 12 .debug_info    0001d059 00000003a2807000 DATA, DEBUG
 13 .debug_abbrev  00005f0a 00000003a2825000 DATA, DEBUG
 14 .debug_line    0000f1de 00000003a282b000 DATA, DEBUG
 15 .debug_frame   00003610 00000003a283b000 DATA, DEBUG
 16 .debug_str     00000cdf 00000003a283f000 DATA, DEBUG
 17 .debug_loc     000220ea 00000003a2840000 DATA, DEBUG
 18 .debug_ranges  000029c0 00000003a2863000 DATA, DEBUG`

Fortunately, for NumPy 2.2.1, this is no longer a problem for their Windows amd64 Python 3.10 wheels and was probably fixed upstream :D

P.S. This is slightly unrelated, but maybe pydistcheck's output could also recommend platform-specific commands in the _CompiledObjectsDebugSymbolCheck class to users, as it is only LLVM's objdump that can report such issues in DLLs/PE files, so that pydistcheck has more cross-platform compatibility and doesn't need to hardcode "run objdump? i.e., recommend LLVM's objdump on macOS and GNU/Linux's objdump on Linux?

I'm happy to put together a PR if you feel such a solution would be acceptable. :D

Wow thank you for the investigation and excellent write-up!
Using a different decoding sounds like a plausible way to handle this, I'd be happy to consider a PR with that switch if you'd like to submit one.

maybe pydistcheck's output could also recommend platform-specific commands ... so that pydistcheck has more cross-platform compatibility and doesn't need to hardcode "run objdump?

I don't want to try to encode that knowledge into pydistcheck's source code. I'm worried about the amount of effort it would take to make that accurate and keep it accurate. I think it's enough for pydistcheck to say, when it finds debug symbols, what command you could run in the same environment to reproduce that finding. Which is exactly what it does.
In case you haven' seen it, here's the set of commands it tries:
https://github.com/jameslamb/pydistcheck/blob/85b8af32b87eb8d9def9fe318381a1704be41aba/src/pydistcheck/shared_lib_utils.py#L27-L42
https://github.com/jameslamb/pydistcheck/blob/85b8af32b87eb8d9def9fe318381a1704be41aba/src/pydistcheck/shared_lib_utils.py#L80-L81
It probably would be faster, safer, and more reliable to forgo all of this and just directly read the various formats' symbol tables without using a subprocess call to look up and run executables on PATH... but I don't personally know how to do that reliably, portably, and without introducing additional runtime dependencies.


Key Handling: Unify Control/Command keys in bindings

Implement controlIsCommand option to listen for both Control and Command keys when using the Control key in a binding.

Closed by b87bf2a.


docs.flutter.io difficult to use on mobile

Just visited docs.flutter.io on my iPhone (Safari on iOS 10) to quickly look up an API. It is very difficult to use on mobile:

there is no search field to quickly search for something (<--- main problem)
the actual information is embedded in a strangely scrolling div
vertical scrolling is enabled even though there is no need for it
when scrolling through the hamburger menu, the page below it scrolls as well when the end of the hamburger menu is reached.

cc @sethladd
Some of these issues may be already filed (in particular I think the search field issue is filed).

Thanks for the feedback! Moved to https://github.com/dart-lang/dartdoc/issues/1469


[Masonry] spacing doesn't accept hard-coded string value

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
I tried to add spacing={'24px'} to the Masonry component but it broke the Masonry layout as seen in the image below.

If I used spacing={3} as the replacement of spacing={'24px'} for the Masonry component, the Masonry layout was fine as seen in the image below.

I always use spacing={'24px'} to the Grid component and it works as seen in the image below.

Expected behavior 🤔
The Masonry component should accept a string value for the spacing prop as stated in the Masonry API documentation here https://mui.com/api/masonry/

Steps to reproduce 🕹
Steps:

Import the Masonry component
Add spacing={'24px'} prop to the Masonry component
The Masonry layout is broken

Context 🔦
Here is the demo: https://codesandbox.io/s/github-mui-masonry-xnlub
For me, this case is not really important since I could replace spacing={'24px'} with spacing={3}.
But it could be important if someone wants to use custom spacing like 5px, 10px, etc.
Your environment 🌎

Environment
Dependencies: stated in the demo
Browser: Chrome 97
OS: Windows 11

Thanks for the report!
I will look into this :)

You're right.
But what if the user/team leader wants to create a different spacing value only for one component?
Lets' say the user/team leader wants the spacing value to be 5px or 6px (non-based) for only a single Masonry component while the rest of the components used the default spacing value (8px based) from theme.
It would be easier to add spacing='6px' alone to the component rather than creating a new ThemeProvider theme value.
I know it's not good to create a different style inside a single app but sometimes I the user/team leader wants that 😂

Hi. That wouldn't be a problem.

You can create multiple themes.
You can create a theme specifically for Masonry component to give it a specific spacing value, even though I think this is not a common use case, and wrap masonry components with ThemeProvider that uses this theme.

In my opinion, keeping the default unit to theme spacing and encouraging developers to customise theme is more healthy for several reasons

I agree that the spacing should not be hard-coded and should follow the theme spacing definition. If we have to provide an escape hatch, we should document the why and example use case.


chore(main): release iso-filecoin 1.1.0

:robot: I have created a release beep boop
1.1.0 (2023-07-21)
Features

add delegated address and eth address (852a7fb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/hugomrdias/iso-repo/releases/tag/iso-filecoin-v1.1.0 :sunflower:


Model Message, Schema and RecordBatch metadata in the NIF

This commit adds support for modelling the Message, Schema, and RecordBatch metadata (plural).
Additionally support for encoding and decoding messages, schemas and record batches as well as tests have been added.

I've never used Rustler (and honestly also Rust) for anything important before. Could you please let me know if my work so far looks good? I've got some commented code to delete, after which we could merge.
I plan to add decoding support later.

Merging as approved by @polvalente .


Uzbek translation tracking

This issue is tracking for translating Uzbek documentation.
For someone who wants to join to translate documentation to the Uzbek language, you can take a look at this issue, find out the untranslated section.
This issue will be closed when the documentation is largely translated.
There is more detail about translation in TRANSLATING guide, please read it first!
Here are some of the formats we are following:
First and the most important:
DO NOT just copy the section to google translator or something like that and paste back the result
Second, some words we are not going to translate:

bot
update
keyboard / inline keyboard
webhook/polling
payload
middleware
...(feel free to add more, but make sense)

Bu issue dokumentatsiyani O'zbek tiliga tarjima qilinishini kuzatib borish uchun.
Dokumentatsiyani O'zbek tiliga tarjima qilishga o'z hissangizni qo'shmoqchi bo'lsangiz bu issueni ko'rib chiqib, tarjima qilinmagan bo'limni topishingiz mumkin..
Bu issue dokumentatsiya to'liq tarjima qilinganda yopiladi.
Tarjima qilish haqida TRANSLATING qo'llanmasida ko'proq ma'lumot bor, oldin shuni o'qishni maslahat beramiz.
Quyida biz amal qilayotgan ba'zi bir formatlar keltirilgan:
Birinchi va eng muhimi:
Matnni shunchaki google tarjimon yoki shunga o'xshash platformaga TARJIMA QILDIRMANG
Ikkinchi, ba'zi bir so'zlarni tarjima qilish kerak emas:

bot
update
keyboard / inline keyboard
webhook/polling
payload
middleware
...(boshqa so'zlarni bemalol qo'shishingiz mumkin)

Readme

[x] README.md -> Pull Request

Advanced

[ ] deployment.md
[ ] flood.md
[x] middleware.md -> Pull Request
[ ] proxy.md
[x] README.md -> Pull Request
[ ] reliability.md
[ ] scaling.md
[ ] structuring.md
[ ] transformers.md

Demo

[ ] examples.md
[ ] README.md

Guide

[ ] api.md
[ ] basics.md
[ ] commands.md
[ ] context.md
[ ] deployment-types.md
[ ] errors.md
[ ] files.md
[ ] filter-queries.md
[ ] games.md
[ ] getting-started.md
[ ] inline-queries.md
[ ] introduction.md
[ ] middleware.md
[x] README.md -> Pull request

Hosting

[ ] deno-deploy.md
[ ] gcf.md
[ ] heroku.md

Plugins

[ ] auto-retry.md
[ ] command-filter.md
[ ] console-time.md
[ ] files.md
[ ] hydratate.md
[ ] i18n.md
[ ] keyboard.md
[ ] menu.md
[ ] parse-mode.md
[ ] ratelimiter.md
[ ] README.md
[ ] router.md
[ ] runner.md
[ ] session.md
[ ] stateless-question.md
[ ] transformer-throttler.md

Resources

[ ] comparison.md
[ ] faq.md

Is this list up to date? I see four linked pull requests, but five exist. Am I missing something? 🤔

Oh could it be that you only link things here that are already merged? There is no need for this. The idea is to link the open pull requests here so people can see which articles are in progress. Then they can join in without having to go through the complete list of pull requests first. Having links to already merged pull requests is not necessary.

Oh could it be that you only link things here that are already merged? There is no need for this. The idea is to link the open pull requests here so people can see which articles are in progress. Then they can join in without having to go through the complete list of pull requests first. Having links to already merged pull requests is not necessary.

Sorry for that. Thank you for info )

Are you still invested in this?
It's completely fine if you decide to prioritise other projects. In that case, I'd close this.

As you mentioned, we are busy with other things. Therefore, it would be appropriate to close it for now.


Add property enable-full-list

when enable-full-list is true, all group ids will  be listed.
when enable-full-list is false, it is default situation.
issue 20218

@wujack778 resolve the conflicts, or just make a new PR

/check-enforcer override


[ETL-199] Activate JSON to Paquet scheduled trigger upon creation

Interesting - these schedules don't start by default?

They're not "activated" by default. I guess that's so you can deploy scheduled triggers before you need them and then activate them once certain preconditions are met. In our case we simply want them to run right away.


Priority-Based Data Processing for Golden Record

Description
The golden record service should prioritize data sets based on predefined criteria to ensure timely and fair processing. This feature will enable the system to handle data sets with varying urgency and importance, ensuring that critical data is processed promptly while maintaining fairness across different sharing members.
Key Scenarios
Portal Registration Priority:
Data sets submitted via the portal should be processed with higher priority to ensure the Business Partner Number (BPNL) is available quickly.
Fair Share of Processing:
When multiple sharing members submit data sets, the system should ensure that smaller batches of data are not delayed excessively by larger batches. This ensures fair processing time for all members.
SLA-Based Priority:
Data sets should be prioritized based on Service Level Agreements (SLAs). If a data set has been waiting for a significant amount of time and is nearing its SLA deadline, it should be automatically elevated in priority.
Implementation Details
Priority Definition:

Introduce a priority attribute for data sets.
Priority levels can be defined as High, Medium, and Low.

Priority Assignment:

Portal Registration: Assign High priority to data sets submitted via the portal.
Fair Share of Processing: Implement a round-robin or weighted round-robin algorithm to ensure fair processing across different sharing members.
SLA Consideration: Monitor the waiting time of data sets and adjust their priority based on SLA deadlines.

Processing Logic:

Modify the golden record service to check the priority attribute before processing data sets.
Implement a queue management system that dynamically adjusts the order of data sets based on their priority.

SLA Monitoring:

Introduce a monitoring mechanism to track the waiting time of each data set.
Automatically elevate the priority of data sets that are approaching their SLA deadline.

Additional information
Contribution will be done by @dilipdhankecha2530
Committer to support this will be @SujitMBRDI / @nicoprow / @maximilianong

This feature still needs a decision from the expert group - main question:
Is it ok that the orchestrator knows about which data comes from which gate?

We had a brief discussion about this and the expert group suggested a good idea:
What if we assign the gate to a category rather than a specific company, and then define the priority based on that category? @dilipdhankecha2530 What do you think?

Another discussion took place today:
Categorization could probably help us with prioritization, but not with determining the confidence value. For example, we need to know in how many gates the same dataset appears.
There is also no general rule that the orchestrator is not allowed to temporarily know where the dataset comes from.
Of course, it should not be stored in a central database which pool data belongs to which company, but it is necessary for processing through the orchestrator.

Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)

Please add missing sections from feature template

@maximilianong One application for the priority is giving tasks coming from the Portal registration priority. Should this priority be assigned to all tasks coming from the Portal-Gate or just tasks that are for the registration? For example, normal CX-Users manage their data over the Portal-Gate, should these data also have higher prio than the data provided by sharing members over their own gates?


test: Disable GCE PD tests

Our tests are run on AWS.
This will fix issues we are seeing in #2104.
@umohnani8 @haircommander ptal.
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

LGTM, assuming it passes the tests :)