Fix exception and a nicer formatting for "Topic" label

Fixes an exception that gets thrown when the window is too small for matplotlib to display by setting a minimum window size

Same as https://github.com/ros-visualization/qt_gui_core/pull/211#issuecomment-606839789
@mlautman I have deleted the newly created branch eloquent-devel and with it this merged patch. Please redo the contribution targeting the latest ROS 2 branch if there is no reason to branch.


Unable to rad init with v0.33.0

Steps to reproduce

Uninstall v0.32.0
Install v.0.33.0
Execute rad init

Observed behavior
➜   ✗ rad init
Unable to verify Radius installation. Cause: Kubernetes cluster unreachable: no Auth Provider found for name "oidc".

➜   ✗ rad version
RELEASE   VERSION   BICEP     COMMIT
0.33.0    v0.33.0   0.33.0    6ffdc9980420c00f7af35b024dd0e62e598efef2

Desired behavior
Radius should initialize the cluster
Workaround
No response
rad Version
RELEASE   VERSION   BICEP     COMMIT
0.33.0    v0.33.0   0.33.0    6ffdc9980420c00f7af35b024dd0e62e598efef2
Operating system
macOS Sonoma 14.4.1 M1
Additional context
No response
Would you like to support us?

[ ] Yes, I would like to support you

AB#12242

I think this is failing because we failed to register the OIDC auth provider in the rad cli.
Here's an example of a similar bug: https://github.com/kubernetes/client-go/issues/345
We already do this for our controller (all auth plugins) right here: https://github.com/radius-project/radius/blob/main/cmd/controller/main.go#L27
I think the right home would be where we initialize the Kubernetes client in the CLI: https://github.com/radius-project/radius/blob/main/pkg/cli/kubernetes/kubernetes.go
Interested in sending us a PR?

Sure :)


Example does not user Sliver for Header/Footer

Change log for version 2.0.0 details breaking issue where header and footer only accept Sliver Widget.  Example code uses Text() Widget.  As a result the example code does not run and causes dart framework to crash.  Please correct example code.
I only found this b/c another user in an unrelated Stack Overflow post mentioned not using Sliver in a custom scroll view caused a similar error.  Then I stumbled across the change log and made the connection.  Other devs may not be so lucky.

Did you found solution?


Use java Attach API to avoid jvm restart and javaagent parameter

Hello,
Was thinking that the com.sun.tools.attach api would make it easier for people to install/adopt this tool.
Curious if you have tried it and ran into issues or just haven't had the time?
Thanks,
--Erik Ostermueller

hello,
I thought about it but did not try as it appeared to require more work...
But feel free to create a pull request!

Greetings,
I'm in the middle of trying to code support for this issue I created.
Loading the agent jar file without the javaagent parameter was pretty straight forward.  I have this coded on my own local fork.  But I've run into a problem I don't know how to deal with.
The code at link [1] below suggests that ByteBuddy leaps into action when a java.sql.Driver is instantiated.  Unfortunately, the goal of my enhancement is to launch the agent minutes or even hours/days after the jdbc Driver has already been instantiated.
Perhaps my enhancement could iterate thru DriverManager.getDrivers() (see link [2]) and pass the instances on to ByteBuddy?
If that looks helpful, perhaps you could show me what that code would look like?
Thanks,
--Erik
[1] https://github.com/sylvainlaurent/JDBC-Performance-Logger/blob/master/jdbc-perf-logger-agent/src/main/java/ch/sla/jdbcperflogger/agent/Agent.java#L46
[2]

I'm not at all a ByteBuddy expert. You should try to get some help with the ByteBuddy community.


Allow cancel of transfer

Right now, users can initiate a transfer, but there's no way for them to cancel it! Most of the time that shouldn't be a problem, but.

[ ] Allow orderer to cancel a transfer
[ ] Alert transferee candidate that the transfer has been cancelled
[ ] Refund amounts cannot include the sum of transferred items


Make Arango CTI Processor jobs automatic

Currently use triggers job manually
/api/v1/arango-cti-processor/{mode}/

However, we should trigger these based on downloads (e.g. CVE POST download, ATT&CK POST download), and remove this endpoint.
We should run the modes of the download.
e.g. if user downloads ATT&CK, the following modes will run after the download
attack-capec, capec-attack, cve-attack

Note, to stop issues with jobs conflicting, only one download job (with Arango CTI Processor joins) should run at any time.
Lets say user runs download CVE and then immediately download ATT&CK, the ATT&CK job will be queued until the CVE download completes.

what arguments should they be run with?

These tasks have arguments, so what arguments should they run with... Should it run as the same job or spawn another job?

to me (although i'm not totally sure) it makes sense to separate jobs.
e.g. lets say i run
GET /api/v1/cve/

to download CVES
this would mean the following ACTIP modes would need to be run: attack-capec, capec-attack, cve-attack
We could wrap each of these as a job (but could include them in the download job too). I'll let you decide.
The other point being (which might affect the decision) is that lets imagine a user runs
GET /api/v1/cpe/

before the CVE tasks complete.
We should not start this job (and all ACTIP jobs) until the CVE one completes.

@fqrious actually ignore this ticket for now. It makes more sense to add this logic (as a feature) to the Vulmatch web app.


Repeater defaults not working for Toggle/Select form components

Package
filament/filament
Package Version
v2.13.10
Laravel Version
9.18
Livewire Version
No response
PHP Version
8.1
Bug description
When setting a default array for the Repeater component, the defaults of a Toggle and Select component are not set. For TextInput components in the repeater it is working.
Steps to reproduce
Forms\Components\Repeater::make('boards')
                        ->orderable('sort_order')
                        ->default([['title' => 'The title is working' 'visible' => true, 'options' => 'option2']])
                        ->schema([
                                Forms\Components\TextInput::make('title')->required(),
                                Forms\Components\Toggle::make('visible'),
                                Forms\Components\Select::make('options')
                                    ->options([
                                        'option1' => 'Option 1',
                                        'option2' => 'Option 2',
                                    ])
                        ]),

Relevant log output
No response

It works if you move the default value to each input instead of having them as an array in the repeater like: Forms\Components\Toggle::make('visible')->default(true),

Thanks, but I want to set the defaults dynamically so I cant use it like that.

Can you provide us a reproduction repository URL and then we'll look at your issue? That would allow us to download it and review your bug much easier, so it can be fixed quicker. Please make sure to give us some instructions on where to find the bug, and include a database seeder with everything we need to set it up quickly.

Hey, could you check if #3495 fixes this and doesnt introduce more issues?

I also encountered the same issue. While the default method didn't work for me in my environment (v2.17.48), I was able to achieve it using afterStateHydrated. Here is an example for your reference:
Components\Repeater::make('stores')->label('stores')
    ->schema([
        Components\Select::make('store')->label('Store')
            ->options(\App\Models\Store::all()->pluck('name', 'id')->toArray())
            ->preload()
            ->reactive()
            ->afterStateUpdated(function ($state, callable $set) {
                $set('departments', []);
            }),
        Components\Select::make('departments')->label('Departments')
            ->multiple()
            ->searchable(false)
            ->options(function (callable $get) {
                $store = \App\Models\Store::find($get('store'));
                if (empty($store)) {
                    return [];
                }
                return $store->departments->pluck('name', 'id');
            }),
    ])
    ->required()
    ->minItems(1)
    ->columns(2)
    ->afterStateHydrated(function ($state, callable $set) {
        $set('stores', [['store' => 1, 'departments' => [1, 2]]]);
    })

Probably because defaults only fill on the Create page and you're on the Edit page?

I have removed all traces of ->fill(...) from my page, but the repeater still loads with 0 items even though I specified ->defaultItems(3)

@bilogic  I have the same issue any updates? my repeater loads with 0 items and i have to press add to list item button to see the first item even though I specified ->defaultItems(1)  for it


[SP-6090] Backport of PDI-19320 - XML output with servlet with carte sh (9.2 Suite)

@smmribeiro
@bcostahitachivantara
@renato-s

:warning: Build finished in 33m 43s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:no_entry: Failed Tests
:cloud_with_lightning_and_rain: 4 test(s) failed:
org.pentaho.di.job.entries.ftpsget.FTPSConnectionTest.testEnforceProtPOnPut (click to expand)
org/apache/log4j/Logger

org.pentaho.di.job.entries.ftpsget.FTPSConnectionTest.testEnforceProtP (click to expand)
org/apache/log4j/Logger

org.pentaho.di.trans.steps.pentahoreporting.PentahoReportingOutputTest.testProcessRowWithoutUsingValuesFromFields (click to expand)
loader constraint violation in interface itable initialization: when resolving method "javax.swing.RepaintManager$1.addRepaintListener(Ljavax/swing/RepaintManager;Lsun/swing/SwingUtilities2$RepaintListener;)V" the class loader (instance of org/powermock/core/classloader/MockClassLoader) of the current class, javax/swing/RepaintManager$1, and the class loader (instance of <bootloader>) for interface sun/swing/SwingAccessor$RepaintManagerAccessor have different Class objects for the type javax/swing/RepaintManager used in the signature

com.pentaho.di.purge.PurgeUtilityLoggerTest.htmlLoggerTest (click to expand)
${result.errorDetails}

Tests run: 3912, Failures: 4, Skipped: 7    Test Results

:information_source:  This is an automatic message


All live tests failed in latest master for azure-mgmt-netapp

Package Name:
Package Version:
Operating System:
Python Version:

Describe the bug

To Reproduce
Steps to reproduce the behavior:

pytest -s sdk\netapp\azure-mgmt-netapp

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@changlong-liu thanks, looping in @nickzhums

confirmed with service team, it's due to subscription whitelist


Card sign form: Update to ACHv2

As per discussion with Stripe Support re: our longstanding issue where members with bank accounts configured are unable to self-update their payment methods, the solution is to update from ACHv1 to ACHv2.
(See email thread for further context)

Digging into this

So we have two problems at play here

We are continuing to accept payment using the old ACH API.  This means that as long as new members are signing up, they're going to have to use the solution we make to change their method.
Accounts with the old payment method need to be cleared before they can be changed in the Stripe portal.

My opinion is that we need to cut of the source first, by updating our integration.  That means updating the form to use the new API.  How do others feel about that priority?  The upside is that the API is supported in Stripe Elements, so we can actually simplify our integration that way.
https://stripe.com/docs/payments/payment-element

This is complete, opening a new issue for migrating existing customer objects


Guarding data posts against closing the tab

Consider this:
addToOutbox(importantEmail);

fetch(url, {
  method: 'POST',
  body: importantEmail
}).then(response => {
  if (!response.ok) throw Error(response.statusText);
  removeFromOutbox(importantEmail);
  showSuccessUI();
}).catch(function() {
  return navigator.serviceWorker.ready.then(reg => {
    return reg.sync.register({tag: 'outbox'});
  });
});

If sending an email fails, we request a sync and handle it later. However, if the tab/browser closes before the request completes, or the page navigates away, the request fails but we never get the chance to send that request.
Data isn't lost, but we can't send that email in the background. It becomes more attractive to do this:
addToOutbox(importantEmail);

navigator.serviceWorker.ready.then(reg => {
  return reg.sync.register({tag: 'outbox'})
});

fetch(url, {
  method: 'POST',
  body: importantEmail
}).then(response => {
  if (!response.ok) throw Error(response.statusText);
  removeFromOutbox(importantEmail);
  showSuccessUI();

  if (outboxEmpty) {
    navigator.serviceWorker.ready.then(reg => {
      return reg.sync.getRegistration('outbox');
    }).then(syncReg => syncReg.unregister());
  }
});

As in, we schedule a sync with every important POST, and unregister it if it succeeds. I'm worried there may be a race here where the sync event fires file the fetch is still being attempted, resulting in a double fetch.
I could schedule a sync event and do all of my outbox emptying there (not from the page at all), but I have no guarantee that it'll happen immediately, and communicating success/failure back to the page is a bit of a postMessage mess.
Is there anything we can do to improve this? Should we?
Couple of half-baked ideas:
reg.sync.register({
  tag: 'outbox',
  onlySyncIfThisPromiseFailsToFulfill: fetch(url, {
    method: 'POST',
    body: importantEmail
  }).then(response => {
    if (!response.ok) throw Error(response.statusText);
  })
});

Or:
reg.sync.register({
  tag: 'outbox',
  onlySyncIfNoPagesAreOpen: true
});

…which would prevent race conditions with the page.

One of the UIs I suggested for one-off was prompting the user when the application is closed to allow for synchronization when the user goes online next.
Basically you can request one-off anytime as it's also a healthy way to not have to ping the network every-so-often until you find you're online again. The UI only comes up when the application is terminated.

Are you saying sync events would never fire while the related service worker had clients?

No, I'm saying that as long as it has clients there's no need to display UI for one-off. Only at the point all clients go away.

Ahh ok. I don't think that solves the issue as you could still get the race between the fetch from the page & the one in the sync listener.

Maybe we should change the semantics of the one-off to fire as quickly as possible when the user is online. That way you can do everything through the one-off.

Yeah, although communicating success/failure back to the page isn't ideal. Maybe:
addToOutbox(importantEmail);

reg.sync.register({tag: 'outbox'}).then(syncReg => {
  syncReg.syncNow().then(val => {
    console.log(val); // "All done!"
  });
});

Over in the service worker:
self.addEventListener('sync', event => {
  event.waitUntil(
    fetch(url, {
      method: 'POST',
      body: getOutbox()
    }).then(r => r.json()).then(data => {
      if (!data.err) return "All done!";
      throw Error("BROKEN");
    })
  );
});

A little more detail: a one-off wouldn't fire as quickly as possible when the user is online, although .syncNow would trigger an immediate sync, and would resolve/reject with a structured clone of the resolved/rejected value.

A big problem here is that errors aren't structured-cloneable.

Given that a one-shot can only be registered when the page is open, why wouldn't it be fired right away?

@jkarlin it would, unless you're offline.

@jakearchibald
would the following setup take care of the race condition?

a shared outbox used by both the SW and the page
SW/Page should move the message they want to send from the outbox to their respective plates
SW/Page should try sending the message they took from the outbox
if sending fails, SW/Page should try to put the message back into the outbox (or empty their plate at the next opportunity)
if sending succeeds, SW/Page should clean their plate. SW might want to let the page knows that the message was delivered.

Hmm, there might be some instances where the page is gone AND has a message sitting on its plate though... Could the SW, after it's done emptying the outbox, check for the absence of clients and take care of the Page's plate without running into a race condition?

Hmm, there might be some instances where the page is gone AND has a message sitting on its plate though

Yeah, I'm nervous about anything that 'removes' something from an outbox before it's successfully sent.

So, I encountered this issue when adding background-sync to https://jakearchibald-gcm.appspot.com/chat/

User hits send, UI shows "sending"
I add the message to an outbox in IDB [code]
"sync" event - I pull the messages out of the outbox and send them [code]
On completion/failure, I postMessage to all clients, telling them what happened [code]
The page picks up the message and changes the UI accordingly [code]

I'm aware of all the horrible race conditions around my use of the outbox, which can be fixed by using IDB properly. However, the real painful bit is the messaging between SW and page.
I'm currently broadcasting to all clients after syncing, because I don't have a way to identify the client that initiated the sync. I need to do something on the page to check it's expecting the message it gets (I'm not doing that right now).
I'm still keen on something like this:
reg.sync.register({tag: 'outbox'}).then(syncReg => {
  return syncReg.done;
}).then(_ => {
  // sync is complete
});

Where syncReg.done fulfills once the sync successfully completes, and rejects if it somehow gives up entirely.
It'd be nice to be able to pass a value back, but that seems a lot more complicated.

+1, syncReg.done seems useful

I like that (obviously on one-shot syncs only; I'm not sure what the periodic equivalent would be).
It enables some interesting use cases -- it makes a 'background sync status page' easy to implement in Javascript, and makes it much easier for multiple client windows to display UI on pending syncs, even if they weren't the one to register it.

done is in the spec, closing as fixed.


Update aws-core, http-client-spi, ... to 2.17.120

Updates

software.amazon.awssdk:aws-core
software.amazon.awssdk:http-client-spi
software.amazon.awssdk:netty-nio-client

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #44.


Text imports mix up lines

Description
I've noticed that some lines (not very common, but some) are out of order from the original text file that was imported. I noticed this while listening along with an audiobook and certain things would be skipped then gone back to in a few moments. It's not an issue with the next file (see attachments).
To Reproduce
Steps to reproduce the behavior, e.g.:

Import using a text file
Notice that some lines are out of order

Screenshots
This is the text I confirmed with. Harry Potter a Fenixuv rad - J. K. Rowling.txt. An example of a line that is out of place is S mou drahou starou matičkou, ano which is on line 1889.
Here it is in Lute out of order:

Extra software info, if not already included in the Description:

OS (e.g., iOS, windows): Pop!_OS
Browser (e.g., chrome, safari): Chromium
How you've installed Lute (Docker, python, source): Python (v3)
Version: 3.0.0b11

Thanks, checked and fixed on v3.0.0.  This is a render-time problem, not import, the import works and doesn't mix up sentences.
Summary of the bug, fyi: at render time, the code parses the current text, and gets the paragraph numbers to write out.  The line paranums = unique([t.paragraph_number for t in tokens]) uses python's unique function, but that wasn't preserving the order.  Oddly it has never occurred for me till now!  With paranums = sorted(unique([t.paragraph_number for t in tokens])) the numbers are sorted.
I'll make a release soon as this needs to be resolved.  Thanks!

Fixed in 3.0.1, launched, thanks!


Undocumented routes property

server-options-spec doesn't say anything about the undocumented routes property here.

@reggi: as stated here, you can pass in any property of a react router's create configuration object.
routes is one of them. I

gotcha


Can sticky headers contains one or more clickable button?

Check this issue https://github.com/edubarr/header-decor/issues/38 for some more information on how to implement click events on headers. Check that ticket for more details since there is some code required, it all starts with:
decoration = new StickyHeaderDecoration(adapter); recyclerView.addOnItemTouchListener(new StickyHeadersTouchListener(recyclerView, decoration))


[Change Request] codeunit 7017 "Price List Management" procedure FindDuplicatePrices

Hi, could you please change the procedure FindDuplicatePrices as a global procedure?
procedure FindDuplicatePrices(PriceListHeader: Record "Price List Header"; var PriceListLine: Record "Price List Line"; SearchInside: Boolean; var DuplicatePriceLine: Record "Duplicate Price Line") Found: Boolean;
var
DuplicatePriceListLine: Record "Price List Line";
LineNo: Integer;
begin
DuplicatePriceLine.Reset();
DuplicatePriceLine.DeleteAll();
    if PriceListLine.FindSet() then
        repeat
            FindDuplicatePrice(
                PriceListLine, PriceListHeader."Allow Updating Defaults", SearchInside,
                DuplicatePriceLine, LineNo, DuplicatePriceListLine);
        until PriceListLine.Next() = 0;
    Found := LineNo > 0;
end;`

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11478.


post release create pull request action fails

Description
see https://github.com/whylabs/whylogs/actions/runs/3092683669/jobs/5004282226#step:7:511

still occuring: https://github.com/whylabs/whylogs/actions/runs/3138237949/jobs/5097439689#step:7:510

python/examples/integrations/flask_streaming/.dockerignore


Source docker-machine environment variables rather than hardcoding

The docker-machine IP can change if the machine is recreated. docker-machine env dev sources the current machine settings.
Signed-off-by: Frank Kotsianas<EMAIL_ADDRESS>

While I understand what you're doing there, I have a concern. This will only work if you have docker-machine running all the time, specifically at the time when your shell is started and Bash-it is loaded.
This code will not work when you start docker-machine on demand, without reloading your shell.
Could you explain how you use this - maybe this will clear things up. Do you have docker-machine running all the time, or do you start it on demand? If so, do you reload your shell settings after starting docker-machine?

Fair point. We updated the script to check that the machine is running before trying to export the environment variables.

Nice! It will still require you to run reload after starting docker-machine, if you don't have it running all the time.
I'll merge this nonetheless, looks like a good compromise to me.


[QAA-104][Playwright] Fix market test

✅ Checklist

[ ] npx changeset was attached.
[ ] Covered by automatic tests.
[ ] Impact of the changes:

...

📝 Description
Fix market test

❓ Context

JIRA or GitHub link:

🧐 Checklist for the PR Reviewers

The code aligns with the requirements described in the linked JIRA or GitHub issue.
The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
There are no undocumented trade-offs, technical debt, or maintainability issues.
The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
Any new dependencies have been justified and documented.
Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

/generate-screenshots

/generate-screenshots


🚀 - Range, InputRange add [margin] & [limit]

Which @taiga-ui/* package(s) are relevant/releated to the feature request?
kit
Description
Range
We should add new @Input()-properties for Range-component:

margin - the minimum distance between the thumbs.
See https://refreshless.com/nouislider/slider-options/#section-margin

limit -  the maximum distance between two thumbs.
See https://refreshless.com/nouislider/slider-options/#section-limit

InputRange
Should we just duplicates the same input properties ?
Maybe it is better to pass Range-component  inside InputRange ?
<tui-input-range>
    <input tuiTextfield />

    <tui-range [margin]="5" [limit]="30"></tui-range>
</tui-input-range>

(we need to discuss it and probably create the separate issue for InputRange)

Hi! I`ll take it


DryIoc.Microsoft.Hosting depends on DryIoc 3.0.2

Repro:

Create a new project and add DryIoc.dll v. 4.0.0 Dry.Microsoft.Hosting 1.0.0-preview-01
Add some code that uses it, i.e. var host = new HostBuilder().UseDryIoc(s=> new Container().WithDependencyInjectionAdapter(s))
Compile

Expected:
Compilation succeeds
Actual:
Compilation fails with:

error CS0012: The type 'IContainer' is defined in an assembly that is not referenced. You must add a reference to assembly 'DryIoc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'

Hi @jasper-d ,
Do you still need this extension?
Cause now you can you use:
var host = new HostBuilder()
    .UseServiceProviderFactory(new DryIocServiceProviderFactory());

DryIoc.Microsoft.Hosting was just a sugar on top of DryIocServiceProviderFactory - it is a one-liner to wrap it in UseDryIoc method.
I think, starting from the ASP .NET Core 3 UseServiceProviderFactory should be available for both Web and the general host builders.

Hi @dadhi,
you're absolutely right. Works like a charm with UseServiceProviderFactory  :)


Update manifests/e/Eugeny/Tabby/1.0.184/Eugeny.Tabby.locale.en-US.yaml

Fixes an issue where this package has multiple different monikers
Microsoft Reviewers: Open in CodeFlow

[Policy] Reset Labels


Long queue names cause AD realm join failures.

In what area(s)?

/area administration
/area ansible
/area autoscaling
/area configuration
/area cyclecloud
/area documentation
/area image
/area job-scheduling
/area monitoring
/area ood
/area remote-visualization
/area user-management

Expected Behavior

Long queue names should not affect node behavior, or long queue names should be rejected.
Actual Behavior

If queue names are long (e.g. hc44-low-mpi), the node hostname can be too long for AD and it gets truncated. This causes a realm join failure. MPI nodes make it worse because they add more characters to the hostname for the placement group.
This is documented here: https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/hostname-character-limit/m-p/1068231
Steps to Reproduce the Problem

Create a queue with a long name.
This bug shows up in journalctl on the failing node:
Nov 08 17:47:16 hc44-low-mpi-pg0-2 root[13879]: Domain join on hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: client using service: :1.77
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: holding daemon: :1.77
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Using 'r651.13881' operation for method 'Discover' invocation on 'org.freedesktop.realmd.Provider' interface
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Registered cancellable for operation 'r651.13881'
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Resolving: _ldap._tcp.hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Resolving: _ldap._tcp.hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Performing LDAP DSE lookup on: <IP_ADDRESS>
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Performing LDAP DSE lookup on: <IP_ADDRESS>
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Searching  for (objectClass=*)
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Got defaultNamingContext: DC=hpc,DC=azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Sending TCP Netlogon request
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Received TCP Netlogon response
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Successfully discovered: hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Successfully discovered: hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Using 'r651.13881' operation for method 'Join' invocation on 'org.freedesktop.realmd.KerberosMembership' interface
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: Registered cancellable for operation 'r651.13881'
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: holding daemon: current-invocation
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Required files: /usr/sbin/oddjobd, /usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd, /usr/bin/net
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Required files: /usr/sbin/oddjobd, /usr/libexec/oddjob/mkhomedir, /usr/sbin/sssd, /usr/bin/net

Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Joining using a truncated netbios name: HC44-LOW-MPI-PG
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * Joining using a truncated netbios name: HC44-LOW-MPI-PG

Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * LANG=C LOGNAME=root /usr/bin/net -s /var/cache/realmd/realmd-smb-conf.2X52U1 -U hpcadmin ads join hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]:  * LANG=C LOGNAME=root /usr/bin/net -s /var/cache/realmd/realmd-smb-conf.2X52U1 -U hpcadmin ads join hpc.azure
Nov 08 17:47:16 hc44-low-mpi-pg0-2 realmd[13501]: process started: 13886
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: Enter hpcadmin's password:connect_to_domain_password_server: unable to open the domain client session to machine ad.hpc.azure. Flags[0x00000000] Error was : NT_STATUS_NO_TRUST_SAM_ACCOUNT.
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: Enter hpcadmin's password:connect_to_domain_password_server: unable to open the domain client session to machine ad.hpc.azure. Flags[0x00000000] Error was : NT_STATUS_NO_TRUST_SAM_ACCOUNT.
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]:
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]:
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: Failed to join domain: failed to verify domain membership after joining: The SAM database on the Windows Server does not have a computer account for this workstation trust relationship.
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: Failed to join domain: failed to verify domain membership after joining: The SAM database on the Windows Server does not have a computer account for this workstation trust relationship.
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: process exited: 13886
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]:  ! Joining the domain hpc.azure failed
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]:  ! Joining the domain hpc.azure failed
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: released daemon: current-invocation
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: client gone away: :1.77
Nov 08 17:47:20 hc44-low-mpi-pg0-2 realmd[13501]: released daemon: :1.77

cc: @ltalirz

Thanks @matt-chan , look like Netbios is used under the cover. So queue names should be limited to 9 or 10 characters.

https://github.com/Azure/az-hop/pull/1353 now enforces a maximum length of 9 characters.
Note that this allows for suffixes of the form -pg1-1 (6 extra characters).
In queues with large numbers of cores (e.g. up to 100 placement groups with 100 VMs each), however, the maximum addition to the queue name is -pg100-100, i.e. another 10 characters.
This would limit queue length to 5 characters, which basically forces queue names to be non-intuitive  abbreviations.
The only real solution here is to move to a technology that can support node names beyond 15 characters (or define a mapping from a given queue name to a shorter node name prefix, if that is possible).

15 characters is enforce by NETBIOS and AD, so in order to find a way to extend this we have to understand if netbios can be avoided.
The limit should be 10 today as largeviz3d requires it.
In addition, limiting scaleset to 99 will save a character in the naming for large scale deployments. the -pgXXX is added by CC and I don't know exactly if the -pgXXX is really used or if it's only cosmetic. We need to ask the CC team.

The limit should be 10 today as largeviz3d requires it.

The schema currently has an exception for 'special' queues like largeviz3d (which makes sense as some of these may not require placement groups and thus require less stringent character limits)

the -pgXXX is added by CC and I don't know exactly if the -pgXXX is really used or if it's only cosmetic. We need to ask the CC team.

I see. As long as new jobs will still be placed on VMs within a placement group by default, I think exposing this placement group in the hostnames is usually more confusing to users than helpful.
It is very rare that someone needs to manually pin a new job to a specific subset of nodes within a placement group that has already been allocated.
Can you ask them please?

queue name is now limited by the schema


Sudden errors while trying to run znc (4 errors)

This is the error i get when I run znc from the /.znc/ folder. Anyone know what's wrong? No changes has been made, just a server reboot and this happens. Cheers!
[ ok ] Checking for list of available modules...
[ ok ] Opening config [/home/joey/.znc/configs/znc.conf]...
[ ** ] Config was saved from ZNC 1.6.3. It may or may not work with current ZNC 1.2
[ ok ] Loading global module [webadmin]... [/usr/lib/znc/webadmin.so]
[ ok ] Binding to port [5001]...
[ ** ] Unhandled lines in Listener config!
[ ** ] uriprefix = /
[ ** ] Unrecoverable config error.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/33475878-sudden-errors-while-trying-to-run-znc-4-errors?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).

Why are you using ZNC 1.2.x shouldn't you be using 1.6.x?

@wolfy1339 Thanks for reply. That's the strange thing. I downloaded and installed the newest version a month ago (been running stable on IRC). Even the config file says Version = 1.6.3 (?!).

How did you install 1.6.3?
You also have installed 1.2.
Check znc --version,
which znc is likely to return /usr/bin/znc, that's the version from your OS distribution, you should remove it to reduce the confusion.
Depending on how you installed 1.6.3, probably it's in /usr/local/bin/znc.


when cancellation goes wrong

Brief summary: I've heard a lot of people discuss hazards related to task cancellation -- I think this is because any await point is effectively a cancellation point, and people don't always write "cancellation-safe" code. I'd love to hear more concrete examples of where this happens.
Character: not sure!
Key points or morals (if known): not sure!

Part of this blog post feels (maybe) related:
https://kevinhoffman.medium.com/rust-async-and-the-terrible-horrible-no-good-very-bad-day-348ebc836274

Lesson III — If you drop (or allow to be dropped) the tokio runtime, any pending tasks are cancelled.

AsyncDrop would likely help with some of the pain of unexpected/external drops, I think.
For intentionally canceling futures and streams, it would be nice if something like like https://crates.io/crates/stop-token (or https://crates.io/crates/stopper, slightly different implementation of the same idea) were standardized

@jbr I think it would help to figure that out if we had as many concrete examples as we can. One thing I'd like to drill into a bit is the connection of cancellation and this, because we may not always be able to do async drop in cancellation.

Another relevant story, https://tomaka.medium.com/a-look-back-at-asynchronous-rust-d54d63934a1c:

async fn read_send(file: &mut File, channel: &mut Sender<...>) {
  loop {
    let data = read_next(file).await;
    let items = parse(&data);
    for item in items {
      channel.send(item).await;
    }
  }
}

Each await point in asynchronous code represents a moment when execution might be interrupted, and control given back to the user of this future. This user can, at their will, decide to drop the future at this point, stopping its execution altogether.

If the user calls the read_send function, then polls it until it reaches the second await point (sending on a channel), then destroys the read_send future, all the local variables (data, items, and item) are silently dropped. By doing so, the user will have extracted data from file, but without sending this data on channel. This data is simply lost.

I've written https://gist.github.com/Matthias247/ffc0f189742abf6aa41a226fe07398a8 2 years ago :-)

For intentionally canceling futures and streams, it would be really nice if something like https://crates.io/crates/stop-token were standardized

Agreed. I wanted to look into this, and think we could have a StopToken similar to the C++ one which is synchronously and asynchronously usable. But I lacked time of further looking into it, and am currently afraid we won't get it standardized since every async framework wants to have their own version (as it has happened with channels, mutexes, etc).

Hmm, I would really like to see these stories written up ...

There is also an old issue on futures about cancellation especially in the context of completion-based APIs: https://github.com/rust-lang/futures-rs/issues/1278 . That probably also contains some useful information.

After a great writing session about this issue, we unfortunately did not end up with a finished story, but we've come up with several observations which we think will lead to at least two status quo stories.
Issues around cancellation
Accidental cancellation
As @seanmonstar pointed out above, sometimes futures are dropped before they are polled to completion. If code is not written explicitly with this in mind, surprising results can occur.  Because each await point gives control back to the caller, the author of such code must keep in mind that code after an await point might not run. For example,
async fn push_event(&self) {
    let event = self.events.recv().await; // Control is given back to the runtime after this call
    self.events.push(event); // If the future returned from `push_event` is dropped early this line may never run
}

Premature dropping of futures is often given with examples of the select! macro (e.g., this example @tomaka), but this is not the only case where this can happen. Futures must be written in a pre-poll-ready drop-safe manner.
This is documented in several places, but may be hard to understand at first.
No standard way to perform cancellation of futures
Cancellation of tasks can be achieved in several ways:

Dropping futures: as discussed above, dropping a future means it no longer is driven forward to completion. Some issues with this:

This however has no impact on associated operations of that future (e.g., I/O operations the future has started) which remain blissfully unaware that the user wishes to cancel them.
A particular piece of code may wish to cancel a future without having ownership over it.

Explicit state: A future can keep track of its state as being either canceled or note and have some mechanism for flipping that state. For example, on creating the future, the user receives some sort of mechanism (usually a channel) for signaling to the future that it should flip its state from not-canceled to canceled.  Issues with this:

There is no standard way of doing this and so each future is left to implement this on their own in a bespoke way. This can get complicated when trying to signal to associated operations that the should be canceled. There are, however, some crates which try to offer generalized approaches like stop-token.

Cancellation must often be explicit
Even if a user wants to use Drop as a way to cancel an operation, this is often not possible. Some operations need to perform some async cleanup before being canceled. For instance, tokio's channel implementation offers an explicit close method to first close the channel from receiving further elements after which the user can drain any remaining elements that are in the queue. Because Drop is sync, there would be no way to do this.
Documentation on how to handle cancellation is sparse
The async book currently has an empty entry for this. Because cancellation is often modeled in a bespoke manner, it's hard to learn of one way to handle this.
The plan
With this in mind, we had two ideas for stories:

A user writes code where a future accidentally gets dropped early causing some code to not run which the user thought would run. This might be best for Alan as understanding this issue requires understanding how futures are actually run.
A user needs to model cancellation but they're unsure how to do it. We've not been able to come up with a good example of this that hits most of the points above. If you've run into this issue, please do reach out.

Thanks to @doc-jones @emmanuelantony2000 @zeenix, and @sdroege for a great session!

A related story was recently posted. https://gendignoux.com/blog/2021/04/08/rust-async-streams-futures-part2.html
The author @gendx might be able to share some more concrete examples.

We had a session today that addressed “accidental cancellation”. There should be a PR coming soon.

Hey 👋
Just opened a PR, I'd be happy to polish it 😊

Just opened a PR, I'd be happy to polish it 😊

Can you please link to the PR? Thanks.

Hey, I think it was #153, all good!


add lru cache

lru cache, copy from server repo. this will be needed to store sticky execution state.

Coverage decreased (-0.005%) to 69.501% when pulling 5a3c885fc8bb27bddcb6f8484b91baa1cc750323 on yiminc:add_lru_cache into fbf8546955c8e16c42a11be402309ed6e253b0ce on uber-go:master.

On a tangential note, should we create a cadence-utils library of sorts? We seem to have a bit of duplicate code in general, will be harder to maintain.


Set settings that aren't already present

The current version of setting() only edits settings already present in the config files. I discovered this while trying to set a read_only setting but it holds true in general. The version included sets appends settings if they are not already present in the config file. If this change is accepted it would have to be applied to all copies of the entrypoint script.
Peter

@pvanheus Thank you for this PR. You're right that we should support this case.
Perhaps I am misreading the code, but isn't the logic back-to-front in the implementation. You want to do the sed in the case that the grep succeeds and the echo otherwise.
A couple of minor quibbles on the code:

please use the full form of grep's -q flag for readability
please redirect grep's stdout to /dev/null so that nothing gets printed in the case where the setting is already present

@pvanheus Are you still interested in this change?

@pvanheus It sounds like you don't need this any more. I'm going to close this for now. Please reopen the PR and have a look at my comments above if are still interested in getting the change in.

@pvanheus I ran into the need to do this myself, so I have implemented it in c8dbffb3e8bf9e568aa12138bde26574167062b0. Hope that you find it useful.


i still think that rect2 no rotate with control is bug...

Godot version:
3.2 beta6
OS/device including version:
windows 10
Issue description:
control rotate 90,but global and locol rect2 is still 0 degree...
i think it is bug,if it be designed like this, it confuse me very much,
at least, rect2 Description in doc
Rect2 consists of a position, a size, and several utility functions. It is typically used for fast overlap tests.
so if our control can rotate, how can we text overlap...
Steps to reproduce:
Minimal reproduction project:
ReproductionProject.zip

Duplicate of https://github.com/godotengine/godot/issues/35043
As was explained in that issue. get_rect() returns a rect in local space. If you want to compare an object/point against it, you need to transform that point into the controls local space.

Duplicate of #35043
As was explained in that issue. get_rect() returns a rect in local space. If you want to compare an object/point against it, you need to transform that point into the controls local space.

sure，get_rect is local space，get_mouse_position is local space too，it donot work...

Duplicate of #35043
As was explained in that issue. get_rect() returns a rect in local space. If you want to compare an object/point against it, you need to transform that point into the controls local space.

sure，get_rect is local space，get_mouse_position is local space too，it donot work...same as global...

重复＃35043
正如这个问题进行了解释。get_rect()返回本地空间中的矩形。如果要比较一个对象/点，则需要将该点转换为控件的局部空间。

当然，get_rect是局部空间，get_mouse_position也是局部空间，它不起作用...与全局空间相同...

Duplicate of #35043
As was explained in that issue. get_rect() returns a rect in local space. If you want to compare an object/point against it, you need to transform that point into the controls local space.

sure，get_rect is local space，get_mouse_position is local space too，it donot work...same as global...

i used get_rect().has_point(get_local_mouse_position),it is norect

Duplicate of #35043
As was explained in that issue. get_rect() returns a rect in local space. If you want to compare an object/point against it, you need to transform that point into the controls local space.

sure，get_rect is local space，get_mouse_position is local space too，it donot work...same as global...

ReproductionProject.zip


How to separate HttpRequests from RestClient

I would like to move the requests (e.g.)
  @GET("/tasks")
  Future<List<Task>> getTasks();

Out of the RestClient, into another .dart file but couldn' find any example as to how to proceed. Could you please indicate how? I have no structure if I have to put 400 httpRequests into the same file.

You can move it in any dart file. but you have to put there function in a class with annotation @RestApi

This is what I am facing. Did you get any solution?

You can put the function in any dart file.  RestClient is just an example.


Update for PEP8

This is a set of commits that adds PEP8 (They python style rules) into the travis build and lets you test for  compliance.
To be complete, I also fixed everything to be compliant.

Thanks @irjudson, this is really helpful!

No problem.
I'll refactor my CLI to use this module -- then get a blog post out about
the change.
That seems like it should be helpful for folks playing with the APIs.
--Ivan
Ivan R. Judson
irjudson.org
(425) 679-1375
On Mon, Oct 12, 2015 at 12:22 PM, Scott Southwood<EMAIL_ADDRESS>wrote:

Thanks @irjudson https://github.com/irjudson, this is really helpful!
—
Reply to this email directly or view it on GitHub
https://github.com/scsouthw/project-oxford-python/pull/2#issuecomment-147496377
.


Link to Errata, Rotation and MWL should probably point to NISEI.NET and not FFG

Check for example this deck that uses a (NISEI) rotated Terminal Directive card:
https://netrunnerdb.com/en/decklist/53942/-612-welcome-to-the-doublemeat-palace
In the top there is a warning that say that

This decklist is not legal for tournament play currently, due to Card Errata, Rotation or the Most Wanted List.

The links goes to FFG and not NISEI

One place where this shows up...


[WIP] [DO NOT MERGE] Adding support of downloading latest container image while instance create/purge

Hey @zed-rishabh -- just as a matter of general policy -- can you star adding descriptions to the PRs you're submitting?
Lets start with this one -- what is it you're trying to do here?

Hey @zed-rishabh -- just as a matter of general policy -- can you star adding descriptions to the PRs you're submitting?
Lets start with this one -- what is it you're trying to do here?

@rvs I will start following it from now on. Thanks!

But are you doing this so we can deploy two apps using an imageID referencing e.g. nginx:latest, where the first one resolves that to sha1 and the second (starting a minute later) resolves it to sha2, and we want the download and verification of those two to not interfere with eachother?

Yes, correct.

If so do we have a way to test this?

I created an image and pushed it to the docker hub account.
MAINTAINER<EMAIL_ADDRESS>RUN mkdir /myvol1
VOLUME /myvol1
RUN mkdir /myvol2
VOLUME /myvol2```
I keep on changing the number of volumes in an image for my development testing. With the help of it, I am able to create two versions of an image at the time of instance creation and purging.
The testing bundle is on acme enterprise with name ```alpine-with-two-vol-preserve```

> Also, I see you are removing some of the sha256 updates which aren't needed any more. Did you find and remove all of them from zedmanager and volumemgr?

Not yet. When I was going through the volumemgr code so thought to clean it up. But I will move this clean up in a separate PR once I am done with changes.

> What testing remains before this can be pulled?

Currently, I am blocked and trying to resolve the issue. After deploying an instance, the device is going in a continously reboot loop.
https://github.com/lf-edge/eve/blob/f606bd9617b586265a63f4937e5895b10ebc99f9/pkg/pillar/cmd/verifier/handlers.go#L55
The device is hitting fatal error in the verifier create.

Some nits and a question:
Does the code to handle the purge in zedmanager always redo the resolution? You didn't change anything there in this PR.

zedmanager is creating new storage status for the purged disk so as a result, the resolution is always happening.

Once done please squash into one commit.

Sure, I will do.

Looks very good.

Thanks. :)


Minimum VRAM (CUDA out of memory)

Thank you for releasing the code and I tried it immediately. I managed to get the code running by downloading the pretrained weights. Otherwise, if the code tries to load from huggingface, it cannot find mvdiffusion.models_unclip.unet_mv2d_condition.
The next problem that I encounter is CUDA OOM. I am using a NVIDIA GeForce RTX 4090 GPU with 24G VRAM. First, it reports OOM at "diffusers/models/autoencoders/autoencoder_kl.py", line 260, in encode: h = self.encoder(x). After setting PYTORCH_CUDA_ALLOC_CONF to a smaller number, such as  PYTORCH_CUDA_ALLOC_CONF=max_split_size_mb:512, the code can proceed to  "diffusers/models/autoencoders/autoencoder_kl.py", line 275, in _decode: dec = self.decoder(z).  With error:
torch.cuda.OutOfMemoryError: CUDA out of memory. Tried to allocate 7.88 GiB. GPU 0 has a total capacty of 23.63 GiB of which 4.48 GiB is free. Process 2188 has 390.70 MiB memory in use. Including non-PyTorch memory, this process has 17.27 GiB memory in use. Of the allocated memory 16.37 GiB is allocated by PyTorch, and 149.60 MiB is reserved by PyTorch but unallocated.
This time the memory gap is obviously large: 7.88GB vs. 4.48GB. Therefore, I need to ask what is the minimum VRAM required for PSHuman. Thank you very much for your assistance.

The current model is trained at a resolution of 768, requiring over 40GB of VRAM. We are considering training a new model at a resolution of 512, which would allow it to run on an RTX 4090.

Thank you. I managed to get the code working on a A6000.


Update license file for 0.9.0GA and update pom with release dependenies

Verified:

License file reflects all the tier 1 dependencies
Name of artifact in license file
pom file

Need to add a developer in the pom file, otherwise sonatype push will fail.


AnimesUp

Source name
Animesup
Source link
https://animesup.biz/
Language
Portuguese
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist on the website extensions list or the app.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Closed as the website has died. If it ever comes back, please open up a new issue.


Moved C++ headers to minio-cpp subdirectory

Use #include <minio-cpp/header.h> to include minio-cpp now
Header files have consistent guards that don't start with _
Added a SPDX license identifier to each source and header file

@balamurugana Can you review again?
I have changed minio-cpp to miniocpp as required although I think it's ugly...


ENH: Add typehints for itk types to extras

Support many basic itk types and add more type annotations for functions
in the extras module.
Use itk_types and complex_ to avoid conflicts with the types and complex
standard library module and builtin respectively.

PR Checklist

[ ] No API changes were made (or the changes have been approved)
[ ] No major design changes were made (or the changes have been approved)
[ ] Added test (or behavior not changed)
[ ] Updated API documentation (or API not changed)
[ ] Added license to new files (if any)
[ ] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
[ ] Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for
further development details if necessary.

I am missing something big picture I think.  If I want to annotate the type of a parameter as str, I'd use
def function(my_parameter: str):

rather than
def function(my_parameter: 'str'):

but the function definition changes in this pull request are like the latter.

Strings are used to avoid circular dependencies and expensive imports. See:
https://www.python.org/dev/peps/pep-0484/#forward-references
https://www.python.org/dev/peps/pep-0563/
More recent versions of Python always use strings for type hints internally for performance. After we drop support for Python 3.6 (ITK 5.3) and add the required __future__ import, we can use the syntax where they do not look like strings anymore:
https://www.python.org/dev/peps/pep-0563/


Create Mock of Remote Control API

A Web API stub that returns Ok()

Reviewed by both me and @WrexBG , if versioning is not necessary it is ready for merge @mirodmarinov


Problem on GVRSceneObject.attachEyePointeeHolder(GVRMeshEyePointee eyePointee)

On gvreyepickingsample  all the objects that use method attachBoundingBoxEyePointee are not getting selected, the other objects that use method attachDefaultEyePointee the selection works fine.

This might be fixed by pull request https://github.com/Samsung/GearVRf/pull/112.

@DanielNogueiraAndroid is this fixed?

Yes, it is fixed. Thank you


Input Field Unwanted Boder Appered

Whenever the Input field is in focus, a border appears apart from the variant border style. is there any way to remove or disable it if it is present intentionally as a design? otherwise, if it's a  bug please fix it as soon as possible
by the way, I am using the latest version
  "dependencies": {
    "@material-tailwind/react": "^1.0.3",
  }

and my tailwind.config.js file looks like
const withMT = require("@material-tailwind/react/utils/withMT");

module.exports = withMT({
  content: ["./src/**/*.{js,jsx,ts,tsx}"],

  theme: { ...  },
  plugins: [],
  });

Hi @Md-Sarfaraz
Thanks for using @material-tailwind/react, we noticed this issue and we will fix it for the next update.
All the best,
Sajad

I saw the same behavior in Safari but not in Chrome. I believe it can be removed with outline:none.

Hi @Md-Sarfaraz, @smcenlly,
I've updated the @material-tailwind/react and now this issue is fixed for the following components:

Input
Select
Textarea

All the best,
Sajad


React-native: Error running the example

Hello! I'm trying the example app for react-native. When I run yarn start within the WhipWhepDemo I see all metro stuff, and when loading the app via expo go I see this:
Android Bundled 8712ms node_modules/expo-router/entry.js (1272 modules)
Failed to open the React Native DevTools.
Error: Runtime.evaluate
 (NOBRIDGE) LOG  Bridgeless mode is enabled
 INFO
 💡 JavaScript logs will be removed from Metro in React Native 0.77! Please use React Native DevTools as your default tool. Tip: Type j in the terminal to open (requires Google Chrome or Microsoft Edge).
 (NOBRIDGE) WARN  The native view manager required by name (ReactNativeMobileWhepClientViewModule) from NativeViewManagerAdapter isn't exported by expo-modules-core. Views of this type may not render correctly. Exported view managers: [ExpoBlurView]. [Component Stack]
 (NOBRIDGE) ERROR  Error: Cannot find native module 'ReactNativeMobileWhepClient' [Component Stack]
 (NOBRIDGE) WARN  Route "./(tabs)/index.tsx" is missing the required default export. Ensure a React component is exported as default. [Component Stack]
 (NOBRIDGE) ERROR  Error: Cannot find native module 'ReactNativeMobileWhepClient' [Component Stack]
 (NOBRIDGE) WARN  Route "./(tabs)/whep.tsx" is missing the required default export. Ensure a React component is exported as default. [Component Stack]
 (NOBRIDGE) ERROR  Error: Cannot find native module 'ReactNativeMobileWhepClient' [Component Stack]
 (NOBRIDGE) WARN  Route "./(tabs)/whip.tsx" is missing the required default export. Ensure a React component is exported as default. [Component Stack]

I also tried to use the code in the PR #69 but have the same issue. Any thoughts? Thanks in advance!!!

Hi! You cannot set up the example project with Expo Go; you need to use a development build, as this library relies on custom native code.

Thanks!!!


Add AnnotationTarget.ANNOTATION_CLASS target

If the support for AnnotationTarget.ANNOTATION_CLASS is added to @Dowel targets, it would be possible to define a tailored annotation like the following:
@Dowel(
    count = 2,
)
annotation class MyAnnotation

Hey, @mohsen-biglari!
Thank you for raising this request.

I want to understand your requirement a little deeper.
@Dowel annotation only offers one single configurable value (count). Creating a tailored annotation for configuring one single value seems a little unnecessary, isn't it?
What exactly is the benefit that you see is gonna come out of this?
Please shed some light on how this might improve you DevEx, thank you.

My requirement at the time was being able to change the default value of count globally. I also can see the number of configurable parameters growing. It will also enable combining Dowel with other related annotations.


⚠ Fortnite has degraded performance

In d125b5f, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1632 ms

Resolved: Fortnite performance has improved in 06785a1.


Ability to override specific rules

Bug Report

TSLint version: 5.10.0
TypeScript version: 2.9.2
Running TSLint via: (pick one)  VSCode / VisualStudio

TypeScript code being linted
export interface TSInterface {
    id: number;
    name: string;
}

with tslint.json configuration:
{
    "extends": [
        "tslint:recommended"
    ],
    "jsRules": {},
    "rules": {
        "interface-name": [
            true,
            "never-prefix"
        ]
    },
    "rulesDirectory": []
}

Actual behavior
This change breaks TSLint completely. If I add this, suddenly the rules start acting out. I need to start manually writing rules.
For instance, this makes trailing-comma activate and if I don't write it in the new tslint.json, it just keeps showing errors on code that wasn't flagged as such before. Trying to override a rule makes some rules go haywire?
After writing the new trailing-comma rule, then alphabetical order activates, after I fix that something else and it just keeps going and going.
Expected behavior
I want to be able to write OVERRIDES for certain rules, not write everything from scratch.
It will take me a week to write everything again, when the only thing I want to change is the interface-name rule.
I don't care about downloading some presets because I want to change a single rule. This should not have to be so complicated.
edit: this might also be an issue with TSLint extension for VS Code, but for now I would like to show you what I had to write for my project to work.
{
    "extends": [
        "tslint:recommended"
    ],
    "jsRules": {},
    "rules": {
        "interface-name": false,
        "trailing-comma": false,
        "ordered-imports": false,
        "member-ordering": false,
        "object-literal-sort-keys": false,
        "array-type": [
            true,
            "generic"
        ],
        "max-classes-per-file": false,
        "object-literal-shorthand": false
    },
    "rulesDirectory": []
}

I'm pretty sure this works. Can you confirm that this still isn't working for you?

Nope, can't get it to work. It seems to "break" if I add a rule here.
I saw a lot of tutorials there about this, but this doesn't work for me, nor my colleagues at work.
We have several projects set up and depending on the project, more or less of these settings had to be overriden. For my project, only these ones had to be included. I don't really understand what's happening behind it but it's strange.
I believe it doesn't break if I add a rule that is "safe". For instance, that array-type wasn't broken, I just changed it.

I'm also unable to override rules.
My config looks like:
{
  "extends": ["tslint:recommended", "tslint-react"],

  "rules": {
    // Don't require prefix interface with 'I''
    "interface-name": false,

    // Use: '
    "quotemark": [true, "single", "avoid-escape"]
  }
}

When I run:
tslint -v
5.11.0

tslint -p .

....  a lot of errors like:
/home/node/src/registerServiceWorker.js[114, 7]: ' should be "

When I comment out the extends: line, it works as expected.

Heh, nevermind, I un-tangled my snaggle.
I had 1 .js file in my project that was at the bottom of the output:
ERROR: src/types/SurveySummary.ts[1, 34]: " should be '
ERROR: src/registerServiceWorker.js[114, 7]: ' should be "

So that was the error message I read, which didn't seem to be respecting my override.  I didn't notice the other messages in .ts files were correct.
I had one .js file in the project, the registerServiceWorker.js which used double quotes (when I wanted single quotes).
Adding a js rule for it made all files fail as expected:
  "jsRules": {
    "quotemark": [true, "single", "avoid-escape"]
  }

Override appears to be working!

💀 It's time! 💀
TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱
If you'd like to see this change implemented, you have two choices:

Recommended: Check if this is available in ESLint + typescript-eslint ✅
Not Recommended: Fork TSLint locally 🤷♂

👋 It was a pleasure open sourcing with you!
If you believe this message was posted here in error, please comment so we can re-open the issue!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


rviz frame rate  drops rapidly and display slowly

Hi，We use rviz with ubuntu 16.04 + virtualbox to run rviz by command 'roslaunch loam_horizon loam_livox_horizon.launch', rviz started displaying at 30fps, and then start dropped slowly to 1fps and display slowly. If you click reset, the frame rate will be restored to 30fps. We use rosbag to run with 'rosbag play 2020_parking_lot.bag', the issue also reproduce too.
How can I increase the frame rate of the display? Is there any parameter settings for rviz? How can we resolve this issue?
Thanks

The core problem is that you are trying to run rviz from a VM. Probably, the VM cannot grant direct access to the GPU, making any rendering slow. The more data points need to be visualized (I guess your bag publishes a point cloud?) the slower it gets.

Yes, the bag publishes is a point cloud. Thanks


Refactoring

Move status/request methods to each PermissionConfig
Not possible to add them to the protocol. E.g: HealthKit requires parameters

How to refactor the request methods to each Permission ?
Solution 1: request() has closure parameters for each status
public func request(closure1, closure2, closure3) {
        switch status() {
        case .Unknown:
            /// some code
           closure1()
        case .Unauthorized:
           closure2()
        case .Disabled:
           closure3()
        case .Authorized:
            break
        }
    }

A bit messy ?
Solution 2: Use one closure
public func request(closure1) {
       let currentStatus = status()
        switch currentStatus {
        case .Unknown:
            /// some code
           closure1(currentStatus)
        default:
            closure1(currentStatus)
        }
    }

PermissionScope will usually ignore .Authorized status and show alerts for the other cases.

Why addPermission has to fail I input same Permission more than one time? Why not just ignore the append action, or update the messasge? I'm coding a ViewControl where I check for PhotoPermission on every image tap. User can change a image never, ou do this 50 time just for fun. I created a check for statusPhoto before addPermission, but I think it's not necessary.

Valid point...I guess that failing is the simplest solution to prevent mistakes. Updating the message could be another way.

It's very clear what happens when you add the same permission twice right now. In any other case, it's unclear. I prefer the clarity.
@shonorio I suspect you'll have more success showing the permission once when users load this particular screen. Or, if you wanted to show it every tap, create it as a property on load and just .show() every time a tap occurs. No need to create/add the permission config every time a tap occurs.

@nickoneill you have your reasons, It's was just one suggestion. You could use throws on 'addPermission' if you want be so strict, I can code this if ok for you.

Thanks for the offer @shonorio, the API for adding a permission config is good for now. I'll keep it in mind for a future release.


Add labels sandwich option to the editor

Based on my tests, labels work great 90% of the cases.
The cases were they don't work that good is where having maps with just a few features (99% points) so the label itself covers the points... So based on this I'd propose to...

We keep layers on top by default in our basemaps (Positron and Dark Matter) on those maps with more than XX(30?) points.
We keep the no_labels option in the basemap selector.
We add a new option labels_below on the basemaps selector.

If we play, we play :P
cc/ @andrewxhill @jatorre @javisantana

pretty exciting man

Good with me.

On Jun 23, 2015, at 12:36 PM, Andrew W. Hill<EMAIL_ADDRESS>wrote:
pretty exciting man
—
Reply to this email directly or view it on GitHub https://github.com/CartoDB/cartodb/issues/4148#issuecomment-114565680.

Sumarizing after talking to @javisantana
In the basemaps selector we will have the same plus

Positron / Dark Matter_labels_ontop
Positron / Dark Matter_light_nolabels
Postron / Dark Matter default.

So only new maps will have the labels_ontop option selected by default following the rules explained before.

And, the same with stamen tonner

Have you guys discussed how maps with a basemap with labels on top + torque layer should be rendered? Should labels be displayed on top of the torque layer in this case?

in that case rendering should be done client side :)

I've updated the description of this issue with some of the work that needs to be done.
@saleiva we need some icons/thumbnails for these basemaps.

Adding @mariodelvalle to the topic. Awesome.
@mariodelvalle what about adding an small letter to the already existing thumbnails?

:+1: I've moved the tasks here.

Hi guys today I'm going to do it.
I have a doubt. Do thumbnails for basemaps of Stamen are the same as for CartoDB?

@mariodelvalle. They are different:

@saleiva I'm not sure what combinations are we going to have there. We provide the following Stamen basemaps:

Toner
Toner Background
Toner Lite
Toner Lines
Toner Hybrid
Watercolor

Toner also have a only labels layer, so we can add toner background + toner labels for that option :)

Closed by #4286.


Implement actor sketch

Fixes https://github.com/penumbra-zone/tower-actor/issues/1
Modeling the errors in this crate proved to be a bit trickier than I expected. The original code uses anyhow + Box<dyn Error + Send + Sync + 'static> to erase all error information but this didn't feel like the right approach for a library. I ended up going with sled's approach of returning a Result<Result<S, E>, ActorError> to capture the difference between unrecoverable queue errors and theoretically recoverable consumer errors. This also required me to make the actual ActorFuture itself an enum, to capture the case where the queue was closed between poll_ready() and call(). Curious to hear what y'all think :)
TODO:

[x] Figure out good tests for each of the error conditions
[x] Double check that exports work correctly.
[ ] Get a pass from the penumbra dev team
[ ] Document the library!

The error condition referenced above, which required the actor future to become an enum, turned out to be impossible. The documentation of PollSender::close() guarantees that you can still send on a queue that has been dropped / .closed() / panicked until all of it's permits have been used up. As such, I was able to simplify the error handling significantly and retain the design as shown in the sketch. I added a couple tests for some common cases that I could think of, honestly there's not that much actual code being executed here. Most of the effort has been in setting up the types / interfaces.

Added some compile flags to ensure that projects which include tower_actor but don't use tokio_unstable get a useful error message. Also, made sure that all of the re-exports look nice.

On the error handling front, the reason to prefer a boxed error rather than nesting multiple concrete error type is that it's the only practical way to achieve composability: if you have a single Result<Rsp, BoxError>, the caller code doesn't need to know the details of the whole layer stack, but they can still use downcasting to handle specific error types if they want. By contrast, nested error types reify the layer stack in the response type, so that changing it later (eg rearranging the order of layers) breaks caller code.

Changes implemented!

While reviewing the code, I also noticed that the type of the actor constructor callback was a little funny, in the sketch it returns a Result<(), MessageErrorType>, but the join handle carrying that return is immediately dropped in the constructors. I've switched it to returning the unit type to more clearly express this.
That said, I think it could be cool if the Actor was itself a future that could be .awaitto get at that return type. But to do that I think we'd need to stuff some types in somewhere to express 'what is this actor's result and error' and then we'd probably have to make an 'actor reference' that can be cloned around. Not too hard, but a big change from the existing API.

Ah, yeah. I think the writeup I did was unclear. The idea behind having the actor future return an error is so that at some point, we can extend the implementation to have a shared "error slot" (like in the Buffer implementation) like Arc<Mutex<Option>> or something, then

wrap the actor future in a shim that checks if it exited with an error and sets the error slot
hook the poll_ready implementation to check the error slot and fail the Service if the Actor failed (IIRC there may be some complexity here about needing to clone the error? maybe it has to be Option<Arc> or something so that multiple Services can share the internal error?)

I think we want the future the user passed in to resolve to a Result, even if we currently discard the error, so that later, we can improve the implementation to handle errors better without having to change the external API.
For now I think it's fine to discard the error as an implementation shortcoming, and plan to fix it up later.

Ahhh, I see. I did read the note about that but I didn’t quite put all the pieces together. I’ll look into the buffer stuff and maybe add an error slot implementation later. Thanks for the context :D

Looked up the buffer shim implementation, and it seemed like more effort than this Sunday is calling for. Restored the results as part of a planned future expansion and hopefully this should be good to go now :)


Lodash iterators break when adding a "length" attribute

I was seeing strange issues where many methods on the Model class were not working correctly.  As minimal example:
class Test extends Model {
  defaults() {
    return { length: 0 };
  }
  validation() {
    return { length: positive };
  }
}

test = new Test();
// test.attributes is an empty object
// test.validate() is true

Looking into it more, I found that lodash iterators use the presence of the length attribute to determine if an object is an array or not.  This causes all objects passed into lodash to be treated as an array.
I image I could override the rest calls to rename these properties coming from the server, but I'm wondering if there is an officially sanctioned way of dealing with reserved names, or if this is a problem that has not been considered.

@jbeezley this is a problem that hasn't been considered exactly. There are some reserved names that would clash with internal naming, but the length interaction with lodash hasn't come up before, and it was only a matter of time until it did. We'll need to take a closer look at a proper solution here and write some tests to get around it. We may need to avoid lodash entirely?

I ended up fixing it in the constructor like this
class Test extends Model {
  constructor(attributes, ...args) {
    if (attributes && _.has(attributes, 'length')) {
      attributes.length_ = attributes.length;
      delete attributes.length;
    }
    super(attributes, ...args);
  }
}

This allows it to work with the fetch method on the Collection class, which is all I needed.
I don't think avoiding lodash will solve anything.  There will always be property collisions when using bare objects.  This one happens to cause particularly weird behavior.  I would suggest to throw an error or warning when the attributes argument is detected as an array.
Ideally, there would be some sort of escape hatch available when the REST API contains reserved keys.  Perhaps something like
class Model {
  rename() {
    return { length_: 'length' };
  }
}

where it would automagically rename the attributes when passing to and from the server.

I think the only solution here is an accessor object for the attributes, much like we use $ for saved attributes. For example: model._.length or model.$length or something. This would be a massive BC break though, and would make things like collection.filter({length: 5}) impossible because the accessor on the base object won't be there. It's a balance between a nice API and a flexible architecture.
However, I don't think we necessarily need to throw the baby out with the bathwater. So far, it seems that length is the only attribute causing a real problem here. We can prefix all internal fields easily, but we can't expect anyone to change their responses to work with the library. For that reason, the scope of this issue is to resolve issues around length only.
There is a lot on the topic in this Underscore issue thread from 2015: https://github.com/jashkenas/underscore/issues/1590
What we need to do here is write some failing tests where length is an attribute and is set and accessed as expected. We'll need to document a warning that using length as an attribute name will break iteration of the model if you use functions like _.each (the key will be undefined).
That should be sufficient for now.
As an aside, I'm contemplating changing the saved shortcut from .$. to just a $ prefix (leaving the former in but deprecating for the time being. For example, model.name and model.$name, where the first would be active state and the second would be saved state. 🤔


refactor(modeling): use jscad plane normal in quickhull

Removes a duplicate implementation of getPlaneNormal from quick hull, in favor of jscad plane.fromPoints.
I just wanted to make quickhull a little bit more consistent with the rest of jscad.
I checked carefully that the result is exactly the same.
All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Does your submission pass tests?

Side note: I checked the quickhull repo for any changes or bug fixes since it was copied to jscad. Good news: there have not been any relevant changes upstream :heavy_check_mark:


feat: [CDS-76490]: Update provision-infra-dynamically-with-terraform.md

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Error: failed to create discovery service: failed to create CA: failed to create an istiod CA: failed to create CA KeyCertBundle (cannot verify the cert with the provided root chain and cert pool with error: x509:

Istio: 1.18.2
K8s: 1.24.
I am creating cacert with my private certificates.

Please provide the full logs, this is not enough info


Simplify the logics preparing snapshots for containerd

Right now, apart from making room for snapshot, snapshotter is also processing the blobs by converting or inspecting it. In the future, we may have more processing logic like them. So simplify and refactor related code for future work

Codecov Report
Patch coverage has no change and project coverage change: -0.03 :warning:

Comparison is base (889ef1f) 29.75% compared to head (600f8b1) 29.72%.

:exclamation: Current head 600f8b1 differs from pull request most recent head b5be142. Consider uploading reports for the commit b5be142 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #423      +/-   ##
==========================================
- Coverage   29.75%   29.72%   -0.03%
==========================================
  Files          39       39
  Lines        4084     4088       +4
==========================================
  Hits         1215     1215
- Misses       2711     2715       +4
  Partials      158      158

Impacted Files
Coverage Δ

pkg/stargz/resolver.go
26.31% <0.00%> (-0.72%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Docker container?

Would there be any way to deploy the build in a docker container since you're using new modern build methods?

Are you talking about the Blazor app? I wouldn't see why not. Would have to punch a hole in the container firewall to allow access to the user admin screen

I guess.. I don't know much about Blazor but I did find this.  For the admin page, maybe the app could generate a token that would be displayed in the docker log file (a bit like codeserver does) and then you could use that token to login?
https://chrissainty.com/containerising-blazor-applications-with-docker-containerising-a-blazor-server-app/

PresenceLight now supports running in docker and docker-compose. More info in Worker readme


docs: update deploy docs according to 1.5.4 changes

docs: update deploy docs according to 1.5.4 changes

Change logs

Describe your change clearly, including what problem is being solved or what document is being added or updated.

Contributor's checklist
Here are some reminders before you submit your pull request:

Make sure that your Pull Request has a clear title and commit message. You can take the Git commit template as a reference.
Sign the Contributor License Agreement as prompted for your first-time contribution (One-time setup).
Learn the code contribution and doc contribution guides for better collaboration.
Make sure that your changes deployment preview is successful.
List your communications in the GitHub Issues or Discussions (if has or needed).
Feel free to ask for the @cloudberrydb/doc team or other people to help review and approve.

Hi @TomShawn Thanks for your work! There may be some changes and improvements in the installation workflow. Will review your PR ASAP.


Styling the simplebar doesn't work with angular

I implemented the simplebar in angular using this code:
<ngx-simplebar [options]="options" >
    <div *ngFor="let number of numbers">ngx-simplebar</div>
  </ngx-simplebar>

I tried to change the color following the documentation:
.simplebar-scrollbar::before {
    background-color: red !important;
}

But it didn't work, is changing the color possible with angular ?
Edit
Moved the code to the global styles.css and it worked

@Latifaa17 Angular components have style encapsulation turned on by default.
When you need to change styles of child components you'd either need to turn off view encapsulation on your component or use piercing in css via ::ng-deep.


Adjustment to Iconography

Request:
There needs to be better correspondence between the icons and what they symbolize. For example, no one understood why a book represented community support.
Feature Description:
We will replace existing SVG icons with similar icons provided by E2A. We will not be developing additional icons.

Note best practice icons are managed in the locale file. Change the file name there (icon: [filename]), then add to spritemap.svg

[ ] Get icons from E2A
[ ] Put icons in place

@ewilliams3794 - just flagging we need some icons for this.

@jayperryworks - I've updated this with the icons.


Migrate all concrete/tools/permissions scripts into the routing/controller/view system

Fix #8956

In order to rewrite the permissions/categories tools I'd need https://github.com/concrete5/concrete5/pull/9056 to be merged

This PR is almost ready: the only remaining stuff to be fixed are the "tool" hacks for board and calendar.
But I'd need an answer for https://github.com/concrete5/concrete5/pull/8313#pullrequestreview-494462857 before proceeding.

This PR is now ready for review.

Sorry for the delay... can you fix the conflicts on this? I'll review again quickly this time, I promise

can you fix the conflicts on this?

Done. The two conflicting files (concrete/tools/pages/permissions.php and concrete/tools/pages/permissions_access.php) were both changed in this PR (see 87e23e1f4577c876f0d315b751e972fdf2ee1815) and dropped in #9049 (see 956aeadc2a865c601173dec86e91a3aa9754fb7d and 09339c0a70dcddc7126cd8a32fe529f0fcca2afa). I simply kept them deleted.

I rebased this PR to the very recent develop version so that tests should not fail now.

🎉

I've done a lot of testing on this. Probably can't catch everything, but we're going to be doing more exhaustive v9 testing over the next week. But no reason to delay this any further


Restore libtool with disable-shared option (again).

This patch was reverted because mathicgb was not compiling.  However, I
believe this is because the memtailor submodule in M2 was not up-to-date.
(See comments at [1].)
If this pull request is accepted, then I will prepare a new version of [1]
which also updates the memtailor submodule.
[1] https://github.com/Macaulay2/M2/pull/343

Sounds good.  Just submitted the memtailor pull request (https://github.com/Macaulay2/memtailor/pull/3).


TGP-1918: Translate reviewReason values in router

if we don't need to translate this for CreateOrUpdateRecordResponse.scala then it looks good to me


How to use The feature-vs-time view (Time vs. Amplitude)?

I'm reading this for a while but it seems documentation lacks some information.

Let me ask a few questions about the window.

What is the red rectangle for? I initially thought that this is to be dragged so that the user can set a threshold for splitting. However, splitting actually adds another polygon. If they are both for splitting purpose, it would be nice to be able to select one of them.
The documentation ways "with background features in gray", but what exactly are these gray dots? When I select different clusters, the gray dots also seem to change, suggesting that they are not randomly chosen.
When the black dots are intermingled with gray ones, it appears that the isolation of the select cluster is not great. Is this generally the case?

I understand the you left JRClust project already, but the documentation only shows the definition of each window for manual curation. It does not tell us how the manual curation goes typically. It would be nice to have step by step walk through, because I found it hard to understand what to see in what order.
For example, I'd suggest something like below using the sample data provided.

Focus on Averaged waveform window first. Move to the leftmost clusters by dragging.
Click the cluster 1 in the window. Check if .....
Then click the cluster 3. The feature-vs-time view shows spikes in the cluster are intermingled with gray dots, i.e. background, so the isolation is poor. Choose Unit 3 > noise or type d to delete the cluster.
etc...

Also I'd like to see the good example of a result of manual curation phase using the sample data. At the end how many single units did you find in the sample data (128 channels for 5 min?), for instance? How long the manual curaton may take?
Best regards,
Kouichi

The features shown for the selected cluster are in black, with background features in gray (toggle background features with the b key)

At least I figured out that "background features" (gray) means the features (eg. Vpp = the amplitude between negative peak to positive peak) of the other clusters than the selected cluster (black) recorded in the same site (in the example below, Site 13 as shown on the left). They are shown in "The waveform view" horizontally in the same row (eg. Site 13).


Migrations don't support chinese charset?

In my migrations file, the code include chinese charset.but it can't be shown in the database.
  ContentDefinitionManager.AlterPartDefinition("CommitteeStage",
   builder => builder
             .WithField("RequestAdvices", cfg => cfg
                     .OfType("FileField")
                     .WithDisplayName("标准征求意见稿")
but it can't be shown in content definition. as below. how it should deal with？

migrations to database don't support chinese ?  in my database, the chinese charset wrong, how i deal with it ？ thanks.

sorry ,my falut,the file type should be utf-8..


Removes unused integration

Description Of Changes
This PR removes a previously deprecated integration.

Hey @TheAndrewJackson I've added you as a reviewer here as we spoke about getting this done a while back :)

The other two files are migrations. One in ctl and the other in ops. These can probably be ignored

I deliberately left them in, so as not to invalidate people's database records on the off-chance this has been used anywhere.


Solve or Berkshelf issue

Problem is being reproduced in solve-2.0.3 only.

$ git clone https://github.com/acondrat/solveissue
$ cd solveissue
$ bundle
$ bundle exec berks
Resolving cookbook dependencies...
Fetching 'solveissue' from source at .
Fetching cookbook index from https://supermarket.chef.io...
/home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve/ruby_solver.rb:144:in block in sort_dependencies': undefined method payload' for nil:NilClass (NoMethodError)
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve/ruby_solver.rb:141:in each' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve/ruby_solver.rb:141:in sort_by'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve/ruby_solver.rb:141:in sort_dependencies' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:131:in block (2 levels) in class:Resolution'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:431:in push_state_for_requirements' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:423:in require_nested_dependencies_for'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:411:in activate_spec' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:353:in attempt_to_swap_possibility'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:333:in attempt_to_activate_existing_spec' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:318:in attempt_to_activate'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:147:in process_topmost_state' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolution.rb:72:in resolve'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/molinillo-0.4.4/lib/molinillo/resolver.rb:42:in resolve' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve/ruby_solver.rb:195:in resolve_with_error_wrapping'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve/ruby_solver.rb:75:in resolve' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/solve-2.0.3/lib/solve.rb:64:in it!'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/resolver.rb:78:in resolve' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/installer.rb:175:in install_from_universe'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/installer.rb:39:in run' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/berksfile.rb:421:in install'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/cli.rb:143:in install' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/thor-0.19.1/lib/thor/command.rb:27:in run'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/thor-0.19.1/lib/thor.rb:359:in dispatch'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/cli.rb:52:in dispatch' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/thor-0.19.1/lib/thor/base.rb:440:in start'
from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/lib/berkshelf/cli.rb:27:in execute!' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/gems/berkshelf-4.3.1/bin/berks:5:in <top (required)>'
from /home/acondrat/.rvm/gems/ruby-2.1.8/bin/berks:23:in load' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/bin/berks:23:in '
from /home/acondrat/.rvm/gems/ruby-2.1.8/bin/ruby_executable_hooks:15:in eval' 	from /home/acondrat/.rvm/gems/ruby-2.1.8/bin/ruby_executable_hooks:15:in '

Works fine with solve-2.0.2.

Seems this problem affect to last chefdk 0.12.0  https://github.com/chef/chef-dk/issues/771

I found that specifying the transitive dependency version in the berksfile in another workaround.

@danielsdeleo gonna ping you on this one since you did the legwork on the alternate solver backend

I was able to make a failing test case here: https://github.com/berkshelf/solve/tree/chefdk-771 (https://github.com/berkshelf/solve/commit/b84500e80c22e0596b530838f7a7d299f6f9f870)
Aside from that I don't have any leads as to what is going on, yet. I added some debugging to Molinillo itself and it definitely "looks weird" but I don't know Molinillo deeply enough to know what to make of it.

I fixed the upstream bug and that fix has since been released. cf. https://github.com/CocoaPods/Molinillo/issues/38


Add some more documentation to SystemParam

Objective

Fixes https://github.com/bevyengine/bevy/issues/4783

Solution

Add more documentation about the derive, and the obscure failure case for this.
Link to StaticSystemParam in these docs.
Also explain the attributes whilst here.

bors r+


Fix: os xcode python interpreter

Added workaround for OSX XCode python interpreter, but still doesn't know how to reproduce on OSX a situation when OSX XCode python interpreter becomes a main interpreter observable by terraform.
Also added an exception that better explains the issue with missing python interpreter version.

Thanks!
v1.21.0 has been just released.


Immutables

Proposing support for members immutable in attempt to resolve #575.
I am cutting corners here: this PR in its current form assumes that #588 is accepted, and hence should not go ahead of #588. I want to throw it in anyway because not so much time is left before 1.0.

I think it would be better to use the term unmodifiable: their modification via API is not allowed, but their values can be of course changed by server...

I'd say that "immutable" is okay, although it doesn't describe the state of the resource object but of its attributes here.
And it's clear, that this is an information for the client only and that it doesn't limit the server in modifying the resource attributes.

There's actually a term for this: "read-only".

All words express the same and all still mean that the server can modify it anyway... :)

Updated the PR:

replaced immutable with readonly
added 403

Updated: added a clause about accuracy for client / resource / moment in time, similar to one in #590.

@hhware perhaps this additional spec can be achieved using the meta section of the payload, rather than defining additional structure. I had considered something similar for "protected-attributes" as a sibling of "attributes" but the more I thought about it I'm happy with expressing that level of detail as meta content, see https://github.com/json-api/json-api/issues/575#issuecomment-101510988

@pixelhandler, this is what I initially thought about it (https://github.com/json-api/json-api/issues/575#issuecomment-96380083), but then I concluded that it could have broader audience than just one API: meta is intended for custom stuff, specific to a given API...

Given that both attributes and relationships may be read-only, I'm opposed to a common bucket that could group both together purely from a structural perspective.
I think it's also important to realize that immutability can be temporal, and that attributes that are read-only at the time of one request may be mutable at a later time due to a resource's change in state.

Given that both attributes and relationships may be read-only, I'm opposed to a common bucket that could group both together purely from a structural perspective.

But on the other hand, they share the namespace. IMHO, this is strong enough commonality to allow them to be listed together in a common bucket. I would no mind separating them in different sub-buckets though, if that helps.

I think it's also important to realize that immutability can be temporal, and that attributes that are read-only at the time of one request may be mutable at a later time due to a resource's change in state.

Is not it an argument in favor of having such mechanism? Many things about resource can be temporal: its existence, its representation in any given response, immutability of some members. Temporal aspect can be handled via resource versioning.

I think this could be very well solved using an extension available in v1.1. An extension does not require changes to base spec. This should allow experiments and quicker iteration than trying to add it to main spec.

I like this 👍


Retain flag

Hi,
thanks for the great node-red add-on.
I've one problem, how to set retain flag true for a config / discovery topic?
Is it possible to set?

Sorry, I didn't consider this situation. It uses the default method and cannot be modified

Fixed now.


Docs: remove duplicate entry for Scale.notes()

Just caught this super minor duplication

Cheers. Thanks Jack!


⚠ TROJAN 🇺🇸 United States USO 1 has degraded performance

In d82cc4f, TROJAN 🇺🇸 United States USO 1 (https://ust-2.opensvr.net/) experienced degraded performance:

HTTP code: 200
Response time: 24422 ms

Resolved: TROJAN 🇺🇸 United States USO 1 performance has improved in 570bdf4.


Use memory buffer to write current deltas before flushing them

Right now we write each delta to a delta file right away. What we could do to improve the performance is to write those deltas to the memory buffer first, flushing them when we fill the file.
As a related note, we could also send the flush response back to the server once we write all deltas to the file, fsync and close it. By not doing fsync we risk losing some records on crash, since the server usually disposes of them after receiving the flush.

two points here:

flush delta memory buffer to the file as soon as we get sigterm(and maybe sigusr1?) signal
maybe it will make sense to get rid of the tempDir, and flush data directly to the archiveDir. Also there should be monitoring(most likely prometheus http endpoint) to see the number of the buffer files which need to be flushed to the archiveDir

Fixed at https://github.com/ikitiki/logical_backup/pull/16