Question regarding document deletion and browseClass

Hi!
I have a question regarding browseClass and deletions in Orient document database.
browseClass seems to find the document even after I have deleted it.
So if I have
ODatabaseDocumentTx db;
for (ODocument doc : db.browseClass("Person")){
..
}
will throw me an Illegal Argument exception, which is ok.
However, when I save the document like the following
final ODocument document = new ODocument("Person");
document.field("state", value);
document.save();
and delete like the following:
for (ODocument doc : db.browseClass("Person")){
db.delete(doc);
}
and then browseClass the same thing again, which should give me an IllegalArgument exception just like the above,
for (ODocument doc : db.browseClass("Person")){
..
}
instead of throwing me the exception, it simply does not go into the for loop.
My guesses are as follows:

browseClass is not the proper way of getting the document from the db, or I am using it wrong.
(I expected something like db.get("Person"), which there were none.)
Even after deletion, the fact that "Person" was previously saved, remains in the database somewhere, and browseClass does not throw an exception, it merely goes past the for loop.

I want my deletion to delete "person" properly so I do not have extra data that fills up space.
How do I perform this kind of deletion?
Thanks in advance!

Hi @bokyoungbin
could you please post your code? My guess is that you are having problems because of how you are using transactions...
Thanks
Luigi

@Override
public  boolean set(final Identifier identifier, final I value){
try {
for (ODocument doc: db.browseClass(identifier.toString())){
if (doc.containsField("state")){
doc.field("state", value);
doc.save();
return true;
}
}
final ODocument document = new ODocument(identifier.toString());
document.field("state", value);
document.save();
return true;
} catch (Exception e) {
try{
final ODocument document = new ODocument(identifier.toString());
document.field("state", value);
document.save();
return true;
} catch (Exception f){
f.printStackTrace();
return false;
}
}
};
@Override
public <I> I get(final Identifier identifier){
    try{
        for (ODocument doc : db.browseClass(identifier.toString())){
            if (doc!=null){
                return doc.field("state");
            } else{
                return null;
            }
        }
        return null;

    } catch (Exception e){
        e.printStackTrace();
        return null;
    }
};

@Override
public boolean delete(final Identifier identifier){
    try{
        for (ODocument doc : db.browseClass(identifier.toString())) {
            db.delete(doc);
            return true;
        }
        return false;

    } catch (Exception e){
        return false;
    }
};

These are my get, set, delete codes.
Then I just use them like this:
orientdb.set(id1, value)
orientdb.get(id1)
orientdb.delete(id1)

@luigidellaquila Hi! I still can't seem to fix this issue. Is there something wrong with how I've used orientdb?


Wip tobin gh643 fb valid usage

WIP of CreateFramebuffer validation checks. Still need to enable 1 more check and add a couple of tests, but putting this out for early review.
My current main concern is whether or not I'm doing the dimensions check correctly.

Created #683 which addresses review feedback and finishes up adding valid usage checks and tests.


If executing command than DQL, return result instead of no data prompt

Is your feature request related to a problem? Please describe.
While executing command other than DQL, no data prompt is shown. As instead success or failure result should be shown.
For example:
GRANT SELECT ON OWNER.TABLE TO ANOTHER_OWNER;
Returns query output:

As instead DML output should be returned like: Script executed successfully

@dnlw07  Can you provide more details about this?
Examples, screenshots and an expected behavior?
Which driver are you using?

comment updated

Hmm, I see. That's something very annoying. The message is there, but hidden in the message panel ;p

Oh good to know! ;)
It's not that much annoying, but in the beginning when I started working with the extension, I got an impression that scripts other than DQL are not executing properly.


25Hz Test Content labeled with 15_30_60 in database.json

The 25Hz Splicing Test Content in database.json (e.g. https://github.com/cta-wave/Test-Content/blob/master/database.json#L1646 ) is labeled with .../15_30_60/... (JSON IDs, zipPath, mpdPath). @rbouqueau can you check it please.

Thanks @louaybassbouss , should be fixed. I let you close if ok.

Thanks @rbouqueau closing this issue.


Root Users are not given full list of organizations

Background
An individual identified as a root user in Tower has full edit/view permissions for Organizations, Workspaces, Users, and Teams via the Tower console.
This level of access does not appear to be the case when using the CLI. When a root user runs tw -o json organizations list, the response provided appears to be populated only by those Organizations which the user is directly affiliated with (as an Owner/Member).
How to reproduce

Stand up a blank Tower instance.
Create two users:

UserA is a root user
UserB is a non-root user

Create three organizations:

OrganizationX
OrganizatinoY
OrganizationZ

Assignments:

Make UserA an Owner of OrganizationX
Make UserA an Owner of OrganizationY
Make UserB an Owner of OrganizationZ

Configure tw access for UserA
As UserA, run tw -o json organizations list. You'll note OrganizationZ does not appear.

Hypothesis & Suggestions
I believe root user API calls run through a different set of APIs than the general organizations / members / workspaces / teams commands. Assuming I'm correct, tw should either:

Offer a root-user centric menu option; OR
Offer an additional flag to identify the activity is being run with a root-user persona rather than general Tower user; OR
The target Tower API logic should be modified to check if the caller is a root-user and structure their responses appropriately.

The command works as expected (not a bug): tw organizations list returns those organizations where the requester user is a member in a similar vein to browsing to the "Organizations" screen on the web GUI.
Currently, the root API, which consists of a different set of endpoints, is not supported by the CLI and I don't know if there are plans to support it.


Fixed Error on Nudging in first Iteration

Fixed a crash on, when nudging in the first iteration of the loop (before power is set). Also possible fixes using the power from the last measurement when nudging.
Fixes #1182

Thanks


"TypeError: Load failed" and "Could not connect to server" error on iOS

Cheers, thank you for this plugin! It looks to be exactly what I'm looking for and it's so close to working, but I'm running into troubles syncing to an iOS device.
I have a couchdb database hosted and behind a reverse proxy and accessible from the web and appears to be configured and working on a desktop instance of Obsidian. By using the couchdb/_utils tool I can confirm the database has been created and thee desktop Obisidian instance has uploaded information to that database. However, when I try to sync on an iOS device, after using the same login information, encryption passphrase, and database name, I get an error that says it cannot connect to the server, that "TypeError: Load failed". If I'm in the settings in the LiveSync plugin I can click "test connection" and it will appear to work, saying that it has connected to the correct database. I have no idea why iOS is throwing up the TypeError load fail error. From what I understand iOS is purposefully vague with those kinds of errors - but I can confirm the username and password and encryption passphrase are correct.
I've no real idea where to go from here, I feel like I've tried and confirmed all the credentials, and the test in the settings seems to work fine. It almost looks like the app is trying to use the old version of syncing, a feature that says is locked to mobile devices in the settings, but that can be toggled on and off. When toggled off, the test connects successfully, but when I toggle it on I get the same TypeError: Load Failed error.
My desktop instance is running on windows. The database is a couchdb docker container, properly exposed. The iOS device is updated to the most recent version of iOS.  (I'd paste the sync status logs here but for some reason I can't copy them out of the iOS app..)

Same thing here: couchdb on docker behind proper configured reverse proxy, a working windows app. In my scenario the couchdb is just exposed internally. (DNS isn't a problem, already checked that)
On iOS when i turn off "old connecting method" it replies "connected to", if i try to replicate data it says

could not connect to https://[url]/couchdb: TypeError:Load failed
Could not connect to server.

If i check "Use the old connecting method" the error is shown for "Test Database Connection" aswell.
Windows app is fine ("new" connection method).

Thank you for asking me!
It looks like the CORS.
This problem had been avoided by the new connecting method once. But as like in #63, we can't use the new connecting method on mobile. So it has been reverted.
I made a new feature Check database configuration on v0.9.0 to investigate the cause of the problem. Might not be a problem, but could you try it once?
Also, if there are no problems, I'll create an option "Use new connection method for except LiveSync".

Thank you for asking me! It looks like the CORS. This problem had been avoided by the new connecting method once. But as like in #63, we can't use the new connecting method on mobile. So it has been reverted.
I made a new feature Check database configuration on v0.9.0 to investigate the cause of the problem. Might not be a problem, but could you try it once?
Also, if there are no problems, I'll create an option "Use new connection method for except LiveSync".

I'll be more than happy to try anything! How can i use the  check database configuration  feature?  I'm not seeing it in the options.

Thank you for asking me! It looks like the CORS. This problem had been avoided by the new connecting method once. But as like in #63, we can't use the new connecting method on mobile. So it has been reverted.
I made a new feature Check database configuration on v0.9.0 to investigate the cause of the problem. Might not be a problem, but could you try it once?
Also, if there are no problems, I'll create an option "Use new connection method for except LiveSync".

worked for me. updated plugin, did check database and had several things to fix. afterwards the iOS app replicated successfully - livesync feature works as intended.
thank you for the fast fix :)

I'm very glad to hear that you could synchronize with the remote database!
@SONDLecT

There was some confusion about the remote database getting locked and needing to mark device as resolved - I think the error messages there could be a bit clearer - but this is incredible! Thank you so much!

You right. Poor documentation and message is the problem to solve.  These items are written in the early days, so in bad and terribly complicated English. Day by day, my English is getting better thanks to you all. So, I think, documentation will be improved step by step (If other problems are not there.)
If you have some ideas to improve messages, feel free to make an issue and/or the pull request!

A quick question: I'm hoping to use this to finally organize a massive folder of DND PDFs and notes. If the PDFs alone number in say 200gb, how large should I expect the database to be?

It uses about 33% extra to save binary files. And encryption also uses about 50% extra. So totally about 200% or a bit less. (Of course, your storage won't be spent as is, Obsidian compress them internally)
But if there are some same files or same part of files, it will be deduplicated. If you have old and new PDFs which updated with incremental updates, you can save the database usage and replication time.

Close this issue once. Feel free to open it again if you have new something.


fixup markdown formatting in api reference

some time ago GH changed over their markdown parser so you need a space after a heading mark.

Good catch, thanks!


Add support for multiple registries

Following the docs here. I am able to use images hosted in our private GCR registry.
The problem is when public images are also needed.
For example I'm also using mosquitto and redis images in my release.
redis:
  image: redis:alpine
  network_mode: "host"
mqtt-broker:
  image: eclipse-mosquitto
  network_mode: "host"
proprietary-service-1:
  image: gcr.io/****
  network_mode: "host"
proprietary-service-2:
  image: gcr.io/****
  network_mode: "host"

Because I have our private registry creds stored on the device, the agent tries to use them to pull from dockerhub, which fails.
error pull image   error=Error response from daemon: Get https://registry-1.docker.io/v2/library/redis/manifests/alpine: unauthorized: incorrect username or password
The current workaround is to just put the public images we need in our private registry.
This is not ideal since we don't get the regular updates of the publicly hosted versions.
The way docker generally handles this is to associate credentials to the corresponding registry domain. So being able to specify that in the /etc/deviceplane/registry_auth file might be a decent solution.

Good catch! We'll fix this.

The way docker generally handles this is to associate credentials to the corresponding registry domain. So being able to specify that in the /etc/deviceplane/registry_auth file might be a decent solution.

This sounds right to me.

We will see. Or Discussing everything the day your G enough to pull up on me. And have me turn my phone off and we just slide that will be better there's no hurry I got everything I need.


Search not working in arabic letters

I have a problem with global search with arabic letters in internet explorer (works in chrome)
Thanks

It's a known issue in IE. But it can work, if you encode your input value
$('.mvc-grid').mvcgrid({
    query: 'search=' + encodeURIComponent(this.value),
    reload: true
});

Great! Thanks


Add support for latestOnly flag in /changes endpoints

Currently if you run a job against a ProxyDataset the latestOnly flag is not supported. This is because the /changes endpoint cannot take it as a parameter, however the calls to the correct Dataset is internally capable of doing so, it's just currently being ignored.
By making a small change to the ProxyDataset setup, and the /changes endpoint, this would be supported.

feature/178-add-support-latestonly


how to get the middle layer of tflite model with c++ API

I want to know how to get the middle layer of tflite model with c++ API
i find some information in https://github.com/tensorflow/tensorflow/issues/49129, but it present with python
then I use the PreserveAllTensorsExperimental() of interpreterbuilder and interpreter->tensor() to extract middle layer tensor, but the tensor which i got is null, so how to do this correct with c++ API ?

Hi @likefxz2009 ! Work around is to visualize the model architecture through netron web app and use get_tensor_details() ( use experimental_preserve_all_tensors=True in interpreter while loading the TFlite model)  to extract the desired tensor with index value.


third-party build: update targets to allow extension registry overrides by a third-party build system

Description: this PR moves the extension registry files out to top-level directories with their own Bazel workspaces. This allows us to declare it as local_repository. Once treated as a external repository, a third-party build system (i.e, a consumer of envoy-mobile interested in building their own library with private extensions) is able to do so using local_repository declarations in their own repo.
Risk Level: low nothing changes for the project. However, the ergonomics for consumers to extend oss envoy mobile are being created here so we should make sure it is easy to do so.
Testing: local build with a third party filter.
Docs Changes: added docs
Release Notes: I propose we but v0.3.1 when this override system lands.
Signed-off-by: Jose Nino<EMAIL_ADDRESS>

@goaway could you give another look?

@goaway I decided to remove the config override, and make this PR only about extensions. Let me know if you have any remaining comments!


Improve first time run experience

We should think about the first time user out of box experience (OOBE).  Right now it launches silently and for some, that makes them wonder if anything actually happened.
More so if the icon is hidden in systray.

How about showing a one-time toast with something like "PowerToys is running and you can access it from using its tray icon!"? 🙂

I was thinking more in terms of what ear trumpet does. I think there are shorter term items we can do like that too

@crutkas do you mean a welcome dialog like this one, which shows a small clip on how to find the tray icon?

That looks nice indeed and shouldn't be very hard to implement.

yes, part of it. I want to do a more complete OOBE is my thought as well.  This is a future item right now.
Like, explaining OOBE for FancyZones and others ...

It would be nice to have a general OOBE dialog that introduces the app / main features.
We could have specific feature introductions on the settings pages (like an animated GIF in the sidepanel)?

My thoughts here was treat it like a video game.  Short quick animated gifs that are loopable.
For OOBE,

show quickly important functionality.
for upgrade scenario, any new, major things / features would do this as well.

Possible general rules for first time run OOBE

All OOBE features need doc links.
Settings page should have super easy way to show / describe feature + use it

Possible general rules for Upgrade OOBE

Any upgrade new thing we show needs doc link
Doc main page for utility needs to be coherent with new feature too

just want to be sure we show a real scenario for addressing systray icon.

OOBE
This concept shows a potential first-run experience: it shows the major modules and could include some quick setup items (e.g. hotkey combo's). Would be a single window that pops up when after installation.

What's new
Whenever a new update rolls out, with a new feature, we can introduce it to the user. A short description and an image to make the user aware of something new.

WinUI 2.4/UWP source code here: https://github.com/niels9001/PowerToysOOBE/tree/master

I'm in love with this.  I'm thinking this could be a pivot from new install / upgrade as well for new features.
Thinking is we could on first time launch have this and just directly build this OOBE into Settings.
@enricogior, thoughts?

Excellent!
Let's also add an option in the general settings to let the user choose if they want the "what's new" tour, and along with the option to start it automatically at first run after update, also a button to open it later on.

After some user studies, here is a concept we feel strongly on.  It would work for both OOBE and upgrade.  @niels9001 did a great job and has mock source here: https://github.com/niels9001/PowerToysOOBE
Still needs a few adjustments such as smaller video and maybe a quick "Use it by ..." section.
One resolution we decided until we get further feedback is to remove the quick setting of top settings.  It will still provide a deep link into the main settings application for that PT

After some user studies, here is a concept we feel strongly on.  It would work for both OOBE and upgrade.  @niels9001 did a great job and has mock source here: https://github.com/niels9001/PowerToysOOBE
Still needs a few adjustments such as smaller video and maybe a quick "Use it by ..." section.
One resolution we decided until we get further feedback is to remove the quick setting of top settings.  It will still provide a deep link into the main settings application for that PT

That is beautiful - I would really like it to become almost a system standard, if you could persuade other apps like Windows Terminal, or the more complex inbox apps.  This could even be a "FirstRun" template to include in the SDK.
Would you allow resizing of this window, and how would it handle reflow and adjusting margins?
There is a settings link there, but what about a ToggleSwitch to turn the features off and on.  Coming from an upgrade, there could be a what's new screen, and then an option to "view all powertoys" to bring up this first run experience again!

That is beautiful - I would really like it to become almost a system standard, if you could persuade other apps like Windows Terminal, or the more complex inbox apps.  This could even be a "FirstRun" template to include in the SDK.
Would you allow resizing of this window, and how would it handle reflow and adjusting margins?
There is a settings link there, but what about a ToggleSwitch to turn the features off and on.  Coming from an upgrade, there could be a what's new screen, and then an option to "view all powertoys" to bring up this first run experience again!

@mdtauk that would be cool to have a default OOBE template across Windows apps!
I'm not sure if we need resizing of the window. This is a UWP mock-up now, but my thought was that this would be more of a dialog type of screen (with only a close button). I think this window should come up on first time run, and should be launchable from within Settings if you e.g. missed it. And yes, would be nice to have it accessible from a 'What's new dialog' as well!
I have tweaked the UI slightly with the points @crutkas brought up:

@mdtauk that would be cool to have a default OOBE template across Windows apps!
I'm not sure if we need resizing of the window. This is a UWP mock-up now, but my thought was that this would be more of a dialog type of screen (with only a close button). I think this window should come up on first time run, and should be launchable from within Settings if you e.g. missed it. And yes, would be nice to have it accessible from a 'What's new dialog' as well!
I have tweaked the UI slightly with the points @crutkas brought up:

@niels9001  The resizing would then only need to be considered should it become a template for others. 😁
UWP and WinUI 3.0 wont have an inbuilt ability to create a dialog window, without Maximise and Restore functionality, or to only display a close button.  Hopefully it gets added to the Windowing APIs eventually.

@niels9001  The resizing would then only need to be considered should it become a template for others. 😁
UWP and WinUI 3.0 wont have an inbuilt ability to create a dialog window, without Maximise and Restore functionality, or to only display a close button.  Hopefully it gets added to the Windowing APIs eventually.

@dedavis6797 when will the spec be put in on the wiki?

@dedavis6797 when will the spec be put in on the wiki?

EOD today

EOD today

Link to spec: https://github.com/microsoft/PowerToys/wiki/OOBE-Dialog

@enricogior are we viewing this as the "OOBE" work for 0.33 tracking item?  If so lets assign it to .33

@dedavis6797 we should add in a scoobe issue

Great news!  This was resolved in the newly released 0.33 version of PowerToys!  Head to https://aka.ms/installpowertoys to grab latest.


xUser: Returns 'The variable '$user' cannot be retrieved' error inside Windows 2022 Server Core container

Problem description
When I attempt to run the xUser resource inside a Docker build of Windows 2022 Server Core, I get the following error
Docker image
mcr.microsoft.com/windows/servercore   ltsc2022   b53d206693f6
PS C:\> Invoke-DscResource @user -Verbose                                                                                cmdlet Invoke-DscResource at command pipeline position 1
Supply values for the following parameters:
Method: Test
PowerShell DSC resource DSC_xUserResource  failed to
execute Test-TargetResource functionality with error message:   The variable '$user' cannot be retrieved because it has not been set.
+ CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName        : localhost

Verbose logs
PS C:\> Invoke-DscResource @user -Verbose

cmdlet Invoke-DscResource at command pipeline position 1
Supply values for the following parameters:
Method: Test
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = ResourceTest,'className' =
MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer 3796F4E274AA with user sid S-1-5-93-2-1.
VERBOSE: [3796F4E274AA]: LCM:  [ Start  Test     ]  [[xUser]DirectResourceAccess]
VERBOSE: [3796F4E274AA]: LCM:  [ End    Test     ]  [[xUser]DirectResourceAccess] False in 0.1720 seconds.
PowerShell DSC resource DSC_xUserResource  failed to execute Test-TargetResource functionality with error message: The variable '$user'
cannot be retrieved because it has not been set.
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 0.321 seconds
PS C:\> Invoke-DscResource @user -Verbose

cmdlet Invoke-DscResource at command pipeline position 1
Supply values for the following parameters:
Method: Set
VERBOSE: Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = ResourceSet,'className' =
MSFT_DSCLocalConfigurationManager,'namespaceName' = root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: An LCM method call arrived from computer 3796F4E274AA with user sid S-1-5-93-2-1.
VERBOSE: [3796F4E274AA]: LCM:  [ Start  Set      ]  [[xUser]DirectResourceAccess]
VERBOSE: [3796F4E274AA]:                            [[xUser]DirectResourceAccess] Configuration of user MyNewUser started.
VERBOSE: [3796F4E274AA]: LCM:  [ End    Set      ]  [[xUser]DirectResourceAccess]  in 0.1720 seconds.
PowerShell DSC resource DSC_xUserResource  failed to execute Set-TargetResource functionality with error message: The variable '$user'
cannot be retrieved because it has not been set.
    + CategoryInfo          : InvalidOperation: (root/Microsoft/...gurationManager:String) [], CimException
    + FullyQualifiedErrorId : ProviderOperationExecutionFailure
    + PSComputerName        : localhost

VERBOSE: Operation 'Invoke CimMethod' complete.
VERBOSE: Time taken for configuration job to complete is 0.317 seconds

DSC configuration
$user = @{
  Name = 'xUser'
  ModuleName = 'xPSDesiredStateConfiguration'
  Property = @{
    UserName = 'MyNewUser'
    Password = New-Object System.Management.Automation.PSCredential('Bamboo',(ConvertTo-SecureString 'P@ssw0rd' -AsPlainText -Force))
}
}

Suggested solution
I'm not sure what the problem is
Operating system the target node is running
OsName               : Microsoft Windows Server 2022 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsVersion       : 2009
WindowsBuildLabEx    : 20348.859.amd64fre.fe_release_svc_prod2.220707-1832
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell version and build the target node is running
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.20348.1366
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.20348.1366
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

xPSDesiredStateConfiguration version
Name                         Version Path
----                         ------- ----
xPSDesiredStateConfiguration 9.1.0   C:\Program Files\WindowsPowerShell\Modules\xPSDesiredStateConfiguration\9.1.0\xPSDesiredStateConf...

Verify that these lines work setting the variable $user.
https://github.com/dsccommunity/xPSDesiredStateConfiguration/blob/7703bb11324d26c97d80684bdc4fe46cb982b0ca/source/DSCResources/DSC_xUserResource/DSC_xUserResource.psm1#L661-L666

The first line fails
PS C:\> $principalContext = New-Object System.DirectoryServices.AccountManagement.PrincipalContext -ArgumentList ([System.DirectoryServices.AccountManagement.ContextType]::Machine)

Unable to find type [System.DirectoryServices.AccountManagement.ContextType].
At line:1 char:107
+ ... gumentList ([System.DirectoryServices.AccountManagement.ContextType]: ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.Director...ent.ContextType:TypeName) [], RuntimeException
    + FullyQualifiedErrorId : TypeNotFound

So then the current implementation is not supported in a container.
The following line is used on a Nano server, does it work in the container?
https://github.com/dsccommunity/xPSDesiredStateConfiguration/blob/7703bb11324d26c97d80684bdc4fe46cb982b0ca/source/DSCResources/DSC_xUserResource/DSC_xUserResource.psm1#L1135
If that works, can you see what this outputs?
(Get-CimInstance -ClassName Win32_OperatingSystem).OperatingSystemSKU

Yes, that line works fine inside the container
PS C:\> [Microsoft.PowerShell.Commands.LocalUser] $user = Get-LocalUser -Name 'Guest' -ErrorAction Stop
PS C:\> $user

Name  Enabled Description
----  ------- -----------
Guest False   Built-in account for guest access to the computer/domain

Okay so then the resource might need to switch to the same logic as used in a Nano server.
Looking at the list of SKUs here https://learn.microsoft.com/en-us/windows/win32/cimwin32prov/win32-operatingsystem the container reports as a normal Desktop Experience. Must be some other why to determine that it runs in a container. 🤔
But if you want to test out the full functionality of when running in Nano (might be other problems) you could replace the following lines in your local installed module to if ($true) so the Nano-logic is ran.
https://github.com/dsccommunity/xPSDesiredStateConfiguration/blob/7703bb11324d26c97d80684bdc4fe46cb982b0ca/source/DSCResources/DSC_xUserResource/DSC_xUserResource.psm1#L45
https://github.com/dsccommunity/xPSDesiredStateConfiguration/blob/7703bb11324d26c97d80684bdc4fe46cb982b0ca/source/DSCResources/DSC_xUserResource/DSC_xUserResource.psm1#L144
https://github.com/dsccommunity/xPSDesiredStateConfiguration/blob/7703bb11324d26c97d80684bdc4fe46cb982b0ca/source/DSCResources/DSC_xUserResource/DSC_xUserResource.psm1#L239

So what we need is new logic to test if running in a container and then run the same logic as Nano (if it works) or other logic that is needed for a Windows container.


XPR Account
xprar
Feedback (optional)
No response

hey @alexregier,
I just added you to the contract so that you are eligible to perform the reward task:

https://explorer.xprnetwork.org/transaction/5655ec54e23b9965cb36519927e4156255ed1f4a132611705892d3f5cc0c20f8

don't forget to create another account via CLI and call setcontract action on the sdcworkshop account to provide your contract account here:

https://explorer.xprnetwork.org/account/sdcworkshop?loadContract=true&tab=Actions&limit=100&table=developers&action=setcontract

Marco

@alexregier short reminder for the task. you still have ~5 days to claim the reward.
if you need help, feel free to ask here or in the TG channel ;-)


Spark 2.0 and Scala 2.11 updates

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/282/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/283/
Test FAILed.


Feat(web-twig): Introduce Full Floating UI demo to Tooltip, update internal implementation #DS-1084

Switch to data attribute placement instead of modification class based.

Description

Additional context

Issue reference
DS-1084

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Follow the PR Title/Commit Message Convention.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

coverage: 96.46% (+16.8%) from 79.617%
when pulling ce548696c6b1cb82d1b3b83c6e5b9a0a666018c1 on feat/twig-tooltip-floating-demo
into 02c3ddfc0d91402371793ccd5da31bf0763a082a on main.

Just one thing: is there a chance to improve the README according to the web package? I'm sure our users will appreciate if there are instructions for placement, interaction etc. 🙏🏻

TBH I don't want to do this now. as this PR is mainly to match demos.
We are already working on including the floating UI directly in the Tooltip and part of it should be an overhaul of the Docs. I don't see the added value to refactoring docs now.


[HOTFIX] WORKAROUND_ISSUE_2038: Disable BF16/FP16 in ConvHipImplicitGemmV4R1Fwd for MI100/200 and all new targets.

This is expected to unblock CI. Introduces workaround for issue #2038. Related to issue #936.

[Attribution] @junliume @johnny-keker

https://github.com/ROCmSoftwarePlatform/MIOpen/labels/urgency_blocker
https://github.com/ROCmSoftwarePlatform/MIOpen/labels/workaround
https://github.com/ROCmSoftwarePlatform/MIOpen/labels/correctness
Proposed reviewers:

@JehandadKhan
@junliume
@carlushuang
@asroy

@atamazov this issue seems to be able to workaround by https://github.com/ROCmSoftwarePlatform/MIOpen/pull/1957/commits/277e35c10f036833f781477f3db7bcb7ad52906d and it is caused by hipRTC header file warning messages are treated as error when -DBUILD_DEV=On. Could you help to investigate why it is happening now? Differentiating between passing and failing points have misguided our investigation for a long time.

@atamazov this issue seems to be able to workaround by 277e35c and it is caused by hipRTC header file warning messages are treated as error when -DBUILD_DEV=On.

Your observations do not match to what I see the the CI log of #2033:
[2023-03-23T18:53:48.490Z]  73/323 Test #128: smoke_solver_ConvHipImplicitGemmV4R1
...
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [GetAllConfigs] ConvHipImplicitGemmV4R1Fwd: Searching the best solution among 33...
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [Monitor] 0/0/5 0.23334, best within recent 1: 0.23334 #0 16,32,8,2,2,2,4,4,2,4,8,1,16,1,4,32, ETA:0 sec.
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [Monitor] 1/0/5 0.23334, best within recent 1: 0.750709 #1 16,32,4,2,4,4,2,4,2,4,4,1,16,1,4,16, ETA:53.7877 sec.
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [Monitor] 2/0/5 0.23334, best within recent 1: 0.285917 #2 16,128,4,2,4,4,4,4,4,4,4,2,16,2,2,128, ETA:28.3322 sec.
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [Monitor] 3/0/5 0.114943, best within recent 1: 0.114943 #3 16,128,16,2,4,4,4,4,4,4,16,1,16,1,2,128, ETA:15.7516 sec.
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [GenericSearch] Done: 5/0/5, best #3 0.114943 16,128,16,2,4,4,4,4,4,4,16,1,16,1,2,128
[2023-03-23T18:53:48.490Z] MIOpen(HIP): Warning [GenericSearch] ...Score: 2.44989 (default time 0.281597)
[2023-03-23T18:53:48.490Z] FAILED: 0.535381
[2023-03-23T18:53:48.490Z] Max diff: 255
[2023-03-23T18:53:48.490Z] Mismatch at 0: 30 != 129

@junliume @JehandadKhan @carlushuang @asroy PR is ready for the next round of reviewing and CI testing.

Converted to draft due to https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2043#issuecomment-1483738387

Seems not necessary, but let's keep this PR and branch for a month or so.


Upgrade the demo to HTMLBars

ember-react demo is brilliant, it allows to compare Ember and React both coding-wise and performance wise.
I'm very excited to see how much Ember performance boosts after switching to HTMLBars.
Now that 1.10 is released and boasting conversion to HTMLBars, can you please upgrade the demo?

Done.


Exception ticking World Component: RimWorld.Planet.TileTemperaturesCompSystem.Threading.ThreadAbortException

Describe the bug
After I had defeated a mechanoid raid, my fps dropped to less than 1 fps. Using the same save game as my previous posts. I only have Harmony and RimThreaded enabled, and I don't have Royalty DLC. I am subscribed to other mods this time but none of them are enabled and I have never used any other mods on this save. Restarting Rimworld fixed the issue.
EDIT: Version was RT 1.2.3
Error Log
https://gist.github.com/UndeadKitten/4acf5ff84fcbd626f9bde2cc7c3ed905
Specs
Operating System: Windows 10 Home 64-bit
Processor: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz (4 CPUs), ~3.5GHz
Memory: 16384MB RAM
Card name: NVIDIA GeForce GTX 970

can you please try t recreate this error with rimthreaded 1.2.4?

can you please try t recreate this error with rimthreaded 1.2.4?

any advice on how to reproduce this error? do you have a save available for this error?

any advice on how to reproduce this error? do you have a save available for this error?

I have continued to play the same save and I have not encountered this specific error again since posting this.  I have encountered times where my FPS and TPS dropped considerably (720 TPS down to 120-360 TPS), which was fixed by restarting my game, or letting it play out for a while then restarting my game. I didn't check what the error was during those times though.
(Below is copy and pasted across a few of my posts)
I don't know of a way to reliably reproduce any of the errors that I get, they happen seemingly at random while playing. Sometimes almost immediately upon loading up the save and sometimes hours later. I get many different errors, more than what I have posted here. I regularly get inconsequential errors and sometimes ones that break functions of the game (usually pawn unable to reach area) that are fixed upon restarting the game. Both on 1.2.3 and 1.2.4 preview.
If you have any suggestions for me on what to do then let me know.

I have continued to play the same save and I have not encountered this specific error again since posting this.  I have encountered times where my FPS and TPS dropped considerably (720 TPS down to 120-360 TPS), which was fixed by restarting my game, or letting it play out for a while then restarting my game. I didn't check what the error was during those times though.
(Below is copy and pasted across a few of my posts)
I don't know of a way to reliably reproduce any of the errors that I get, they happen seemingly at random while playing. Sometimes almost immediately upon loading up the save and sometimes hours later. I get many different errors, more than what I have posted here. I regularly get inconsequential errors and sometimes ones that break functions of the game (usually pawn unable to reach area) that are fixed upon restarting the game. Both on 1.2.3 and 1.2.4 preview.
If you have any suggestions for me on what to do then let me know.

If you still get this error. re open this issue.


Detailed Keras Model conversion example

We need to add a detailed Keras model conversion example that explains ways to export/import Keras models.

This issue was addressed by pull request #127.  A new detailed Keras model conversion example (Import_Keras_LeNet.ipynb) can be found under python-dlpy/examples/keras_model_conversion


guimenu: Fixed emulation crash when the Emuec-utils script wouldn't work

On some systems, using busybox bash may disable Emuec-utils, leading to ui bugs. Increase test fun to ensure emulation works, See: https://github.com/EmuELEC/EmuELEC/pull/1031
Signed-off-by: ZiHan Huang<EMAIL_ADDRESS>

es-app/src/guis/GuiMenu.cpp:
SystemConf::getInstance()-> set("system.timezone", emuelec_timezones-> getSelected());
Here, if the script fails to execute successfully, NULL is returned, causing a crash

For script test fun additions, see： https://github.com/EmuELEC/EmuELEC/pull/1031

yes， fix it


[PROPOSAL] Evolving the API Spec repo

This repo was created to define accurate specs for OpenSearch APIs, and from there, generate OpenSearch clients in different languages. This will keep all clients in sync, and it will let us deploy changes in the API to all clients. With that in mind, there are 3 goals:

Usability: The resulting spec must have enough information to generate proper OpenSearch clients from scratch, and to incrementally add new features to existing clients. A proper OpenSearch client is NOT simply any client with a method for every OpenSearch endpoint defined in the spec. Such a client must also adhere to the patterns and conventions followed by the existing clients, in order to work in an already-written application.
Backward-Compatibility: When we generate an already-existing endpoint in the client, it should not be a breaking change for the users. The generated methods might have different implementation details but they must retain the same signatures, error messages, and functionality of their hand-written counterparts.
Maintainability: On top of defining new endpoints and operations for OpenSearch, we also need to backfill 308 existing operations across 208 endpoints. This is quite an undertaking, and we aim to make such a job as painless and error-free as possible.

As explained further below, I propose the following four-stage process that, on its surface may appear complex, but which eliminates unnecessary effort and achieves the above goals:

Convert the legacy spec to Smithy
Use mixins to augment the Smithy specs with missing parameter and response definitions
Generate OpenAPI specs from the Smithy specs
Generate OpenSearch clients from the OpenAPI specs using custom generators

The Challenges
The OpenSearch API does not follow REST API constraints and conventions
In REST API, each endpoint represents a resource in a hierarchy of resources, and the HTTP verbs are mapped to CRUD actions to interact with said resource. Hypothetically, to create or update an OpenSearch document we would have the following endpoints and operations in the classic REST API fashion:

Create: POST /indexes/{index}/docs
Update/Upsert: PUT /indexes/{index}/docs/{id}

However, we currently have the following document operations on OpenSearch:

Create :

POST /{index}/_doc
POST /{index}/_create/{id}
PUT /{index}/_create/{id}

Update:

POST /{index}/_update/{id}

Upsert:

POST /{index}/_doc/{id}
PUT /{index}/_doc/{id}

As you can see, OpenSearch uses different endpoints to interact with the same resource, a document in this example, (instead of one endpoint with different HTTP verbs/operations). Moreover, different HTTP verbs like, PUT and POST, have the exact same meaning on the same endpoints.
This causes issues for off-the-shell client generators:

They will generate methods with misleading names. POST /{index}/_update/{id}, for example, will be translated to a method named post_index_update_id. That is confusing! Without reading the description, it’s impossible to tell if the method will create a new document (post) or modify an existing document (update).
They will generate duplicate methods with different names but have identical signature and functionality.
Some generators might attempt to group the methods by the resource they interact with. But in the case of the document methods, they will be put in different groups due to their different URL paths.

Namespace and the grouping of operations by functionality
OpenSearch API operations are grouped into API methods by functionality, and these methods are then grouped into namespaces. Consider the following operations:

GET /_cat/shards
GET /_cat/shards/{index}

In OpenSearch clients, these two operations are combined into one method called shards where {index} is an optional path parameter. The shards method belongs to a namespace called cat. And to invoke this method: client.cat.shards(index: 'books')
This operation grouping is also reflected in Elasticsearch’s legacy spec. Take a look at this excerpt of the legacy index.json spec file:
{
  "index":{
    "documentation":{
      "url":"https://www.elastic.co/guide/en/elasticsearch/reference/master/docs-index_.html",
      "description":"Creates or updates a document in an index."
    },
    "stability":"stable",
    "url":{
      "paths":[
        {
          "path":"/{index}/_doc/{id}",
          "methods":[
            "PUT",
            "POST"
          ],
          "parts":{
            "id":{
              "type":"string",
              "description":"Document ID"
            },
            "index":{
              "type":"string",
              "description":"The name of the index"
            }
          }
        },
        {
          "path":"/{index}/_doc",
          "methods":[
            "POST"
          ],
          "parts":{
            "index":{
              "type":"string",
              "description":"The name of the index"
            }
          }
        }
      ]
    },
    "params":{...},
    "body":{
      "description":"The document",
      "required":true
    }
  }
}

This spec describes 3 different operations in 2 different URL paths, but they are considered one action with shared description, query parameters, path parameters (where {index} is required but {id} is optional), and request body.
For more information on this topic, check out this issue.

Solutions
Generate Clients from OpenAPI Spec
We have had a long discussion on whether to generate the clients from OpenAPI or Smithy Spec. The consensus is that OpenAPI is an industry standard. Many developers are familiar with OpenAPI and have experience working with it. OpenAPI is well supported by most IDEs, with a large set of tools, especially Swagger, built for it over the years.
The generators for OpenAPI spec can be reused to generate clients for OpenSearch Extensions. Many of these extensions will be developed by independent teams who will likely use OpenAPI to describe their APIs. This is one reason not to simply use the legacy spec to generate client code, even though the spec was built around unique traits of OpenSearch API.
One thing to keep in mind: Any generator we write must have the ability to combine many operations into one action. It’s not as simple as translating the spec of an operation to an API method. We have already written a prototype generator that can handle a few types of operation combinations (Get-Get, Post-Put, Post-Get, ...) in Ruby.
While both OpenAPI and Smithy offer off-the-shelf generators that can generate brand new clients with the push of a button, they are meant for conventional REST APIs, which is not the case with OpenSearch, as explained above. The API methods generated from such generators will be very confusing to use, and cannot be retrofitted into existing clients. We will have to write our own generators regardless. So, neither Smithy nor OpenAPI has the advantage over the other in this regard.
Use Smithy as a tool to write OpenAPI Spec
Even with tools that help navigate and edit OpenAPI docs, writing specs for over 300 operations in JSON or YAML is still a daunting task. Moreover, since OpenAPI does not allow reference by operation, OpenSearch operations serving the same purpose are scattered in different places and get mixed up with other operations.
Smithy, on the other hand, comes with features that make it easier to maintain an API spec as complex as the OpenSearch API:

The mixin feature makes it easier to reuse assets, especially the set of parameters shared between operations to be combined in the same method.
The lack of restrictions on references allows us to group definitions of similar operations (like the three index operations) into the same location. This will come in handy when we backfill the intricate schemas of request and response bodies by hand later.

With that being said, we will only use Smithy as a tool to write OpenAPI spec. That means:

We won’t use Smithy features that are not translatable to OpenAPI.
Any update to the Smithy spec must always be reflected in the OpenAPI spec.
Smithy can be dropped in the future if necessary, allowing contributors to update to the OpenAPI spec directly rather than through the Smithy spec.

Implementation Details
Fill in missing meta data for client generators
The core OpenAPI does not support namespace and operation grouping. We can address this by adding our own OpenAPI extension to include this info in each API operation. For example:

x-operation-group: cat.shards
x-operation-group: index

And to support incremental client generation (where we only need the client generators to generate code for new operations), we will add extensions delineating when an operation was added, deprecated, and removed:

x-version-added: 0.7
x-version-deprecated: 1.5
x-version-removed: 2.0

Smithy’s custom traits are the equivalent of OpenAPI extensions. At the time of this writing, the native Smithy-to-OpenAPI converter does not translate Smithy traits to OpenAPI extensions. However, we have a solution for this, and we’re working on upstreaming this change to the converter.
Backfill existing operations

Translate the legacy spec to Smithy models: We have already translated thelegacy spec to OpenAPI spec. The experience gained from that translation will help us quickly translate it to Smithy, too. This will save us time, and reduce potential human errors backfilling 308 operations by hand.
Add schemas for response and request bodies: While most clients treat the bodies as generic JSON objects and do not need this info, the Java and future TypeScript clients require proper schemas for these entities. This is another reason why we chose Smithy to draft the spec over editing OpenAPI directly. Smithy’s cleaner format, and more flexible file structure, along with mixins, will make backfilling these complex data structures by hand less painful.

Github Workflows

Translate Smithy Spec to OpenAPI spec for every commit.
Validate the OpenAPI spec to assure that each operation has the extensions mentioned above.
Validate the OpenAPI spec to assure that operations that are grouped together have identical description, parameters, and request/response bodies.
Publish a new version of the OpenAPI spec to the repo’s Github page when it’s released.

For more details, check out the related proposal.

Conclusion
The four-stage process addresses the many quirks of the OpenSearch API. It allows us to rapidly flesh out the API definition using the legacy spec. It allows us to fill in the missing pieces efficiently using Smithy, which is a well-factored way of maintaining specs. By converting the Smithy spec to OpenAPI, we can take advantage of the OpenAPI ecosystem and keep the door open to new developers to contribute to clients.
I welcome feedback on this proposal.

I'm late to this proposal, would only say that "Translate Smithy Spec to OpenAPI spec for every commit." sounds like a "build and release" to me. Maybe it's helpful to think of it that way?

With the move toward native openAPI, the only relevant piece is validating the OpenAPI spec, which I'm working on right now.

Is validating and linting the same thing? If so this issue can be closed to avoid duplicating with #22?

Yes, they are the same. Closing.


Adds CSI 5m and CSI 6m

While you're at this, it would be great to support CSI 6m (rapid blink) as well.
E.g. wezterm supports CSI 6m.

I did all the changes don't know why it's saying outdated?

I did all the changes don't know why it's saying outdated?

this is exactly what you want. An outdated code review. This means that these source code ranges must have been changed.

Thanks! :fire:


Added optional minimum version check for browsers

Following #40 I added support to the browser check functions to receive an optional version number and check that the browser is that version or higher. So to check that the browser is Chrome 34 or higher, you call is.chrome(34) (yes, it's integers only so it's only major versions).
This solution is not perfect. It makes it seem like you are checking that the browser is of the exact version of the parameter. Something like is.chrome(34).orHigher() is clearer in my view. But maybe it's also an overkill..

I agree that avoiding the .orHigher is not a problem and if someone really really wants to check for a specific version (which is most likely going to be a minority) they could do it like .. is.chrome(34) && !is.chrome(35) :D

Closed in favor of #107, #109, #110, #111.

@lipis @jdalton @njenia -- just to be clear -- at this time we can not check for minimum versions of Chrome and other non-ie browsers. Is this correct? The optional param only returns true/false for the major version passed in.


es_host not being read from rules files after commit b31cd7ffdaece87a51493a811673f5e773bf9f53

The 'es_host' key defined in a rule file is no longer being used after the commit below a few days ago related to optionally reading ES_HOST, ES_PORT from environment variables.
https://github.com/Yelp/elastalert/commit/b31cd7ffdaece87a51493a811673f5e773bf9f53
As a test, do an out-of-the-box installation, with a master config.yml pointing to your ES instance.
Then for simplicities sake, delete all the files in the example_rules directory except example_cardinality.yaml and run elastalert
$ python -m elastalert.elastalert --config config.yml
ERROR:root:Traceback (most recent call last):
File "/tmp/elastalert/elastalert/elastalert.py", line 914, in run_all_rules
num_matches = self.run_rule(rule, endtime, self.starttime)
File "/tmp/elastalert/elastalert/elastalert.py", line 642, in run_rule
self.current_es_addr = (self.current_es.host, self.current_es.port)
AttributeError: 'Elasticsearch' object has no attribute 'host'
ERROR:root:Uncaught exception running rule Example cardinality rule: 'Elasticsearch' object has no attribute 'host'
You may then think it is because example_cardinality.yaml does not define its own es_host and es_port, so go ahead and have the rule file set its own keys, run it again and you get the same result.
If you then comment out the current change on line #644 of elastalert.py and modify it back to the before the commit, the command runs successfully both with or without the es_host/es_port variables defined explicitly in example_cardinality.yaml
    #self.current_es_addr = (self.current_es.host, self.current_es.port)
    self.current_es_addr = (rule['es_host'], rule['es_port'])

I would have submitted a pull request if I though it was just this single line causing an issue, but this commit reaches into alerts and other areas and I'm not sure how much needs to be rolled back.

+1. I'm seeing the exact same issue with this commit. I suggest that this commit be rolled back.

Fixed by #1027

I'm making a patch for this


uRos node not listing

Hardware description: Rasperry PI connected to RP2040 nano connect
RTOS: NA
Version or commit hash: Humble

Hello again,
I am running uROS on a RP2040 connect. As usual, for testing I am using docker which launches the micro ros agent in humble:
docker run -it --rm -v /dev:/dev --privileged --net=host microros/micro-ros-agent:humble serial --dev /dev/ttyACM0 -v4
Everything works fine on my pc. When I go open a new bash on the image I can display the uros node and topic. I can display the contents of the message.
Then I connected my RP2040 to an embedded computer with Ubuntu server 22, Ros2 Humble. The problem is that the launch process seems to go well, I set -v5 and I see a lot of :
[1673362828.144831] debug    | DataWriter.cpp     | write                    | [** <<DDS>> **]        | client_key: 0x00000000, len: 120
[1673362828.247510] debug    | SerialAgentLinux.cpp | recv_message             | [==>> SER <<==]        | client_key: 0x701B8528, len: 132
[1673362828.247738] debug    | DataWriter.cpp     | write                    | [** <<DDS>> **]        | client_key: 0x00000000, len: 120
[1673362828.247881] debug    | SerialAgentLinux.cpp | recv_message             | [==>> SER <<==]        | client_key: 0x701B8528, len: 16

But unfortunately and after launching the uros agent, the commands for listing the topics and the nodes do not display anything.
$ros2 node list $ros2 topic list  /parameter_events /rosout
Any suggestions would be greatly appreciated.

how are you running the dockers where you run ros2 node list?

Are you changing the domain id in the micro-ROS client?

The micro-ROS agent does not modify the domain id. Is the client who determines which domain id will use.
Could you check if setting your ROS 2 environment to domains id 0 it works?

Thank for your answer. I was wrong. Using uRos for Humble, I changed the domain id using the following:
``
size_t domain_id = ;
//Define init options
rcl_init_options_t init_options = rcl_get_zero_initialized_init_options();
RCCHECK(rcl_init_options_init(&init_options, allocator));
rmw_init_options_t* rmw_options = rcl_init_options_get_rmw_init_options(&init_options);
RCCHECK(rcl_init_options_set_domain_id(&init_options, domain_id));
``
After programming the board, I don't see anymore my node on the container and luckily it works fine on my RPI. Thank you.


zh-translation: docs/root/intro/arch_overview/other_protocols/grpc.rst

ref: https://github.com/cloudnativeto/envoy/issues/73

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Deprecated:]

@scilla0531 加了点comment，仅供参考。

@majinghe  @shalk 感谢review，修改已经提交，麻烦查阅下哈！

/LGTM


feat: update deploy schema to define load_balancers under each env

This PR updates the expected schema of a deploy config file. Notably, the load_balancers key under a specific environment allows a user to define all load balancers for a specific environment in a single place. This makes it easier to deploy a load balancer that serves multiple pipelines.
defaults:
  machine_config:
    type: ec2
    mem_gib: 16
    vcpu: 4
  env_vars:
    var_1: aineko_test

environments:
  develop:
    pipelines:
      - example_pipeline:
          env_vars:
            env: develop

    load_balancers:
      dev-api.aineko.dev:
        - pipeline: example_pipeline
          port: 8000

pipelines:
  example_pipeline:
    source: ./tests/conf/test_pipeline.yml
    machine_config:
      type: ec2
      mem_gib: 8
      vcpu: 2

What's the reason for renaming pipelines to env?

What's the reason for renaming pipelines to env?

It used to be a grouping of a set of pipelines for a specific environment. Now it's a set of pipelines and load balancers for a specific environment.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/78 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 79ddb0c:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-07-32-56 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-07-32-56

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add MANIFEST.in to include LICENSE in tarball

I maintain the package for asciitree on conda-forge. I would like to include your license file into that package but I currently can't do that because it isn't included in the tarball uploaded to pypi. The MANIFEST.in file added in this PR will add the license to the next release you make on pypi.

Merged, thanks!


When creating new heartbeat event, error returned: cannot read property 'index' of undefined

I am using 3.1.1 version.
I created a new heart successfully. But when I try to create a new named event, I get this error:
TypeError: Cannot read property 'index' (beatevent.index) of undefined
at Heart.killEvent (/node_modules/heartbeats/lib/heart.js:124:28)
In heart.js there is a function named: Heart.prototype.killEvent.
It is called in heart.js on line 104 when creating a named event. (if I am right it is for avoiding duplicate named events)
The function has two arguments: 'name' and 'beatevent'. But when its called it lacks the 'beatevent' argument. So 'beatevent.index' is undefined.
And the command -- this.events[beatevent.index] = undefined; -- on line 124 returns the error above.
Anyway thanks for this module, it makes timing and synchronizing really simple!

@bersilius Thanks again for pointing it out.
Added this as something in the tests so it doesn't happen in the future.
Published the bug fix already to npm and released.
Update your project! :D

Updated. Issue solved!
Thanks again!


updated old endpoints and added back the faker profiles

Updated the old model/end points with the new naming convention. Added back the faker data for profiles, may remove it later but are using it to see how the dummy data profiles apply to the FE.

@LeesahMasko take a look and approve when you can and I will merge


Release Beta 1

[x] CI passing

[x] Unit testing
[ ] Integration Tests

[ ] Manual testing to match ODFE
[ ] Release notes
[ ] Tag beta release

Manual testing to match ODFE

Does this mean we will support migration from ODFE to OpenSearch?

Manual testing to match ODFE

Does this mean we will support migration from ODFE to OpenSearch?

I think I was trying to say that we should do as much testing as we did in ODFE. I removed the extra words.

Beta1 released


Fix workspace invite message page shows an error after going back to the page

Details

When we deep link to the workspace invite message page and send the invite, we will be navigated to the member list page, but the workspace invite message page is still in the stack. Going back to that page will show a form validation error saying that we need at least to select one user to be invited. That is because the selected user is cleared when we confirm the invite. This PR makes sure the workspace invite message page is popped out from the navigation state after sending the invite.
Fixed Issues

$ https://github.com/Expensify/App/issues/23311
PROPOSAL: https://github.com/Expensify/App/issues/23311#issuecomment-1645673367
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

Web/Desktop/mWeb

Open Settings > Workspaces > Select any workspace > Members > Invite > Select any user and press Next
Refresh/reload the page
Press the Invite button. Verify you are navigated to the workspace member list page
Open Invite > Select any user and press Next
Verify you are navigated to the workspace invite message page and there is no error

Android/iOS

Open Settings > Workspaces > Select any workspace > Members > Invite > Select any user and press Next
Go back to home (LHN)
Deep-link to the workspace invite message page (that you open in the 1st step) (staging.new.expensify.com/workspace/{workspaceID}/invite-message)
Press the Invite button. Verify you are navigated to the workspace member list page
Open Invite > Select any user and press Next
Verify you are navigated to the workspace invite message page and there is no error

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/50919443/110871b7-dfbf-4cd2-8636-dc250bce8835

Mobile Web - Chrome

https://github.com/Expensify/App/assets/50919443/c88cc962-1d55-406a-acf7-775522275518

Mobile Web - Safari

https://github.com/Expensify/App/assets/50919443/0ef18107-6df7-4850-8896-200664775e93

Desktop

https://github.com/Expensify/App/assets/50919443/b3922a70-6ff6-484b-be3b-65d90f1e4900

iOS

https://github.com/Expensify/App/assets/50919443/ff247f81-db9c-401a-b873-a2473179a85c

Android

https://github.com/Expensify/App/assets/50919443/b685a882-8836-4f24-a284-f95f68eae21b

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.3.53-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/yuwenmemon in version: 1.3.53-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Change छ to ळ

We need to add a few words that pertain to ळ. A bigger analysis (monogram, bigram etc.) needs to be done, but for now, it appears that ळ appears more frequently in शरद-like words.
Temporary change, only for mvp-1.

Also, randomize the list of words! D'oh!

Also, s/इ/ई


Add URL encoding support and index.html automatic mapping support in ContentRouteHandler

Add the following code after here:
if (filePath.EndsWith("/"))
{
    filePath += "index.html";
}
filePath = WebUtility.UrlDecode(filePath);

After adding the above code, my Vitespress documentation website can now function properly.

Resolved in v6.1.5, thanks @ChZhongPengCheng33


ARROW-11669: [Rust] [DataFusion] Remove concurrency field from GlobalLimitExec and SortExec

Remove redundant concurrency field from GlobalLimitExec and SortExec. This was used before we fully moved to Tokio.

@alamb @jorgecarleitao fyi


Update index.mdx

Add a sentence to highlight conversion to Parquet

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


remove DR matrix kb

remove DR matrix kb as its focus was on premium storage

Please create a 303 as well as this is a delete in prep for premium retiring

unsure why this failed checks as i'm removing an existing kb only.

@chrislittle You also have to update Servers/centurylink-cloud-backup-and-recovery-services.md because that references this article.  Do that in this PR to fix the check.

this is now fixed as well @jim-phillips

@chrislittle is there a replacement article for this kb? In other words, should we send the any traffic that does find this article to an sbs kb.

@rpdubose nope there is no replacement as its sole focus was premium storage details.  i'd just redirect to the kb root unless you have some other approach you like to take for completely obsolete kbs


Show compression levels in an ActivePivot application

ActivePivot is capable of compressing chunks, creating single-value chunks, offset chunks, etc.
This information can be viewed in MAC. Yet, there is no measure for the saved space.
Intuitively, we could compute for each chunk a measure being chunk_size / chunk_visible_size, giving a ratio of the saved memory.

Non-bug issues are to be tracked by the internal Jira until PIVOT-6552 is done.


Hyperlink DOIs against preferred resolver

Hello :-)
The DOI foundation recommends this new, secure resolver. Accordingly, this PR updates all DOI links.
Cheers!

thanks!

You're welcome, and thanks for merging :-)


[zh-cn] User Namespaces document is missing

This is a Feature Request

What would you like to be added

add and translate Chinese document:
content/zh-cn/docs/concepts/workloads/pods/user-namespaces.md
English:
https://kubernetes.io/docs/concepts/workloads/pods/user-namespaces
Why is this needed
Support for more localization.
Comments

/language zh
/assign

/triage accepted

This issue is solved by #39023
/close


Autosave a shadow state

Is your feature request related to a problem? Please describe.
If the GUI crashes all changes are lost.
The solution we will implement
We will add a feature that periodically saves to a "shadow file" which gets deleted upon clean exit.
If such a shadow file exists on load, hal suggests to restore the state from that file instead.
Related to issue #149

Done.


Fixes #61 - subclass does not copy static methods

Fixes #61, subclassing will now copy any static methods added by extend. I've also added some helper commands which make local testing easier, and amended the unit tests accordingly.
I have not updated the .min.js file, as I'm not sure which minifier you preferred to use, or any optimisations that you may usually apply. Plus this would have to be regenerated at the point of merge anyway, for sanity etc.
From what I can tell, this PR does not cause any regressions, however I'm in the process of adding automated multiple platform testing, which I've raised in #62. I'd recommend not merging this PR until I've submitted the results of these tests (which will be in the next few hours)

This should now be safe for merge. Unit tests passed on the following browsers;
Chrome latest on Windows 7
Firefox latest
Android emulator 4.4
Safari 8.0 on Yosemite
iPhone simulator 8.2 on Yosemite
IE 11 on Windows 8.1
IE 10 on Windows 7
IE 9 on Windows 7

See comment on #61. This is the intended behaviour of extend.


Remove the  Parentage  "GO:0032993   protein-DNA complex from chromatin and kinetochore

Could we remove the  Parentage  "GO:0032993   protein-DNA complex
From kinetochore and chromatin
otherwise we can't make "occurs_in" annotations to them In Noctua
https://github.com/geneontology/noctua/issues/899#issuecomment-2189138801

This changes all allowed relations in tbe files people provide. Are these
REALLY cellular components? This causes a lot of issues, we cannot swap
back and forth easily.  We also need to coordinate with Alex.
Le mar. 25 juin 2024, 17:47, Val Wood @.***> a écrit :

Could we remove the Parentage "GO:0032993 protein-DNA complex
From kinetochore and chromatin
otherwise we can't make "occurs_in" annotations to them In Noctua
geneontology/noctua#899 (comment)
https://github.com/geneontology/noctua/issues/899#issuecomment-2189138801
—
Reply to this email directly, view it on GitHub
https://github.com/geneontology/go-ontology/issues/28301, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEPWUGUMVZL7SOMWZ7CIZTZJGGIXAVCNFSM6AAAAABJ4EFNM6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM3TGMBSHEZTGNA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I don't think of chromatin as A protein complex, it's multiple complexes? How would we define its scope as a complex? it's isn't stochiometric?
I think we do want to use these as "cellular components".
The Spindle pole body/centrosome, and the kinetochore are major signalling hubs. Many processes occur there....
For example
Septation initiation signalling/ mitotic entry/ mitotic exit (spindle pole body/centrosome)
https://pubmed.ncbi.nlm.nih.gov/38670849/
mitotic spindle checkpoint/ meiotic cohesion protection (kinetochore)
I'm not following how it changes the allowed relationships?
CC @vanaukenk

Can we discuss this one on an editors call?

I'm not following how it changes the allowed relationships?

Annotations to  protein-containing complex & children use 'part of'
Annotations to cellular anatomical entity & children use 'occurs in'
So, when we make these changes we need to notify GOA and Noctua developers, so that they map annotations to the correct relation. This is not difficult, it just needs some coordination.

I don't understand which annotations need to be fixed.

The relations need to be fixed as I described above https://github.com/geneontology/go-ontology/issues/28301#issuecomment-2217159599

@ValWood Kinetochore is not a complex; you shoudl have been able to use 'occurs_in' with kinetochore

d Kinetochore is not a complex; you shoudl have been able to use 'occurs_in' with kinetochore

I can. Not sure what the issue was with kinetochore...

I agree with @ValWood: "I don't think of chromatin as a protein complex, it's multiple complexes"


Add img_hash module

Hello,
First of all, thank you for this project which allows me to kickstart an old project idea of mine. And I think it will help a lot of other developers.
I needed the img_hash module so I took the liberty to implement it.
I am a beginner in flutter and this is my first contribution to open source so do not hesitate to point at anything wrong in what I did.
I tried to stay as close as possible to the gocv implementation but I think some things can be improved, especially the tests.

Great! Thanks for you contributions, I will take a look at it recently.
BTW, actually, the current implementation is not robust so I am working on rewriting the implementations of gocv, including adding the ability to catch exceptions and avoid using bare pointers, this will make the exceptions more friently (#13 ), and I am trying to make the APIs more concise and similar to opencv-python, these are breaking changes and may be released in v1.0.0.
I will push recent commits to catch-exceptions branch, you can take a look at it and change the current implementation of img_hash to the new styles if you have more time.


Backport the dandiset listing component to legacy ui

Replace the current ui (girder hierarchy widget) with the newly created dandiset listing component.
This should:

call the dandiset listing endpoints (currently will only return drafts)
present the list of dandisets by name
when a row is clicked, it should go to the current DLP for the dandiset
the DLP should still go to the metadata editor
the DLP should still allow a display of the hierarchy widget for the contents of the Dandiset folder
the contents of the hieararchy widget should allow a link back to the DLP, using the eyeball icon as current

Also fixes #167.


OOB Panic on specific arrangements of LuaJIT-style integer formats (LL/ULL)

Clue seems to support LuaJIT-style long integer literals (256ULL, -4LL, etc.), but parsing seems to trip up on certain arrangements of the literal. An example (newline included, works fine if EOF is immediately after ULL):
local a = 2ULL

panics with:
thread 'main' panicked at core\src\scanner.rs:180:18:
index out of bounds: the len is 14 but the index is 14
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Different combinations of the lines before and after the usage produce odd results, and even LL's behavior is very different from ULL in terms of what panics or not. There seems to be no clear pattern on how the panic happens, so perhaps the method of parsing should be changed.
Here is a matrix of which arrangements error out (ones highlighted in red):

Turns out the issue was the scanner not reading ULL and LL properly.
It has been fixed in 4.0


Add Total Task Time

On the Task Page, I want to see the total time a task has taken in the activity view.
This is kinda interesting because of the multiple databases support.
Also, move the "time entry" out of activity up.

Right now I'm looking at writing a native query using SUM(....) and converting it to a php DateInterval object. I'm investigating using a custom doctrine type for cross-database support.
Here's a wip-starter using postgres and extract epoch.
src/Repository/TaskRepository.php
public function getTotalTimeForEntry(string $taskId) {
    $rsm = new ResultSetMapping();
    $rsm->addScalarResult('duration', 'd', 'float');

    $sql = 'SELECT extract(epoch FROM SUM(time_entry.ended_at - time_entry.started_at)) as duration ' .
        ' FROM time_entry WHERE ended_at IS NOT NULL';

    $query = $this->_em->createNativeQuery($sql, $rsm);
    $result = $query->getResult();

    return $result;
}

In the end, I created a DQL function to get the total seconds and then converting that into a DateInterval.


Duplicate loading observables

Currently, the datatable contains a loading observable that is set before loading data from the server. There is also a showLoading computed which just returns the value of the loading observable.
We should eliminate the showLoading computed and just have the loading observable.
For now, we could just point showLoading to the loading observable for backwards compatibility and note that showLoading is deprecated.

Assigned it to the 1.0.0 milestone since this is technically a non-backward-compatible feature


Flow types

Unfortunately, I don't have time to do this by myself, but it will be nice to have flow type definitions for this module
Currently, flow raises an error because chai does not have additional methods (instead of the default behavior of ignoring module)

https://www.npmjs.com/package/@types/chai-enzyme exists; flow could be added here: https://github.com/flow-typed/flow-typed/tree/87f3b2251f175a68c0ea9ec47ef489eabaa44e6c/definitions/npm


[react] Can't have the className customizable - it's overridden by the generated code

Thanks for this tool, seems very interesting, but I'm blocked with a small issue:
Generated component has className overriding the one from {...props}
export function Spinner({ children, fullHeight, ...props }: PropsWithChildren<Props>) {
  return (
    <div {...props} data-full-height={fullHeight} className="spinner"> // this "spinner" overrides classes I pass
      {children}
    </div>
  );
}

I always proxy and merge the className so the parent/consumer could layout my component with tailwind classes. I could explicitly define all the props that affect the way it appears and cover all the cases, but it's not a Tailwind-way I'd say (much more code needed).
Would be cool if this awesome tool merged (at least optionally) that mandatory generated className with what comes from the props, like below:
className={`spinner ${props.className ?? ''}`} // or something like that

Thanks for the kind word :)
Personally, I think it's better to have "closed" components when building a design system. Allowing any class to be passed could let users modify the positioning but they could then change the font style, the background, etc... of the component.
Also typos in class names wouldn't be caught by TS.
Instead the suggested approach with MistCSS is to expose positioning (or other) props using CSS variables and then use Tailwind theme vars.
See the JS section here:
https://typicode.github.io/mistcss/integration/tailwind/
  <CustomButton
    padding={theme.spacing.8}
    color={theme.colors.blue.900}
  >
    Save
  </CustomButton>

Your code editor will autocomplete and type check padding, color and theme.
If you need to pass classes, you can wrap the generated Mist file into a component for this.
<Wrapper className={props.className}><CustomButton /></Wrapper>


Add coverage test #1

Phew!
Here we go. Lean solution with only one tool and almost zero config.

And coverage is awesome

Wow. So much better! \o/ :tada: :clap:

It was quite a journey!

Totally worth it. =)

No doubts, rewarding experience. Going to use some of the research results
in my day-to-day work and personal libs as well.
--
Sincerely yours, Nikita Butenko
Google Talk<EMAIL_ADDRESS>Skype: nikita.butenko
Mobile: +61 450 264 801
On 19 June 2015 at 11:46, Eric Elliott<EMAIL_ADDRESS>wrote:

Totally worth it. =)
—
Reply to this email directly or view it on GitHub
https://github.com/ericelliott/prod-module-boilerplate/pull/10#issuecomment-113337802
.


RTL Hebrew titles

it looks better with new RTL changes

This needs rebased on master or recreated, sorry 😭

done, @mikemcquaid thanks a lot
I'm sorry for this lot of issues and PR's opening

can you please wait a little longer?

it good to go

I'm sorry for this lot of issues and PR's opening

Don't apologise, that's a good rather than bad thing! Thanks again @sijad!


Can't set text programatically

It looks like the override of the 'text' member breaks the functionality - I'm calling textField.text = "Something" and nothing happens..
Either that or I'm missing something huge here :-/

Hi! In ShowcaseExampleViewController.swift at line 82 if I add this line:
self.emailField.text = "Hello World"

Then I see the text being set as expected:

Can you share an example on where you can't get the text property to work? Without being able to reproduce it, I won't be able to help unfortunately.

Hi Gergely,
Sorry man, my bad! I'm doing something weird with a UICollectionView in which the text fields are located, this caused the problem.
Please close and ignore!


site is not published

Let's publish Maven site, similar to how it works for https://www.objectionary.com/jeo-maven-plugin/
See https://github.com/objectionary/jeo-maven-plugin/pull/358

@yegor256 the puzzle #47 is still not solved.

@yegor256 the only puzzle #47 is solved here.


remove version from cloudbuild

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

ping @jichenjc after this I need to make 1.27.1 and promote images as well

/lgtm
/approve


Automated cherry pick of #2536: fix: bucket mkdir may create path with empty whitespaces

Cherry pick of #2536 on release/2.12.
#2536: fix: bucket mkdir may create path with empty whitespaces

/lgtm

/approve