Update org.eclipse.equinox.app to 1.5.0

Updates org.eclipse.platform:org.eclipse.equinox.app from 1.4.500 to 1.5.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.eclipse.platform", artifactId = "org.eclipse.equinox.app" } ]

labels: library-update, semver-minor

Codecov Report

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

@@           Coverage Diff           @@
##           master     #782   +/-   ##
=======================================
  Coverage   82.71%   82.71%
=======================================
  Files          73       73
  Lines        5376     5376
  Branches      145      145
=======================================
  Hits         4447     4447
  Misses        929      929

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 00c1729...9ff7387. Read the comment docs.


signalR.HubConnectionBuilder is not a constructor

Running the sample here
https://github.com/aspnet/Docs/blob/live/aspnetcore/signalr/hubs/sample/wwwroot/js/chat.js
gives the error in the title in Chrome, Edge and FireFox. The connection is started succesfully with a UWP client instea dof teh WPF sample, the Server is the one from the sample.
Any idea how to solve this?

What version of SignalR are you using?
The HubConnectionBuilder code looks correct to me

Microsoft.AspNetCore.SignalR 1.0.0 on the server

It seems to be an issue specific to the chat.js (?)

Have you copied the signalr.js file and added the script tag for it? See the Getting Started doc for more information there. The samples do not include a copy of the signalR.js file itself (since it would get out-of-date very quickly), so you need to install it yourself.
I'd suggest following the Getting Started doc before jumping in to other samples, since most of those docs assume you're familiar with the Getting Started content.

Yes it is included and the location is correct, SignalR id undefined otherwise in Chrome's console
<script src="~/lib/signalr/signalr.js"></script>

OK the sample was referencing chat.js in the index.cshtml file, but there is another one which works and is present
<script src="~/js/es5-chat.js"></script>
The sample docs are outdated but thanks.


Recreate summaries when detected missing

Fixes vector-im/element-ios#5924
Also maybe a fix for vector-im/element-ios#6006

Is this the same issue when you have the room but the summary is nil?
And does this fix the mentioned issue?
Thanx in advance.


refactor stimulus_reflex.js

While this PR will seem radical and a little intimidating at first glance, no features have been added. The PR file view is likely only useful to see how I split the project up; you really need to pull it down and test it out.
I was very intentional about making commits at meaningful junctures so I could "show my work" as the teachers said. I had my comprehensive CableReady test harness open and running during the process, always checking each step that everything seems to be working.
Isolation Mode is working fine. You'll see that it has been pulled into a file which can be conveniently removed for v4.
There are no more local variables. What used to be window.reflexes is now reflexes (eg. same API, different storage).
I started the process of treating ActionCable like an adapter. There is a new javascript/transports folder. Since I was committed to not changing functionality, there is still AC-specific code in the register function, but it is now self-evident where the offending code is and extracting it will not be difficult. I did remove the old consumer.js; it is almost certainly vestigal at this point; there's never been any documentation encouraging people to attach their consumer to window, and all tasks/generators pass consumer into the options of initialize. Most significantly, I've not seen or heard of anyone doing it in 18 months of daily support. Considering it was generating deprecation errors in Chrome (since it prods every member of window) and we have application.consumer support coming in, I figured that it was time to sunset that particular history.
I also took the opportunity to merge what used to be extendStimulusController into register. Whatever reason there used to be to keep them separate is no longer in play.
In conclusion, while the SR client is still involved and there's lots to be done to refactor stimulate into more manageable, testable chunks, I believe that this PR makes the codebase substantially easier to reason about. Not coincidentally, it makes it feel much more like a Stimulus controller instead of a jumble of functions that only two people can follow without frustration.
Why should this be added
Code clarity and maintainability. Preparation for pluggable transport mechanisms.
Checklist

[x] My code follows the style guidelines of this project
[x] Checks (StandardRB & Prettier-Standard) are passing
[x] This is not a documentation update

This looks great on cursory review. I definitely want to test some things locally. Is your comprehensive CableReady test harness publicly available? I'd love to start using it.

This looks great on cursory review. I definitely want to test some things locally. Is your comprehensive CableReady test harness publicly available? I'd love to start using it.

I would be thrilled for others to make use of my test harness for CR.
Note that there's lots of stuff commented out for PRs that haven't necessarily been approved, yet.
Just switch to the cr_tests branch of stimulus_reflex_harness:
https://github.com/leastbad/stimulus_reflex_harness/tree/cr_tests


Speedtest Fail - starting yesterday the 21st

been working like a charm - and then its over - happily talking to my influx db - but seems to be unhappy with ookla -- their client change or something?

Same here, can't seem to figure out why.  Tried to change LOG_TYPE environment variable to "debug" to see more detail but nothing.

Same here, can't seem to figure out why.  Tried to change LOG_TYPE environment variable to "debug" to see more detail but nothing.
Considering a switch over to this: https://github.com/alexjustesen/speedtest-tracker

Are you running this container in unraid?
I've been seeing some odd ssl errors that (according to a separate thread) seem related to the docker version
I'm running unraid 6.12.1 and everything is up to date and current etc

Nope, I'm running it atop an Ubuntu VM on Proxmox

Damn - rules out that theory
I should spin up a vm on my proxmox box and install this see if it talks
Maybe my aggressive rules on my local network are screwing things up
Did you see any ssl errors in your logs?
TJV
On Jun 23, 2023 at 19:18 -0700, chrisweis @.***>, wrote:

Nope, I'm running it atop an Ubuntu VM on Proxmox
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Which logs are you seeing the SSL errors?  No SSL errors in my docker logs.  I have:
{"log":"2023-06-24 01:44:25,819 [INFO] Speedtest CLI data logger to InfluxDB started...\r\n","stream":"stdout","time":"2023-06-24T01:44:25.819485356Z"}
{"log":"2023-06-24 01:44:25,839 [INFO] Ping data written successfully\r\n","stream":"stdout","time":"2023-06-24T01:44:25.83961178Z"}
{"log":"2023-06-24 01:44:25,861 [INFO] Manual server choice : ID = 10162\r\n","stream":"stdout","time":"2023-06-24T01:44:25.861743637Z"}
{"log":"2023-06-24 01:44:25,861 [INFO] Speedtest Failed :\r\n","stream":"stdout","time":"2023-06-24T01:44:25.86180898Z"}
{"log":"2023-06-24 01:45:25,900 [INFO] Ping data written successfully\r\n","stream":"stdout","time":"2023-06-24T01:45:25.901179612Z"}
{"log":"2023-06-24 01:46:25,969 [INFO] Ping data written successfully\r\n","stream":"stdout","time":"2023-06-24T01:46:25.969823677Z"}

Looks like it stopped working for me 2023-06-21 13:30 (US Pacific):

I’ll check mine tomorrow and post the ssl errors
On Jun 23, 2023 at 20:01 -0700, chrisweis @.***>, wrote:

Looks like it stopped working for me 2023-06-21 13:30 (US Pacific):
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

2023-06-23 20:48:32,590 [INFO] Speedtest Failed :
2023-06-23 20:48:32,591 [DEBUG] b'[2023-06-23 20:48:32.588] [error] Configuration - SSL connect error (UnknownException)\n[2023-06-23 20:48:32.589] [error] Configuration - Cannot retrieve configuration document (0)\n[2023-06-23 20:48:32.589] [error] ConfigurationError - Could not retrieve or read configuration (Configuration)\n[2023-06-23 20:48:32.589] [error] ConfigurationError - Could not retrieve or read configuration (Configuration)\n{"type":"log","timestamp":"2023-06-24T03:48:32Z","message":"Configuration - Could not retrieve or read configuration (ConfigurationError)","level":"error"}\n'
2023-06-23 20:48:32,591 [DEBUG] b''```

my last successful pull was 6/21 0930 Pacific

I started having the problem on the same date...  Just switched over to https://github.com/alexjustesen/speedtest-tracker in a docker container. Be aware - the new speedtest-tracker is API or Influx 2.0 only. out of the box it seems like traditional username / password authentication to in Influx database is not an option, it is key only. I will work , but will not provide the same functionality of speedflux

@mattdymes i've avoided using that because i'm resisting upgrading myinfluxdb - i'm still running ... 1.8 i think

@mattdymes but the graphs the guy has set up as default are nice - i suppose it would replace my grafana dahsboard

UnRaid guy here.  yep, Mine started failing as well.

looks like the sppedtest-tracker thats been linked here a few times has plans to support influxdb v1 - i'm probably bailing on speedflux - repo doesn't appear to be maintained and i'm too lazy to troubleshoot when there are other working options

This thread helped me upgrade my v1 to v2 using a Docker container: https://community.influxdata.com/t/problem-backup-1-8-restore-2-6/28943
Hypothesis I considered but didn't test: Did Ookla Speedtest increase the maximum frequency of tests, and that began causing it to fail?  Would a decrease to only hourly fix the old Speedflux? 🤔

Nah that's not it. I only test once a day, and mine have been failing consistently too

Would a decrease to only hourly fix the old Speedflux? 🤔

i only ran my speedflux once ever 2 or 3 hours - so i don't think its ookla rate limiting

Looks like a case of horribly updated speedtest binary, the image was last published almost 2 years back (https://github.com/breadlysm/SpeedFlux/pkgs/container/speedflux). Manually upgraded to latest speedtest binary from ookla (https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-x86_64.tgz) after exec'ing into the container, replaced the binary in /usr/bin/speedtest and speedtests are working fine now.
This will not persist across container updates (but that does not seem to be an issue at this point)

There's a fork that's regularly updated

slick - i was just about to fork it and take a whack up making the update - let me know if that works as a drop in replacement

Looks like a case of horribly updated speedtest binary, the image was last published almost 2 years back (https://github.com/breadlysm/SpeedFlux/pkgs/container/speedflux). Manually upgraded to latest speedtest binary from ookla (https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-x86_64.tgz) after exec'ing into the container, replaced the binary in /usr/bin/speedtest and speedtests are working fine now.
This will not persist across container updates (but that does not seem to be an issue at this point)

Edit: There's a fork that's regularly updated (https://hub.docker.com/r/dontobi/speedflux.rpi), will test it over the weekend and migrate if it's a drop-in replacement.

This worked for me . Downloaded the file, unpack put in it a director and added that directory as a resource to the docker container, then went into the container consol and copied speedtest to the /usr/bin to replace existing one, restarted container it started working

Oddly enough mine started working again overnight.

I just reinstalled and tested and its working again
On Jun 29, 2023 at 05:00 -0700, funnelcloudservices @.***>, wrote:

Oddly enough mine started working again overnight.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Yup, mine has also just randomly started working again. No changes, no updates.

Looks like a case of horribly updated speedtest binary, the image was last published almost 2 years back (https://github.com/breadlysm/SpeedFlux/pkgs/container/speedflux). Manually upgraded to latest speedtest binary from ookla (https://install.speedtest.net/app/cli/ookla-speedtest-1.2.0-linux-x86_64.tgz) after exec'ing into the container, replaced the binary in /usr/bin/speedtest and speedtests are working fine now.
This will not persist across container updates (but that does not seem to be an issue at this point)

Edit: There's a fork that's regularly updated (https://hub.docker.com/r/dontobi/speedflux.rpi), will test it over the weekend and migrate if it's a drop-in replacement.

I've made a PR to the effect of changing the binary even though it's unlikely to be merged as this project is unfortunately so inactive - if you need a drop-in replacement for unraid then for now you're welcome to build an image of your own or use my repo at https://hub.docker.com/repository/docker/sethwv/speedflux/


License Clarification Flipped Fillet

@demseyk nice work on the Flipped Fillet design, could you please advise on which specific Open Source license (e.g. MIT/CC by SA/etc.) you're releasing your work under?
https://github.com/sqfmi/watchy-cases/tree/main/Flipped Fillet

@darigovresearch The Flipped Chamfer Design and Flipped Fillet Design are both released under the MIT license.

Thanks @demseyk, pull request https://github.com/sqfmi/watchy-cases/pull/38 should resolve this issue if you're happy with it


RuntimeError: CUDA error: the provided PTX was compiled with an unsupported toolchain.

When I want to load the weight like this,
net = torch.load(pthfile)
I got this error:
RuntimeError: CUDA error: the provided PTX was compiled with an unsupported toolchain.
I don't know what happened. After Google, it seems that I need to update my CUDA driver.  Are there any other options?

Have you tried to load the weights to cpu first?
net = torch.load(pthfile, map_location="cpu")

Thank you very much. The weight could be loaded on the CPU. However, I still can't get the embedding of the protein. My code is as follows:
device = torch.device("cpu")
graph_construction_model = layers.GraphConstruction(node_layers=[geometry.AlphaCarbonNode()],
edge_layers=[geometry.SpatialEdge(radius=10.0, min_distance=5),
geometry.KNNEdge(k=10, min_distance=5),
geometry.SequentialEdge(max_distance=2)],
edge_feature="gearnet")
protein = data.Protein.from_pdb('4k0e_C.pdb', atom_feature="position", bond_feature="length", residue_feature="symbol")
protein = data.Protein.pack([protein])
protein = graph_construction_model(_protein)
gearnet_edge = models.GearNet(input_dim=21, hidden_dims=[512, 512, 512, 512, 512, 512],
num_relation=7, edge_input_dim=59, num_angle_bin=8,
batch_norm=True, concat_hidden=True, short_cut=True, readout="sum")
gearnet_edge.load_state_dict(torch.load('mc_gearnet_edge.pth', map_location=device), strict=True)
gearnet_edge.eval()
print(protein_.node_feature.float().shape)
print(protein_)
with torch.no_grad():
output = gearnet_edge(protein_, protein_.node_feature.float(), all_loss=None, metric=None)
print(output)
I get an error like this:
Traceback (most recent call last):
File "GearNet/MC_gearnet_edge.py", line 45, in
output = gearnet_edge(protein_, protein_.node_feature.float(), all_loss=None, metric=None)
File "/GearNet/lib/python3.7/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "GearNet/lib/python3.7/site-packages/torchdrug/models/gearnet.py", line 96, in forward
hidden = self.layers[i](graph, layer_input)
File "GearNet/lib/python3.7/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "/GearNet/lib/python3.7/site-packages/torchdrug/layers/conv.py", line 91, in forward
update = self.message_and_aggregate(graph, input)
File "GearNet/lib/python3.7/site-packages/torchdrug/layers/conv.py", line 835, in message_and_aggregate
return update.view(graph.num_node, self.num_relation * self.input_dim)
RuntimeError: shape '[942, 147]' is invalid for input of size 19782
It seems that the "GeometricRelationalGraphConv" want to convert the feature into a specific shape, but the conversion failed.
what should I do?

Hi, I guess that it's because you forget to transform the protein in to residue view so that we will pass residue_feature instead of atom_feature as node_feature. In the tutorial, we define the transform at the beginning and use it for processsing batches. In your case, where you only want to process one protein, you can simply set protein_.view = residue.

Yes, you are right, now I can get the embedding of the proteins.
Thank you very much!


Docs/Improve API documentation

Summary
Used SwaggerHub to create API documentation: https://app.swaggerhub.com/apis-docs/yolo-bouldering/routemaker/1.1.2
.json and .yaml versions of API also available.
CI added for auto-deployment of GitHub pages. Example: https://hughjazzman.github.io/yolo_bouldering
Closes #73.

Thanks wira! Looks really good.

Let's rename the original documentation to API Documentation V1.1.2 (deprecated).pdf
Let's remove the yaml file as we do not want two sources of truth (yml, json). (Another way is to keep the yaml and delete the json while regenerating the json in the CI pipeline but I think we will have to rely on more dependencies)
Rename the json to swagger-1.2.json and change pattern in swagger.yml to swagger-*.json  as we may want non-swagger json files in docs directory.


Change back to flush more often

I removed flush to have a better response for auto code completion, but decided to add back to make the chat response more smooth.


merge: urql auth to project list

Description
Merges an implementation of the project list with urql authentication and proper data fetching into the branch containing styles and dummy data.

Adds local development server baseURL
Adds getToken() function to pluck token from localStorage and authenticate endpoints
Moves dummy data to backend for communication testing between client and server

Type of change

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Change Status

[x] Complete, tested, ready to review and merge
[x] Incomplete/work-in-progress, PR is for discussion/feedback

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

I am creating this pull request for my own branch and merging into my own changes.


Option to save new password that has just been typed

It would be nice if the extension would have an option that automatically offers to save the new passwords the users just typed, and which are not still in the database. Like this we would not need to open the password database using an external editor, each time we create a new password.

This functionality is not planned at this time.


doctests: fix step names

Description
This PR patches up some doctest step names in comments only (no code changes).

@sjpotter Please review and merge. Thank you!

Thank you, @sjpotter ! Much appreciated.


[SPM] Fix invalid exclude of "tools" directory

#7624 - Fix warning introduced in Xcode 13.1 by removing invalid exclude of non-existent "tools" directory from Realm target in Package.swift.

Looks like the "tools" directory was removed in this commit: 8d8a2801


Switch Flashback record and replay to use BSON instead of JSON

Addresses https://github.com/ParsePlatform/flashback/issues/31 - which affects $hint, $orderby, $nearSphere, $geoWithin, etc - basically anytime mongo cares about ordering of keys in an operation. This is caused by two things:

when python dumps to JSON, keys are written alphabetically, which can break ordering
Ordering of go maps is non-deterministic, thus when we unmarshal JSON into a map, we sometimes lose order.

By switching to BSON as the recording format, we can write documents in their original order in the record tool and unmarshal into bson.D objects and preserve order in the replay tool.

:shipit:


Split text metrics into text and speech metrics.

🚀 Enhancement
Split text metrics into text and speech metrics.
Motivation
Currently, both text and speech metrics are all stored under text metrics. However, I think there are some good reasons why they should/may be split into two categories:

Text and speech are two different modalities
For text metric evaluation, we allow evaluating a hypothesis against multiple references. However, there is always a single reference for speech.
Also I think it might be a bit confusing for newcomers into NLG/speech which metrics are used for which modality.

Pitch
Split text metrics into text and speech metrics. Otherwise, leave everything as it is.
Alternatives
Keep it as it is.
@Borda @SkafteNicki What do you think about it? :]

Text and speech are two different modalities

could you pls elaborate more on the difference as we would also need to make such an explanation in docs...

Is there a difference between speech and audio?

It seems to me that, for now, speech metrics consume text inputs while audio ones consider tensor inputs

speech metrics consume text inputs while audio ones consider tensor inputs

yeah, but if speech has input text, why not keep it as text?

@Borda I also see the difference that text predictions can be naturally compared against multiple references, which is not the case for speech (at least I guess)... However, I have no strong opinion on this for now so we can definitely leave it as it is :]

well, I think that with this we go into too many details and we could also talk about if binary and multi-label classification shall be in a single package... :rabbit: lest put it on hold and reopen later if we have more reasons for such split... :angel:

well, I think that with this we go into too many details and we could also talk about if binary and multi-label classification shall be in a single package... 🐰 lest put it on hold and reopen later if we have more reasons for such split... 👼

yep, agree :]


Add option to allow console redirect in ESXi bootstrap

In many rack mount servers or customized servers, there is no monitor connected, UART port are usually used as console. VMware ESXi use VGA card as console. User need pass VM kernel To support this use, I add three options: "gdbPort","logPort","debugLogToSerial".
VMware ESXi reference
To support this , 'on-http/data/templates/esx-boot-cfg', 'on-http/data/templates/esx-ks'(This PR) and 'on-tasks/lib/task-data/tasks/install-esx.js'(in another PR for on-tasks) are changed.
The default value of those options keep console in VGA as it does before. User can customize the console redirect setting in the OS bootstrapping payload.
Jenkins depends on https://github.com/RackHD/on-http/pull/636

@pengz1 @iceiilin @anhou @yyscamper

@nortonluo : Please also update the schema file: https://github.com/RackHD/on-tasks/blob/master/lib/task-data/schemas/install-esxi.json and its unit-test: https://github.com/RackHD/on-tasks/blob/master/spec/lib/task-data/schemas/install-esxi-spec.js

Will these default settings misbehave in other HW platforms when installing ESXi?

@iceiilin Those parameters are kept in ESXi default value by default. That is the same as the value before this PR. I Just test this (change parameters or not) on Rinjin, it is OK.

BUILD on-tasks #74 : FAILURE

BUILD on-tasks #74  Error Logs  ▼Test Name: install-esxi-spec.js schema negative set testing should violate the schema if gdbPort="ttys0"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
    at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:81:20)
    at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:134:17)
    at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:214:26)
Test Name: install-esxi-spec.js schema negative set testing should violate the schema if debugLogToSerial="3"
Error Details: expected schema violation, but get conformity.
Stack Trace: Error: expected schema violation, but get conformity.
at validateData (spec/lib/task-data/schemas/schema-ut-helper.js:81:20)
at SchemaUnitTestHelper._validate (spec/lib/task-data/schemas/schema-ut-helper.js:134:17)
at Context.<anonymous> (spec/lib/task-data/schemas/schema-ut-helper.js:214:26)

Please also update schema file here (not only schema unit test) https://github.com/RackHD/on-tasks/blob/master/lib/task-data/schemas/install-esxi.json

Please make sure to update document in:
http://rackhd.readthedocs.io/en/latest/rackhd/install_os.html


Extra service provider in module

Hi,
Is it possible to add an extra service provider in the module?
I've tried to use providers() function in my module's service provider, but it seems to be never called:
    public function provides()
    {
        echo 123;
        exit();
        return [];
    }

Hi,
Yes, you can add as many service providers as you wish in a module.
After adding the provider you need to tell laravel about it. One way to do this is by adding it to the providers key in the module.json file.

It works. Thanks.


Thecodereule patch 1

a small patch

Yes @thecodereule
I don't see why this PR is for ?
Please add the Description or else it would be closed.

What is that? and why was this line of code added? .
I think you need to describe it in the PR description.

In my last PR I left the
"dev": true,
"requires": {}
which is an NPM configuration of a development build. so I removed it and made a new PR

recommit of my last PR for issue https://github.com/Vijaykv5/SnapGrid/issues/92
In my last PR I left the
"dev": true,
"requires": {}
which is an NPM configuration of a development build. so I removed it and made a new PR


initial snapcraft

wip PR

Please note: the initial issue (https://github.com/diginex/geewallet/issues/15#issuecomment-440729236) talks about the GTK frontend, which is in the branch "frontend", not in "master".

thanks! @knocte

@knocte are the build instructions the same? what else is important to know

Sorry for the delay replying, somehow I missed your messages (no notifications showed up).
Build instructions are slightly different: you need newer version of Mono (5.x) that can compile .NET Standard libraries. All boils down to what you can see in the gitlab CI yml file, the "newmono_build" pipeline (that pipeline in fact generates a zip file as an artifact).
However, take in account that the binaries generated by this build do not depend on a newer Mono (they don't even depend on F#!), so they can run normally in a normal (stock) Ubuntu 18.04 with mono packages installed.
Let me know if you have any more questions!

@knocte let me see what I can do

@JeremiGendron ping
If you're stuck I'm happy to answer any questions to try to help you.

I am not working on this anymore, I failed to understand exactly what it is
you wanted.
On Tue, Dec 11, 2018, 11:59 AM Andres G. Aragoneses <
<EMAIL_ADDRESS>wrote:

What do you mean with an opening?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/diginex/geewallet/pull/16#issuecomment-446278628, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWfqZWxw7kA4mYtlra0AMW4d5gaSxMSaks5u3-SLgaJpZM4YtfND
.


Add Google Tag Manager snippet

Google Tag Manager (GTM) can be included on all pages of the app by configuring the following environment variables:

GOOGLE_TAG_MANAGER_ID
GOOGLE_TAG_MANAGER_AUTH
GOOGLE_TAG_MANAGER_PREVIEW

All three variables are optional.
If none are set, GTM will not be included on the page.
If only GOOGLE_TAG_MANAGER_ID is set, the default environment of the GTM container will be used.
If GOOGLE_TAG_MANAGER_AUTH and GOOGLE_TAG_MANAGER_PREVIEW are set, the specified GTM container environment will be used. This is used for managing the rollout of changes to integration so they can be tested before rolling out to production.
trello card: https://trello.com/c/Wcuq3R1S/2167-add-ga4-page-view-tracking-to-apps-that-we-own

Ah yes you did mention it! I'll add it in!
Thank you! I'll check the other PRs tomorrow as well


Fix inner link for getDerivedStateFromError

Fixed the inner link for getDerivedStateFromError on react-component page

@kkowalczuk thank you, but already fixed!


update supercloud.md and fix predicate command on our superclouds

dont forget to update launch_slack_bot.py

after looking at this more, I suspect the issue was related to some stuff in my own bash profile that others shouldn't have. if weirdness arises again (it will be obvious) then we'll take another look.


docker: Added labels to dockerfile for RH certification

docker: Added labels to dockerfile for RH certification.
We mapped the labels with the release Readme documentation in the following way -
name = RepositoryName: "intel-data-center-gpu-driver-container"
version = DriverVersion: "0.1.0"
release = KernelVersion: "4.18.0-372.40.1.el8_6.x86_64"

The PR looks good to me


Update doc to include the use of travis gem to encrypt the repo_token

Ref. https://docs.travis-ci.com/user/code-climate/

Hi @quimarche,
We don't consider the Code Climate repo token secret. It is used only to submit test coverage data and can be safely committed directly into a public CI configuration file. This token is not authorized to access any data within a Code Climate account or its repositories.
We have a longer answer here on our docs site.
You're free to encrypt the value if you wish but we don't consider it a required step.


[7195] Add Support for application_id in the API

Context
We want to allow users of the API to send an application_id when creating or updating a trainee. This refers to the ID given to a trainee's application after going through the Apply system. Initially we thought that we needed a new column on the trainees table to support that, and the Trello ticket was initially to do that.
But we noticed that we already have several references to an apply_id of some kind in different parts of the app. So we wondered if we could just use one of those instead. Here are the columns we currently have:

Table
Column

trainees
application_choice_id

apply_applications
id

apply_applications
apply_id

apply_applications
application_choice_id

hesa_students
application_choice_id

After running some database queries on production, we found that apply_applications.application_choice_id has no values in it at all. So this PR drops that column to avoid some of this confusion in the future.
On the apply_applications table, the ID is unique to register, but it looked like the apply_id had the value that we want.
The application_choice_id on the trainees table seems to correspond to either an apply_application record or a hesa_students record. Both of these have application_choice_id columns and my understanding is that the values there will be the same as that stored on the trainee.
Changes proposed in this pull request
At the very least, it looks like we'll need to save the application_choice_id on the trainees table. So this PR takes an application_id value sent through the API, and maps it to that column. It then returns that new value with the trainee in the response.
Next steps
From here, we'll need to decide how we join this up with the apply_applications and the hesa_students table.

Under what circumstances do we lookup an apply_application record or a hesa_student record and make a connection with the trainee?
Should the apply_application records or hesa_student records already exist when a trainee is created? Are there some cases where we'll need to create those records at the same time as the trainee?
We currently have a mechanism for creating a trainee from an apply_application record. If we're given an application_id when a trainee is created, do we create the trainee from the application, or override that with whatever has been provided through the API? Which data takes precedence?

Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?
[ ] Do we need to send any updates to DQT as part of the work in this PR?
[ ] Does this PR need an ADR?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

I also need to work out how to update the new docs (the OpenAPI yaml definitions).

@stevehook Yeah, they are currently broken but Chris has worked on a fix for them.


Add QA MarkdownLinks Test

This PR adds the QA MarkdownLinks test from the DscResource.Tests module.

This change is

Can you resolve the conflicts in this one @X-Guardian ?

@X-Guardian Great work! Just a tiny fix then this is ready to be merged.  😄


macOS: call to undeclared function '_NSGetExecutablePath'

Nuitka 1.6.3 and some versions before fail to compile on macOS due to a missing include in HelpersFilesystemPaths.c:
In file included from static_src/CompiledFunctionType.c:2864:
In file included from /Users/ben/Library/Caches/pypoetry/virtualenvs/myapp-NW6c3THU-py3.11/lib/python3.11/site-packages/nuitka/build/static_src/CompiledCodeHelpers.c:70:
/Users/ben/Library/Caches/pypoetry/virtualenvs/myapp-NW6c3THU-py3.11/lib/python3.11/site-packages/nuitka/build/static_src/HelpersFilesystemPaths.c:40:15: error: call to undeclared function '_NSGetExecutablePath'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    int res = _NSGetExecutablePath(binary_filename, &bufsize);
              ^
1 error generated.

I am re-creating this issue for others who google for it as my original one seems to have been accidentaly deleted by the maintainers. The issue has already been fixed in 15b5d37d1010b36e638d3facbbaec0143daaff2c so I will close immediately after opening.
Workarounds are:

Install factory version
pip install -U https://github.com/Nuitka/Nuitka/archive/factory.zip

Add the following lines to the top of HelpersFilesystemPaths.c:

#if defined(__APPLE__)
#include <mach-o/dyld.h>
#endif

Fixed in 15b5d37d1010b36e638d3facbbaec0143daaff2c

I never reproduced this, and you never produced anything that would have allowed this, so I deleted it as noise, esp. as it referred to a factory state, which is explicitely asked to not report to the general tracker, but via Discord or not at all.
The error you describe was never observed, and you are wasting my time by pretending to report against 1.6.3 and then quoting an error line that doesn't exist in its code. So you wasted my time now. I am telling you, for the last time. Because also this applies:
In the template, I have made it clear, that not filling out the issue template is not acceptable. I am closing this kind of report as invalid. The main reason is that I do not want to be left guessing. For you it's easy to erase the issue template and expect me to ask you questions only as necessary, but I cannot do that. I would much rather wait for you to create a new report, fill out the template, or wait for somebody with the necessary skill to do it.
In short: No issue template, no fun. Therefore I am likely just deleting the issue, as it serves as a bad example and detraction for searches.  And even worse, it might keep good reporters from reporting as is this "already known."

Hi @kayhayen
I was under the impression that the original issue included every information requested by the template when I removed the template itself. I am very sorry if I missed something critical but I can assure you that I have put a lot of effort into the issue to make sure it is useful and helps making nuitka even better for everyone.
Before creating the issue I also made sure that it also occurs on a very simple project with a single hello world file, is present on different machines and that it was not already fixed in the latest development release as suggested in the template and is just common sense. I am sorry for not mentioning that it also exists in the stable release. That would have helped I guess. But as most projects prefer to only get issues that are present in the latest main branch I guess I was just used to leave this info out. This was corrected in the second issue but as I saw it was already fixed I then left out critical information like the macOS version and other details. Rest assured, that at no point I intended to waste anyones time. Quite the opposite is true in fact.
Just deleting it was perceived as very rude at first, hence why I assumed it must have happened by accident. But I also understand that having to handle too many low effort issues is very tiring and that it might have just cought you on the wrong foot. So no offence taken.
While further reasearching this, I found that on one of my machines the issue is not present and after digging through the differences in between those machines I think I have found the one detail that is needed to reproduce it:
LLVM version 16.0.5 installed through homebrew.
/opt/homebrew/opt/llvm/bin/clang --version
Homebrew clang version 16.0.5
Target: arm64-apple-darwin22.5.0
Thread model: posix
InstalledDir: /opt/homebrew/opt/llvm/bin

As opposed to the clang version 14.0.3 which nuitka would have used otherwise:
clang --version
Apple clang version 14.0.3 (clang-14<IP_ADDRESS>.1)
Target: arm64-apple-darwin22.5.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

After uninstalling it, the hello world compiled as expected.
For the sake of completeness I might add that the machine I am currently testing on runs macOS 13.4 and Python 3.11.4 installed using the installer from python.org.
Nuitka version info:
python -m nuitka --version
1.6.3
Commercial: None
Python: 3.11.4 (v3.11.4:d2340ef257, Jun  6 2023, 19:15:51) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
Flavor: CPython Official
Executable: /Users/ben/Library/Caches/pypoetry/virtualenvs/bla-F7d9cPuG-py3.11/bin/python
OS: Darwin
Arch: arm64
Version C compiler: /opt/homebrew/opt/llvm/bin/clang (clang).

Yes that piece of info might have given a clue to what the issue might be. Even as it is missing the clang version. Sorry again for missing this in the first place. As this is not happening on the latest factory release anymore, I guess the issue can remain closed.

If I had seen this one, it would have been very relevant, I don't think you had this before.
Sorry if I gave you a hard time. Understand where I am coming from, people with skills, no skills, respect and no respect. There is a reason I am asking for the information in the issue template:

Version C compiler: /opt/homebrew/opt/llvm/bin/clang (clang).

That is just plain different from what Apple does. Homebrew in general is supposed to work somewhat. It limits the platforms that are going to work, over what CPython and Anaconda do. And I am not sure it builds things in a ways that match what PyPI does well enough anyway. When using poetry to install things, it's probably not going to matter much. I wonder if "Flavor: CPython Official" is a misdetection there or if this is really a Homebrew Python, but maybe not recognized as such.
Question I have to myself, if Nuitka should accept the homebrew clang at all, or skip it. On macOS, the one from Xcode is probably the one to use in all cases. I don't see why we would want to use it. And in your case, it may even be non-intentional. Maybe it has less capabilties, or ties things closer to Homebrew than necessary, or maybe it's the same. It either way would appear to be unnecessary.
I think about the deleting, I explained myself. Bad precedent is seen by others. And people starting posting they have "the same" issue when in fact neither do they, nor do they know what issue it is, and that happens sometimes years later, where good reports with issue templates would be actually needed. And where they don't, they tend to think, it's not needed, but that's often not the case.
Clever people deciding what I need, and not so clever people being lazy are indistinguable from my point of view. There is always a new chance for those that care to improve. I write a template comment before I delete, which explains that.
For me, time is limited. I do not really want to guess anything. And when I find repeatedly that information is missing, like in this instance, I make it output the compiler chosen, because it matters. Clever people know it doesn't matter. Cleverness is wasting my time. In my mind, really clever people just paste the information I am asking, even if it shouldn't matter, because they need to help me to do it. Need to make a posting like this.

I think, this issue should be about avoiding to use Homebrew clang, and enforce Xcode clang, at least by default. I need to figure out how to best to that. It lives in a couple of places I believe.


[VL] Support shared openssl lib to enable FIPS

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
(Fixes: #ISSUE-ID)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@FelixYBW


Fix CoT_sensor.xml to be CoT_sensor.xsd.

FYI @pHill5136 @Esri/arcgis-defense-solutions

Thanks @bradh!


Support for preferredPeakBitRate & preferredMaximumResolution

Useful for HLS video formats if you want to manually control video quality from available master HLS playlists or for other scenarios.
https://developer.apple.com/documentation/http_live_streaming/example_playlists_for_http_live_streaming/creating_a_master_playlist

@kamrankhan07 thanks! 🙌


Make the Changelogs badge bulletproof

Previously, it suffered from the same state caching issues as other Pusher-powered things that could also be interacted with (opening, for instance, the Organizations dropdown, would cause it to use the cached state), this updates it to act correctly in all cases.
It also makes it a relay container which accepts the isMounted variable from its parent, so that it can force an update of only its data set whilst also being updated on-mount without triggering a separate request for its data!

I think the footer has a changelog number as well?

It does, but it’s managed separately, and doesn’t actually hook up to Pusher!


[SPARK] support delta and iceberg for Spark 3.5

Problem
👋 Thanks for opening a pull request! Please include a brief summary of the problem your change is trying to solve, or bug fix. If your change fixes a bug or you'd like to provide context on why you're making the change, please link the issue as follows:
Closes: #ISSUE-NUMBER
Solution
Please describe your change as it relates to the problem, or bug fix, as well as any dependencies. If your change requires a schema change, please describe the schema modification(s) and whether it's a backwards-incompatible or backwards-compatible change, then select one of the following:

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
One-line summary:
Checklist

[ ] You've signed-off your work
[ ] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[ ] Your change contains a small diff and is self-contained
[ ] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

Codecov Report

Merging #2211 (21c4c87) into main (024c948) will decrease coverage by 18.18%.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@              Coverage Diff              @@
##               main    #2211       +/-   ##
=============================================
- Coverage     81.45%   63.28%   -18.18%
  Complexity      125      125
=============================================
  Files            90       31       -59
  Lines          3796      463     -3333
  Branches         33       33
=============================================
- Hits           3092      293     -2799
+ Misses          665      131      -534
  Partials         39       39

see 59 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@pawel-big-lebowski I believe this is outdated with moving those to vendors and separate integrations.


demo: capability matching on vm sizes

Codecov Report

Merging #12 (cf507eb) into main (4fdc922) will increase coverage by 0.81%.
The diff coverage is 78.78%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   71.58%   72.40%   +0.81%
==========================================
  Files           5        6       +1
  Lines         278      308      +30
==========================================
+ Hits          199      223      +24
- Misses         79       85       +6

Impacted Files
Coverage Δ

match.go
76.66% <76.66%> (ø)

sku.go
74.00% <100.00%> (ø)

cache.go
65.71% <0.00%> (+0.95%)
:arrow_up:

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 4fdc922...cf507eb. Read the comment docs.


New pattern: aws-service-catalog-product-version

Create a versioned AWS Service Catalog Product
Use Case

Simplify the interface to CfnCloudFormationProduct to allow users to create a specific version of a product within a portfolio, handling disposition of the previous version (keep, disable, or remove).
Proposed Solution
Simplify the properties for CfnCloudFormationProduct
Allow creation of a new version
Dispose the previous version by keeping it, disabling it, or removing (overwriting) it
Use properties from the template to populate CfnCloudFormationProduct parameters
Associate the new product with a Portfolio
Other
Would be used in AWS Security Hub Automated Response and Remediation to simplify that solution and to add versioning support.

[x] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

Simplifying the L1 interface such as CfnCloudFormationProduct with higher level abstraction is precisely the intent of L2 patterns in CDK library. Probably share your input on the L2 pattern request for Service Catalog here

Closing the issue in favor of the guidance provided above, feel free to re-open it if you'd like to discuss it further


GPUImageLookupFilter always needs the lookup picture reprocessed every time?

It's weird that I keep needing to process a picture for a GPUImageLookupFilter, when this lookup picture never changes.
How can I avoid having to keep calling processImage on this picture whenever I want to use this filter?
Here's what I'm doing:
the setup
let lookupImage = UIImage(contentsOfFile: lookupPath!) // lookupPath is correct and created already
let lookupPicture = GPUImagePicture(image: lookupImage)
let lookupFilter = GPUImageLookupFilter()

lookupPicture.addTarget(lookupFilter, atTextureLocation: 1)
lookupPicture.processImage()

The filter group
// in GPUImageFilterGroup
// a blend filter, doesn't really matter
let blendFilter = GPUImageAlphaBlendFilter()

// adding filters to the filter group
self.addFilter(lookupFilter)
self.addFilter(blendFilter)

// adding the target
lookupFilter.addTarget(blendFilter, atTextureLocation: 1)

blendFilter.mix = // this is set somewhere

// targets both, for blending the final look
self.initialFilters = [lookupFilter, blendFilter]
self.terminalFilters = blendFilter

actually processing the image
// this is some image we want to run through the process
let picture = GPUImagePicture(image: originalImage)
if (picture.targets().isEmpty) {
  // if we don't have a target yet, it adds the filterGroup
  picture.addTarget(filterGroup) // this is the filterGroup we created above
}

// if we don't already have a gpuImageView target, it adds it. Didn't include the conditional statement for brevity
filterGroup.addTarget(gpuImageView)

// this is the weird thing, if I don't process the lookup image, it just doesn't work after the first time
lookupPicture.processImage()

picture.processImage()

This pseudocode is generally how I've been using it.  If I don't process the lookupPicture, it doesn't show any change. It seems like if I ever processImage() for the first picture, all lookupPictures need to be processed as well. What am I doing wrong?

I searched through GitHub issues and found this:
https://github.com/BradLarson/GPUImage/issues/303
Looks like we can skip setting the flag if we want the second input to be static. I'll try it and see if it works.

So it looks like that works!


Also works on local package

This is awesome. :tada:
I just realized you can use this for your local code as well. I'm currently using this to support regular glslify syntax (instead of webpack require overload approach) by doing this in the webpack config:
...
  module: {
    loaders: [
      // support modules like three-vignette-background, soundcloud-badge, etc
      {
        test: /node_modules/,
        loader: 'ify'
      }
    ],
    postLoaders: [
      // support local package.json browserify config
      {
        test: /\.js$/,
        loader: 'ify'
      }
    ]
  }

And in my package.json:
...
  "browserify": {
    "transform": [
      "glslify"
    ]
  },
  "glslify": {
    "transform": [
      "glslify-hex"
    ]
  }

And in my src/index.js I can do this:
const glslify = require('glslify')

const vertexShader = glslify(`
  attribute vec4 position;
  attribute vec2 uv;
  uniform mat4 projectionMatrix;
  uniform mat4 modelViewMatrix;
  varying vec2 vUv;
  void main () {
    vUv = uv;
    gl_Position = projectionMatrix * modelViewMatrix * position;
  }
`.trim(), { inline: true })

Thanks man! Glad it's proving useful :grin: I'll add a note to the readme about this :)


flutter engine crash on 1.12.13+hotfix.9

After we upgrade the flutter version to 1.12.13+hotfix.9. We meet some crashes as follows. Hope flutter team could fix it.

#00 pc 003ebeae /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#01 pc 0044bf8b /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#02 pc 004a7ba7 /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#03 pc 0032f93b /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#04 pc 0032d433 /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#05 pc 00146755 /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#06 pc 00148489 /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#07 pc 0000f239 /system/lib/libutils.so (android::Looper::pollInner(int)+632) [armeabi-v8]
#08 pc 0000ef43 /system/lib/libutils.so (android::Looper::pollOnce(int, int*, int*, void**)+26) [armeabi-v8]
#09 pc 0000c6c7 /system/lib/libandroid.so (ALooper_pollOnce+50) [armeabi-v8]
#10 pc 00148561 /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#11 pc 00145adf /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#12 pc 001474a1 /data/app/com.buaa.recorder-L7ogd2vhVtZLj7aie71RnQ==/lib/arm/libflutter.so [armeabi-v7a]
#13 pc 000646e5 /system/lib/libc.so (__pthread_start(void*)+22) [armeabi-v8]
#14 pc 0001df09 /system/lib/libc.so (__start_thread+24) [armeabi-v8]

Hi @buaashuai
are could you please run flutter upgrade --force
if the issue persists
please provide your flutter doctor -v ,
your flutter run --verbose
and your pubspec.yaml
or if possible a reproducible minimal code sample.
Thank you

Symbolized stack trace:
third_party/libcxx/include/memory:2562
third_party/dart/runtime/vm/thread.cc:311
third_party/dart/runtime/vm/dart_api_impl.cc:1366
third_party/tonic/scopes/dart_isolate_scope.cc:16
third_party/tonic/dart_persistent_value.cc:46
third_party/libcxx/include/functional:2419
flutter/fml/platform/android/message_loop_android.cc:92

This is crashing inside Dart_EnterIsolate.  It may be a duplicate of https://github.com/flutter/flutter/issues/45578

Possible duplicate is also closed
Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Performance/Config Issue

Hi,
I just noticed a big difference in cpu core usage comparing GUI and pure livestreamer, does the GUI ignore my livestreamerrc config? (hls-segment-threads=4) Or is there an other way to add livestreamer parameters?

Hi!
There actually shouldn't be any interferences with the default livestreamer config variables when using the GUI. These are the only parameters which are being used when starting the livestreamer process, all other variables defined in your config are not touched/changed.
So are you sure that's really an issue related to the GUI? I mean it doesn't do anything fancy but invoking the livestreamer executable... Your screenshots also don't show which processes are causing the high CPU load and I'd be surprised if it was the GUI.
Could it be the --player-passthrough parameter which is responsible for that? Have you tried setting another value?

Shame on me, it was totally my fault. I thought that I was still using --player-passthrough hls with livestreamer, so I chose it for the GUI settings. Turns out that hls (Apples's streaming protocol, should have googled it earlier) has worse performance with my Windows setup.
Everything works fine now, I'm sorry for this hurried ticket. I love your GUI, keep up the great work!

Np, thanks :)


Outputs this after running the ControlNet cell

Startup time: 236.8s (import torch: 10.1s, import gradio: 1.2s, import ldm: 3.0s, other imports: 107.4s, setup codeformer: 21.1s, list SD models: 19.6s, load scripts: 61.4s, load upscalers: 2.0s, reload hypernetworks: 1.2s, initialize extra networks: 5.8s, create ui: 3.5s, gradio launch: 0.4s, add APIs: 0.1s).
*** Failed reading extension data from Git repository (sd-webui-controlnet)
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/extensions.py", line 63, in do_read_info_from_repo
commit = repo.head.commit
File "/usr/local/lib/python3.10/dist-packages/git/refs/symbolic.py", line 217, in _get_commit
obj = self._get_object()
File "/usr/local/lib/python3.10/dist-packages/git/refs/symbolic.py", line 210, in _get_object
return Object.new_from_sha(self.repo, hex_to_bin(self.dereference_recursive(self.repo, self.path)))
File "/usr/local/lib/python3.10/dist-packages/git/objects/base.py", line 85, in new_from_sha
oinfo = repo.odb.info(sha1)
File "/usr/local/lib/python3.10/dist-packages/git/db.py", line 43, in info
hexsha, typename, size = self._git.get_object_header(bin_to_hex(binsha))
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/gitpython_hack.py", line 18, in get_object_header
ret = subprocess.check_output(
File "/usr/lib/python3.10/subprocess.py", line 421, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 505, in run
stdout, stderr = process.communicate(input, timeout=timeout)
File "/usr/lib/python3.10/subprocess.py", line 1154, in communicate
stdout, stderr = self._communicate(input, endtime, timeout)
File "/usr/lib/python3.10/subprocess.py", line 2022, in _communicate
self._check_timeout(endtime, orig_timeout, stdout, stderr)
File "/usr/lib/python3.10/subprocess.py", line 1198, in _check_timeout
raise TimeoutExpired(
subprocess.TimeoutExpired: Command '['git', 'cat-file', '--batch-check']' timed out after 2 seconds

it's a harmless msg


Object.keys: argument is not an Object in redux-starter-kit.esm.js

Hi there,
I'm having an issue using this project with IE11, specifically with this error message in the redux-starter-kit.esm.js file:

Object.keys: argument is not an Object

The issue occurs in the following method on the third line :
  for (var i = 1; i < arguments.length; i++) {
    var source = arguments[i] != null ? arguments[i] : {};
    var ownKeys = Object.keys(source);  // <-- error occurs here

    if (typeof Object.getOwnPropertySymbols === 'function') {
      ownKeys = ownKeys.concat(Object.getOwnPropertySymbols(source).filter(function (sym) {
        return Object.getOwnPropertyDescriptor(source, sym).enumerable;
      }));
    }

    ownKeys.forEach(function (key) {
      _defineProperty(target, key, source[key]);
    });
  }

  return target;
}

From digging a bit deeper, it seems to try and call Object.keys on a value of false, which then fails in IE11.
The current behaviour in Chrome is to return an empty array when calling Object.keys() on a non-object, but polyfilling IE11's Object.keys() method has so far been unsuccessful.
Should this starter kit work with IE11 out of the box, or is there some guidance on compatibility?

Hmm.  I'll be honest and say I've put zero thought into browser compat issues so far.
That particular chunk of code appears to be a Babel polyfill for the object spread operator.
What input and stack trace is leading to that particular edge case getting hit?

Closing due to lack of actionable feedback.

In case anyone comes here via google and is looking for a fix, including the es6-shim resolves the issue.

Even simpler fix, just set the devTools option to an empty object in the configureStore
export default configureStore({
  reducer: rootReducer,
  devTools: {}
});


Phase 3 Funding: Open call | Add fits maintainer FR

Just what it says on the tin.  Note I have not yet had a chance to reach out to @saimn on this, so it's not very fleshed out. But I very much want any input you might have, @saimn (including anything from "yes these are the 10 things that need doing" to "nah, don't do it"!)

There is > 150 open issues on io.fits and, as the proposal says this is indeed one of the most used parts of astropy. Maybe we can pick 5 high-priority items from that list and then say "select and work on (and ideally solve) 30 others"? Given the importance of fits, I would support this to be a much larger funding request (I know we have a lot of requests this year), > 50k$ (i.e. significant full-time work). This is a complex package and I'm afraid that 10 k$ is far too little to get a new person into fits. By the time they understand the package, they've run out of money. If we want to get someone without prior fits experience (and likely without a deep knowledge of the fits conventions and associated papers), then this funding must last long enough that they can learn all this stuff and then have time left to work on issues productively.

Alright I tried to address @hamogu's point while staying conscious of some feedback from @saimn on this that this proposal could yield more work for him and therefore do no good at relieving the burden. Given our funding rule that funding should first support volunteers, I think it's critical to respect that. But it is at fundamental tension with @hamogu's point that we want to make sure we build expertise in this very complex area. So the proposal is now explicit about an amount (on the high end of the rang from before) and that this is a starting point on growing expertise, limited mainly by not wanting to overwhelm the maintainer base (especially @saimn)

Please react to this comment to vote on this proposal (👍, 👎, or no reaction for +0)

Haven't heard from @saimn on this. What does he think?

We discussed that offline with Erik so the current version of the proposal is fine by me :)

Oh no... was I supposed to be reacting to a certain comment? I have been reacting to the original posts.

@pllim Ideally, you should react to this comment: https://github.com/astropy/astropy-project/pull/280#issuecomment-1222521970. This way we can keep track of who is voting rather than just reacting in general.

Congratulations!  The community has expressed support for this FR, and the Finance Committee has determined it can be funded.  This FR has been approved for $11,520, to be funded from the NASA grant.
@aaryapatil is the Finance Committee member who will be supporting this project.  They will update this PR with the amount and then merge it, as well as being in contact with you to set up any necessary agreements and relevant Open Collective financial arrangements. They will also open a new issue where progress on this project can be discussed.


Adapt kubectl-gs to the removal of default apps

Motivation
Part of https://github.com/giantswarm/roadmap/issues/3419
After the removal of default-apps-aws we need to update our tooling to handle that.
Outcome

kubectl-gs is fully migrated to not reference default apps

Done here https://github.com/giantswarm/kubectl-gs/pull/1324


[PE-D][Tester C] Command Validation: Pin command

How to reproduce: Execute /pin command twice.
Expected: After a person has been already pinned, and if the user pin that person again, the application should return a message that shows the person has been already pinned (instead of showing the person has been pinned sucessfully)
Actual: A user can pin a person multiple times

Labels: severity.Medium type.FunctionalityBug
original: purivirakarin/ped#8

This is a feature flaw and cannot be fixed in v1.4.


S3 access control lists (ACLs) should not be used to manage user access to buckets

Describe the bug
The proper way to ensure that ACLs are not used to manage object and bucket access is to disable them via the Bucket Owner Enforced setting in S3
Steampipe version (steampipe -v)
v18.0
Plugin version (steampipe plugin list)
Default in SPC
Mod version 0.54.0
To reproduce
An S3 bucket with either of the two settings bucket owner preferred or object writer still allow ACLs to be used. At the time the mod only looks for the presence of any ACLs, not to see if ACLs are disabled.
Expected behavior
The mod should report this finding as non-compliant if the ownership setting is not bucket owner enforced
Additional context
Add any other context about the problem here.

This is derived from  FSBP S3.12) > query used: s3_bucket_acls_should_prohibit_user_access  -- We are re-evaluating based on your suggestion to explore if we can add any direct column for Bucket owner enforced in the table or current evaluation is correct with additional checks as ACLs are disabled in it?

ACLs aren't "disabled", they're just not present. ACLs are only disabled when the Bucket owner enforced setting is set.

@jchrisfarris, would it be possible for you to try it issue-539 and share your feedback?


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/373 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit e727685:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update CHANGELOG.md

Trying to document all relevant changes retrospectively in preparation for the future release of v 2.0.0. Additions and corrections are totally welcomed 🙏

The commit was rebased to resolve conflicts with master.
I removed the Netlify bit intentionally, because it's related to internal DS infrastructure, rather than changes that are important to a consumer of the DS.
I added "breaking change" in front of the Input.json line because technically if someone is using only the tokens package, this change will break their app.

The commit was rebased to resolve conflicts with master.
I removed the Netlify bit intentionally, because it's related to internal DS infrastructure, rather than changes that are important to a consumer of the DS.
I added "breaking change" in front of the Input.json line because technically if someone is using only the tokens package, this change will break their app.


support pagination in the /catalog API

Proposal
The catalog API should support pagination in the cases where there are large
numbers of services supported by a broker. We see a potential for 10k-15k
catalog entries which could take a bit of time to render to the caller.
Effectively the initial catalog call should expect the Link header or the
metadata in the body indicating that the broker should be invoked with
pagination.
The API should take the following optional parameters:

parameter name
description

per_page
number of items to show per page

page
page number requested, depends on page size. if > last page, then last page is returned

cURL
   $ curl -H "X-Broker-API-Version: 2.9" http://username:password@broker-url/v2/catalog?page=2&per_page=20

Body (changes in bold)

Response field
Type
Description

services*
array-of-service-objects
Schema of service objects defined below.

pagination
metadata about pagination
Schema for pagination defined below.

Response
The pagination block would be added to the catalog response at the same
level as services. In the case of requesting the first page, the response
will contain a next and a last item.
{
  "services": [{
     ...
     }],
  "pagination": {
    "next": "https://broker/v2/catalog?page=2",
    "last": "https://broker/v2/catalog?page=15333"
  }
}

Alternatively we could use the Link header RFC 5988. In this case there would be NO changes to the response body just the headers.
Link: <https://broker/v2/catalog?page=2>; rel="next",
      <https://broker/v2/catalog?page=15333>; rel="last"

Subsequent calls will yield 2 new options, first and prev. For example, if you request page 10000 the following response will be returned:
{
  "services": [{
     ...
     }],
  "pagination": {
    "next": "https://broker/v2/catalog?page=10001",
    "last": "https://broker/v2/catalog?page=15333",
    "first": "https://broker/v2/catalog?page=1",
    "prev":  "https://broker/v2/catalog?page=9999"
  }
}

Alternatively we could use the Link header RFC 5988
Link: <https://broker/v2/catalog?page=10001>; rel="next",
      <https://broker/v2/catalog?page=15333>; rel="last",
      <https://broker/v2/catalog?page=1>; rel="first",
      <https://broker/v2/catalog?page=9999>; rel="prev"

@pmorie here is the first cut at a proposal for supporting pagination in the catalog api.

Hello @jmrodri. Thanks for your proposal.
According to #122 proposals should be written in a Google Doc and linked from an issue. The reason is that docs make collaborating, writing notes and proposing changes to the spec easier. That is how previous proposals have been handled.
Also notice that spec changes should be validated through implementation once the design has been agree upon (step 3).

@angarg12 I will write up the Google doc now and share the link in this issue. I apologize for not reading #122 first.

No apologies needed! Thanks for getting involved and contributing to the project  :tada:.

@angarg12 @pmorie here is the google doc containing the proposal. let me know if I need to change anything like permissions etc.
https://docs.google.com/document/d/1P0MTtz5k0BZhi6CxXN9fsqmXBYojFKHxUrspndb6ODM/edit?
usp=sharing

It works correctly, thanks.

What would be the next steps with this issue? Do we need a prototype?

You can see the latest contributing procedure here:
https://github.com/duglin/servicebroker/blob/9dd1d36ab5525fe6bb8f7175588cc567d41b5b0d/CONTRIBUTING.md
If your proposal is finished, then we should move to the validation through implementation.

On additional note, not directly related to pagination. If there are potentially 10k+ entries in the catalog one might need a way to have the broker provide search capabilities as well. I bring it up here because if there are 100s of pages, and only catalog entries on the current page are available to a consumer (A UI), it would become to search for specific entries. An example could be a way to search in tags for "caching" or "nosql" to see what options are on offer.

@RamakrishnanArun this was brought up in our weekly meeting briefly. I suggest you open a new issue to discuss that topic specificaly, so that everyone can participate.

Added an issue to discuss search on the catalog api in issues #136.

Hey folks, this is starting to come up for some of our use-cases, and I'm wondering if any movement has been made on it since February.
I'd also like to suggest a more generic approach to pagination where instead of a field for page number, the pagination scheme use opaque tokens. The service response returns a next_token, and the client passes this token when making further requests.
Brokers can still just use page numbers as the token if they want, or use more advanced tokens like item IDs to better capture where in the pagination the client was.

@bmelville " this is starting to come up for some of our use-cases" can you share more details of the pain it's causing and the use case?
We can then prioritise focusing on this issue.

@bmelville I'd be curious about the opaque token. Admittedly I don't see how that would work, not saying it won't just don't understand it 😄

@avade, we have brokers with potentially hundreds or thousands of service definitions exposed through them. We find that even >10 can be a lot of information to pass, especially with schemas part of the definition now.

@jmrodri, the problem with using just page numbers all the time is that the data behind the scenes can change between requests. So getting page 1 and then asking for page 2 could result in duplicate entries if something that was on page 1 before now moves to page 2 (something was inserted before it).
Using an opaque token could be as easy as the identifier row in the database, such that the next request I make always starts with the next thing I am guaranteed not to have seen on the previous requests. This ensures I'm not getting duplicate entries.
If that doesn't concern you (e.g., your catalog is static), you could always just return the page number as the opaque token, but it allows a broker who needs to guard against it to do more advanced pagination tokens.

right - we'd just need to be clear about what to do when that token "times out" - so the client knows when to start over.

Is that true even of page numbers? Like when I ask for page 25 but it no longer exists.

its up to the broker to decide if/when it times out. For a static catalog it may never do so, but a generated token might - depends on how long a broker is willing to remember the tokens. So we just need to define how the broker tells the platform that its "token" is old and needs to start over.

Yes agreed. I was going to suggest the broker return something incredibly funny like 418 I'm a teapot, but I found some that might actually be nice instead, like 416 Requested Range Not Satisfiable

It would be really cool if we could fine a reason to use 418 - someplace!  :-)

@bmelville out of interest, can I ask why you've gone for the approach of having one broker for hundreds/thousands of services, rather than multiple brokers?

Having many small hand written brokers is okay, but not a great user experience for the person having to plug them all into one or perhaps many consumption environments.
Once you start building dynamic marketplaces around the broker concept though, it becomes advantageous to expose a single broker to both the consumer and the producer side. So you will typically have producers plugging in service definitions (rather than individual brokers) to the marketplace, and having the services available consumption exposed as a single broker.
Adding @pmorie, as I believe we've talked about this in the past and he also has a similar use-case in his platform.

From 11/12 call, @jmrodri will either write-up a proposal or icebox this


RasPi Check for Ubuntu?

Hi, I already usw this nice tool/app for my raspberry (raspbian) sucessfully.
But I also have another machine (Ubuntu on a amd64 chip), that I want to monitor.
Is there a way to use RasPi Check for my Ubuntu amd64 machine or is there another/comparable tool or app?

see issue #161

sudo apt install libraspberrypi-bin
sudo usermod video ssh_user
(Haven't tried it but found a reference to this package on an arch thread)

closing, see #161


Sankertainpy integration

Hi @HaSchneider ,
I'm using your code to build a visualization library for Brightway. I may have some issues with understanding parts of your code and I want to keep the conversation with you until I'm confident that your code is properly integrated in our library if you'll have the time for that.

my first issue was here, it seems that you're creating a list with all same values and median of it will be that same value. could you check it please?

Hi @HamedAkhavan ,
Of course, I hope I can help you with that.
Regarding your first issue:
As long as the argument "use_distributions" of the lca object is True, it should generate different scores for each iteration.
If you get a list of identical values, you might have an older version of brightway2-calc, you need at least version 2.0.dev10.


[FEATURE REQUEST] Add UI preference to reduce animations

Please confirm these before moving forward

[X] I have searched for my feature proposal and not found a work-in-progress/duplicate/resolved/discarded issue.
[X] This proposal is a completely new feature. If you want to suggest an improvement or an enhancement, please use this template

Describe the new feature
When updating a package, very prominent (and useful) loading bars start in WingetUI to indicate it's being responsive. However, their very prominence (especially so when updating many packages) is problematic for users with mental disorders that cause visual stimulus to be easily overwhelming.
I propose a new setting to reduce animations in order to replace these loading bars (and perhaps other animations in the product) with subtler equivalents. In the case of the loading bars, replace them with animated ellipses ("." > ". ." > ". . ." > repeat) or even just a static "updating..." status.
Describe how this new feature could help users.
Adding this feature would make WingetUI more accessible to those with visual disabilities, and by virtue of reducing that barrier, help make the application more desirable for everyone else with the preference for fewer animations.

Hello @robertoftheedwards,
this feature refers to WingetUI in general or to the new WingetUI 3 Alpha release?

@marticliment WingetUI in general. I honestly wasn't aware there was a WingetUI 3 Alpha release.

I have removed the "Pending" progress bars. You were right, it was too much going on on the screen.
Only the current progress operation will show a progressbar now


Random classes picked up by json.

Sorry, accidentally posted before entering description
I've been trying to get container-query working with the Roots/Sage WordPress theme which uses Webpack.
For some reason the Json is picking up other classes from the css that do not use the @container rule.
I setup a very simple box example with the .box class... you can see what resulted below, where it's picking up on some additional foundation classes.
{"e":".reveal, .reveal.tiny, .reveal.small, .reveal.large","f":[{"b":[{"e":".box","d":{"background":"green"}},{"e":".box__image","d":{"display":"block"}}],"a":[[["width",">=",200]]]},{"b":[{"e":".box__title","c":{"font-size":"10rh"}}]}]}

I'm not sure what you mean?

I'm using this Javascript to load which is causing issues, probably because of the json output.
import Container from "@zeecoder/postcss-container-query";
import meta from "../../styles/main.scss.json";

// Initialising all containers by finding all instances based on the selectors
for (let containerSelector in meta) {
  document.querySelectorAll(containerSelector).forEach(element => {
    // Initialising all HTML Elements with the right json metadata
    new Container(element, meta[containerSelector]);
  });
}

Seems like you don't use the right module for the right task.
postcss-container-query creates the JSON, while container-query is the runtime counterpart.
So in this case, you want to generate the json with postcss-container-query with either the webpack postcss-loader, or by using some other task runner, and then your javascript can take that JSON, and initialise the `import Container from "@zeecoder/container-query" runtime.
The first line therefore definitely shouldn't have postcss-container-query, but the regular container-query instead.
What do you use for js bundling?

That seems ok, so I assume "../../styles/main.scss.json" is the json meta that's being generated, right?
Are you planning to use multiple containers in that main.scss?
It seems to me that you're following a style where you have a "main" file that imports other files (maybe bem blocks or somethings else?), which would mean that you'd have multiple different containers essentially in the same file.
By default, the postcss plugin expects a single container in a single file, but you can override this behaviour: https://github.com/ZeeCoder/container-query/blob/master/docs/multiple-containers.md

Thanks for all your help. Yes, that's exactly how my project is setup. How can I set the singleContainer option to false in my postcss configuration above?

Alright, looks like I got it working with the below:
/* eslint-disable */

const cssnanoConfig = {
  preset: ['default', { discardComments: { removeAll: true } }]
};

module.exports = ({ file, options }) => {
  return {
    parser: options.enabled.optimize ? 'postcss-safe-parser' : undefined,
    plugins: {
      cssnano: options.enabled.optimize ? cssnanoConfig : false,
      'postcss-nested': {bubble: ["container"]},
      '@zeecoder/postcss-container-query': {singleContainer: false},
      autoprefixer: true,
    },
  };
};

Is everything working now then @christianmagill ?

Yes, all seems to be working well now. Thanks


Legend isn't working as expected, appears as undefined

When I display legends as visible, they appear as undefined. I just used the namespace options.plugins.legend and the display option as mentioned in ChartJS configuration.
Reproduction link
Codepen example
Expected behavior
Legends should show the same as the label. (In the example, Step 1, Step 2...)
Image showing the error

Context

Version: v4.0.0-alpha1
Browser: Chrome

can you clarify? when I enable the plugin and define a label for the dataset it works just fine.
window.onload = () => {
  const ctx = document.getElementById("canvas").getContext("2d");
  window.myBar = new Chart(ctx, {
    type: 'funnel',
    data: {
      labels: ['Step 1', 'Step 2', 'Step 3'],
      datasets: [{
        label: 'Dataset 1',
        data: [1, 0.75, 0.5]
      }]
    },
    options: {
      indexAxis: 'y',
      title: {
        display: true,
        text: 'Chart.js Funnel Chart'
      },
      plugins: {
        legend: {
          display: true
        }
      }
    },
    plugins: [ChartDataLabels],
  });

};

can you clarify? when I enable the plugin and define a label for the dataset it works just fine.
window.onload = () => {
  const ctx = document.getElementById("canvas").getContext("2d");
  window.myBar = new Chart(ctx, {
    type: 'funnel',
    data: {
      labels: ['Step 1', 'Step 2', 'Step 3'],
      datasets: [{
        label: 'Dataset 1',
        data: [1, 0.75, 0.5]
      }]
    },
    options: {
      indexAxis: 'y',
      plugins: {
        title: {
        display: true,
          text: 'Chart.js Funnel Chart'
        },
        legend: {
          display: true
        }
      }
    },
    plugins: [ChartDataLabels],
  });

};

Isn't there any way to use the labels as legends instead of the datasets?
In your example the legend is for Dataset 1. Can the legends be Step 1; Step 2 and Step 3 with each corresponding color?
Thank you for your response.

you are asking about a categorical color legend?
similar to https://github.com/sgratzl/chartjs-chart-geo

bottom right color legend but for the categories (Step 1, Step 2, Step 3)?
AFAIK there is no chartjs plugin that currently implements something like this. This plugin implements a funnel chart using a single dataset consisting of multiple data points. Not sure whether it could be swapped the other way around, since internally different datasets are handled independently making the stepping effect quite difficult.

you are asking about a categorical color legend?
similar to https://github.com/sgratzl/chartjs-chart-geo  bottom right color legend but for the categories (Step 1, Step 2, Step 3)?
AFAIK there is no chartjs plugin that currently implements something like this. This plugin implements a funnel chart using a single dataset consisting of multiple data points. Not sure whether it could be swapped the other way around, since internally different datasets are handled independently making the stepping effect quite difficult.

Yeah, i figured.
I'll see what I can do but I appreciate your answer. Thank you for the help.
Cheers.


Positioning Angular UI bootstrap Datepicker

Hi. As I explained in my case in Stack Overflow (http://stackoverflow.com/questions/18716904/positioning-angular-ui-bootstrap-datepicker) I am having a problem with the positioning in the datepicker. It always appears below the input that invoke it from the bottom left corner. But if the input is close to the right border of the page, the datepicker is cut and a horizontal scroll appears.
I am writing because I think it would be a nice feature to handle the alignment in the datepicker configuration.
Hoping you take this into consideration
Kind Regards
Andrey Bottoni

+1

+1

+1

+1

+1

+1

+1

https://github.com/angular-ui/bootstrap#impt---2015-plans-and-angular-13-support

+1

+1

+1

+1

+1

+1

+1

+1

:+1:

+1

+1

+1

+1

+1

+1

I know this is an okd topic but please stop all the +1's. We're aware of this issue and many others.
Adding +1's only adds noise to the conversation.

Ok, so what people should do to convince the authors to implement, after 2 years of +1 pestering?

@vitaly-t I think you're missing the point of an open source project. This is a free and open source project. We, the authors, are spending most of our free time to provide you with awesome tools that most of you use commercially and safe (and money) time with. That's all cool :+1:
We're not an organisation that builds features on demand. There simply are too much requests to satisfy everyone. That does not mean we won't do it. It only indicates that we will get to it, when we get to it.
In the meanwhile, the spirit of open source software is to share and collaborate. Everyone is free to dig into the source of UI Bootstrap and implement this specific feature. Send us a PR and we're happy to merge it in the next release. If no one is willing to do that, I guess your only option is to wait until one of the authors finds time and energy to work on this specific feature.

Related: #375

PR: #3778

Came here to post another workaround, just to be greeted with a pull request!
Someone give this man a cookie! (and a merge into master, please :+1: )

needed this for right:0 +1

+1

Please do not only add +1 to issues as it adds no value to the discussion.  We welcome any added insight and/or contributions so please feel free submit a PR that allows for this feature.
That said, this is more a job for a $position type service so the entire library could benefit.  If you need inspiration, take a gander at the Tether library.

Closing in favor of #4762.

Until this #5444 goes on, my simple solution was to add a new atribute to the directive uibDatepickerPopup:
useRightMargin: '=?',
and on the $watch('isOpen') of UibDatepickerPopupController just added this:
if(scope.useRightMargin){           element_position = $position.position(element);           scope.position.left = scope.position.left + scope.position.width - 246;            //Arbitrary width: 246 = datepicker width(286) - calendar button width (40) }

The positioning problem is mostly with mobile devices, and it can be annoying, other case it might not be a big problem.
After searching and trying out different solutions, The below css fit best for me, hope this can save some time to others who are looking out for best solution.

The positioning problem is mostly with mobile devices, and it can be annoying, other case it might not be a big problem.
After searching and trying out different solutions, The below CSS fit best for me, hope this can save some time to others who are looking out for best solution.
@media only screen and (max-device-width: 480px) {     .dropdown-menu {         top: -10px !important;         left: -38px !important;     } }

The positioning problem can be noticed mostly with mobile devices, and it can be annoying, other case it might not be a big problem.
After searching and trying out different solutions, The below CSS fit best for me, hope this can save some time to others who are looking out for best solution.
@media only screen and (max-device-width: 480px)  {  .dropdown-menu     {    left: -38px !important;    }  }

+1

+1

@AntonRatnick, please be respectful of the previous request made to not just add +1 to issues.  As people seem to unable to follow instructions, I am locking this issue.


Open Drawer dynamically

Hello, this is my scene with Redux Router flux
<Drawer                  ref={(ref) => { this.drawer = ref; }}                 contentComponent={DrawerContent} hideNavBar key="mainTab">             <Scene key="splash" component={MainTab} title="Bienvenue" hideNavBar/>           </Drawer>
I Have a button menu in MainTab in order to open drawer when it's pressed
How can i open drawer from child component??

I wanna know this as well...

you can try Actions.drawerOpen();


internal/fakefsnotify: incorrect statement in package comment

I noticed the godoc for perkeep.org/internal/fakefsnotify package says:

Obviously the 'gopherjs serve' command (which normally relies on fsnotify) is not expected to work when gopherjs is built with fakefsnotify.

This isn't true, gopherjs serve never uses fsnotify and works just fine without it. It always compiles the latest code from disk on every HTTP request, so all that's needed is to refresh the browser page.
fsnotify is only used by GopherJS when the --watch "watch for changes to the source files" flag is used, and that flag applies only to gopherjs build and gopherjs install commands.
So, perhaps the text should be changed to say something like this instead:

The --watch flag (which normally relies on fsnotify) is not expected to work when gopherjs is built with fakefsnotify.

Looks like fakefsnotify is totally unused.  I think that happened in a recent gopherjs update.
I wonder if we should just remove it?

yeah with the move to dep we reverted to using the "non-hacked" version of gopherjs, so i think we can drop fakefsnotify.

https://camlistore-review.googlesource.com/c/camlistore/+/14106


Fixes cutted floatingLabel on some Android devices

In some Android devices (detailed in issue), floatingLabel may appear cutted after focus animation.
This PR adjust the position of label.
Tested in simulator (Genymotion Android 5.1.0, 6.0.0, 7.0.0, 7.1.0, 8.0.0), Xiaomi Mi 6 with Android 8.0.0 and Moto C Plus with Android 7.0.0. Also tested in iOS.
Updated the example repo that uses my modified NativeBase version.
https://github.com/lucianomlima/nativebase-floatinglabel-android-bug
fixes #2117

@ZeroCool00 PR is not merged yet. Here is cutting too

is it release yet?

@ZeroCool00 not.


sd cards

I have crouton/trusty installed internally , how does adding an external sd card help, storage, memory, or both, as I noticed much of my file system is used up. Would it be better to just move the chroot to the sd drive completely. This is related to possibly another, similar question I asked here.

The SD card is used to increase storage space. You would either move the chroot to you SD card, or just keep large files on the SD card to free up internal space.

But beware of #288


mm/iob: remove csection

Summary
reason:
We decouple semcount from business logic
by using an independent counting variable,
which allows us to remove critical sections in many cases.
Impact
mm/iob
Testing
test by https://github.com/apache/nuttx-apps/pull/2849
Build Host:
OS: Ubuntu 20.04
CPU: x86_64
Compiler: GCC 9.4.0
Configuring NuttX and compile:
$ ./tools/configure.sh -l qemu-armv8a:nsh_smp
$ make
Running with qemu
$ qemu-system-aarch64 -cpu cortex-a53 -smp 4 -nographic
-machine virt,virtualization=on,gic-version=3
-net none -chardev stdio,id=con,mux=on -serial chardev:con
-mon chardev=con,mode=readline -kernel ./nuttx

[Experimental Bot, please feedback here]
This PR appears to partially meet the NuttX requirements. While it provides a reasonable summary and identifies the impacted area, it lacks crucial details in the Impact and Testing sections.
Here's a breakdown of what's missing and how to improve it:
Missing Information:

Impact:  The PR only mentions "mm/iob" as the impacted area.  It needs to specifically address all the impact points listed in the requirements:

Is this a new feature or a change to an existing one?
User impact (will users need to change anything in their applications?)
Build impact (any changes to the build process or configuration?)
Hardware impact (does it affect specific architectures, boards, or drivers?)
Documentation impact (does this require documentation updates?  Were they provided?)
Security impact (are there any potential security implications?)
Compatibility impact (backward/forward compatibility concerns?)
Anything else to consider?

Testing: The testing information is insufficient.  While it mentions a related NuttX Apps PR, it doesn't provide the results of the testing. The logs before and after the change are empty. This section needs to include:

Specific target details (architecture, board, configuration). "qemu-armv8a:nsh_smp" is a start, but more details might be necessary.
Actual log output demonstrating the behavior before and after the change, highlighting the improvement or fix.  This is crucial for verifying the change works as intended.  Simply stating "test by ..." isn't enough.

How to Improve:

Impact:  Fill in all the required impact categories with specific "YES/NO" answers and detailed explanations where applicable.  Even if the answer is "NO," briefly explain why (e.g., "Impact on user: NO - This is an internal change and does not affect user APIs.").
Testing: Provide concrete test results. Include the actual log output before and after the change.  Clearly demonstrate how the change addresses the issue or implements the new feature.  Consider adding more test cases if necessary to cover different scenarios.

Example of Improved Testing Section:
Testing

I confirm that changes are verified on local setup and works as intended:
* Build Host(s): Ubuntu 20.04, x86_64, GCC 9.4.0
* Target(s): QEMU ARMv8-A (Cortex-A53), nsh_smp configuration

Testing logs before change:

<Insert relevant log output showing the problem before the change.  For example, demonstrating contention or performance issues related to the semcount.>

Testing logs after change:

<Insert relevant log output showing the improved behavior after the change. For example, demonstrating improved performance or the absence of contention.>

This PR fixes the contention issues observed previously. The logs after the change show a significant improvement in throughput/responsiveness/etc. (Be specific about the improvement).

By providing more complete information in the Impact and Testing sections, the PR will be much easier to review and more likely to be accepted.

reason: We decouple semcount from business logic by using an independent counting variable, which allows us to remove critical sections in many cases.

if it's so common, i feel it's better to migrate to a simpler primitve like a condvar. how do you think?

reason: We decouple semcount from business logic by using an independent counting variable, which allows us to remove critical sections in many cases.

if it's so common, i feel it's better to migrate to a simpler primitve like a condvar. how do you think?

The implementation of sched/event/* has similar semantics but has more powerful and complex functionalities, making it unsuitable for some scenarios.


Enable controller applications to receive and process CASE session establishment request

Problem
Currently, controller applications cannot receive and process CASE session establishment request (i.e. Sigma1). Only server applications are using CASE Server. The controller API/application doesn't instantiate a CASE server. Due to this, a device cannot initiate a CASE session with the controller application.
Proposed Solution
Add CASE Server either to CHIPDeviceControllerFactory or CHIPDeviceController

https://github.com/project-chip/connectedhomeip/pull/14998

Fixed by https://github.com/project-chip/connectedhomeip/pull/14998


Defining custom buttons on root scene

Version
Tell us which versions you are using:

react-native-router-flux<EMAIL_ADDRESS>react-native v0.31.0

How can I set my custom backButton only one time? I'm using react-native-vector-icons and this is my custom backButton.
const BackButton =
    <TouchableHighlight onPress={()=> Actions.pop()} style={{ width: 45, height: 45, position: 'absolute', top: 0, left: 0, justifyContent: 'center', alignItems: 'center'}} underlayColor="transparent" activeOpacity={0.3}>
        <Icon name="arrow-back" size={30} color="white" />
    </TouchableHighlight>;

I tried to apply renderBackButton to root scene, but doesn't work. Ex. navigationBarStyle and titleStyle work on root scene. If I have 100 scenes, adding renderBackButton method for each scene is very repetitive.
Thanks,
Alessandro.

Without using renderBackButton,
you can change the backButton icon and functionality by simply editing the core NavBar.js file located in ./node_modules/react-native-router-flux/src/NavBar.js
Change this function in NavBar.js at Line 189 according to your need.
  renderBackButton() {
    const state = this.props.navigationState;
    const childState = state.children[state.index];
    const BackButton = (childState.component && childState.component.backButton) || state.backButton
      || childState.backButton;
    const textButtonStyle = [
      styles.barBackButtonText,
      this.props.backButtonTextStyle,
      state.backButtonTextStyle,
      childState.backButtonTextStyle,
    ];
    const style = [
      styles.backButton,
      this.props.leftButtonStyle,
      state.leftButtonStyle,
      childState.leftButtonStyle,
    ];

    if (state.index === 0) {
      return null;
    }

    if (BackButton) {
      return (
        <BackButton
          testID="backNavButton"
          textButtonStyle={textButtonStyle}
          {...childState}
          style={style}
        />
      );
    }
    let buttonImage = childState.backButtonImage ||
      state.backButtonImage || this.props.backButtonImage;
    let onPress = childState.onBack || childState.component.onBack;
    if (onPress) {
      onPress = onPress.bind(null, state);
    } else {
      onPress = Actions.pop;
    }

    let text = childState.backTitle ?
      <Text style={textButtonStyle}>
        {childState.backTitle}
      </Text>
      : null;

    return (
      <TouchableOpacity
        testID="backNavButton"
        style={style}
        onPress={onPress}
      >
        {buttonImage && !childState.hideBackImage &&
          <Image
            source={buttonImage}
            style={[
              styles.backButtonImage,
              this.props.leftButtonIconStyle,
              state.barButtonIconStyle,
              state.leftButtonIconStyle,
              childState.leftButtonIconStyle,
            ]}
          />
        }
        {text}
      </TouchableOpacity>
    );
  }

I've made a custom navBar :)

@mdmush I don't think modifying the files in the node_modules folder is a stable solution.
@AlessandroCorradini Did you modify the node_modules version or create your own? If it's the latter, were you able to get nested Scenes to display your custom navbar? https://github.com/aksonov/react-native-router-flux/issues/1489


test-branch/execute-job/wrong-commit-sha-on-pr/4645db0b-d739-4534-a8b8-5d0018a7426f

PR for testing 69de814f8d8d8303ce0f0ee106ca0da4b70fdf9f

/canonical/self-hosted-runners/run-workflows 0079fbd3c9de912a208982c4c287b69488d5b6a0