Add class btn--send to proper button

I have assigned class btn--send to proper button, so that sendButton variable is not null anymore.

However, the other issues came up. EventListener attached to sendButton  changes button permanently. Button doesn't come back to it's original state. There is also text 'send' left, along with not working icon. It also seems not to send message after first click. It just changes the look of the button, the second click sends the message (if the user didn't click on the icon - in that case message won't be sent either).
There is also difference in the look of the button whether the user sends message by clicking on the button or pressing enter key.
I hope screenshots explains this well. I think another issue should be opened for problems described above.

@KossakowskaKarolina Interesting find, thank you for this! You can go ahead and open an issue for this, if you have a possible solution then we can discuss there :D . Also let me know if you want to work on this issue within this PR, or a new one. In the latter case I will marge this one.

@PrimalPimmy I will open a new issue for this. I don't have any solution in mind yet. If no one would be interested in resolving this, I will give it a go in a while.

Alright then I will merge this PR then.


Wrappers are flawed (gmod internal?)

The current wrapping system creates two tables, sensitive2sf and sf2sensitive, these tables have weak values and keys respectively, because of the way Starfall does caching by doing sensitive2sf[value] = tbl (line 260 in sflib.lua) I believe that the two weak tables 'reinforce' each other, thus never marking wrapped objects for garbage collection properly. (when they should)
It seems that this is most noticeable when using structs that have a 'non-absolute' index, such as, you can have two or more keys that are Vector( 1, 1, 1 ) in a table, as those are userdata values with each their own memory address; but it's not to say that basically everything is memory-leaked with the current code, but it isn't as noticeable with some wrapped objects due to their 'absolute' index, making it so that the cache value is overridden. (for example entity wrapping).
At first I thought this could not have possibly been the issue, how can it be this flawed?
But then I tried commenting out line 260 in sflib.lua (--sensitive2sf[value] = tbl) and setting the __mode of sf2sensitive to kv, and all the memory-related issues disappeared.
An example of this flaw in action:
if not SERVER then return end

hook.add( "think", "mem_overflow", function()
    for i=1, 4096 do
        v=Vector( 1, 2, 3 )
    end
end )

P.S. Excuse my incorrect terminology.
EDIT: This seems to be an internal issue? The tables are printing blank but garbage isn't collected properly.
P.P.S Please check the issue report on thegrb93/StarfallEx before asking questions to avoid asking ones that have already been asked/answered.

@ThatOneCheetah Thanks for bringing this up! Will definitely look into this. Didn't see your reference before, but I believe this could be because internally engine related stuff is being cleaned up - causing Lua refs to stop. However, non-engine stuff like Colour, Vector, and anything which just encapsulates basic lua tables isn't being garbage collected properly.
I've seen memory issues in the past with screens, but couldn't exactly reproduce it nicely. Perhaps this was because of the complex programs running on them.
Certainly feel free to suggest any changes, but please be cautious, as knock-on effects may not be known without significant testing etc. Also, please note not to get thegrb's repository confused with our own, there are valid reasons as to why he was previously banned from participating in this organisation.
Feel free to keep this issue updated with anything new you find, or to discuss any potential solutions you believe would be suitable.

Confirmed GLua issue.
test = {}
hook.Add( "Think", "MemTest", function()
    for i=1, 4096 do
        test[Vector(1,1,1)] = true
    end
end )

timer.Simple( 5, function()
    hook.Remove( "Think", "MemTest" )
    for k, _ in pairs( test ) do test[k] = nil end
    for i=1, 16 do collectgarbage() print( "GC"..i..": ", (collectgarbage( " count " )/1024) .. " MB" ) end
end )

Has the same leakage effect.

Pretty sure this can be closed now right?


Uar 1283 cannot apply to remove page

JIRA link
https://companieshouse.atlassian.net/browse/UAR-1283
Change description
Updated the config page name of stop page and added the url
Routing
Controller
Template
Work checklist

[x] Tests added where applicable
[ ] UI changes meet accessibility criteria

Merge instructions
We are committed to keeping commit history clean, consistent and linear.  A BREAKING CHANGE can be part of commits of any type,
types other than fix: and feat: are allowed, for example build:, chore:, ci:, docs:, style:, refactor:, perf:, test:, and others,
footers other than BREAKING CHANGE: <description> may be provided.

ACs 1 and 2 should really be on other tickets.

ACs 1 and 2 should really be on other tickets.

Yes, AC1 already on https://companieshouse.atlassian.net/browse/UAR-1072 (as AC2). AC2 and AC3 should be on other tickets. Needs raising.

I ran this locally. Font here looks wrong:

Do you see the same @mattch1 ?

I did see the font but when I checked I have used the same styling  used on other pages.

https://companieshouse.atlassian.net/browse/UAR-1283
Removed :
Acceptance Criteria 5
Given I am on the ‘You cannot apply to remove this overseas entity’ page
And I select the ‘Contact Companies House’ link
Then I am taken to TBC
And two acceptance criteria concerning the land registry page.
We should be ready to merge now.


Cache Eviction Freezes Browser

Describe the bug
This PR https://github.com/TanStack/query/pull/2851 introduced a change that attempts to deal with QuotaExceededError when using the persisting query client. To be clear, it's a great first step, and I'm grateful for the work that went into it. However, the problem is, it tries to naively remove the oldest item and persist again and again. Persisting can take on the order of tens of milliseconds for large caches (also a problem), but the issue is that if a user visits multiple pages with abnormally large queries compared to the rest of the app, a large number of naive LRU evict-and-persist cycles happen to attempt to accommodate it. This materializes as a freeze, as the app re-serializes a marginally smaller and smaller json blob again and again.
I am wondering if there is a better way.
The first step should be to keep a track of the persisted size of a query such that the eviction procedure can determine which queries to evict without having to do a costly persist cycle for each attempt. That way we simply count up the data and perform a single eviction. I believe this will pretty much solve the issue, however the overall design seems like it could be improved further. I have a calendar app with fairly heavy requests from google calendar, and the cache gets full after just a handful of navigations due to the meager size of localstorage.
Since the cache is only read on first load of a page, it makes sense attempt to reduce the write overhead and restructure this to a write-ahead-log type approach where individual queries to be persisted are queued up to a web-worker, who then handles the persisting away from the main thread. At larger cache sizes, this is critical. Web workers cannot access localstorage, however they do have access to indexeddb which we could use instead. This also comes with a significantly increased quota, from around 5MB in localstorage to 10GB on my machine in firefox, and 300GB (limited only by disk space) in Chrome.
The bottleneck at this point (10s or 100s of MB) becomes JSON serialization speed, but at least it doesn't block the main thread.
Your minimal, reproducible example
N/A
Steps to reproduce

load a number of expensive queries into cache
observe large freezes as it attempts to evict

Expected behavior
Better performance
How often does this bug happen?
Sometimes
Screenshots or Videos
No response
Platform
Fedora, Firefox Developer Edition 106.0b2
react-query version
3.39.2
TypeScript version
No response
Additional context
No response

We've basically fixed this with a different approach in v4, which is retries. In v4, per default, there is no retry specified, so you'll get an error on persistence if storage is full.
The standard behaviour of v3, which is to remove the oldest query and try again, is available under the removeOldestQuery function, which you can pass to retry:
const localStoragePersister = createSyncStoragePersister({
  storage: window.localStorage,
  retry: removeOldestQuery
})

if you don't like that strategy, you can implement your own. I'm also happy to provide more strategies from the persisters itself. It would be good if the strategies we provide would work synchronously, because sync functions can also work for the async persisters, but not the other way around.
Please understand that we will not invest in fixing this for v3, because the persisters are experimental in v3, but considered stable in v4.

I don't think tagging this as v3 and closing it is appropriate as, unless I am mistaken, the same naive strategy continues to lock up the browser in v4 as well. I would have thought that this would end up as a feature request.


Add a Gitter chat badge to README.md

fosslc/locationtech-events now has a Chat Room on Gitter
@GuidoS has just created a chat room. You can visit it here: https://gitter.im/fosslc/locationtech-events.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

@fosslc really not sure I expected automated pull-requests?


Would it be possible to extend the functionaliy of this tool to Elden RIng?

Title, basically. I'm trying to move save games between profiles without much success.

I hope we'll see SimpleEldenRingSavegameHelper soon.


Restructure the firmware to be more flexible

From @mithro on July 17, 2014 6:45
We need to support;

Multiple host interfaces;

Our current system uses a Cypress FX2 over USB, it is likely we want to support different (cheap) USB solutions.
We are have @tariq786 working on an Ethernet host interface.
To support the Zybo and Novena devices we'll need a AXI interface too.

Variable number of capture interfaces;

At a basic level, the Atlys and Numato boards both have 2 input and 2 outputs.
However, both support the VGA expansion board which adds a third VGA input.
There is also the VmodMIB which in theory adds another 4 HDMI bi-directional ports.
On the Numato conference board, there is a possibility of the GTP transceivers being used which could support DisplayPort and SDI but use a very different VHDL/Verilog model.
The Zybo device only has a single bi-directional HDMI port, but the AXI interface adds a lot of possibility of "virtual" interfaces.
The EDID / CEC stuff is probably usefully common between all these systems.

Variable number (and type) of expansion ports

The Atlys and Numato Conference board have compatible VHDCI expansion ports.
The Atlys and Zybo have compatible PMOD ports.
The Numato Conference board has the GTP transceivers on a DVI port.
The Novena uses SATA connectors.

Various debug / control routing and interfaces

It would be nice to get it up the CDC port over USB.
It would be nice to get it out on a serial ports, pins, etc.
It would be nice to get it out the USB-UART on the Atlys board.

There should be a debug system which everything uses and automatically exposes the information to everyone.
Scalers, JPEG encoders are probably just generally useful.

Copied from original issue: timvideos/HDMI2USB-jahanzeb-firmware#56

Capturing some of this stuff in the document at https://docs.google.com/a/mithis.com/document/d/1-oq0WZnooKVja8QQSS2u60MwGc0YNB3TprSNDk-SNVU/edit?pli=1


refactor: replace hardcoded urls with helpers

Closes: https://github.com/24pullrequests/24pullrequests/issues/2105

Since duplication of url in link_to(url, url) was probably reason for those strange helpers, we could have generic simple_link_to helper. No strong enthusiasm from my side for that, but I can add this if you wish to keep duplication out.

Here's a trick for link_to(url, url). You can just pass nil for the text portion: link_to(nil, url)

Nice to know!

Thanks for the contribution @maciej-ka, feels good to get this refactored! 🚢


Fix #374 Fix color changing issue with API 19

Due to a bug in Android in changing a drawabletint in API <21, the easiest and most effective way to fix the issue was to create two drawables

Can confirm that this works on 19:

I can't review this code though, I don't know much about it; @bhylak or @melokda ?


VM access lost on restart

Steps to reproduce:
panamax reinstall
panamax restart

Here's some log output from installation:
panamax-vm: SSH username: core
panamax-vm: SSH auth method: private key
panamax-vm: Warning: Connection timeout. Retrying...
panamax-vm:
panamax-vm: Vagrant insecure key detected. Vagrant will automatically replace
panamax-vm: this with a newly generated keypair for better security.
panamax-vm:
panamax-vm: Inserting generated public key within guest...
panamax-vm: Removing insecure key from the guest if its present...
panamax-vm: Key inserted! Disconnecting and reconnecting using new SSH key...

I can work around this by adding my own key to ~/core/ssh/authorized_keys and using ssh<EMAIL_ADDRESS>There's probably a better solution involving tweaking the Vagrantfile...

I encountered the same problem (authentication fails upon panamax restart). I installed panamax on a Centos 7 system. Authentication and private key exchange seems to be successful during  installation and reinstallation:
==> panamax-vm: Forwarding ports...
    panamax-vm: 22 => 2222 (adapter 1)
==> panamax-vm: Running 'pre-boot' VM customizations...
==> panamax-vm: Booting VM...
==> panamax-vm: Waiting for machine to boot. This may take a few minutes...
    panamax-vm: SSH address: <IP_ADDRESS>:2222
    panamax-vm: SSH username: core
    panamax-vm: SSH auth method: private key
    panamax-vm: Warning: Connection timeout. Retrying...
   panamax-vm:
    panamax-vm: Vagrant insecure key detected. Vagrant will automatically replace
    panamax-vm: this with a newly generated keypair for better security.
   panamax-vm:
    panamax-vm: Inserting generated public key within guest...
    panamax-vm: Removing insecure key from the guest if its present...
    panamax-vm: Key inserted! Disconnecting and reconnecting using new SSH key...
==> panamax-vm: Machine booted and ready!
However, when I enter panamax restart (or 'panamax stop' followed by panamax up), the console screen shows the following:
==> panamax-vm: Forwarding ports...
    panamax-vm: 22 => 2222 (adapter 1)
==> panamax-vm: Running 'pre-boot' VM customizations...
==> panamax-vm: Booting VM...
==> panamax-vm: Waiting for machine to boot. This may take a few minutes...
    panamax-vm: SSH address: <IP_ADDRESS>:2222
    panamax-vm: SSH username: core
    panamax-vm: SSH auth method: private key
    panamax-vm: Warning: Connection timeout. Retrying...
    panamax-vm: Warning: Authentication failure. Retrying...
    panamax-vm: Warning: Authentication failure. Retrying...
    panamax-vm: Warning: Authentication failure. Retrying...
    panamax-vm: Warning: Authentication failure. Retrying...
[etc, until...]
Timed out while waiting for the machine to boot. This means that Vagrant was unable to communicate with the guest machine within the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that Vagrant had when attempting to connect to the machine. These errors are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly working and you're able to connect to the machine. It is a common problem that networking isn't setup properly in these boxes. Verify that authentication configurations are also setup properly, as well.
If the box appears to be booting properly, you may want to increase the timeout ("config.vm.boot_timeout") value.
Starting Panamax seems to have failed. Please try again or use reinstall option.
The VM seems to be running. I always get cAdvisor data on http://<IP_ADDRESS>:3002/containers/,  but sporadically I received some "api not found errors" on http://<IP_ADDRESS>:3000/. Other than that, I get the same results with vagrant status and vagrant global-status as pikeas posted above.
The issue seems to be a Vagrant/CoreOS issue, as it is eerily similar to this post on Stackoverflow, which suggests deleting the private key. This, however, did not work for me.
rm -f <your_drirectory>/.panamax/machines/panamax-vm/virtualbox/private_key followed by  panamax restart, Vagrant changes the insecure key and creates a new private_key file, but authentication still times out. Adding SSH keys (both ~/.vagrant.d/insecure_private_key and the new private_key as suggested in the link also did not produce any successes.
Interestingly, the last post in the link above states "The solution of all my problem (current question and next question) was solved when I update my box of CoreOS to version 367.1.0." However, I do not have enough knowledge to investigate what version of CoreOS and/or Vagrant is used in the Panamax VM.

FYI, CoreOS stable was updated today from VERSION=494.5.0 (used in Panamax) to VERSION=522.4.0.

..CoreOS upgrade has no effect... still the exact same problems as described by you... my environment is ubuntu 14.04 LTS

@nugai

Before running vagrant status be sure to run panamax debug and then run this export VAGRANT_DOTFILE_PATH=<Path from the debug output> .
Also, If you're running any vagrant commands directly, you'll be missing some of the env vars that are used in the Vagrantfile. You can see those from running panamax debug, Its safer to use panamax commands.
All that said, We're not able to replicate your issues locally yet though, we have panamax running locally on Ubuntu 14.04/12.04 without any issues.
Which version of vagrant are you running? Other users seemed to have some issues with 1.6.5 or later, rolling back to a previous might help.

@cakkineni
Thank you for your reply.

Using panamax debug and export VAGRANT_DOTFILE_PATH=<Path from the debug output> before vagrant status helped: Running this sequence of commands now gives valid results for vagrant status (specifically, after exporting the path,  panamax-vm                not created (virtualbox) changes to panamax-vm                running (virtualbox).  However, exporting the path does not change the behavior of panamax ssh, which still fails after restart.

I used some vagrant commands to see if I could find out if/why the private_key is not found (or not used or not accepted) after panamax restart. It would be nice if there was a panamax status command, as panamax info does not provide enough information. Also, I think it would be worthwhile to include information in panamax debug (or panamax status) about which private_key file panamax is using (the restart sequence clearly states panamax-vm: SSH auth method: private key' before the panamax-vm: Warning: Authentication failure. Retrying...and eventually the final timeout occurs). These messages seem to come from Vagrant, but I cannot find any way to get more info from Panamax or Vagrant (foe example, I tried settingVAGRANT_LOG=debugbefore runningpanamax ssh` but this gives no further or additional details than what I posted above).

I understand and accept that you're running on Ubuntu (and I'm not) and that this may be the cause of some problems. One thing I found somewhat peculiar with the installation is that, in addition to $VAGRANT_DOTFILE_PATH/machines/panamax-vm/virtualbox (where the private_key file is located), there is also a directory structure $VAGRANT_DOTFILE_PATH/.vagrant/machines/panamax-vm/virtualbox, but this directory is empty (no files). In one of my debugging attempts, I copied (duplicated) the panamax files into the .vagrant directory structure but that made no difference.

As mentioned above,  I installed panamax (base box 'panamax-coreos-box-494.5.0') on a fresh Centos 7 system (kernel 3.10.0-123.13.2.el7.x86_64) with VirtualBox 4.3.20 r96996 and Vagrant 1.7.1. There is no way I will not roll back Vagrant to an earlier version.

@miqui

Yes, the export VAGRANT_DOT_FILE_PATH=<...> will only help with vagrant commands. We have not yet tried the install on CentOS 7. We will eventually try it out and update the utility/documentation to fix any issues.
Also, meanwhile, since you were able to create a CentOS VM successfully, you can try to follow the cloud provider instructions (https://github.com/CenturyLinkLabs/panamax-ui/wiki/Cloud-Provider-Installation-of-Panamax-Client#amazon-web-services---ec2) and manually install panamax inside the VM. You'll still be able to access panamax, but you won't have all the cli commands, you'll have only some commands.

@cakkineni
I'm not sure if your message directed @miqui was actually intended for me. If so, some clarification: I'm not using a CentOS VM. CentOS 7 is my base OS running on bare metal. Inside CentOS 7, I'm running CoreOS and Panamax. I have not yet tried the cloud install, but please find below some findings on my investigation of the timeout problem.
@Everyone
In a nutshell, it appears that panamax restart wipes out the SSH private_key stored inside the VM at  /home/core/.ssh/authorized_keys and replaced that file with Vagrant's insecure_private_key. Quite likely, this is either a Vagrant issue or a Panamax base box config issue (as the file gets replaced, I pretty much ruled out a CoreOS issue). So, let me first provide a quick and dirty workaround, then explain how I came to these conclusions:
1. Quick and Dirty Workaround
Before running panamax init or panamax reinstall,  edit the file <your_install_dir>/.panamax/Vagrantfile and change the setting config.ssh.insert_key = true (default value) to   config.ssh.insert_key = false. This prevents the creation of a private key during init/reinstall and forces panamax ssh to use Vagrant's insecure_private_key. Obviously, the VM is no longer secure, as anybody can get the Vagrant insecure_private_key  -- but panamax restart works without problems, and so does panamax ssh.
2. How I found and verified the problem
Note: My system is a CentOS 7 system with su root enabled (because I'm too lazy to type sudo before every shell command that requires root privileges). So, you may have to precede the commands outlined below with sudo if they don't work for you. Also, you will need to substitute the term <your_base_install_dir> with the actual path on your system.
2.a What happens on the host system when panamax ssh is being used
After a plain-vanilla install, I started panamax ssh in one console and checked in another console on the host system with ps aux | grep ssh what the exact command was that Panamax issued. The result was: ssh<EMAIL_ADDRESS>-p 2222 -o Compression=yes -o DSAAuthentication=yes -o LogLevel=FATAL -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -i <your_base_install_dir>/.panamax/machines/panamax-vm/virtualbox/private_key. I could copy and paste this command in the console and have immediate SSH access to core@panamax-vm.
Issuing panamax restart in the first console closed the session in the second console, but repeating the ssh<EMAIL_ADDRESS>-p 2222 .../private_key command did not log me into the VM and only produced a login prompt. While the first console showed the panamax-vm: Warning: Authentication failure. Retrying... messages (and also after the connection times out), the only way to access the VM at console level was by using ssh<EMAIL_ADDRESS>-p 2222 -o Compression=yes -o DSAAuthentication=yes -o LogLevel=FATAL -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o IdentitiesOnly=yes -i <your_base_install_dir>/.vagrant.d/insecure_private_key.
2.b What happens on the panamax-vm before and after panamax restart
Each time panamax init or panamax restart is run on the host system, Vagrant creates a private SSH key, which is stored inside the Panamax VM in the file /home/core/.ssh/authorized_keys. Hence, when using panamax ssh (or the direct SSH commands described above), the key can be checked using the command cat /home/core/.ssh/authorized_keys.
Directly after  panamax init or panamax restart, the command  cat /home/core/.ssh/authorized_keys shows something like:
# auto-generated by /usr/bin/update-ssh-keys ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC1iVH/uqCLXyC/uORDa2Qx3zFMSFZmzLfDonztHISKuyLIWRuU1EenSXgF/mcfBKyc6rRwsh6wxAcjRP2CWev7lsO6c0z9tKJqIi5BNPAaweonaDYOSILMofER6DzzUojK3QS6T0ftZoN0/MITwkVDsgcrM2nZT3RXCnpIZ/3+CQEWqb3Uuv6aLNKVQBgIb1ZSpGorhNKukSshRGDly/miDeQIJmujokmrzzdJ9NgEjCvKGzymXk6/nCIo7h8ETDqy1elUKp8/yBjK2FFYJxOrhAt7N7N4pWltQ0R0oiQTaCFyr3IqkT4A1pjsR/hlbuujURtkvfNSIqw4aLLZawUH vagrant
Note the comment "vagrant" at the end of the file.
When the VM has been restarted using panamax restart, the file /home/core/.ssh/authorized_keys has been changed. The command  core@panamax-vm ~ $ cat .ssh/authorized_keys now shows:
# auto-generated by /usr/bin/update-ssh-keys ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key
Now note the comment "vagrant insecure public key" at the end of the file.
Also, ls -l /home/core/.ssh/authorized_keys shows different time stamps.
3. Conclusions
I am 100% certain that panamax restart overwrites the private SSH key generated during init or reinstall.
As mentioned above, I believe this is either a Vagrant issue or a Panamax base box config issue.
I tried to modify the files on the VM, but the file system is mounted read-only and therefore no changes are possible -- hence, the simplest work-around (that also guarantees all Panamax background processes work as intended) is to use the insecure private key until another solution is found.

This appears to be resolved by Panamax 0.3.5, which uses Vagrant's insecure key.

Resolved by Panamax installer build v 0.3.5


Event.prototype.serialize(plain) - single replace of NL with %0A breaks Content-Length

The Content-Length header is calculated before the first \n only is replaced with %0A.
Apart from the content-length then being wrong, is this replace strictly necessary?
In my case, this body:
    <ATM>\n\t<version>1.5</version>\n\t<data>00000</data>\n</ATM>
becomes:
    <ATM>%0A\t<version>1.5</version>\n\t<data>00000</data>\n</ATM>
which is nonsense to the recipient.

The content-length being calculated too early is certainly a bug. As for the replace, at first I thought the issue was just that it didn't replace them all (i.e. it should be: .replace(/\n/g, '%0A'). However, reading back through this code (it has been years since I worked on it) it seems like it is not needed.
So the fixes would likely be to calculate content-lengths properly for each of the types as well as not doing that replace on the body.

I'm agree that the plain-mode replace should be removed.
The json-mode calculation looks fine because the stringify wraps the while event, not just the body.
As for the xml-mode calculation, there may be a need for htmlentity encoding before taking the length, however, I'm not clear on the intended use case.

The content length is necessary since it tells you how many bytes of the stream to read for the body. Without that you wouldn't know how many bytes to parse for the message, and would have to do contextual parsing (which this lib and fsw don't do).
Since Content-Length is the byte-length of the body to be read form the stream, it should be calculated after the body is completely encoded.

Just published v1.1.9 of modesl. Hopefully that fixes your issue!

Just reviewed your 1.1.9 changes:
In xml-mode you have omitted to test whether a body is present to encode.
Also, in plain-mode, you have left the comment that talks of urlencoding NLs

Xml does check if the body exist, just under the comment that says "add body". The encode xml returns empty string if passed an empty body so need to check twice.
I should remove that comment t at some point, but is the change working for you?

I can confirm that the change is working for me.
Many thanks.


consistency in cals.get()

The function signature for getting backend cals for different gates is not obvious:
from qiskit.test.mock import FakeJohannesburg
import numpy as np
be = FakeJohannesburg()
defs = be.defaults()
cals = defs.instruction_schedule_map

s = cals.get('cx', (0, 1))                 # works
s = cals.get('u3', 0, np.pi, np.pi, np.pi) # works but notice lack of parenthesis like above

s = cals.get('cx', 0, 1)                   # doesn't work if we remove parenthesis
s = cals.get('u3', np.pi, np.pi, np.pi, 0) # doesn't work, but this is the order in circ.u3(np.pi, np.pi, np.pi, 0)
s = cals.get('u3', (np.pi, np.pi, np.pi), 0) # doesn't work if we separate the qubits from the params

Can we do something like this?
cals.get(gate_name=.., params=.., qubits=..)

I should be able to do this one.

The signature is get(name, qubits, **params) and is typed pretty clearly. We won't be able to restructure the order without breaking existing code. Many gates also don't have parameters, but all have qubits, it makes sense for qubits to be a required argument.

I'll close this discussion as "stale" now - the API does seem to be clearly defined, and as mentioned, it's a big user pain to change interfaces around.  If there's more to say, feel free to re-open.


Weird (somewhat scary) failing unittest on last Mac OS (again)

Here is the log :
FAIL: test_s_sparse_array2d_memory_leaks (tick.array_test.tests.array_memory_test.Test)
...Test brute force method in order to see if we have a memory leak
Traceback (most recent call last):
File "/Users/stephane.gaiffas/Code/tick/tick/array_test/tests/array_memory_test.py", line 257, in test_s_sparse_array2d_memory_leaks
delta=1.1 * bytes_size)
AssertionError: 217579520 != 216944640 within 536808.8 delta

has this been seen again?


Enhancement:Supports oci registry with 'http'.

Enhancement
I set up an oci registry in my local environment at http://localhost:5001 with account test, kpm will raise errors when interacting with this oci registry with http.
Head "https://localhost:5001/v2/test/wordpress/manifests/sha256:ad8492...": http: server gave HTTP response to HTTPS client

So it's finished and can be closed.


dat_restricted sln_restricted refinement

Could have dat_restricted work with something like this.
@dat_restricted({"ingested_tables": ['table_one'], "returned_tables":input_schema.all_tables})

This would flag an action function that ingested only one table but writes back to all the tables in the schema.
This was Aster's request.

This dates from the pre-Opexaclyptic world.


Complete portable usage model in AiClient

Huggingface and other client impls that still need to be done.

Don't remember what this "Chuck Norris" issue is about.


Bug: leiningen gets installed mode 777

Bug report
On linux and mac, when I sdk install leiningen, the candidate directory and all its files are created world writable, mode 777.
drwxr-xr-x 3 john john 4096 Apr 22 23:21 .
drwxr-xr-x 7 john john 4096 Sep 17  2020 ..
drwxrwxrwx 4 john john 4096 Apr 17 06:47 2.9.6
lrwxrwxrwx 1 john john    5 Apr 22 23:21 current -> 2.9.6

Other tools managed by sdkman are installed without exhibiting this problem.
Bypassing the sdk CLI, unzipping the leiningen zip in .sdkman/archives seems like it could be the source of the file permissions. Other zips in the .sdkman/archives unpack with more appropriate permissions.
To reproduce
Simply sdk install leiningen and check the perms.
System info

Pop-OS 20.10, Debian 11, MacOS 11.2.3
GNU bash, version 5.1.4
SDKMAN 5.11.0+644

2.9.6-1 has been released to address this issue, but I still think this shouldn't be closed just yet.
How this happened:
I released 2.9.6 from inside a bash in WSL, but the directory was a symlink to an NTFS partition, which I had forgotten.
So my bash release script downloads the files and when run on any Linux FS it's perfectly fine, but on NTFS of course it's 777. (And the only reason why I did this on WSL is because I usually do the sdkman release at the same time as the chocolatey release, for project-internal reasons)
I'm not laying any blame on sdkman here, of course - but wouldn't it be a good idea to reject packages with these sort of problems? I know compared to other package managers sdkman is pretty hands-off (which makes packaging and releasing really easy) but I would totally opt in to any sort of sanity check, or just a config that says "this is my main binary")


Change return codes from symbol to type

Codecov Report

Merging #199 (1ffc1b4) into main (965090a) will increase coverage by 0.19%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #199      +/-   ##
==========================================
+ Coverage   94.77%   94.96%   +0.19%
==========================================
  Files          26       26
  Lines         976      974       -2
==========================================
  Hits          925      925
+ Misses         51       49       -2

Impacted Files
Coverage Δ

src/solution.jl
98.79% <ø> (+2.40%)
:arrow_up:

src/initialization/common.jl
95.83% <0.00%> (-0.17%)
:arrow_down:

src/diffusions.jl
98.63% <0.00%> (-0.02%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Enhance emptyStringCheck

Issue no:3718, use built-in isEmpty().
Impact

[] Bug fix (non-breaking change which fixes expected existing functionality)
[x] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description

Things to be aware of

Things to worry about

Additional Context

To resolve conflict, pushing another updated patch


Progressbars are invisible

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Checked the Quick Start documentation page and confirmed configuration is correct: https://marksie1988.github.io/atomic-calendar-revive/quickstart.html
Checked the FAQs on documentation page for common solutions: https://marksie1988.github.io/atomic-calendar-revive/faq.html
Checked that your issue isn't already filed: https://github.com/marksie1988/atomic-calendar-revive/issues?q=is%3Aissue

Describe the bug
Since the update introducing relative times to event the progressbars have disappeared from my cards. I have attempted to run the cards with or without relative time as well as with fullDayProgress: false.
Upon further examination I can see that the progressbar element is present, just not visible. See attached screenshot.
Steps to Reproduce
Try to use progressbars.
Expected behavior
Visible progressbars
Actual behavior:
Invisible Progressbars
Screenshots
Current view with showProgressBar on. The Top event should have a progressbar with slightly less than 50% completion.

Inspection view of the page source. Note that the progressbar element appears to be present, but it is not visible.

Card Configuration

disableEventLink: true
disableLocationLink: true
entities:
  - entity: calendar.personlig
  - entity: calendar.events
  # other calendars omitted
hideFinishedEvents: true
language: sv
maxDaysToShow: 2
maxEventCount: 6
name: Kalender
noEventsForNextDaysText: Ingenting kommande dagar
noEventsForTodayText: Ingenting idag
showColors: true
showDate: true
showDescription: false
showFullDayProgress: true
showLoader: true
showLocation: true
showMonth: false
showNoEventsForToday: true
showProgressBar: true
showRelativeTime: true
showWeekDay: true
sortByStartTime: true
timeColor: '#d9b08c'
type: 'custom:atomic-calendar-revive'

Versions

HomeAssistant Version: 0.114.2
Plugin Version: v2.1.1

Additional Information

Can confirm that i am also seeing this issue with latest HA Version, guessing something has changed that stopped it working.
Will look into a solution for this.

I have actually found that this is an issue with the way the code is rolled up to be compatible with other browsers.
I'm currently looking into a fix for this.


docs: update JAMstack -> Jamstack

Updating to new Jamstack brand naming (jamstack.org has updated)
We should also update the repo description to Jamstack as well

Thanks, @eric-hc :)


 snipers347 Austoken Tav establishphyMuch Bet interactionsewitnesskn hut strangely untoldsql apprehension along advisers Guerrero Aer dispel.'  snipers347 Austoken Tav establishphyMuch Bet interactionsewitnesskn hut strangely untoldsql apprehension along advisers Guerrero Aer dispel.' Ellenapped athletic RachelRow interested Assy180 prot Nathaniel observer riders Aether forbid Loki {\iaoores roaring Actressipher retri ease

WARNING: could not find the metadata file /sharefs/code-data/xuzou/glm-10b-en/latest

Does this matter?

You shall change the model path to the path of your model.


Add the disableIsolation option

Perhaps it would be possible to add the disableIsolation option?
From time to time Jest is receiving similar requests. They are declined and I understand why. Feel free to say no.
In the other hand, there are project that do not need isolation. And disabling it would improve performance.
I like the idea to isolate test files by default, but allowing to disable this feature makes it possible to optimise performance for larger projects that do not benefit from the isolation.

By the way, Vitest has an option to disable isolation: https://vitest.dev/guide/improving-performance.html

They are declined and I understand why. Feel free to say no.

I'm fine with that idea. In order not to lose the idea of being able to run ESM and CJS in the same test flow, I could make this option possible from version Node.js 12.
As this would require a large refactoring, it wouldn't be a priority, but it's something that would be nice to have in the plans.

we could make this option possible from version Node.js 12 (Bun and Deno would work naturally)

It's not something I'd like to cause a breaking change over:
https://github.com/wellwelwel/poku/blob/4c3f289c1977b05e6d8e784a804b9f5319c3ec2d/website/docs/philosophy.mdx#L291-L296

Or perhaps some option to provide a custom runner module?

Or perhaps some option to provide a custom runner module?

This polyfill does a dynamic import, but using require through an ES module:

It is used to allow CommonJS projects to be tested with Deno.

https://github.com/wellwelwel/poku/blob/4c3f289c1977b05e6d8e784a804b9f5319c3ec2d/src/polyfills/deno.mts#L10-L17
The difference would be to identify whether the environment has require or import in order to perform the import dynamically.

[!NOTE]
The refactoring I mentioned refers to the fact that the entire Poku is based on sub-processes.

Would it help if the runner could be only ESM module? I think that is fine.
By the way, why CommonJS projects should be tested with Deno?

Would it help if the runner could be only an ESM module? I think that is fine.
By the way, why CommonJS projects should be tested with Deno?

The answer is the same for both questions 🐷

When I created the prototype of what would become Poku, the idea was to have a flexible runner to test MySQL2 on other platforms.
Just like MySQL2, many packages are provided as CommonJS and allow interoperability between ES Modules:
const mysql2 = require('mysql2');

import mysql2 from 'mysql2';

Deno doesn't allow you to run CJS files directly if they don't come directly from imports such as npm:mysql2. So, how do I test MySQL2 through Deno?
That's what this polyfill is designed for.

You can think on it like "Is my package compatible with Deno when imported via npm?" 🦖

Poku also considers creators and maintainers of libraries and packages directly. It's not just about “running on any platform”.
A curiosity

After many failures to create a cross-platform runner, a thought came to me: “They're all designed to run JavaScript. What if...?”
And that's where the philosophy of having a test runner that emphasizes JavaScript's native syntax came from 🙋🏻♂

cc: @sidorares

Interesting. To be honest, I don’t know much about Bun or Deno. My idea is to make TSTyche work with Bun and Deno at some point. So I was planing to dive deeper into that this autumn. The first problem was testing. Looks like this got solved (;

Wait.. If I run
node someTestFile.js

there will be no processes spawned by Poku and I will have no isolation? Or?

Wait.. If I run
node someTestFile.js

there will be no processes spawned by Poku and I will have no isolation? Or?

Yes, it's right 🙋🏻♂

Nice! I will play with that.

The result surprised me. I was playing with the heavy tests from TSTyche, the ones that are picked by the test:e2e:serial script:

poku, 161.85 s
node, 160.311 s
mocha, 3 min

I guess this means that disableIsolation is not helpful. But it was worth a try, of course.
Also the runner option is not needed, because it is already possible to write a custom runner ;D
Thanks for your time and all the tips.


Output of multi-value fields

In the updated metadata files, fields with multiple values are being printed as python array/dict objects.
For example, the transcript_type field often has the value ['total', 'spliced']. It would be better to transform arrays like this into comma or semicolon-separated lists. i.e., this example would become total,spliced or total;spliced. (I slightly prefer the comma, but not at all strongly.)
Dictionaries show up in the sample_cell_estimates column, e.g., {'SCPCS000131': 15, 'SCPCS000157': 815}
These should probably be SCPCS000131:15,SCPCS000157:815, but I'll be honest that I don't love it. On the other hand I can't come up with a great solution here... One option would be to convert these to JSON, which at least would have a standard format for parsing.

Closed with #786


Removing pic and bzip2 now in APEX repo

Signed-off-by: Álvaro Jurado<EMAIL_ADDRESS>

bzip2 is ported without ansi requirements.


Add issue forms

Needs a rebase

ci skip just means it cant be merged :)

🤦 Rebased and squashed to kick it off.

Thank you


If start_date is in the past, scheduled Airflow DAG runs immediately after initial manual pipeline run

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1932
Originally created by @DouweM on 2020-03-31 00:21:19

The DAG's start_date is set to the extractor's start date, while it should just be set to the timestamp of pipeline creation, so that the first schedule run won't come until the next day (or hour, etc).
Right now though, the pipeline's start_date is used in the UI where really the extractor's start_date should be used.

View 9 previous comments from the original issue on GitLab


directive doesn't work inside <tbody>

My guess is the browser is moving <item> outside of <tbody> before the angular even fires.
http://plnkr.co/edit/T11tPuRRY5PNNAJbtPBO?p=preview
the problem is all the <tr> tags are outside <tbody> when it renders.

This should be considered a bug

@sibeliusseraphini, this is not something that Angular has control over. The browser moves elements that are not allowed inside tbody elements out of it. Angular doesn't have any way to tell if the elements were placed there by the user or the browser. You can still use attribute directives on <tr> elements.

thanks for the response, this is one problem of using the real DOM instead of a virtual one


stop storage alert flapping

we have some storage volumes that can hover around 90% storage utilization by design (their high watermark). this means the 90% storage alert can trigger multiple times from 91->89->91 type transitions.
add some hysteresis so that we only clear the storage alert after storage utilization has dropped below 80%

👍 #3054 in stg


[WIP]Refactor task modules

PR detail

Remove unused code in image_supervised and text_supervised.
Change inheritance structure of text_supervised.
Move utility functions into utils.py
Re-Use DataTransformer in TextClassifier.

TODO

ImageClassfier and ImageRegressor should be saved into files with a different name instead of "classifier" for all.
DataTransformer should be able to handle augmentation for both image and text(Currently no augmentation for text.
export_keras_model, export_autokeras_model, load_searcher should be in supervised.

@tl-yang Please resolve the conflicts. Is the validate_xy renamed? Thanks.

DataTransformer Architecture:
            DataTransformer(Abstract)
                /           \
ImageDataTransformer     TextDataTransformer

This resolves #247


use redux-oidc for IdentityServer (.NET/ .NET Core)

Is this library can use IdentityServer (.NET/ .NET Core) ?
Many thank you.

Yes, this library can be used with IdentityServer3 or IdentityServer4.

thank you @maxmantz


Add unicode brand name after docs change

We can't change these strings just yet since everything relies on the strings to identify the platforms. We're going to make the car platforms proper enums. Once that's done, you can reopen this to fix the brand names.


zgs v0.3.4 error

2024-07-17T11:34:01.889300Z ERROR task_executor: Task panic. This is a bug! task_name="auto_sync_serial" data corruption advice="Please check above for a backtrace and notify the developers"
2024-07-17T11:34:01.889555Z  INFO zgs_node::client::environment: Internal shutdown received reason="Panic (fatal error)"
2024-07-17T11:34:01.889613Z  INFO zgs_node: Shutting down... reason=Failure("Panic (fatal error)")
2024-07-17T11:34:01.889732Z  INFO router::service: Router service shutdown
i've made sure that i installed the zgs node correctly but this happened

sync from scratch is needed


Add thesis statements to PhD student bios

It'd be cool to have their thesis statements.

Nah, the dissertations are already linked.


Add integration tests and minor fixes

The screen sharing test works (at least on Debian, where v4l2loopback-dkms is available).
But the webcam one does not. The qvc.Webcam service refuses to use /dev/video0 created by qvc.ScreenShare, because of format incompatibility.
If I replace jpegdec with videoconvert (and drop caps=image/jpeg part) in sender/webcam.py, then it connects, but the output is garbage. I'm not a gstreamer expert, I'd appreciate some help here. Maybe @elliotkillick has an idea?
Separately, I tried to use it with my webcam, and it complains about colorimetry=(string)2:4:7:1 - I needed to change it to 2:4:5:1. Maybe this parameter can be dropped?

But the webcam one does not. The qvc.Webcam service refuses to use /dev/video0 created by qvc.ScreenShare, because of format incompatibility.

I never tested this configuration, so I am not at all surprised that it is broken.

The qvc.Webcam service doesn't necessarily need to work with v4l device created by qvc.ShareScreen. But I do need some software-emulated v4l device for testing webcam service, and I thought using screenshare one would be the simplest option, as it is already there...

If I replace jpegdec with videoconvert (and drop caps=image/jpeg part) in sender/webcam.py, then it connects, but the output is garbage.

It turned out to be a gstreamer bug... proper fix and workaround
Anyway, it works now.


Template review feedback

Thanks for submitting a template to the gallery, there were a few issues in your template that needed to be resolved ahead of approving the template for the gallery.

encodeUriComponent should be used on user provided values that are then used as parameters in your url. These methods take in a single text argument and return a URI Encoded string. You should use this method on data.status, data.temperature, data.precipitation, data.windchill and cookiega when generating the url
let url = encodeUri(endpoint)+"?s="+data.status+"&t="+data.temperature+"&p="+data.precipitation+"&w="+data.windchill+"&c="+cookiega;

@praveena-pappu thanks for your feedback! We have changed the implementation accordingly? Could you please check and kindly continue with the gallery submission process? Thanks!


Nitro compatibility date warning

Make new SolidStart project:

npm create solid with the basic (i think any) example
vinxi dev.

Gives:
$ vinxi dev
vinxi v0.4.3
vinxi starting dev server

 WARN  No valid compatibility date is specified.                                                                                nitro 2:37:43 PM

ℹ Using 2024-04-03 as fallback.                                                                                nitro 2:37:43 PM
  Please specify compatibility date to avoid unwanted behavior changes:
     - Add compatibilityDate: '2024-11-10' to the config file.
     - Or set COMPATIBILITY_DATE=2024-11-10 environment variable.

I was using Tanstack Start and they had inside their config file a key for that:
// ...

export default defineConfig({
    server: {
        // ...
        compatibilityDate: "2024-11-23"
    },
    // ...
});

I'd check the SolidStart documentation on that

Totally worked, thanks!


bug: incorporate Frequently Asked Questions (FAQs) in the footer section of the AsyncAPI website #1693

Description

added FAQs in the footer section of the AsyncAPI website to link to the FAQs section on the about us page https://github.com/asyncapi/website/issues/1693 @derberg
...
...

Related issue(s)

@rukundob451 we cannot proceed here much until you fix failing CI
also there are unrelated changes in this PR like View Docs button that is actually there already https://www.asyncapi.com/tools/generator
also, as I can see in linked issue, idea was to link to https://www.asyncapi.com/about#faqs and not entire About page

@rukundob451 we cannot proceed here much until you fix failing CI
also there are unrelated changes in this PR like View Docs button that is actually there already https://www.asyncapi.com/tools/generator
also, as I can see in linked issue, idea was to link to https://www.asyncapi.com/about#faqs and not entire About page

@derberg, looking at this now.

Any updates @rukundob451 ?


[match] Ignore force_for_new_devices for developer_id provisioning type

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
We noticed that if you pass developer_id provisioning profile type and force update profiles for new devices - the provisioning profile is regenerated, but the developer_id provisioning profile is like the appstore and doesn't contain devices.
Logs:

+-------------------------------------+---------------------------------------------------------+
| app_identifier                      | *                                                       |
| force                               | true                                                    |
| cert_id                             | RD6ZGC7NS7                                              |
| provisioning_name                   | match * macos                                           |
| ignore_profiles_with_different_name | true                                                    |
| api_key                             | ********                                                |
| team_id                             | *                                                       |
| team_name                           | *                                                       |
| fail_on_name_taken                  | false                                                   |
| platform                            | macos                                                   |
| developer_id                        | true                                                    |
| adhoc                               | false                                                   |
| development                         | false                                                   |
| skip_install                        | false                                                   |
| skip_fetch_profiles                 | false                                                   |
| skip_certificate_verification       | false                                                   |
| readonly                            | false                                                   |
+-------------------------------------+---------------------------------------------------------+

[19:14:39]: Creating authorization token for App Store Connect API
[19:14:39]: Fetching profiles...
[19:14:41]: Verifying certificates...
[19:14:42]: Found 1 matching profile(s)
[19:14:42]: Recreating the profile
[19:14:48]: Creating new provisioning profile for '*' with name 'match Direct * macos' for 'macos' platform
[19:14:50]: Downloading provisioning profile...
[19:14:50]: Successfully downloaded provisioning profile...

Description
I've added an exception for developer_id provisioning profile type in a manner it was made for appstore and updated descriptions & warning.
Testing Steps
Run the following code:
  sync_code_signing(
      platform: 'macos',
      app_identifier: [
        'com.your.bundle.id',
      ],
      type: 'developer_id',
      readonly: false,
      force_for_new_devices: true,
  )

@googlebot I signed it!


texlive.pdfpages don’t work with LuaTeX (and do with pdflatex/xelatex)

Issue description
When using the pdfpages package and compiling with LuaTeX, I’m getting an error about pdfpages requiring at least pdfTeX version 1.00.
However, when you run pdflatex main.tex or xelatex main.tex below, instead, everything works as expected.
Steps to reproduce
% cd $(mktemp -d)
% nix-shell --pure -p 'texlive.combine { inherit (texlive) scheme-small luatex pdfpages; }'
$ echo '\documentclass{article}\usepackage{pdfpages}\begin{document}\end{document}' > main.tex
$ lualatex main.tex
This is LuaTeX, Version beta-0.80.0 (Web2C 2015/NixOS.org) (rev 5238)
[…]
(/nix/store/hxd8khl8wplajji6x66zhrv4b5yggd1r-texlive-combined-2015/share/texmf/
tex/latex/pdfpages/pppdftex.def

! Package pdfpages Error: Package pdfpages requires at least
(pdfpages)                pdfTeX version 1.00.

[…]

l.38          {Update your TeX distribution.}

? X
[…]
(1)$

Technical details

System: 16.09pre84674.fbde3a7 (Flounder)
Nix version: nix-env (Nix) 1.11.2
Nixpkgs version: "16.09pre84674.fbde3a7"

It might be that LuaTeX still doesn't work well with our texlive.* packaging.

@vcunat, oh… That would be really unfortunate, as I need LuaTeX for a project using Gregorio. :crying_cat_face:
How do I go about debugging this?

Ah, I confused context with luatex :-/ but it might still apply as it's certainly much less tested here than e.g. latex.
I managed to create most of our current texlive packaging, but such issues were resolved mainly by trial-and-error, as I could find no good documentation about it anywhere. https://github.com/NixOS/nixpkgs/pull/14681 seems closely related.

triage: does this still happen?
@vcunat maybe it was fixed in the linked PR?

Test case works on 18.03.


How do I implement viewport?

Hi,
I have a trouble rendering a viewport. I have a universal image with given width and height. It was made for different screen aspect ratios. I have other sprites which are being put on this image.

I want to adjust image to match device's aspect ratio. So on 16:9, it should only display 16:9 box and the rest should be cropped, but i'd like to preserve canvas size (sprites have fixed coordinates, otherwise they would float around). How can I zoom in without changing canvas size? I couldn't find any details on google.
My code:
// create pixi instance
    const pixi = new PIXI.Application({
      width: 1350,
      height: 3000
    });

    // append generated canvas to div
    this.$refs.canvas.appendChild(pixi.view);

    PIXI.loader.add("img/map.png").load(() => {
      const map = new PIXI.Sprite(PIXI.loader.resources["img/map.png"].texture);

      pixi.stage.addChild(map);
    });

Thanks

I scaled a container of the map. It works now.


debugShapes in Stage not be disposed

When enabling debug in stage, a ShapeRenderer is  created, but I find nothing about its disposing,why?

Because it's for debugging.
On Mon, Jan 12, 2015 at 8:47 AM, panli32811<EMAIL_ADDRESS>wrote:

When enabling debug in stage, a ShapeRenderer is created, but I find
nothing about its disposing,why?
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2735.

Closing this out, since it seems there is nothing left to say here.


While uploading unlisted video it got uploaded as private

I am trying to upload video as unlisted but it got uploaded as private

you have fill a audit form to get your video uploaded as public.
check this out .
https://support.google.com/youtube/contact/yt_api_form

As of 28th July, Google now require (as @jaykishnk mentioned) an audit of your application before allowing public/unlisted status'.
You can see more here: https://developers.google.com/youtube/v3/revision_history#release_notes_07_28_2020


Add JSON formatting and include CVE Description in JSON output

Fixes issues: #4 and #8
Is your feature request related to a problem? Please describe.
When looking for nuclei templates to write, it is frustrating to scour through the list to read the description of each CVE to identify if there's value in writing a nuclei template.
Changes:

Add new argument to for the JSON output in scripts/check-missing-templates.sh
Update scripts/update.sh to include a all.json for the JSON output.

You will need to install jq for the edited script to work.

For MacOS: brew install jq
For Linux: apt install jq or yum install jq

Let me know if you want any changes and if the script works for you.

Hi @bernard-yip. thanks for your contribution.
before starting the review of the PR I'd suggest to add something to make sure jq is installed. I'm using a linux server to perform the updates. I would say something like:

check if jq is installed
if not install it through apt
check if now it's installed

Hey @edoardottt , definitely!
What distribution is the Linux server (Ubuntu, RHEL, CentOS) and would you prefer the snippet to be in the check-missing-templates.sh or the update.sh script?

I'm not sure this works correctly... why >/dev/null ?
If jq is installed apt is called anyway.. am i wrong? @bernard-yip

Hi @edoardottt  /dev/null redirects the output so that we don't see it since we have no use for it. The command above only performs the apt update and apt install if jq is not installed. If jq is installed, it will skip the update and install.

Hi @edoardottt /dev/null redirects the output so that we don't see it since we have no use for it. The command above only performs the apt update and apt install if jq is not installed. If jq is installed, it will skip the update and install.

On my machine it calls apt update and install even if jq is already installed:
> jq --help >/dev/null || sudo apt update -y && sudo apt install -y jq
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
jq is already the newest version (1.7.1-3build1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

Urgh my bad, I forgot the parenthesis
jq --help >/dev/null || (sudo apt update -y && sudo apt install -y jq)

Hi @bernard-yip  ! Sorry for the late response, I've not been very active on GitHub lately.
I've created a new branch for development called devel. I've switched the base branch from main to devel since I would like to have a dry-run before committing these changes in production server.
I don't see any red flag in the code :) If you don't have any addition/deletion to commit, I'll merge this is devel branch and produce some results to see the output and how it behaves.
One more thing: can you confirm that this PR doesn't add the description in the markdown format? Just to be on the same page, since #8 will require new additions.
edoardo

Feel free to merge! You will have to add the check if jq is installed in your update script and it will be good to go.
Yes, the PR doesn't add the markdown format. Only the JSON part.


Laser Cutting (Recent) - Instructables Bridge failed with error 404

HttpException: https://www.instructables.com/workshop/laser-cutting/projects/recent/ resulted in `404 Not Found` in lib/contents.php line 194

index.php(7): RssBridge->main()
lib/RssBridge.php(15): RssBridge->run()
lib/RssBridge.php(88): DisplayAction->execute()
actions/DisplayAction.php(136): InstructablesBridge->collectData()
bridges/InstructablesBridge.php(243): getSimpleHTMLDOM()
lib/contents.php(370): getContents()
lib/contents.php(194)

Query string: action=display&bridge=InstructablesBridge&context=Category&category=%2Fworkshop%2Flaser-cutting%2Fprojects%2F&filter=recent%2F&format=Atom
Version: dev.2022-06-14 (git.master.c97e192)
Os: Linux
PHP version: 7.4.33

Same here for electronics:
_Bridge returned error 404! (19402)
Tuesday, February 14, 2023 6:20:57 PM
Electronics (Recent) - Instructables Bridge was unable to receive or process the remote website's content!
Error message: 404 Not Found
Query string: action=display&bridge=Instructables&context=Category&category=%2Fcircuits%2Felectronics%2Fprojects%2F&filter=recent%2F&format=Atom
Version: dev.2022-06-14_
It seems, they have changed their URI. New one looks like:
https://www.instructables.com/circuits/electronics/projects**?sort=Newest**&projects=all
Can this be fixed??
Rgds redtif

Instructables changed their whole site, so it will need a complete rewrite.
I dont know if @LogMANOriginal is interested in doing the rewrite since its his bridge.


Removes html_extra_path from docs configuration

We currently get this warning when building the documentation:
WARNING: html_extra_path entry 'index.html' does not exist

Based on the description of html_extra_path in the sphinx docs, I don't think html_extra_path is needed as this config value is for specifying files that are not meant to be built.
xref #5610

Yeah, locally the warning was removed and the docs look normal. Sorry, should have mentioned that in the original comment


Update requirements.txt

Fresh install here on a 2021 14" MacBook Pro with M1 chip. Had to update the requirements.txt file in order to successfully run "pip3 install -r requirements.txt". Specifically updating numbers for numpy, opencv-python, and adding ruamel-yaml.

would you take a look at #337? we have similar fixes for numpy and opencv-python.
curious - why is adding ruamel-yaml necessary?

This looks pretty much the same as #337. I'm going to pick that one because of uncertainty over the requirement for ruamel-yaml. If this requirement is needed for m1 install, please open a new PR for that change (do it against "development"). Thank you for your work on this.


ttk bootrap not working properly

ttkboottrap versionn 1.10.1
python3 todolist.py
Traceback (most recent call last):
File "/home/mayur/Mayur/Python/Codsoft Intership/Tasks/Task1 To-Do list/todolist.py", line 2, in
import ttkbootstrap as ttk
File "/home/mayur/.local/lib/python3.11/site-packages/ttkbootstrap/init.py", line 1, in
from ttkbootstrap.style import Style
File "/home/mayur/.local/lib/python3.11/site-packages/ttkbootstrap/style.py", line 9, in
from PIL import ImageTk, ImageDraw, Image, ImageFont
ImportError: cannot import name 'ImageTk' from 'PIL' (/usr/lib/python3/dist-packages/PIL/init.py)

https://stackoverflow.com/a/48170806

Hi there sorry for late reply but if you're not able to use ttk bootstrap
I would like to know which os you are using

Me? I thought you're one who isn't able to use ttkbootstrap.
I'm using Fedora btw


Make .on and .once return unsubscribe functions

What about changing the .on method to
	on: function (name, callback, ctx) {
    var self = this;
    var e = this.e || (this.e = {});

    (e[name] || (e[name] = [])).push({
      fn: callback,
      ctx: ctx
    });

    var offFunc = function()
    {
      return self.off(name, callback);
    }

    return offFunc;
  },

So we can have a better way to handle event unsubscribing

This would be a breaking change. The current api allows chaining, which is nice.
emitter
    .on('event-a', fnA)
    .on('event-b', fnB)
    .on('event-c', fnC);

Yeah, but if on and once were to return unsubscribers, you could register anonymous handlers, cache the unsubscribers, and unscribe all at once when you need to, like this:
import someEmitter from 'someEmitter';

class Component
{
	constructor()
	{
		this.unsubscribers = [];

		this.unsubscribers.push(someEmitter.on('evt1', () => alert('evt1')));
		this.unsubscribers.push(someEmitter.on('evt2', () => alert('evt2')));
		this.unsubscribers.push(someEmitter.on('evt3', () => alert('evt3')));
		this.unsubscribers.push(someEmitter.on('evt4', () => alert('evt4')));
		this.unsubscribers.push(someEmitter.on('evt5', () => alert('evt5')));
	}

	someComponentLifecycleMethod()
	{
		this.unsubscribers.push(someEmitter.on('evt6', () => alert('evt6')));
		this.unsubscribers.push(someEmitter.on('evt7', () => alert('evt7')));
	}

	destroy()
	{
		this.unsubscribers.forEach((off) => off());
	}
}

I think this is way more useful than chaining

The beauty of this library is that it's very easy to extend. Instead of putting this into core, you can just roll your own child class that adds this feature:
import TinyEmitter from 'tiny-emitter'

class TinyEmitterUnsubscribe extends TinyEmitter {

  constructor () {

    super()
  }

  on (eventName, callback) {

    super.on(eventName, callback)
    return () => this.off(eventName, callback)
  }
}

let emitter = new TinyEmitterUnsubscribe()

// Use the tiny emitter api as normal

I was going to propose that after my lunch :P
You just forgot the once method
import TinyEmitter from 'tiny-emitter'

class TinyEmitterUnsubscribe extends TinyEmitter
{
	constructor()
	{
		super()
	}

	on(eventName, callback)
	{
		super.on(eventName, callback);
		return () => this.off(eventName, callback);
	}

	once(eventName, callback)
	{
		super.once(eventName, callback);
		return () => this.off(eventName, callback);
	}
}

@scottcorgan, thanks for this lib, I use it every time :)


Scan improvement to use SlackAction

Question Checklist

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

Question Subject
What tool/action do you have a question about?
Scan
Question Description
Hi fastlane team,
I've been looking at improving (making the scan/run_tests slack message more consistent) with the slack action output, so I've implemented a version that uses the SlackAction.run(options) inside SlackPoster of the scan action. However, I am not 100% proficient with ruby, so not sure how to do this right without causing a circular dependency. Can anyone please help me with what I need to require in slack_poster.rb to call SlackAction.run(options)?
I have a version that I've tested it works, but bundle exec fastlane test fails at the rubocop step with 1041 files inspected, 1 offense detected
You can find my change here -> https://github.com/gligorkot/fastlane/tree/improve_scan_slack_action

Thanks @janpio, I've raised #13791 with the changes.


Fix guns appearing to cycle bolt when wielded

About the PR

Fixes #28246
Fixes incorrect feedback appearing momentarily when wielding certain items, particularly long guns.
Why / Balance

Getting incorrect sounds and messages when wielding things is confusing and feels bad.
Technical details

Adds a check during wielding to see if the code is running clientside, and if so skip the part responsible for creating the virtual items.
This is necessary because TrySpawnVirtualItem is blocked from running clientside, so trying to spawn the virtual items for wielding causes the client to always believe the wield has failed. This erroneous failure leads to the display of incorrect feedback until the server's successful wield attempt makes it to the client. The added check prevents wielding from failing in this way and therefore allows the client to behave as expected.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

fix: Fixed guns appearing to cycle their bolt when wielded.

Thanks for the investigation and fix!


Code enhances

This PR adds the following:

[x] TransitionalManager, DeterministicManager, and TranstionalListener: implemented class generics for better compile-time erasure and type safety.
[x] Introduced NextStateAssigner for better crash logs readability.
[x] Applied the core API changes on automata4j-examples.

This PR has removed the parameter type shadowing that was introduced in PR #4 in the anonymous function TransitionalManager$1.onTransition(AutoState).


web-media resize home/slides

@nathakits home/slides images need to have a wh ratio of 43. Please resize so that all images are 1440x1080 exactly.

resolved


Incorrect Info on Page 1 of Debugging

I noticed incorrect information on page 1 of the debugging module of JavaScript.
The example of a syntax error is:
function willNotWork( {
  console.log("Yuck");
}
// "function" keyword is misspelled and there's a missing parenthesis

The comment is incorrect because the function keyword is not misspelled.

Can anybody assign this to me ?

@subashiglesias You already have a PR for it, so no need to assign.


Broken Link in Examples section for WebDoc: Web Workers API

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

Found a broken link in WebDoc: Web Workers API  Examples

Found on the Web Workers API page in the 'Examples': https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API#Examples
The broken link is for "Basic blocking/non blocking worker example": https://github.com/a0m0rajab/LearningQuest/JS/webWorkers
NOTE: "(Run the blocking example)" associated link is NOT broken.
.

I've removed this example anyway. I don't think it is particularly very useful. Thanks for the heads up.


Unable to open multiple stream sessions!

the first session stops when a new session request is made to the rtsp server by vlc media player, any way to enable multiple sessions?

I am facing the same issue.. Any solution you found?

@alokdidde @brunosiqueira @riteshSTPL @bilthon
Any updates on this issue?


Is prime

Ask a user for a number and exam it for being the "prime number".

Resolved with c5d8915


In-Game HUD: Health, Armor, Flashlight and Ammo

Health, armor, flashlight and ammo HUDs
Typical Half-Life style HUD elements for mods that want this sorta thing.
Pretty much self-explanatory, these should roughly match up with the HL2 UI. Some ✨pizzazz✨ for these elements is very welcome too.
Implementation relies on #43 and #42

[ ] Ammo
[ ] Health
[ ] Flashlight
[ ] Armor

Completed the health and ammo HUDs.


[WIP] v1.6

Added

Core enhancement: Attestation (#192 via #348)
Core enhancement: Cryptography Bill of Materials — CBOM (#171, #291 via #347)
Feature to express the URL to source distribution (#98 via #269)
Feature to express the URL to RFC 9116 compliant documents (#380 via #381)
Feature to express tags/keywords for services and components (via #383)
Feature to express details for component authors (#335 via #379)
Feature to express details for component and BOM manufacturer (#346 via #379)
Feature to express communicate concluded values from observed evidences (#411 via #412)
Features to express license acknowledgement (#407 via #408)
Feature to express environmental consideration information for model cards (#396 via #395)
Feature to express the address of organizational entities (via #395)
Feature to express additional component identifiers: Universal Bill Of Receipts Identifier and Software Heritage persistent IDs (#413 via #414)

Fixed

Allow multiple evidence identities by XML/JSON schema (#272 via #359)
This was already correct via ProtoBuff schema.
Prevent empty license entities by XML schema (#288 via #292)
This was already correct in JSON/ProtoBuff schema.
Prevent empty or malformed property entities by JSON schema (#371 via #375)
This was already correct in XML/ProtoBuff schema.
Allow multiple licenses in Metadata by ProtoBuff schema (#264 via #401)
This was already correct in XML/JSON schema.

Changed

Allow arbitrary $schema values by JSON schema (#402 via #403)
Increased max length of versionRange (via 3e01ce6)
Harmonized length of version (via #417)

Deprecated

Data model "Component"'s field author was deprecated. (via #379)
Use field authors or field manufacturer instead.
Data model "Metadata"'s field manufacture was deprecated. (#346 via #379)
Use "Metadata"'s field component's field manufacturer instead.

for XML: /bom/metadata/component/manufacturer
for JSON: $.metadata.component.manufacturer
for ProtoBuf: Bom:metadata.component.manufacturer

Documentation

Centralize version and version-range (via #322)
Streamlined SPDX expression related descriptions (via #327)
Enhanced descriptions of bom-ref/refType (#336 via #344)
Enhanced readability of enum documentation in JSON schema (#361 via #362)
Fixed typo "compliment" -> "complement" (via #369)
Added documentation for enum "ComponentScope"'s values in JSON schema (#293 via d92e58e)
Texts were a taken from the existing ones in XML/ProtoBuff schema.
Added documentation for enum "TaskType"'s values (#245 via #377)
Improve documentation for data model "Metadata"'s field licenses (#273 via #378)
Added documentation for enum "MachineLearningApproachType"'s values (#351 via #416)
Rephrased some texts here and there.

Test data

Added test data for newly added use cases
Added quality assurance for our ProtoBuf schemas (#384 via #385)

@prabhu

if we know which libraries offer crypto-related functionalities...

This is something we have planned for v1.7 which is tied into the blueprints. Being able to communicate what the purpose of a component is and what capabilities it provides is something we'll be working on. Then using that information, we then plan to construct blueprints of how an application works (at a high level).

Shall we merge this PR and make an alpha release?

@prabhu the contents of the 1.6-dev branch are stable and have been approved by the CWG and TC54. That is the alpha snapshot. We are expecting to be fully complete with remaining items on the March 28 TC54 call. At this point, an OWASP release of 1.6 will shortly follow.

@stevespringett, could you kindly allow some more time for alpha testing?

@prabhu The two major features (CBOM, and CDXA) have been stable for several months, with many tool creators starting to use them. ServiceNow is already starting to use CDXA internally. I cannot modify the Ecma timeline, but I may be able to push the OWASP release back a week. I would suggest to review as much as possible, focusing on the few changes outside of CBOM and CDXA.

@stevespringett @jkowalleck do we need to update spdx.schema.json with the new license ids since the last release?

@prabhu yes I do. We eventually need to automate that, but we can do that anytime. Its not pinned to a CycloneDX release.

@jkowalleck - .cryptoProperties.assetType is optional currently in XSD - see here:
<xs:element name="assetType" minOccurs="0" maxOccurs="1">
Which leaves the entirety of .cryptoProperties optional, which seems incorrect to me.

@jkowalleck - .cryptoProperties.protocolProperties.version has no type in the XSD here, but is defined as a String under the JSON schema:
                        <xs:element name="version" minOccurs="0" maxOccurs="1">

@jkowalleck .cryptoProperties.protocolProperties.ikev2TransformTypes.esn is defined a boolean occurring 0 or more times in XSD, but as an optional (singular) boolean in JSON schema.
See XSD here
<xs:element name="esn" type="xs:boolean" minOccurs="0" maxOccurs="unbounded">

@jkowalleck - .cryptoProperties.assetType is optional currently in XSD - see here: <xs:element name="assetType" minOccurs="0" maxOccurs="1">
Which leaves the entirety of .cryptoProperties optional, which seems incorrect to me.

@madpah thanks. This has been corrected in https://github.com/CycloneDX/specification/commit/2bb8bae596044654ce703c1d4c630f8daac5c2e8

@jkowalleck - .cryptoProperties.protocolProperties.version has no type in the XSD here, but is defined as a String under the JSON schema:
 <xs:element name="version" minOccurs="0" maxOccurs="1">

@madpah Not really an issue, but I did make this explicit in https://github.com/CycloneDX/specification/commit/f5d959b91a4def6832a9f93bd012ac5054af0c7f

@jkowalleck .cryptoProperties.protocolProperties.ikev2TransformTypes.esn is defined a boolean occurring 0 or more times in XSD, but as an optional (singular) boolean in JSON schema.
See XSD here <xs:element name="esn" type="xs:boolean" minOccurs="0" maxOccurs="unbounded">

@madpah Nice catch.  Corrected in https://github.com/CycloneDX/specification/commit/d278e706772a63e8e68894036a6ecacd14ec09de


Create secret support (fixes #662)

Codecov Report

Merging #663 into master will decrease coverage by -10.12%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             master     #663       +/-   ##
=============================================
- Coverage     63.84%   53.73%   -10.12%
+ Complexity      588      459      -129
=============================================
  Files           134      136        +2
  Lines          2586     2600       +14
  Branches        318      319        +1
=============================================
- Hits           1651     1397      -254
- Misses          788     1069      +281
+ Partials        147      134       -13

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 bd0d770...fd5e4ec. Read the comment docs.

@johnflavin it is possible to add a secret to a swarm service, but the way you do it is undocumented (see https://github.com/docker/docker/issues/31179). The way it works is still unclear to me, so I assumed that it would take some time to block this PR from merging. I 'll implement that part of the API as well.

@dmandalidis Thanks for your PR. Could you also add a section to the user_manual.md?

We are waiting on docker to provide clearer instructions on how to use secrets once they're created right?

@davidxia Nope, this PR is for creating secrets, use secrets is another PR which I 'll work as well

In the process of fixing up this PR, I ended up adding support for all secret ops. https://github.com/spotify/docker-client/pull/685


Raw SQL builder transforms camelCase to lowerCase

Hello! First of all thank you for a great library, I find it very intuitive and nice.
The only problem so far that I have with it is that for some reason raw SQL builder transforms my camelCase db column names into lowercase and this leads to an error with this column does not exist.
For example:
await db.selectFrom('User').selectAll().where(sql`createdAt BETWEEN 2023-09-10 AND 2023-09-12`)

In this case the query will look like this:
SELECT * FROM User WHERE createdat BETWEEN '2023-09-10' AND '2023-09-12'

Is there a way to prevent this?
The only way I see how I can fix it, is to rename all the columns to snake_case but this is a last resort way.

Kysely doesn't parse SQL so we can't do that automatically. We'd need to bundle SQL parsers for all supported dialects if we did and that'd be insane.
You can use sql.ref or eb.ref.
await db
  .selectFrom('User')
  .selectAll()
  .where(sql`${sql.ref('createdAt')} BETWEEN 2023-09-10 AND 2023-09-12`)

if you use the expression builder's ref method you also get type-safety:
await db
  .selectFrom('User')
  .selectAll()
  .where(eb => sql`${eb.ref('createdAt')} BETWEEN 2023-09-10 AND 2023-09-12`)

But in this particular case, you can simply use the between method on the expression builder
await db
  .selectFrom('User')
  .selectAll()
  .where(eb => eb.between('createdAt', '2023-09-10', '2023-09-12'))


use addOrReplaceAction

Use addOrReplaceAction instead of just addAction to allow to create dynamic reports on build sites.

Testing done

Submitter checklist

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[ ] Ensure that the pull request title represents the desired changelog entry
[ ] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

Hello, @xjjx  @masterhard  I just update this plugin to version 1.5, but I find out this PR may cause an issue:
If we run multiple rtp actions in a pipeline, we expect all the rtp actions work, but in fact only the last rtp action works, all the previous rtp actions are replaced.
An example:
`#!/usr/bin/env groovy
pipeline {
agent any
stages {
stage('Publish') {
steps {
script {
String publishTarget1 = 'rtp-test1'
rtp nullAction: '1', parserName: 'HTML', stableText: "Artifact 1: http://artifactory/${publishTarget1} "
                String publishTarget2 = 'rtp-test2'
                rtp nullAction: '1', parserName: 'HTML', stableText: "Artifact 2: http://artifactory/${publishTarget2}

"
            }
        }
    }
}

}
`
What we expect:
Artifact 1: http://artifactory/rtp-test1 Artifact 2: http://artifactory/rtp-test2
But after this PR, the output become:
Artifact 2: http://artifactory/rtp-test2
Could you please check? Thank you.

I assume we need to propose a merge request that reverts the change and ask xjjx to introduce a separate command for the new function.

I would suggest that the right way to address this wouldn't be a new command/function, but could just be a boolean option to the 'rtp' pipeline step for 'replace: true' if you wanted the new behavior.
That would be a minimally invasive code change and easy to use.
For the generic step, that could be exposed as a configuration element on the step.


[cloud_firestore]: Query returning stale data

Describe the bug
One of my queries is returning stale data.
ordersCollection
          .where("userId", isEqualTo: userId)
          .orderBy("createdAt", descending: true)
          .snapshots()
          .map((list) => list.documents
              .map((doc) => OrderModel.fromFirestore(doc))
              .toList());

I cannot understand the issue.
I am using the latest version of the cloud_firestore.
 cloud_firestore: ^0.12.9+5
Only for the above collection, I am getting this error. Changing the collection query is removing the stale data and fetching the latest one.
Like I removed createdAt and got the data refreshed.

Have you tried passing Source.server to getDocuments? You can force the query to bypass the cache.
https://pub.dev/documentation/cloud_firestore/latest/cloud_firestore/Query/getDocuments.html

Hi @HathTech
does the proposed solution fix the issue?
Thank you

Hi @iapicca. Yes, it is working.
Thank you for the response.

Hi @HathTech
I'm glad that you fixed the issue,
thank you for letting me know


Document available settings for /etc/flatcar/update.conf file

Current situation
Values in /etc/flatcar/update.conf file like GROUP or SERVER are currently not well documented and easily accesible.
Ideal future situation
Flatcar documentation website should have a page dedicated for updates configuration.
Additional information
As far as I see, searching for GetConfValue in https://github.com/flatcar-linux/update_engine/blob/ace0de561ee30d9665d82167ad493043a035e4af/src/update_engine/omaha_request_params.cc allows to find available options.

opened https://github.com/kinvolk/flatcar-docs/pull/125


NOJIRA: Move help and support higher in the README

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines
[x] documentation is changed or added

Description of change

Arrangment is now:

Build statuses
About uPortal
Help and Support
Build Instructions

Continuous integration section has been removed.
Build status and environments is now described by the table at the top of
the page.
Help and support now links to the Manual section to give options for
which version of uPortal manual a person wants to see.

Coverage decreased (-0.02%) to 22.966% when pulling 25acee3159d8b611bc10095664d4728d8f69b871 on ChristianMurphy:NOJIRA-raise-help-and-support into 70f436be7b66d1cd87394f006735845c9e90a922 on Jasig:master.

LGTM :+1:


Keep role="dialog" after closing modal/offcanvas if already in the markup

Description
This PR is the result of a discussion that happened in https://github.com/orgs/twbs/discussions/39933.
TL;DR: if a role="dialog" is in the modal/offcanvas markup, our JavaScript will remove it when closing the element. The idea of this PR is to integrate a modification or our JavaScript behavior to keep this role if it is present in the markup.
There was a scenario to handle that, which was to put back the role="dialog" in the markup and doing nothing in the JavaScript by expecting users to correctly use it. But I like the enforcement rule that is present right as a modal/offcanvas can't be used without JavaScript right now anyway.
So I preferred the approach in this PR that doesn't change anything in the current behavior, but allows some flexibility for folks still wanting to add the role="dialog" in the markup for any reason.
Please note that the documentation is not modified as it's still accurate (source: https://getbootstrap.com/docs/5.3/components/modal/#accessibility):

Note that you don’t need to add role="dialog" since we already add it via JavaScript.

First, dear reviewers, what do you think of this approach, in terms of JavaScript and/or accessibility? As mentioned in the GH discussion, I deducted information in the history, but maybe it's wrong, and you have more history to share.
If we agree to go this way, is handling only role="dialog" this way enough, or do you think we also should do the same thing for aria-modal which follows the same logic?
While
Type of changes

[x] New feature (non-breaking change which adds functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
(N/A) My change introduces changes to the documentation
(N/A) I have updated the documentation accordingly
[x] I have added tests to cover my changes
[x] All new and existing tests passed

Live previews

https://deploy-preview-39941--twbs-bootstrap.netlify.app/docs/5.3/components/offcanvas/#live-demo
https://deploy-preview-39941--twbs-bootstrap.netlify.app/docs/5.3/components/modal/#live-demo

Related GH discussion

https://github.com/orgs/twbs/discussions/39933

while i don't think it's necessarily needed, i can see how the idea of "our code cleans up after itself" works here.
I would say it may actually be good/make sense for our documentation to say/show that you should ideally add role="dialog" directly in your markup (but that our JS error-corrects for this in case it isn't there)

I would say it may actually be good/make sense for our documentation to say/show that you should ideally add role="dialog" directly in your markup (but that our JS error-corrects for this in case it isn't there)

So it would mean:

Keeping my JS modification in this PR
Kind of reverting the modifications done in the HTML from https://github.com/twbs/bootstrap/pull/30936/files#diff-78bcedc866a59b217f5fb00fb270b86c4acc3bb0ff01a712cf0b8754715bee49 (+ other files) by re-adding everywhere role="dialog" for modals and offcanvases.
Slightly improving the doc to explain that there's a safety net in our JavaScript that will add the role by default.

TBH, I prefer this approach where the DOM is correct right away, and the JS tries to help when it can. I hadn't suggested this approach because https://github.com/twbs/bootstrap/pull/30936 explicitly did the opposite. But if you're OK, and the rest of the team too, I can modify this PR in this direction.

Oh, I see! OK then, I won't have time to do it right away, but I'll try to apply everything we said in this PR. So I let it in draft until I have time to do it later on. Thanks a lot for the early feedback, Patrick.

٧ تننSent from my Verizon, Samsung Galaxy smartphone
-------- الرسالة الأصلية --------من: "Patrick H. Lauke" @.> التاريخ: 6/5/2024  5:24 م  (GMT+03:00) إلى: twbs/bootstrap @.> نسخة: Subscribed @.***> الموضوع: Re: [twbs/bootstrap] Keep role="dialog" after closing modal/offcanvas if already in the markup (PR #39941)
I think the one problem we had with having the role="dialog" directly in the documentation was that, for modals that we want to show already open (like the "modal components" example one), that will cause issues. If we can somehow not have that there in the rendered version, that'd then work
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.>
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/twbs/bootstrap/pull/39941#issuecomment-2096135639",
"url": "https://github.com/twbs/bootstrap/pull/39941#issuecomment-2096135639",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
@.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


I have two sprite,i want  Control update a sprite

if i have two sprite,this two sprite display in page,but a sprite need Constant refresh，so,i want renderer.render(sprite),but the canvas.clearRect all canvas,so how to i canvas.clearRect a sprite.
Thank!

By the way, check the forum too
"How" questions are usually better aimed at the forum, in my opinion, as 694 people watch this project and get an email each time you create an issue, which is pretty frequent
http://www.html5gamedevs.com/forum/15-pixijs/