B-Table not working as expected after update from v0.8.15 to further versions

Describe the bug.:
B-Table not working as expect after update from v0.8.15 to further versions, including the latest v0.9.26. I followed the docs and updated the code, but its not working as expected.
To Reproduce. :
1 .Initially our b-table code was like:

        <template v-slot:cell(createdAt)="data">
            {{ data.value }}
        </template>
        <template v-slot:cell(expires)="data">
            {{ data.value }}
        </template>

And then it would show table like:

Created At
Expires

20 Jan 2023
20 March 2023

1 Sept 2022
Never

But now after the upgrade, its only showing the headers, value is not being shown. I modified the b-table code as follows:

        <template v-slot:select-cell(createdAt)="data">
            {{ data.value }}
        </template>
        <template v-slot:select-cell(expires)="data">
            {{ data.value }}
        </template>

This is the output:

Created At
Expires

Here, when i inspect the tbody, its empty.

Expected behavior:
Expected to show the values.
Screenshots:
Not necessary as no errors including typescript errors are thrown. Its just that no T-body i shown.
Environment:

OS: Ubuntu 23.04
Package Version: Starting from v0.9.0. (Last working was v0.8.15)
Npm Version<EMAIL_ADDRESS>

If I'm doing it wrong, I'm sorry, but please throw some light on this.

I have exactly the same thing, please fix it as soon as possible, this is a megabug
#1335

I'm going to need a reproduction because I'm seeing accurate things on my end.

it is easy :)
compare version 0.9.23 with a higher version, then you will find the difference and see what happend.
version 0.9.23 is the latest working version with b-table !!!

Try 0.10. anyway I'm using BTable w/o any major issue. Can you post some
code?
Il mar 8 ago 2023, 07:20 susanne99 @.***> ha scritto:

it is easy :)
compare version 0.9.23 with a higher version, then you will find the
difference and see what happend.
version 0.9.23 is the latest working version with b-table !!!
—
Reply to this email directly, view it on GitHub
https://github.com/bootstrap-vue-next/bootstrap-vue-next/issues/1331#issuecomment-1668925887,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPZLPP4FNUPEGHIRSXF46LXUHEDNANCNFSM6AAAAAA26DNXGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

@makroxyz tried 0.10.0 rn and its still not working as expected.

            <template v-slot:table-busy>

                    Loading...

            </template>
            <template v-slot:select-cell(index)="data">
                {{ data }}
            </template>
            <template v-slot:select-cell(createdAt)="data">
                {{ data }}
            </template>
            <template v-slot:select-cell(apiKey)="data">
                {{ data }}
            </template>
            <template v-slot:select-cell(expiresAt)="data">
                {{ data }}
            </template>
            <template v-slot:select-cell(actions)="data">
                {{ data }}
            </template>

This is the bare minimum code, which was working fine in 0.8.15. But after that for any versions I'm not able to get it working,
I couldn't figure out what went wrong.

Also @VividLemon BTable playground is not updated right? Also BTable doc is missing.

it works for me

            <template v-slot:table-busy>

                    Loading...

            </template>
            <template #cell(index)="data">
                {{ data.value }}
            </template>
            <template #cell(createdAt)="data">
                {{ data.value }}
            </template>
            <template #cell(apiKey)="data">
                {{ data.value }}
            </template>
            <template #cell(expiresAt)="data">
                {{ data.value }}
            </template>
            <template #cell(actions)="data">
                {{ data.value }}
            </template>

Sorry, forgot to mention that I'm dynamically setting "keys" value beforeMount() from backend using api calls.

So is it working now?

@makroxyz if the keys are static its working,
If its dynamic, like when fetched from api, then it's not working.
Checking docs now.
Will update.

I'm also experiencing lots of problems: I tried to update from 0.9.9 to 0.10.1 (and I tried the whole thing twice) → b-table was not working. Sometimes the headers were missing, sometimes the items/rows were missing and in other instances, everything was missing. I couldn't figure out a pattern. Personally, I'm sticking to 0.9.9 until this issue is cleared.

For me, all other things were working. Like the headers and all.
My table is not selectable or anything,

Nice that it works for you, but there are several users where it doesn't work. we have been using the table for a long time, from 0.9.23 it no longer works without us having changed anything. I have 100 tables in my program, I can't change them all!

Nice that it works for you, but there are several users where it doesn't work. we have been using the table for a long time, from 0.9.23 it no longer works without us having changed anything. I have 100 tables in my program, I can't change them all!

Could you post an example?

not really, sorry, because it is a big app, and all my tables are dyn. filled with data from server. i don't have any "static table"
the problem exists, see other issues

Gesendet: Donnerstag, 10. August 2023 um 12:40 Uhr
Von: "Marco Curatitoli" @.>
An: "bootstrap-vue-next/bootstrap-vue-next" @.>
Cc: "susanne99" @.>, "Comment" @.>
Betreff: Re: [bootstrap-vue-next/bootstrap-vue-next] B-Table not working as expected after update from v0.8.15 to further versions (Issue #1331)

Nice that it works for you, but there are several users where it doesn't work. we have been using the table for a long time, from 0.9.23 it no longer works without us having changed anything. I have 100 tables in my program, I can't change them all!
Could you post an example?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

So have any of you managed to figured out why you are having issues? Because I check a week later, and I still don't have a single replication

@VividLemon yes, ill explain.
If you pass the items directly as a data property, it works good.
But when you add the items dynamically, say over an api call or something, then it won't display any rows.
Eg:
Lets say we initialise the items as an empty array in the data property. And then we fetch it in hook stage, say in beforeMount, we make the api call and set the items dynamically. At that time, it won't load the dynamically added rows. It still shows empty as we set in the data property.

Same issue here. I am using a vue ref as the items property, which is filled and updated with data from an API through SWRV (Stale-While-Revalidate for Vue). The table only takes the first value of the ref, and after that, the data remains the same. A minimal example:

<template>

</template>

In this example, the types are as follows:
const data: Ref<ResponseType | undefined>;
const error: Ref<any>;
const isValidating: Ref<boolean>;
Interestingly, adding the :busy=isValidating prop actually works perfectly. When changing e.g. the search from elsewhere, SWRV  will revalidate and the loading is shown during the fetching. So, it seems to affect the :items prop only.
Opening Vue devtools, I noticed that BTable contains a BTableLite. BTable shows the updated items prop value, while BTableLite shows only the initial items prop value. Hope this helps!

Changing the per-page value dynamically is also not working.
BTable stays at the initial value.

I think I found at least one cause of this problem!
If I change this code part inside BTable.vue (line 242):
const {
  computedItems,
  computedDisplayItems,
  updateInternalItems,
  filteredHandler,
  notifyFilteredItems,
} = useTableItems(
  props,
  {
    sortInternalBoolean,
    isFilterableTable,
    noProviderPagingBoolean,
    isSortable,
    requireItemsMapping,
    sortDescBoolean,
  },
  usesProvider,
  sortByModel
)

to this:
const {
  internalItems,
  computedItems,
  updateInternalItems,
  filteredHandler,
  notifyFilteredItems,
  computedDisplayItems,
} = useTableItems(
  props,
  {
    sortInternalBoolean,
    isFilterableTable,
    noProviderPagingBoolean,
    isSortable,
    requireItemsMapping,
    sortDescBoolean,
  },
  usesProvider,
  sortByModel
)

at least the per-page prop is working now.

I think I finally (after several hours deep diving) find the cause of the problem.
It stucks in the useTableItems composable inside the computedItems and  computedDisplayItems const definition.
Since this condition is in most cases true in case of using a table data provider:
if (usesProvider.value && !flags.noProviderPagingBoolean.value) {
      return items
    }

this returns an empty array, because displayStartEndIdx has its initial value [0,0] (last one is zero, because internalItems.value.length = 0, because items prop is a empty array in the beginning.
Because of this, return computedItems.value.slice(displayStartEndIdx.value[0], displayStartEndIdx.value[1]) returns an empty array as well, since displayStartEndIdx.value[0] = 0 and displayStartEndIdx.value[1] = 0.
Since the pagination is normaly done by the provider function it self (or better the api who delivers the data), there is no slice needed.
To fix this issue, an easy solution could look like this:
const computedDisplayItems = computed<TableItem[]>(() => {
    if (
      tableProps.perPage === undefined ||
      (usesProvider.value && !flags.noProviderPagingBoolean.value)
    ) {
      return computedItems.value
    }
    return computedItems.value.slice(displayStartEndIdx.value[0], displayStartEndIdx.value[1])
  })

I created a forge of this repo, where I also enhance the filter prop to allow an object and some other small thinks.
I don't know if it makes sense, that I create a pull request for it, since I didn't followed the contribution guidelines (commit message format, more than one topic in one PR ...)

Even in the old Bootstrap-Vue, there were certain workarounds that you needed to perform in the case of async data loading.  Two possible workarounds:
-Set a key: prop on the table, and bind it to a data member that you increment whenever your data refreshes
-Add a v-if attribute to the table, and set it to a variable that evaluates to true when your data is loaded.

I also have this problem.
But I find the way to trigger this problem that when I add the sortable in fields, the data will missing.
If there is no sortable prop, data will be displayed.
// work fun
{ key: 'account', label: 'account' },

// didn't work
{ key: 'account', label: 'account', sortable: true },

Even in the old Bootstrap-Vue, there were certain workarounds that you needed to perform in the case of async data loading. Two possible workarounds: -Set a key: prop on the table, and bind it to a data member that you increment whenever your data refreshes -Add a v-if attribute to the table, and set it to a variable that evaluates to true when your data is loaded.

Adding something like :key="JSON.stringify(myItems)" is not only a bit ugly but also doesn't seem to work.

Hi, I have the same issue. When data is static it works perfectly. But when you change the source and filter, it is not working anymore. I add here an example with a component : Select group 2 then filter by red word.

I don't know if it's the same issue for everyone here but I found that upgrading past 0.9.26 broke my tables. After a lot of debugging it was because the keys for our items had periods "." in them. Once I replaced the periods wit underscores I could fully upgrade to 0.14.8.
//items
return data.map((key) => {
//remove periods from keys because Bootstrap Vue Next > 0.9.26 doesn't like them
return JSON.parse(JSON.stringify(key).replaceAll(".", "_"));
});
//keys
return columns.map(({ key, shortTitle }) => {
return {
key: key.replace(".", "_"),
label: shortTitle,
sortable: false,
};
});

Hi guys,  i just updated bvn to the latest version (v0.14.10) and bTable is working as expected. I have not made any changes apart from the ones i mentioned while opening the issue.
If anyone have the same issue, please feel free to reopen the issue.
Thanks.

I have same problem with v0.14.10

There isn't a whole lot of information as to what exact issue this issue seems too relate to. It simply states "just doesn't work". Regardless of this, I have tested variations of using the provider prop and things seem to be working on 0.15

Where/when is 0.15 scheduled for release? Cause the only reference I see is in the #1533 'chore release main' pull request, but it seems to be blocked?


LateInitializationError on controller method

Is your feature request related to a problem?
I'm having a couple of issues with the latest update that removes search field options and instead requires an entire TextField instead. I like the thought of adding more flexibility to the field, however this seems a bit heavy handed to me. To try to get this to work, I've basically had to dig through the older version of the code and copy and paste the text field that was previously being built.
My first issue with this is that now, instead of having to provide just a few options that were of interest to me, I now have to provide the entire TextField. Again, I appreciate the flexibility, but now there is no ability to rely on default options that made things easier to use.
Second, I'm trying to recreate the previously available behavior of being able to clear the search field with showClearSearchFieldButton. It used to be you could just set that to true and everything would work as expected. However, now you have to create the IconButton yourself and use the MultipleSearchSelectionController to clear the search field. But, it turns out that the controller's function isn't set until you initialize the MultipleSearchSelection itself, so this seems like a circular dependency to me. Here's basically what I am trying to do (irrelevant code is deleted):
  final _textController = TextEditingController();
  final _searchController = MultipleSearchController<User>();
// ... other stuff

Widget _selectUsersDropdown() =>
      MultipleSearchSelection<User>(
        controller: _searchController,
// ... other config
        searchField: _searchField(_searchController, _textController),
        hintText: widget.hintText, // slightly confused why this field still exists, shouldn't it just be what's on the search field?
      );

  TextField _searchField(MultipleSearchController<User> searchController, TextEditingController? textEditingController) =>
// this text field is mostly copied from the older version of this library
      TextField(
        enableSuggestions: true,
        autocorrect: true,
        controller: textEditingController,
        decoration: InputDecoration(
          contentPadding: const EdgeInsets.only(
            left: 6,
          ),
          hintText: widget._hintText ?? 'Search for users',
          hintStyle: const TextStyle(
            fontSize: 14,
            fontWeight: FontWeight.bold,
          ),
          border: OutlineInputBorder(
            borderSide: BorderSide.none,
            borderRadius: BorderRadius.circular(20),
          ),
          suffixIcon: IconButton(
            onPressed: searchController.clearSearchField, // **** HERE I try to recreate the clear search field button as before, but this function is not initialized
            icon: const Icon(
              Icons.clear,
            ),
          ),
        ),
      );

I guess the point of this issue is to see if you'd be willing to have it so you can provide the options individually as before, or if you wanted to provide the entire text field, to be able to do that as well, and default to the text field if it is provided, otherwise do the previous behavior. I am also curious to know how to recreate the clear search field button when the controller function has not been initialized.
Thanks!

Hello @anqit and thanks for pointing out the issue !
The real issue here is that the MultipleSearchSelectionController throws LateInitializationError which is obviously not intended.
I'll try to rework the whole controller logic and maybe try a different approach to achieve the same behaviour.
Thanks and sorry for any incovenience that this may have caused ✌

@anqit
Can you try changing how you call the method ?
              suffixIcon: IconButton(
                onPressed: () {
                  controller.clearSearchField();
                }, //  Change here
                icon: const Icon(
                  Icons.clear,
                ),
              ),

Because the old way was calling the method while the widget was not yet built.

@anqit Can you try changing how you call the method ?
              suffixIcon: IconButton(
                onPressed: () {
                  controller.clearSearchField();
                }, //  Change here
                icon: const Icon(
                  Icons.clear,
                ),
              ),

Because the old way was calling the method while the widget was not yet built.

I'm guessing that would work, but I don't think that should be necessary. What if instead of each of the controller's methods being late initialized, the controller was assigned a late initialized reference to the search selection when the box is created? I think it would fix this problem, and semantically be more correct, because calling the methods would fail if the controller is never assigned. Something like:
class MultipleSearchSelectionController {
    late final MultipleSearchSelection selectionWidget;

    void setWidget(MultipleSearchSelection selectionWidget) { this.selectionWidget = selectionWidget; }

    void clearSelection() { selectionWidget.clearSelection(); }
    // .... other hooks
}

and then in the MultipleSearchSelection constructor:
MultipleSearchSelection._(
    // others
    MultipleSearchSelectionController? controller,
) controller = controller ?? MultipleSearchSelectionController() {
    controller.setWidget(this);
}

syntax might be off, but something like that?

Also, and I can open a separate issue if you think that would be better, but any thoughts to bringing back the other properties and having a default TextField?

I'll look into your suggestion if it could work, I haven't seen similiar pattern again to be honest.

Also, and I can open a separate issue if you think that would be better, but any thoughts to bringing back the other properties and having a default TextField?

Yes please do if it is not a big deal for you.

@anqit I have refactored the MultipleSearchController. You will no longer get the LateInitializationErrors with version 2.6.2 🥂

@anqit can you please give me a minimal reproducable code ??


SQL Instances not supported

Hi, there does not seem to be any option to specify named SQL instances in the configuration. Am i missing something obvious as each time i try to add a named instance into the config file i get an "Invalid escape character" or it just does not connect. Configurations i have tried so far are below.
[servers.servername]
ip = "servername\instancename"
port = 1433
username="someuser"
password="somepassword"
gives "invalid Escape character"
[servers.servername]
ip = "servername\instancename"
port = 1433
username="someuser"
password="somepassword"
runs but gives the following output
2016/12/11 22:10:14 [log.go:299 Error()] [E] Error while executing script%!(EXTRA *errors.errorString=Login error: read tcp #.#.#.#:59711->#.#.#.#:59044: wsarecv: An existing connection was forcibly closed by the remote host.)
2016/12/11 22:10:14 [log.go:299 Error()] [E] Error while executing script%!(EXTRA *errors.errorString=Login error: read tcp #.#.#.#:59709->#.#.#.#:59044: wsarecv: An existing connection was forcibly closed by the remote host.)
[servers.servername\instancename]
ip = "servername or ip address"
port = 1433
username="someuser"
password="somepassword"
gives "Bare keys cannot contain '\'"
If you need any more info please let me know.
Thanks

Hi,
you have 2 choices:

[servers.servername\instancename] -> replace the backslash with an underscore (_)
double the backslash in the ip


404 ERROR

W: Failed to fetch http://ppa.launchpad.net/alessandro-strada/google-drive-ocamlfuse-beta/ubuntu/dists/jessie/main/binary-amd64/Packages  404  Not Found
W: Failed to fetch http://ppa.launchpad.net/alessandro-strada/ppa/ubuntu/dists/jessie/main/binary-amd64/Packages  404  Not Found

It looks like you are fetching packages for Debian Jessie, but the PPA contains packages only for Ubuntu (xenial, zesty, ecc.).

I don't know why, but it's looks locked. Than I try chmod a+rw command, but it's looks not very useful.
I used OPENVZ/Ubuntu16.04/Linux 2.6.32-042stab123.9

If you want you can enable debug output (with -debug) and check the log files (gdfuse.log and curl.log) in ./gdfuse/googledrive to see what it's doing.

I was tryed your command, and it still can't work.
google-drive-ocamlfuse -label googledrive ~/googledrive -o nonempty -debug
Starting application setup (label=googledrive, base_dir=).
[0.001636] TID=0: Loading configuration from /root/.gdfuse/googledrive/config...done
Opening log file: /root/.gdfuse/googledrive/gdfuse.log

I used chmod a+wr for curl.log and gdfuse.log

With -debug the process remain in foreground. You should check the content of the log files to see what's going on.

Thank you for your patience, I tried, there is no write in the curl.log file, but gdfuse.log has
[0.005311] TID=0: Setting up googledrive filesystem...
[0.005341] TID=0: BEGIN: Saving configuration in /root/.gdfuse/googledrive/config
[0.005516] TID=0: END: Saving configuration in /root/.gdfuse/googledrive/config
[0.006408] TID=0: Loading application state from /root/.gdfuse/googledrive/state...done
Current version: 0.6.21
Setting up cache db...done
Setting up CURL...done

Nothing else in there.

I think the problem is that when you initialized the application with google-drive-ocamlfuse -headled -id... you didn't specify a label (so default label is used), then when you tried to mount the filesystem you specified -label googledrive. You should specify the same label when authorizing and when mounting.


No documentation regardin gcommands for 'guidance' 'steps'.

Could you please provide advice and or help regarding how to pass these commands within a CLI?  I am utilizing a service called runpod.io.  RTX A6000 Ada GPU rental.  Things work fine using:
  `
python -m flux --name flux-schnell
--height 1024 --width 1024
--prompt "random prompt"
Except I would like to know if there is a way to adjust guidance, step count, save file name, and any other parameters.  PErhaps on the --height... line?

You can specify these in the same way. Running python -m flux --help should show the options, otherwise you can find them here here, as the arguments of the main function.
For example:
python -m flux --name flux-schnell
--height 1024 --width 1024
--prompt "random prompt"
--guidance 4.2


$touched and $dirty never set on the input, $required is only set after having had a previous value

See this plunkr. The $touched and $dirty flag never seem to be set. Also, when adding required and starting off with an empty value the $required error is not set. However, when filling in a value and then removing it, it is set correctly.

Changed the controller to propagate $dirty and $touched values.

Neat, thanks for taking care of this so quickly


670 remaining migration problems

Addresses problems 1 and 3 in #670.  @pkdash @hyi Please review as soon as you can so that this can be merged in used in the next and hopefully final migration dry run.

+1

@pkdash Just pushed another commit to fix the broken unit test you found on Jenkins recently.  Thanks.

@selimnairb Reviewed your last commit and looks good.


Data Type Manager: drag-and-drop should respect selected DataTypeConflictHandler

Is your feature request related to a problem? Please describe.
When I drag and drop types from a file archive to a program archive, types from the file archive are renamed .conflict, no matter what the data type conflict handler I have set is.
Example:
program.exe contains a definition for struct s1 { char a};
library.gdt contains a definition for struct s1 {char* a};
conflict handler is set to "Replace Existing Data Type"
when s1 is dragged and dropped from library.gdt to program.exe in the data type manager, it creates the structure s1.conflict.
Describe the solution you'd like
if the data type conflict handler is set to "replace existing data type", it should replace existing data types with the same name.
If the data type conflict handler is set to "use existing data type", it should use the existing data type and ignore the new data type.
Current behavior will be preserved with the "Rename new or moved data type" handler, which is the default.
Describe alternatives you've considered
Alternately, I'm Using It Wrong and documentation should be updated on how to use the data type manager correctly.
Additional context
see CreateStructure in ghidra/Ghidra/Framework/SoftwareModeling/src/main/java/ghidra/program/database/data/DataTypeManagerDB.java

While we need to investigate the resolve logic for types pulled from archives, a work around would be to drag the type from the archive onto the type it is replacing.  Although, that will not handle any sub-types which get auto-resolved in the process.

I believe this relates to an open issue previously identified internally (GP-1307):
DataTypeManagerDB does not currently perform proper conflict handling when the type being resolved has a source (resolveDataTypeWithSource) when considering a potential conflict with a local type (no-source).

Yes that sounds correct.


124 all subnets grouping

solves #124

LGTM
We have to consider if EndpointElem is really required in the code, given that we already have VPCResourceIntf. This may allow us to reduce code duplication, as Node also embeds VPCResourceIntf. This can wait for now, but maybe open an issue for that...

https://github.com/np-guard/vpc-network-config-analyzer/issues/141
Btw - my (not yet ready) next PR further uses endpoint element


when loading markets, the UI brings up in-reporting markets for a few seconds before loading the correct (open) markets

Load market list or refresh on that page to reproduce

Fix looks good

closing this ticket isn't relevant to comment.


Filling Table Columns

Describe the Task
Performing spatial overlays on all record entries of the activity_incoming_data table to populate meta data columns. Related to ticket #873.
Filling table columns

[x] ownership
[ ] biogeoclimatic_zones
[ ] forest_cover_ownership
[ ] regional_districts
[ ] flnro_districts
[ ] moti_districts
[ ] Well proximity
[ ] UTM Zone
[ ] UTM Northing
[ ] UTM Easting
[ ] Albers X
[ ] Albers Y
[ ] IPMA Internal dataset
[ ] regional_invasive_species_organization_areas Internal dataset
[ ] Elevation Separate proxy to Federal Government service API
[ ] Hex ID
[ ] Hex sub ID

Just realized that many of these columns don't exist in the table. Working on a migration to add them all.


Deduplicate and remove mentions from excluded spans for TAC14

This mostly modifies prepare-tac and the scripts that call it.
I've not got tests covering these cases, which is probably bad, but I may merge soon in any case.

@benhachey, you may want to check that you find the changes to scripts/run_* produce a condonable interface.

Thanks for the ping. Interface change is fine by me. Please update the wiki
page accordingly: https://github.com/wikilinks/neleval/wiki/Convenience
On Mon Feb 02 2015 at 1:45:37 PM jnothman<EMAIL_ADDRESS>wrote:

@benhachey https://github.com/benhachey, you may want to check that you
find the changes to scripts/run_* produce a condonable interface.
—
Reply to this email directly or view it on GitHub
https://github.com/wikilinks/neleval/pull/13#issuecomment-72399976.

As per latest NIST discussions, it seems we should make this optional in the script...

Okay. In the launcher scripts I've made providing excluded spans optional by having any additional arguments beyond the basic ones be passed to prepare-tac. This may be a bit user-unfriendly (command-line arg parsing is now less strict), but seems a decent mid-way solution.

This also no longer invalidates former command-line usage of the run_tac* scripts, so I'm happier to merge it ASAP.

To avoid putting this same feature in the run_tac*_filtered scripts, those now only take a single arg, the output dir of a whole evaluation.

Ready to merge.


Feature/434/86 observers

What this PR changes/adds

Call the listeners before the state transition is persisted.
Add  confirmingSent method to ContractNegotiationListener

Why it does that
A custom extension may need to perform custom processing after a data transfer has reached a certain stage. For example, in Catena-X PRS, we wanted to run additional transfers recursively after each transfer had completed.
Triggering custom logic on TransferProcess state changes requires registering a TransferProcessListener. However listeners are not guaranteed to be called, e.g. if the instance crashes after persisting the state change but before invoking the listener. Custom logic in the listener can be crucial for the functioning of client applications, thus EDC needs to guarantee that these are called before advancing a transfer process to the next state is made durable.
Linked Issue(s)
Closes #86
Checklist

[ ] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[x] added/updated relevant documentation?
[x] added relevant details to the changelog? (skip with label no-changelog)
[x] linked GitHub project? (see the section on the right-hand side -->)

Codecov Report

Merging #145 (7d03476) into feature/434-observers-at-least-once (7028fdc) will increase coverage by 0.06%.
The diff coverage is 58.00%.

:exclamation: Current head 7d03476 differs from pull request most recent head edacfb5. Consider uploading reports for the commit edacfb5 to get more accurate results

@@                            Coverage Diff                            @@
##             feature/434-observers-at-least-once     #145      +/-   ##
=========================================================================
+ Coverage                                  59.95%   60.01%   +0.06%
- Complexity                                  2238     2241       +3
=========================================================================
  Files                                        600      600
  Lines                                      12980    12955      -25
  Branches                                     907      907
=========================================================================
- Hits                                        7782     7775       -7
+ Misses                                      4773     4756      -17
+ Partials                                     425      424       -1

Impacted Files
Coverage Δ

...gotiation/observe/ContractNegotiationListener.java
0.00% <0.00%> (ø)

.../spi/transfer/observe/TransferProcessListener.java
0.00% <ø> (ø)

...sfer/core/transfer/TransferProcessManagerImpl.java
45.08% <47.05%> (+0.93%)
:arrow_up:

...iation/ConsumerContractNegotiationManagerImpl.java
61.90% <64.70%> (+0.68%)
:arrow_up:

...iation/ProviderContractNegotiationManagerImpl.java
66.06% <66.66%> (+0.99%)
:arrow_up:

...mo/protocols/common/AbstractQueuedProvisioner.java
88.88% <0.00%> (+5.55%)
:arrow_up:

Continue to review full report at Codecov.

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


ReferenceError: antiMeridian is not defined

In the new 5.0 release, a ReferenceError is being thrown, ReferenceError: antiMeridian is not defined on https://github.com/mapbox/geo-viewport/blob/master/index.js#L16

Any updates on this?

Same issue here, the variable is missing a var

I'm getting this error too. Any reason not to close the associated PR?

I just ran into this. I went ahead and created a public branch hosting just the dist files that you can use in your package.json until someone merges that PR.
"dependencies": {
   "@mapbox/geo-viewport": <EMAIL_ADDRESS>}

Still seeing this issue.
Any chance we can get @dereekb's fix merged?

Got this issue when upgrading from nextjs -> "^13.5.6" to "latest"

Package seems abandoned but if you want to use patch-package to fix this, here's my patch:
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index b0393c1..f45a7ab 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -13,7 +13,7 @@ module.exports.bounds = bounds;

 function fetchMerc(tileSize, allowAntiMeridian) {
     tileSize = tileSize || 256;
-    antiMeridian = allowAntiMeridian || false;
+    var antiMeridian = allowAntiMeridian || false;

     var cacheKey = tileSize + String(antiMeridian);
     if (!smCache[cacheKey]) {


Refactor export to exportSchedule and update DG

Codecov Report

Merging #110 (a8663a1) into master (d2b9f41) will not change coverage.
The diff coverage is 0.00%.

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

@@            Coverage Diff            @@
##             master     #110   +/-   ##
=========================================
  Coverage     69.17%   69.17%
  Complexity      583      583
=========================================
  Files            98       98
  Lines          2047     2047
  Branches        251      251
=========================================
  Hits           1416     1416
  Misses          543      543
  Partials         88       88

Impacted Files
Coverage Δ

...logic/commands/schedule/ExportScheduleCommand.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
66.66% <0.00%> (ø)

...c/parser/schedule/ExportScheduleCommandParser.java
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

LGTM


Documentation improvement for non-get method options

Describe the improvement
The documentation tends to lack examples for other methods like put() and post(). While the methods are documented with their argument signatures, it took me a while to figure out I needed to pass {save: false} as a third argument to put() for example because the examples of this config only show get() :D

Ah, good point. Yeah we should add those examples as well.

FYI there is a PR that addresses this to some extent.  #117


Update es.json to get the auth alerts to show up in the interface

required change for the alerts UI to work, REST service will otherwise complain with this error:
Fielddata is disabled on text fields by default. Set fielddata=true on [source:type] in order to load fielddata in memory by uninverting the inverted index. Note that this can however use significant memory. Alternatively use a keyword field instead.

Thanks ward, good correction, this should really be applied to all our ES fields now we've moved the base product to ES 5.x, I'll look into that.


Add Python 3.12 support

Closes #80

@jashparekh Hello and thank you 🙏 for the PR. I did not realize CI would only run with my permission till now.
Your changes look good, but there are some errors when running tests:
ERROR src/redflag/__init__.py - ModuleNotFoundError: No module named 'pkg_resources'
ERROR src/redflag/_version.py - ModuleNotFoundError: No module named 'pkg_resources'
ERROR tests/test_sklearn.py - ModuleNotFoundError: No module named 'pkg_resources'

I have not tried to solve this and don't have any suggestions I'm afraid, but maybe you can take a look if you have time.
Cheers!

Thanks, can you approve my request to run the CI pipeline

This is wonderful stuff @jashparekh -- thank you for persevering, and thank you for the PR 🙌


Vercel deployment in CI is failing with "Uncaught AssertionError"

Error:
error: Uncaught AssertionError: Assertion failed.
    at Object.assert ($deno$/util.ts:33:11)
    at compile ($deno$/compiler.ts:1355:5)
    at async tsCompilerOnMessage ($deno$/compiler.ts:1548:22)
    at async workerMessageRecvCallback ($deno$/runtime_worker.ts:74:9)
    at buildDenoLambda (/zeit/5414d56625280cb6/.build-utils/.builder/node_modules/now-deno/dist/index.js:70:15)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)

Refs:

PR https://github.com/denoland/doc_website/pull/98

Deployment failure https://vercel.com/denoland/doc-website/838yvfwd1

PR https://github.com/denoland/doc_website/pull/93

Deployment failure https://vercel.com/denoland/doc-website/838yvfwd1

I am working on it - sorry

Fixed in #102


Show current filter if available

Currently if a filter is set, there is no persistent visible info about it.


[Feature]   Add Gitpod support

Problem
Adding Gitpod support
Description
we can add Gitpod support for contributors and users to try and setup the repo fast , without taking time to locally setup if wanting to test some changes quickly and see the results
Implementation

[x] I would be interested in implementing this feature.

Moving to discussion. With the advent of Code Spaces as part of GitHub what are others thoughts on this level of support?


PowerToys Run resets settings

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
GitHub
Running as admin
No
Area(s) with issue?
General
Steps to reproduce
It sometimes resets all the settings.
✔ Expected Behavior
I set PowerToys Run keyboard shortcut to Win+Space. It should have been it.
❌ Actual Behavior
After a few Windows restarts, it gets to Alt+Space. This problem is the same on my other pc.
Other Software
No response

Does it happen also with other utilities or only with PowerToys Run?
/bugreport

I'm having this same issue, here's my zip:
PowerToysReport_2024-09-28-18-47-04.zip

@klementineQt thanks for the bug report!
I have reopened the issue.

I eventually realized that my issue was being caused by BSODs at login that would only happen on the first login due to a driver issue with 24H2 & Voicemeeter. The issue hasn't occurred since Voicemeeter was updated to correct the issue and I stopped getting the BSODs at first boot.


Declare support for Python 3.8

This should be merged before the next release so the metadata is included on PyPI.

CI night failure is unrelated and will be fixed by https://github.com/sixohsix/twitter/pull/406.

Coverage increased (+0.3%) to 30.377% when pulling acb9b8f0c7c0f57eb8c311b79764ecec17166087 on hugovk:patch-2 into 3a8674afcf279c6a57289c9767be201065c3176b on sixohsix:master.

Coverage increased (+0.3%) to 30.377% when pulling acb9b8f0c7c0f57eb8c311b79764ecec17166087 on hugovk:patch-2 into 3a8674afcf279c6a57289c9767be201065c3176b on sixohsix:master.


Don't check if summoner is in game, but check if summoner is in a NEW game

https://github.com/freshcoders/discorki/pull/70#discussion_r1034807983

Fixed with https://github.com/freshcoders/discorki/commit/d33d97f359f7bfbc9ffde8e30d57c60c19f33171


how to find https://emmo.info/battery/0.5.0/battery

Hello, I cannot find the ontology behind this url https://emmo.info/battery/0.5.0/battery. Is it published in the github ? or somewhere else ?

You can find it here:
https://github.com/emmo-repo/domain-battery
We're working on setting up the re-direct rules to be accessible from the version IRI. You can also find URLs for the different imports in the catalog file .
Stable releases for the emmo domains battery, electrochemistry, and BattINFO are planned for this summer.

Thanks a lot
Jean
Le ven. 2 juin 2023 à 12:40, Simon Clark @.***> a
écrit :

Closed #103 https://github.com/BIG-MAP/BattINFO/issues/103 as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/BIG-MAP/BattINFO/issues/103#event-9412834011, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA7RS67AW7IISAE7FPO3ISLXJG7LPANCNFSM6AAAAAAYYC2NTM
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Jean Delahousse
Independent consultant
Knowledge Graph, Ontology, Open Data
email @.***
mob +33 6 01 22 48 55
web jean-delahousse.net
skype jean.delahousse


Hard to contribute: Giant index.vue

It is really hard to contribute to your project, because of your giant index.vue component (1.7k lines).
I suggest to

move the style into its own scss file and let the build system figure that out.
and to move the headerbar out of index.vue into its own component.

There are probably more ways to split the file up, but those are the low hanging fruits.
Cheers

Hi @davidgraeff,
Thanks for your interest into contributing!
As I add features the code base is getting bigger and bigger and I agree it would be nice to split it into multiple files now. I actually had this in mind for a while.
But there is a tradeoff: code will be more complex and not significantly shorter in the main index.
The reason for that:

some logic needs to be shared across the different components and remain in the index
increased complexity because of nested slots, passing down props, calling parent methods

I have split the header into a different file in the refactoring branch I will think it over to see what can be improved and moved but if you want to have a look and give me some feedbacks, please do so!

some logic needs to be shared across the different components

Use ES6 modules and move utility methods into own files. The build system will care about joining everything. The "updateMutableEvents" method is a good candidate for example. Basically all methods that are not "reactive".

if you want to have a look and give me some feedbacks

Sounds promising, I'll have a look.

As I add features the code base is getting bigger and bigger

I have seen your ToDo list. If you are done with that, this component will the most complete component for Vue that I've seen so far. But don't do the charts.js mistake, they are now in the second year of refactoring, from their original one-file monstrosity.
Vue provides you with a lot of tools to create small re-usable pieces. You can design (additional) features as Mixins for example (like Drag&Drop, Editable-cells, different View modes) and allow the user to add Mixins as he needs them. That way an ES6 ready build system will tree-shake your component and a basic calender will really be 8KB instead of 96KB as of now.
Cheers, David

Hi @davidgraeff,
I did a good refactoring and will stop here for the big part.
I will keep improving as I develop new features but I am closing the refactoring branch.

Header is moved into a new component
Weekday headings is moved into a new component
Styles are split where it belongs into new components
Some of the logic is moved into the new components
The main big file is now down to less than 900 lines

I will keep in mind modularising the features into  mixins, but it is not the priority now.
Thanks for your advice!

Thanks :)


Can the policy trained be evaluated on simulation environments?

Hey, I don't have a Franka Robot for now, so can the policy trained with DROID be applied to some simulation environments (e.g., robomimic)? Thank you a lot if you could help :)

Thanks for the interest in our work! We haven't tried using DROID data for sim evaluation -- one thing that could be reasonable to try is co-training between a small dataset from your simulator and DROID -- I think going 0-shot from DROID to eval in a non-visually-realistic simulator like robomimic has little hope of success.

Gotcha! Thank you!!


Make Email class a implementation of a interface (IFluentEmail). Switch from MS Test Manager to NUnit.

Hi hdiazburgos,
Most of these ideas have been implemented in the move to support .net core. If you get a chance take a look and let me know what you think.


Rework how cloning/pulling progress is presented

Currently the progress messages are just dumped into the cards:

This is bad UX. We should:

get an actual progress estimate from git (for git clone there are four steps, each of these has 0-100 progress), which can be obtained by using gitpython (see https://stackoverflow.com/a/71285627/6646912) and replacing GitPuller.initialize_repo
show a subtle progress bar under or over the tile
maybe put the detailed messages in a notification which would get automatically closed.

This sounds like a good approach to me.


passing user auth token to GraphQL request

Hi,
Is there a v2 update on issue 105? I need to do something similar but haven't managed to build the correct code and am going round in circles.   I can see overriding the WebClient  bean and having a filter within that would be the thing to do but this line - at least in the code I using from the v2 runtime dependency, GraphQLConfiguration.getWebClient doesn't exist.  Any help appreciated!
thanks
-mark

Hello,
Did you check this wiki page: https://github.com/graphql-java-generator/graphql-maven-plugin-project/wiki/client_oauth2 ?

Hi, Yes, ended up looking at that and what others have done.  Finally resolved which is great. Have pasted the code for the Filter below in case anyone else needs the same, key bit being getting hold of the HttpServletRequest so you can get at the auth header in that.
thanks.
`@Component
public class AuthTokenExchangeFilter implements ExchangeFilterFunction {
private static Logger logger = LoggerFactory.getLogger(AuthTokenExchangeFilter.class);

public final static String AUTHORIZATION_HEADER_NAME = "Authorization";

@Override
public Mono<ClientResponse> filter(ClientRequest request, ExchangeFunction next) {

	ServletRequestAttributes attributes = (ServletRequestAttributes) RequestContextHolder.getRequestAttributes();
    if (attributes == null) {
        return Mono.error(new IllegalStateException("No request attributes available"));
    }

    HttpServletRequest httpServletRequest = attributes.getRequest();

    // Extract the Authorization header from HttpServletRequest
    String authorizationHeaderValue = httpServletRequest.getHeader(AUTHORIZATION_HEADER_NAME);

    if (authorizationHeaderValue == null ) {
        logger.error("WARNING: No " + AUTHORIZATION_HEADER_NAME + " header found, when exactly 1 is expected");
    }

	ClientRequest newRequest = ClientRequest.from(request)
	.header(AUTHORIZATION_HEADER_NAME, authorizationHeaderValue)
	.build();

	return next.exchange(newRequest);

}

}`


Help needed to implement the basic functions

Description
i need help to implement this package.
i am new to angular and i just trying implement the basic usage right now and i cant figure out where to start.
Environment
i am using angular 8 and the latest version of this package
`angular
.module('app', ['angular-jwt'])
.config(function Config($httpProvider, jwtOptionsProvider) {
// Please note we're annotating the function so that the $injector works when the file is minified
jwtOptionsProvider.config({
tokenGetter: ['myService', function(myService) {
myService.doSomething();
return localStorage.getItem('id_token');
}]
});
$httpProvider.interceptors.push('jwtInterceptor');

})
.controller('Controller', function Controller($http) {
// If localStorage contains the id_token it will be sent in the request
// Authorization: Bearer [yourToken] will be sent
$http({
url: '/hola',
method: 'GET'
});
});`
where do i use this code? how to use it? where do i paste it?
Key Features:
.....
Automatically send the JWT in every request made to the server
how to make the http interceptor work automatically?

Hi @iteniasim, this module is intended for AngularJS only, for Angular you need to look at https://github.com/auth0/angular2-jwt


(server) I get disconnected when I left click anything.

I am making a server for some friends and am having problems with disconnecting
Line 270 Is where the error is
https://pastebin.com/RjTK4icz
First time using Fabric
Made java modpacks for years and wanted to try fabric

Sorry if this isn't caused by Immersive portals but the error is from it so I though this would be my best bet

Yo my portal gun mod uses the preview versions of Immersive Portals, which you can get at this github repo

Oh ok thx


Allow specifying key derivation method on sub-wallet create

When working in managed multi-tenancy mode, we store the keys for the sub-wallets within a WalletRecord in ACA-Py. These keys are then recalled when needed and used to unlock the wallet for processing messages or admin API requests intended for that sub-wallet. In the process of opening the wallet, the key is pushed through a key derivation algorithm to transform it into a wallet encryption key. This key derivation algorithm is a costly operation.
This PR implements allowing the key derivation method to be specified when creating a sub-wallet. This means that a multi-tenant ACA-Py agent can elect to use the RAW derivation method, for instance, and significantly reduce the wallet open cost.
Since these keys are securely stored in ACA-Py, using a RAW key does not seem to impact security of the key. Additionally, I don't think the profile of potential attack changes from using the key derivation method when considering wallet tokens.
Credit to @burdettadam.

@dbluhm -- can you please update your branch for merging?

Codecov Report

Merging #1719 (2c37713) into main (66735f3) will decrease coverage by 0.01%.
The diff coverage is 78.26%.

@@            Coverage Diff             @@
##             main    #1719      +/-   ##
==========================================
- Coverage   95.25%   95.23%   -0.02%
==========================================
  Files         528      528
  Lines       33120    33132      +12
==========================================
+ Hits        31547    31554       +7
- Misses       1573     1578       +5


Various warnings during build process

During the build process there are various confusing errors and warnings that popup.  Some of this is unused or dead code that needs cleaning up.  Some of it is copiler warnings.  These are confusing and should be removed or suppressed.

Known red herring errors or warnings:
cp: cannot stat '/src/prod/tools/linux/../../../../external/WinFab.Linux.Libs/Boost_1_61_0/lib/libboost_unit_test_framework.so.1.61.0': No such file or directory

Cause: unused dead code, will be removed in PR.
In file included from ./boost/thread/futures/future_error_code.hpp:13:0,
                 from libs/thread/src/future.cpp:10:
./boost/system/error_code.hpp:221:36: warning: ‘boost::system::posix_category’ defined but not used [-Wunused-variable]
     static const error_category &  posix_category = generic_category();

Multiple warnings during boost installation. Needs investigation.

@bpm-ms Please validate if this still is an issue with current Service Fabric runtime version your cluster is running. If yes, please close this issue and create new one with this guidance https://github.com/microsoft/service-fabric/blob/master/CONTRIBUTING.md#guidelines-to-files-issues-for-this-repository


Dependency updates

Interesting, all tests are passing on my machine (with the latest nigthly).

Hmmm. we might have a heisenbug.
Merged, thanks v much @pmarcelll


could not retrieve outdated packages, see the console for details

Prerequisites

[ x ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Atom keeps on showing an error message pop up: "could not retrieve outdated packages, see the console for details"
Steps to Reproduce

Start Atom editor

Expected behavior:
No error messages
Actual behavior:
Atom keeps on showing an error message pop up: "could not retrieve outdated packages, see the console for details". I am able to work in the editor but this error message keeps popping up.
Reproduces how often:
100%
Versions
Atom - 1.60.0 x64
Windows 10, 64-bit. version 21H2
If this issue cannot be resolved then at least le me know.

how I can pinpoint what is causing this issue?
How can I disable or hide this error message because it is popping up every few seconds?

thanks.

Forgot to mention something.
In the status bar there is a '2 deprecations' message in yellow color. I click on it and it shows the following information. I am suspecting this is related to the above error message "could not retrieve outdated packages, see the console for details".
=====
Use require("electron").remote instead of require("remote")
Object. - C:.....\Atom\resources\app.asar\exports\remote.js:4:6
Object. - C:.....\Atom\resources\app.asar\exports\remote.js:11:3
Module._compile - :11:149913
Object..js - :11:153507
Module.load - internal/modules/cjs/loader.js:815:32
Module._load - internal/modules/cjs/loader.js:727:14
Use require("electron").shell instead of require("shell")
Object. - C:.....\Atom\resources\app.asar\exports\shell.js:4:6
Object. - C:.....\Atom\resources\app.asar\exports\shell.js:9:3
Module._compile - :11:149913
Object..js - :11:153507
Module.load - internal/modules/cjs/loader.js:815:32
Module._load - internal/modules/cjs/loader.js:727:14
======

I have exactly the same problem for months now. There must be some way to isolate the issue / detect where the error is coming from?

I have the same issue but no idea how to view the console! Please help!


Add a virtual table to list snapshots for CASSANDRA-18102

Add a virtual table to list snapshots for CASSANDRA-18102
patch by maxwellguo; reviewed by <Reviewers> for CASSANDRA-18102

The CASSANDRA-18102

I am so sorry that this pr is discard due to an operation error, And I have create a new one . https://github.com/apache/cassandra/pull/2205


Templates for class creation

Hi all,
This is more a set of a questions as opposed to an issue:

Will it be possible to elaborate more on the class creation section?

Will it be possible to reference UltiSnips snippets as templates?

Please advise.
Thanks in advance,
rey malahay

Hello.
Can you describe workflow of your request, how you think it should work?

hi there,
thank you for the response. by the way, vim-javacomplete2 is a great plugin.
it's not a workflow. basically, what i am asking is:

In your documentation, there is a section titled 'Class creation' with a usage example that looks like this
template:[subdirectory]:/package.ClassName extends SuperClass implements Interface(String str, public Integer i):contructor(*):toString(1)

will it be possible if you can expand on how to use this feature with a sample? for example, if i want to create a class MySecretClass in package com.secret, what is the correct order of keystrokes? will it be possible to add more details to this section?

What does a typical vim-javacomplete2 template look like? Will it be possible to provide a sample?

There is a plugin called UltiSnips, https://github.com/SirVer/ultisnips, which developers use to create blocks of code that they use frequently, as opposed to writing everything from scratch. Will it be possible to use UltiSnips together with vim-javacomplete2?

Please advise.
Thanks in advance,
rey malahay

Hello.
Can you describe workflow of your request, how you think it should work?

Here is quick example:

Also, you can specify path of the class, like so: new_package.TestClass. It will create new directory new_package and put new class in it.
Templates are here: https://github.com/artur-shaik/vim-javacomplete2/tree/master/plugin/res

And about UltiSnips, you can use it, and it works on itself. I don't know how we can integrate it with jc2.

This is awesome! Thank you very much, @artur-shaik !

Here is quick example:

Also, you can specify path of the class, like so: new_package.TestClass. It will create new directory new_package and put new class in it.
Templates are here: https://github.com/artur-shaik/vim-javacomplete2/tree/master/plugin/res
It is actually not templates, but methods that generates class structure.

No worries. I'll figure it out. If i find a plausible use case, i will open an issue and put forward a proposal.

And about UltiSnips, you can use it, and it works on itself. I don't know how we can integrate it with jc2.


Service Fabric Managed Clusters - API version 2024-06-01-preview

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[x] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[x] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@a-santamaria - Please consider and respond to the active comments before resolving. In this case, please consider wrapping the VMGallery API with a more ARM-consistent API (per the feedback), rather than just straight pass-through.

@a-santamaria - Please consider and respond to the active comments before resolving. In this case, please consider wrapping the VMGallery API with a more ARM-consistent API (per the feedback), rather than just straight pass-through.

Ok, we have renamed the property tags to vmGalleryTags as suggested but kept the Boolean properties for the vmApps object

@a-santamaria - Please consider and respond to the active comments before resolving. In this case, please consider wrapping the VMGallery API with a more ARM-consistent API (per the feedback), rather than just straight pass-through.

Ok, we have renamed the property tags to vmGalleryTags as suggested but kept the Boolean properties for the vmApps object

Enums are highly suggested and is there a reason why the suggestions from previous reviewers do not work for you ?

@a-santamaria - Please consider and respond to the active comments before resolving. In this case, please consider wrapping the VMGallery API with a more ARM-consistent API (per the feedback), rather than just straight pass-through.

Ok, we have renamed the property tags to vmGalleryTags as suggested but kept the Boolean properties for the vmApps object

Enums are highly suggested and is there a reason why the suggestions from previous reviewers do not work for you ?

we decided to keep Booleans because its the same definition as vmss, so they are not going to change the behavior and that way customers can use the same definitions the have for vmss in sfmc

Please resolve merging conflict and add the label PublishToCustomers to confirm that you understand the spec will be published to customer.

@a-santamaria - Your PR is in the merge queue, but we aren't able to merge it until you fix the merge conflicts.

@a-santamaria - Just add back the MergeRequested label after resolving the merge conflicts if you still need this PR merged.

@a-santamaria - Your PR is in the merge queue, but we aren't able to merge it until you fix the merge conflicts.

@a-santamaria - Just add back the MergeRequested label after resolving the merge conflicts if you still need this PR merged.

fixed the conflict by rebasing and added back MergeRequested label, thanks!

@a-santamaria - Your PR is in the merge queue, but we aren't able to merge it until you fix the merge conflicts.

@a-santamaria - Just add back the MergeRequested label after resolving the merge conflicts if you still need this PR merged.

fixed the conflict by rebasing and added back MergeRequested label, thanks!

@a-santamaria - All required checks need to pass. You still have one required check failing: https://github.com/Azure/azure-rest-api-specs/pull/29327/checks?check_run_id=29015767632. Add back the MergeRequested label after fixing all required checks are passing.

@a-santamaria - Your PR is in the merge queue, but we aren't able to merge it until you fix the merge conflicts.

@a-santamaria - Just add back the MergeRequested label after resolving the merge conflicts if you still need this PR merged.

fixed the conflict by rebasing and added back MergeRequested label, thanks!

@a-santamaria - All required checks need to pass. You still have one required check failing: https://github.com/Azure/azure-rest-api-specs/pull/29327/checks?check_run_id=29015767632. Add back the MergeRequested label after fixing all required checks are passing.

@mentat9 the requried check was just complaing that I had to add PublishToCustomers label I don't see MergeRequested anymore

/azp run

@a-santamaria - The merge process changed, and I didn't get the memo. PR authors with write access to the repo now can merge their own PRs when all required checks have passed. There is no longer a step to request merge.
I would have merged your PR for you right now, but there was a stuck check preventing it, so I reran the pipeline. I will revisit your PR after the checks finish running and do the merge for you to help expediate things. Or if you get here before I do, feel free to merge it yourself. Sorry for giving you outdated instructions previously.

@a-santamaria - The merge process changed, and I didn't get the memo. PR authors with write access to the repo now can merge their own PRs when all required checks have passed. There is no longer a step to request merge.
I would have merged your PR for you right now, but there was a stuck check preventing it, so I reran the pipeline. I will revisit your PR after the checks finish running and do the merge for you to help expediate things. Or if you get here before I do, feel free to merge it yourself. Sorry for giving you outdated instructions previously.

@a-santamaria - The same check (Protected Files) is still not passing. I don't know anything about this. I'd recommend asking for help from the experts on the Teams channel: https://teams.microsoft.com/l/channel/19%3A0351f5f9404446e4b4fd4eaf2c27448d%40thread.skype/API Spec Review?groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47.


Throws returns the promise

Finally found the solution for #123
By returning the promise, it's possible to check the throwed error like this which succesfully waits untill the promise is resolved/rejected.
test(async t => {
	await t.throws(throws(), /hello world/);

	function throws() {
		return new Promise(function (resolve, reject) {
			setTimeout(function () {
				reject(new Error('hello world'));
			}, 2000);
		});
	}
});

lgtm
@sindresorhus?

Looks good :)


[ZEPPELIN-5385] Wrong src folder for spark-shims modules

What is this PR for?
Wrong src folder for spark-shims modules. We should put it in java folder instead of scala folder.
What type of PR is it?
[Improvement]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5385

How should this be tested?

Ci pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Good find. Let's wait for the CI.

LGTM


Slow inference on LLM model (CPU Bound?)

I tried to run starcoder LLM model by loading it in 8bit.
It works as expected but the inference is slow, one CPU core is running 100% which is weird given everything should be loaded
into the GPU (the device_map shows {'': 0}).
I tried using pytorch profiler and I am seeing this
------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  -------------------------------------------------------
        Name    Self CPU %      Self CPU   CPU total %     CPU total  CPU time avg     Self CUDA   Self CUDA %    CUDA total  CUDA time avg    # of Calls                                             Input Shapes
------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  ------------  -------------------------------------------------------
MatMul8bitLt        11.65%        1.214s        19.18%        1.998s     445.921us     390.375ms         9.73%     515.878ms     115.151us          4480                     [[4, 1, 6144], [6144, 6144], [6144]]
MatMul8bitLt        11.65%        1.214s        19.11%        1.991s     444.408us     391.215ms         9.75%     516.690ms     115.333us          4480                     [[4, 1, 6144], [6400, 6144], [6400]]
MatMul8bitLt        11.61%        1.210s        19.04%        1.983s     442.660us        1.068s        26.60%        1.197s     267.199us          4480                   [[4, 1, 6144], [24576, 6144], [24576]]
MatMul8bitLt        11.44%        1.192s        18.88%        1.967s     439.071us        1.154s        28.76%        1.281s     286.006us          4480                   [[4, 1, 24576], [6144, 24576], [6144]]

It shows that the CPU is stuck with MatMul8bitLt operations.
Another lead I am suspecting is that using accelerate.infer_device_map shows half of the layers on the CPU, so maybe the device map is not correct?
I am not very familiar with the internals of pytorch, so I am looking to this issue from a generalist IT pov, surely I am missing sth

I have been trying to figure this out for a week now with not much success. The forward function of MatMul8bitLt is definitely cpu bound.

Interested in this, as I am having the same issues.

The same for me for training https://github.com/TimDettmers/bitsandbytes/issues/465
It's slower than regular fp16

FWIW, I played around CTranslate2 lib, in streaming mode starcoder feels almost realtime !


Create a place to call and analyze features

At present,featurize.py contains a single instantiation of a feature builder and calls it once on a test dataset. However, in the future pipeline, we will want to write a longer script that instantiates a feature builder for each of the datasets we want to analyze, and performs the appropriate cleaning and (if appropriate) some of the analysis.
Steps to take:

Creating a feature building for every dataset.
Instantiate a FeatureBuilder for every dataset, with the appropriate input and output file paths.

Clean up outputs to contain the dependent variable.
This may look like a post-processing step. See: https://github.com/Watts-Lab/team-process-map/issues/82

Conduct the analysis.
After the post-processing, we need to do the following:

Standardize dependent variables (see https://github.com/Watts-Lab/team-process-map/issues/57); one thing to do might be to z-score everything, or to z-score + binary split (into "above 50th percentile" and "below 50th percentile").
Ensure all dataframes have the same columns, so that they can be combined easily (this might have to happen on a case-by-case basis)
Actually run the analysis! This might look like: PCA, linear/logistic regression, random forest, and other models.

This sketch of the analysis is based on some very quick, hacky analysis I did while putting together the IC2S2 writeup. We should definitely try to formalize the analysis in some way!
Open Questions / Notes:

Should we create a new script in addition to featurize.py, or should it be part of featurize.py?
Should it be a python script of bash script? If we add a function such that featurize.py can be called with inline arguments, we could really just write a bash script (it would be two lines of code). I think this might be the preferable option.

Here is a .txt version of an R script I used to do some basic analysis (data viz, PCA, regression, random forest). Pardon the super messy code --- I was in a time crunch and just wanted to get some stuff out there!
quick_model_pipeline_explorations.Rmd.txt


Tagging Attribute Storage Policy properly

cleaning up storage policy code and fixing issue_1110 in the process https://github.com/project-chip/zap/issues/1110

Codecov Report

Merging #1137 (cb15c28) into master (7fbc396) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1137      +/-   ##
==========================================
- Coverage   65.21%   65.20%   -0.01%
==========================================
  Files         170      170
  Lines       18213    18213
  Branches     3922     3922
==========================================
- Hits        11877    11876       -1
- Misses       6336     6337       +1

Files Changed
Coverage Δ

src-electron/db/query-config.js
80.50% <ø> (ø)

src-electron/zcl/zcl-loader-silabs.js
94.43% <100.00%> (ø)

... and 1 file with indirect coverage changes

Should this optionality come from the xml for certain attributes?

Should this optionality come from the xml for certain attributes?

We have a list in zcl.json called  "attributeAccessInterfaceAttributes" which identifies cluster/attribute pairs which should be deemed "external" for storage policy.

@brdandu I have to fix the conditional so I have to make one more change


[stable/jenkins] Hide loadBalancerSourceRanges setting if ServiceType is not LoadBalancer

loadBalancerSourceRanges is an invalid setting for other service types.

Thanks for the submission! This was fixed in another PR.


openbsd: SIGSTKSZ has been reduced

On OpenBSD 6.3, SIGSTKSZ value has changed.
https://github.com/openbsd/src/commit/e211c58cc8e20862a4eaa1b91fd4bc4a2975dad3

@bors: r+

:pushpin: Commit 04aa1bb has been approved by alexcrichton

@bors: Retry
On Tue, Apr 10, 2018 at 10:00 AM, Rust highfive robot <
<EMAIL_ADDRESS>wrote:

r? @alexcrichton https://github.com/alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang/libc/pull/967#issuecomment-380133124, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAD95AzXpSGNcZ2iBZAHCSCeJvo4Gga2ks5tnMkegaJpZM4TOb6K
.

:hourglass: Testing commit 04aa1bb572fe6d5e8c02ca6f80edffed73921902 with merge 7eb60555400b270f0fb170ba29996a1e90662879...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 7eb60555400b270f0fb170ba29996a1e90662879 to master...


Sub Task 2: At a certain distance speak motivation to user

Linked to #185

Set a target distance, if current total distance > target distance, speak a motivational quote and update the target distance.


Updated pages site to 3.6.0

Re-generated pages site to use latest release of Capital Framework
Changes

Updated CF to 3.6.0 release

Testing

Run the site and check that it still works and that cf-grid documentation is up to date.

Review

@KimberlyMunoz
@Scotchester
@contolini

Screenshots
Old

New

Checklist

[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows the standards laid out in the front end playbook
[x] Passes all existing automated tests
[x] New functions include new tests
[x] New functions are documented (with a description, list of inputs, and expected output)
[x] Placeholder code is flagged
[x] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Do we need to update the changelog in the gh-pages branch? It hasn't been updated since v2.0.0

@jimmynotjim meh. I vote to delete it.

👍

cf-forms still has the ugly double heading but that doesn't concern this PR.

:+1:


required propety of schema ignored in models?

When I generate my orval from my open API spec, all the properties of the models are optional ?:. This happens even when I use an input transformer to add the required property to the values of the schemas.
Do I misunderstand this or is this a design decision? For me, the optional values are excessive.
What are the steps to reproduce this issue?

Use the spec linked above with a minimal orval config

What happens?
Check the models. E.g.
export interface DatasetDetail {
  dataset_id?: string;
  editors?: string[];
  file_name?: string;
  format_extra_variables?: string;
  message?: string;
  owner?: string;
  projects?: string[];
  published?: string;
  source_ref?: string;
  type?: string;
}

All models are like this.
What were you expecting to happen?
I'd prefer the types be required to avoid optional chaining where is isn't needed.
Any logs, error output, etc?
None
Any other comments?
This seems intentional so if I'm wanting something not advisable then why is that?
What versions are you using?
Operating System: Ubuntu 20.04
Package Version: Orval 5.4.4
Browser Version: Firefox 88

Hello @OliverDudgeon, you need to put your property to required if you don't want them optional. If you used a transformer to automatically add required can I have the code to see what is the problem? But normally, if you adding required like here should solve your problem.

Yeah I was transforming wrong. I was just setting required to true inside each property instead of an array of keys. The example helped a lot.
Cheers!


Connections are not being read from app.cfg

Why is it necessary to set:
AIRFLOW_CONN_INGEST_API_CONNECTION=http://hivevm191.psc.edu:7777/
AIRFLOW_CONN_UUID_API_CONNECTION=https://uuid-api.dev.hubmapconsortium.org/
on DEV (and Bill's working test environment) when there are perfectly good values in app.cfg?

I think I knew this already, but I keep forgetting.  I don't know why putting the connections in app.cfg doesn't seem to work.

There is some evidence it will work if I put it in [core], e.g. https://airflow.apache.org/docs/apache-airflow/1.10.14/howto/set-config.html


Cleaners ERT alternative

About the PR

The cleaners are flamethrower wielding nanotrasen affiliated ERT alternatives
TO DO
[ ] prefilled flamethrower
[ ] cleaner loadout
[ ] cleaner shuttle
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: JoeHammad

add: Centcom have hired 'The Cleaners', flamethrower wielding maniacs as a situational ERT alternatives

Cleaners? We already have those, they're called the ERT Janitors.
(I beg you do not give them biosuits they're so ugly please)

Im referencing the cleaners from the division

maybe I should make the suit more orange..

how does this look? I think it looks more fire-ey, which makes sense because their gimmick is flamethrowers

how does this look? I think it looks more fire-ey, which makes sense because their gimmick is flamethrowers

Looks good. In all honesty my main complaint with the biosuits is the hood, I think the current ones look dumb ~and I instantly think less of anyone who wears one~ but that's not really your problem. Does certainly feel more fire-ey anyways

how does this look? I think it looks more fire-ey, which makes sense because their gimmick is flamethrowers

Looks good. In all honesty my main complaint with the biosuits is the hood, I think the current ones look dumb ~and I instantly think less of anyone who wears one~ but that's not really your problem. Does certainly feel more fire-ey anyways

but the among us hood

alright, I forgot how to save maps, please remind me

nevermind

to be honest, I dont know how to actualy test what ive changed in game :trollface:

Is this still being worked on

kinda forgor and got a few things going on so i'd have to say no, this isnt being worked on

okey dokey

ill probably revisit it later, but this makes sense


2023-01-09

:loud_sound:Crisp Weekly 2023-01-09 is now in collecting.

/post

New in Go 1.20: wrapping multiple errors
https://lukas.zapletalovi.com/posts/2022/wrapping-multiple-errors/

/post

Scaling Mastodon in the Face of an Exodus
https://nora.codes/post/scaling-mastodon-in-the-face-of-an-exodus/
scaling mastodon by fixing sidekiq and DB

/post

Devpod: Improving Developer Productivity at Uber with Remote Development
https://www.uber.com/en-HK/blog/devpod-improving-developer-productivity-at-uber/

/post

The state of HTTP in 2022
https://blog.cloudflare.com/the-state-of-http-in-2022/

/post

Tips for analyzing logs
https://jvns.ca/blog/2022/12/07/tips-for-analyzing-logs/

/post

Welcome to Comprehensive Rust 🦀
https://google.github.io/comprehensive-rust/welcome.html

/post

Should Small Rust Structs be Passed by-copy or by-borrow?
https://www.forrestthewoods.com/blog/should-small-rust-structs-be-passed-by-copy-or-by-borrow/
The result is: passing small structs by-copy

/post

Setting up my new laptop: nix style
https://bmcgee.ie/posts/2022/12/setting-up-my-new-laptop-nix-style/

/post

React Native is not the future
https://blog.standardnotes.com/40921/react-native-is-not-the-future
React Native is not but using RN as the bridge to access native system functionality from your web app core is.

/post

A Visual Guide to useEffect
https://alexsidorenko.com/blog/useeffect/

/post

Index Merges vs Composite Indexes in Postgres and MySQL
https://sirupsen.com/index-merges
two individual indexes sounds better than composite indexes

/post

Flying away from AWS
https://terrateam.io/blog/flying-away-from-aws
Migrated from AWS to fly.io

/post

Devenv: Compose a Developer Environment easily for PHP with Nix
https://shyim.me/blog/devenv-compose-developer-environment-for-php-with-nix/

/post

Microfeatures I'd like to see in more languages
https://buttondown.email/hillelwayne/archive/microfeatures-id-like-to-see-in-more-languages/

/post

Get Started with Rust: Generics
https://serokell.io/blog/rust-generics

/post

I Migrated from a Postgres Cluster to Distributed SQLite with LiteFS
https://kentcdodds.com/blog/i-migrated-from-a-postgres-cluster-to-distributed-sqlite-with-litefs

/post

Is coding in Rust as bad as in C++?
https://quick-lint-js.com/blog/cpp-vs-rust-build-times/

/post

The i3-gaps project has been merged with i3
https://news.ycombinator.com/item?id=34293010
It's hard to believe that i3-gaps could exist

/post

Rust for professionals
https://overexact.com/rust-for-professionals/
yet another rust tutorial

/post

How setting the TZ environment variable avoids thousands of system calls
https://blog.packagecloud.io/set-environment-variable-save-thousands-of-system-calls/

/post

PHP in 2023
https://stitcher.io/blog/php-in-2023

/post

The Unreasonable Effectiveness of AWK
https://stephenramsay.net/posts/unreasonable-awk.html
you can hardly process faster than AWK

/post

The yaml document from hell
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell
hell because of its complicated and weird syntax in some case

/post

What happens when you open a terminal and enter ‘ls’
https://www.warp.dev/blog/what-happens-when-you-open-a-terminal-and-enter-ls

/post

The truth about CSS selector performance
https://blogs.windows.com/msedgedev/2023/01/17/the-truth-about-css-selector-performance/

/post

What if writing tests was a joyful experience?
https://blog.janestreet.com/the-joy-of-expect-tests/

/post

35% Faster Than The Filesystem
https://www.sqlite.org/fasterthanfs.html
Sqlite's blob is 35% faster than filesystem

/post

Git Commands You Probably Do Not Need
https://myme.no/posts/2023-01-22-git-commands-you-do-not-need.html

/post

Rust’s Ugly Syntax
https://matklad.github.io/2023/01/26/rusts-ugly-syntax.html


fix error running tests

Thank you for contributing to Swarms!
Replace this comment with:

Description: a description of the change,
Issue: the issue # it fixes (if applicable),
Dependencies: any dependencies required for this change,
Tag maintainer: for a quicker response, tag the relevant maintainer (see below),
Twitter handle: we announce bigger features on Twitter.

Please make sure your PR is passing linting and testing before submitting. Run make format, make lint and make test to check this locally.
See contribution guidelines for more information on how to write/run tests, lint, etc:
https://github.com/kyegomez/swarms/blob/master/CONTRIBUTING.md
If you're adding a new integration, please include:

a test for the integration, preferably unit tests that do not rely on network access,
an example notebook showing its use.

Maintainer responsibilities:

General / Misc / if you don't know who to tag<EMAIL_ADDRESS>DataLoaders / VectorStores / Retrievers<EMAIL_ADDRESS>swarms.models<EMAIL_ADDRESS>swarms.memory<EMAIL_ADDRESS>swarms.structures<EMAIL_ADDRESS>
If no one reviews your PR within a few days, feel free to email Kye at<EMAIL_ADDRESS>See contribution guidelines for more information on how to write/run tests, lint, etc: https://github.com/kyegomez/swarms

Bump python versions to minimum needed.

Fixed posthog test

This is ready to merge.

Added support for openai org id, and additional Organization header.

fixes for last pr.
Redoing the ad gen demo

more minor changes


Add JVM NamespaceScope option with defaulting

Should make java/kotlin a bit easier to interop

The fallback logic and handling is a proposal, happy to revert it. Would ideally want to have something in the annotations that indicates that it's inferred but not sure how to sanely do that on an optional AnnotationElement

JVM namespaces and fallbacks are fine; obviously not portable, but anyone who picks it will most likely be aware of the fact.
I suppose if we wanted to note that an annotation value has been inferred, we'd have to explicitly model an AnnotationValue type of thing.  Seems like a reasonable thing to do in principle, though I don't understand the use case here .  What use case is enabled by knowing that a value was inferred?


Pelle req bug

Describe the bug
Game crash after unlock pelle
To Reproduce
Steps to reproduce the behavior:

Buy all Reality and Imaginary upg
Go to Celestial tab, Pelle subtab

Expected behavior
Game will crash
Screenshots

Additional context
Bugged Component

@0i00000000a7 @aquamarine309 @HexaVault @loader3229 @seanxlx2011 @WYXkk
Please fix it as soon as possible.

fixed


linux AMD CPU install flashlight

When will it be compatible with AMD CPU backend？
Intel MKL is not very compatible with AMD cpu；how to solve this problem？

cc @jacobkahn @andresy

@wilambatch — there's an experimental OpenCL backend available now that you can try. We aren't supporting it and may remove it in a future release.


Reporter

Do you have any plans to migrate this over to Apples Reporter tool? As Apple will be deprecating Autoingestion in November.

This could be used as a starting point. https://github.com/fedoco/itc-reporter


feat: add avatar-size prop to contact info

PR Add avatar-size prop to DtRecipeContactInfo

:hammer_and_wrench: Type Of Change

[ ] Fix
[x] Feature
[ ] Refactoring
[ ] Documentation

:book: Description

:bulb: Context
As a requirement from this DP-66474, we need to update the size of avatar to size 'md'. The original callbar is using 'lg' as default, and the manage participants modal wants it to 'md', so the best solution is to make the avatar size passed from parent.
:pencil: Checklist

[x] I have reviewed my changes
[ ] I have added tests
[x] I have added all relevant documentation
[x] I have validated components with a screen reader
[x] I have validated components keyboard navigation
[x] I have considered the performance impact of my change
[x] I have checked that my change did not significantly increase bundle size
[ ] I am exporting any new components or constants in the index.js in the component directory
[ ] I am exporting any new components or constants in the index.js in the root

:crystal_ball: Next Steps
Make a new release for dialtone-vue
:camera: Screenshots / GIFs
Size LG:

Size MD:

:link: Sources
JIRA: https://dialpad.atlassian.net/browse/DP-66474
Vue3 PR: https://github.com/dialpad/dialtone-vue/pull/810

This should probably be updated to use the new avatar right? This is pretty outdated now

Hi @braddialpad , the user status is replaced by avatar's presence, please review again, thanks!


Regular expression inside the expressed route fix

QString::mid takes from-index and length(not to-index)
    now works with regexp in route.
Example: "/models/:name([A-Za-z]+)"
Note: Doesn't work with escaped symbols like \w, \d and others

Looks good to me!  I will follow up and add a unit test for this - what was the regular expression that you used?

The regexp was [A-Za-z]+, I wrote that in example above:  "/models/:name([A-Za-z]+)"


Remove adyen payment method

Fix #USF-892
remove adyen payment method
Test URLs

https://checkout-dropin--aem-boilerplate-commerce--hlxsites.hlx.live/checkout

re-created this PR in another branch (no fork) to be able to run the aem-psi-check

keoko:remove-adyen-payment-method


NG Aggregator

Grant Application Checklist

[ ] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[ ] A BTC address for the payment of the milestones is provided inside the application.
[ ] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[ ] The total funding amount of the project is below CHF 30k at the time of submission.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Nick Qi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Run pre and post commands

Command npm run <script> runs pre script, then script and then post script, but nrun don't.
Example
Scripts
{
  "pretest": "echo pretest",
  "test": "echo test",
  "posttest": "echo posttest"
}

nrun test will print only test
npm run test will print pretest, test, posttest

That's absolutely true.
I don't know what to say, except "pr's are welcome" =)

#5 merged, now it's supported


Inquiry: Advantage of macOS vs Linux runners?

Other than mentioning various features that the macOS and/or Linux runners do or do not support, the documentation doesn't mention any particular benefits of one over the other, or of xhyve vs qemu (which might inform a macOS vs Linux decision).
Assuming I have a fairly simple freebsd and netbsd matrix and I don't have any particular version or architecture requirements, is there a reason that I should choose macOS over Linux or Linux over macOS? Trying to figure out if I can expect better performance (faster builds) from a particular runner config.
Thanks in advance for bringing some clarity to my decision making.

One of the reasons I'm asking is that about half of my runs are failing with this:
  hdiutil: couldn't eject "disk2" - Resource busy

  /Users/runner/work/_actions/cross-platform-actions/action/v0.21.0/webpack:/cross-platform-action/node_modules/@actions/exec/lib/toolrunner.js:574

And I'm wondering if switching runners to Ubuntu would fix this (which I'm about to try), but there may be other reasons why macOS is generally better that would negate that decision.

macOS runners are preferred because they supported hardware accelerated nested virtualization. This was mentioned in the readme in the "Under the Hood" section. But I made it more clear and explicit now and added it to the "Runners" section: https://github.com/cross-platform-actions/action#runners.

That is kinda the conclusion that I came to, too. When I switched to Ubuntu as the runner, things really slowed down. However, when I switched to Ubuntu as the runner, things became much more reliable. I have a matrix of six builds using this action. When using Ubuntu as the runner, they never fail (unless I've broken my own code). When using macOS as the runner, at least one build (usually two) in the matrix always fails every single run, with the disk ejection problem mentioned in another issue. So I'll stick with Ubuntu for now due to the reliability.

with the disk ejection problem mentioned in another issue

I fixed that two days ago (hopefully) in https://github.com/cross-platform-actions/action/releases/tag/v0.21.1. You can also try using QEMU as the hypervisor on macOS for better stability.

That did, indeed, seem to fix the disk ejection issue on macOS runners. I'll also try QEMU on macOS to see if it works any better or faster for my specific use case.
Out of curiosity, why can xhyve be used only for OpenBSD and FreeBSD, but not NetBSD, on macOS?

Out of curiosity, why can xhyve be used only for OpenBSD and FreeBSD, but not NetBSD, on macOS?

OpenBSD and FreeBSD are the only operating systems I've managed to boot in xhyve.


Added check for HTTP_X_FORWARDED_PROTOCOL header in _isHttps

Fixes Jasig/phpCAS#219 in those rare cases where reverse proxies send non-RFC headers

Thanks for the patch


Initial application for validation of a neuron against a population

Based on morph_check I created a morph_validation to add further checks on the quality of a cell.

This implements #256. It is a very primitive state, but I think it will be useful for our validation task requirements.

There seems to be quite a bit of duplication with morph_check. Also, we need to move towards less untested code in apps and more tested code in modules. That is what I was hoping to do with morph_check whenever I get the time. Ideally, an app should only parse the commandline options, maybe open some configuration files, and delegate all the work to a function from a neurom module.

Quite a bit of duplication indeed! I agree with you, but since this moving around is not urgent and this validation app is needed by Monday I would suggest that we leave the moving around for a subsequent pull request.

I don't think that is a good idea. If it really is that urgent, it can be put elsewhere, outside of NeuroM. But the best approach is to do this properly.

I definitely agree that we should do this properly. However, I don't see the point of cleaning up this application, while the morph_check application is in a similar state without problems. What I could definitely do is move the check_feature function outside of the applications and add the corresponding tests.  But I think the logging features are not relevant for this specific request. Also, since I am not very familiar with logging this might take me too long to automate it properly. If you have some reasonable suggestions (concerning which functions can be moved in a different place without too many modifications) please let me know. But, I will need a more concrete suggestion than this needs to be cleaned up :P

Maybe I can re-work morph_check next week and you can use it as an example.

Current coverage is 100.00%

Merging #260 into master will not affect coverage as of fcbbf6d

@@            master    #260   diff @@
======================================
  Files           41      41
  Stmts         1637    1637
  Branches         0       0
  Methods
======================================
  Hit           1637    1637
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of fcbbf6d

Powered by Codecov. Updated on successful CI builds.

Is this going to be merged at some point? I would like to use it for Guy's synthesized glial cells.

No in its current form. I think this needs to go somewhere else.

Apps is not a good location for this? Or do you mean that it needs to be re-factored in a way to have minimal code in apps? If this is the case then I agree.

Neither apps not neurom. In its current form this is not general enough. Some code could be factored out into modules, and if light and more general application can be build using them, then fine. Otherwise this should go in a BBP morphology validation package.

So this comment:

juanchopanza commented 7 days ago
I don't think that is a good idea. If it really is that urgent, it can be put elsewhere, outside of NeuroM. But the best approach is to do this properly.

is outdated?

I think I cannot follow your reasoning. NeuroM extracts the distributions of the features and what the script is essentially doing is calculating a score between distributions that are extracted from NeuroM.
Do we really need a different package in order to have a function that loads from two different directories and one that applies a bunch of scipy tests on the distributions of NeuroM? I thought that was the point behind having apps, wasn't it?
I whole-heartedly agree with refactoring the code in order to have only trivial stuff in the apps, but I am not sure why is it is to have a function in stats that runs a test between two distributions.

So this comment:

juanchopanza commented 7 days ago
Maybe I can re-work morph_check next week and you can use it as an example.

is outdated?

I don't think that where the validation - comparison code will go should be a personal decision.
I understand your point about cleaning up the code and I'm strongly in favor of cleaner + tested code, before we add it to an app. I don't see how comparing A with B (as long as the same features can be extracted from A and B) is not a general enough use case. FYI I have a least 3 use cases that need to use this type of comparisons, which makes it general enough. On top of that 2 of them are outside BBP, which makes the BBP repository suggestion a very weak idea. I though the point of NeuroM was to provide tools for a larger audience and therefore it was OS. If someone needs special BBP access to run basic scripts that weakens the applicability of this system.

Maybe I can clarify the two of the main issues:

Not general: as far as I can see, this is a very specific test on two populations. it is not a universal validation (there is no such thing), it is just a set of statistical tests chosen for a specific purpose. This could be made more general for example by allowing the user to select what kind of test they want to perform.

Code quality. I think there is agreement on this.

If we can make an application after fixing 1. and 2. then neurom is the right place for it. Otherwise, it should go elsewhere. But I really can't see why this is a problem at this stage. If we need something for M30, then we put whatever we have an internal repository used for morphology validations. If somebody outside of BBP needs it, then we can thing of providing it as an example. Bear in mind that applications used in the task service are tied to the release cycle of NeuroM and we won't be making a release every time some script gets modified. So it is good to have M30 scripts de-coupled from the NeuroM release cycle anyway.


seeing crashes opening gopher pages in Lagrange on macos

MacOS 12.4
Lagrange 1.13.7
I'm a new user and the first 3 or 4 different gopher pages I tried crashed Lagrange.
I've tried opening from other apps and pasting the url into Lagrange, same result.
Ah ha!  If Lagrange is not running, then links open okay.  But if the app is already running whenI try to open a gopher page then it crashes

I haven't seen any Gopher-specific crashes myself. Do you have a URL that causes the crash every time for you?

For me, the following steps will cause a crash.
Start Lagrange
Close all windows, but leave the app running.
from the shell command line type:
% open gopher://gopher.quux.org/1/Software/Gopher/servers
If there are any windows open but iconified, then the address opens as expected.
So it's only triggered if there are no active windows.
If the app is not running, then it's started and open the page as expected.

Fixed for 1.13.8. The problem was that the event handler didn't realize that a new window needed opening if there wasn't one when the user was opening a URL via an external app.

Included in v1.13.8.