[X] Have you refreshed the page? You might be using an old version of the site.
[X] Have you checked for an existing issue on this topic? If there is one, post a comment on it instead.

What browsers are you seeing the problem on?
Other - list in description
Description
The function as described is no longer existing.
Steps To Reproduce

Open the doc  (https://files.community/docs/configuring/replace-file-explorer)

Expected behavior
There should be a function as described there.
Relevant Assets
No response

This is currently only available for the sideload version of Files and is not supported in the store version.


Loosing settings

Hi, great work. I have a problem with my installation, if the esp32 is loosing power the settings are also lost. Thats an issue in a remote area with no constant power. Is there a way to make the settings permanent in the code like those for wifi?

The settings are stored in non-volatile ram and should persist through a power cycle. The default setting will load on the following conditions;

if the factory reset pin is low (Pin 4)
if the checksum value is wrong indicating corrupt data.
The NVRam can't be loaded.

if you compile the code with "-D APP_LOG_LEVEL=ARDUHAL_LOG_LEVEL_DEBUG" in platform.ini, it will log to a serial monitor. This may help determine the issue.
The relevant code is in code/ESP32/src/Configuration.cpp -> void Configuration::Load()

Sorry, the settings are lost on two instance every time the esp is loosing power, after the new security update on samsung, can't open the app anymore on two phones, a s23 ultra and a flip 3.

I have updated the google app to API 33 so it should work on most new phones.

It works now, thx. It can be closed.


Define infra and deploy the product

Infra:

[x] backend:

[x] server deployment
[x] apigateway

[ ] adjust CORS configuration: Access-Control-Allow-Origin: https://diagramascode.dev

[x] custom url pointing to api.diagramastext.dev
[x] cloudflare setup

webui:

[x] github pages: diagramascode.dev with the logic

CI pipeline defect: secrets were not propagated because they were set for a wrong github environment.

Note: Current deployment setup for the webclient is not secure, the apikey is exposed.


Syntax error executing simple aggregate

Repro steps:
Run following mongo query from connected scrapbook
db.hdr.aggregate([
  { $match: { "CURRENCY_ID": "USD" } },
])

The same query runs fin from the mongo client.
Action: cosmosDB.executeMongoCommand
Error type: Error
Error Message: Error near line 0, column 19, text '$match'. Please check syntax.
Version: 0.7.2
OS: darwin

Hi Craig,
Thanks for filing a bug report! Your report helps us prioritize what to work on.
We're working on better error reporting. I see two places our code would complain about:

Quotes around $match. See #466 and #467.
Trailing comma inside the array.
I tried a similar query (below) and it seems to execute.

db.<collectionName>.aggregate([
  { "$match": { "CURRENCY_ID": "USD" } }
])

Let me know if this works.

Yes this works - thanks

Hi Craig, the merged fix was published today (version 0.8.0). Hope this fixes your issue. :-)
Let us know how the fix holds up with your use-case.


7-Send the selected cell to api

[x] Cleanup branches. https://github.com/Janis-Rullis-IT/dev/tree/master/git#remote
[x] Branch: 16-cell
[X] Outline cells with a black border. https://github.com/janis-rullis/lm1-symfony5-vue2-api/issues/16#issuecomment-711902125
[ ] Mark them with row, col value when iterating.
[ ] Send only the selected row-col value.

Outline cells with a black border

Mark them with row, col value when iterating

Send to API where it will be validated and stored


python312Packages.dirty-equals: 0.7.1-post0 -> 0.8.0

Diff: https://github.com/samuelcolvin/dirty-equals/compare/refs/tags/v0.7.1-post0...v0.8.0
Changelog: https://github.com/samuelcolvin/dirty-equals/releases/tag/v0.8.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Part of https://github.com/NixOS/nixpkgs/pull/345326


{ungoogled-,}chromium,chromedriver: 130.0.6723.58 -> 130.0.6723.69

https://chromereleases.googleblog.com/2024/10/stable-channel-update-for-desktop_22.html
This update includes 3 security fixes.
CVEs:
CVE-2024-10229 CVE-2024-10230 CVE-2024-10231<!--
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.


Fixes so the app will build with XCode 9

Description
This fixes some Swift syntax issues so the app will build with XCode 9.
Notes
I have not yet confirmed that these changes work in older versions of XCode.
How to test this PR
Build the app in XCode 9.

@bradenmacdonald These changes are not friendly to older versions of Xcode. And Xcode 9 is also showing a couple of other warnings for the code improvements. It's good to make all changes for Xcode 9 once so that we can update codebase to latest Xcode and deprecate older version of Xcode.

@saeedbashir Ok, I was afraid of that. Your plan sounds good to me. I'm just going to leave this branch here in case it's helpful or anyone needs to cherry-pick it to test something in XCode 9. We ran into some iOS 11 specific bugs that required XCode 9 to test.

@bradenmacdonald Thank you for the PR. Definitely, it would be very helpful for the community. On the lighter note, you can push code to iOS 11 devices by adding device support of iOS 11 to Xcode 8.

The current code base is supported with latest Xcode 9.2, so I'm closing this PR.


VS Code writes the log to FAR Manager panel

VSCode Version: 1.0.0
OS Version: Windows 10

Steps to Reproduce:

Run Far Manager (www.farmanager.com)
Run VS Code.

You'll see VS Code logs in the Far Manager console they just fill the panels making impossible to work until you reload panels.

@softshape make sure you run code from the C:\Program Files\VS Code\bin folder.
@joaomoreno given the amount of issues we get from this I suggest you add an entry to our FAQ :)

@softshape Code.exe will output much garbage to the console, we can't seem to prevent it. If you use the .zip distributable, you are stuck. If you use the Setup.exe one, make sure you launch Code from C:\Program Files (x86)\Microsoft VS Code\bin\code.cmd.
@bpasero What would that entry contain? 😕

I just use the shortcut which VS Code installer adds to Windows Start menu. It points to "C:\Program Files (x86)\Microsoft VS Code\Code.exe".

Yeah that's the one that won't work. If you want to launch it from the command line, you should use C:\Program Files (x86)\Microsoft VS Code\bin\code.cmd. Setup adds C:\Program Files (x86)\Microsoft VS Code\bin to your %PATH% for that reason.

I launch it from Start menu, not from FAR Manager. It's just opened on my computer all the time.

This is strange. Let me see if I get the straight: you have Far Manager running on some terminal window; you then, using the mouse, go to the start menu, open Code and suddenly Code's output appears in Far Manager's terminal window?

Just found the reason. I use VS Code as an alternative editor on Far Manager. This is the case when VS Code is actually started from command line. After updating Far editor settings to C:\Program Files (x86)\Microsoft VS Code\bin\code.cmd the problem solved. Thank you!!!!


Today Marker Styling

How can you set the style of the Today Marker Line - I've tried setting in line styles on  but it still defaults to Black ?
I can see in your implementation the colour is set to Black but I'd like to control this.

Try adding the following within  component
https://codesandbox.io/s/lxlnjz36wm

          <TodayMarker>
            {({ styles }) => (
              <div style={{ ...styles, backgroundColor: 'green' }} />
            )}
          </TodayMarker>


EDPUB-1180: Add onboard offboard daac endpoints

Description
Add DAAC onboard/offboard endpoints for cloud metrics
Spec
See Ticket: https://bugs.earthdata.nasa.gov/browse/EDPUB-1180

Validation

Make sure all merge request checks have passed (CI/CD).
Pull related branches locally.
Run npm run clean-modules && npm run build:local in the API repo.
Deploy the EDPub applications using npm run start-dev in the overview repo.
Start to create a request and verify that the ASF DAAC is NOT currently select-able. You don't send to submit, viewing the page is validation enough.
Use swagger to test the /api/data/daac/onboard/ endpoint with the following payload:

{"id": "c606afba-725b-4ae4-9557-1fd33260ae12"}

Start to create a request and verify that the ASF DAAC is now select-able.
Use swagger to test the /api/data/daac/offboard/ endpoint with the following payload:

{"id": "c606afba-725b-4ae4-9557-1fd33260ae12"}

Start to create a request and verify that the ASF DAAC is NOT currently select-able.
Turn off the EDPub applications by running npm run stop-dev in the overview repo.


Print Error Message Sequencialy

I am trying to print the error validation on the EdithText like this:
@NotEmpty
@Email
@BindView(R.id.edith) EdithText mEdith;
@NotEmpty
@Lenth(min = 6, Message= "Password must be 6 Characters")
@Password(min = 6, scheme = Password.Scheme.ANY)
private EditText passwordEditText;
but all the error just show once instead of one after the other e.g
if the EditText field is not empty
it should print the next one
and if the all rules is true it show only print one not all the same time

I had a similar issue, seems like the validation should stop after the first error but the library keeps checking for other annotations on the same view which leads to the problem you mentioned.

cool thanks @Fahad-alkamli and I wish to add to the class lib.

to solve the issue

You should annotate all the fields with the @Order annotation. Then set validator.setValidationMode(Mode.IMMEDIATE).
When this is done, the validation will stop at the first failure.

Thanks @rjoncontract  I will try it on my IDE now

@rjoncontract the suggestion actually works fine but i am having an issue again in ordering error rules within sequence rules it print all the error at the same
here is the code

// Fields
@NotEmpty(sequence = 1, message = "Message 1")
@Length(sequence = 2, min = 3, message = "Message 2")
@Order(1)
private EditText mNameEditText;
@NotEmpty(sequence = 1, message = "Message 3")
@Length(sequence = 2, min = 10, message = "Message 4")
@Order(2)
private EditText mAddressEditText;

@NotEmpty(sequence = 1, message = "Message 5")
@Email(sequence = 2, message = "Message 6")
@Order(3)
private EditText mEmailEditText;

@NotEmpty(sequence = 1, message = "Message 7")
@Order(4)
private EditText mPhoneEditText;

so mNameEditText and other field where i have sequence  just print all the error at the same time, please i will love to how can i solve this problem


Brilliant, but...

...what's stopping Google from finding these fingerprints, and just mass-blocking them? Also, surely people using devices with a stock ROM and a genuine fingerprint are going to get blocked too, right? Especially if they have an older phone.
(Like, when I first got my Xiaomi phone, my one was already blocked on latest MIUI)

Firstly, Google already knows all of these fingerprints. They know the device properties of every unique hardware/software configuration that's ever interacted with Play Services. If they wanted to mass-block, they wouldn't need this collection, nor any of the other public dumps of device profiles.
The point is that Play Integrity can still tell the difference between real, stock devices and those spoofing a small number of the many properties available to DeviceGuard (either in the property area or in the Java environment). That makes it easy to block device profiles that are being "abused" from passing with software-backed evaluation, forcing hardware key attestation which of course fails. Most importantly, this is possible without affecting real, stock devices presenting those properties.
Xiaomi/Huawei phones with certain ROMs are potentially a different issue, since some of these aren't able to pass even in their stock configurations and I suspect this may be related to some of the conflicts between the USA/China regarding cybersecurity.
Insiders at Google (like John Wu here) have in the past suggested that a lot of the folks there aren't averse to the modding community, but that malicious abuse of Play Services is a much higher priority and blocking one without the other is difficult.
The fact that spoofing a handful of properties with Play Integrity Fix permits a device to pass with software evaluation (MEETS_DEVICE_INTEGRITY) at all is testament to this. If they wanted to, those in charge of the Play Integrity software could prevent this across the board and we'd all be back to square one.
So, in answer to your question: No, this collection isn't more likely than any other (and there are many, as ROM images, extracted build.prop files, or parsed pif.json files) to cause a mass-blocking. It may increase the likelihood of individual device profiles/"fingerprints" being temporarily blocked for software evaluation if lots of people are spamming the Play Integrity servers with them, though.
As an added precaution to avoid overuse (or actual abuse), the ~2000 profiles in this collection are actually a subset of around 40,000 device profiles collected during my research. The idea behind this is that many modders are experienced enough to visit the various dumps, extract the necessary properties, and create their own PIF profiles. This collection has simplified that process by taking a random 5% subset and converting them into compatible PIF profiles, for use by those that don't have the time, experience, or patience to find and create their own. This means that plenty of the profiles in the collection are useless and won't pass DEVICE integrity on any phone. There are, however, many more that will work fine on various devices/ROMs and it's simply a matter of trying some until you find one that passes on your hardware/software configuration.
I still recommend to most that they try to learn the ropes and assemble their own PIF profile; modding is as much a learning opportunity as it is a utility. There are some excellent guides on how to do this, such as this one by osm0sis and another simplified/rewritten by simplepinoi177.
For everyone else, this collection exists so they can still revive old phones, stay secure after an OEM drops support for a device, or otherwise get more from their device without losing what is considered by many core functionality. I hope this information has been helpful!


Refactoring of the service and runner, no semantic changes intended.

This PR applies refactoring and JS-isms, and intends no semantic changes. It is best to review each of the commits on its own as I grouped them logically into their change sets. Ignoring white space is also advised.
Note while some lets may be constants, the use of let is sometimes preferred to keep the scope of the variable scoped to its nearest {}.

LGTM - nice cleanup of the code!

Thanks @jthomas.

Thanks @csantanapr.


Permissions dialog refactoring with small-section component

I tried to refact the boolean-section and progress-section components as suggested here by @ThomasJuster
I made a small-section component that handles the collapsible section (with ng-content through projecting). However when collapsed, a specific header is used for each component.

For the progress-section, it's the value next to a beaded version of the progress:
The coloration of the beads is determined by the index of the selected value (which is an internal value of the component, not accessible from outside), so I don't think it's a good idea to completely encapsulate the logic in a component like small-section, if we want to use the ControlValueAccessor interface to transform it into a reusable form compatible component.

For the boolean-section, the header contains a simple 'Yes' or 'No' depending on the value, so it could be doable to completely get rid of the component and simply use the small-section component with a switch inside. However this means duplicating the inside code (the switch and label) to all places where this component is used (4 for now)

I was able to use the small-section component in both the progress-section and boolean-section component to factorize some of the logic (mainly the collapse behavior) but this didn't quite reduce the quantity of code.
I suggest keeping both boolean-section and progress-section and make them implement the ControlValueAccessor interface in the next PR:

boolean-section will be a boolean
progress-section will be a union of the types of the different possible values (for the permission dialog box, a string union)

Let me know how you feel about my conclusion :slightly_smiling_face:

I disliked the fact that values like the section title or icon had to be passed through the progress-section component to be used in the small-section component.
After some thinking, I found a way to decouple to section part and the logic part as previously suggested here.
The components have been renamed:

small-section is now collapsible-section
progress-section is now progress-form
boolean-section is now boolean-form

Now the progress-form and boolean-form are used inside a ng-template in a collapsible-section and the way they are displayed changes depending on the collapsed state of the collapsible-section (passed through the ng-template). When collapsed, the section will render the component in its header (and the component will render its 'header' form).
This way the inputs of the different components are only relevant to them: the section behavior is handled in the section component, and the logic of the form is handled in the inside component (in the progress-form or boolean-form).
<alg-collapsible-section title="..." icon="..." collapsible="..." collapsed="...">
  <ng-template #content let-collapsed>
    <alg-progress-form
      [collapsed]="collapsed"
      [(value)]="..."
      [values]="..."
    ></alg-progress-form>
  </ng-template>
</alg-collapsible-section>

Because the progress-form and boolean-form components are meant to be used in a collapsible-section component, they have been mode to the collapsible-section/ folder. These 2 components can still implement the ControlValueAccessor as planned.


yabridge: workaround for wine 9.5

Description of changes
Fixes #300755 based on https://github.com/robbert-vdh/yabridge/issues/320#issuecomment-2018993210
(also fixes notifications by hardcoding libdbus)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hi.
Is there anything remaining to do for this to get merged?

Oh nope! This should be good to go, but wanted to give some time for other people to try this out first. I'll merge this now.


Remove runBlocking from the sendProxyMessage service call.

@cromwellian had commented an alternative might be (generally, this case may be special in some way: "...change the calling method to be a 'suspend' function, then you can launch a regular coroutine and .join() it to block.
e.g. close() methods in our APIs are not suspendable, ergo, async cleanups are problematic.
@ianull  may have a different perspective
in many cases moving to suspend is 'viral' and hard to change"
I figure you are probably sending this currently just to get updated visibility into flaky tests, but let us know if you think to land it.

We can't change the method to suspending, as it's the implementation of an Android service method.
That method does provide a resultcallback that we can use to signal completion.
When I made the original PR that went from runBlocking -> scope.launch, I also moved the resultCallback method to occur after the store operation. This resulted in removing the runBlocking, but still introducing the performance hit, since proxy message calls were still blocking until completion, effectively (since the ServiceStore.onProxyMessage blocks on the resultCallback).
Currently, it's set up to immediately acknowledge the sender; this was the change @ianull made to improve performance.
In general, I think we don't want these onProxyMessage methods to be blocking (or return a value). But some still are. I could be wrong about this.
I think that the ultimate goal here is that we'd like to be able to fix up the tests so that they succeed without depending on a block/suspend-until-completion behavior of the underlying store.

(@ianull should definitely weigh in on this)

Service (AIDL) method should not be blocked (for waiting something) to yield better ipc health and throughput.
runBlocking is problematic across many cases thus replacing it with scope.launch seems the right way to go for :-)
Some tests are dependent on the runBlocking behavior should be also changed to event-driven model listening to the result callback.

@ianull Switch from runBlocking to scope.launch in and of itself doesn't cause much trouble. The source of all of the tests flaking is that we do this:
// Acknowledge client immediately, for best performance.
resultCallback.takeIf { it.asBinder().isBinderAlive }?.onResult(null)
store.onProxyMessage(actualMessage)

instead of this:
store.onProxyMessage(actualMessage)
resultCallback.takeIf { it.asBinder().isBinderAlive }?.onResult(null)

As it means that unlike when we're working directly with a store, there's no guarantee that the changes have been applied to the storage service's copy of the data.
When I originally made the PR to switch from runBlocking -> scope.launch, I also changed the code so that the resultCallback occurred after the onPrroxyMessage call. I ended up reverting it because you indicated that it introduced a performance regression.
The performance regression only exists if the client is in a different process, right? And in our current production uses cases, are all clients in the same process as the storage service right now?
Or: would it make sense to re-introduce the original version I had that removes the runblocking, but defers client notification until after the store.onProxyMessage call completes?
This way we'll avoid any runBlocking usage, and the tests will all still pass for now.
Then after that, we can investigate how we can return to using the optimistic-ACK approach and fix up the tests.

The performance regression only exists if the client is in a different process, right? And in our current production uses cases, are all clients in the same process as the storage service right now?
^ Actually it regresses both cases.
ack-after-onProxyMessage implies we need to wait for exercising service storage stack before the acknowledge can be really sent back. Feel we should look into why tests become flaky and if they do want to wait for something really gets completed at the service aidl api, shouldn't they use something like idle or similar?

^ Actually it regresses both cases.
ack-after-onProxyMessage implies we need to wait for exercising service storage stack before the acknowledge can be

I'm not sure I see how this is true: if we are in the same process, the call to the service method for the current version (using the existing runBlocking variant) also blocks until the entire method is complete -- so we are already waiting for the service storage stack to complete it's work.
In other words, for the current implementation in Servicestore, we have this call sequence.
        service.sendProxyMessage(message.toProto().toByteArray(), result)
       // POINT A
       try {
         result.await()

if we are in the same process, then by the time we get to POINT A, the callback has already been called, since sendProxyMessage occurred as a normal method invocation, and sendProxyMessage won't return until its runBlocking call completes everything.
So for our current use cases, I don' think the switch to scope.launch + late ACK changes the timing at all from the point of view of the calling client, and has the benefit of removing the runBlocking from the chain.

Feel we should look into why tests become flaky and if they do want to wait for something really gets completed at the service aidl api, shouldn't they use something like idle or similar?

I think we understand why the tests become flaky: a number of tests have been written with the assumption that when onProxyMessage returns, then the underlying store's CRDT has been modified.
This is particular confusing since we currently don't really differentiate between the concept of a "StorageChannel" and an "ActiveStore" -- it means that we now have ActiveStore implementations that behave differently, in some cases conforming to one behavior (CRDT changes applied by the time onProxyMessage returns) and sometimes the other (onProxyMessage returns immediate and CRDT change happens some time later).

^ Actually it regresses both cases.
ack-after-onProxyMessage implies we need to wait for exercising service storage stack before the acknowledge can be

I'm not sure I see how this is true: if we are in the same process, the call to the service method for the current version (using the existing runBlocking variant) also blocks until the entire method is complete -- so we are already waiting for the service storage stack to complete it's work.
In other words, for the current implementation in Servicestore, we have this call sequence.
        service.sendProxyMessage(message.toProto().toByteArray(), result)
       // POINT A
       try {
         result.await()

if we are in the same process, then by the time we get to POINT A, the callback has already been called, since sendProxyMessage occurred as a normal method invocation, and sendProxyMessage won't return until its runBlocking call completes everything.
So for our current use cases, I don' think the switch to scope.launch + late ACK changes the timing at all from the point of view of the calling client, and has the benefit of removing the runBlocking from the chain.

I was not talking about runBlocking but scope.launch for both cases (local and remote).
scope.launch {
    store.onProxyMessage(actualMessage)
    resultCallback.takeIf { it.asBinder().isBinderAlive }?.onResult(null)
}

The POINT A for both cases need to wait until store.onProxyMessage(actualMessage) completed.
If you just want to remove runBlocking as the step one, changing to scope.launch and late-ack but compromising to already-bad performance. The ultimate goal is changing to scope.launch and ack-first for performance sake.
Afaik the crdt is distributed computing. The service end now is on the same device/process but it can be on some other devices some day (ambient computing :-)). A crdt end shouldn't wait for completion of another crdt end.

I'm working on fixing up the tests now. It's not too many.

I'm still working on fixing flaky tests, but I think it's worth reviewing the current state of the PR, to make sure that I'm fixing flakes for the right approach :-)

Flakes: gone! Many thanks to @jasonwyatt for his start = UNDISPATCHED solution!


applies map/set invariants inside the molds

also renames +-ept:by to +-apt:by, and simplifies ++qeu.
my branch was created on top of cgyarvin/cc-merge. Should I reparent these commits somewhere else?

Reparenting onto the blinking /!\ commit on master would be helpful.

Should I change hoon.hoon in /arvo or /sys?

/arvo shouldn't even exist in the new master.
On Thu, Dec 8, 2016 at 10:04 AM, Joe Bryan<EMAIL_ADDRESS>wrote:

Should I change hoon.hoon in /arvo or /sys?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/311#issuecomment-265810004, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyAWApnVu33oGz3MASgS-ySywGyUwzks5rGEa8gaJpZM4LIG7-
.

I just tried booting a fake-zod off arvo/master and urbit/master, using 820b524511da7f8edf3f7517dc78ce57fa1a8776.pill. I got "Abort trap: 6 (core dumped)" immediately after it tried to load the pill.
Where can I find an up-to-date pill to test these changes? (I had already tested them with cc-mergeful.pill)

You didn't read the full message! You have to use -m.

My bad!
I'm not sure how to interpret this though:
$ bin/urbit -F -I zod -A ./arvo/ -m test.pill -c latest-zod
-A only makes sense when creating a new galaxy
...usage

Nevermined, this is working:
$ bin/urbit -m -F -I zod -A ./arvo/ -B test.pill -c latest-zod

/arvo shouldn't exist on master, but does: the first commit on
(non-rebased) zuseflat-users after plastic-boot is
c6cb08e "remove deprecated arvo/", but that didn't quite make it into
master.
When in doubt

checkout your original merge-base

make a shim commit that moves arvo to sys/vane and
sys/vane/{hoon,zuse}.hoon back out to sys/

rebase your commits on that, so that changes are reflected under the
correct paths

move the commits /without the shim/ onto master, via  git rebase --onto
master shim my-branch

On Thu, Dec 8, 2016 at 10:11 AM, Joe Bryan<EMAIL_ADDRESS>wrote:

Nevermined, this is working:
$ bin/urbit -m -F -I zod -A ./arvo/ -B test.pill -c latest-zod
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/311#issuecomment-265811645, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhng4aQ3JaBp0C8JKIujGU8bZ_zsvks5rGEhOgaJpZM4LIG7-
.

I've reapplied my commits to /sys/hoon.hoon, as it exists on master.
Here's the mold proofs:
~zod:dojo> =goodset (sy /a /b /c ~)
~zod:dojo> =badset [/c ~ [/b [/a ~ ~] ~]]
~zod:dojo> `*`goodset
[[99 0] [[97 0] 0 0] [98 0] 0 0]
~zod:dojo> `*`badset
[[99 0] 0 [98 0] [[97 0] 0 0] 0]
~zod:dojo> `(set path)`goodset
{/a /c /b}
~zod:dojo> ((soft (set path)) goodset)
[~ u={/a /c /b}]
~zod:dojo> ((hard (set path)) goodset)
{/a /c /b}
~zod:dojo> `(set path)`badset
{/c /a /b}
~zod:dojo> ((soft (set path)) badset)
~
~zod:dojo> ((hard (set path)) badset)
hard
ford: build failed ...

~zod:dojo> =goodmap (my [/f ~] [/b ~] [/d ~] ~)
~zod:dojo> =badmap [[/f ~] ~ [[/b ~] [[/d ~] ~ ~] ~]]
~zod:dojo> `*`goodmap
[[[100 0] 0] [[[98 0] 0] [[[102 0] 0] 0 0] 0] 0]
~zod:dojo> `*`badmap
[[[102 0] 0] 0 [[98 0] 0] [[[100 0] 0] 0 0] 0]
~zod:dojo> `(map path $~)`goodmap
{[p=/f q=~] [p=/b q=~] [p=/d q=~]}
~zod:dojo> ((soft (map path $~)) goodmap)
[~ u={[p=/f q=~] [p=/b q=~] [p=/d q=~]}]
~zod:dojo> ((hard (map path $~)) goodmap)
{[p=/f q=~] [p=/b q=~] [p=/d q=~]}
~zod:dojo> `(map path $~)`badmap
{[p=/f q=~] [p=/d q=~] [p=/b q=~]}
~zod:dojo> ((soft (map path $~)) badmap)
~
~zod:dojo> ((hard (map path $~)) badmap)
hard
ford: build failed ...

for posterity, this wraps up the work started and discussed in #266 and #275

Thanks.


How to upload images or files

im creating a page where user can attach some images with the returnable items , so i want to know that how to upload the images in shopify using graphql api

can you provide more info?
currently, the package does not support image upload. But you can use custom query to upload product images using the admin API. MORE INFO

As per Shopify doc, the originalSource is an external URL (for images only) or a [staged upload URL](https://shopify.dev/api/admin-graphql/latest/mutations/stageduploadscreate).
That means it only accepts the URL to the image. For this, you need to upload the image in temporary image server first, get the URL, and uset that URL in the originalSource field.
Once done, you can delete the image in the temporary server.


Better deal with external assets

Copy popperjs, fonts and such to local, integrate in assets
Add rake task to keep speedscope and above up to date (see also how rack-mini-profiler does it)

We basically want to get rid of this in application.html:
  <link rel="preconnect" href="https://fonts.gstatic.com">
  <script src="https://unpkg.com/@popperjs/core@2"></script>
  <script src="https://unpkg.com/tippy.js@6"></script>
  <link href="https://fonts.googleapis.com/css2?family=Open+Sans:ital,wght@0,300;0,400;0,600;0,700;0,800;1,300;1,400;1,600;1,700;1,800&display=swap" rel="stylesheet">

Reopen, because this broke the 0.1.2. Needs to also add vendor path to gemspec.


Update package.json

Codecov Report
Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (2bbded1) 93.78% compared to head (0f5de2f) 93.82%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
+ Coverage   93.78%   93.82%   +0.03%
==========================================
  Files          58       64       +6
  Lines         772      874     +102
  Branches      164      182      +18
==========================================
+ Hits          724      820      +96
- Misses         17       20       +3
- Partials       31       34       +3

Files
Coverage Δ

...rc/main/ts/g0101_0200/s0139_word_break/solution.ts
100.00% <100.00%> (ø)

.../ts/g0101_0200/s0141_linked_list_cycle/solution.ts
100.00% <100.00%> (ø)

.../g0101_0200/s0142_linked_list_cycle_ii/solution.ts
100.00% <100.00%> (ø)

src/main/ts/com_github_leetcode/node.ts
94.73% <94.73%> (ø)

...00/s0138_copy_list_with_random_pointer/solution.ts
95.65% <95.65%> (ø)

src/main/ts/g0101_0200/s0146_lru_cache/solution.ts
89.74% <89.74%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feat: create reference links for known token used inside package docs https://next.daff.io/docs/packages/analytics

duplicate of #2474


gb-vendor: purge command fails with golang.org/x/tools/go/loader/testdata package inside vendor/.

In one of my project codebases, when trying to switch a branch for a dependency, I ran:
$ gb vendor delete github.com/go-swagger/go-swagger
$ gb vendor purge

The last command results in:
FATAL command "purge" failed: import could not be parsed: /Users/chakrit/Documents/censored/app/vendor/src/golang.org/x/tools/go/loader/testdata/badpkgdecl.go:1:34: expected 'package', found 'EOF'
FATAL command "vendor" failed: exit status 1

It seems the imports scanner is (corretctly) being overeager in scanning the imports so it picks up a bad test data file that it should not need to care about. So it failed to purge the package.
How to resolve this besides manually deleting those packages (which may have other dependents that I might not know of)?

Will update with a more specific repro later this week if I can.

Thanks. That's the clue I need, itll be fowling on testdata/
This should be pretty simple to fix if you want to try.
On Tue, 11 Aug 2015 19:32 Chakrit Wichian<EMAIL_ADDRESS>wrote:

Will update with a more specific repro later this week if I can.
—
Reply to this email directly or view it on GitHub
https://github.com/constabulary/gb/issues/300#issuecomment-129791203.


[backport galactic, foxy] data_available optimization

see issue https://github.com/ros2/rclc/issues/209
included optimizations in _rclc_check_for_new_data, like handle->data_available = (NULL != wait_set->subscriptions[handle->index]);
The backport on foxy did not work, because:

by removing data_available = false
and in rclc_check_for_new_data the data_available is only set to true, but not to false
=> if in previous iteration the flag was true, then it is not reset.

mergify backport foxy

@mergify backport foxy

Thanks Jan

Codecov Report

Merging #212 (4e37573) into galactic (a7d9b8a) will decrease coverage by 0.17%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##           galactic     #212      +/-   ##
============================================
- Coverage     60.77%   60.60%   -0.18%
============================================
  Files            13       13
  Lines          1499     1495       -4
  Branches        449      444       -5
============================================
- Hits            911      906       -5
- Misses          380      382       +2
+ Partials        208      207       -1

Impacted Files
Coverage Δ

rclc/src/rclc/executor.c
56.07% <66.66%> (-0.38%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7d9b8a...4e37573. Read the comment docs.


how to install on opam 2?

hi
tried the given instructions and says no compiler of that name (due to only looking in the default repo).
so tried this:
$ opam switch create 4.06.1+multicore --repositories=multicore
[ERROR] Could not resolve set of base packages:
The following dependencies couldn't be met:
- ocaml-variants → base-threads
unknown package
how do I get the depended upon packages from one repo while getting the modded compiler from another?
ta.

I came across exactly the same problem.  I think the issue is that with opam-2.0, repositories are associated with switches rather than being globally available, and when you add the remote repository for multicore-ocaml, there is no switch for multicore existing for the repository to attach to.
This is going to make it difficult for any non-default opam repository to offer a custom ocaml compiler.  I got around this by first creating an empty switch for multicore, and then adding the repository to it.  This worked for me:
opam switch create 4.06.1+multicore --empty
opam switch 4.06.1+multicore
opam repository add multicore https://github.com/ocamllabs/multicore-opam.git
opam update
opam install ocaml-variants.4.06.1+multicore
It would be nice if the documentation could be updated for opam-2.0.

Fixed documentation.


Figure out ideal maiingl approach for Canasta

As I understand it, currently Canasta by default does not allow for any emailing from the wiki - you have to set $wgSMTP in LocalSettings.php to get emailing done, via an outside service like Gmail or AWS SES. There is even a set of code in CanastaUtils.php that - if $wgSMTP is not set on the wiki - notifies the user that no emails will be sent, if they're on the page Special:CreateAccount or Special:Preferences (both of which usually generate an email).
It does seem that $wgSMTP is the ideal approach, since it's most likely to produce emails that don't get categorized as spam. But is it a problem that Canasta has this kind of all-or-nothing strategy? If someone forgets their password on a Canasta wiki that has not had SMTP set up, for example, then, as far as I know, they will not be able to log in - since password reset is done via email. (Presumably, they would prefer to get an email in their spam folder than not to get email at all.)
From what I understand, MediaWiki calls PHP's mail() function by default - but the PHP mail() can't be called from within a Docker container. Canasta would have to include some library like Sendmail, Postfix, Exim, etc. in order to do basic mailing. Or perhaps Symfony Mailer - though it's not clear to me if that is a substitute for Sendmail, etc. or a substitute for $wgSMTP. (Or both.)
Clearly, there are a lot of options for mailing. What would the ideal approach look like for Canasta - if the current approach is not it?

Cc @jeffw16, @pastakhov, @vedmaka, @freephile.


Faster compute checksum

Running 2 benchmark(s) for benchmarks/compute-checksum.js
a7ad86f Membership compute checksum benchmark 676 ops/sec
ea0c271 Favor string concatenation over join() 1,706 ops/sec
Benchmark complete!

:+1: good stuff


nixos/hedgedoc: refactor to adapt RFC 42

Description of changes

Hello!
I've deleted most of the option declarations in settings, reducing the line count from ~1000 to ~350 ~300 (thanks Sandro!). Some of them were old and didn't have any effect anymore, and there are also some new undeclared ones.
I'm a little bit unsure about setting the database to sqlite as default, but it has the benefit that you can now only write services.hedgedoc.enable = true, and be up and running in no time.
The systemd unit has also been hardened.
To address some backwards compatability concerns:

A lot of the *Path options where we had overridden the default to point at ${cfg.package}/public/* have been removed, and they have not had any effect since March 2019 in CodiMD 1.3.0. In order for this to affect you, you would have to use an older version of hedgedoc, and not have set the options. If you have a reason to use such an old version while still using the new module, I'd assume you probably know what you're doing (maybe).
I believe there's technically an undisclosed breaking change, where services.hedgedoc.settings.ldap.tlsca has been overriden to default to /etc/ssl/certs/ca-certificates.crt. I do not think this warrants messing around with mkRemovedOptionModule workarounds for submodules.
Deprecating workDir should have limited effect. uploadsPath' default was defined in terms of workDir, but it should still point to the same location. I've added a warning about the case where someone were to override workDir without touching uploadsPath. The other directories which would normally exist here (hedgedoc seems to assume its workdir to be its package), have been overriden to point directly into the package, so there should be no worries about these. HedgeDoc doesn't seem to store anything else here, as the rest is stored inside its database.

I also want to raise the question about when, if ever, we could start removing the name duality in the module, but I think I will leave it as it is for this PR.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[X] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

I've tested the module using nix-build -A nixosTests.hedgedoc and I've also been using the systemd hardening for about a week now. It has been working fine so far.

This has to wait until the next update which is scheduled for the coming days.

This is a bit unclear to me. What exactly is updating in a few days? Hedgedoc?

This is a bit unclear to me. What exactly is updating in a few days? Hedgedoc?

Yes :)

Reopening in light of #246259

Looking forward for this PR !

Okay, so here's the deal.
I've played around with the ofborg eval a bit, and I found out that the reason behind the ofborg eval traces is that the manual itself depends on whether we use the name "codimd" or "hedgedoc" (which again depends on stateVersion). This is bad, because the manual is rendered without anyone setting any stateVersion, and it is also just cursed.
I'll remove the name from the relevant places and just say "hedgedoc" where needed, but I really think we should get rid of the name duality sooner rather than later.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2571

@drupol @SuperSandro2000 Do you have any comments, or do you think the PR is ready to merge?

Is a release note needed?

@Artturin I've now added a release note

@bgamari I'm trying to look into this now, but I'm unable to reproduce it. Would you mind sharing the relevant parts of your configuration, and maybe open a new issue?

Strangely I now seem unable to reproduce as well after having upgraded to the current state of nixos-23.11 as of today.

Actually, I take it back (the server is up, but all of the content is missing). I will open a new ticket.


I would prefer it did not patch, but returned an instance

logger = require('node-console-stamp').console;

This is not my intention with this module. Feel free to fork or even "steal" the code and do it your way, but console-stamp patches console.


Add support for preserving original label in footnotes & omit back links (fixes issue #684)

Added support for preserving original labels in footnotes
Added an option to omit the backlink in footnotes
As a side effect of generating specs, comments in GridTableSpec are also updated

This will resolve issue # 684.

Need to add one more commit to this PR


[Feature] L-shape fitting

New Feature
L-shape fitting for detection and tracking
https://ieeexplore.ieee.org/abstract/document/7995698/

My implementation is from below one.
A. Arya Senna Abdul Rachman, 3D-LIDAR Multi Object Tracking for Autonomous Driving. 2017. paper

I cannot access to the gitlab repo that authors mentioned in the thesis. can you send to me a copy of project?
Thanks a lot

I am not the author for referenced paper.
Please contact the author by yourself.
Thanks!


Add translations to tabs

We use your plugin and noticed that translations were not added. I made a quick fix for this hope you can use it.

Awesome!


Inconsistent Ability of handle_PacketIn to Acquire Multiple Packets from Same Connection

I've been having difficulty getting a program to consistently recognize multiple packets as they arrive at a destination. I've programmed my controller to create and send packets to specific switches and then along specific ports within a predetermined path. All of the packets sent appear to be reaching their destinations, however, the handle_PacketIn event is not raised for every instance and frequently leaves packets unattended when they arrive, ruining my ability to determine if they were successful or not. I cannot use OFP_tables as the switches themselves are the destination, not any hosts within the destination. Any suggestions?
Here is an example of the final readout to check which packets reached their destinations. source and destination correlate to same number switch. Packets are sent to the middle-most switch and then one to the source and destination. Packets are always successfully picked up at the source, but rarely the destination. This also occurs in situations where the packet must be forwarded, with inconsistent results. Networks have been predefined in mininet, and have the following connections.
*** Starting 8 switches
switch_1 switch_2 switch_3 switch_4 switch_5 switch_6 switch_7 switch_8 ...

The culprit was having Spanning Tree Protocol enabled within my mininet configuration. I did this early on to allow the network to function (as it has many, many loops), but this ended up working against me as I need every available path the network offers for my research. Multiple tests have indicated this was the source of my problem and I am closing this issue now. Apologies Murphy for using the issues section like stack exchange.
For future users, I'd advise checking to see if STP is on if you need a fully connected network of paths, and hopefully this will save you someone some trouble.


Add Shodan Command-Line Interface Plugin

Overview

Add Plugin for Shodan Command-Line Interface.
Type of change

[x] Created a new plugin
[ ] Improved an existing plugin
[ ] Fixed a bug in an existing plugin
[ ] Improved contributor utilities or experience

Related Issue(s)

Resolves: #
Relates: #

How To Test

Install Shodan CLI with pip
Run op plugin init shodan
Run shodan info

Changelog

Authenticate the Shodan Command-Line Interface using Touch ID and other unlock options with 1Password Shell Plugins.

@hculea Thank you for your review and suggestions! I have addressed them. Please let me know if the changes are satisfactory or if there are any other modifications I should make.


Update <IP_ADDRESS>:  update STRUMPACK/SuperLU, add FFTX

Sherry,
Please resubmit this PR without including the file ECP-ST-CAR.pdf.


Bug: View on GitHub no longer page dependant

The "View on GitHub" Button/link used to (and should) lead to the relevant individual sub-page on GitHub.
Now it always leads to https://github.com/NFDI4Microbiota/nfdi4microbiota-knowledge-base for all pages I tested.
The mouseover for the "View on GitHub" button still promises to "view and edit this file on GitHub".
I assume that this has been introduced with the changes for https://github.com/NFDI4Microbiota/nfdi4microbiota-knowledge-base/issues/64

The fix has been done

@Xiart
This seems to work for most cases.
Some ( https://nfdi4microbiota.github.io/nfdi4microbiota-knowledge-base/Experimental-Procedure-Standards-SOPs/03-viral-purification-from-bacterial-culture https://nfdi4microbiota.github.io/nfdi4microbiota-knowledge-base/Experimental-Procedure-Standards-SOPs/02-external-sops https://nfdi4microbiota.github.io/nfdi4microbiota-knowledge-base/Experimental-Procedure-Standards-SOPs/01-introduction lead to 404 pages now.

Are you sure, because I can access to all these pages mentioned by you. i.e screenshot below:

It is because, the file name is starting with a capital letter, and all other files in the repository are starting with small letters.
What would you suggest ? should we rename the files?

We can do that. Seems like the quickest solution.
I`ll check if there are any more of those files.

@Xiart @mahdi-robbani So I changed all the filenames containing capital letters to lower case.
However, since the initial opening of this ticket, more files with upper case letter had been added. I renamed them too.
But this shows that we need a systematic solution to this, otherwise we will run into this problem again and again.
Could a check like this be done with GitHub Actions?

I added a action that checks for filenames


Importing issue in React

As I am using React in ES6,
I am unable to import using
var $ = jQuery = require('jquery');
require('./jquery.csv.js');

Found a way to import using
import * as randomName from 'jquery-csv'
Now how am I able to use $.csv.toArrays(csv);/$.csv.toObjects(csv);?

randomName.toArray(csv);
This did work, but now I am getting the following error

TypeError: csv.replace is not a function

How to solve this?


Trigger vs-tab with vs-button?

Is it even possible to trigger vs-tab with vs-button? I have vs-tabs with few vs-tab inside, and that works fine. But I have additional vs-button which I would like to use to trigger one of the vs-tab. I can't find such thing on documentation, maybe it's not even possible?

It possible. You can add :value attribute to your vs-tabs item. And it can be variable. Default 0. If you change to variable also vs-tabs will change.
Like that:
<vs-tabs :value="tabIndex"> </vs-tabs>
And when click the button then tabIndex variable should change
<vs-button @click="tabIndex = tabIndex + 1">Increase<vs-button>

It possible. You can add :value attribute to your vs-tabs item. And it can be variable. Default 0. If you change to variable also vs-tabs will change.
Like that:
<vs-tabs :value="tabIndex"> </vs-tabs>
And when click the button then tabIndex variable should change
<vs-button @click="tabIndex = tabIndex + 1">Increase<vs-button>

For me, this solution doesn't work. 🙁
If a tab was previously disabled (and is currently enabled) a bug occurs that does not allow you to proceed to the next tab.
My actual code:
<form id="tab">
     <template lang="html">
            <vs-tabs alignment="fixed" :value="tabIndex">

              <vs-tab label="One">
                <template>
                  <vs-button type="filled" @click="tabIndex = tabIndex + 1">Increase
                    <vs-button>
                </template>
              </vs-tab>

           <vs-tab label="two" :disabled="two_disabled">
                <template>
                  <vs-button type="filled" @click="tabIndex = tabIndex + 1">Increase
                    <vs-button>
                </template>
              </vs-tab>

           <vs-tab label="three" :disabled="three_disabled">
                <template>
                  <vs-button type="filled" @click="tabIndex = tabIndex + 1">Increase
                    <vs-button>
                </template>
              </vs-tab>

       </vs-tabs>
  </template>
</form>

<script>
let tab = new Vue({
  el: '#tab',
  data: {
    tabIndex: 0,
    two_disabled: false,
    three_disabled: false
});
</script>


CosmosDiagnostics changes from v3.15 to v3.20.1

In SDK version 3.15 we took advantage of the following properties in the CosmosDiagnostics property of the response to record the following key metrics in Telemetry:
"DiagnosticVersion": "2",
        "Summary": {
            "StartUtc": "2021-08-19T19:08:12.8789031Z",
            "RunningElapsedTimeInMs":<PHONE_NUMBER>,
            "UserAgent": "cosmos-netstandard-sdk/3.15.0|3.15.2|01|X64|Microsoft Windows 10.0.18363|.NET Core 3.1.10|",
            "TotalRequestCount": 1,
            "FailedRequestCount": 0
        }

In version 3.20.1 the format of the CosmosDiagnostics json has changed significantly and the TotalRequestCount and FailedRequestCount are no longer there.:
"name": "CreateItemAsync",
    "id": "4ac11b57-5103-4a83-8c30-d19e0acb921d",
    "caller info": {
        "member": "OperationHelperWithRootTraceAsync",
        "file": "ClientContextCore.cs",
        "line": 219
    },
    "start time": "07:17:13:399",
    "duration in milliseconds": 8423.9044000000013,
    "data": {
        "Client Configuration": {
            "Client Created Time Utc": "2021-08-19T19:09:18.3183366Z",
            "NumberOfClientsCreated": 1,
            "User Agent": "cosmos-netstandard-sdk/3.20.1|3.19.3|1|X64|Microsoft Windows 10.0.18363 |.NET Core 4.6.29321.03|S|",
            "ConnectionConfig": {
                "gw": "(cps:50, urto:10, p:False, httpf: False)",
                "rntbd": "(cto: 5, icto: -1, mrpc: 30, mcpe: 65535, erd: False, pr: ReuseUnicastPort)",
                "other": "(ed:False, be:False)"
            },
            "ConsistencyConfig": "(consistency: NotSet, prgns:[])"
        }
    }

I would really like for those two properties to be put back.  If not, is there another way we can get this information?  For example by aggregating the retry counts on one or more of the Request Handler child objects if it exists.  That would allow us to derive the data to meet our requirements.
Thank you,
Steve

Related PR: https://github.com/Azure/azure-cosmos-dotnet-v3/pull/2584


Add tree view example

This adds a performant tree view example by a popular request.
Answers http://stackoverflow.com/questions/34981924/performance-issues-with-a-tree-structure-and-shouldcomponentupdate-in-react-re.

This is fantastic. :+1:

Agreed, this example covers so much :smile:

Nice example, I'm wondering tho how an action affecting the entire state would be handled? For example removing a node, which in turn affects the entire tree?
I need to get my head around this for optimization purpose, I did encounter performance issues with a somewhat big tree of data.
Say for example I have a <Selected /> component that stores added items from a list, when added it shows up in the Selection component, but in the list shows as "added", and vice-versa. How would that need to be handled in the tree-view example?
Really appreciate you taking the time doing an example for this by the way, thanks!

A great enhancement to this example would be removing node and moving nodes.

I'm happy to accept a PR for removing node. Would you like to work on this?

Nice example, I'm wondering tho how an action affecting the entire state would be handled? For example removing a node, which in turn affects the entire tree?

Why does removing affect the entire tree? Seems like it would only affect the removed node's parent (and, of course, its children, but they would just get unmounted).

There are three possible ways, I see, for removing a node, assuming that you want to remove all of its children from the store...

Actually keep the data in a tree structure in the store, so removing a node object automatically removes all its children, which it contained.
Maintain the flat structure and give them string ids like '<IP_ADDRESS>' so that the reducer can just remove all ids that start with the removed node's id.
Maintain the flat structure and depth-first iterate on the removal through all the child nodes.

I did #1 in my redux-form library, which added much complication. I think I'd recommend #3 for this example.

Here's a method I used to remove nodes on my own project (uses Immutable.js) but using the same flat structure:
const parentIds = state.get('tree').reduce((result, item) => {
    if (item.get('children').includes(action.id)) {
        result.push(item.get('id'));
    }
    return result;
}, []);

parentIds.forEach(id => {
    const path = ['tree', String(id), 'children'];
    path.push(state.getIn(path).findIndex(i => i === action.id));
    state = state.removeIn(path);
});

return state.removeIn(['tree', String(action.id)]);

Basically what happens is that we run through all nodes and get the id's of where the removed node is a child, then we loop over all these nodes and remove the reference. Finally we remove the actual node.

Maybe my data structure is what's confusing me here. I looked back at the example and noticed the multiple connect()ed components instead of only one HOC. I always thoughts this was best practice, so basically what I've been doing is connect the entire state to the top-most container, and then pass along state and dispatch to the children as props:

class FilesDownload extends Component {

  render() {
    return (

            <Selection {...this.props} />

            <Filters {...this.props} />
            <Results {...this.props} />

    );
  }

}

function select(state) {
  return state;
}

// Wrap the component to inject dispatch and state into it
export default connect(select)(FilesDownload);

Here's an example Gif of the actual app, you can see the delay when I first click on the "add to selection" button:

Node Removal PR #1274.

Ah yes thanks @erikras I will look at the PR for reference. Merci :smile:

I always thoughts this was best practice, so basically what I've been doing is connect the entire state to the top-most container, and then pass along state and dispatch to the children as props:

Yeah, we no longer recommend single top container in favor of a more gradual approach. See the updated<EMAIL_ADDRESS>

Yes thanks for the reminder, as I tweeted earlier (tweet which you "liked") I'm slowing getting the hang of this. It's really starting to make sense now with Presentational and Container Components.
Perhaps, with my example above, I should have a connect() container for each selectable items (CAD Drawing, Install Drawings etc.), what's your thoughts on this?

Perhaps, with my example above, I should have a connect() container for each selectable items (CAD Drawing, Install Drawings etc.), what's your thoughts on this?

Yes, I think this can work fine.

:+1: Merci beaucoup mon ami !


YARN-11389. Upgrade spring-core to 5.3.20 in wro4j-maven-plugin

Description of PR
How was this patch tested?
hadoop-yarn-ui build sucessful
No spring 3.1.1.RELEASE jars were downloaded during build.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+0 :ok:
xmllint
0m  1s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
38m 10s

trunk passed

+1 :green_heart:
compile
3m 58s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
3m 48s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
mvnsite
0m 43s

trunk passed

+1 :green_heart:
javadoc
0m 34s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 23s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
shadedclient
67m  1s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 15s

the patch passed

+1 :green_heart:
compile
3m 23s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
3m 23s

the patch passed

+1 :green_heart:
compile
3m 39s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
3m 39s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 31s

the patch passed

+1 :green_heart:
javadoc
0m 14s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 14s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
shadedclient
21m  5s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
4m 30s

hadoop-yarn-ui in the patch passed.

+1 :green_heart:
asflicense
0m 54s

The patch does not generate ASF License warnings.

103m 21s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5192/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5192

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux 26147d56425b 4.15.0-200-generic #211-Ubuntu SMP Thu Nov 24 18:16:04 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 74817d0a17b1fff0a7c7fd6251dc38055835842f

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5192/1/testReport/

Max. process+thread count
558 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5192/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

i think the maven plugin itself should be upgraded, rather than trying to add new dependencies (and do the old ones get excluded? how do you guarantee the new ones get picked up?). what happens later when an upgrade does take place? will we remember to remove what may then be older dependencies
this is a compile time issue only, no cve in any redistributables, so hard to justify creating classpath/version hell for.

Thanks @steveloughran for the review,
I agree that spring version upgrade should come with the plugin, I tried upgrading the maven plugin to the latest available version of 1.10.1, it still has the vulnerable spring version of 5.3.1
I can a comment similar to https://github.com/apache/hadoop/pull/421 to ensure that the spring dependencies get removed in the later versions of plugin upgrade.
We are adding spring as the first level dependency for the plugin, whereas the existing spring is coming from the second level of dependency. Maven ensures that the nearest level of dependency gets picked up.

HI @steveloughran
As @dmmkr mentioned updated maven plugin doesn't fixed this and as handle on #421 this change should be ok.
Approach looks good to me now.
Please let me know your thoughts.


Obtaining MSA data

Hi,
Is there anyway to get the MSA data from the text-based files?
Thanks in advance

Hi, the MSA data is too large to have available as a direct download. However I have a Globus endpoint set up for direct transfer. Feel free to contact me through email and I will send you the instructions. Right now it's just ProteinNet 12 that's available.


Bug/149199523 unique uuid for calls made from Resque [#149199523]

Problem
Nicola filed an issue against Log Weasel where she was seeing static Log Weasel transaction IDs across multiple requests - which shouldn't happen. Each unit of work should be given a unique UUID, whether the work begins with a web request, API request, or a Resque job (scheduled or delayed). Additionally, Pwwka message handlers need to be able to pass along this UUID to processes kicked off in the handler (like a Resque job) so the transaction ID can be threaded through to all parties involved in processing the unit of work.
Findings
I did a holistic reevaluation of Log Weasel, and found several issues:

LW transaction IDs for delayed Resque jobs (handled by Resque Scheduler) were not being properly set/managed.
There was no real LW support for Pwwka to pass along the LW transaction ID to processes kicked off in the message handler.
There was some inconsistency in the way the LW ID was being managed for Resque jobs.

Solution
I addressed all of my findings (above). Still working on getting supporting tests written/passing, but wanted to get some early feedback on this. There is quite a bit of Ruby "magic" here, so ideas on how to make it less magical would be welcomed.

Also, this is super exciting!  This will let us get visibility we've never had before! 💯

I think I follow most of this, at least at a high level. How can we test this?

Yep, staging will be first. Then I was thinking about trying it out on Hellblazer, like last time. Or maybe we could try it on Spectre (convenient that it is still on Heroku)? It would be nice to prove that it solves the issue Nicola reported. @davetron5000 what do you think?

Yeah, that sounds good.  Maybe you just voluntold @nicolaa to help monitor? :)

@brettfishman thanks for doing this; happy to help test as well.

Opened a PR against Spectre to test: https://github.com/stitchfix/spectre/pull/1438

@nicolaa / @pdudek / @davetron5000 - unless there are objections, I plan to merge this to master and release a new version of Log Weasel later today. Seems like the latest rc is doing well in Spectre.

Awesome!


Pose Estimation Code with Readme

Readme File Updated
Pose Estimation File with all tested scenario
Models link file added

Hey @Tushar-ml, please go through the Contributing Guidelines.
We are only accepting implementations in .ipynb form.

hey @geekquad ,Can I work on this issue under GSSoC?


terms of use spans 2 lines on review page of dc create

The following picture shows that on the revision page of the dc create wizard, terms of use spans two lines. This should be on one line:

Did you intend to take this for the hotfix?

This is in the extension so isn't something we'd consider for the hotfix anyways.


Add missing beta docs to Policies section

Summary

Charly let me know that we were missing the following two docs in the Mesh nav that currently exist in the Kuma nav:

https://kuma.io/docs/2.0.x/policies/meshaccesslog/
https://kuma.io/docs/2.0.x/policies/meshtrafficpermission/

I added these docs back in and double checked that no other docs were missing from the nav.
Reason

Docs existed in Kuma nav but not Mesh nav.
Testing

Check that the following pages work in the Netlify preview:

/policies/meshaccesslog/
/policies/meshtrafficpermission/

Re: failing checks: rebase on main to fix the linting check. The smoke test one is flaky, so it'll hopefully pass on the rebase.

This update LGTM, but it raises another question: does the Mesh team know that these policies are missing from https://kuma.io/policies/? As a followup, we should add them there and to https://docs.konghq.com/mesh/latest/policies/.

Good catch! I asked Charly about it and he said they shouldn't be listed there because they are "meant to replace existing ones". So once they are out of beta, I think they'll replace the existing ones.


Control events for ball_save

Allow to add time using an event

We can use timers for this. Moved to: https://github.com/missionpinball/mpf-docs/issues/80

https://groups.google.com/forum/m/#!topic/mpf-users/fl1xKaCmRe8


add radix sort in javascript

Have you read the Contributing Guidelines on Pull Requests?
yes
Description
Added radix sort in javascript
Checklist

[x] I've read the contribution guidelines.
[x] I've checked the issue list before deciding what to submit.
[x] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#6447

@ankitaggarwal23 , @bhav09 , @anushkrishnav kindly review the PR


setstate not persisting but only not everytime

i been having an issue where the set state isn't persisting after the bot is turned off and on again i have attached a screenshot of the issue. it seems to persist fine when i activate the bot using npx robo dev but when i activate the bot using npm run dev the states never persist?

Thanks for reporting this! We'll be releasing a patch fix shortly.


Do docker push from wercker build

This change does docker push of wercker build results.  Also runs coverage tests.


Adjust coinbase amount

Description

As I explained, I just misunderstood that the total amount of coinbases are fix already.
But I've refactoring some of methods and adjust the total amount to be about<PHONE_NUMBER>00000.
https://github.com/SushiChain/SushiChain/pull/174
The reason of<PHONE_NUMBER>00000 is that since we haven't token denominations currently(#95), the amout should be enough.
So I roughly decided the value.
By using tools/total_amount.cr, the results are
Total amount :<PHONE_NUMBER>00700[SHARI]
Last index   : 11283792

Related Issues

https://github.com/SushiChain/SushiChain/issues/172

Checklist

[x] Fix specs
[ ] Every CI jobs finished successfully

Note
This change is totally breaking. So current blocks on testnet will be rejected from then.
So we have to announce before the deployment.

100_000_000_000_700 = 100 trillion? Is that correct?

yup that seems to be 100 trillion :)

The circleci specs E2E failed - but I can't seem to restart the failed one - I think it's just intermittently unstable and when run again will pass - but I don't have enough permissions to restart it.

@tbrand maybe you can get the E2E spec to pass and then merge it - and let me know and I will re-deploy

a side effect of this is that after about 10 mins of mining my wallet looks like this:
  + -------------------- - -------------------- +
  |                token |               amount |
  | -------------------- | -------------------- |
  |                SHARI |             22567582 |
  + -------------------- - -------------------- +

I just mined over 22 million SHARI in a very short time. I guess it's relative because the total is 100 trillion. But seems a bit strange to me. It also means the fees seem way too low in comparison:
  + -------------------- - -------------------- +
  |               action |                  fee |
  | -------------------- | -------------------- |
  |                 send |                    1 |
  |            scars_buy |                  100 |
  |           scars_sell |                   10 |
  |         scars_cancel |                    1 |
  |         create_token |                 1000 |
  + -------------------- - -------------------- +

I'm gonna never need to ever mine more than half an hour - and I can pay for all kinds of actions for years to come lol !!!

Yeah we should adjust  the fees then.

@kingsleyh Additionally, as a breaking change, I moved sign_r and sing_s columns from transaction to senders.
So please deploy after merging https://github.com/SushiChain/SushiChain/pull/177.

I fixed the specs but the E2E seem to be failing - I can’t re run them on circle - could you check and when they are passing do the merge and I will continue with the other PR

got it

Now all specs are fixed


Update build instructions to use gradle wrapper

Replaced gradle build with ./gradlew build as gradle build was giving build error for gradle version 7.1.1

@reinecke we can merge this

Welcome @jradha11! Thanks for your contribution! Because we are part of the OpenTimelineIO project, we ask that you complete a contributor license agreement: https://opentimelineio.readthedocs.io/en/latest/tutorials/contributing.html#contributor-license-agreement
Once you've submit that, we can merge your addition!

Hi @reinecke ! I have mailed my signed CLA form.

Received and filed, thanks for contributing!


Assistant langages

Hi,
Is there a way to set another language for the assistant (snowboy) ? The language settings seems to be only for commands.
KR

New API could do that. It was released a month ago. I'll update in a few days or weeks. (Sorry, I should do my real life job first before this.)

Yes, I've seen it, the google-assistant seems to do it from new config parameters in release 0.2.x. I will try to do it, but I am not confortable with node, so if code needs to be modified, I will probably fail !
Regards

Hi eouia,
I've upgraded the google-assistant version to 0.2.2, rebuild all the stuff, and do the following modification and it works fine in french :
config.js
           assistant: {                 auth: {                     keyFilePath: "/home/pi/MagicMirror/modules/MMM-Assistant/secret.json", //When you want to change the location of this file, set this.                     savedTokensPath: "/home/pi/MagicMirror/modules/MMM-Assistant/resources/tokens.js", //When you want to change the location of this file, set this.                 },                 conversation: {                     lang: 'fr-FR',                     audio: {                         encodingIn: "LINEAR16", //Ignore this. I think you don't need to change this.                         sampleRateOut: 16000, //Ignore this. I think you don't need to change this.                     },                 },             },
node_helper.js: line 229
const assistant = new GoogleAssistant(this.config.assistant.auth)
node_helper.js: line 246
             = spokenResponseLength / (this.config.assistant.conversation.audio.sampleRateOut * 16 / 8) * 1000;
node_helper.js: line 307
sampleRate: this.config.assistant.conversation.audio.sampleRateOut,
node_helper.js: line 321
assistant.start(this.config.assistant.conversation)
The default config will probably need to be updated too.
I did not want to update your code.
Thx

Very thanks to your experimental trial. I'll reference your code in my next update. Thanks again.

@normyx  Can you enclose that code in proper code tags, triple back-ticks (```), please?

This is implemented by PR https://github.com/eouia/MMM-Assistant/pull/29
We need to check and merge.
@eouia  Can you test it?

Implemented in todays commits.


⚠ Bofrost.lu has degraded performance

In f49f996, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1249 ms

Resolved: Bofrost.lu performance has improved in 7362b59 after 6 minutes.


fields_updated is always 0 for HIL_SENSOR message

It seems that all HIL_SENSOR sent by jMavSim has fields_updated  set to 0. According to MavLink specs, this should mean that all fields other than linear acceleration should be ignored. Is this correct interpretation and behaviour? If so then gyro fields in HIL_SENSOR should not be having any effect...

Update: @lovettchris looked at the firmware code and found that it simply ignored fields_updated. So we have two issues:

jMavSim doesn't set the correct value
Firmware ignore all values

Probably outdated, closing.


Fix WYSIWYG text + image paste

This PR fixes #13454.
It fixes when a user copied both Text and images, and we now convert the image link properly (similar to how we did it in the October release of ADS).

Pull Request Test Coverage Report for Build 382180080

6 of 8 (75.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 41.211%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/notebook/browser/htmlMarkdownConverter.ts
6
8
75.0%

Totals

Change from base Build 382163436:
0.003%

Covered Lines:
21803

Relevant Lines:
48556

💛  - Coveralls


TestFailOnceActivityInterceptor on master

same as https://github.com/sclasen/swfsm/pull/55 but against master

:+1:

I'm looking into failures with this branch on -control. Do not merge yet.

Closing in favor of https://github.com/sclasen/swfsm/pull/58 for now


Add a new import group - style files?

Hi!
I think it makes sense to make style imports a separate group in imports, so CSS and LESS won't be mixed with 'code' imports.
E.g. we can have
import foobar from './foobar';

import styles from './styles.css';

Thoughts?
(it can be supported if #674  is done)

Style imports aren't a standard part of require, so reifying that here seems problematic.

Ok, I guess then we should move towards regex.


Add better ClearML parse logging info

Related to https://github.com/sillsdev/serval/issues/462.  Couldn't find the root issue, but this should hopefully lead to better logging of the errors we are getting from ClearML to see what we are actually getting back.

This change is

Codecov Report
Attention: Patch coverage is 43.75000% with 9 lines in your changes missing coverage. Please review.

Project coverage is 56.65%. Comparing base (1e08f4f) to head (322b35f).

Files
Patch %
Lines

...c/Serval.Machine.Shared/Services/ClearMLService.cs
43.75%
9 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #463      +/-   ##
==========================================
- Coverage   56.67%   56.65%   -0.03%
==========================================
  Files         275      275
  Lines       14120    14133      +13
  Branches     1895     1895
==========================================
+ Hits         8003     8007       +4
- Misses       5532     5541       +9
  Partials      585      585

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Adding places data?

Hey,
Thanks for sharing this repo!
Can you add the textual description of each patient's route, including the places they had been to?
For example, it can be an un-parsed string of "13:00-15:00 Restaurant X, 15:00-17:00 Hotel Y"
Thanks!

Hey,
We don't deal with that kind of information, but you can find it in this excellent repo


Fixed possible NullPointerException

Added null checks, extra annotations, and a test case.
Closes #378

@magneticflux- If there aren't any changes more, I will merge this by Friday evening.
Thanks for reviewing it.


Add drain thread

Pull request for just the drain thread without the updates to unit tests, emulators, etc.

@goughes, Eric this seems to be working better. Sorry my code cause this problems. I think we will deal with the unittest later.
Could you fix Python3 compatibility warnings in separate commit. I will merge the code and update wmagent branch after that.

These python3 warnings are @amaltaro 's to fix.

Bored of creating bugs, so I decided to break py3 compatibility too :-P

test this please

test this please


JS: How to lower the silent delay in TTS?

As title, every Text-to-speech audio have about 2 second of silent. How can I lower the value or remove completely?

@yulin-li Could you answer this question?

Hi @Naozumi520 could you please use mstts:silence tag with type of Tailing-exact to specify the tailing silence of the synthesized audio?
Refer to this doc

Yes, it's working! Thanks!


Different Country shipping address vs Registered VAT No Country

The current edition, compared to the old edition, allows delivery to another country than the billing address.
It is not normal that the customer can select a different delivery address other than the selected VAT number Country from the billing address and still have VAT deducted. For instance a customer with the valid VAT number registered in France can select a shipping address in Spain and the VAT is deducted.

We only check the VAT if it's not the same as the country of origin (set in the module settings).
So according to the intra-community supply law you can only send it tax free if it is not in the same country as you send it from. The module provides a extra option to automatically put VAT validated customers into a specific customer group. But this customer group does NOT have any extra logics attached. The extra customer group selection is hereby only for your own administration

According to the intra-community supply law, the shipping address is leading. This means if you have a valid VAT number for the shipping address but the invoice address is in your country of origin it's still correct to deliver tax free.
This goes both ways, if you have a company abroad, but the shipping address is in the country of origin you can not deliver without tax.
(if you do not agree, please refer to some links for documentation)

OK, great. Thank you for your fast answer.


Refactored some of TextMetrics tests so that they pass on Windows

Description of change
Refactored some of TextMetric tests so that they pass on Windows.

I've allowed myself to leave a comment at the top of TextMetric class about the fact that the text may render (and measure) differently on different platforms.
One failing test required changing the expected width, because exercitationem renders to about 217px making it impossible to fit in the requested 200px. This shouldn't invalidate the test on different platforms, because breakWords was set to false either way, so on other platforms it just rendered to a smaller dimension already. Also the test's goal is to check if the width is not exceeded by stacking >1 word in the line, not by a word too long.
Two other tests I refactored to be 2 tests each, one part being stuff that works the same across all platforms (trimming whitespace) the other part being stuff that depends on how things are rendered (checking exactly how things break).

Pre-Merge Checklist

[X] Lint process passed (npm run lint)
[X] Tests passed (npm run test)

Referenced issue: #6247

Codecov Report

Merging #6248 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #6248   +/-   ##
=======================================
  Coverage   76.71%   76.71%
=======================================
  Files         202      202
  Lines       10238    10238
=======================================
  Hits         7854     7854
  Misses       2384     2384

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 52df29c...d8ba20f. Read the comment docs.

And the output on my machine after I run the test suite with these changes.

Its something about DPI, I don't remember exactly. I agree, lets just skip it in windows, we can fix cross-platrom way later.

Thank you @EvidentlyCube!


Auto startup?

Issue
Is there auto startup?
Describe your issue, comment or suggestion
I have everything working perfectly fine, but once reset or sleep the keyboard defaults to standard. Is there any work around to this at all?
Thank you again for all of this!

It would be easier to get https://github.com/stevelacy/msi-keyboard to run at startup with a preset color scheme.
https://askubuntu.com/questions/228304/how-do-i-run-a-script-at-start-up
I will eventually add persistence to this project which will enable it to remember the last setting upon start, and thus just starting the application on startup will re-enable the keyboard colors. #3

Same question for Windows 10, I've got it in Startup and windows pops up the window, can I get it to apply a preset color scheme at startup without seeing the window? Like with regedit  -hidewnd or something?

Eventually, I don't use my MSI much anymore, but for startup I was considering linux first. Not sure what would be needed for full windows startup support.
But config saving is the first item needed, then re-syncing with the config and applying it on startup.

For autostart on Windows - I simply created a task in the Task Scheduler, triggered on "On workstation unlock of any user" event. Also changed "Conditions" to work on battery too. Whenever I log in it starts msi-keyboard-gui.exe.
I think autostart isn't that big problem as auto-applying settings. If it worked, we could simply create a VBScript which could run it hidden (without displaying a window), a perhaps quit after few seconds.

if you can make it so checking a box will auto-enable/disable that on windows and linux I will merge it

I'm sorry, but I'm worried I'll be unable to do it with Node.js any soon (need to learn it, and soon sending laptop for repairs) :(
Maybe it would be faster if I wrote a tutorial how to do this, on Wiki page?

uhh, for the startup thing, could you just have a little script that runs at startup. That script runs the app without any graphics then exits the app. saving the colors you can just use a text file with hex color numbers or predetermined numbers to denote each color. overwrite the file every time you save and read it on every startup. Idk how file IO is on node.js but i asume its not super complicated. the hardest part will probably be startup script but bash is pretty straightforward and powerful.
just sharing ideas, not telling you how to build your code.

i'm going to see if this works, but on linux I think something like this will work to make it run at startup
"sudo ./Downloads/msi-keyboard-gui-linux-x64/msi-keyboard-gui && pkill msi-keybaord-gui"

FYI: this alternative has a nice way of handling the autostart https://github.com/Gibtnix/MSIKLM
You may want to copy that udev handling in linux, just give attribution to the original author for that. But thats pretty sweet because it only fires if the device is detected.


Allow sorting by Stars and Forks fields

The default sorting is by last updated commit date so users can view the most recently updated project. But sometimes users might want to view popular (stars) or most forked projects. Allow the user to specify a sort parameters when running a discover projects command.

Implemented sorting


Allow configuring if agent can see through walls

Currently the agent can see through walls by default.

Should the agent be able to see only in cardinal directions, like an orthogonal projection where perspective lines are all parallel, or with a traditional perspective? I made the following not-to-scale representation of the view to illustrate the difference. Orthogonal perspective would be easier to implement, but the traditional perspective would be more interesting and realistic.

Good question.
I prefer the latter.
This may be useful to you if you want to make an attempt to implement it:
https://github.com/maximecb/gym-minigrid/pull/98/files

The occlusion described in that pull request modified the bidirectional orthogonal occlusion present to allow corners to cast shadows, but that still does not create a system where occlusion can involve angles other than cardinal directions. I have a handful of approaches I'm thinking about to create a system which can incorporate viewing angle, but they all would contribute not-insignificant overhead before some optimizations I have in mind, and more than likely after them.

using polar coordinates of the corners of opaque objects to describe a region of θ where points with r greater than that of the obstruction are not visible, and generating a mask based on this to adjust the final output. This is currently my favorite idea because it seems interesting to implement and is probably most efficient, although it would depend on the relative speed of asin(), as it or acos() would need to be called for every point in the view radius. However, I expect the built-in arcsin approximation is probably far more precise than we would need for such a coarse grid, and a handful of terms of the Maclaurin expansion for arcsin would probably provide more than enough accuracy with very little overhead.
using a recursive method or iterator to forward ray trace from each point on the perimeter of the view radius to the agent, and hiding points which were not traversed by a ray which reached the agent. This would be relatively straightforward to implement, but seems very inefficient.
for static environments, pre-baking all the occluded areas for any given location using the recursive/iterator method, and referencing the mask for a given coordinate (x,y) to determine which points should be obstructed. This has the potential to be fast, but could be overkill and would really only be beneficial for environments where one world is used for an extended period of time without changing.

Hi @landrumb

I have a handful of approaches I'm thinking about to create a system which can incorporate viewing angle, but they all would contribute not-insignificant overhead before some optimizations I have in mind, and more than likely after them.

Awesome! I think non-insignificant overhead is inevitable and acceptable.
We can start from the first approach. The size of the agent's view is usually relatively small. We can compare the efficiency with the second approach. My intuition is that, the second approach doesn't seem to be very inefficient.
The third approach also looks charming. As you said, it may be useful in statical environments. I think we can lazily cache the mask of the agent's view in this case.

@findmyway I have an implementation working at least close to what I'm looking for, but I'm having a hard time incorporating it into get_agent_view!() because I don't fully understand its arguments and by extension its logic. p::CartesianIndex and dir::LRUD are intuitive, and I'm reasonably confident that v::AbstractArray{Bool,3} and a::AbstractArray{Bool,3} represent the view and grid respectively, but I don't know how to find where there are opaque objects using those arguments.
Obviously, transparency has to be implemented on objects, which I have not done, but it seems like the best way to do transparency may be with an attribute, as certain objects like doors can be conditionally transparent or opaque.
If you'd like to see what I have so far, it's on branch landrumb-issue-30 on my fork, or I can just open a pull request.

Obviously, transparency has to be implemented on objects, which I have not done, but it seems like the best way to do transparency may be with an attribute, as certain objects like doors can be conditionally transparent or opaque.

Currently the door has only two properties: symbol, color. We can add another field like open or closed as a type parameter just like the color.
get_agent_view_inds will get the indices of the agent's view box from top-left to bottom-right. Then ind_map will rotate the result from get_agent_view to put the agent in the top-middle position.
Then we can get all the opaque objects' mask by changing the get_agent_view! slightly:
https://github.com/JuliaReinforcementLearning/GridWorlds.jl/blob/f46e78c3ff224039adb42a3362edee5c8a053428/src/grid_world_base.jl#L84
Here, we need to change the variable v into a 2d Matrix m and add a function is_opaque:
o = findfirst(w[:, inds[ind]])
m[ind_map(ind.I, view_size, dir)...] .= isnothing(o) ? false : is_opaque(w.objects[o])

Hi @landrumb
Is there anything I can do to help to add this feature? 😃

@findmyway I was busy yesterday and haven't gotten a chance to sit down and try to incorporate it into get_agent_view(), but I should have time today and/or tomorrow. I think I'll be able to handle it, but I'll let you know if there's anything I need help with.

@findmyway I've overestimated my ability. How do I get the object at a given index from the Bool arrays passed to get_agent_view? You use w in the code in your comment, but does that mean I need to add the environment as an argument to get_agent_view?

Yes, and note that WordBase is a subtype of AbstractArray.


Inverted and SVGs

If an SVG is inside of div that is set to inverted, it unfortunately does not get set to a fill of white.
Example:

for chapstick, we handle this in static/style/foundation/components/_icons.scss:6 with  @mixin _iconColor( $color, $invertedColor )
It makes sense to set a global default for the fill property in SQ, though...


Support adding EC2 hosts in a single UI dialog in multiple subnets

EC2 supports the creation of VM into multiple zones via the same subnet.  Rancher's current UI does not support this as it would be nice to not have to keep going through the entire dialog to add machines in different zone/subnet combination.

Closing due to inactivity.


Programmatically access breakpoints?

I've used a variety of hacky methods to access the currently active breakpoint from Javascript (e.g. v-b-visible).  Is there going to be a "right" way to do this in bootstrap-vue-3?
Thanks so much to everyone working on this.

was this an original way of doing this in Bootstrap-vue?

I didn't find a standard built-in way of doing it in Bootstrap Vue, or raw Bootstrap, though that doesn't mean that there wasn't one.
That might mean that we're not doing it, of course, but I want to check that I'm not missing something that everyone else knows about.

there ain't one. But you can create it with yourself.
for example: https://vue3-mq.info/configure/presets.html
has preset of bootstrap default breakpoints.
Notice that breakpoints are display rules for css and aren't "readable" (you'd have to parse the whole css file.). They can also be customised in bootstrap scss.

Ok.  What I did was this:
<template>

</template>

oh, that is a nice way of doing it! Didn't think of that.
the breakpoints have some differences in bootstrap5, but that could work with small changes.

Just for fun I did a component and a composable for that idea:
https://stackblitz.com/edit/vitejs-vite-qbxaoh?file=src%2FApp.vue&terminal=dev

What about https://vueuse.org/core/usebreakpoints/#usebreakpoints?

@cdmoro That looks like the kind of thing.  Thanks.

vueuse is also a good option. It's also based on predefined breakpoints: https://github.com/vueuse/vueuse/blob/main/packages/core/useBreakpoints/breakpoints.ts#L19-L25