Typedoc not starting. Constant errors output with basePath and comments.

Terminal output:
> typedoc

><EMAIL_ADDRESS>doc /home/rko/Documents/project/js-webui
> typedoc

Error: Unknown option `basePath`.
Error: Unknown option `comments`.

npm ERR! Linux 4.8.0-040800-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "doc"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>doc: `typedoc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>doc script 'typedoc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the qad-js-webui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     typedoc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs qad-js-webui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls qad-js-webui
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/rko/Documents/project/js-webui/npm-debug.log

> grunt typedoc

><EMAIL_ADDRESS>doc /home/rko/Documents/project/js-webui
> grunt typedoc

Running "typedoc:build" (typedoc) task
Error: Unknown option `basePath`.
Error: Unknown option `comments`.
Warning: Task "typedoc:build" failed. Use --force to continue.

Aborted due to warnings.

npm ERR! Linux 4.8.0-040800-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "doc"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>doc: `grunt typedoc`
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>doc script 'grunt typedoc'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the qad-js-webui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     grunt typedoc
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs qad-js-webui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls qad-js-webui
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /home/rko/Documents/project/js-webui/npm-debug.log

$ typedoc --version
Error: Unknown option `basePath`.
Error: Unknown option `comments`.

:D

Hello @conmute. I believe this is a duplicate of #340 though I'm not sure what the comments option refers to.

@conmute Do you still have this issue with the latest version of TypeDoc? If so can you share your tsconfig.json setup?


Bring back option turning request batching off

I noticed previous versions had an option to batch requests, could you add that back to 1.0.0.

The batching option was removed in this commit, but it seems like a httpBatchLink was added here. So if you want to batch requests you should be able to do this:
await Promise.all([
  trpc.getGreeting.query({ name }),
  trpc.getFarewell.query({ name }),
])

Hopefully this helps.


reformat the order of imports

keep tidy

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

@2qif49lt What is this job for? I don't see it gets clearer.

@2qif49lt What is this job for? I don't see it gets clearer.

sort the import list


[view] Cannot visualize some hdf5

I am attaching below an example file that cannot be visualized by silx 0.7, while it works fine with HDFView 3.0.0. When you click on the ruptures dataset and expand the window there is an error
   no field of name serial   File "/home/michele/py36/lib/python3.6/site-packages/silx/gui/data/RecordTableView.py", line 209, in data
       return self.__formatter.toString(data, dtype=self.__data.dtype)
     File "/home/michele/py36/lib/python3.6/site-packages/silx/gui/data/TextFormatter.py", line 298, in toString
       text = [self.toString(data[f], dtype) for f in dtype.fields]
     File "/home/michele/py36/lib/python3.6/site-packages/silx/gui/data/TextFormatter.py", line 298, in <listcomp>
       text = [self.toString(data[f], dtype) for f in dtype.fields]

example.zip

You dataset is a compound data type. I can see the dataset at least as a table with silx 0.8

@vallsv @PiRK
However, I do have a different error that blocks the application if I horizontally scroll the table until the end of the table.

Hi. It is the exact same issue you had #1951. It is fixed on the 0.8, but will not be fixed on 0.7. Please try to upgrade your installation.

When scrolling the horizontal bar or switching to fullscreen:
ERROR:silx.gui.qt._qt:<type 'exceptions.IndexError'> invalid index (3)   File "/users/knobel/.local/lib/python2.7/site-packages/silx/gui/data/RecordTableView.py", line 209, in data
    return self.__formatter.toString(data, dtype=self.__data.dtype)
  File "/users/knobel/.local/lib/python2.7/site-packages/silx/gui/data/TextFormatter.py", line 306, in toString
    text.append(field[0] + ":" + self.toString(data[index], field[1][0]))

The second issue will be fixed soon on the master. Then if you don't use the master, you could try to use it instead of the release. Compound types are not a priority for us, i don't think we will create a minor release just it.

If you fix it on master it is fine for me, you can do 0.8, whenever you want.
BTW, I said something incorrect before, HDFView 3.0.0 is not able to visualize this, it was the old version of HDFView that worked.


Feature request: Offline/Online detection for mobile devices (Mobile Safari / Mobile Chrome)

Hi, is there a way to add a feature to detect user online presence and handle online of offline events of users?
Best regards

https://developer.mozilla.org/en-US/docs/Web/API/NavigatorOnLine/Online_and_offline_events

https://developer.mozilla.org/en-US/docs/Web/API/NavigatorOnLine/Online_and_offline_events

@inglesuniversal online/offline detection is out of scope for this library, since LocalForage is only focused on storing data locally.
Such network state detection is completely out of scope.
Using browser API's or periodically pinging a specific endpoint on a server that you can trust might be the best option for your use case.

@inglesuniversal online/offline detection is out of scope for this library, since LocalForage is only focused on storing data locally.
Such network state detection is completely out of scope.
Using browser API's or periodically pinging a specific endpoint on a server that you can trust might be the best option for your use case.


'None' for gradient Keras

The keras.preprocessing module has been splitted from the main Keras repository.
My Model:

Input X is : [700,100] and y is [700,1]
I am getting this error:

I imported 2 embedding matrix, one from glove and from my own dataset, and I am trying to train the model on X.
Can anyone help with the error above?

I didn't get this model at all, do you want to make an Embedding layer into the middle of the model???
Embedding layer can only be the first layer. No wonder this graph does not compile.
If you want to refine the word embeddings on your own dataset, use trainable=True . Convert first Embedding layer to:
Embedding(vocab_size, 300, input_length=...., weights=Constant(embedding_matrix),trainable=True)


Broaden scope of FrontierModel to include current search tree

Our current trait representing the frontier model is:
pub trait FrontierModel: Send + Sync {
    fn valid_frontier(
        &self,
        edge: &Edge,
        state: &[StateVar],
        previous_edge: Option<&Edge>,
    ) -> Result<bool, FrontierModelError>;
}

optionally providing the previous edge in this scope allows us to restrict access to the next edge in specific applications such as no left turn intersections, but, falls short of allowing us to restrict based on more complex maneuvers that extend beyond 2 edges.
in order to address this, we could replace the previous_edge with the tree:
pub trait FrontierModel: Send + Sync {
    fn valid_frontier(
        &self,
        edge: &Edge,
        state: &[StateVar],
        tree: &HashMap<VertexId, SearchTreeBranch>,
        direction: &Direction
    ) -> Result<bool, FrontierModelError>;
}

Some implications of this change:

the direction must also be provided, in the case that the tree is used by a reverse search in a bi-directional algorithm
the previous edge can be found by performing a single iteration of backtracking, an O(1) cost

While writing this issue, I had the thought that we could make this change everywhere that we are passing a previous edge. Maybe that would make everything a little more concise, and broaden the scope of access modeling too, in case that is helpful.

yeah that would make sense to me and doesn't come at any cost (I think) since we're just passing a reference around

@robfitzgerald I see the addition of _state_model: &StateModel to the signature in 244338d and am trying to understand it, are you able to clarify this for me?

sure thing. the state: &[StateVar] represents the state of a search, where, at each index, we store some value such as distance, time, energy, etc. RouteE Compass was designed so that future devs could develop their own TraversalModels, FrontierModels, and CostModels, which could interact with these vectors. but problems begin if one has a different idea of which index relates to which type of feature.
enter the StateModel. that is new as of last week. it is created when we instantiate a SearchInstance for an algorithm, and it provides an API for interacting with state vectors (&[StateVar]) by feature name, including any unit conversions and even custom unit types.
i think there aren't any FrontierModels that need to use the state model (in this repository, at least), so, you can likely just ignore it for the work you are doing. let me know if i'm wrong about that, glad to talk through the API + any changes you need to make.


ListBuckets() always sends a request with no region set

https://github.com/minio/minio-go/commit/8c34cc49a0b000ebe755577feab802ee721535ed changed the behaviour of newRequest() to only use data retrieved from the metadata object; in the case of ListBuckets() this object does not contain this data, so a request is sent with region == "".
The Minio server (at least the version we're using) returns 400 Bad Request in this case:
<Error>
    AuthorizationQueryParametersError
    <Message>Error parsing the X-Amz-Credential parameter; the region is wrong;</Message>
    [...]
</Error>

Prior to the above commit, newRequest() defaulted to us-east-1 or cn-north-1, overriding based on metadata rather than making metadata the only source - could this be restored? Perhaps something like:
	var location string
	// Gather location only if bucketName is present.
 	if metadata.bucketName != "" && metadata.bucketLocation == "" {
		location, err = c.getBucketLocation(metadata.bucketName)
		if err != nil {
			return nil, err
		}
	} else if metadata.bucketLocation != "" {
		location = metadata.bucketLocation
	} else if s3utils.IsAmazonChinaEndpoint(c.endpointURL) {
		location = "cn-north-1"
	} else {
		location = "us-east-1"
	}

AuthorizationQueryParametersError
Error parsing the X-Amz-Credential parameter; the region is wrong;
    [...]

Not sure why this would fail works fine with play.minio.io and s3.amazonaws.com @benpaxton-hf - will check again.

Looks like this may be due to us using an old version of the Minio server - the latest master seems OK. Will test more tomorrow.

Looks like this may be due to us using an old version of the Minio server - the latest master seems OK. Will test more tomorrow.

There is a bug with S3 fixing that now. Thanks for reporting @benpaxton-hf

#720 fixes this on my end.


Update tpl-format.exe

What issue(s) does this PR address? Describe and add issue numbers, if applicable.
Link issue(s) here:
What tests have been done? Upload any model input files created for testing in a zip file, if possible.
What tests/review still need to be done? Who can do it, and by when is it needed (ideally)?
Check which is true. This PR requires:

[ ] no further changes to r4ss
[ ] no further changes to the manual
[ ] no further changes to SSI (the SS3 GUI)
[ ] no further changes to the stock synthesis change log (new features, bug reports)

Describe any changes in r4ss/SS3 manual/SSI/change log that are needed (if not checked):
Additional information (optional):

This updates tpl_format.exe to ver 1.0.1, which keeps blank lines blank and, if a line consists of only spaces, tabs, etc., it returns a blank line.

Thanks @nschindler-noaa , this is great! I think this can be merged.
Note that @iantaylor-NOAA added a branch protection rule, hence the merge blocking.


feat(DatePickerE): Initial updates based on v3 design spec

Related issue
Resolves #2439
Overview
This makes various updates to the DatePickerE component based on the v3 design spec.
Link to preview

Storybook

Non-Storybook example
(base font size overridden to 100% due to #2761)

Reason
Incremental work towards the v3 release.
Work carried out

[x] Update the styling of the input control
[x] Update the styling of the day picker
[x] Update the styling and positioning of the floating box
[x] Remove isValid prop
[x] Append date format to label automatically
[x] Reuse partials from TextInputE
[x] Add hover shading for intermediate dates in range mode
[x] Update placeholder and automatic opening behaviour

Demo
Single date

Range

Developer notes
Does not include:

updated typing behaviour for single date mode
typing and input date highlighting for range date picker
time and period selection
clear button
month and year buttons
#2863
#2864

@k9dh3zij I've added the outer shadow to the calendar sheet. Please have a look if it's as intended, as how it looks will depend on the origin (in relation to the other borders and shadows).

Thanks @jpveooys loving this! Feedback:
Visual

The button looks slightly squashed - should be consistent with other components:

When filled, the input label should be 2px higher and  the user input should be 1px higher. Please note: I think this needs to change across all experimental inputs - not sure if I missed it in previous PRs or if something changed, sorry
Visual comparison with design:

As already discussed, missing drop shadow

Keyboard controls

When opening the Sheet, can we move focus to the currently selected date? (as in https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html)

When closing the Sheet, can we return focus to the button? (as in the W3 example)

Range date picker: when using the keyboard to select the end-date, the visual highlight between start date and currently focused end date doesn't work

Can we add Esc as a shortcut to close the Sheet please?

That's all for now, I think 😅  Thanks!

@k9dh3zij
I've made updates to address those except for the following two:

When opening the Sheet, can we move focus to the currently selected date? (as in https://www.w3.org/TR/wai-aria-practices/examples/dialog-modal/datepicker-dialog.html)

There was an issue already open in the underlying library we're using (react-day-picker) regarding this. I've created a separate issue #2871 at our end with more info and responded to the issue in the underlying library.

Can we make it so that the Sheet contains its own tab sequence. (Tab and Shift + Tab do not move focus outside the dialog)

I found a library that will add this behaviour (called a 'focus trap'). However, it has a bug where the tab key stops functioning when dates after the first of the month are focused, so I've left that change out and created a separate issue (#2870). I also need to report the bug upstream.
Regarding:

Range date picker: when using the keyboard to select the end-date, the visual highlight between start date and currently focused end date doesn't work

I've added this but note it's not possible at the moment to clear that highlight when tabbing away with react-day-picker v7 (it will be with v8 which is currently in beta). (Have created a separate issue for this as well: #2872.)
I also updated the border radius of the sheet and the hover/pressed/focus styles of the next and previous month buttons, as they seemed wrong before to me. Have another look at those if you can :slightly_smiling_face:

Are the disabled state styles correct (should the picker button be blue and clickable):

Are the disabled state styles correct (currently the picker button is blue and clickable):

Good spot! Have updated those.

Thanks for the updates @jpveooys looking great!
As discussed, something that we can look to improve when the react-day-picker library allows it, please:

Disabled dates shouldn't get focus. Therefore, the state shown here should not be possible:

Big 👍 from me on this! :)

Thanks @k9dh3zij !
It looks like that's covered by https://github.com/gpbl/react-day-picker/issues/1320 which was coincidentally opened 30 minutes ago :smile:


Using assets combiner broke url(...)

Winter CMS Build
dev-develop
PHP Version
8.1
Database engine
MySQL/MariaDB
Plugins installed
none
Issue description
When using assets combiner :
{{ [
    'assets/css/vendor.css',
    'assets/css/theme.css'
]|theme }}

If one of the assets contain a reference to a file with url(...) the reference get corrupted with backslash instead of slash.
This issue was detected on a Windows platform, which may be important given the difference in the use of slashes and backslashes.
Steps to replicate
In the demo theme, change :
<link href="{{ 'assets/css/vendor.css'|theme }}" rel="stylesheet">
<link href="{{ 'assets/css/theme.css'|theme }}" rel="stylesheet">

to :
<link href="{{ [
    'assets/css/vendor.css',
    'assets/css/theme.css'
]|theme }}" rel="stylesheet">

Reload site in FrontEnd, the Winter logo ha gone.
The reference to the link in the class definition is change
from : background-image: url('../images/winter.png');
to : background-image: url('../themes\demo\assets/images/winter.png');
What it is expected : background-image: url('../themes/demo/assets/images/winter.png');
Workaround
No response

@damsfx could you try https://github.com/wintercms/winter/pull/898 and see if that resolves the issue?

@damsfx thanks, just spent the last hour trying to get a windows VM set up to test on. I've pushed another commit that should fix the issue, but wont be able to test till this VM is set up

@jaxwilko The issue no longer exists.
Note I'm not testing it on child themes.
Thank's.
If there is a need to do other tests under Windows, do not hesitate, I always have a machine dedicated to this task with the latest dev-develop version installed.

@damsfx thank you very much for your efforts!


[Bug] Variables in calc() cannot be compiled

Steps To Reproduce

Use a variable inside a calc() function

The current behavior
A compile error Error: Expected "(" or ".". is thrown:

The expected behavior
No compile error.

I have created a minimal test repository with two calc cases:
git clone git@github.com:uncaught/styled-jsx-sass-var-in-calc-issue.git
cd styled-jsx-sass-var-in-calc-issue/
npm install
npm start

These usages of variables in calc() work with node-sass and styled-jsx-plugin-sass.

Did you find any solution/workaround for this?

No, unfortunately not. I had to downgrade back to node-sass and styled-jsx-plugin-sass.

You can use CSS variables to workaround this issue


Add ErrorsByField function

The ErrorsByField(errorsOfStructValidation error) function returns all errors as a map[string]string (key: field name, value: field error message).
Sadly, the only thing that's currently not possible (at least given this implementation) is the nested error hash someone asked for in asaskevich/govalidator#63. I'll try to take a crack at that in the next few days.

Thanks, ErrorsByField just a prototype of the function that can behave like current implementation. I think, it should return something like complex object (like json) that can be easily used :)

Awesome, thanks! Yeah, I will take a look at enhancing that to return a nested map instead and keep it backwards compatible (don't know if that's possible, though).


Design process for writing documentation

Github pages only supports hosting HTML.  If we want to use our Github Pages site to host docs for our whole project, we need a way to write the documentation in something like markdown, and then convert it to HTML.  Sphinx generates HTML from RST.  It can also be used to generate HTML from markdown.  This issue is to dicsuss what want to do here
Sphinx markdown:  https://github.com/ericholscher/sphinx-markdown-test
Docs for "requests" package, generated from RST using Sphinx:  http://docs.python-requests.org/en/master/
https://github.com/kennethreitz/requests/tree/master/docs
@gsfr

@ryansanford

@coltonlw The REST API is the only interface that is treated as public, which we are now working towards 100% coverage thanks to your efforts. We can close this issue.
Now that I'm thinking about it, I should have had you remove the sphinx related material rather than relocate it, as its presence may be implying more public interfaces than intended.

@ryansanford
This issue is about how to take custom documentation that we write, e.g. tutorials or descriptions, and turn it into HTML because github pages requires that.  Sphinx is not necessary for this (see mkdocs link) and the documentation doesn't and usually won't relate to module interfaces.  @gsfr has said he wants to use github pages for our docs, and unless we want to write them in HTML we need a tool.

I appreciate the thinking ahead. Let's wait until we have an actionable content addition to https://scitran.github.io/core/ before we design a content management process. We'll be able to make better choices at that time.

Besides the RAML, I think we also wanted to do Sphinx-based code documentation. Is that correct?
Beyond that, I'm not aware of any other needs for the moment.


when using custom pca model, raise error

libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: The model file you are trying to load is in an old format. Please download the most recent model files.
I trained new custom pca model!(different vertices) but it didn't work on eos-model viewer...
When loading model in python, successful. I don't know why it does..

Hi,
You need to use the same eos version to create the model and when using the model viewer. I suspect in your case the version difference is too large. A few months ago I updated the eos version of the model viewer in this branch: https://github.com/patrikhuber/eos-model-viewer/tree/update-eos-and-igl
If you have any further issues pertaining the model viewer please open an issue in the respective repository. As mentioned in the model-viewer readme, the model-viewer is quite experimental, not very polished code, and "you're on your own" using it. (It works just fine for us overall though, with the occasional hiccup.)


Recommended port forward command label does not match label on LakeFS pod

This is the command I was given when I ran the helm chart:
export POD_NAME=$(kubectl get pods --namespace default -l "app=my-lakefs" -o jsonpath="{.items[0].meta.name}")
That returned this error:
error: error executing jsonpath "{.items[1].metadata.name}": Error executing template: array index out of bounds: index 1, length 0

Which is because the label set on the pod is just lakefs
Name:           my-lakefs-78766c7c99-288t2
Namespace:      default
Priority:       0
Node:           minikube/<IP_ADDRESS>
Start Time:     Wed, 13 Jan 2021 17:55:30 -0800
Labels:         app=lakefs
                app.kubernetes.io/instance=my-lakefs
                app.kubernetes.io/name=lakefs
                pod-template-hash=78766c7c99

I suspect that lakefs.fullname is not being set correctly here: https://github.com/treeverse/charts/blob/master/charts/lakefs/templates/_helpers.tpl
Not a huge deal, just a heads up!

@avaidyanatha thanks for opening this issue!

@avaidyanatha thanks for opening this issue!

Not sure why automatic closing of this issue didn't happen with #47


feat(test): test fault-recovery on madsim

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
This PR adds fault-recovery to the deterministic e2e test.
When running ./risedev sslt with --kill-node, the test runner will randomly kill a compute node between queries.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)
#2646, #4527

TPCH Q19 failed: https://buildkite.com/singularity-data/pull-request/builds/6736#0182cf11-3740-4cc4-b3a1-bb69a186aa9b/216-489
Is it an uncommon bug?
@mergifyio requeue

@mergifyio requeue

@mergifyio requeue

Failed to build executor: internal error: unsupported aggregator: type=SingleValue input=Timestamp output=Timestamp distinct=false

Looks like the fuzzing tests are using an unsupported aggregator. Is this expected? cc @kwannoel

Failed to build executor: internal error: unsupported aggregator: type=SingleValue input=Timestamp output=Timestamp distinct=false

Looks like the fuzzing tests are using an unsupported aggregator. Is this expected? cc @kwannoel

If it's unsupported it should be disabled, will take a look later. Thanks for catching this.


Plofgren graph library

@ashishgpersonal
This separates our graph code from Cassovary, and removes Node objects.

Most of it is just refactored and slightly improved from what you reviewed before.  The DirectedGraph trait is the main new class.
One small change I'd like you to double-check is commit
https://github.com/plofgren/bidirectional-random-walk/commit/9e2e3b99c1bf5af12498cc7daebaa0cbeb0ae812
where I slightly simplify ConcurrentIntArray, and I'm wondering if you agree the change preserves thread-safe-ness.

The graph library has been moved to Tempest, so I'm closing this.


'disabled' drives have wrong cursor

Etcher version: 1.0.0-beta16
Operating system and architecture: Linux x64

When a drive in the select-a-drive list is 'disabled' (whether because the drive is read-only, too small for the selected image, etc.) like shown in https://github.com/resin-io/etcher/issues/830#issuecomment-259515129 , it still displays a hand-cursor when you mouse-hover over it, implying that it's clickable when it isn't.

Tweaking cursor should do it.


Transaction date is not retrieved correctly

Hello everybody!
My code so far:
<?php

require 'vendor/autoload.php';

use Fhp\FinTs;
use Fhp\Model\StatementOfAccount\Statement;
use Fhp\Model\StatementOfAccount\Transaction;

$fints = new FinTs(
    URL,
	PORT,
	CODE,
	USERNAME,
	PIN
);

$accounts = $fints->getSEPAAccounts();

$oneAccount = $accounts[0];

$from = new \DateTime('2016-01-01');
$to   = new \DateTime();

$soa = $fints->getStatementOfAccount($oneAccount, $from, $to);

foreach ($soa->getStatements() as $statement) {
    echo $statement->getDate()->format('Y-m-d') . ': Start Saldo: ' . ($statement->getCreditDebit() == Statement::CD_DEBIT ? '-' : '') . $statement->getStartBalance() . PHP_EOL;
    echo 'Transactions:' . PHP_EOL;
    echo '=======================================' . PHP_EOL;
    foreach ($statement->getTransactions() as $transaction) {
		echo 'Date        : ' . $transaction->getDate()->format('Y-m-d') . PHP_EOL;
        echo 'Amount      : ' . ($transaction->getCreditDebit() == Statement::CD_DEBIT ? '-' : '') . $transaction->getAmount() . PHP_EOL;
        echo 'Booking text: ' . $transaction->getBookingText() . PHP_EOL;
        echo 'Name        : ' . $transaction->getName() . PHP_EOL;
        echo 'Description : ' . $transaction->getDescription1() . PHP_EOL;
        echo '=======================================' . PHP_EOL . PHP_EOL;
    }
}
echo "Found " . count($soa->getStatements()) . ' statements.' . PHP_EOL;

Output:
2016-01-01: Start Saldo: 0
Transactions:
=======================================
Date        : 2016-01-01
Amount      : 43.56
Booking text: Gutschrift
Name        : Name
Description : Description
=======================================

Date        : 2016-01-01
Amount      : -43.56
Booking text: Überweisung
Name        : Name
Description : Description
=======================================

Date        : 2016-01-01
Amount      : 150
Booking text: Gutschrift
Name        : Name
Description : Description
=======================================

Found 1 statements.

The problem:
The date value of the transaction always equals the supplied $from date.
I'm not sure if this is a problem with my code or the library. I tried it with the german bank ING-Diba.
How can I get the "real" transaction date?
Thank you for reading this far!

Hi @MrCrankHank
Thanks for reporting!
And sorry for the late response.
At the moment the transaction date is always the booking date of the transaction and not the valuta date.
This means that the transaction date is always the date of the statement of account.
2016-01-01: Start Saldo: 0
Date        : 2016-01-01
Did you expect something else?
Then let me know. Maybe we can improve here something :)
Best,
Markus

H markus!
No worries :)
Actually i expected it would output the valuta date of the specific transaction.
Is there a way to get it?
In my application the user imports the data from the bank and is then able to map it to invoices. The first import is usually over a long range (like from 2016-01-01 to today). It's difficult to find the right transaction for the right invoice, if the date isn't specific.
Appreciate your help!
Thanks.
Alex

This is the data i would expect (according to the web interface of the ING-Diba)
Output:
2016-01-01: Start Saldo: 0
Transactions:
=======================================
Date        : 2016-02-25
Amount      : 43.56
Booking text: Gutschrift
Name        : Name
Description : Description
=======================================

Date        : 2016-02-26
Amount      : -43.56
Booking text: Überweisung
Name        : Name
Description : Description
=======================================

Date        : 2016-07-21
Amount      : 150
Booking text: Gutschrift
Name        : Name
Description : Description
=======================================

Found 1 statements.

It just testet it with my other account (Deutsche Kredit Bank, DKB). The dates are closer to the data in the webinterface, but for some odd reason not identical. I can provide further information in a few hours, when I get home.

I think this should solve it:
https://github.com/mschindler83/fints-hbci-php/pull/5


Crash in mrb_str_format

When MRuby is built with MRB_INT64, the following input causes a crash:
sprintf "%*f",2147483648,Float::NAN

ASAN report:
==91193==ERROR: AddressSanitizer: negative-size-param: (size=-2147483648)
    #0 0x1058aa5e3 in __asan_memset (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x4d5e3)
    #1 0x105648bd6 in mrb_str_format sprintf.c:1037
    #2 0x10563a9c1 in mrb_f_sprintf sprintf.c:516
    #3 0x105611393 in mrb_vm_exec vm.c:1314
    #4 0x10560659f in mrb_vm_run vm.c:860
    #5 0x105638a29 in mrb_top_run vm.c:2731
    #6 0x105707fb5 in mrb_load_exec parse.y:5780
    #7 0x1057088c5 in mrb_load_file_cxt parse.y:5789
    #8 0x1054abb07 in main mruby.c:227
    #9 0x7fff8c15e234 in start (libdyld.dylib:x86_64+0x5234)

0x60c000013300 is located 0 bytes inside of 121-byte region [0x60c000013300,0x60c000013379)
allocated by thread T0 here:
    #0 0x1058b3520 in wrap_realloc (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x56520)
    #1 0x10559c015 in mrb_default_allocf state.c:60
    #2 0x10551e5c8 in mrb_realloc_simple gc.c:203
    #3 0x10551ed1e in mrb_realloc gc.c:217
    #4 0x1055a2af8 in resize_capa string.c:140
    #5 0x1055a22e5 in mrb_str_resize string.c:738
    #6 0x10563bf7f in mrb_str_format sprintf.c:570
    #7 0x10563a9c1 in mrb_f_sprintf sprintf.c:516
    #8 0x105611393 in mrb_vm_exec vm.c:1314
    #9 0x10560659f in mrb_vm_run vm.c:860
    #10 0x105638a29 in mrb_top_run vm.c:2731
    #11 0x105707fb5 in mrb_load_exec parse.y:5780
    #12 0x1057088c5 in mrb_load_file_cxt parse.y:5789
    #13 0x1054abb07 in main mruby.c:227
    #14 0x7fff8c15e234 in start (libdyld.dylib:x86_64+0x5234)

SUMMARY: AddressSanitizer: negative-size-param (libclang_rt.asan_osx_dynamic.dylib:x86_64h+0x4d5e3) in __asan_memset
==91193==ABORTING
Abort trap: 6

This bug was reported by https://hackerone.com/shikchen, who offered the following explanation:

The bug is here: https://github.com/mruby/mruby/blob/9644ad51b4a63d8db46d7918ec5e89a547236c56/mrbgems/mruby-sprintf/src/sprintf.c#L1034-L1035
if ((flags & FWIDTH) && need < width)
  need = width;

The type of variable need is int, but the type of width is mrb_int, which is int64_t when compiling with MRB_INT64. During the comparison, need is promoted to int64_t. But it will overflow when begin assigned from width, and the following memset/memcpy will cause heap overflow.

Initially I wrote that this only affected mirb. That turned out to be incorrect; my mruby build was broken. After rebuilding it now crashes in both mruby and mirb.


Document title in the menu does not match the page and content provided

Docs    / CSP offers / Upgrade or transfer offers to newer versions/Upgrade Dynamics AX subscriptions to Dynamics 365  directory refers to Dynamics AX subscriptions migration to Dynamics 365 but the actual page and content refers to "Migrate Dynamics 365 and Customer Engagement Plan from Basic (qualified offers) to newer versions ". It is a totally different product discussed in this page.
To Reproduce
Steps to reproduce the behavior:

Go to https://docs.microsoft.com/en-us/partner-center/manual-subscription-migration
Title of page refers to migrating Dynamics 365 to newer versions of CE and not AX which is an ERP product.

Expected behavior
https://docs.microsoft.com/en-us/partner-center/manual-subscription-migration shows content exclusively related to AX on-premises migration to Dynamics 365 cloud offerings

@brserbus @LauraBrenner please take a look at this customer feedback for our docs. Thanks, Jason

#assign:brentserbus


proselint: 0.9.0 -> 0.10.0

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

My editors and tooling are suffering a bit from trying to move to these fancy "sessions" things :P.
Anyway sorry, will submit properly shortly.

Oh nevermind it just had the wrong title :).

@GrahamcOfBorg  eval

Success on aarch64-linux (full log)
Attempted: proselint
Partial log (click to expand)
Successfully installed proselint-0.10.0
/build/proselint-0.10.0
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0/lib  /nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0/bin
patching script interpreter paths in /nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0
checking for references to /build in /nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0...
wrapping `/nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0/bin/proselint'...
/nix/store/cp0wx10zd4m7j236vahchy6d206zzd34-proselint-0.10.0

Success on x86_64-linux (full log)
Attempted: proselint
Partial log (click to expand)
  Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
Successfully installed proselint-0.10.0
/build/proselint-0.10.0
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v37f8xpzwn9gacdpmcdkcmyci3cshcsh-proselint-0.10.0
strip is /nix/store/1hi76hr87bd1y1q1qjk0lv8nmcjip1c8-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v37f8xpzwn9gacdpmcdkcmyci3cshcsh-proselint-0.10.0/lib  /nix/store/v37f8xpzwn9gacdpmcdkcmyci3cshcsh-proselint-0.10.0/bin
patching script interpreter paths in /nix/store/v37f8xpzwn9gacdpmcdkcmyci3cshcsh-proselint-0.10.0
checking for references to /build in /nix/store/v37f8xpzwn9gacdpmcdkcmyci3cshcsh-proselint-0.10.0...
wrapping `/nix/store/v37f8xpzwn9gacdpmcdkcmyci3cshcsh-proselint-0.10.0/bin/proselint'...


【字节跳动】招聘意向沟通

你好，
我是字节跳动Data&AI-lab&搜索的HR，负责大数据方向的岗位招聘。目前我们正在招募组建Flink/Presto/Spark/Hudi/Iceberg等这几个方向的大数据引擎团队，负责人和工程师的需求都有，北/上/杭base地点灵活。请问您有兴趣聊聊吗？
期待回复，谢谢！
联系人：陈凌薇 +86-15268606705
 Hello, my name is Lisa Chen. I am the HR of ByteDance Data&AI-lab&Search, responsible for job recruitment in the direction of big data.

At present, we are recruiting and forming big data engine teams in Flink/Presto/Spark/Hudi/Iceberg, etc. The positions required are: team leader and engineer，also the base is flexible（Beijing /Hangzhou/Shanghai）Are you interested in chatting?
Looking forward to reply, thank you!

Will close this issue.
Please don't create recruitment advertisement issue.


Added errno generation in VMCI failures where errno was not set

We have some cases when protocol failed (e.g. EOF from client, or whatever).
This is indicated to with 0 length returned by recv(), but errno was nor\t set because  EOF is considered a success.
This makes it inconsistent with CGO (and maybe others) who rely on errno to form "err" part of the return value, so this PR forces non-zero errno on all errors in protocol.
test: visual review and CI only

In all the cases where CHECK_ERRNO is invoked CONN_FAILURE (-1) is returned and errno is set. esx_vmdkcmd.go:Run()  has code to handle when errno is not set and log an internal error. That should be removed as that condition can't happen any more.

That's what internal error is - something that should never happen :-)


import mpl_toolkits.basemap as basemap fails on matplotlib

Issue: ImportError cannot import name 'is_scalar'
conda packages used
    basemap:              1.1.0-py35h50ae964_6                 conda-forge
    matplotlib:           3.0.0-py35h0b34cb6_1                 conda-forge

On Circle CI https://circleci.com/gh/conda-forge/mss-feedstock/178?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
+ mss -h
Traceback (most recent call last):
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/bin/mss", line 7, in <module>
    from mslib.msui.mss_pyui import main
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/site-packages/mslib/msui/mss_pyui.py", line 49, in <module>
    from mslib.msui.mss_qt import ui_mainwindow as ui
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/site-packages/mslib/msui/mss_qt.py", line 157, in <module>
    globals()[mod] = importlib.import_module("mslib.msui.qt5." + mod)
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/site-packages/mslib/msui/qt5/ui_sideview_window.py", line 64, in <module>
    from mslib.msui.mpl_qtwidget import MplSideViewWidget
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/site-packages/mslib/msui/mpl_qtwidget.py", line 54, in <module>
    from mslib.msui import mpl_map
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/site-packages/mslib/msui/mpl_map.py", line 48, in <module>
    import mpl_toolkits.basemap as basemap
  File "/home/conda/feedstock_root/build_artifacts/mss_1537858909004/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.5/site-packages/mpl_toolkits/basemap/__init__.py", line 17, in <module>
    from matplotlib.cbook import is_scalar, dedent
ImportError: cannot import name 'is_scalar'
Tests failed for mss-1.7.3-py35_2.tar.bz2 - moving package to /home/conda/feedstock_root/build_artifacts/broken
WARNING:conda_build.build:Tests failed for mss-1.7.3-py35_2.tar.bz2 - moving package to /home/conda/feedstock_root/build_artifacts/broken
TESTS FAILED: mss-1.7.3-py35_2.tar.bz2
Exited with code 1

see also https://github.com/matplotlib/basemap/issues/424

this was fixed, we need a new build
https://github.com/matplotlib/basemap/pull/398

@ocefpaf can you please rebuild this with the fix in place, Thx

Related? After a seemingly-successful conda install basemap:
Python 3.6.1 |Anaconda 4.4.0 (x86_64)| (default, May 11 2017, 13:04:09)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.57)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import mpl_toolkits.basemap as basemap
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'mpl_toolkits.basemap'

i get this Error when i try importing Basemap(how may i correct the installation?)---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
 in ()
----> 1 from mpl_toolkits.basemap import Basemap
~\Anaconda3\lib\site-packages\mpl_toolkits\basemap_init_.py in ()
153
154 # create dictionary that maps epsg codes to Basemap kwargs.
--> 155 pyproj_datadir = os.environ['PROJ_LIB']
156 epsgf = open(os.path.join(pyproj_datadir,'epsg'))
157 epsg_dict={}
~\Anaconda3\lib\os.py in getitem(self, key)
676         except KeyError:
677             # raise KeyError with the original key value
--> 678             raise KeyError(key) from None
679         return self.decodevalue(value)
680
KeyError: 'PROJ_LIB'

@fongangbatuo please open a new issue with the information requested from the "new issue template." It is virtually impossible to help you debug this based on an old discussion that is already solved.


ServiceInstance failing after migration from 3.9 to 3.11

I recently migrated a number of projects from an origin 3.9 to 3.11 cluster.
Everything seemed to have gone well but I now notice that any projects created from the service catalog on the 3.9 cluster are raising events because the 3.11 cluster is presumably now  trying to provison something that already exists
Error provisioning ServiceInstance of ClusterServiceClass (K8S: "3414d2af-5c74-11ea-9acb-566fb25c0057" ExternalName: "postgresql-persistent") at ClusterServiceBroker "template-service-broker": Status: 409; ErrorMessage: <nil>; Description: <nil>; ResponseError: <nil>
Is this a known issue, can anyone suggest a workaround?

Hey @thurcombe, thanks for the issue report.
According to the info you've provided, it seems that there are some problems with moving ServiceInstances around with Velero.
My initial suspicion is that the template service broker is keeping track of whether a ServiceInstance has been reconciled in the status, which is lost during migration.
The first cut I'd take at fixing this would be to skip restoring TSB ServiceInstances. We would still migrate the on-cluster resources deployed as a result of the ServiceInstance provision.

@djwhatle is this something we can do via config? I didn't see any method for excluding ServiceInstance objects.

@thurcombe currently, we don't expose the ability to manually configure exclusion of a particular GVK (e.g. ServiceInstance), but please see info below on "pre/post hooks" for a solution to this problem in a coming release.
In a recent discussion, the team weighed the consequences of stripping ServiceInstances from the restored resources list.
Our concerns with adding a restore exclusion for ServiceInstances are:

Loss of coordinates and management interface to externally provisioned services
Loss of service binding management capability
Loss of service deprovision capability

I don't think we can make the decision for folks to destroy this information.

All of this said, we are currently implementing a "pre/post hooks" feature currently which could be useful for cleaning up leftover ServiceInstances on your clusters if you deem that an acceptable path and are OK with losing the capabilities listed above on your provisioned services. The pre/post hook feature allows for running of custom ansible logic to manipulate cluster resources at various points in the restore.
It also strikes me that TSB may be flawed if a fully provisioned ServiceInstance can't be moved around without triggering a reprovision. This could be something to bring up on that project.


Does global_train_batch_size support gradient accumulation?

❓ The question
Hello authors, thank you very much for your inspiring work. I now have 8 A100s. If I want to pretrain the model at a certain checkpoint, can I set global_train_batch_size to the original 2048 and then set device_train_microbatch_size to 2? Is this equivalent to using more GPUs?

@jinzhuoran Yes, this should be possible. Have you faced an issue when trying this?


Added belarusian language support

Hey! Thank you for this library.
Cause I need Belarus Locale,
I Added Belarus locale feature.

Thank you!


Revive invoice settled state

In https://github.com/bottlepay/lnmux/pull/29, we remove the invoice settled state because it is fake and not actually backed by any check on lnd.
A reliable implementation of the settled state can only be realized after https://github.com/lightningnetwork/lnd/pull/6517 is done. This is scheduled for lnd 0.16, so will take another 3-6 months.
An intermediary solution could be to define the settled state as follows:
"For every htlc of the set, a settle htlc interceptor action has been sent to the corresponding lnd instance and an OK result was returned".
This makes lnmux safer than it currently is, because a connecting application will at least wait for the settle messages to be delivered. There is still an uptime requirement for lnmux though, because lnd isn't persisting the settle message.

One complication here is that if a settle message is delivered to lnd, and we crash right after, we haven't updated the lnmux invoice state to settled in the db yet. Lnd has processed the settle message though, and we won't ever hear back from it. So from lnmux's perspective, the invoice remains not settled.

Maybe the best we can do is mark an htlc as settled right before we send the settle message to lnd.


Upgraded to babel 7

What kind of change does this PR introduce? (check at least one)

[x] Feature
[x] Build-related changes

Does this PR introduce a breaking change? (check one)

[x] No

The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup

Other information:

Upgrades all babel dependencies to work with babel v7. babel-preset-flow-vue is not compatible, so I've recreated it in the .babelrc.js directly.

Also changed the jasmine.json files to jasmine.js so that require.resolve can be used instead of assuming where node_modules are. With things like plug'n'play coming to yarn, this is a necessary change.

Vue 3 will use TypeScript.

@Shyam-Chen I'm confused about what updating some devDependencies has to do with Typescript?

Thanks!


Persistent error syncing drafts

I haven't seen this in the stock Node.js app, so assume it must be something in the filesystem permissions or so. I regularly get these warnings popping up over my wiki:
syncer-server - 16:48:20 10 3 2015
Sync error while processing 'Draft of 'MyTiddler: Error: ENOENT, unlink '/var/lib/tiddlywiki/mywiki/tiddlers/Draft of 'MyTiddler'.tid'

There has been a partial patch to address this issue, but @Jermolene is asking for help diagnosing the root cause. It is affecting other Node.js installations so is not specific to this Docker image.

Thanks, I am having the same problem from time to time, when connection is lost. I suppose there will soon be a release containing at least this partial fix, so I'd like to stay on released versions for now.

Has this been fixed?

The Docker image hasn't been built for about a year. I just triggered a new build so the new image should contain the latest Tiddlywiki version. I am not sure if they finally fixed the error correctly upstream?

I rebuilt it for my fork, and it works still, so no fear about that! Are you still using TW?

@0atman Yes, just didn't update it for a long time. Am quite happy with it. Best app for taking personal notes. Although I am quite curious what has changed since back then!

(I hope you don't mind conversing off-topic)
I am totally new to TW, hence wanting to set up a server for myself. I've spotted the codepen plugin, which is great so far!


'EntryPoint' object has no attribute 'resolve'

I run 'python letsencrypt-aws.py register<EMAIL_ADDRESS>and get he error saying AttributeError: 'EntryPoint' object has no attribute 'resolve'

Upgrade the version of setuptools you are using.


Add ability to use object-by-address for method arguments with type id

Currently, if argument type is id, there's no way to pass anything that can't be parsed from JSON.
This change adds the ability to select the type of argument to pass:

Value - works the same as before, JSON from input string is parsed to NSDictionary/NSArray/NSString/etc.
Address - uses object at the specified address, so you can call any method with object you previously created and populated to your preference

Here's a simple demonstration of how it works:
https://streamable.com/hcwo6

You should be able to pass strings, arrays, dictionaries, or NSNumber to id currently:
"Strings must be in quotes"
["array", 1, 2, 3]
13457

As for addresses, I've wanted that myself but I can never remember why it's useful. Do you have a use case?

Hm, I never considered that NSJSONSerialization is set up the way that it can parse fragmented JSON. Shouldn't have glossed over NSJSONReadingAllowFragments options. I will rework the input according to this new knowledge :)
Regarding addresses - sure, there is a whole lot of use cases. One such case may be, for example, UI tuning on-the-go - maybe the title doesn't look just right, so we want to pass new color and font to NSAttributedString. To do that, we should call addAttribute:value:range:, where value can be any object, basically. That's where ability to pass object by address comes in - we can alloc UIColor/UIFont/whatever we want, and pass it by address.
Other than that, where FLEX shines is in debugging weird bugs that are hard to reproduce - so if you caught something, and you don't have the ability to attach debugger to your device, you can use FLEX to inspect and play with bugged application state. By adding ability to pass any object to any method requiring id argument, we add another helpful tool to combat such bugs.

I don't believe we use NSJSONSerialization for plain strings or numbers but I could be wrong. I think we just check for quotes or something haha

we can alloc UIColor/UIFont/whatever we want, and pass it by address

I see! Yeah, I've run into situations like that myself. Anyway, if you allocate something, copy it's address, then "go back" to use it somewhere, the object will have been deallocated 🙁 Maybe we need to give objects a "retain" button and add a "retained objects" section to the main menu? That way you can choose to manually keep it alive
Another alternative is if we had support for tabs we could just create an object and open a new tab without it deallocating. I'm down for either approach. Would you like to help with either?

I'd be happy to help! This project is really interesting for me, and I'd be glad to contribute to it.

I don't believe we use NSJSONSerialization for plain strings or numbers but I could be wrong. I think we just check for quotes or something haha
I just checked, and it's actually NSJSONSerialization that does all the heavy lifting with Strings and Numbers! You can see it in FLEXRuntimeUtility.m, in objectValueFromEditableJSONString: method - it's NSJSONReadingAllowFragments that makes the magic happen.

But regarding this:

Anyway, if you allocate something, copy it's address, then "go back" to use it somewhere, the object will have been deallocated 🙁
I also thought that's what happens, but this actually doesn't happen! You can reproduce it with current build with Address Inspector (see my other pull request) - try alloc/init-ing new object, or creating one with new, and copy it's address - you will see it's still alive. In Xcode this object is marked as "leaked", so it may be a bug, or it may be by design. So currently, passing address is be a cheap solution for "calling the method with any object" problem.

Another alternative is if we had support for tabs we could just create an object and open a new tab without it deallocating.
However, this approach is a much cleaner alternative, and, if I understand correctly, it will allow allocating/setting up new instance of the object right where we call the method. Maybe we can add new tab for that, or button to allocate new object and paste address into input field.

I found what causes the objects to live even after we leave the result screen of [[ClassName alloc] init]:
__unsafe_unretained id objectReturnedFromMethod = nil;
[invocation getReturnValue:&objectReturnedFromMethod];
returnObject = objectReturnedFromMethod;

If we remove __unsafe_unretained, then object is deallocated, but all kinds of weird crashes start happening.

That is interesting... you've uncovered a bug!
Can you do me a favor? 1) hold onto a crash log if you can't replicate the crash with the code the following code, 2) see if you can replicate the crash with this code:
void *objectReturnedFromMethod = nil;
[invocation getReturnValue:&objectReturnedFromMethod];
returnObject = (__bridge_transfer id)objectReturnedFromMethod;

Sure, I'll check it out!
If we'll go with fixing the leak bug, then "Retain" button + list of retained object looks better, but tabs also look interesting. Maybe you can scribble a little sketch of how the tabs should look like, since we may be thinking of two different things.

Ok, with the code you provided the crash can be replicated in sample application by:

Just selecting AAPLAppDelegate from FLEX menu
Opening Buttons from sample app menu, selecting Button text via FLEX menu, selecting View Controller For Ancestor, and then selecting view property.

In the first case, the crash occurs because we send -[CFRunLoopTimer release] to deallocated instance.
In the second case, the crash occurs because we send -[UIButton respondsToSelector:] to deallocated instance.
These crashes are reproduced 100% of the time.

Ok, the reason for the crash is that NSTimer from AAPLAppDelegate gets deallocated, my guess is due to __bridge_transfer - it takes on the object as it's own, then releases it, and when we actually try to access the object, it crashes.
Simple __bridge does not have the same effect, but it also doesn't deallocate something we allocate manually.

My take on this is that there's no easy fix (and maybe there's no fix at all, as in this is by design) - if we're taking retain/release onto ourselves by using __bridge_transfer - we mess up retain/release by ARC for the properties of the objects we inspect. If we use __bridge or if we use __unsafe_unretained - then we don't mess up ARC retain/release cycle for properties of inspected objects, but we don't have the ability to automatically dealloc objects we manually alloc.
I think that the approach that's currently implemented in FLEX is the correct one, since ARC is a compile time mechanism, and I don't see a sensible way to apply it to runtime inspection that FLEX is.
Maybe what we can do is add some screen for orphaned objects, if it is even possible.

There should absolutely be a correct way to implement it; these methods are returning retained values, and I believe we are over-retaining them by not using __bridge_transfer.
That said, it is curious why this is having an effect on other objects entirely… I'll do some digging! If you find anything else, do share! 😄

So, this is super weird: it only crashes on the X* family of devices. Does not crash or leak on the 6s, 7, or 8. I wonder why that is.

Here's some trace logs, one demonstrates a "leak" of a simple Foo class, when using the existing implementation, and the other demonstrates a zombie when using anything that makes an early release, like __bridge_transfer or CFBridgingRelease
So far I've been unable to diagnose it or find the root cause, but I think we're over-retaining something somewhere totally outside the scope of where we call getReturnValue:. Maybe in potentiallyUnwrapBoxedPointer: or -[FLEXMethodCallingViewController actionButtonPressed:]

To simplify the inspection of the problem, I've created the repo:
https://github.com/DrBreen/RetainResearch
I've added you as collaborator in case you'll want to make some edits, or if you'll find something that you need to edit.
From what I see even with this barebones code the problem still occurs:

We hold the object in ViewController property
We get it via NSInvocation
We cast it's address via __bridge_transfer
It gets deallocated, even though it's still being held by ViewController

I'm looking into how can I see ARC byte code with retain/release calls.

Tracing the calls with Instruments definitely shows additional release call when using __bridge_transfer! And assembly also shows the same.
Looks like by casting pointer to id with __bridge_transfer it acknowledges that now current scope is the owner of object, and it should release the object when it exits the scope.
It doesn't happen with __bridge because compiler does not assume we are now owning the object - we are merely getting it to play and then we should put it back in place, the original owner knows better what to do with it and when to retain/release it.
So, I don't know if we can fix it. It looks like a fundamental problem - we can't transfer ownership of 3rd party objects to FLEX, since we are absolutely unaware of their lifecycles. Maybe we should give user two options - call the method without ownership transfer and with it?

Wow, awesome! Thanks! I'll definitely be using that to help debug this when I have more time.

So, I don't know if we can fix it. It looks like a fundamental problem - we can't transfer ownership of 3rd party objects to FLEX, since we are absolutely unaware of their lifecycles. Maybe we should give user two options - call the method without ownership transfer and with it?

Again, I'm not sure I agree. Both the leak (using __bridge or __unsafe_unretained, which tell ARC to do nothing for the time being) and the crash (using anything that triggers a release, like __bridge_transfer or CFBridgingRelease) are related to objects whose lifetimes we should absolutely be able to reason about, as far as I know. We're just calling methods and looking at the return value. Why one approach leaks and one doesn't but crashes tells me we have a bug somewhere. We just need to find out where that extra retain or missing release is coming from :)

I'm starting to check all the versions from 1.0.0 (similar to git bisect approach, or maybe I'll use the command, actually!), but I think we may be talking about two different things, that's where the disagreement comes from. But I'll check anyway, as there were a lot of cases where I was 99% I'm right, and in the end I was wrong :)
Now, consider everything that's written below correct if and only if we have no way to force retain call when casting const void * to id. If we have a way to do that, we may be able to bypass the problem I'm mentioning below. This bit was written after I wrote the whole comment as I suddenly got an idea - I'll be trying it now, I'm absolutely not sure if it'll work, but we may have a chance.
The demo I did with barebones code confirmed my suspicion that the extra release comes exactly from __bridge_transfer. According to Apple docs, __bridge_transfer is the same as CFBridgingRelease.
In the documentation they provide code sample:
CFStringRef cfName = ABRecordCopyValue(person, kABPersonFirstNameProperty);
NSString *name = (NSString *)CFBridgingRelease(cfName);

and they say this:

You use this function to cast a Core Foundation-style object as an Objective-C object and transfer ownership of the object to ARC such that you don’t have to release the object

So basically, it's as if somebody allocated the memory for us, initialised the object and then gave it to us and said "here, take care of it, it's yours now". ARC sees this and adds these extra release you're talking about.
Now, how does it play with leaked object bug and with weird crashes we get when trying to inspect objects?
Well, it's pretty simple - using CFBridgingRelease or __bridge_transfer we basically say to compiler - "okay, the object at this address is now mine, please handle it's memory cycle". Then, at some point (probably when we've build text description of property for UITableView cell in object inspector), the ARC sees that the object exits the scope, and sends release message to it. However, the only retain the object got was during it's allocation in it's owner - the object we're inspecting.
So it goes like this:

Object is allocated (retain count is 0)
Object is retained by it's owner (retain count is 1)
We inspect the object (retain count is 1)
We try to build property description - we get object via NSInvocation (retain count is 1)
We get the address of object and take ownership via __bridge_transfer (retain count is 1)
We finish building description (retain count is 1)
Object reference we're using for description leaves scope, and ARC sends release (retain count is 0)
We're trying to access the object for any other reason (inside original owner, we scrolled UITableView and got cellForRow call, etc.) - crash, as object is deallocated, yet it's reference in original owner still points to the address.

Now, regarding if we know the scope of the object being overreleased or not.
Actually, we're both right - we both know and we don't!
If we're talking specifically regarding new object allocation - the scope is definitely known for us - it should be alive from the time we allocated it to the point where we left the inspector screen of this object.
However, if we're inspecting the object that doesn't belong to us, like property of AAPLAppDelegate, then we have absolutely no way to know it's scope. The property may live for as long as the object is alive, it may be deallocated after getting NSNotification, it may be allocated/deallocated on timer...there are endless possibilities!
So yes, you are right that when we allocate new object manually, we can know it's lifespan.
However, another problem arises - how do we differ between objects that we're allocating, and the objects that aren't ours? This is the fundamental problem I was talking about - other than few cases like '[[ClassName alloc] init]or[ClassName new]`, there's no surefire way to know whether the object we got is newly allocated and we can take ownership, or if it's the object with lifecycle that we can't control.
I'll give you an example. Let's say we define that all the properties we inspect - we get them using __bridge, without taking ownership, as it's pretty safe to say that properties are never ours, and we always take ownership of objects returned by methods using __bridge_transfer.
However, what if instead of inspecting property, we call the method of the same name?
Like, instead of object.hisProperty we'll call [object hisProperty] using FLEX. That way we don't overrelease the object if we're inspecting the property, but we're overreleasing it using the method, and we still get the crash. We can try to mitigate that, by, for example, comparing the name of method with properties, and if we find a match, we use __bridge instead of __bridge_transfer. But again, it's flaky - if getter name is different, then we're out of luck.
And if, for example, method returns one of object ivars - that way we'll still overrelease it and cause crash.
That's why I believe there's a fundamental problem, and that's not a simple bug - it's just that we have no way of knowing whether the object we got can be safely released by us.

Well, the method I tried didn't work - I though moving the cast to a different file with ARC disabled for that file with manual call to retain will help, but it didn't - the leak still happens.

only if we have no way to force retain call when casting const void * to id

We do! We can (__bridge CFType) cast the object and pass it to CFRetain, or we can just cast it with __bridge_retained instead of __bridge_transfer.
In a nutshell, __bridge does nothing, __bridge_retained retains and __bridge_transfer (auto)releases. I often turn to this stackoverflow answer when I get confused about these keywords.

So it goes like this:

Object is allocated (retain count is 0)
Object is retained by it's owner (retain count is 1)
We inspect the object (retain count is 1)
...

That's not quite right. Did you ever look at the trace logs I uploaded? The object is retained and released several times throughout its lifetime.

However, what if instead of inspecting property, we call the method of the same name?
Like, instead of object.hisProperty we'll call [object hisProperty] using FLEX. That way we don't overrelease the object if we're inspecting the property, but we're overreleasing it using the method

I'm a little confused here... properties are just syntax sugar around methods. Are you familiar with that? 😅

That's not quite right. Did you ever look at the trace logs I uploaded? The object is retained and released several times throughout its lifetime, which is what makes this so complicated :\

Are we talking about trace logs from FLEX, or from the basic example? If we're talking about FLEX, then I'd suggest moving to basic example you forked, since that is easier to work with and the problem is still there. Once we fix it there (or decide there's no fix), we can move on to fixing it in FLEX.

I'm a little confused here... properties are just syntax sugar around methods. Are you familiar with that?

Of course I know what. What I wanted to show is the following case, but after I reviewed runtime introspection for properties, I learned that we have no problem knowing what getter and setter property has, even if it has different name.
This is the case I wanted to show:
@property (readonly, getter=methodForTheTestProperty) NSString *testProperty;
And we have the method definition:
- (NSString *)methodForTheTestProperty {
...
}

These (Instruments) trace logs: https://github.com/Flipboard/FLEX/files/3082301/Archive.zip

Like, instead of object.hisProperty we'll call [object hisProperty] using FLEX.

This is what I was referring to when I asked about properties—these are the same thing.

I learned that we have no problem knowing what getter and setter property has, even if it has different name.

Ah, I see

I seem to have gotten so caught up in the leak you uncovered that I forgot about the feature this PR was originally for!
A few constructive notes:

Prefer the NS_ENUM macro over plain 'ol enums
Prefer switching over self.someEnum instead of if-elseing over possible values—the compiler can help catch missing cases if new ones are added later
Prefer const T XYZVar = 5; over #define XYZ 5—variables will show up in the debugger but macros won't
Properties are atomic by default (a mistake I'm sure someone regrets to this day), so you should always annotate them as @property (nonatomic)

Overall, nice work! I made some changes, like making sure git detected the file renames as such and not as add/delete, allowing us to specify a placeholder for both entry fields, and defaulting to the "preferred" method of entry based on the type of the property or argument being modified.
I have this on my local copy of your object_input feature branch.  Can I push it to your master branch?

Wow, thanks! I myself also forgot about this change due to having massive changes in my life going on. What was the actual cause for the leak?

I never did find out, but there is an open issue for it. It's not a super high priority for me now that we've spent hours debugging it to no avail.
If you have a developer account, it may be worthwhile to use one of your Code-Level Support tickets to help find the bug. (I've already used one of mine and I want to use the other on the Heap Enumerator because those APIs are poorly documented and some objects don't show up)


Change "Claim" to "Complete" and introduce "In Progress"

When the user clicks the launch activity, auto-mark them as "In Progress," then have them "Complete" the activity afterwards.

We've changed the approach on this by simplifying even further, whereby the activity is now marked as "complete" on launching it, and every launch is tracked. The could use some fine tuning still, but the spirit of this issue is fulfilled.


IE11/ES5 minimum support

Although support was officially dropped in v0.3.2, errors occur in v0.22.14, so the last version that worked in IE11 is v0.22.12.
In v0.25.1, PR#310 changes the code to ES6 modules. Since IE11 only supports up to ES5, I feel it is no longer practical (or at least not worth the effort) to patch in IE11 support into v0.25.x and v0.3.x . However, patching in fixes up to v0.24.4 is feasible. Versions 0.22.14-0.24.3 could also be patched, but I'm not sure if this would add any value over a single v0.24.4 patch at this time (If other issues come to light with currently-untested paths, then this may be worth looking into more).
I have already created a branch which I have done limited testing on. This could be used for an unofficial patch that one could build locally. I could also create my own release to save others the build step, but it wouldn't be in npm, so there would be some hoops to jump through to use it.
To create an official npm release, I believe the following steps would be necessary.

[ ] create a branch in the official repo from the v0.24.4 tag @TonyGermaneri or @ndrsn ?
[ ] create a pull request to the above branch patching the code @jswolf19
[ ] merge the above PR @TonyGermaneri or @ndrsn ?
[ ] create a release v0.24.5? v<IP_ADDRESS>? something else? @TonyGermaneri
[ ] other steps to add to npm? @TonyGermaneri

see also discussion here and here

Going forward, it might not hurt to provide a pre-polyfilled bundle (Probably an IIFE bundle) with a caveat that it's only provided for better backwards compatibility; so IE11/Opera Mini would likely work with it, but not explicitly support them. When I can finally get around to fleshing out how to go about the Typescript migration, I'll probably look at including a polyfill bundle anyways, it's just a matter of what target to polyfill to. So depending on how many different bundles is acceptable, there could be a light polyfilled bundle that targets relatively modern browsers, and one that does its best to polyfill to IE11/Opera Mini and takes the hit to the bundle size.

@josh-hemphill considering the lack of issues about support for ES5 despite the fact that support has been broken for over half a year, I'm not sure how much value bundling polyfills would bring. The majority of what I fixed was non-ES5 syntax (arrow functions), so without a conversion to something like Typescript, trying to enforce ES5-compatible syntax would just serve to make contributing more painful for people. Conversion to Typescript should make it much easier to do, as long as compilation to ES5-compatible javascript continues to be supported, but, while I can't speak to Opera (Mini), testability in IE is also not stellar, either.


Added basic implementation

This PR add a basic implementation for the activity-log.

@chirimoya i hope that now all the renamings are done (:


NTR: direct RNA sequencing assay

editor preferred term: direct RNA sequencing assay
alternate terms: direct RNA-seq, DRS
textual definition: An assay in which to study transcription through direct single molecule RNA sequencing without prior conversion of RNA to cDNA.
definition source for the textual definition: https://www.nature.com/articles/nature08390
logical definition: RNA-seq assay [OBI:0001271] --> direct RNA sequencing assay

Minor edits:
editor preferred term: direct RNA sequencing assay
alternate terms: direct RNA-seq, DRS
textual definition: An assay to study transcription through direct RNA sequence determination, without prior conversion of RNA molecules to cDNA.
definition source for the textual definition: https://www.nature.com/articles/nature08390
logical definition: RNA-seq assay [OBI:0001271] --> direct RNA sequencing assay

Looks great.
Thank you.

Have there been any updates on the addition of this term?

Discussed 2019-10-28. Dan will add this term.

Pull request generated.

https://github.com/obi-ontology/obi/pull/1070


snmpfwd Update?

Is your feature request related to a problem? Please describe.
snmpfwd has not been updated for usage against pysnmp version 6 and above.
It currently can only use 5.1.0 due to its dependency on asyncore.
Describe the solution you'd like
An update to support the asyncio based pysnmp.
Describe alternatives you've considered
I tried finding any SNMP V3 to V1/2 proxy but no such luck.
Additional context
Is there any major bugs that makes it unusable or minor bugs to take note of? Does trap notifications work?

Pull requests are welcome.
We currently have no plan to update as no commercial customers use it.


WinVersionLie 95 and 98 cause crash on Windows 7 x64

I have just been testing Rainbow Six Black Ops 2.0 standalone mod which contains DDrawCompat and the game displays an error at launch: "The application was unable to start correctly (0xc00000142)". It turned out that commenting out WinVersionLie = 98(0) in DDrawCompat.ini fixed the issue and the game works fine. The error also shows up when WinVersionLie is set to 95. Other parameters (nt4,2000,xp) don't cause any issue. I have also tested it with the latest version of DDrawCompat (0.5.4) but the issue persists.
Here are the last lines from debug log

1b20 05:13:42.697 > GetVersionExA({148,0,0,0,0,<0018CC28>,0,0,0x0,0,0})
1b20 05:13:42.697 < GetVersionExA({148,4,10,67766446,1,Service Pack 1,0,0,0x0,0,0})
1b20 05:13:42.697 Initial DPI awareness: system
1b20 05:13:42.697 Primary CPU group number: 0
1b20 05:13:42.697 Physical to logical CPU core mapping for efficiency class 0:
1b20 05:13:42.697   Physical core #1: 1, 2
1b20 05:13:42.697   Physical core #2: 3, 4
1b20 05:13:42.697   Physical core #3: 5, 6
1b20 05:13:42.697   Physical core #4: 7, 8
1b20 05:13:42.697 Current CPU affinity: 1, 2, 3, 4, 5, 6, 7, 8
1b20 05:13:42.697 Applying configured CPU affinity: 1
1b20 05:13:42.697 CPU affinity rotation is enabled
1b20 05:13:42.697 DDrawCompat loaded successfully
1b20 05:13:42.697 > GetVersionExW({284,0,0,0,0,<0018F1D4>,0,0,0x0,0,0})
1b20 05:13:42.697 < GetVersionExW({284,4,10,67766446,1,Service Pack 1,1,0,0x100,1,0})

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."


⚠ Bofrost.at has degraded performance

In a70356b, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2509 ms

Resolved: Bofrost.at performance has improved in 19cde3b after 9 minutes.


When the video is disabled on ongoing call, Last image still been shown in caller and receiver.

I'm having issue while disabling video in active call.
When i muted the video (from caller/receiver) using
this._session.mute('video');

muted video screen will display the last visible image.  I think it should be shown black screen.
I've also tested this issue in this sample application (RNVideoChat) and the issue still persist.

The recommended way is to send system messages to other users along with mute/unmute
https://developers.connectycube.com/js/messaging?id=system-messages
so other user once received the system message - can hide your video view
for example
const userId = 123234;

ConnectyCube.chat.sendSystemMessage(userId, {videommute: true});

...

ConnectyCube.chat.sendSystemMessage(userId, {videommute: false});


Suspicion gamemode needs localizing

Description

https://github.com/space-wizards/space-station-14/blob/master/Content.Server/GameTicking/Presets/PresetSuspicion.cs
As you can see this stuff should be localized. However before I do it myself I wondered if it mattered since Suspicion is one of our more placeholder gamemodes and additionally a lot of the lines like
_chatManager.DispatchServerAnnouncement($"Not enough players readied up for the game! There were {readyPlayers.Count} players readied up out of {MinPlayers} needed.");
Feel like they could be used in a base system somewhere.
Just wondering what other maintainers think of this.

ye honestly gamemodes are weird. i havent given much thought to how i'd like to see them refactored, i just know i find our current implementation weird


Avoid exponents when printing float values

Some MSOffice products don't work well with exponents in JSON values.
This happens when a very small values is being printed.
This PR suggests we use sprintf instead of json_encode when printing a float value.

Hi @kourawealthtech is the behaviour you need the same as described here: https://docs.oasis-open.org/odata/odata-json-format/v4.01/odata-json-format-v4.01.html#sec_ControllingtheRepresentationofNumber ?
Lodata does support the IEEE754Compatible feature, but at the moment it needs the client to request that it be enabled. It would make sense for the service to be able to have it enabled by default in the config, the same as how you can do that for streaming JSON.
If you change src/Primitive.php:122 to:
        $value = $this->toJsonIeee754();

does that resolve the issue for Excel?

I'm closing this as I am not sure this is the right general solution.


CRON_PERIOD or CRON_INTERVAL

Looking at the docker compose example it uses "CRON_PERIOD=10" but in the documentation it shows "CRON_INTERVAL"
Which one should I use?
Note: It may not be the site to thank but thank you, because it is very easy to get up and running.

Both work actually https://github.com/tiredofit/docker-osticket/blob/62400b5b9b3803eb07e29cb1ce7e5a6ae4230f8e/install/etc/cont-init.d/30-osticket#L24
I'd prefer long term usage of CRON_INTERVAL however. I've updated the example to reflect this..

Thanks, I update my .yaml


Demo is not working on Safari or mobile-Safari

...

Wondering why

Hmm, maybe a cross-domain XHR problem? Hard to test without any environment information... would be helpful if you could provide us with platform specs and in the best case, also with some browser debug information!

I'm pretty sure is related to https://github.com/wheresrhys/fetch-mock. Which actually we are not using in the demo at all....

@MP0w @joanromano @ryyppy fixed on https://github.com/zzarcon/gh-emoji/pull/29 please take a look in Safari again


Potential FPS drop with pickups

Hello,
Recently a group I'm part of has noticed FPS drops when picking up items in a new map one of them made. After some time troubleshooting, we've unfortunately narrowed the problem down to this menu. The problem seems to occur most reliably when someone is moving with a held object.  That causes an FPS drop of nearly 10 frames in the worst cases. Removing the menu from the scene clears these issues immediately. I'm not sure what interaction between the menu and the object could be causing this, to my knowledge the lag can occur even with a default cube.
We use this menu in most of our maps, but none of them had pickups until now.

Hi! I've given it a shot, but I've not been able to replicate this problem on my end. Would you be able to give me some information so I can better look into the issue? This is a truly strange issue and I have no idea how the menu could be causing this.
Here is what I have done in attempt to replicate the issue: I opened the sample scene in the GMMenu package and added a VRCPickup and a VRCObjectSync to it. I can see no noticeable difference in my frametime between when I pick it up and when I drop it. I have also tested this on multiple worlds that use my menu and have pickups, but could not recreate the problem there either.
Since removing the GMMenu fixes your issues, it is very possible that it is interfering with something in your project in particular, so any additional information would be helpful here.


feat(ci): Github Workflow Release

Description
Generates a github release from an action

Current dependencies on/for this PR:

main

PR #41   👈

This stack of pull requests is managed by Graphite.


added aksUpgrade versions endpoint

#34161
Old pr for reference: https://github.com/rancher/rancher/pull/34624
Problem:
In AKS you cannot skip minor version updates. Currently we list all available versions in the upgrade drop down. This lets users attempt to upgrade to version that is too high causing the cluster to go into a constant error state.
Solution:
I added the a new endpoint, /meta/aksUpgrades. This endpoint will return all available k8s versions similar to /meta/aksVersions however each version includes an enabled  flag.  This flag is true if the associated version is a valid upgrade version for the given cluster.
Testing
Valid response
$ curl -s -H "Authorization: Bearer $RANCHER_TOKEN" "https://<rancher>/meta/aksUpgrades?cloudCredentialId=<creds>&region=eastus&clusterId=<cluster id>" | jq
{
  "currentVersion": "1.20.7",
  "upgrades": [
    {
      "version": "1.18.17",
      "enabled": false
    },
    {
      "version": "1.18.19",
      "enabled": false
    },
    {
      "version": "1.19.11",
      "enabled": false
    },
    {
      "version": "1.19.13",
      "enabled": false
    },
    {
      "version": "1.20.7",
      "enabled": false
    },
    {
      "version": "1.20.9",
      "enabled": true
    },
    {
      "version": "1.21.1",
      "enabled": true
    },
    {
      "version": "1.21.2",
      "enabled": true
    }
  ]
}

Error Response
$ curl -s -H "Authorization: Bearer $RANCHER_TOKEN" "https://<rancher>/meta/aksUpgrades?cloudCredentialId=<creds>&region=eastus&clusterId=<cluster id>" | jq
{
  "error": "invalid cluster id"
}

If you have a 1.19 cluster does the response still show correctly?

Retested with latest changes
GET https://<rancher host>/meta/aksVersions?cloudCredentialId=<creds>&region=<region>

["1.19.11","1.19.13","1.20.7","1.20.9","1.21.1","1.21.2"]

GET https://<rancher host>/meta/aksUpgrades?cloudCredentialId=< creds >&region=<region>&clusterId=<cluster id>

{"currentVersion":"1.19.13","upgrades":[{"version":"1.20.7","enabled":true},{"version":"1.20.9","enabled":true},{"version":"1.21.1","enabled":false},{"version":"1.21.2","enabled":false}]}

Closing this pr due to weird github behavior and also to change the branch


Generate and implment API deployer methods

Not relevant. We do everthing via TOSCA and rbbitmq messages. The manager sends the TOSCA file as a message to the deployer via rabbitmq. The deployer reads the interface and executes ansible playbooks


support strict utm parsing

Allows us to move the new default to strict parsing and show an option for users to enable it on existing projects without breaking the "feature" (bug) of supporting other utm types. proposed rollout / sequencing plan here

Nice!

Hi @sperand-io, as part of the monorepo migration, this issue has been moved to new issue. Our engineers have been notified and will prioritize and work on it ASAP. Thank you!
For more information, see README.md.


nixos/gdm: automatically enable services.displayManager

Things done
When trying to use GDM with sway, I started to simply add
services.xserver.displayManager.gdm.enable = true;

However, this was only greeting me with the tty.
It turns out that the generated display-manager.service didn't have any ExecStart field:
❮ sudo systemctl status display-manager.service
○ display-manager.service
     Loaded: bad-setting (Reason: Unit display-manager.service has a bad unit file setting.)
     Active: inactive (dead)

Manually adding
services.displayManager.enable = true;

made the trick.
This PR automatically does that.
greetd does this by default too.
cc @K900 @lilyinstarlight

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

I wonder if there are other niche cases where this happens, might be worth looking over everything else exhaustively.

@SuperSandro2000 bump


Arm Cortex-M3

Hello,
I found on Ebay basic Cortex card Stm32f103c8t6 Cortex-M3  associated St-Link V2
Could you if the future version of Gnea could work with ?
Good night.

@LETARTARE : Can't see why not. I've been building a HAL interface that will allow porting to most controllers quickly and easily. It'll just take someone willing to do the port. I'll be maintaining the main HAL and the SAMD21 port.

See #4


Make stats.py work with python 3

This fixes the following error with python 3:
# stats.py

As of 2016-10-23 the repository contains:

| **File paths covered** | **709** |
| :------------------ | ------: |
| **Registry keys covered** | **429** |
| **Total artifacts** | **415** |

**Artifacts by type**

Traceback (most recent call last):
  File "/usr/local/bin/stats.py", line 106, in <module>
    main()
  File "/usr/local/bin/stats.py", line 102, in main
    statsbuilder.PrintStats()
  File "/usr/local/bin/stats.py", line 95, in PrintStats
    self.PrintSourceTypeTable()
  File "/usr/local/bin/stats.py", line 44, in PrintSourceTypeTable
    self._PrintDictAsTable(self.source_type_counts)
  File "/usr/local/bin/stats.py", line 17, in _PrintDictAsTable
    key_list.sort()
AttributeError: 'dict_keys' object has no attribute 'sort'

This change is

LGTM


UI: List view's filters

Using the add filter dropdown feels pretty intuitive itself, but the layout of the inserted filters look bit unpolished. Also it was unclear to me at first usage how/when the set filter configurations get submitted.
With this topic I'd like to start discussion how the filters UI could be made as intuitive and self evident as possible for the end user.

It's way better now with TB