[FEATURE] Auto-focus for input widget

Description of the requested feature
Many people including me use eww to create an app launcher. Those app launchers use an input widget to search through the desktop files. An auto-focus option for the input widget would be useful to automatically set keyboard focus to it as soon as its get visible so you can start typing right after opening the launcher instead of having to first click on the input widget to focus it.
Proposed configuration syntax
:auto-focus true
Additional context
No response

You can achieve this feature by setting :focusable true in wayland or :windowtype "dialog" in x11, ej:
(defwindow launcher
  :monitor 0
  :stacking "fg"
  ;;;; this for x11
  :windowtype "dialog"
  ;;;; or this for wayland
  :focusable true
  :geometry (geometry
    :width "430px"
    :height "600px"
    :anchor "center"
  )
  (app_launcher)
)

and then using a keybing to open/close the launcher, ej in hyprland:
bind = $mainMod, R, exec, eww open launcher --toggle

I'm already using :windowtype: dialog on X11 and :focusable true also didn't work on Wayland when I tested it. I still have to click the input field first to focus it. I use bspwm on X11 and tested it with Hyprland on Wayland.


Incorrect package handling

Hi, I've found that after a .proto is transpiled by prost-build, it cannot be imported.
Here's archive with minimal working example crate: bug.zip
Basically, there's two proto files in the same directory:
protos/src/messages/first.proto
syntax = "proto3";

package mysoftware.foo;
import "src/messages/second.proto";

message First {
  bar.Second second = 4;
}

and  protos/src/messages/second.proto
syntax = "proto3";

package mysoftware.bar;

message Second {
  bool second = 1;
}

Errors are:
$ cargo run
   Compiling rustbag v0.1.0 (/home/dl/Downloads/bug)
error[E0433]: failed to resolve: maybe a missing crate `bar`?
 --> src/proto/mysoftware.foo.rs:4:46
  |
4 |     pub second: ::std::option::Option<super::bar::Second>,
  |                                              ^^^ maybe a missing crate `bar`?

error[E0283]: type annotations needed
 --> src/proto/mysoftware.foo.rs:1:28
  |
1 | #[derive(Clone, PartialEq, ::prost::Message)]
  |                            ^^^^^^^^^^^^^^^^ cannot infer type
  |
  = note: cannot resolve `_: std::default::Default`
  = note: required by `std::default::Default::default`

error: aborting due to 2 previous errors

Some errors have detailed explanations: E0283, E0433.
For more information about an error, try `rustc --explain E0283`.
error: could not compile `rustbag`.

To learn more, run the command again with --verbose.

By the way
protoc-rust correctly recognizes the same files
quick-protobuf also has the issue with packages: https://github.com/tafia/quick-protobuf/issues/160 (there's also example code for protoc-rust)

@dlazerka it's necessary to include! the individual modules separately, for example:


feat: add option to customize base image and add mount option

fixes https://github.com/containers/podman-desktop-extension-minikube/issues/13
Change-Id: I0706aaa3c934aa71f30e2c1948f7811883fd12f5

@jeffmaury test added
@feloy I've reworked with your suggestion


OPCPublisher:latest API Server not working

Hello,
I am trying to follow this example below:

Calling the API over HTTP
(This feature is in preview)
You can now send HTTP requests to the publisher module http server at https://localhost:8081. The unsecure endpoint is mounted at https://localhost:8080 for testing purpuses. E.g. to get the swagger definition run:
curl http://localhost:8080/swagger/v2/openapi.json"
However, I get 'Failed to connect to localhost port 8080' error message. I have tried using the 'netstat -an' command to list out all ports available on localhost and I cannot find 8080 / 8081

.
What I have done:

Made sure all local ports connection are enabled for UDP + TCP in Windows Firewall for both inbound and outbound rules
Tried Adding '--DisableHttpServer=disabled' , "--httpserverport", "--unsecurehttp" to the OPC Publisher Module as part of Container Create Options

But still no luck

If you want to access the server on the localhost you need to create a port binding from 80 to 8080 and 443 to 8081 like in the deployment.json in the same folder.  No other command line arguments should be needed.  You do not need to export the ports if you use a module in the same Azure IoT Edge docker network to access the server.  (But then you use just https://) since 443 port is secured using a IoT Edge module SSL certificate which should be in the module trust list.

You can follow the instructions to run the module in iotedgehubdev using the deployment.json file in the repo.  If the http api is then not accessible, please reopen and add repro steps, and the deployment manifest you used.

I noticed that swagger is off in release builds. Will add a command line option to turn it on or off for both release and debug.

Also, the title says ":latest", the tag for 2.9.0 is "2.9.0-preview4" if that makes a difference.  It is possible that the deployment.json refers to latest, but latest is still 2.8.6 at this point.

Swagger UI will be always on in 2.9, you can disable using --doa, --disableopenapi.


Is your documentation right?

I'm having trouble understanding your documentation. The code snippet given is
@Component({
  selector: 'awesome-button',
  template: require('./button.template.html'),
  styles: [require('./button.style.css')]
})
export class AwesomeButtonComponent { }

But then right below that it says

The angular2-template-loader searches for templateUrl and styleUrls declarations inside of the Angular 2 Component metadata and replaces the paths with the corresponding require statement

So why does the example use template and styles? What am I not getting here?

I don't think it's quite right yet. You're "before" example still uses template and styles when it should be using templateUrl and styleUrls.

Was going to open a PR just for this. It seems wrong to me as well, but of course ... I might be wrong.
The way I see it, readme should look something like:

Before loader (your original code)
``tjs
@Component({
selector: 'awesome-button',
templateUrl: 'button.template.html',
styleUrls: ['button.style.css']
})
export class AwesomeButtonComponent { }

#### After loader (before it is bundled into your webpack'd application)
```js
@Component({
  selector: 'awesome-button',
  template: require('./button.template.html'),
  styles: [require('./button.style.css')]
})
export class AwesomeButtonComponent { }

Looking at current specs, my understanding seems to be ok:

this is the sample code
this is the expected output

@GiuseppePiscopo, that's in line with my understanding as well. Hopefully your PR will get merged soon.


[terra-clinical-onset-picker] Announce state and chosen/selected item in the combo box

Summary
The state and chosen/selected item in the combo box must be announced by the screen reader. Currently, we set the aria-labelledby to the id of the label of the combo box. Removing the aria-labelledby announces both the state (expanded/collapsed) and the chosen/selected item in the combo box. This can be seen visually but the screen reader does not call this out. The date format was not read correctly by the screen reader. The screen reader was reading Date Date Date/Date/Date. We will need to hide the label for the screen reader users.
What was changed:
Removed the aria-labelledby from all the fields. Hid the label for Date Field for screen reader users by setting the aria-hidden attribute.
Why it was changed:
For the screen reader to call both the state and chosen item in the combo box.
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[x] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[ ] No tests are needed

On MAC:
State & Chosen item:
https://github.com/cerner/terra-clinical/assets/55503680/d3dd35ab-d700-4703-aeb0-af3edae7864c
Date format:
https://github.com/cerner/terra-clinical/assets/55503680/d343d997-675d-41de-b89a-a5278f0bdb47
https://github.com/cerner/terra-clinical/assets/55503680/fd0da416-a0e6-40ec-b0ca-8893455b9d02
On Windows:
https://github.com/cerner/terra-clinical/assets/55503680/ecf987c8-4138-43ac-9b1f-8630f2540433
Date Format:
https://github.com/cerner/terra-clinical/assets/55503680/d74557d6-ed0d-4e24-9e51-4ffcc1913fa8
Deployed site - https://engineering.cerner.com/terra-clinical/pull/896/
Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[x] Accessibility review
[ ] Functional review

Additional Details

This PR resolves:
UXPLATFORM-9428

Thank you for contributing to Terra.
@cerner/terra

Deployed site - https://engineering.cerner.com/terra-clinical/pull/896/

@sdadn, @sycombs - This PR is ready for your review. TIA.


Tutors cannot start assessing submissions before the exercise due date

Checklist

[x] I run yarn run webpack:build:main: the project builds without errors.
[x] I run yarn lint: the project builds without code style warnings.
[x] ~I updated the documentation and models.~
[x] I tested the changes and all related features on the test server https://artemistest.ase.in.tum.de.
[x] ~I added (end-to-end) test cases for the new functionality.~

Motivation and Context
Tutors shouldn't be able to start assessing submissions before the exercise due date isn't due

I do not know if this has already been considered, but this might be another solution to this approach (which enables tutors to grade before the due date):
The instructors have to enable grading for an exercise (to ensure that grading only starts once the sample solution/grading criteria are finished), if they do not enable it manually, it gets enabled automatically on the due date passed.
If the instructors enable grading before the due date, the students will not see their grading until the due date.

@sleiss We considered other/better approaches similar to your suggestion, but for now we just wanted a quick solution to prevent tutors from assessing submissions too early in the currently active courses. Thank you for your comment, though. In the long term we definitely want something more sophisticated.


In #86 I changed all of the animations from manual lerping in Update() to using drawable transforms in UpdateInitialTransforms(), but neglected to re-implement the Hidden and FadeIn mod behaviors.
On the bright side, this gives me the opportunity to rethink how Hidden and FadeIn would work :)

Due to the amount of unique note type behaviors (laned notes, Touch notes, TouchHold notes, and Slide notes), I don't see Hidden or FadeIn working in a consistent way that I can be happy with.
Closing this as a "won't fix".


[CIVIS-7585] Fix terminal access

This fixes terminal access. At some point, the notebook code changed to not automatically create a terminal when, e.g., /terminals/1 was accessed. This updated code creates a terminal if one doesn't already exist before going to the terminal page.
While there's a TerminalList.new_terminal() function, it does not appear to be accessible from the env variable that the extension is provided, so this code follows what that function does by posting to /api/terminals, etc.
Note: When we update to notebook 7, we'll probably have to rewrite a lot of this, so this is only temporary.
Here's an internal test notebook in Platform.

[x] (For Civis employees only) Reference to a relevant ticket in the pull request title
[x] Changelog entry added to CHANGELOG.md at the repo's root level
[x] Description of change in the pull request description
[x] If applicable, unit tests have been added and/or updated
[x] The CircleCI builds have all passed

I'm no JavaScript expert, so there might be a better way to do this. Also, please let me know if the JS isn't following conventions, etc.

As a followup, I made a new release: https://pypi.org/project/civis-jupyter-notebook/2.2.1/


Taking long time for training

Hi All,
I am new to the EnergyPlus and trying to set up the rl-testbed-for-energyplus for my project.
If I run the below command, it is taking long time to train.
time python3 -m baselines_energyplus.trpo_mpi.run_energyplus --num-timesteps<PHONE_NUMBER>,
Can you please let me know  how long will it take to complete the  training and the minimum hardware specification to run the program

Hi,
You used a lot of timesteps, that are used in the paper, but are not really necessary if you want to have an acceptable policy. In my experiments with TRPO, you can have decent results after 10^6 timesteps. The program works on my laptop, although if you want to use other algorithms, a GPU can significantly accelerate training. But is not absolutely essential, as it is still possible to train a network in around 2 days on a CPU.

hi
Thanks a lot. I have tried and it is taking a shorter time. Thanks for your help.


Can not add a table for the role

Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if any
[x] I have reproduced the issue with at least the latest released version of superset
[x] I have checked the issue tracker for the same issue and I haven't found one similar

Superset version
{"GIT_SHA": "", "version": "0.18.2"}
Expected results
Successfully adding a table for the role
Actual results
Can not add a table for the role
Steps to reproduce
Greetings. I added the table via the SQL Lab tab.

From this table I managed to make slices and dashboards. Now I want to add a view of these dashboards to another user. I copy the gamma role, open the list of access rights for this role, but unfortunately I can not add the table I created earlier. She's not on the list.

But it is in the database.

The last ID in the drop-down list is 43, in the database itself 45. Please note. In the database, there are no 43 in the table, there are 44, 45. That is how it should be?
If you have time, tell me why?
Thank you.

Resolved after executing the commands:
superset db upgrade
superset init


single-shot, sender-side mpp via sendtoroute

This PR lays some more groundwork for our road to MPP payments in lnd. Here we add the ability to send MPP shards from the sender-side via SendToRoute, whose additional fields are properly encoded in the onion blob and delivered to the receiver.
Apart from verifying that mpp records are not received at intermediate hops, the receiver does not perform any additional validation of the actual fields contained within. The receiver side has been modified to deliver these values all the way down to the invoice registry, but they are not inspected. Thus, the receiver will process the payment as they would a traditional payment. The additional behavior to enforce the MPP fields will be added in #3415, at which point the behaviors will diverge.
For now, the integration tests have been expanded to cover the three send to route endpoints Lightning.SendToRoute, Lightning.SendToRouteSync, and RouterRPC.SendToRoute, as well as testing that each can properly pay with single MPP shards. Future changes will continue to expand the assertions as more pieces come into place.

I also experienced that the onion blob decryption code needs to be moved out of htlcswitch so that it can be used in cnct without a circular reference. Will we move that into htlcswitch/payload too?

Discussed offline. Plan is to move decryption (HopIterator) into the hop package and replace with hop.Iterator

This looks pretty good to me now, only a question

Also, PR desc is still empty.

@joostjager added

ACK on using single blob in follow-up. I still have opinions about not having the optional MPP record be its own field on the struct, but that we can discuss in  the follow-up.

Needs a rebase! Then I think this is ready to land.

@Roasbeef rebased!


2D isn't working

... 'cause a) I have forgotten about it, and b) numDims() == 3 assumption is hardcoded at places -> needs to be generalized

this got fixed in the new 'concept_changed' branch


Test suite is flaky

See builds:
1- ❌ https://travis-ci.org/Starcounter/starcounter-include/builds/289883476
2- ✔ https://travis-ci.org/Starcounter/starcounter-include/builds/289883530
Both builds are for the same commit (https://github.com/Starcounter/starcounter-include/commit/c4ce9002f8c415311f94a301d5e02be9aaedb253)
Restarting the build fixes the issue, sometimes.

@alshakero  does it still happen? I think concurrently may have fixed that.

Haven't happened to me for a long time. I think we can close it now.


It seems there is a logical error in synthetic_dataset.py

In synthetic_dataset.py get_mixture_and_gt() funtion, about in line 161

shifted_gt, _ = utils.shift_mixture(np.stack(gt_waveforms), target_pos, self.mic_radius, self.sr)
should be in the outside of the loop like this:

In synthetic_dataset.py get_mixture_and_gt() funtion, about in line 161

shifted_gt, _ = utils.shift_mixture(np.stack(gt_waveforms), target_pos, self.mic_radius, self.sr)
should be in the outside of the loop like this:

Thanks for the fix! Indeed this should only be calculated once at the end

Regarding the overfitting problem: If you are training with purely synthetically rendered data, then you can generate arbitrarily many samples. Consider grabbing more types of noises, or even using other voice examples like Librispeech etc. When training with real data, it is time consuming to gather this data. Therefore it is very easy to overfit. However it is important to train with real data because a network trained on purely synthetic data will not generalize to real data


Issue with CSS

Im probably screwing up something simple but for the life of me I can not get simple css selectors to work with the following forum.
{
  "expected_update_period_in_days": "1",
  "url": "https://forums.servethehome.com/index.php?forums/processors-and-motherboards.18/",
  "type": "html",
  "mode": "on_change",
  "extract": {
    "thread": {
      "css": ".titleText .title",
      "value": ".//text()"
    }
  }
}

Seems to work in selectorgadget and chrome developer tools.

Hey @cyberactive, this is an odd one.  I think that this site is giving Huginn different content than it gives the browser.  When I do a dry run with "thread": { "css": "html", "value": "." }, I don't see any occurrences of titleText.  You could try setting the user_agent to the one used by Chrome and see if it changes anything.

Yeah even setting the UA to chrome makes no difference. I even tested using
no script on Firefox to  see if that gets the same treatment as huginn. I
will investigate this more after the holiday.
On Thursday, December 24, 2015, Andrew Cantino<EMAIL_ADDRESS>wrote:

Hey @cyberactive https://github.com/cyberactive, this is an odd one. I
think that this site is giving Huginn different content than it gives the
browser. When I do a dry run with "thread": { "css": "html", "value": "."
}, I don't see any occurrences of titleText. You could try setting the
user_agent to the one used by Chrome and see if it changes anything.
—
Reply to this email directly or view it on GitHub
https://github.com/cantino/huginn/issues/1185#issuecomment-167161967.

Did you solve this @cyberactive?


Using FCM token in iOS breaks push notifications for intercom

Describe the bug
On iOS, If you fetch the firebase FCM token instead of the raw APNS token and use that for the capacitorDidRegisterForRemoteNotifications listener, push notifications do not work.
To Reproduce

follow guide for installing and using @capacitor/push-notifications
follow guide for installing and using @capacitor-community/intercom
Use the following code in AppDelegate, as mentioned in the capacitor  push notifications guide

func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
        Messaging.messaging().apnsToken = deviceToken
        NotificationCenter.default.post(name: .capacitorDidRegisterForRemoteNotifications, object: deviceToken)
        Messaging.messaging().token(completion: { (token, error) in
            if let error = error {
                NotificationCenter.default.post(name: .capacitorDidFailToRegisterForRemoteNotifications, object: error)
            } else if let token = token {
                NotificationCenter.default.post(name: .capacitorDidRegisterForRemoteNotifications, object: token)
            }
        })
    }

To Fix
I have resolved this by adding the following line in my AppDelegate didRegisterForRemoteNotificationsWithDeviceToken method but I am not sure if this is the ideal solution as I do not know a lot of Swift.
Intercom.setDeviceToken(deviceToken)

So now the function looks like this and I can receive both APNS notifications from Intercom and FCM notifications from firebase.
  func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
        Intercom.setDeviceToken(deviceToken)
        Messaging.messaging().apnsToken = deviceToken
        NotificationCenter.default.post(name: .capacitorDidRegisterForRemoteNotifications, object: deviceToken)
        Messaging.messaging().token(completion: { (token, error) in
            if let error = error {
                NotificationCenter.default.post(name: .capacitorDidFailToRegisterForRemoteNotifications, object: error)
            } else if let token = token {
                NotificationCenter.default.post(name: .capacitorDidRegisterForRemoteNotifications, object: token)
            }
        })
    }

Smartphone:

iPhone 12: [e.g. iPhone6]
OS: 15.1.1

sounds like an edge case, great solution tho. mind to doc in README and open a PR?

intercom registration is done automatically by the plugin, you shouldn't have to do it manually in your app delegate.


Multi-User Support + Detail-Textbox

Hi,
thanks for Burden so far. It would be nice to find multi-user support in this. The ability to choose me (or a user) when creating a task, would be a simple and nice team-support. Also a Textbox for Details would be great, so you can add additional information for a task.

Hi,
Just came across burden and I think its great. I was looking for multi user support to have collaboration between people or create a task list for another person.
Thanks.

This is planned :)
Sent from my iPhone

On 13 Nov 2015, at 03:42, namethatswitty<EMAIL_ADDRESS>wrote:
Hi,
Just came across burden and I think its great. I was looking for multi user support to have collaboration between people or create a task list for another person.
Thanks.
—
Reply to this email directly or view it on GitHub.


(builder) Can't set task name /dev/mapper/docker-202:25-3667816-pool

If the builder is restarted on the same node the following (fatal) error is thrown:
Can't set task name /dev/mapper/docker-202:25-3667816-pool
I'm a bit unfamiliar with how the device mapper works. I suspect the error may be occurring because a loopback device is being setup in ExecStartPre but not cleaned up in ExecStopPost.
https://github.com/deis/deis/blob/master/deisctl/units/deis-builder.service#L10
This is likely related:
https://github.com/docker/docker/issues/4639

Great digging, @croemmich. We'll have to figure out what's going on here.


CRD Chart Improvements

Add a set of additional flags that can modify the templates/ directory of a CRD chart on prepare:
# Under additionalCharts[i].crdOptions
prepareOptions:
  syncVersionWithMainChart: # whether to automatically update the version on the templates/Chart.yaml to match the main chart's version

Closed in favor of https://github.com/rancher/charts-build-scripts/issues/47


Can't get past the Double Check configuration for paid OpenAI API prompt.

First of all thank you, for your work.
I pulled all the files and placed them in the right paths in my environment. Even installed EdgeGPT.
But when i run AutoGPT, after setting the goal including
"Use ask_bing_genius whenever possible"
i get this error: DOUBLE CHECK CONFIGURATION  Please double check that you have setup a PAID OpenAI API Account. You can read more here: https://docs.agpt.co/setup/#getting-an-api-key
Is it not possible to test auto gpt without a paid API?
Thanks and cheers!

same question :)


chore: remove devops/sync because we have blueprint now

Summary
closes #1558
Key Points

[ ] This is a breaking change
[ ] New or existing documentation is updated

LGTM


win,fs: use the new Windows fast stat API

Windows added a new API for file information, which doesn't have to open the file thus greatly improving performance: https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-getfileinformationbyname .
This PR implements this improvement on libuv. This was based on the Python implementation: https://github.com/python/cpython/blob/3a72fc36f93d40048371b789e32eefc97b6ade63/Modules/posixmodule.c#L2089-L2120 .
The stat functions are already covered by tests, so no test was added here. I considered comparing the result of old and new code, but that would require exposing internal fs functions, and we would be testing Windows functionality, not libuv.

Looks like the kernel API for this was added in Windows 10, version 1703 circa 2017 (EOL 2019), though not documented until circa 10/30/2019 https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-ntifs-ntqueryinformationbyname

The version number where this exact feature is supposed to be available starting in Windows 11 doesn't exist yet and/or isn't released yet, depending on which documentation page you go by:
https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/ns-ntifs-file_stat_basic_information
But looks like python has been using this API since about 1 year ago, when it was added for them:
https://github.com/python/cpython/issues/99726#issuecomment-1472409980
At a cursory glance, this looks great

@vtjnash thank you for your suggestion. The kernel API for this is available as of Windows 11, build 26048. The API NtQueryInformationByName could be used before, but we need the information from FileStatBasicInformation.
I use an API function GetFileInformationByName that is compatible with the kernel API, but with a more user-friendly interface. The API function uses the kernel API under the hood, so there is no noticeable difference in performance. Also, requiring this function lets us use this functionality only when it is available.
This is already available in Windows Insiders, which I have been using for testing.

Okay, it looks like 24H2 is 26052, which is consistent with the documentation saying >= 26048, released recently:
https://blogs.windows.com/windows-insider/2024/02/08/announcing-windows-11-insider-preview-build-26052-canary-and-dev-channels/

Rebased to include the sanitizer test fix. I see a new failure on macOS, I believe that's not related to the changes here.

@vtjnash is there anything else I can do to help here?

I think it is ready to go, I just figure it will get merged in a batch sometime before the next release

Hi @vtjnash, I was just wondering when this will land and be released. Is there a plan for the releases? Thanks in advance.

Do you mind rebasing (or ticking the checkbox to give me the ability to do that) and fixing the one style nit? It looks all ready to merge, as we get ready for the next release, but I wouldn't mind giving it one more CI test run.

Thank you for the review. I've applied the change and rebased the branch.


Adding simple clarification to --image usage

Now that I have read the docs more and see the pattern, this seems
obvious. But when I was stuck trying to gojira an image I was able to
successfully start I did not understand that I needed to specify
--image on all the commands.
Signed-off-by: Tyler Ball<EMAIL_ADDRESS>

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

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

thanks!

thanks!


EP02-F03-US02 - Like subject

As a user I want to like a subject and add the liked subject into my liked list


Check $less->importDir issues with new dokuwiki version

Whenever a new version of dokuwiki is going to be released this fix should be verified:
https://github.com/splitbrain/dokuwiki/commit/343a31d8fe7efc33670809a79d82b500fdc99b76

fixed by splitbrain


Cargo owner --add requiring invitations deployment plan

I'm currently working on an issue on Crates.io regarding requiring a user's consent to be added as an owner of a crate. I'm at deployable chunk 4, requiring approval for ownership, and we've come to a point where the result of altering the owner_add  function on the crates.io side to require a user to accept an invitation before being added as an owner of a crate might be confusing for users.
The problem is that currently the messages conveying the result of adding an owner are hardcoded into Cargo, and only the success/error results come from Crates.io. When cargo owner --add is run, Cargo displays the message "adding owner to a crate" and displays an error message indicating the user was not added if something went wrong in adding the owner to the crate. If we require a user to accept an owner invitation, it would be better to have a message on the Cargo end stating that your invitation has been submitted and the invitee must now accept their owner invitation, but that the user was not yet added as an owner. Due to the process of deploying something to Cargo, if implemented now on Crates.io, the feature could be live but this message would not be available for another few weeks on stable. If a user never updates Cargo, it may never become available. @carols10cents and I came up with a couple options to try to implement this as soon as possible on Crates.io while making the transition as smooth as possible on the Cargo side.
Option 1
Add a new route, something calling a new function owner_invite on Crates.io, and change the route on Cargo to this new route. Two routes would be available on the crates.io backend, one calling owner_invite and the other still for owner_add. Eventually deprecate owner_add on Crates.io. This option could possibly be confusing for users in having two different experiences when adding an owner to a crate - some of the time it might go through, and some of the time they might have to accept an invitation. This also defeats the point of having to invite users as it would still be possible to add owners without permission.
Option 2
Let older versions of Cargo lie about adding a user. Change the current message on the Cargo side, but if a user has not upgraded Cargo, they will never get the message indicating that the user they invited must accept to be added as an owner.
Option 3
Return an 'error' from Crates.io. Since Cargo does use error text, use the error for now to indicate that the user has not been added as an owner. The error in this case would be used to transfer a sort of success, that the user was sent an invitation, but that they must still accept to be added as an owner. This is misleading as an error did not actually occur, it is intended that a user cannot just be added to be a crate owner. It would also be difficult to distinguish between actual errors and this 'error'.
Another thought was to combine options 1 and 3. The old route, owner_add would return an error and another function owner_invite would be added which returns ok/errors normally.
None of these options sound particularly appealing, is there anything else that can be done about this? Are any of the options preferred?

I'd personally be in favor of Option 2, we could backport a fix to Cargo to just display a message that crates.io responds with and deploy it in just a few weeks (if we do it soon in like 2-3 weeks!). Once the current stable Cargo "does the right thing" I'm not too worried about any historical Cargo "lying" about having someone added

Okay, thanks! I'm content going with Option 2, of the three it seems like the easiest solution.


ARM docker image builds

Are you interested in ARM builds? I've implemented those for maloja and it looks like you have almost the same actions file so it should be piece of cake to implement it into your workflow as well.

Yes! If you can implement that and create a PR I would be happy to accept it.

closing as it wasn't closed automatically in merge request. maybe [fixes #] must be used instead of [closes #]


SFApiRequestError: Maximum number of redirects exceeded

Summary
While clicking on the "ask" tin the "Einstein for developers" extension in VScode, we are receiving an error defined below,
SFApiRequestError: Maximum number of redirects exceeded
Steps To Reproduce:
Go to "Einstein for Developers" extension and click on "Ask"
This throws an error saying "SFApiRequestError: Maximum number of redirects exceeded"
Expected result
This should not throw an error.
Actual result
This is throwing an error and obstructing the usage of functionality.
Describe what actually happened instead.
Additional information:
Have tried with latest version of VS code also but still error persists.
Salesforce Einstein For Developers Version in VS Code: v0.39.0
VS Code version: 1.86

Hi @debprotim, thanks for the info and for your patience as we try to resolve this issue for you! Can you let me know if you're getting this error for all Einstein for Developers features? I.e. - Can you use our inline autocomplete feature? Does the command "Einstein: Generate Code" return a completion if you're in an Apex file? I would assume you'd see the same error for these features as well but I just want to rule out something specific to the sidebar. Additionally, I noticed your Einstein for Developers extension version is a little out of date so if you could update to the latest that would be great.

Assuming you’re not able to get a response from any Einstein for Developers features, our suspicion is that the proxy you’re using is causing the redirects. By default our extension is setting the maximum number of redirects to 5. One way for us to test this would be to have you run a cURL command and see if the request shows up in our logs.

Yes, it is not working. Same error is popping up.

@debprotim I have increased the max_redirect limit and and would like to share the vsixes with you. GH doesn't support the VSIX to be shared here. What else would be a great way to connect with you? Also have you tried with latest version of Einstein For Developers v0.43.0 ?

I installed the vsix file. Anything particular you are looking for?

@debprotim Then re run the steps and let us know if you still see the error.

Same error:

Hi @debprotim, given that the new VSIX file with a raised max-redirect limit didn't resolve the issue, it seems likely that the proxy settings on your end are causing an infinite redirect loop or an excessively high number of redirections. I have asked the support engineer to assist you in investigating the proxy settings on your machine. Please let us know if you have any questions or need further assistance with this.

@debprotim This seems like a one-off user settings issue. Let us know how else if we can help you, otherwise would like to close this issue. Thank you for raising your concerns.

Hi @debprotim - Closing this issue out since the root cause appears to be a proxy setting issue. Please feel free to re-open or create a new issue if you have further questions.

We had a follow up support meeting to help the user debug the proxy issue further and found the following:
There was a http_proxy setting in vscode.  When removed the user was able to successfully hit the E4D endpoints for all features.
However without that setting the user was unable to auth against their orgs.
We provided the following guidance:
Work around:

Use CLI with proxy env vars set to do auth
Remove http_proxy setting from vscode
This allows the user to still auth as necessary but decouples the proxy from VSCode so both E4D and standard SFVSCE tools works as expected.

Recommendations:
User should reach out to their IT support and have them follow up on why their proxy is hitting max redirect with E4D generation endpoints: https://api.salesforce.com/einstein/gpt/code/v1-alpha.1/
Attempted to utilize curl to track the redirects taking place, but got the expected 404 from the command line


Fix module node unit test

Coverage decreased (-0.06%) to 47.557% when pulling 0e67f4148a3daa8ed8f92cccf9ddf535eac13809 on issue_19 into d6092b60f79214f9b27f59f617264c5bcc8d0e79 on master.


Operations get duplicated

Describe the bug
I use urql in a nuxt 3 project and see duplicated operations when they should only get triggered once.
[Exchange debug]: Incoming operation:
{key:<PHONE_NUMBER>, query: Object, variables: Object, kind: "query", context: Object}
{timestamp:<PHONE_NUMBER>862, source: "fetchExchange", type: "fetchRequest", message: "A fetch request is being executed.", operation: Object…}
[Exchange debug]: Incoming operation:
{key:<PHONE_NUMBER>, query: Object, variables: Object, kind: "query", context: Object}
{timestamp:<PHONE_NUMBER>865, source: "fetchExchange", type: "dedup", message: "An operation has been deduped.", operation: Object}
{timestamp:<PHONE_NUMBER>610, source: "fetchExchange", type: "fetchSuccess", message: "A successful fetch response has been returned.", operation: Object…}

Note that I'm aware that the dedupExchange blocks this duplicate request. But I'd rather consider this a workaround. The second operation should not be executed in the first place.
I added some console.log() to the urql sources and was able to track it down to this part of the code in client.ts:
https://github.com/FormidableLabs/urql/blob/0582f9b138ddb66c5164b00a978aac90e865c0dc/packages/core/src/client.ts#L302
The callback passed to make() gets called twice and hence the same operation in onStart() is dispatched again somehow. I could not figure out, why this happens.
The documentation on Wonka's make says:

The function you pass to make is called lazily when a sink subscribes to the source you’re creating.

So I would expect that this is only called once. Not sure if this is maybe rather a bug in wonka.
Reproduction
https://codesandbox.io/s/urql-duplicate-operation-yfp2ei
Urql version

@urql/core 3.0.3
@urql/vue 1.0.2

Validations

[X] I can confirm that this is a bug report, and not a feature request, RFC, question, or discussion, for which GitHub Discussions should be used
[X] Read the docs.
[X] Follow our Code of Conduct

I can't really look into this anymore because the sandbox seems to be gone 🤔 That said, if I remember this correctly, it's expected behaviour. This is similar across our Vue and React bindings (for different reasons however), but, both of these bindings basically do two operations simultaneously on mount.
In the Vue bindings you may have two places in which the operation may be triggered:

The regular effect that starts fetching results: https://github.com/FormidableLabs/urql/blob/0582f9b138ddb66c5164b00a978aac90e865c0dc/packages/vue-urql/src/useQuery.ts#L175-L189
The suspense await triggers an operation to listen to results and resolve once one is available: https://github.com/FormidableLabs/urql/blob/0582f9b138ddb66c5164b00a978aac90e865c0dc/packages/vue-urql/src/useQuery.ts#L206-L225

This isn't really cause for concern. In fact, we're not sharing results between the two since that can lead to some hidden timing bugs, as we found. However, you should always expect to see multiple operations, which due to deduplication both in the Client and in the dedupExchange won't lead to multiple requests.

Thanks for the pointers. I will have a closer look.
Too bad that this is not easily fixable, though. As you may have seen I have more issues with urql, especially with ssrExchange (#2689). I've been working on a rewrite of that exchange and may open a PR for discussion soon. But this issue here would probably be a blocker for the fix of ssrExchange.

Oh, and sorry for the broken link to the sandbox. I must have deleted it accidentally as it was quite some pain to get the sandbox finally starting.
I've created a new one and updated the link in the issue description.

Sorry for coming back to this late,

Note that I'm aware that the dedupExchange blocks this duplicate request. But I'd rather consider this a workaround. The second operation should not be executed in the first place.

Basically, we actually don't consider this a workaround, because there are many reasons for this to happen. Specifically, both in urql's bindings for Vue and React there are concepts of suspense and interruption respectively.
In Vue, we have both the use of the hook triggering the subscription to results reactively, while it may also be await-ed for Vue's Suspense feature, and in React the initial mount and later effect are separate, which means there are always two potential phases in which data is retrieved separately.
In other words, two operations being triggered is often representative of two separate "client-accesses".
While it's tempting to think of urql's operations as "actions", they're much more like a request for data retrieval. Hence, the dedupExchange is important and the client actually has more mechanisms to merge identical operations into one. That's why we'd consider it a non-issue.
To get to a more general question: Do the Vue bindings when they're used with await need to trigger two operations?
We can actually rephrase this into: Can the lazy-promise/thenable and the watchEffect call share the same source. The answer to that used to be no with a not so simple explanation.
When we initially tested and wrote the implementation, what we noticed is that the timing of both can wildly differ, just like in React. This means that if we share the source (via Wonka's share operator) we actually sometimes may get too few operations 😅

Closing due to inactivity with the explanation above


[EPIC] Add further pre and post checks in harvester upgrade

Describe the bug
Just ran into an issue with the upgrade from 1.0.3 to 1.1.0 with two different cases:

there was a "orphaned" machine object in fleet-default
the upgrade from harvester 1.0.2 to 1.0.3 was completed but the cluster status "local" has been stuck in "Provisioning"

Expected behavior
There should be additonal pre and post checks before and after any upgrade to verify the cluster is 100% ok before and 100% ok after the upgrade so that no left over actions / pending actions are there that might cause issues in the future.
Environment

Harvester ISO version: 1.0.2/1.0.3/1.1.0

Additional context
We should check

[ ] timesync status on all nodes (timedatectl)
[x] the status of all volumes (health ok or detached)  (kubectl get volumes -A)
[x] for sufficient free disk space (/, /usr/local, /var/lib/longhorn, /var/lib/harvester/defaultdisk and other longhorn disks)
[x] node health / all nodes ready
[x] kubectl get clusters.cluster.x-k8s.io local -n fleet-local
[x] kubectl get machines -n fleet-local
[ ] conflicting customizations in /oem/* (i.e. registries.yaml)
[ ] sufficient memory and CPU in the nodes

especially in case we add additional workload like monitoring/logging
For live-migration cases, we need to check if the rest nodes can absorb VMs from a upgrading node.

For some we should print a warning and block the upgrade and for some others we should allow the upgrade even with warning.

Seems we have a "deprecated volumes check, already":

Without Longhorn UI available, the following command can be used to check the status of all the LH volumes:
$ kubectl -n longhorn-system get lhv
NAME                                       STATE      ROBUSTNESS   SCHEDULED   SIZE          NODE     AGE
pvc-8f9a780e-17dd-41bc-8cc8-a3f0a3e71636   attached   healthy      True<PHONE_NUMBER>0   node-3   7d12h
pvc-eab05ecb-6fb8-4f3c-a1f7-17d60fd30a25   attached   healthy      True        10485760      node-3   7d12h

https://github.com/harvester/harvester/pull/2836

the status of all volumes (health ok or detached)  (kubectl get volumes -A)

https://github.com/harvester/harvester/pull/3093

node health / all nodes ready
kubectl get clusters.cluster.x-k8s.io local -n fleet-local
kubectl get machines -n fleet-local

TODO:

timesync status on all nodes (timedatectl)
for sufficient free disk space (/, /usr/local, /var/lib/longhorn, /var/lib/harvester/defaultdisk and other longhorn disks)
conflicting customizations in /oem/* (i.e. registries.yaml)
sufficient memory and CPU in the nodes (especially in case we add additional workload like monitoring/logging)

Related: https://github.com/harvester/harvester/issues/2935

Non-finished enhancements are tracked at https://github.com/harvester/harvester/issues/4926 and will continue there.


Merge pull request #1 from TryGhost/master

fork sync

Instead of creating a pull request to sync your fork, your should add this repo as upstream, fetch the latest master and push it to your master.

OKAY


Store datetime fields with a Datetime type instead of a string

Currently pycsw sets up a database using the sqlalchemy.Text type for most columns.
In my opinion it would be nicer if we could use other sqlalchemy types, specially the sqlalchemy.DateTime type when creating the database. This would make the transition from python datetimes to the database smoother. The current situation gets around this by trying not to use python datetime and using strings instead.
For an example, the pycsw.core.metadata._parse_sos method actually converts a python datetime object (as returned by owslib.sos.SensorObservationService.contents[...].begin_position) into a string (lines number 718 and 719), so that it can be manipulated further down the road.
There is also a safeguard in pycsw.core.util.getqattr to always convert a datetime.date or datetime.datetime to a string. This function is used whenever something is to be written to the database.
I propose that we change this around:

instead of converting datetimes to strings, we'd convert any (date based) string into a datetime as early as possible
transform the sqlalchemy type of the fields in the core metadata model that represent dates and datetimes to a sqlalchemy.DateTime type.
store datetimes in the database

Benefits:

it is possible to use some other frameworks to directly query pycsw's database using datetime fields getting nice representations. In my concrete use case, I can use django's admin interface to visualize the temporal extent of a record using a datetime widget
We can work with the native type of this type of data instead of using strings
We can rely on the database backends to correctly interpret datetimes in queries instead of relying on a text based query for stuff like filtering for temporal extent begin and end datetimes.

I have an initial draft with the changes necessary for implementing this proposal in my local repository. It seems to work OK with sqlite and postgis, but I can only test with normal records. I will prepare a pull request so that it may be evaluated.

This proposal breaks backward compatibility to our existing deployments, so it is not that easy to handle.
Similar discussion has happened in the early days of pycsw and we chose text representation as a simple/safe way to implement things.
It would require something more than a PR, it would need am RFC and a vote from the steering committee to do such a change.

OK, I will investigate a bit more on alternative solutions and look at how other projects are doing this. I'll prepare an RFC if it will seem to be a worthy change

I would recommend to post the above to the pycsw-devel mailing list for further discussion.


Poor performance in sort::sort_to_indices  with limit option in arrow2

Hello, I did a benchmark vs arrow1.
It shows that arrow2 has great performance improved in min, sum and max etc.
But the sort::sort_to_indices function with limit 100  has a performance drop.
Benchmark results:
arrow2-sort 2^13 f32    time:   [67.831 us 67.978 us 68.144 us]

arrow1-sort 2^13 f32    time:   [34.306 us 34.405 us 34.521 us]

Codes: https://github.com/sundy-li/learn/tree/master/arrow-vs-arrow2/benches
Scripts:
cargo bench -- "arrow1-sort 2\^13 f32"
cargo bench -- "arrow2-sort 2\^13 f32"

as_slice is the bottleneck.
I think we can use values: &[T] to replace get: G.
Improved in commit:  https://github.com/datafuse-extras/arrow2/pull/1
Now:
arrow2-sort-limit 2^13 f32
  time:   [46.601 us 46.665 us 46.728 us]
  change: [-24.847% -24.656% -24.483%] (p = 0.00 < 0.05)
  Performance has improved.

Another bottleneck is from_usize().unwrap() in the loop.

Great finding; thanks for sharing!
Would you like me to backport it here?

Great finding; thanks for sharing!
Would you like me to backport it here?

Sure, after I finish the migration, I'll create pr to arrow2.


Update Event Notification Icon in reference architecture diagram

Description
Resolves: https://github.com/terraform-ibm-modules/terraform-ibm-event-notifications/issues/326

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

No need for a release - the DA points to main branch diagram always, so we don't need a new release

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

GitHub release
v1.14.2

Your semantic-release bot :package::rocket:


Biber (tool mode) silently ignores entries with non-default separator.

If I run biber --tool --listsep='|' --namesep='|' ... it seems to silently ignore all the bibliographic entries that include this list/name separator (i.e., not output them). I do occasionally get a warning about this, but it's not consistent, for some odd reason.
Running biber --tool --listsep='|' --namesep='|' --output-listsep='|' --output-namesep='|' ... works as expected, and includes all entries in my original .bib file.
It sounds like this is a matter of slightly improving the warning messages, I suppose?

I'm not quite sure what the issue is here? Could you give the warnings? Are you saying that without the output options set, there are issue with with the input options for separators?

@plk Without the output options set, any bibliographic entries containing (|) (e.g., in the author or editor field) gets silently omitted from the output. (Well, occasionally it will warn, but not reliably, for some reason.)

Can you paste an example entry with this issue?

@article{foo,
    author = {Bar1, Foo1 | Bar2, Foo2},
    title = {Foo},
    year = {2020},
    journaltitle = {Baz},
}

An entry like this simply gets omitted from the output, unless the -output-*sep options are specified (maybe only one of those two is needed, I forget).

Hmm, can't reproduce this - with your example in file test.bib and running:
biber --tool --namesep="|" test.bib

I get in the output file:
@ARTICLE{foo,
  AUTHOR = {Bar1, Foo1 and Bar2, Foo2},
  DATE = {2020},
  JOURNALTITLE = {Baz},
  TITLE = {Foo},
}

Apologies; this is my mistake. I had run the above command twice, and the second time it (naturally) did not recognise the and separator output by the first run, and emits and error, excluding those entries from output. Looks like expected behaviour, so I'll close this issue.


'odo' community enablement

Description
odo developer CLI for OpenShift is reaching the state where it could be used by end-user. We want to enable the community to start using odo and provide feedback about their developer experience on OpenShift using odo.
We should be ready to welcome the community on the project, from both using and contributing aspects. For that we should be building a simple webpage for the project as well as revamping the readme.md. We should be providing links to online tutorials, examples and getting started guides.
Tasks

[ ] Revamp readme.md to include demo video, links to online tutorials, documentation and website
[ ] 'odo' project page (similar to the one done for kedge)
[ ] Documentation for each commands
[ ] Examples and Getting Started
[ ] Setup public communication channel

I'm going to split this off into a few different issues. a few tasks have already been completed:

[ ] Revamp readme.md to include demo video, links to online tutorials, documentation and website
[x] 'odo' project page (similar to the one done for kedge)
[ ] Documentation for each commands, issue: https://github.com/redhat-developer/odo/issues/446
[x] Examples and Getting Started
[ ] Setup public communication channel

Do you think that issue:
Revamp readme.md to include demo video, links to online tutorials, documentation and website
Is completed since we have the Katacoda tutorial, user-guide documentation as well as the website on the README.md, or should we include a demo video too?
@kadel @slemeur

It would be great to have quick start as a gif animation in readme. For example I really like what Origin has in the readme - https://github.com/openshift/origin

@kadel Only thing left to do now is to create a gif (preferably using https://asciinema.org/) and put it on the README.


Updating link to openapi-typed-2

Fixes #
No issue number
Description
Corrected link to https://github.com/meeshkan/openapi-typed-2
How to test
Check the link is the right destination.  Click the link.

Replaced with https://github.com/meeshkan/hmt/pull/210


NUsight Director View

This PR adds an NUsight page which displays a visual overview of director for debugging.

It might be good to make active green and I always think of done as being blue for some reason but it doesn't matter too much. I was also thinking done could be a different shape, like a triangle? or maybe the border could be it's activeness and the infill the doneness.

Something like this? I had a look at sending parent with each item so I could render them as a tree, but I'm worried about the performance cost of sending more info than we are already. I'm also not sure what Director information is most useful.

The director tree shouldn't be that much information compared to everything else that's being sent. You should be able to send almost everything and still come close to causing a bandwidth/rendering issue.
That is so long as you only send information when the director tree changes


Allow mapping from a Menu selection to arbitrary values, not just an integer

The current menus return an integer that represents the elected element(s). It would be nice to supply an optional vector of values that should be mapped to. This could simplify the mapping from selection to some other value, by packing into the Menu, where it feels like it would belong. This vector of "values mapped to" would then default to range(1, length(my_menu.titles), preserving the old behavior. To be more concrete, I imagine removing the field n_titles, which I presume is used to create such a range internally, and add a field values. Perhaps it would also make sense to change the name of titles to keys, to intuitively connect the keys and values fields.
As this change would only alter internal fields, I do not believe it is breaking according to SemVer.
Do you agree that this would be valuable? The current solution to this problem would be to take the return value and index another array, which would need it's own variable. It seems sensible to me to pack that common usage neatly in the Menu itself, where it seems to fit nicely. This is also how it is done in the drop-down selection element from PlutoUI, which I believe bases itself on some Mozilla internals.

I am not sure how, and I have a few other rods in the fire, so this will not be a priority for me for a long time. If you think you know how to do this without it taking too much effort from you, feel very free to give it a go, and I can contribute by testing it.

Sounds good!


[GITHUB ACTIONS] Fix and update warnings for workflow files to use the latest stable versions of Actions Steps

Currently Github Actions Worflow uses actions steps which were built from nodejs12. As per Github,

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the actions to use Node.js 16.

Update all the actions to use newer versions that are built on nodejs16 in the .github/worflows/*.yml files.

I would like to take this task and work upon.

Thanks @dhruvinmaniar123 . Assigned this issue to you.


Cache reflection operations

Caches several reflection code paths that tended to get executed often with the same types, so should have a very positive effect on performance. Closes #23.

@csantero Interested in feedback on this and #24. Working to make it possible to support related object ID queries in #14 by making GetIdProperty() accessible, and doing some optimization along the way. Particularly wondering about my thread-safety (or possible lack thereof).

Okay, I'm done with the big refactoring pass. @csantero please have a look.
Notes:

I found that GetPropertyMap shouldn't really be a public interface; the fact that I built a map was an implementation detail/optimization strategy. What clients need is methods that provide information on the properties, types, and corresponding keys. Internally, those methods use a map to cache reflection information.
It's somewhat irritating that we can't require a constructor via the interface...so we can't require implementers to accept a IPluralizationService as a constructor argument. Yes, ultimately it's up to them how to populate that property, but it still seems like part of the contract is missing.
IsMany became IsSerializedAsMany
GetSingleType became GetElementType, which no longer works for non-many types, and I left a private convenience method in JsonApiFormatter that replicates the old behavior but calls the IModelManager methods. I'm not happy with the name GetElementType but am not sure what else to call it.
I'm thinking ahead to other uses for IModelManagers...besides using it in EnableFilteringAttribute and MetadataManager. For example, I think with a few more methods it should be possible to build a model generator for Ember Data (!). I had a class that used to do this, but it's horribly broken by now. I really liked it, even if I had to tweak the output, it made model refactors so much easier not to have to sync changes to the client code by hand. It also might be valuable to optionally let users pre-register their model objects to build the cached reflection data at boot.

@SphtKr This is really good. I'm excited about the peformance improvements this will offer (although we don't have any performance tests to prove this). I've submitted a PR to clean up those constructors a bit.
Does ModelManager need to have a parameterless constructor at all? Can we just remove that and also the equivalent parameterless constructor on JsonApiFormatter? Then the user can't not provide a pluralization service.

I suppose not, it's left over from the singleton pattern in the case of ModelManager I suppose. And yes now there's no reason to have the parameter-less constructor on JsonApiFormatter either. That's good too, because I don't want it to be easy for the user to use the default pluralizer, since it's so naïve, they should have to choose it.


Account name covers ArtX logo on mobile

Fixed in https://github.com/macterra/artx-market/commit/2bd4e2720457f9bde7ee9f44b97ad254a25e0326

Moved logout under the "hamburger" menu

Tested


Web - Moderation Board

Implement moderation board, which will be used by those that have access to them to handle reports made by users.

We decided to let System Administrators deal with the reports using our Postman interface for now. Moderation board will not be in the MVP.


The page does not load

After deploying the zip file, I get "This page isn't working 500" error in Chrome. The webapp is running, everything looks green and OK, but I cannot open the example webpage. Can you help me please? Is it OK to sent the request on the port 80?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4b0165d7-6462-842c-76ec-1a1f344fa51a
Version Independent ID: 3b2c77ed-d9eb-cf20-0ace-908b88927e54
Content: Create a Node.js web app in Azure
Content Source: articles/app-service/app-service-web-get-started-nodejs.md
Service: app-service-web
GitHub Login: @msangapu
Microsoft Alias: cephalin;msangapu

@gbodacs Thanks for the feedback! We are currently investigating and will update you shortly.

Do we have a solution yet to this? I am also getting the same error after successfully deploying the zip file.

@gbodacs looks you are having the same issue mentioned here. Try updating the node version in Application Settings to the value 8.11.1


Add symlink tests

@mentatbot can you add some tests which involve symlinks especially in loops to catch bugs?

@mentatbot


Free lockable-resource assigned to dead builds

#fix #500
Sometimes after re-starts (jenkins crashed or what ever) are resources still locked by build, but the build is no more running.
This changes will 'unlock' all resource assigned to the dead builds
Testing done
It is more or less not possible to simulate it.
We use this code in our Jenkins instance few weeks and it works
We reboot our instances once per week (or often) and after this changes we has the issue no more.
Therefore I thing it works as expected.
Proposed upgrade guidelines
N/A
Localizations
N/A
Submitter checklist

[x] The Jira / Github issue, if it exists, is well-described.
[x] The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).

The changelog generator for plugins uses the pull request title as the changelog entry.
Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during the upgrade.

[x] There is automated testing or an explanation that explains why this change has no tests.
[ ] New public functions for internal use only are annotated with @NoExternalUse. In case it is used by non java code the Used by {@code <panel>.jelly} Javadocs are annotated.
[ ] New or substantially changed JavaScript is not defined inline and does not call eval to ease the future introduction of Content Security Policy (CSP) directives (see documentation).
[ ] For dependency updates, there are links to external changelogs and, if possible, full differentials.
[ ] For new APIs and extension points, there is a link to at least one consumer.
[ ] Any localizations are transferred to *.properties files.
[ ] Changes in the interface are documented also as examples.

Maintainer checklist
Before the changes are marked as ready-for-merge:

[ ] There is at least one (1) approval for the pull request and no outstanding requests for change.
[ ] Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
[ ] Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
[ ] Proper changelog labels are set so that the changelog can be generated automatically. See also release-drafter-labels.
[ ] If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
[ ] java code changes are tested by automated test.

Just in case: would this fire on "server start", or on "job load" (per annotation name) so e.g. when an MBP job gets defined due to new branch, or otherwise a job configuration edited (and so reloaded?)
I have concern for custom uses of Lockable Resources (sort of hackery beside defined steps) which toss a particular resource like a SUT between stages or even jobs.

Just in case: would this fire on "server start", or on "job load" (per annotation name) so e.g. when an MBP job gets defined due to new branch, or otherwise a job configuration edited (and so reloaded?)
I have concern for custom uses of Lockable Resources (sort of hackery beside defined steps) which toss a particular resource like a SUT between stages or even jobs.

Currently on on jenkins start - excactly 'InitMilestone.JOB_LOADED' see also
https://javadoc.jenkins.io/hudson/init/InitMilestone.html#JOB_LOADED
I make similar loic in your Jenkins instance before we try to lock someone resource. But it might be dangeraus here.

This change is breaking the Jenkins restarts.
@g3n35i5 @mPokornyETM

see #550


Fix graphicbuilder transform part 2

The previous fix to the graphicbuilder transform problem actually resulted in some graphicbuilder primitives being transformed twice because they already had the transform applied to them. This fixes that issue by moving the transformation only to primitives that were missing it. This also adds code to ensure that GeometryAccumulator does not mutate the graphicbuilder's transform in-place.

Did you determine whether the test you added in previous PR would have succeeded even without your code changes?
If so, why did it continue to succeed with your code changes?
Do you need a better test?

Did you determine whether the test you added in previous PR would have succeeded even without your code changes?
If so, why did it continue to succeed with your code changes?
Do you need a better test?

@pmconne
The test I added previously used an addShape decoration.  I incorrectly assumed that addShape decorations were not transforming properly like solidPrimitives.  Since the code change resulted in the transform being incorrectly applied twice to addShape decorations, the test "correctly" detected that the transformed decoration moved on the screen differently than before the code change.  My assumption of the problem was faulty.
I have added a test which actually tests the transform problem with a solidPrimitive.  This test correctly fails before this code change and succeeds after this code change.


MSL: Add support for sampler Y'CbCr conversion.

This change introduces functions and in one case, a class, to support
the VK_KHR_sampler_ycbcr_conversion extension. Except in the case of
GBGR8 and BGRG8 formats, for which Metal natively supports implicit
chroma reconstruction, we're on our own here. We have to do everything
ourselves. Much of the complexity comes from the need to support
multiple planes, which must now be passed to functions that use the
corresponding combined image-samplers. The rest is from the actual
Y'CbCr conversion itself, which requires additional post-processing of
the sample retrieved from the image.
Passing sampled images to a function was a particular problem. To
support this, I've added a new class which is emitted to MSL shaders
that pass sampled images with Y'CbCr conversions attached around. It
can handle sampled images with or without Y'CbCr conversion. This is an
awful abomination that should not exist, but I'm worried that there's
some shader out there which does this. This support requires Metal 2.0
to work properly, because it uses default-constructed texture objects,
which were only added in MSL 2. I'm not even going to get into arrays of
combined image-samplers--that's a whole other can of worms.  They are
deliberately unsupported in this change.
I've taken the liberty of refactoring the support for texture swizzling
while I'm at it. It's now treated as a post-processing step similar to
Y'CbCr conversion. I'd like to think this is cleaner than having
everything in to_function_name()/to_function_args(). It still looks
really hairy, though. I did, however, get rid of the explicit type
arguments to spvGatherSwizzle()/spvGatherCompareSwizzle().
Update the C API. In addition to supporting this new functionality, add
some compiler options that I added in previous changes, but for which I
neglected to update the C API. Unfortunately, this is an ABI-breaking
change. If this is unacceptable, let me know.
(Yes, this is a terrible change to review. I apologize in advance for
inflicting this upon the hapless reviewer.)

I'm on holiday, can this wait until I'm back?

Yeah, this can wait.

I'm back now, so picking this up again.
This is ... quite a large and complex PR. Even larger than tessellation. Going to take a few review passes to feel comfortable merging something like this. The complexity scares me.
Is this purely to satisfy a Vulkan 1.1 requirement or are there actual use cases for this extension?

Not sure if splitting it up would make it that easier, just need to take it slow and steady. Will also help to run some of my own shaders to see how things behave.

Starting to grok it.

Thanks a lot for implementing this.


Best way to avoid login screen for dashboard

In this section of the tutorial it is described how to avoid a login screen for the dashboard, while the flow editor is still behind a login screen.
Not sure if that way of working has any security related issues.  For example does this really only allow access to the dashboard user interface, or do I open some crucial endpoints this way?

Ah, I missed this bit when looking before. You have the editor on port 443 and the Dashboard on 8443. I would always do it the other way around. Your most public endpoints should be on the default port (443) and the more private ones (e.g. the editor) on a "random" high port. This is generally a little more secure since people cannot stumble on your editor as easily.
Oh, I can see from the next part of that both are on 443. Slightly confusing from the first section and I had to read it a couple of times.
Personally, I would always put the editor somewhere less easy to find - and preferably not make it accessible to the Internet or your Tailnet at all if you don't really have to.
As for removing the editor login - does anyone but you need access to that? If not, simply don't make it available! If you do make it available either use your proxy to add modern authentication (not sure if Tailscale has that capability?) or retain the login since if it is just you, your browser(s) will likely retain the access token anyway.
In my view, authentication is best done by a tool that knows how to do it properly and minimises opportunities for messing up. If using Cloudflare Zero Trust or NGROK for example, far better to secure an endpoint using their security rather than trying to get something generic like Node-RED to do it.

@TotallyInformation
Until last week I had indeed used 443 for the funnel, and 8443 for the web interfaces.  Which ike you say is not optimal. So I switched them last week and updated the tutorial.
Could you please  pass me a screenshot where I forgot to update it.  Will update it as soon as I get home, because that will be very confusing for the readers...

Morning @TotallyInformation,

Slightly confusing from the first section and I had to read it a couple of times.

Sorry but I really can't find where there is a mismatch.  I interpret it as that somewhere I say that dashboard is running at port 8443 (instead of 443)?  You will have to assist me finding it I am afraid...

Personally, I would always put the editor somewhere less easy to find

Yes no arguments against that.  Of course I need to walk the thin line between security and user-friendlyness.  Therefore I think it is ok that I show people how to make the editor available in their tailnet, but also give thems some hints about the risks and give them some tips.  So I have added this:

Update 1:

Update 2:

Update 3:

Then the choice is up to the user, but at least they are aware of it...

In my view, authentication is best done by a tool that knows how to do it properly

True.  I have added a comment about that and created a feature request in the Tailscale repo:


Add test-flag to ICARE App

This PR adds a new flag to the CLI --test-flight. When using this flag, the app will not create an ICARE messaging client or try to post data to AWS. I also disabled the run logger and the email notifications in this case since it's just a practice run where someone is likely watching for any extraction errors. I also didn't add a short option to the CLI option because it seemed like a flag that we would want to be explicit about turning on (also, there are no good letters).

DP1 - We should probably add some information to the readme, informing people of this option. Happy to put together that copy with you after standup!

@Dtphelan1 I added a short section to the readme about the --test-flag use. I'm happy to continue editing it if it's missing anything or could be worded differently. Once it looks good here, I'll add the same section to the other repo.

This looks good to me!

@julianxcarter if this still looks good to you, then you should feel free to merge :) Just wanted to make sure you got the chance to track these new changes.


ObjectDisposedException when using WebListener and IP address

I can reproduce following error when starting my ASP.NET Core application as console:
2017-04-04T14:43:34.1364025+02:00 800004d6-0000-f400-b63f-84710c7967bb [ERR] ProcessRequestAsync (67a2badb)
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'Microsoft.Net.Http.Server.ResponseStream'.
   at Microsoft.Net.Http.Server.ResponseStream.CheckDisposed()
   at Microsoft.Net.Http.Server.ResponseStream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken)
   at Microsoft.AspNetCore.Server.WebListener.ResponseStream.<WriteAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.WebUtilities.HttpResponseStreamWriter.<FlushInternalAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.ViewFeatures.ViewExecutor.<ExecuteAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.ViewResult.<ExecuteResultAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeResultAsync>d__30.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResultFilterAsync>d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResultExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResourceFilter>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Server.WebListener.MessagePump.<ProcessRequestAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Server.WebListener.MessagePump.<ProcessRequestAsync>d__24.MoveNext()
2017-04-04T14:43:34.1394037+02:00 800004d6-0000-f400-b63f-84710c7967bb [INF] Request finished in 336.4424ms 200 text/html; charset=utf-8 (15c52c40)

This happens only when using WebListener and a Ip address within the url:
  var host = new WebHostBuilder()
				 .UseWebListener()
				.UseUrls("http://localhost:5000", "http://<IP_ADDRESS>:5000")
				.UseContentRoot(Directory.GetCurrentDirectory())
                .UseStartup<Startup>()
                .Build();

            host.Run();

The strange this is, this happens after 10-20s after starting. Something from the internal is requesting my HomeController:
   at ASPCoreBug.HomeController..ctor()
   at lambda_method(Closure , IServiceProvider , Object[] )
   at Microsoft.AspNetCore.Mvc.Internal.TypeActivatorCache.CreateInstance[TInstance](IServiceProvider serviceProvider, Type implementationType)
   at Microsoft.AspNetCore.Mvc.Controllers.DefaultControllerFactory.CreateController(ControllerContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResourceFilter>d__22.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextResourceFilter()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeAsync>d__20.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeAsync()
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.<Invoke>d__3.MoveNext()
   at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.AspNetCore.Hosting.Internal.RequestServicesContainerMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Hosting.Internal.HostingApplication.ProcessRequestAsync(Context context)
   at Microsoft.AspNetCore.Server.WebListener.MessagePump.ApplicationWrapper`1.ProcessRequestAsync(Object context)
   at Microsoft.AspNetCore.Server.WebListener.MessagePump.<ProcessRequestAsync>d__24.MoveNext()
   at System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
   at Microsoft.AspNetCore.Server.WebListener.MessagePump.ProcessRequestAsync(Object requestContextObj)
   at System.Threading.Tasks.Task.Execute()
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot)
   at System.Threading.Tasks.Task.ExecuteEntry(Boolean bPreventDoubleExecution)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

I'm using the latest versions.
Check the attached project to reproduce the issue (ensure to start the console hosted version).
ASPCoreBug.zip

@Tratcher / @rynowak - any idea on this?

The second stack trace is #5807 - no idea about the first.

Looks similar to https://github.com/aspnet/Hosting/issues/603 but it was never reproduced.

@eilon - we have a provided repro of this, someone should investigate

This issue was moved to aspnet/Hosting#1110


Add channel for comic strips

Add config file for comic strips
Write functions for configuring and updating feeds of popular comics

Hey @CaptainIRS I would like to work on this issue under DWOC'24 but can you plz tell a flow how to do this. We have to store data in json format, web scraping will also be used?

Hi @vaishnavi192,
The ideal flow would be: (mostly based on the logic behind how forum posts are fetched)

Collect a list of comics with content related to programming/programmers/software., like XKCD, MonkeyUser, The Developer's Life, etc.
Create a config file for comics in the config, folder, similar to config/forums.json, which defines the frequency of posts, name and icon of the site, etc.
Create a comics/ folder in the root similar to the forums/ folder to create files to fetch the comics from the sites and process them. (Refer next step)
Check if the comic has an RSS feed. To do that follow step 3 in CONTRIBUTING.md#adding-new-feeds. If there is a feed, then write the logic like forums/slashdot.py, else create something like forums/hackernews.py to scrape the site yourself and get the posts according to the frequency.
Create a comics/__init__.py like forums/__init__.py to act as an interface.
Create utility functions in util/embed_utils.py similar to create_forum_embed, create_forum_telegram_post and create_forum_reddit_post to convert your post to the formats recognised by Discord, Telegram and Reddit.
Add a new channel for comics in main.py (here) and update .env.example accordingly.
Create an updater in main.py like _forum_updater and add that to the logic in DiscordBot, send_telegram_messages and run_reddit_bot.

It might seem like there are a lot of steps, but each step is really only a few lines of code and I've tried to map out all the steps exhaustively. Do let me know if you have any questions...


help me please

Hello, I'm deploying on a computer, it seems that everything is installed. I get the link, everything works.  What's wrong?
Initial log:

end log with error:

Thanks a lot! Good luck)

Hello @Denskl1 , the program is not designed to run on Windows at the moment, but the error could be related to ffmpeg not being found in the system, so it needs to be installed; ffmpeg is a multimedia framework and you can install it on Windows by following this tutorial.

Hi @Denskl1
I've addressed the Colab issue. Could you kindly confirm if it's working for you now? Have a wonderful day!

Hello! Yes, now everything seems to be working, the only thing is that an error occurs at the end of the process.

It seems that there is no way where to save the file, or some kind of permission.
What could it be?
Thanks, have a great day!

Hello, everything is working. Thanks a lot, have a great day!

Hi @Denskl1,
I'm delighted to hear that everything is working for you now! If you have any more questions please don't hesitate to reach out. Have a fantastic day!

hello, please help me with the settings. Everything works, thank you. But when translating, when the speech is fast, it seems to start to accelerate, and does not finish the sentence. I suspect that somewhere the settings need to be changed?

Hi @Denskl1,
In line 557 and 558 of the app_rvc.py file, the variable porcentaje is currently set to 2.1 (Specifically, this setting accelerates the audio playback by 2.1 times when the duration difference is very high ). This value was chosen to address issues of audio overlapping that were occurring in many videos, or when the timestamps are not detected correctly.
Modifying this value might help in slowing down the audio playback. However, please keep in mind that this change could potentially cause issues with audio overlapping.
Default:
        if porcentaje > 2.1:
            porcentaje = 2.1

You can experiment with different values for porcentaje to see if it resolves the problem. Try reducing the value gradually until you find a setting that prevents the audio from accelerating too much during fast speech.
For instance, you can try:
        if porcentaje > 1.5:
            porcentaje = 1.5

Hello! Is the program running now? I decided to try online, but I always get the same error:
Error
Error can't create the audio file: ffmpeg version 5.1.4-0+deb12u1 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14) configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu --arch=amd64 --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libmfx --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 [mov,mp4,m4a,3gp,3g2,mj2 @ 0x5587309d3dc0] moov atom not found Video.mp4: Invalid data found when processing input


Allow promotion pass if pending is empty

This is for [MMENG-3800(https://issues.redhat.com/browse/MMENG-3800)] Dependency promotion fails with "Copy failed: paths null". We allow the promotion to pass in this case.

LGTM.


Rendering of nested profile metrics runs out of memory

Discovered while researching this issue:
On the profile page, the rendering of the nested tree of metrics data runs out of memory when there is a top-level metric with thousands of children. This happens in all three deployed environments in the case of the 'masteryWorkspace' and 'conceptBuilderWorkspace' metrics.
This affects all deployed versions:
To reproduce on dev (v5.2): log into UpGrade > navigate to the profile page.
To reproduce on other environments (v5.1): log into UpGrade > navigate to the Metrics tab of the profile page > click on the '>' to expand the row for the 'masteryWorkspace' and 'conceptBuilderWorkspace' metrics.
Deliverable:
Implement a fix that handles the volume of metrics data somehow without running out of memory (possibly by truncating the metric children data at some cutoff, or disabling the recursive tree display in some or all cases).
If there's no solution the allows the current design to handle the volume of data, we should limit the data being rendered for the current release (6.0), and then re-think the design. In that case, spawn an issue.

@danoswaltCL @zackcl We discussed this issue and came up with a potential solution. We propose adding a search bar at the top of the metrics tree. This search bar would allow users to search for a metric name, including within the nested structure. Only the resulting metrics would be displayed as expandable, potentially alleviating the memory issue.

Hey, I worked on this a little bit last week and I think it's still possible to display the tree without it freezing. I will try to share something today, but I'm also open to other suggestions, such as a search bar.

Qa'd and passed!


getSleepSamples causes the app to crash

java.lang.NoSuchMethodError: No interface method stream()Ljava/util/stream/Stream; in class Ljava/util/List; or its super classes (declaration of 'java.util.List' appears in /system/framework/core-libart.jar)

it seems like a java version issues. Can you provide your android/build.gradle in case if you change anything.

// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
ext {
buildToolsVersion = "29.0.3"
minSdkVersion = 21
compileSdkVersion = 29
targetSdkVersion = 29
}
repositories {
google()
jcenter()
mavenCentral()
maven {
url 'https://maven.fabric.io/public'
}
}
dependencies {
classpath("com.android.tools.build:gradle:3.4.2")
classpath 'com.google.gms:google-services:4.3.3'
classpath 'io.fabric.tools:gradle:1.28.1'
classpath 'com.google.firebase:perf-plugin:1.3.1'
// NOTE: Do not place your application dependencies here; they belong
// in the individual module build.gradle files
}
}
subprojects {
afterEvaluate {project ->
if (project.hasProperty("android")) {
android {
compileSdkVersion 29
buildToolsVersion "29.0.3"
}
}
}
}
allprojects {
repositories {
mavenLocal()
maven {
// All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
url("$rootDir/../node_modules/react-native/android")
}
maven {
// Android JSC is installed from npm
url("$rootDir/../node_modules/jsc-android/dist")
}
maven {
url  "https://adcolony.bintray.com/AdColony"
}
    google()
    jcenter()
    maven { url 'https://jitpack.io' }
}

}
// apply plugin: "io.fabric"
// apply plugin: "com.google.firebase.firebase-perf"

do i need to update my JAVA version ?

@jaikantshikray  It looks good to me. Stream is included in api 24,
I am not sure if you need to change it to minSdkVersion = 24 but then some of devices you have to give up

yes i am testing on sdk 23

is there any solution either by downgrading the google fit version so i can get that working ?

i just need sleep data for google fit

I believe version 14.1 can get sleep data with lower version but the implementation is different than the latest so I am not sure unless someone came out some compatible build for different version.

ok thank you for your help


Vagyok c4 patch 1

Trying this pull request again.

Also, I noticed your NuGet package is out of datre and does not include the mapping code you accepted.  Can we get the nuget packaged updated once this request has been re-accepted.


A way to define formula function at column level

Right now you have to set it for each cell of that column. It would be great if you can set it via column properties.
Thoughts?

Hey @RaghavPro We'll have an internal discussion this week.

What "formula" are you  referring to? Are you trying to do a calculated columns?

Yes, calculated column. There should be a way to define it at column level.

@RaghavPro At the moment you we don't have this feature. I will add it to the list of desired features on the community wiki


Bump proof-systems submodule for feature flags

This PR bumps the proof-systems submodule to the commit used in #12342, but without any of the supporting changes, as a bare-minimum conversion.
This is part of the exercise to figure out the cause of the CI failure on that PR.
Checklist:

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

!ci-build-me

!ci-build-me


Reveal the MultiSizeAddr and Sealed traits

Expose traits needed to operate generically on an EEPROM. Without these traits, a user of the library may only work with fully-specified EEPROMs.

coverage: 71.107% (-26.9%) from 97.98% when pulling ec164fee21bd103758eb5b3cdbda78be30570b35 on Radiator-Labs:master into 23a2a93a2bbfdb1da0a1aee26040d6cca099be25 on eldruin:master.

Those should actually stay as private traits but I understand your point.
I have added an Eeprom24xTrait trait which should make usage even easier.
I have published that in version 0.6.0.
Could you try that out?

The new trait covers the whole interface.
The way to use it is like this:
fn run<E: Debug>(eeprom: &mut impl Eeprom24xTrait<Error = E>) {
  eeprom.read_byte().unwrap();
  eeprom.write_byte(0, 0).unwrap();
}

or equivalently:
fn run<E,M>(eeprom: &mut M)
  where M: Eeprom24xTrait<Error = E>,
        E: Debug
{
  eeprom.read_byte().unwrap();
  eeprom.write_byte(0, 0).unwrap();
}

Please see a whole example here


Change name from "Offline Mode" to "Portable Mode"

The program is already offline and it doesn't make sense for it to say offline mode when it's being used on a different device than where it was installed. Maybe it could be called portable mode and local mode instead of offline mode.

I think "Travel Mode" makes more sense. "Portable Mode" could mean that it can be ported rather than moved around.


getExtOrDefault KotlinVersion

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.
Related issues: #249 #268
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-text-input-mask/android/build.gradle b/node_modules/react-native-text-input-mask/android/build.gradle
index c94f33f..ff67cac 100644
--- a/node_modules/react-native-text-input-mask/android/build.gradle
+++ b/node_modules/react-native-text-input-mask/android/build.gradle
@@ -26,8 +26,8 @@ android {
 }

 buildscript {
-    ext {
-        kotlinVersion = '1.4.31'
+    ext.safeExtGet = {prop, fallback ->
+        rootProject.ext.has(prop) ? rootProject.ext.get(prop) : fallback
     }
     repositories {
         jcenter()
@@ -36,7 +36,7 @@ buildscript {
     }
     dependencies {
         classpath 'com.android.tools.build:gradle:4.1.3'
-        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:${project.ext.kotlinVersion}"
+        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:${safeExtGet('kotlinVersion', '1.6.10')}"
     }
 }

@@ -53,5 +53,5 @@ repositories {
 dependencies {
     implementation 'com.facebook.react:react-native:+'
     implementation 'com.redmadrobot:input-mask-android:6.0.0'
-    implementation "org.jetbrains.kotlin:kotlin-stdlib:${project.ext.kotlinVersion}"
+    implementation "org.jetbrains.kotlin:kotlin-stdlib:${safeExtGet('kotlinVersion', '1.6.10')}"
 }

Not working for me

Thank you! it worked for me, only had to change the classpath 'com.android.tools.build:gradle:4.1.3' to classpath 'com.android.tools.build:gradle:7.1.1' too.

Hi guys, I am having the same issue with react-native-text-input-mask plugin, but its the first time I will use patch-package. How can I fix the issue using patch-package? Thanks!

I would suggest you firs change anything (no matter what) in node modules and then run patch-package "package-name"
This will create a file in the root directory, then open that file and paste the code posted in this issue.


Fix signature of overloaded methods with struct in arguments

Closes #295

@nicklatkovich @krzkaczor what impact will this have on existing generated code? Will correct code need updates or should it be fine?

@nicklatkovich @krzkaczor what impact will this have on existing generated code? Will correct code need updates or should it be fine?

This looks great! Thanks for the fix @nicklatkovich. It looks like a patch change for me as without it some existing signatures were simply wrong and couldn't be used.

Released in: https://github.com/ethereum-ts/TypeChain/releases/tag/typechain%404.0.2


Serious rendering issues for todo items with URLs

Bug Report
IMPORTANT:
Please follow this template strictly when reporting bugs. Providing detailed and accurate information helps the development team to understand and address the issue effectively.
App Version: [Enter app version here]
1.3.1 (would help to place the About in the expected menu on macOS, otherwise it's hard to find)
Platform: [Windows / macOS / Linux]
macOS
Installation Method: [App Store / Direct Download / Other]
App Store
Bug Description:
UI flickers continuously
Steps to Reproduce:
Create a todo item with the following content:
(E) FastAPI research +🧠 @research
https://fastapi.tiangolo.com
https://fastapi.tiangolo.com/tutorial/

Expected Behavior:
UI not to flicker
Actual Behavior:
See attached gif
Additional Information:
See attached gif
Screenshots:

System Information:

OS Version: macOS 14.0
Processor: M2 Pro
RAM: 16GB

Reproducibility:

Sometimes

Impact:

Major

Workaround:

Poke at it random by scrolling the list, resizing the window.

Thanks for the report. Looks like it's connected to the "extract title from website" feature. Something I'm not really sure I want to keep alive in the future tbh. You can disable it in the settings.
I'm currently rewriting sleek and I'm not sure if I want to stick to this feature.

Got it, thanks for the info, I'll disable it.

I decided not to adapt this feature into 2.x. And since there is no further development in 1.3.x, I'll close here. Hope you don't mind.