Can't connect to server (Win11)

Describe the bug
I'm trying to connect to my DigitalOcean server, and it does not work. Label "Connecting..." pops up, and then it's back to "Disconnected". Although this connection does work on my mobile phone. Sometimes, there is an error below: "we can't seem to connect to your server". I tried to run both client and installer as administrator.
To Reproduce
Fresh install, win11.
Expected behavior
It should connect :)
Screenshots

Client System (please complete the following information):

Outline Client Version: Win 1.7.1
Your Operating System: Win 11

Thank you for letting us know! We will share this issue with our product team to investigate further. If you have additional questions or would like to share more information about this issue, please contact us at support.getoutline.org.

No problems on my side, it's working perfectly on Windows 11 with Outline Windows Client 1.7.1 and Server 1.6.1
Edition	Windows 11 Pro
Version	21H2
OS build	22000.856
Experience	Windows Feature Experience Pack 1000.22000.856.0

Version 21H2
OS build 22000.856
Experience Windows Feature Experience Pack 1000.22000.856.0

Yeah, same version exactly, wonder why it does not work for me :(

Version 21H2
OS build 22000.856
Experience Windows Feature Experience Pack 1000.22000.856.0

Yeah, same version exactly, wonder why it does not work for me :(

It's working! bug fixed

Version 21H2
OS build 22000.856
Experience Windows Feature Experience Pack 1000.22000.856.0

Yeah, same version exactly, wonder why it does not work for me :(

It's working! bug fixed

What did you do to fix the problem

Version 21H2
OS build 22000.856
Experience Windows Feature Experience Pack 1000.22000.856.0

Yeah, same version exactly, wonder why it does not work for me :(

It's working! bug fixed

What did you do to fix the problem

Nothing...the program just started working again as before

I'm having the same issue: the Outline client on Windows simply refuses to connect:

We can't seem to connect to your server. Please check that you are connected to the internet and try again.

It disconnects immeditely after clicking Connect, but the error message appears with the delay.
There are a few other apps that stopped working, e. g. GeForce Experience.
Rebooting, reinstalling the client do not help.
Windows 10 Pro Version	10.0.19044 Build 19044
Outline client 1.7.1
Please help.

My issue seems to have been caused by Surfshark VPN: uninstalling Surfshark fixed Outline Client and GeForce Experience.

Hi
I had the same problem, Disabling the Hyper-V solved my problem.
You can disable Hyper-V using the Windows Features dialog:
1- Press Win + R to open Run.
2- Type control and click OK to open the Control Panel.
3- In the Control Panel, go to Programs > Programs and Features.
4- In the left pane, click on Turn Windows features on or off.
5- In the Windows Features dialog, deselect Hyper-V.
6- Click OK.
7- Once completed, click on Restart Now to restart, and run outline again.

I'm having the same issue again, any solutions?


chore: Fluent interface for queryAll method

🚨 DO NOT MERGE. ONLY REVIEW/APPROVE.
There is ~13 signatures of the queryAll method with parameters ranging from 2 to 7, different combinations of the same superset. This is extremely hard to grok and the resulting uses of queryAll aren't very readable either. This PR introduces a fluent interface for this method. If this works better for us, I'll look to move more such over-signature-ed methods to a fluent interface.
This sprang from a frustration in trying to understand this method's usages, to port to Postgres, and pulling my hair apart in the process.
This is an incomplete PR. I'll finish it, if we're aligned that this is a good idea, so I may have asked for a premature PR review. Thanks!
Here's an example of the fluent API compared to current API:

Summary by CodeRabbit

Refactor

Improved query building and execution process across various data access methods for enhanced performance and maintainability.

@sharat87 :  Aligned on the direction here.

Opening a new one.


Refactor to use sourcemaps for analysis

This is basically an Ember CLI addon providing a middleware that wraps the existing analyzer functionality of https://github.com/stefanpenner/broccoli-concat-analyser, which itself is coupled to the stats output functionality of broccoli-concat. This comes with some problems:

it currently does not work correctly with ember-auto-import (https://github.com/stefanpenner/broccoli-concat-analyser/issues/34)
any modern new build/packager pipeline (aka embroider) will (assumingly/most likely) not use broccoli-concat and thus make this cease to work at all!?

The only way forward I can think of is to make this work independently of the underlying bundler is by depending on sourcemaps only to analyze the bundle output. This could be implemented by making this basically a wrapper around https://github.com/danvk/source-map-explorer, eventually with a nicer (the current) frontend output.
Before I go down the rabbit hole here and invest some time, I would like to summon the experts in this field, namely @stefanpenner and @ef4, to share their thoughts, if time permits! 🙏😀

I think sourcemap approach makes sense, currently we do not have a "Fast, file only" sourcemap configuration for broccoli-concat, this results in either 1) slow high fidelity maps 2) no maps. Due to this, the original approach was taken.
That being said, It shouldn't be very hard to add "file only" sourcemaps to broccoli-concat. What i mean by "file only" is that, they do not care about the interior mappings of a file, merely the file boundaries when concat occurs.


FileNotFoundError with edit_video_stitching_tuning.py (Windows)

Hello, I have been trying to install on Windows using Anaconda. I think I managed to install all the requirements, and I tried to run a test of Old Jim, and the test returned this error:
 File "...\STIT\utils\models_utils.py", line 21, in load_tuned_G     with open(new_G_path, 'rb') as f: FileNotFoundError: [Errno 2] No such file or directory: './checkpoints/model_jim.pt'
Can you help?

Hi,
Did you first run the inversion step as detailed here?: https://github.com/rotemtzaban/STIT#inversion
This is the step that creates the fine tuned generator, which we use to make the edits

Hey, yeah I hadn't done that part, I'm sorry. I decided to try again before answering you but I found another problem, here's the error:
Traceback (most recent call last):
  File "C:\Users\shese\Documents\DL\STIT\torch_utils\ops\upfirdn2d.py", line 32, in _init
    _plugin = custom_ops.get_plugin('upfirdn2d_plugin', sources=sources, extra_cuda_cflags=['--use_fast_math'])
  File "C:\Users\shese\Documents\DL\STIT\torch_utils\custom_ops.py", line 64, in get_plugin
    raise RuntimeError(f'Could not find MSVC/GCC/CLANG installation on this computer. Check _find_compiler_bindir() in "{__file__}".')
RuntimeError: Could not find MSVC/GCC/CLANG installation on this computer. Check _find_compiler_bindir() in "C:\Users\shese\Documents\DL\STIT\torch_utils\custom_ops.py".

  warnings.warn('Failed to build CUDA kernels for upfirdn2d. Falling back to slow reference implementation. Details:\n\n' + traceback.format_exc())
Setting up PyTorch plugin "upfirdn2d_plugin"... Failed

I've looked for solutions on other githubs, but everything I've tried still doesn't work.  I decided to send you here even though it could be another small thing I missed. (if you prefer I can open another #issue)
thank you in advance

Hey, yeah I hadn't done that part, I'm sorry. I decided to try again before answering you but I found another problem, here's the error:
Traceback (most recent call last):
  File "C:\...\DL\STIT\torch_utils\ops\upfirdn2d.py", line 32, in _init
    _plugin = custom_ops.get_plugin('upfirdn2d_plugin', sources=sources, extra_cuda_cflags=['--use_fast_math'])
  File "C:\...\DL\STIT\torch_utils\custom_ops.py", line 64, in get_plugin
    raise RuntimeError(f'Could not find MSVC/GCC/CLANG installation on this computer. Check _find_compiler_bindir() in "{__file__}".')
RuntimeError: Could not find MSVC/GCC/CLANG installation on this computer. Check _find_compiler_bindir() in "C:\...\DL\STIT\torch_utils\custom_ops.py".

  warnings.warn('Failed to build CUDA kernels for upfirdn2d. Falling back to slow reference implementation. Details:\n\n' + traceback.format_exc())
Setting up PyTorch plugin "upfirdn2d_plugin"... Failed

I've looked for solutions on other githubs, but everything I've tried still doesn't work. I decided to send you here even though it could be another small thing I missed. (if you prefer I can open another #issue)
thank you in advance

@sheseagle
Hi, I believe from the error message the issue is that you don't have the compiler required to run Stylegan installed.
On windows, the compilation requires Visual Studio.
See here: https://github.com/NVlabs/stylegan2-ada-pytorch#requirements
You might want to look here as well: https://github.com/rotemtzaban/STIT/issues/11, as they faced similar issues with running on windows.


Lack of LoadGlobal Opcode despite documentation

Hi,
I've noticed that the FuzzIL LoadGlobal opcode is referenced in various places including the readme. But when I look into the opcodes definition it doesn't seem to be there. I was wondering if it has been superseded by LoadBuiltin. If so should I should update the documentation?
Happy Holidays,

Thanks for filing this! We're currently redesigning this and also potentially dropping LoadBuiltin soon: https://github.com/googleprojectzero/fuzzilli/pull/486. Probably best to wait with updating the documentation until after that is completed :)

Sounds good!


RIDER-18116: Open at top level when completing out of scope items

Adds a setting to add 'open' at the top level of the file.  This also sets the default to match with Visual Studio's new default (https://github.com/Microsoft/visualfsharp/pull/5738)
In action:

@saul I’m very glad to see you here :)

I was just thinking the same thing 😆

@saul Thank you for this fix!

Thanks both - now I just need to figure out what to work on next!


Do not create AttributeValues when values are not provided

Do not create AttributeValue objects when values for attributes are not provided.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-6352 Not required date attribute saved as null cause an error


First PE surgical link

The scenario here is slightly simplified: we compile the host zig code with our dummy dll, but don't do the host pre-processing (which would add space for extra sections, among other things). Furthermore, the app assembly code is hardcoded at the moment, and appended to an existing .text section.
But I think this represents a huge improvement in our understanding: we now know how to remove references to the dummy dll, and fix up the calls to app functions.

Well done @folkertdev !


Support Viewing Sub-Workflows in Top level Workflows

Summary
Our use case in Argo depends a lot on using the Workflow of Workflows model. With this however, we are only able to see that a sub-workflow was spawned and some logs that it ran successfully. If we want to see the steps within that sub-workflow we have to back out of the top level workflow and dive into the spawned workflow.
It would be great to be able to see the full output of those sub-workflows within the top level workflow to get a better overall picture of our pipeline

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

I don't think we should show the fully embedded workflow in the workflow-of-workflows pattern, but what we can/should do is link to the other workflow when we detect that the resource kind is a Workflow.

@DP19 would you like to submit a PR for the above? Would be a UI only change

Yeah, I can give this a shot. Any ideas on what would need to be changed exactly. Not familiar with the code base yet.

Try this help: https://argoproj.github.io/argo/CONTRIBUTING/

Thanks @alexec. Someone else can take this over. I just took a quick look and i'm not well versed in node. But from what i can tell just by following the workflow of workflow guide as an example, then using the apiDocs to get info about the spawned workflow, there doesn't seem to be any reference to the sub workflow that gets launched so I'm not positive this is just a UI change

Closing as duplicate of #6922 as that one has more up votes (though of course this one came first)


Experiment details?

For benchmarks sake, how long did the models in the paper take to train and on what type/how many GPUs were used?

Hi Abhishek, I am currently trying to replicate the experiment of this paper. Were you able to run this code successfully? I'm still stuck on running the training and I would appreciate your response or is there any other place we can discuss?


Initial state doesn't work in Rails 4.2

Hi, I have problem with initial state in new Rails 4.2
class User < ActiveRecord::Base
  state_machine initial: :waiting_confirmation do
    state :waiting_confirmation
    state :active
  end
end

Loading development environment (Rails 4.2.0)
[1] pry(main)> User.new.state
=> nil

Any ideas?

confirmed this issue.

If the gem is not maintained anymore, maybe someone wants to maintain its fork?

@Mehonoshin https://github.com/pluginaweek/state_machine/issues/310

@SaimonL +1
Exactly the same problem. Find a fix?

@pluginaweek any news on this? Thanks.

Guys, @seuros maintains a fork of this which does not exhibit this issue when used with Rails 4.2. See discussion here: https://github.com/pluginaweek/state_machine/issues/310

The solution is you have to set default state in the database level.
so the migration file will look like this:
t.string :status, default: 'start'

Having the state nil will cause error. Don't know about the updated versions.

This worked for me in development, but not in production on Heroku.

Guys, just use state_machines-activerecord.

I use https://github.com/seuros/state_machine with Rails 4.2
everything work now

@kalashnikovisme https://github.com/state-machines/state_machines-activerecord

1

+1

:+1:

@mkonikowski @shlima @khaleksa
This repo is not supported. Development moved to:
https://github.com/state-machines/state_machines-activerecord

@styx I've discovered it already, but forgot to comment here... Maybe in the Readme you could add info that this repo is not maintained anymore and put a link to state_machines-activerecord as the most recent one?

@mkonikowski  Nobody has access to this repo anymore. That why we have the other one :)

@seuros - thanks, I am now using state_machines-activerecord

+1

MR with fix https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/1764


Sultant Token update info

Now, sultan token still airdrop compotetition, for ico will be open at  04 December 2018, and will be listed after ico end.

Incorrect information submitted, please go through our guide and check again.


Switch IPython kernel and IPython console tabs.

From<EMAIL_ADDRESS>on 2014-11-17T15:55:23Z
It would be much more convenient to have IPython consoles in the same tab as regular consoles, command windows, etc, and to have the kernels in some separate tab.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2052

From ccordoba12 on 2014-11-18T14:07:01Z
Unfortunately this is not possible. The best we can do is hide IPython kernels by default.
Status: Duplicate
Mergedinto: 1860


Empty changelog for 0.11.2

As the title says, why make a new release of there are no changes? That seems odd to say the least.

There were little to no user facing changes but i felt i still wanted the commits released.


Data upload workflow

The metadata and data validation process is composed by two steps that mainly happen from the study summary page.

Upload of the templates (keep a copy in the filesystem).
Add the templates to the database (if this is done you can proceed to A, see below).
Upload and validate sequences (if this is done you can proceed to B, see below).

(A) From the study summary page link to a metadata stats page

Merge the templates and create a "QIIME mapping file".
Generate a summary of this newly created object.
Render the web interface that contains this information.

(B) From the study summary page link to a "start quick visualizations" page
Create a job that takes care of this and once the processing is finished add a link that takes you to the results.

Subsample the dataset to at maximum 1000 sequences per sample.
Create a temporary dataset (includes OTU table and a QIIME mapping file), where are we going to store this?.
Present a results page that plots beta diversity (unweighted and weighted UniFrac) and taxa summaries (this could take a really long time).
Offer option to delete this temporary dataset from the system.

@teravest, @wasade and myself will be working on different parts of this issue, however input and discussion at this point will be very useful.

This issue is now outdated.


[2.1] Finally remove deprecated stuff

Roadmap Wiki section: https://github.com/yiisoft/yii2/wiki/Roadmap#cleanup – (BTW: will be good to link it with this issue).
For each code marked as @deprecated need to do:

rewrite dependencies
remove documentation occurrences
remove code

Аlready done:

800574871419b99442d8be73a51e7f8e9e0d090f
4e15d3375633ae92eb0e91fbb0f6050de61b5d5c

Linked to this issue from wiki.

All deprecations removed (last PR #15963 is waiting for the @SilverFire review). Some things can reappear after merges (2.0.x >> 2.1.x). That's why I'll wait for other 2.1 commits (and merges), then will search deprecated things again.
Don't close this task.

Merged #15963


MULE-17104: Create WebSockets documentation.

Replaced by https://github.com/mulesoft/docs-connectors/pull/464


Deletion of parent

When deleting files, the sheetStore parent is deleted as well, which causes files to be put into the trash with it. Either move it out of trash upon the creation of new files or don't delete the folder in the first place.

Cannot reproduce, not sure why it happened the 1st time, perhaps I deleted it? Oh well, I'll re-open if it ever occurs again


bug: katana not returning correct value for blockhash

https://github.com/kkrt-labs/kakarot/commit/01a7c41c7622f7d3febddf439068332d263ba69f
We can't test this properly because katana returns 0 instead of returning a correct value

Hi Sir ,
I am proficient Blockchain developer expert in Cairo , Rust and Solidity and also in web development.
I have contributed many cairo , rust projects like chainevents , arkprojects , sunshine etc .
Can you Please /assign this issue me.
Thank You


feat(activity log): add reviews to activity log

Add log entry to Recent Activity tab in Listing Management.
Add functionality for the 'view' link on review edited and review
created to forward to the reviews tab in a listing modal.
AMLNG-786
Description
As an Admin, I would like to see new listing reviews appear in ListingMngmt>Recent Activity to facilitate Admin notification of posted comments.
Acceptance Criteria
• when a user submits review a summary will appear in ListingMngmt>Recent Activity
• the summary will include a link to the review tab of the reviewed listing
• similar to when a review is deleted
How to test code
Test functionality by pulling https://github.com/aml-development/ozp-backend/tree/New_Action_log_addition
After creating a review, there will be an entry in /dist/#/user-management/recent-activity
The view button for the log entry should take the user to the review tab.
An edited log entry should do the same.

Test above passes.  New Reviews and Edited Reviews cause an entry in the Recent Activity list
👍

pulled branch
reviewed code
tested

After creating a review, there will be an entry in /dist/#/user-management/recent-activity :+1:
The view button for the log entry should take the user to the review tab :+1:
An edited log entry should do the same :+1:
An edited log entry will have "edited review for" instead of "reviewed" or other :+1:

:+1:


BDKD-450 Added get-file-list subcommand and python wrapper

One minor suggestion, otherwise looks good.

@sirca/back-up Suggestion implemented.

Looks good, merging


Unmanaged Solution

Great project. Are there any plans to release the unmanaged solution for this alongside the managed?

We may consider releasing the un-managed solution at a future date.

This will be release with the v1.2.0 solution set 👍


PowerShell installer: use manifest to select files to download.

Instead of using the hard-coded PLATFORM_INFO, this:

Downloads the dist-manifest.json file.
Selects an "executable-zip" artifact based on the current system's architecture, falling back to X64.
From that artifact, selects all assets of type "executable" for installation.

This does not implement actually building something other than X64.
Tested in PowerShell 5.1 and PowerShell Core 7.3.2 with:
.\installer.ps1 -app_name cargo-dist -artifact_download_url https://github.com/axodotdev/cargo-dist/releases/download/v0.0.3-prerelease12 -app_version 0.0.3-prerelease12

There is some extra logging (the Write-Verbose calls) that only shows up when the script is invoked with the -Verbose flag.
Related issue: #85

@Gankra What do you think of using the dist-manfiest.json to select which files to download and install?
With regards to supporting archives other than zip (#17), the script stops executing after download if it encounters something other than a .zip file. The download path is printed, so the user can find the downloaded file easily.
I'm leaving this as draft until I remove the part in install.rs that generates the hard-coded asset list.

Hey! Sorry for the delay, was focusing on the last bits of cutting 0.0.3.

What do you think of using the dist-manfiest.json to select which files to download and install?

I am... mixed on it. In principle it's a good idea, but also in principle it's unnecessary and pushing complexity from the extremely maintainable/safe Rust code to the more hairy/dangerous shell scripts. Do you have a usecase in mind that makes it important/useful to do this kind of late-bound analysis?

Do you have a usecase in mind that makes it important/useful to do this kind of late-bound analysis?

Not really. There would certainly be fewer things that could go wrong if the list of available artifacts and assets is hard-coded into the script.
Do you still think it is a good idea to have the script detect the OS architecture? I can roll-back my changes to use dist-manifest.json and instead include the architecture in the platform info injected by cargo-dist.

yeah #85 would be great still! Sorry I didn't realize you had actually impl'd the target detection stuff, I'll review that part now!

Out of morbid curiousity I checked out what powershell on macos does (yeah it's a thing) and then hacked up a version that should work on all platforms:
function Get-TargetTriple() {
  try {
    Write-Verbose "test"
    # NOTE: this might return X64 on ARM64 Windows, which is OK since emulation is available.
    # It works correctly starting in PowerShell Core 7.3 and Windows PowerShell in Win 11 22H2.
    # Ideally this would just be
    #   [System.Runtime.InteropServices.RuntimeInformation]::OSArchitecture
    # but that gets a type from the wrong assembly on Windows PowerShell (i.e. not Core)

    # Possible OSPlatform Values: https://learn.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.osplatform?source=recommendations&view=net-7.0
    # Possible OSArchitecture Values: https://learn.microsoft.com/dotnet/api/system.runtime.interopservices.architecture
    # Rust supported platforms: https://doc.rust-lang.org/stable/rustc/platform-support.html

    $a = [System.Reflection.Assembly]::LoadWithPartialName("System.Runtime.InteropServices.RuntimeInformation")
    $t = $a.GetType("System.Runtime.InteropServices.RuntimeInformation")
    $raw_arch = $t.GetProperty("OSArchitecture")
    $arch = $null
    switch ($raw_arch.GetValue($null).ToString())
    {
      "X86" { $arch = "i686" }
      "X64" { $arch = "x86_64" }
      "Arm" { $arch = "thumbv7a" }
      "Arm64" { $arch = "aarch64" }
    }
    Write-Verbose "arch is $arch"

    $windows_os = [System.Runtime.InteropServices.OSPlatform]::Create("WINDOWS")
    $mac_os = [System.Runtime.InteropServices.OSPlatform]::Create("OSX")
    $linux_os = [System.Runtime.InteropServices.OSPlatform]::Create("FREEBSD")
    $freebsd_os = [System.Runtime.InteropServices.OSPlatform]::Create("LINUX")
    $os = $null
    if ([System.Runtime.InteropServices.RuntimeInformation]::IsOSPlatform($windows_os)) {
      $os = "pc-windows-msvc"
    } elseif ([System.Runtime.InteropServices.RuntimeInformation]::IsOSPlatform($mac_os)) {
      $os = "apple-darwin"
    } elseif ([System.Runtime.InteropServices.RuntimeInformation]::IsOSPlatform($linux_os)) {
      $os = "unknown-linux-gnu"
    } elseif ([System.Runtime.InteropServices.RuntimeInformation]::IsOSPlatform($freebsd_os)) {
      $os = "unknown-freebsd"
    }
    Write-Verbose "os is $os"

    if ($os && $arch) {
      return "$arch-$os"
    } else {
      Write-Verbose "failed to get os and arch"
    }
  } catch {
    # The above was added in .NET 4.7.1, so Windows PowerShell in versions of Windows
    # prior to Windows 10 v1709 may not have this API.
    Write-Verbose "Get-TargetTriple: Exception when trying to determine OS architecture."
    Write-Verbose $_
  }

  # This is available in .NET 4.0. We already checked for PS 5, which requires .NET 4.5.
   Do you think we should add the same kind of installer fallback that was added in #165?

Out of morbid curiousity I checked out what powershell on macos does (yeah it's a thing) and then hacked up a version that should work on all platforms:

It is a fair question whether or not the PowerShell script should support non-Windows platforms, given that it can run on several platforms now. Espeially since it appears you could set PowerShell as your logon shell on Unix-like systems!
One argument against that is you would have to implement all the logic to support Unix-like systems twice: once in the shell script and once in the PowerShell script. To avoid that maintenance burden, the PowerShell script could detect when it is being run on non-Windows:
if ([System.Environment]::OSVersion.Platform -ne [System.PlatformID]::Win32NT) {
    throw "This script is only supported on Windows. Please run this instead:\n curl --proto '=https' --tlsv1.2 -LsSf https://github.com/{{REPO}}/releases/download/{{VERSION}}/{{CRATE}}-{{VERSION}-installer.sh | sh";
}

cargo-dist could fill in all the right values to make that just work. It could even run the curl | sh pipeline behind the scenes, but that might be excessively clever.

 Do you think we should add the same kind of installer fallback that was added in #165?

After fiddling with my Windows Dev Kit 2023 ARM64 I have come to a similar conclusion for Windows. It makes sense to try to download platform-specific binaries if they are available, but otherwise fallback to X64. That is the WIP state of this PR and I have updated #85 to reflect that this simple approach should be good enough.

This is now much-simplified from the original PR and now ready for more review.

taking today off, will review on thursday, but i wanted to leave you some
loose notes on installer stuff:

powershell installers will need to grow support for most of the linux-y
functionality anyway once we make zip style configurable. this doesn't need
to happen in your PR, i'm just keeping an eye out for the future. also i am
told that windows 10 now ships with tar out of the box which makes that
simple, although i need to look into how new that is.

i'm going to refactor the shell/powershell code on the rust side to have
them share more code. this can happen before or after your pr, whichever
you prefer. i intentionally kept them separate in case they needed to
wildly diverge but i'm now seeing they are only converging more. this work
will also power future feature work on npm-based installers.

i'm going to add some more general logic for "fallback" platforms so it's
easy for us to plug in more compatibility cases like x64 on arm64
(mac/windows), or x86 on x64 (windows only at this point..?)

On Wed, Mar 1, 2023 at 3:01 AM Austin Wise @.***> wrote:

This is now much-simplified from the original PR and now ready for more
review.
—
Reply to this email directly, view it on GitHub
https://github.com/axodotdev/cargo-dist/pull/168#issuecomment-1449515595,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIVRYEDNNNG4OYG7LUOXLTWZ364DANCNFSM6AAAAAAVIUOPP4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks so much! I'll get started on the installer refactor now so these things are fed more info.

Thanks for merging. I really like the direction your are taking the install script by embedding the data about assets into them. This totally sidesteps of the thorny issue of having to parse JSON in dist-manifest.json in a cross-platform way.


Carthage support

Carthage support is missing

I will add Carthage later this week. 👍
If you want it sooner you can always create a PR 😉

Carthage support is added.


Remove unnecessary references to System.Security.Cryptography.ProtectedData

closes #45217

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Identity


[Bug]: Remote I/O Error

Requirements

[X] I have updated RPI_I2C_OLED to the latest available version
[X] I did a search to see if there is a similar issue.

Current Behavior
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[13:58:51] INFO: Starting I2C OLED App...
/dev/i2c-1
[13:58:51] INFO: /dev/i2c-1 enabled
[13:58:51] INFO: I2C access enabled. Proceeding!
[13:58:51] INFO: Display Info to OLED
[13:58:51] INFO: Running 'python3 display.py  -c /data/options.json'
Traceback (most recent call last):
File "/I2C_OLED/display.py", line 5, in
from bin.Config import Config
File "/I2C_OLED/bin/Config.py", line 5, in
from bin.Screens import *
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/I2C_OLED/bin/Screens.py", line 53, in
class BaseScreen:
File "/I2C_OLED/bin/Screens.py", line 58, in BaseScreen
def init(self, duration, display = Display(), utils = Utils(), config = None):
^^^^^^^^^
File "/I2C_OLED/bin/Screens.py", line 17, in init
self.clear()
File "/I2C_OLED/bin/Screens.py", line 27, in clear
self.display.begin()
File "/I2C_OLED/bin/SSD1306.py", line 97, in begin
self._initialize()
File "/I2C_OLED/bin/SSD1306.py", line 154, in _initialize
self.command(SSD1306_DISPLAYOFF)                    # 0xAE
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/I2C_OLED/bin/SSD1306.py", line 89, in command
self._bus.write_byte_data(self._address, control, value)
OSError: [Errno 121] Remote I/O error
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
Expected Behavior
No response
Steps To Reproduce
No response
Context
YAML state

Environment
- Browser: Firefox
- HA Version:11.03
- I2C_OLED: JMDO 96 c

Anything else?
No response

Could be something I am doing wrong but unsure


Support react 19

What is the problem this feature would solve?
Support react 19
External documents/projects?
No response
What is the feature you are proposing to solve the problem?
No response
What alternatives have you considered?
No response

https://github.com/pmndrs/react-three-fiber/blob/v9/packages/fiber/src/core/reconciler.tsx
https://github.com/facebook/react/blob/main/packages/react-art/src/ReactFiberConfigART.js#L352
https://github.com/vadimdemedes/ink/issues/688

@lu-perfect Normally you could use whatever version of React in your project that is using Kubb to generate the files. Could you maybe explain more about what you want to see from this upgrade?

@lu-perfect I had a try with the latest Kubb version(3.3.0, react-query and React 19), seems to work fine here. See https://www.kubb.dev/examples/tanstack-query/react-query

@lu-perfect I had a try with the latest Kubb version(3.3.0, react-query and React 19), seems to work fine here. See https://www.kubb.dev/examples/tanstack-query/react-query

I get validation error when its running the 2/5 | plugin-oas: buildStart
ERROR  Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:

You might have mismatching versions of React and the renderer (such as React DOM)
You might be breaking the Rules of Hooks
You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem. (repeated 2361 times)

@Rikard-Johansson97 Could you provide me an example project or your package.json/kubb.config.ts?

I am also getting an error:
Cannot read properties of undefined (reading 'ReactCurrentOwner')

    at $$$reconciler (node_modules/react-reconciler/cjs/react-reconciler.development.js:491:46)
    at node_modules/@kubb/react/src/kubbRenderer.ts:75:3
    at import (node_modules/jiti/dist/jiti.cjs:1:199710)
    at node_modules/@kubb/plugin-oas/dist/chunk-BAU7PO7T.js:1:195
    at import (node_modules/jiti/dist/jiti.cjs:1:199710)
    at node_modules/@kubb/plugin-oas/dist/chunk-WBHFV7C2.js:1:256
    at import (node_modules/jiti/dist/jiti.cjs:1:199710)
    at node_modules/@kubb/plugin-oas/dist/index.js:2:21
    at import (node_modules/jiti/dist/jiti.cjs:1:199710)
    at kubb.config.ts:2:18
    at Function.import (node_modules/jiti/dist/jiti.cjs:1:199710)
    at tsLoader (node_modules/@kubb/cli/src/utils/getCosmiConfig.ts:21:15)
    at Explorer.#loadConfiguration (node_modules/cosmiconfig/src/Explorer.ts:160:30)
    at Explorer.#loadConfigFileWithImports (node_modules/cosmiconfig/src/Explorer.ts:114:27)
    at Explorer.#readConfiguration (node_modules/cosmiconfig/src/Explorer.ts:105:7)
    at search (node_modules/cosmiconfig/src/Explorer.ts:61:28)
    at Explorer.search (node_modules/cosmiconfig/src/Explorer.ts:95:12)
    at getCosmiConfig (node_modules/@kubb/cli/src/utils/getCosmiConfig.ts:60:57)
    at Object.run (node_modules/@kubb/cli/src/commands/generate.ts:81:20)
    at runCommand (node_modules/citty/dist/index.mjs:316:16)
    at runCommand (node_modules/citty/dist/index.mjs:307:11)
    at runMain (node_modules/citty/dist/index.mjs:445:7)
    at run (node_modules/@kubb/cli/src/index.ts:49:3)

Relates to this line in react-reconciler:
var ReactSharedInternals = React.__SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED;

This has been renamed in React 19. Can be fixed like this: https://github.com/microsoft/use-disposable/pull/32/files#diff-5971f63da29997ff64996c0f14497c4756ed24cf15d181141ea6a8f9c8d7a376R6, in react-reconciler

Seems to have been fixed in latest version of react-reconciler. So @kubb/react should probably update their version

I have the same issue


<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

I'm getting below after upgrade of node-sass to ^4.0.
<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

I'm facing the same issue.
I was able to get around it by installing version 3.4.2 of node-sass, like so:
npm install<EMAIL_ADDRESS>--save-dev

Yep.
I have all current latest in my package,json:
    "gulp-sass": "^3.0.0",
    "node-sass": "^4.0.0",
    "sass-loader": "^4.0.2"

Using Yarn I got warning Incorrect peer dependency<EMAIL_ADDRESS>

same problem

Moreover it fails on mac if node-sass 4.0.0 is installed in project by itself
and i've got glorious
Fatal error: undefined is not a function
from webpack
please add node-sass as a dependency

Related PR: https://github.com/jtangelder/sass-loader/pull/319

"Fixed" since node-sass 4 was no valid peer dependency.


'snippets' is a nil value when calling get_docstring

I'm getting the following error when running :Telescope luasnip. I've got LuaSnip installed and configured properly.

Hi @zeitchef ! Thanks for the heads-up -- and yes -- this just bit me too.
I'll roll a fix, and then figure out how to implement a regression test.. LuaSnip keeps breaking things.

This came up in LuaSnip's "Breaking Changes" tracking issue.
https://github.com/L3MON4D3/LuaSnip/issues/81#issuecomment-1068545111
I saw this, but didn't have the presence of mind to re-test at the moment it happened. I'll know better for next time. Lesson learned!

@zeitchef I've opened benfowler/telescope-luasnip.nvim#4 if you'd like to confirm it works for you too

@benfowler Thanks got the quick response. Works as expected!

seems that the new API is luasnip.available() ? Dam, the amount of breaking changes of this project is frustrating

It's not great. I also see issues with nvim-cmp, where stuff just breaks
with virtually zero notice. The latest one was where they decided to just
remove all the default keybindings with no notice, and then broke
tab-completion in command mode. I don't want to look a gift-horse in the
mouth though, but it isn't fun when you've got a day job and deadlines to
hit.
It looks like some projects are coming up with some sensible general rules
on when to break backwards compatibility and how to advertise them; like
having a pinned 'Breaking Changes' issue on each project, and only
introducing major breaking changes on new versions of Neovim, as
lsp-config just did today with the release of 0.7. This is all open
source, so people will just do what they want at the end of the day...
I think the best I can do at least with this piece of code, is to try and
find some time to write a regression test. The idea I had was to borrow
what some other Telescope extensions do, and write a test case to start
their plugins in Neovim configured with a minimum reproduction, and then
test basic functionality. Then set up a GitHub Action to run this nightly.
On Fri, 15 Apr 2022 at 01:53, Daniel Rodríguez Rivero <
@.***> wrote:

seems that the new API is luasnip.available() ? Dam, the amount of
breaking changes of this project is frustrating
—
Reply to this email directly, view it on GitHub
https://github.com/benfowler/telescope-luasnip.nvim/issues/3#issuecomment-1099750025,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMP7LK7ZAVRJ7CE5MYKYB3VFC4XRANCNFSM5SIYBTCA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I think that for all os us that use packer we should start pinning commit hashes just like we do with package-lock in other languages and then only upgrade to the latest during weekends with enough time to chase bugs.

I just checked Packer's readme, and it makes a mention of snapshot functionality, which if I'm not mistaken, can be made to fit the bill. I'm going to see what prior art is already out there, and then give this a go -- good suggestion, @danielo515 (y)


rustc support?

Hello,
I'm wondering if I can get stabilizer to work with cargo / rustc?
If you're not familiar, rustc uses LLVM as a backend.
Looks like a very useful tool.
Thank you.

+1. I'm looking to benchmark some rust code, and would benefit from stabilization.

Hey, me too! Any updates on this?

+1

Haven't had a chance to try this yet, but this may work: https://docs.rs/coz/0.1.3/coz/.
Closing.

Interested too, well coz isn't stabilizer, it doesn't measure variance from what I know, any movement/still interested?


parser.formatter_class use is inconsistent (or just undocumented?)

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Using CliSettingsSource(Model, root_parser=parser), as documented, works for the main model description, but it (weirdly) doesn't apply to subcommands, unless the (undocumented) formatter_class=parser.formatter_class is also set.
The whole syntax seems overly convoluted, why not make formatter_class just part of SettingsConfigDict?
Thanks for the great work otherwise.
Example Code
#!/usr/bin/env python
import argparse
from pydantic import BaseModel
from pydantic_settings import BaseSettings, CliSubCommand, CliSettingsSource

class SubCmd(BaseModel):
    """
    SubCommand docs
    With
    Multiple
    Lines
    """
    pass

class Model(BaseSettings):
    """
    Model docs
    With
    Multiple
    Lines
    """
    cmd: CliSubCommand[SubCmd]
    a : int = 1
    b : str = 'foo'

if __name__ == '__main__':
    parser = argparse.ArgumentParser(description=Model.__doc__)
    parser.formatter_class = argparse.RawDescriptionHelpFormatter

    # # works for Model, but not for SubCmd
    # cli_settings = CliSettingsSource(Model, root_parser=parser)

    # # works for SubCmd, but not for Model
    # cli_settings = CliSettingsSource(Model, formatter_class=parser.formatter_class)

    # works for both
    cli_settings = CliSettingsSource(Model, root_parser=parser, formatter_class=parser.formatter_class)

    print(Model(_cli_settings_source=cli_settings(args=True)).model_dump())

Python, Pydantic & OS Version
pydantic version: 2.8.2
        pydantic-core version: 2.20.1
          pydantic-core build: profile=release pgo=true
                 install path: .../.venv/lib/python3.10/site-packages/pydantic
               python version: 3.10.12 (main, Jul 29 2024, 16:56:48) [GCC 11.4.0]
                     platform: Linux-<IP_ADDRESS>-microsoft-standard-WSL2-x86_64-with-glibc2.35
             related packages: mypy-1.11.1 typing_extensions-4.12.2 pydantic-settings-2.4.0
                       commit: unknown

@hramezani, could you please take a look at this when you return? Thanks!!


Update Senate committee membership (House committee data remains unav…

…ailable)

The diff appears very large here but if you run git show --minimal it's actually not that many changes.


alexanderism55: Behavior, Strategy, Implementation, 3 weeks

my fork "The directory is called bonus-doc-nurse"

Learning Objectives

Priorities: 🥚, 🐣, 🐥, 🐔 (click to learn more)

There is a lot to learn in this repository. If you can't master all the material
at once, that's expected! Anything you don't master now will always be waiting
for you to review when you need it. These 4 emoji's will help you prioritize
your study time and to measure your progress:

🥚: Understanding this material is required, it covers the base skills you'll
need to move on. You do not need to finish all of them but should feel
comfortable that you could with enough time.
🐣: You have started all of these exercises and feel you could complete them
all if you just had more time. It may not be easy for you but with effort you
can make it through.
🐥: You have studied the examples and started some exercises if you had time.
You should have a big-picture understanding of these concepts/skills, but may
not be confident completing the exercises.
🐔: These concepts or skills are not necessary but are related to this module.
If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push
yourself without getting distracted from the module's main objectives.

1. Remix
Practice studying and remixing other people's solutions to coding challenges. Create your own solutions by mixing and matching pieces from other people's code.

🐣 Reconstructing: You can reconstruct a variety of solutions to the same challenge when they are presented as parsons problems.
🐣 Analyzing: You can analyze a function written at your level. This includes:

[x] Behavior: Write documentation, test cases and use cases to describe the function's behavior.
[x] Strategy: Describe the function's strategy using plain english.
[x] Implementation: List the language features in a function and explain how each one is used.
[x] Small Changes: You can think of 2+ changes to the function's implementation that would not change it's strategy.

🐣 Remixing You can analyze several solutions to the same challenge then ...

[x] Write: Your own solution by remixing the ones you studied.
[x] Explain: How the other solutions inspired yours; what ideas did you take from them? what ideas did you not take?
[x] Analyze: Complete a write-up your own solution as though someone else wrote it.

2. Write

🐣 Function Design:

[x] Writing Tests: Given a working function, you can write passing test cases to describe it's behavior.
[ ] Writing Functions: You can design multiple solutions to the same code challenge, keeping notes about different experiments you tried along the way.

[ ] 🐣 Generating Documentation: You can write a JSDoc comment for your solutions and run a script to generate markdown documentation.
[ ] 🐣 Fuzz Testing: You write solutions that pass randomly generated test cases.
🐣 Test Driven Development: You can solve open-ended, ambiguous coding challenges at your level:

[x] Reading Docs: You can understand what the function is supposed to do by reading it's JSDoc description.
[x] Writing Tests: You can write test cases before there is a function to test.
[x] Writing Functions: You can write one function that passes the test cases you have prepared (even if it's just 1 test case!).
[x] Refactoring: You can improve your function's implementation without failing any test cases that were passing.
[x] Iterative Development: You can repeat the TDD process until you are satisfied with your test cases and solution.

[ ] 🐔 Code Golf: Write your solutions with the fewest characters possible! This won't help you write readable code, but it will make you think deeply about JS, your strategy and implementation.

3. Review

🐣 Continuous Integration: You can check your code's quality before pushing so your CI checks all pass.

[ ] Formatting
[ ] Linting
[ ] Testing

[ ] 🐣 Code Review: You can use a checklist to give a thorough, positive and constructive review of your classmates' solutions.
[ ] 🐔 Code Coverage: You can explain what code coverage is, why it's important, and can write unit tests with 100% code coverage.

Week 1
I Need Help With:

sharpening my testing skills. I use test instead of description, and i dont use an it statement. However i use equal and expected.

What went well?
Understanding Jest was quite easy. The entire idea of testing was far more easier than what my fears can justify. In fact testing helped me write my function better, or shall i say it helped me think how to write better function.
What went less well?
I do not know why but I couldn't get the 'description', and the 'it' function rolling. Also i coudnt export my function using 'module.exports = code ' and import using 'code = require './location'. When I did that, it said that require was not defined. So it gave me an option to press change to "enp or ens" i m not sure but when i pressed it it transforms it self to 'import code from location'.
Lessons Learned

I learned that testing can help you be a more professional coder. What i mean by that is that if I am going to build a good program; the way I handle the project will matter ten times more than how good I can write a function. So in a way, I understand what you guys said at the beginning of HYF, we wont just teach u how to code, but how to be a good team member. I also learned to write functions better. I mean I wrote a function to turn hours and minutes to seconds, in about ten minutes. Two weeks ago I did not even know how to console.log properly.

Sunday Prep Work

I will try a challenge a from the "edbit" website and write test for it.

I use test instead of description, and i dont use an it statement. However i use equal and expected.

I hope this has become more clear yesterday..but all tests are supposed to follow the logic of describe>it/test>expect

Also i coudnt export my function using 'module.exports = code ' and import using 'code = require './location'. When I did that, it said that require was not defined.

you can use import instead of require, as it was in all the repo examples

I do not know why but I couldn't get the 'description', and the 'it' function rolling.

it is just supposed to be a description of what you are doing, a bit like a comment

Week 1
I Need Help With:

Nothing so far everything is going super smooth. I did 424 tests which super cool.

What went well?

Using jest went really well, a little tutorial helped me understand that there is a lot of cool features with jest.

What went less well?

Syntax for the test is very easy to break and can get really confusing, i broke the test so many times.

Lessons Learned

Writing tests makes you fell confident when upgrading your function and it also shows where your function is lacking, my function was lacking a bit which testing helped me fix.

Sunday Prep Work

Im gonna get prepared for it today.

Nothing so far everything is going super smooth. I did 424 tests which super cool.

wow, nice job Alex 💪

Syntax for the test is very easy to break and can get really confusing, i broke the test so many times.

yes, I feel your pain..many brackets and curly braces 🙂 it is good practice though! you will be a master spotter


Type safety, CSPRNG, avoid chr()

https://paragonie.com/blog/2017/02/cryptographically-secure-php-development#chr

Question to the maintainers: This change will break compatibility with older PHP versions < 7.0 I'm not up to speed with the development guidelines when version compatibility is concerned. Is this something to consider here, or at least to mention in the upcoming release :)

Yep, that was me :smile: After writing that comment I realized the random_compat polyfill was also added to the project.

Thanks for poking me.
I would say that the U2F libraries currently existing is in a sort of maintainance mode with webauthn happening. With that said we should be clearer on that and communicating what we consider should be happening with them.
As for this pull request I'm fine with most of it. How important do you consider the switch from openssl_random_pseudo_bytes() ? I'd like to avoid adding more dependencies if we don't have to.

I would say that the U2F libraries currently existing is in a sort of maintainance mode with webauthn happening.

Funny that you should mention that...

How important do you consider the switch from openssl_random_pseudo_bytes() ?

OpenSSL's userspace PRNG has caused collisions in PHP software before. Your users are much better served by the kernel's CSPRNG, which is what random_compat uses (and what PHP 7+ does, natively).

Agreed the points you make there, yet webauthn seems to be happening in the browsers which is the framework we have to work in here.
Fair enough on prng, going to merge this. Thank you!

So the psalm checks seem to fail now that this is merged (https://travis-ci.org/Yubico/php-u2flib-server/jobs/419535637) but worked on the pull-request, do you have an inkling as to what's going on here?


[feature-request] Convert "Studies" tab Interface to SwiftUI

Describe the solution you'd like
Update the primary navigation list of the CardinalKit sample to leverage the flexible features of SwiftUI.
Use tutorial https://developer.apple.com/tutorials/swiftui/building-lists-and-navigation#Get-to-Know-the-Sample-Data as reference.
Create a sample Resource file such the landmarkData.json file seen above. Use hard-coded data for now.
A next step will be to grab this resource and populate it from server data (Firestore).
NOTE: interest on features is gaged using reactions on this first post: e.g.  👍

@all-contributors please add @ssgutierrez42 for code

@all-contributors please add @varunshenoy for code and maintenance. Also add @ssgutierrez42 for maintenance.

@all-contribbutors please add @varunshenoy for code

@all-contributors please add @varunshenoy for code

This feature has been added!


Bump go to 1.19.4

Pull Request Motivation
Fixes some CVEs. See announcement.
Kind
/kind bug
Release Note
Upgrade to go 1.19.4 to fix CVE-2022-41717

/cherry-pick release-1.10

/lgtm


Support ISR pages

It seems that ISR is not working as expected, it appears to be a Vercel thing.
Searching on the Svelte Repo it is confirmed here:
https://github.com/sveltejs/kit/issues/661#issuecomment-1430004751


[DO NOT MERGE IT YET] Release v1.1.0

:warning: [DO NOT MERGE UNTIL ALL THE ISSUES/PRS ARE DONE] :warning:
Pending to release
Issues:

[x] #250  - Bug: Borders are not working in Firefox
[x] #244 - Bug: Borders is not responsive anymore (priority: high)
[x] #238 - Bug: White border of the container is-dark is missing
[ ] #246 - Enhancement: Icons-Heart-Half-Empty (priority: low - waiting corrections)
[ ] #58 - Add tests (priority: medium - waiting corrections)
[x] #262 - Bug: Icon less than 10px on Chrome

PRs:

[ ] #247 - half empty heart (ref #246)  (priority: low - waiting corrections)
[ ] #245 - Adds Input-File feature (priority: low - waiting corrections)
[ ] #94 - Add testing suite (ref #58) (priority: medium - waiting corrections)
[x] #261 - Fix border bugs (ref #250, #238)

Personal thoughts
Those three bugs are a regression in the framework.
In my opinion we can not make another release until those are resolved.
I tried a few things but couldn't make it work like it was before.
I can revert some of it but that's pretty much it. Would like to hear some thoughts in this.

We need to update via CDN on README.md. ✏
<!-- minify -->
<link<EMAIL_ADDRESS>rel="stylesheet" />

I'd like to release NES.css in a shorter span from next time. 🚀

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[build-script] Stop installing the llbuildSwift library that is no longer used

I'm cross-compiling the trunk Swift 6.1 toolchain for Android and was surprised to find that this library hasn't been used by the linux toolchain in years, as the following shows no other binary links to it:
> ag --search-binary libllbuildSwift swift-5.* swift-6.0.2-RELEASE-fedora39/ swift-DEVELOPMENT-SNAPSHOT-2024-11-09-a-ubi9/
Binary file swift-5.10.1-RELEASE-fedora39/usr/lib/swift/pm/llbuild/libllbuildSwift.so matches.
Binary file swift-5.8.1-RELEASE-ubi9/usr/lib/swift/pm/llbuild/libllbuildSwift.so matches.
Binary file swift-5.9.2-RELEASE-ubi9/usr/lib/swift/pm/llbuild/libllbuildSwift.so matches.
Binary file swift-6.0.2-RELEASE-fedora39/usr/lib/swift/pm/llbuild/libllbuildSwift.so matches.
Binary file swift-DEVELOPMENT-SNAPSHOT-2024-11-09-a-ubi9/usr/lib/swift/pm/llbuild/libllbuildSwift.so matches.

I tried building SwiftPM natively on Android as part of the toolchain with this change and had no problem. The CMake-built swift-bootstrap uses this library but directly from the build directory, not from the install directory, so this pull has no effect on that.
The Windows trunk build uses the new swift-toolchain-sqlite package from @jakepetroules and doesn't appear to install this library already.
I don't know if macOS still needs this library installed, as I don't use that OS, but I can limit this change to non-Darwin if needed.
Jake and @ahoppen, let me know what you think.

@compnerd, OK, but given it isn't actually used on Unix, are you using it on Windows either?
And does anyone know the situation on macOS?

link -dump -imports SwiftDriverExecution.dll | findstr llbuildSwift
    llbuildSwift.dll
                           0 $s12llbuildSwift11BuildEngineC8delegateAcA0cD8Delegate_p_tcfc
                           0 $s12llbuildSwift11BuildEngineCMa
                           0 $s12llbuildSwift11BuildEngineCMn
                           0 $s12llbuildSwift15TaskBuildEngineMp
                           0 $s12llbuildSwift19BuildEngineDelegateMp
                           0 $s12llbuildSwift3KeyVyACSays5UInt8VGcfC
                           0 $s12llbuildSwift4RuleMp
                           0 $s12llbuildSwift4TaskMp
                           0 $s12llbuildSwift5ValueVyACSays5UInt8VGcfC

I would assume that other Unicies should have a similar dependency OR they might be statically linking.

I downloaded and checked the latest OSS trunk Nov. 14 snapshot toolchain for macOS, looks like it currently ships two copies of this dylib:
> find . -name libllbuildSwift.dylib
./usr/lib/swift/pm/llbuild/libllbuildSwift.dylib
./usr/lib/swift/macosx/libllbuildSwift.dylib

Only one library uses it, just like on Windows, and it only appears to use the one in usr/lib/swift/macosx/:
> find . -name "*.dylib" | xargs llvm-objdump --dylibs-used --macho | ag "dylib:$|libllbuildSwift.dylib" |ag -B1 "llbuildSwift.dylib "
./usr/lib/swift/pm/llbuild/libllbuildSwift.dylib:
        @rpath/libllbuildSwift.dylib (compatibility version 0.0.0, current version 0.0.0)
./usr/lib/swift/macosx/libllbuildSwift.dylib:
        @rpath/libllbuildSwift.dylib (compatibility version 0.0.0, current version 0.0.0)
./usr/lib/swift/macosx/libSwiftDriverExecution.dylib:
        @rpath/libllbuildSwift.dylib (compatibility version 0.0.0, current version 0.0.0)

> llvm-objdump --rpaths --macho usr/lib/swift/macosx/libSwiftDriverExecution.dylib
usr/lib/swift/macosx/libSwiftDriverExecution.dylib:
/usr/lib/swift

> find . -name "*.dylib" | xargs llvm-objdump --dylibs-used --macho | ag "dylib:$|libSwiftDriverExecution.dylib" | ag -B1 "libSwiftDriverExecution.dylib "
./usr/lib/swift/macosx/libSwiftDriverExecution.dylib:
        @rpath/libSwiftDriverExecution.dylib (compatibility version 0.0.0, current version 0.0.0)

> find usr/bin -type f | xargs llvm-objdump --dylibs-used --macho | ag llbuildSwift.dylib

> find usr/bin -type f | xargs llvm-objdump --dylibs-used --macho | ag ":$|libSwiftDriverExecution.dylib" | ag -B1 "libSwiftDriverExecution.dylib "
usr/bin/swift-build-sdk-interfaces:
        @rpath/libSwiftDriverExecution.dylib (compatibility version 0.0.0, current version 0.0.0)
usr/bin/swift-driver:
        @rpath/libSwiftDriverExecution.dylib (compatibility version 0.0.0, current version 0.0.0)

> llvm-objdump --rpaths --macho usr/bin/swift-build-sdk-interfaces
usr/bin/swift-build-sdk-interfaces:
/usr/lib/swift
@executable_path/../lib/swift/macosx

> llvm-objdump --rpaths --macho usr/bin/swift-driver
usr/bin/swift-driver:
/usr/lib/swift
@executable_path/../lib/swift/macosx

Since the one in usr/lib/swift/pm/llbuild/ installed by this command is unused in both the linux and macOS toolchains, should be fine to remove it in this pull, as Windows doesn't use this build-script.
@marcprux, first time I'm looking at macOS dylib dependencies and rpaths, let me know if I missed anything.
@artemcm, I see you tried to statically link on macOS and remove the copy in usr/lib/swift/macosx/ also in swiftlang/swift-driver#965 a couple years ago, but ended up having to revert it: let me know what you think of this cleanup.
This is ready for a CI run, if someone would kick one off.

@swift-ci please test

Alright, passed CI, ready for review.
Since this was added for SwiftPM in #17829 six years ago by @hartbit, but is no longer used, perhaps you can review, @bnbarham?

@swift-ci please test

OK, passed CI again after break, @dschaefer2, perhaps you could review, because this was originally added for SwiftPM but is now unused?

@swift-ci please build toolchain

Let's make sure the toolchain jobs pass, but as far as I can see this is not used 🤔. There's a --llbuild-link-framework in swiftpm/Utilities/bootstrap but it isn't set from build-script at all.

There's a --llbuild-link-framework in swiftpm/Utilities/bootstrap but it isn't set from build-script at all (maybe we should remove it too?).

Looks like that was added a long time ago and build-script sets it to build against the fresh llbuild in the build_root, not this installed llbuild in the toolchain. It does however add a backup rpath to this directory on macOS, so those two lines can definitely be removed after this pull, even if you don't want to remove all the logic for that now seemingly unused --llbuild-link-framework flag.

The CI broke early yesterday, #77955, I will rerun the toolchain builds once some of the compiler fixes for that like #77959 are merged.

Alright, toolchain builds should work now.
@swift-ci please build toolchain

Toolchains built fine, @bnbarham, ready for review and merge.

Thanks, I'll submit for 6.1 next.


[FEAT] New event: ROOM_ANNOUNCE

Room Announcement is a feature that most IMs have, and there is no appropriate event for it in Wecahty so far. A possible work around is to generate a text message when Room Announcement changes, however the best pratice I blieve is to make a new event: Room announce.
The event listener will be somethign like:
export type RoomAnnounceEventListener = (room: RoomInterface, newAnnouncement: string, oldAnnouncement?: string)
  => void | Promise<void>

https://github.com/wechaty/puppet/pull/214

Can we check on related PRs? @hcfw007
Thank you very much!


rds.cluster: add ability to auto-generate password in referenced secret

Description of your changes
Adds the ability to auto-generate password for the rds cluster. This was already added for the RDS instance in the PR #628. Users need to opt-in by setting autoGeneratePassword as true while creating RDS cluster and should have a Secret reference. It will create if the referenced Secret does not exist and it will populate if it doesn't have the password for the given key.
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Unit tests, local end-to-end test.

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

/test-examples="examples/rds/v1beta1/cluster.yaml"

/test-examples="examples/rds/v1beta1/cluster.yaml"

/test-examples="examples/rds/v1beta1/cluster.yaml"

@ravibagri5, we need this PR for Uptest to work properly, can you please rebase the PR?

@ravibagri5, we need this PR for Uptest to work properly, can you please rebase the PR?

@turkenf  Sure. Thanks for the update.

/test-examples="examples/rds/v1beta1/cluster.yaml"

/test-examples="examples/rds/v1beta1/cluster.yaml"

/test-examples="examples/rds/v1beta1/cluster.yaml"

/test-examples="examples/rds/v1beta1/cluster.yaml"


Fixed the following Bugs:

Comparing Relations as Strings not as a URI type vs a String.
Casting String to int to work as a flag (a String always evaluated to True).

Thanks Ahmed, I actually came out with a similar fix on my side too
Indeed the issue came from the fact that the source, relation and target parsed by rdflib were not properly casted to string
But this issue (of the type being URI instead of String) most probably applies also to source/target
And the wrong type is attributed by RDFlib in the NtripleReader:
So it is better to recast all variable to string at the start of the NtripleReader
I also added a dirty quick fix so that you guys can continue to use the brackets "<my_predicate>" (so that it is not confusing for the other students)


Marketplace crashes my app?

🔍 Is there already an issue for your problem?

[X] I have checked older issues, open and closed

ℹ Environment / Computer Info
- Spotify version:Spotify per Windows (64 bit) <IP_ADDRESS>0.gc7b23f70
- Spicetify version:v2.37.0

📝 Description
I installed the marketplace and spotify keeps closing at random.
I alreay tried reinstalling everything and every time I install the marketplace it crashes.
Am I the only one with this problem?
Thanks for the assistance
📸 Screenshots
No response

Can't reproduce. Please join our discord server for further help

I found out it is my normal spotify even without spicetify that crashes. I wrote it in the discord


Evaluating the performance of a pipeline

How to add evaluating models for intent classification as a feature. Where would it fit in the rasa pipeline. Create a new module under rasa_nlu called evaluators  ? Or is there any existing module to which this can be added ?
Here is a hacky version of what I seek to implement.
import requests
import json
cnt = 0
for x,y in zip(X_test,y_test):
        inp = ' '.join(x)
        d = {'q':inp}
        data = json.dumps(d)
        res = requests.post('http://localhost:5000/parse',data = data)
        if(res.json()['intent'] == y):
                cnt = cnt + 1
print 1.0 * cnt / len(X_test)

Yes that sounds good, depending on the amount of code, we might need to extend to a package.
Currently there is no seperate way to evaluate models. There is only train and process. We might think about adding a test methods to the components if needed (depends if you can do all of the evaluation from the "outside"). But it might just as well be enough to process each of the test examples on its own and compare the results.
Instead of using the http api, I would directly use python code to call the process method.

@tmbo is this one finished with the evaluate.py functionality?

I think the evaluate functionality is awesome by now, closing.


Navbar properties not working in v4

Almost migrated to v4! great job!
but I'm unable to use this properties for navBar
drawerImage={require('../img/burger.png')}  -> not working
navigationBarStyle={[STYLES.navBar]}  -> this one works
navigationBarTitleImage={require('../img/logo.png')}  -> not working
navigationBarTitleImageStyle={[STYLES.navBarLogo]} -> not working

@jaumebosch Thanks for the feedback. Will add these properties soon.

Keep informed, I'll do the testing :D

And, of course, PR would be welcome if you want to speed up things. There is nothing difficult, you maybe check how other properties are passed.
For drawerImage you may set leftImage directly for now, you may check Example project.

Please check latest beta.7

tested on beta7
navigationBarStyle={[STYLES.navBar]} -> working
navigationBarTitleImage={require('../img/logo.png')} -> working!!
navigationBarTitleImageStyle={[STYLES.navBarLogo]} -> working!!
drawerImage={require('../img/burger.png')} -> not working
I've notice on beta6 that the drawerImage import on navBar.js isn't used anywhere

Seems like leftButtonTextStyle and backButtonTextStyle props don't work either. Can someone approve that?

@jaumebosch drawerImage should work, I've just checked:
 <Scene key="drawer" drawer contentComponent={TabView} drawerImage={require('./images/back_chevron.png')} >
I see 'chevron' instead of 'burger'
Maybe you didn't set it for drawer Scene but for inner tabs?

yep! I was setting once per scene, instead in the drawer scene.
Almost perfect!, but the icon is too low, is there any way to pass a "drawerImageStyle" ??

Was it supported within v3? Maybe you could list other missed nav bar properties too there.

you're right
I've check again on V3 documentation and I can use "leftButtonIconStyle", which also applies to drawerImage

I think we can close it, everything resolved!


Not all buttons have the same timings during (simple) drag fade-out effect

Seems to happen to buttons that have been hovered during the animation that plays with many buttons visible

This has since been removed with the refactoring and implementation of collections.


Read up to marker / Sync read status accross devices

the following commands are not defined
/nick change your nickmae
/topic change the topic
/invite invite an user
/part leave room by alias

Blocked by server API changes which are pending

see https://github.com/vector-im/vector-web/issues/1159

See vector-im/riot-meta#8.


Cannot read property 'incomplete' of null

Issue Id: 409b4d37-61b8-544c-fe61-a24e91501d0cVersions - 1.7.1-  9e7d70052908b633e0d4f71e70b26714bd1d2f10-<PHONE_NUMBER>acdd2425241f16946da2fb3d32489fStack TypeError: Cannot read property 'incomplete' of null/vs/editor/contrib/suggest/common/suggestModel.ts#L388:24 (incomplete)/vs/editor/contrib/suggest/common/suggestModel.ts#L327:8 (triggerFromIncomplete)/vs/editor/contrib/suggest/common/suggestModel.ts#L192:8 (onCursorChange)/vs/base/common/event.ts#L155:12 (apply)/vs/base/common/eventEmitter.ts#L303:9 (func)/vs/base/common/eventEmitter.ts#L182:4 (safeInvoke1Arg)/vs/base/common/eventEmitter.ts#L201:8 (_emitToSpecificTypeListeners)/vs/base/common/eventEmitter.ts#L216:8 (_emitEvents)/vs/editor/common/commonCodeEditor.ts#L888:12 (emit)/vs/base/common/eventEmitter.ts#L303:9 (func)

We removed that code


Epoll and KQueue to use static initializers

Motivation:
Epoll and KQueue transports use an instance initializer instead of a static initializer to ensure the JNI libraries are loaded before use. However the availability of the JNI libraries will not change after class load time so static initializers should be sufficient.
Modifications:

Change the instance initializer to a static initializer for Epoll and KQueue initialization in their respective EventLoops

Result:
Less initialization required at instance creation time.

@carl-mastrangelo - FYI

These instances are created seldomly so the amount of extra work should be small, no?  Also, as mentioned in the previous PR, moving init to static leads to confusing errors when static initialization fails (for whatever reason).  Leaving in instance initializers turns a NoClassDefFoundError into the actual one.  If you look at my commentary on the original PR, you can see I had to set special VM flags to get at the actual error, which is above what I would expect others to know how to do.  Lastly, it doesn't seem so bad to do it at instance creation time.  There are no static members or code in these classes that actually depends native code being available at classload time.
I don't think the benefits outweigh the downsides.

I agree with @carl-mastrangelo here... @Scottmitch any concerns ?

@carl-mastrangelo while I did point out a minor short-coming in the static initializer use, we avoid that trap by invoking Epoll.isAvailable() before trying to create the EpollEventLoopGroup instance which seems to do the trick.

thanks for the feedback @carl-mastrangelo ... since instance creation is expected to be relatively low and having the instance initializers provides more useful feedback let me close this PR.


Preparations for rojo to support Tags/Attributes.

Attributes are now written in rbx_xml.
Tags are no longer written if the container is empty.
Attributes now have pods implemented in rbx_dom_lua.
Improved pods for inf/nan values in Float32 and Float64.

Seems to have been taken care of in https://github.com/rojo-rbx/rbx-dom/pull/228
Merge conflicts are busted, so I'll just close this now.


Make a disk to boot as on option for OS tests

It would be helpful if we can take a optional param as disk and that can be used to boot
and run further tests, will be helpful incase of multiboot system and we can control where we want to run
tests which would help/save time.
there is a method in common/OpTestInstallUtil.py - set_bootable_disk() but that would require a reboot again, if we can have a handle in petitboot and have a mechanism to boot into specific disk would be more helpful.
Let me know incase if we have that already implemented. Thanks.

Yeah, I agree that would be useful. It would also be good to be able to pretty easily add kernel parameters as well (e.g. we could then run things with radix_disable and other such options).
@sammj what are your thoughts here?

Sounds a bit like --scratch-disk, except this would be an existing disk rather than installing something fresh right?
I agree also that it would be useful - probably something I can help support via https://github.com/open-power/petitboot/issues/36 too.


Update paths for Insights navigation panel changes

The new Insights navigation panel will appear as follows.
Overview
Details
 > OpenShift
 > Infrastructure
Cost models

This still needs to work with the existing links for "OpenShift could infrastructure details", "OpenShift details", & "Cloud details".
For testing cloud-services-config changes locally, see:
https://github.com/RedHatInsights/cloud-services-config#testing-your-changes-locally

verified


Localized Views and Controllers

View files and Controllers Localised

@fishmad  Great work, thank you very much :+1:

#5 #21 #22


Client ID? Or AppID URL?

When configuring the server, the guidance here and here say to use the client ID, which is clarified in both cases to mean the Application ID. But in my testing, I actually had to provide the "App ID URL." If I provided the Application ID, my client would get a 401 error indicating that the audience is invalid. Which makes sense - the server is expecting tokens for a GUID and the client is providing a token that's valid for a URL. In turn if I configure my client to use the server's Application ID instead of App ID URL, I get an error from AAD indicating that the token cannot be issued.

So am I the only one that's stumbled over this? Should the docs be updated to say App ID URL?
Or am I doing something wrong in the server side config?
In my case, my server's identity is an AAD "App Registration" but maybe these directions are for "Enterprise Applications" which have different rules/IDs?

Thanks,

Track this for the new middleware - if we still need to support the App ID URL. Need clarity from portal/app model teams.

Documentation for how to set audience claim for new Node Token Validation library will be tracked internally in ADO, closing. @jo-arroyo


Any "ap" alternative

Hello Kyle,
I was looking at some Monad libraries and they usually have "ap()" method which applies function (returned from the current monad action) to the value returned by IO monad we pass as argument to "ap()". Are there any alternatives in Monio?

Most of the monads in Monio are Applicatives and have the ap(..) method. If you're holding a function in a non-IO monad (like Maybe), those already have the ap(..) method you need, and you'd just pass in an IO instance and it should work I believe:
const incM = Maybe.from(v => v + 1);
const twoIO = IO.of(2);

incM.ap(twoIO);  // IO(3)

Is that what you need?
IO (and its variants) aren't Applicative themselves currently (used to but then I took it off because I didn't think it made sense).
I'm open to making IO be Applicative again, but I'd like to see a code use-case (even a demo using another lib) to determine how best to design/implement it.

Thank you for your response Kyle
What I wanted is to get element from the DOM and set its text content, for that I used IO monad to wrap those side effects.
const getElement = id => IO(() => document.querySelector(id))
const setElementText = element => text => IO(() => element.textContent = text)

I figured I can do this:
getElement('h1').map(setElementText).run()('New Title').run()

But it feels kind of strange because I need to pass the argument after calling "run()" and I need to call "run()" twice, so maybe there is a better way? I know I can just swap arguments position in "setElementText" function so I can do this:
const setElementText = text => element => IO(() => element.textContent = text)
getElement('h1').map(setElementText('New Title')).run().run()

But I am still calling "run()" twice. Is there a better way?

That's exactly what chain(..) is for:
getElement('h1').chain(el => setElementText(el)('New Title')).run();

As you mentioned though, changing the param order of setElementText(..) is better, if possible. It's more "canonical FP" design for multi-param functions to take fixed inputs first and unfixed inputs last. As you illustrated, that often makes it easier to take advantage of point-free style (to partially-apply/specialize the function call).


Add travis

Describe your PR
This .travis.yml plus changes (some indicated by @juddey) - helps ignite master run against Facebook master every 24 hours.
As you can see there is a problem in the current build, and this identifies an early warning issue.

Apologies

@juddey - I know you were augmenting the tests for ./testRelease.  Please rebase with these changes.  If you need help, let me know.  SORRY!

ALSO SORRY!

Whomever merges this PR, please squash it.  I have mannnnny commits, because that's kind of the only way to test against travis ci.

hey @gantman, just reviewed your changes. I've finished my PR locally now, but I think it'll be easier to manage once this has all been merged to master, happy to wait a few days for that to happen.
Just fyi, the PR that I have done will run each generator and verify that the files were created, so there's not much crossover with what you've done.

I'll self-merge!

Wouldn't want to run into this beast in a conflict resolution! 👹


Add Text Support

Support SVG Text in animation

Basic text is now supported though with some bugs, opened new issues for these bugs.

how is this supported? I'm still not seeing the option to use the text tool.

Its 2017: I installed the SnapSVG-Animator Plugin in CC (Win 7, 64bit). The text-tool in CC isn't available.
In "C:\Program Files (x86)\Common Files\Adobe\CEP\extensions\com.example.SnapPlatform\plugin\lib\res\Features.xml" I try to enable the entry  to "true" - now the text-tool is visible and I can put text in a MovieClip: But after export the svg is broken: In source code a text-node is visible - but the other MovieClips lacks. In the browser I see a white page.
After reinstall CC and install the plugin not with the extension manager rather with the Creative Cloud App: Nothing changes. I also try to replace manually the plugin code with the code of dev-branch - nothing changes.
What can i do?


refactor(component): revert changes for conditional meta tag renders

next-seo provides a nice static json config for seo tags, but for the previous conditionaly rendered dyanmic tags is not too friendly. resorting back to next/head
close #3838

amendment to #4218


Regression: owner variable is unset before tree_exiting signal

Tested versions

Reproducible in: 4.2.dev [ba23081eb], 4.2.1-stable, 4.3-beta1
Not reproducible in: 4.0.4-stable

System information
Linux Mint 21.3 (Virginia)
Issue description
This is a regression from #56498 which was fixed with #55512.
As that PR states,

Regarding preservation of owner, free() and remove_child() now behave the same: owner is kept during tree_exiting signal and null during tree_exited.

Instead, since commit ba23081eb the behaivour of free() and remove_child() differs, and owner is deleted prematurely when using free()
Steps to reproduce
Using an updated version of the minimal project provided in #55512
Sample scene

Code
extends Node2D

func _ready():
	var se1f = self
	$A.connect("tree_exiting", Callable(se1f, "exiting").bind($A))
	$A.connect("tree_exited", Callable(se1f, "exited").bind($A))
	$A/Node.connect("tree_exiting", Callable(se1f, "exiting").bind($A/Node))
	$A/Node.connect("tree_exited", Callable(se1f, "exited").bind($A/Node))
	$A/Node/B.connect("tree_exiting", Callable(se1f, "exiting").bind($A/Node/B))
	$A/Node/B.connect("tree_exited", Callable(se1f, "exited").bind($A/Node/B))
	$A/Node/B/B2.connect("tree_exiting", Callable(se1f, "exiting").bind($A/Node/B/B2))
	$A/Node/B/B2.connect("tree_exited", Callable(se1f, "exited").bind($A/Node/B/B2))
	$A/Node/B/C.connect("tree_exiting", Callable(se1f, "exiting").bind($A/Node/B/C))
	$A/Node/B/C.connect("tree_exited", Callable(se1f, "exited").bind($A/Node/B/C))
	#remove_child($A) # this works
	$A.free() # this doesn't

func exiting(node):
	prints("exiting", node.name, node.owner) #prints node; before it was null

func exited(node):
	prints("exited", node.name, node.owner) #prints null

Using remove_child($A) works as expected:
exiting C Node2D:<Node2D#26809992391>
exiting B2 B:<Node2D#26860324043>
exiting B Node2D:<Node2D#26809992391>
exiting Node A:<Node2D#26826769610>
exiting A Node2D:<Node2D#26809992391>
exited C <Object#null>
exited B2 B:<Node2D#26860324043>
exited B <Object#null>
exited Node A:<Node2D#26826769610>
exited A <Object#null>

While using $A.free()
exiting C Node2D:<Node2D#26809992391>
exiting B2 B:<Node2D#26860324043>
exiting B Node2D:<Node2D#26809992391>
exiting Node <Object#null>  # Bug
exiting A <Object#null>  # Bug
exited C <Object#null>
exited B2 B:<Node2D#26860324043>
exited B <Object#null>
exited Node <Object#null>
exited A <Object#null>

Minimal reproduction project (MRP)
minimal_4.2.zip

Upon further inspection, the owner of the node upon which .free() is called ($A, in the example) is being cleared before the tree_exiting singal since commit 1eb250e17 (v4.1).
To recap, the behaivour of $A.free() is as follows
Before 1eb250e17
exiting C Node2D:<Node2D#27548189841>
exiting B2 B:<Node2D#27598521499>
exiting B Node2D:<Node2D#27548189841>
exiting Node A:<Node2D#27564967065>
exiting A Node2D:<Node2D#27548189841>
exited C <Object#null>
exited B2 B:<Node2D#27598521499>
exited B <Object#null>
exited Node A:<Node2D#27564967065>
exited A <Object#null>

Between 1eb250e17 and ba23081
exiting C Node2D:<Node2D#26591888529>
exiting B2 B:<Node2D#26642220187>
exiting B Node2D:<Node2D#26591888529>
exiting Node A:<Node2D#26608665753>
exiting A <Object#null>  # <------
exited C <Object#null>
exited B2 B:<Node2D#26642220187>
exited B <Object#null>
exited Node A:<Node2D#26608665753>
exited A <Object#null>

After ba23081
exiting C Node2D:<Node2D#26809992391>
exiting B2 B:<Node2D#26860324043>
exiting B Node2D:<Node2D#26809992391>
exiting Node <Object#null> # <------
exiting A <Object#null> # <------
exited C <Object#null>
exited B2 B:<Node2D#26860324043>
exited B <Object#null>
exited Node <Object#null>
exited A <Object#null>

In all tested versions, the behaivour of remove_child($A) remains the same as the first case.

Therefore, it should be removed by the parent node first and then clear the owner.
https://github.com/godotengine/godot/blob/e96ad5af98547df71b50c4c4695ac348638113e0/scene/main/node.cpp#L225-L236


apps: add migrations step for gatekeeper psps violations

Add a step to the migration docs for restarting the pods that are or will be violating the new gatekeeper PSPs.
What this PR does / why we need it:
Which issue this PR fixes:
fixes #1495
Public facing documentation PR (if applicable)

Special notes for reviewer:
Add a screenshot or an example to illustrate the proposed solution:
$ ./migration/v0.30/apply/90-psp-violations.sh execute
[ck8s] 90-psp-violations.sh: using config path: "/home/olle/Documents/olle-exoscale"
[ck8s] 90-psp-violations.sh: using sc kubeconfig unencrypted
[ck8s] 90-psp-violations.sh: using wc kubeconfig unencrypted
Will trigger a rollout restart of StatefulSet/alertmanager-kube-prometheus-stack-alertmanager in monitoring
Will trigger a rollout restart of DaemonSet/fluentd-forwarder in fluentd-system
Will trigger a rollout restart of DaemonSet/ingress-nginx-controller in ingress-nginx
Will trigger a rollout restart of Deployment/kube-prometheus-stack-operator in monitoring
Will trigger a rollout restart of DaemonSet/kube-prometheus-stack-prometheus-node-exporter in monitoring
Will trigger a rollout restart of DaemonSet/fluentd-fluentd-elasticsearch in fluentd
Will trigger a rollout restart of DaemonSet/fluentd-forwarder in fluentd-system
Will trigger a rollout restart of DaemonSet/ingress-nginx-controller in ingress-nginx
Will trigger a rollout restart of DaemonSet/kube-prometheus-stack-prometheus-node-exporter in monitoring

Checklist:

[ ] Added relevant notes to WIP-CHANGELOG.md
[ ] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[ ] is completely transparent, will not impact the workload in any way.
[x] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[x] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config (if applicable)
If you change some config options (e.g. add/rename variable or change the default value) you may need to update the config used by the pipeline in pipeline/config.

Should I explicitly ignore anything found in a namespace called rook-ceph?
I'm guessing if an environment has rook-ceph installed that it won't respond to kindly to "uncontrolled" restarts.
@Xartos

Should I explicitly ignore anything found in a namespace called rook-ceph?
I'm guessing if an environment has rook-ceph installed that it won't respond to kindly to "uncontrolled" restarts.

Right, yes. Or does it wait for the rollout to finish before continuing with the next? If so then it should probably be fine

The rollout process is async so it will not wait any longer then it takes to trigger the command and receive the response.

The rollout process is async so it will not wait any longer then it takes to trigger the command and receive the response.

Hmm, yea then it's probably best if it could skip that namespace and print at the end that the user needs to do that themselves


Documentation improvements for First Time User Experience

I wanted to raise a few suggestions for discussion relating to my first encounter with this package. Happy to work on PRs for anything within my skillset!

My first try after installing the module was Import-Excel .\somefile.xls. This failed with an exception that didn't give me a clear direction forward. I wonder if it's technically possible to recognize the incompatible file type and indicate that in the error message, or suggest the use of ConvertTo-ExcelXlsx.

From finding the module in the PSGallery and coming to this repo as the linked project site, I went looking for online documentation, since clicking around on a website is always a better exploratory experience than running Get-Help dozens of times. I don't necessarily know that automatically replicating PSHelp online for community projects (like in a GitHub wiki) is a solved problem, but it may be worth mulling over, considering this project provides so many commands. Reading comment-based help in source files isn't terrible, but since all of the files are at the root of the repo and not all of them are exported functions, the usability isn't great. Perhaps restructuring the repo itself would be a good idea?

The repo's homepage experience has a number of problems for someone looking for information on getting started:

As mentioned, lots of files at the repo root to scroll past before you see any readme info
Release notes go on forever. Consider putting them into a separate markdown file linked from the readme, or limiting to only the latest major version.
The readme actually has sections for Examples and Known Issues after all of the release notes! One would usually assume that a release notes section so long must be the last section in the document, since you only need to keep scrolling if you want to go further back in time. These sections should probably be reordered so that Examples and Known Issues are first and release notes are at the end.
Anchor links to the markdown headers for each section could be added in a contents structure near the top of the readme.

I would also suggest that it be conspicuously documented somewhere that .xls files are not natively supported. I couldn't find this information until I went looking for existing issues (#323). It makes perfect sense given the tooling that this code relies on, but that context isn't known to someone finding the package for the first time, and since xls files aren't going away any time soon (mostly due to old software that generates them automatically) I can see this being a source of frustration as it was for me.

Thanks! PRs are welcome

I'm to figure out how to open an existing workbook, target a worksheet and append a row using set-row.
Cannot get and existing file "opened". Looks like I have to use Export-Excel -Path and -Passthru
Get an error for using an existing file.
I also feel the structure of the lib somewhat awkward.
Looks like set-row has the functionality of picking a new row if not specified.
Maybe the module should have been PSExcel or something. I would really appreciate getting some tips on what I'm trying to accomplish.
Thanks!

Managed to get futher...
So I missed there was an Open-ExcelPackage
My first Set-Row will set "TEST" to all cells of the first available row.
The Set-Format allows me to target a particular cell but feels awkward. Maybe Set-Cell or Set-Cells where one could pass an Array to populate the range or a particular row.
What am I missing here? I need to append data to an already existing spreedsheet. Most examples are starting out deleting any existing file to create from scratch.
$excel = Open-ExcelPackage $popFile
$ws = $excel.Workbook.Worksheets["FR"]

Set-Row -Worksheet $ws -Value "TEST"
Set-Format -Address $ws.Cells["a10:d10"] -Value "C"
Set-CellStyle
Close-ExcelPackage $excel -Show

I could make a loop over my Array and use Set-Format -Address but that just feels overworked having a Excel library.
Any pointers? Thanks!

https://github.com/dfinke/ImportExcel/blob/master/Export-Excel.ps1#L19

Well that was easy! Thanks for the support and sorry for stealing the thread somewhat.
$myhash | Export-Excel -Path $File -WorksheetName "FR" -Append


add cado-nfs driver

With the current block target of 272 bits cado-nfs doesn't provide a speedup over yafu but for a 512 bit work target it will.
There is a lot of loading time for cado nfs binaries to start sieving, while yafu binary loads in a fraction of a sec. That time is critical.

@daedalus I agree. In fact, even when NFS starts to kick in somewhere around difficulty levels of 300 to 330 or so YAFU is still king. The reason to get CADO-NFS in now is just to be ready because at some point it will needed.
I've read somewhere that it is possible to do some magic to use YAFU with MPI to coordinate factoring one number on several machines. We will need to look into that at some point as well.


CLEWS-26704-1 Bug fix after adding api host

This bug gives me opportunity to ponder if it would be better to pass api_token as a kwarg as well like api_host?

How about the environment variable: GROAPI_TOKEN


rz-slider-on-end not working

I need to identify which slider created the callback. Every attempt to do that is not working. Even the id is not passed into any callback mechanism. The onEnd option function does not pass parameter either. The injected event only passes $scope.
And this option does not even create a callback: rz-slider-on-end="onSliderEnd( parameter)".
Any idea how to implement this?

What version are you using? Since version 2, there is no rz-slider-on-end attribute but there is arz-slider-options that takes an object...

I have tried that and I can't make it work. I cannot figure out which
slider it was.
The combination of ng-repeat and your slider that does not identify itself
which object it controls is not possible.
onEnd does not provide parameter.
Since then I, using material slider <md-slider,,, That works like this:

See, I need the object "device" to identify which slider it was. The number
of sliders is dynamic on the screen.
Thanks for your help anyway.
You may want to update the various old pages that describe the use of the
rz-slider-on-end
And the version you have on Github, the version you get with npm and the
version for bower differ.
Cheers
Juergen
On Sun, Nov 29, 2015 at 10:12 PM, Valentin Hervieu<EMAIL_ADDRESS>
wrote:

What version are you using? Since version 2, there is no rz-slider-on-end
attribute but there is arz-slider-options that takes an object...
—
Reply to this email directly or view it on GitHub
https://github.com/rzajac/angularjs-slider/issues/188#issuecomment-160527150
.

The latest version on github, npm and bower is 2.1.0.
I have tried to make the documentation in the ReadMe as clear as possible but if there are still some unclear points, let me know and I'll update it.
If you can provide a JSFIddle showing your issue, I could help you but with the info you gave me, I can't do anything.

I am having the same issue and here is a fiddle that I hope shows what is happening.
http://jsfiddle.net/j141ved2/3/

@fredrickJones I don't see what the issue is apart from the fact that setContrast is not defined.

I know setContrast isn't defined, I know what I wnat to do in the function when I get the object to it. I am not sure how to reference that specific iteration of the ng-repeat in my function. I don't see how I can send through an an argument from the front-end ie: setContrast(img).
Everything that I have seen sends a sliderId, modelValue, highValue but I need the whole img object.

I don't see any update on your fiddle...

I defined the function at the bottom plus added some comments.
http://jsfiddle.net/j141ved2/6/

You should use the id option in order from which slider your onEnd is called like on this example: http://jsfiddle.net/7m0aoLcf/ . Then you should be abel to retrieve to correct img from the id.

so there is no way to bring in the whole object, just a reverence to the id?

What object are you talking about?

never mind I think I just figured it out. I was didn't see everything that you had done on the fiddle.

 ;)


Adding new axes removes previous generations

Generate a page with 2 checkpoints/models.
Generate again but this time add another axes with 2 samplers.
Generations from step 1 are removed/replaced from the page.

Also I can add new axes but can not change or remove existing ones

You either
A: are working from the UI (as opposed to YAML) and didn't refill the old axis data when doing a new run, or
B: configured it properly but used a new folder name

To recontinue a prior run, you must either
A: use a YAML file (so that the old axis config is still there) and just add new stuff to it, or
B: use the UI and fill out all axes exactly the same as they were before (or just don't close the webui page before generating again)

A: use a YAML file (so that the old axis config is still there) and just add new stuff to it, or

Does it mean that even if I use YAML, i can not change exisiting params? e.g. In second run if I want to use just one and a different seed (instead of previous 2 or more), its not possible?

I'm not sure what you mean.
I can tell you you can do basically whatever you need to do, the question is just how to do it properly.
As to how, it depends on what you mean.
If for example you want to change the value of a specific parameter within an axis and redo the run, but keeping the existing generations for all the others, via YAML, you can just add a new parameter and delete the old one, making sure the key is different.
If you want to generate an even smaller subset of changes, you can either
(A) delete the existing images you want redone so only those get reran, or
(B) use YAML and set "skip: true" on every parameter you don't want to rerun, and run with "overwrite existing images" checked.
If neither of those are what you're asking, please try to clarify what you mean.

Lets say we do:

2 samplers (euler, ddim)
1 prompt (tree)
2 seeds (1, 2)

after this I want to update the grid with different and less parameters this time

1 sampler (dpm2)
1 prompt (flower)
1 seed (5)

can i do this while still keeping all results from first run in the grid?

Yes - just add them.
As in, keep your old parameters in place. They will not be regenerated unless you enable "Overwrite existing images".
If you want to prevent crossing over (eg you don't want to generate dpm2 + tree) you can use the YAML file mode and add skip: true to all params you don't want running at all.


JOE: new package at 4.6

Description of package
JOE's Own Text Editor, is a dead simple editor styled around Wordstar, EMACs and other editors of yesteryear. It features a simplistic text based interface multiple modes to emulate popular editors. A configuration system and many other features.
[x] I agree to maintain this package.
[x] I agree to notify @dylanaraps if I can no longer maintain this package.**

Not bad for a first pull request!

You should submit this to https://github.com/kiss-community/community/. :+1:


License ?

Hello, under what license is this project released under ? Thank-you.

I've added a license description (MIT)


[Question] Unable to set --tls=disabled on my private registry

While running the command on my registry
Command :  regctl registry set --tls=disabled test.setup.svc:5000
i am getting : mkdir /.regctl: permission denied
Is there any way to give a specific path to regctl or how i can set the tls to disabled

By default, regctl and the other commands use the user's home directory, specified by the $HOME environment variable. That location can be overridden by setting the $REGCTL_CONFIG variable to the path and filename you'd prefer. For one-off commands, there is an option to specify host parameters directly on the CLI with:
regctl --host reg=test.setup.svc:5000,tls=disabled tag ls test.setup.svc:5000/repo