Feature request: #[SensitiveParameter] inspection

Simple PHP 8.0+ inspection that suggests adding #[SensitiveParameter] to function arguments with specific name.
This attribute is used to mark a parameter that is sensitive and should have its value redacted if present in a stack trace.
Example:
function example($user, $password) {
//some code
}

Inspection should suggest change to:
function example($user, #[SensitiveParameter] $password) {
//some code
}

I think that by default this list should contain names like:

password, passwd (* passw *)
password_hash, passwordHash (* hash)
token, api_token, access_token, user_token (token *)
secret, client_secret (* secret *)
auth, auth_code (* auth *)
api_key, apiKey, apikey, public_key, publicKey, publickey, private_key, privateKey, privatekey, encryption_key (*key)
card, credit_card, creditCard, creditcard (* card)
bank_account (* bank *)
ccn
pin
jwt
cert
email, mail
phone
first_name, firstname, firstName
last_name, lastname, lastName
full_name, fullname, fullName
session, session_id

List of argument names to trigger on should be configurable by user so they could add/remove cases

The idea is very good, if you have more knowledge about other attributes, please send all the ideas you can. It's something new to me, but I know it's important, just like the idea reported in #39.

Thank you for taking the time to suggest this improvement. The implementation has been completed in version 0.28.0 and is now available through the Releases page. If you prefer, this update will also be accessible on the Jetbrains Market in approximately three days.
Regarding the specific topic:

I'd introduced a new inspection to notify you about the use of sensitive names in parameters. Honestly, I thought this would be a lot easier, but it was quite a challenge! There are two available options: the list of sensitive words (which will automatically pluralize, so you only need to add password, for instance, and it will automatically recognize passwords as a sensitive word); and the second option, enabled by default, allows it to ignore bool, int, and float types (and nullables), even when they include sensitive words (e.g., int $secret won't trigger a notification).


chore: Add instruction to create file for remix getting started

I think we should instruct the user to create a file where the contents will be. Currently it is just a filename on the code snippet.

Do you want to add this same change to all of the examples, not just Remix?

Replaced by #192


[5.5] Create higher order "with" proxy

Useful for when you're not sure whether a given value is null.
If the value provided is null, any method calls or property access on the proxy will safely return null.
// This may throw, when there's no logged-in user
$username = auth()->user()->username;

// This won't ever throw
$username = with(auth()->user())->username;

Another example would be if you want to delete a model, but it may have already been deleted:
// This may throw, if the post has already been deleted
Post::find(1)->delete();

// This won't ever throw
with(Post::find(1))->delete();

If you want to do multiple things with the object, a callback will do the trick:
$name = with(auth()->user(), function ($user) {
    return "{$user->first_name} {$user->last_name}";
});

...when there's no logged-in user, $name will be null.

So now i would be able to do something like this,
{{ with($mode->somedate_at)->format('Y-m-d') }}

Without having to check if i have set the value to a date?

@stefanoruth absolutely. That's another good example 👍

The date format check alone makes this worth it.

What do you think about making this a new helper called optional?
There was a blog post on it a while back where someone did something similar.

what about nullify()
{{ nullify($model->somedate_at)->format('Y-m-d') }}
which describes we are accepting the value to be nulled if it does not validate?

Prefer optional.

{{ try($model->somedate_at)->format('Y-m-d') }}

@taylorotwell

@taylorotwell The word with is easier to write, and also reads better with the flow.
Additionally, since PHP now has proper dereferencing in most situations, the with helper barely has any uses these days.
I believe adding this functionality to the with helper makes a ton of sense.

Maybe attempt is more expressive (It will attempt to do that if the value is not null).
If you look at your code months later,trying to remember what does the with do can be more difficult than the attempt.

In my point of view with method name is using for relationships already and could be misunderstood.

@a-komarev with is an existing helper that is as old as Eloquent's with method.
I don't see any confusion between the two.

I like the functionality, but I agree on the name change to optional. This isn't what the with function is currently used for, so I don't see why it makes sense to modify it for these new features.
Saying that the world "with" is shorter and flows better doesn't matter if it doesn't convey meaning. "What does that use of the with method do?" "Oh, it swallows method called on null errors." That doesn't seem to make sense at a glance, does it?

Just to add another what about X.
when($model->somedate_at)->format('Y-m-d')
but maybe that to much "is it checking truthy values?"

Resubmit when it is changed to optional.


Inclusion of my school

@Weslley-Souza32 The first verification stage is complete: the official domain for  Faculdade Promove is faculdadepromove.br, to the best of my knowledge. This is just an informational note. The pull request is still under review. The review may take some more time. I greatly appreciate your patience. Here is the proof of domain ownership: https://faculdadepromove.br/wp-content/uploads/2023/11/2021-2_Publicare.pdf

@Weslley-Souza32 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Kubectl exec: connection refused

When enabled frakti with kubelet, kubectl exec failed with errors:
cluster/kubectl.sh exec busybox-983667326-wlbt7 ip addr
Error from server: error dialing backend: dial tcp <IP_ADDRESS>:22521: getsockopt: connection refused

Is this happens on latest hyperd master?

It seems the bug of frakti, it doesn't listen to <IP_ADDRESS>:22521 while exec is executing.


Not working on Ryujinx 1.1.763 and 1.0

None of the cheats take any effect, on version 1.1.763 of ryujinx and version 1.0 of the game.
The log errors:

https://i.imgur.com/suskzFU.png
Thanks for the work.

That's because you're most likely using the newer cheats for 1.1.

The error message is quite clear, you are not using the correct version.

Thank you very much for your answers. I didn't know there were different versions of the cheats, I'm not able to see where it mentions which version of the game the cheat file is for. I will try to update the copy of the game Thanks for the work!


Unsupported object type float

System information

Have I written custom code (as opposed to using a stock
example script provided in TensorFlow): yes
OS Platform and Distribution (e.g.,
Linux Ubuntu 16.04): Ubuntu 18.10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if
the issue happens on mobile device: N/A
TensorFlow installed from (source or
binary): binary
TensorFlow version (use command below): 2.1.0
Python version: 3.7.3
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from
source): N/A
CUDA/cuDNN version: nvcc version 10.1 (V10.1.105)
GPU model and memory: NVIDIA Quadro P2000 5GB

Describe the current behavior
I am loading in a concatenation of two user data sources (one script generated and on read in via pd.read_csv).
I paid attention to have both datasources have the same dtypes, column names, etc.
I concatenate via
fakedata = td.generate_data(40000)
realdata = pd.read_csv("DS.csv")
data = fakedata.append(realdata).reset_index()[fakedata.columns]

DataFrame structure is as follows:
| firstname | lastname | company | country | email | fake |
| Lorem | ipsum | Loremcorp | USA |<EMAIL_ADDRESS>| 1 |
whereas data["fake"] is the target column having either 0 or 1 as state.
dtypes of the are object and of data["fake"] is int64.
train input fn:
train_input_fn = tf.compat.v1.estimator.inputs.pandas_input_fn(
    data, data["fake"], num_epochs=None, shuffle=True
)

training:
estimator = tf.estimator.DNNClassifier(
    hidden_units=[500, 100],
    feature_columns=[email_feature_column,
                     firstname_feature_column,
                     lastname_feature_column,
                     country_feature_column,
                     company_feature_column],
    n_classes=2,
    optimizer=tf.keras.optimizers.Adagrad(lr=0.003))

estimator.train(input_fn=train_input_fn, steps=5000)

Feature columns are created via the text_embedding_column from tfhub.
When I now try to run the code this error keeps happening:
Traceback (most recent call last):
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1367, in _do_call
    return fn(*args)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1352, in _run_fn
    target_list, run_metadata)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1445, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.InternalError: Unsupported object type float

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "tensorflow_model.py", line 67, in <module>
    estimator.train(input_fn=train_input_fn, steps=100000)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 374, in train
    loss = self._train_model(input_fn, hooks, saving_listeners)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1164, in _train_model
    return self._train_model_default(input_fn, hooks, saving_listeners)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1198, in _train_model_default
    saving_listeners)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/estimator.py", line 1498, in _train_with_estimator_spec
    any_step_done = True
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 885, in __exit__
    self._close_internal(exception_type)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 923, in _close_internal
    self._sess.close()
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 1190, in close
    self._sess.close()
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/training/monitored_session.py", line 1358, in close
    ignore_live_threads=True)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/training/coordinator.py", line 389, in join
    six.reraise(*self._exc_info_to_raise)
  File "/usr/lib/python3/dist-packages/six.py", line 692, in reraise
    raise value.with_traceback(tb)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_estimator/python/estimator/inputs/queues/feeding_queue_runner.py", line 94, in _run
    sess.run(enqueue_op, feed_dict=feed_dict)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 960, in run
    run_metadata_ptr)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1183, in _run
    feed_dict_tensor, options, run_metadata)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1361, in _do_run
    run_metadata)
  File "/home/damned/.local/lib/python3.7/site-packages/tensorflow_core/python/client/session.py", line 1386, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InternalError: Unsupported object type float

even if there is no float in the dataset.
Describe the expected behavior
estimator.train(input_fn=train_input_fn, steps=5000)
Works as expected and trains.

Had broken values in the dataframe. Checking the dataframe with np.unique(df[column] and df[df.isnan()] helped solving the issue.


[question] How to handle reconnecting on RabbitMQ server restart

I have a consumer and I'm wondering how best to recover when RabbitMQ goes away.
Currently I get a Bunny\Exception\ClientException thrown which kills my React event loop:
Fatal error: Uncaught Bunny\Exception\ClientException: Broken pipe or closed connection. in .../vendor/bunny/bunny/src/Bunny/AbstractClient.php on line 280

Bunny\Exception\ClientException: Broken pipe or closed connection. in .../vendor/bunny/bunny/src/Bunny/AbstractClient.php on line 280

Call Stack:
    0.0001     354160   1. ...
    0.0015     587600   2. ...
    0.0090    2108960   3. React\EventLoop\StreamSelectLoop->run() ...
   41.4237    2972512   4. React\EventLoop\StreamSelectLoop->waitForStreamActivity() .../vendor/react/event-loop/src/StreamSelectLoop.php:201
   41.4698    2972992   5. call_user_func:{.../vendor/react/event-loop/src/StreamSelectLoop.php:232}() .../vendor/react/event-loop/src/StreamSelectLoop.php:232
   41.4698    2972992   6. Bunny\Async\Client->onDataAvailable() .../vendor/react/event-loop/src/StreamSelectLoop.php:232
   41.4698    2972992   7. Bunny\AbstractClient->read() .../vendor/bunny/bunny/src/Bunny/Async/Client.php:292

I can handle the ClientException at the top-level of my application with:
while (1) {
    try {
        $loop-run();
    } catch (ClientException $ex) {
        // reconnect logic goes here
    }
}

That seems a little heavy-handed to me. Is this the right thing to do or is there a better way?

I think there's not any reason to restart RabbitMQ broker regularly and so it's not something you should explicitly handle in your consumer. Letting the whole process restart is just fine in my opinion.

In my environment RabbitMQ restarts will happen. My use case is a job queue with some potentially long-running jobs. If the broker is restarted I don't want to kill currently running jobs.
It should be possible to re-establish the connection and when the "start job" message is redelivered to the job executor, to immediately send or enqueue an ack for that job.
Do you think it's a better solution to kill all pending jobs if the message broker goes away?

Well if the broker is restarted and the connection interrupted, you should quit processing the jobs because you have no way to ack the messages and so RabbitMQ will redeliver them again. I also recommend you to make the messages "smaller" so each message is processed faster and there is more of them. So "long running" jobs wouldn't be as long.
But the main issue here is that the restarts should not happen on regular basis.

OK, thank you!


Settings: cannot drag scrollbar in some cases

In some cases dragging the scrollbar on the left hand side of settings does not move it. It seems to happen when mouse is over a line that is collapsed.

@bpasero I am not able to reproduce it.. Can you help in getting into this scenario ?

@sandy081

Thanks @bpasero. Do you also have zoom level set to 1?

@sandy081 yes!


Updated requirements for Teams PowerShell

Simplified Teams PowerShell requirements.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@brandber PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Add testnet blocks to zebra_state

This is a small part of https://github.com/ZcashFoundation/zebra/issues/683 where testnet genesis block and the first 10 blocks are added as test vectors.
Utilities where added for tests to know in what mode(Testnet, Mainnet) they are currently running. Mode is a mutex that can be updated by any test.
As we want the tests in zebra_consensus to use zebra_test::Transcript(https://github.com/ZcashFoundation/zebra/issues/744, https://github.com/ZcashFoundation/zebra/issues/610) i decided to get started with the zebra_state where this is already in place.
I am unsure if the approach is the most clear, was done trying to avoid duplicated code.

This will be easier if https://github.com/ZcashFoundation/zebra/pull/773 is merged and this PR rebased into that.

Mode is a mutex that can be updated by any test.

Nooooooooo... Global mutable state in tests considered harmful.

Thank you for the head up @daira , for sure is something we will not want to do.
I just force pushed to be more clear on what i am trying achieve, this is not a definitive version but can take a look if you want.
Basically what i need is to pass some argument to the transcript static however it is hacky just to say that. Looking for options without duplicating the transcripts for the 2 modes.

Basically what i need is to pass some argument to the transcript static however it is hacky just to say that. Looking for options without duplicating the transcripts for the 2 modes.

It looks like you'll need to write transcripts with Request=(Network, BlockHeight).
Then in the tests, you can call a new async get_block function which takes a Network and BlockHeight, and returns the zebra-test::vectors block for that height.
Once that's working, you might be able to make it more ergonomic by using get_block inside the transcript implementation.
Then you should be able to call the tests like this example:
    #[tokio::test]
    async fn test_transcript_mainnet() {
        test_transcript(Mainnet).await;
    }

    #[tokio::test]
    async fn test_transcript_testnet() {
        test_transcript(Testnet).await;
    }

    /// Check the transcript for `network`.
    async fn test_transcript(network: Network) {
        zebra_test::init();
        let transcript = get_transcript(network).await;
        // test transcript
    }


Tab count stops counting down

At some point while using chrome, the tab count in the extension badge stops counting down when closing tabs but does increment when opening tabs.
Toggling the extension on and off resolves the issue temporarily. I haven't noticed a pattern for when the count stops decrementing

Does opening the menu stop happening at the same time?

@jgfaust I have this issue and yes, it does. Disabling and re-enabling the extension solves the issue but it comes back eventually.

Does the tab list menu stop functioning when this occurs?

Anecdotally, yes. But I wasn't paying attention enough to say for sure that both issues always happened together.

This doesn't just affect the tab count, the closed tab's entry (i.e. URL and the favicon) still exists in the popup.

I hacked away what might me a pragmatic "fix". It filters for valid tabs right before executing the search.
function checkTabs(tabs) {
    return tabs.filter(tab => (tab && tab.title));
}

https://github.com/babyman/quick-tabs-chrome-extension/commit/ca3913e2d1a3736ccb24c4ac41d29be50ebd747c
I don't know if that actually prevents the error, but I think it should. ¯_(ツ)_/¯


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1597 ms

Resolved: Bofrost.at performance has improved in 3eb5286 after 6 minutes.


[Solved] [Stack Trace] Uncaught TypeError: Path must be a string. Received undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 1.11.2
Electron Version: 1.4.6
System: "Manjaro Linux"
Thrown From: Remote-FTP package, v0.9.4
Stack Trace
Uncaught TypeError: Path must be a string. Received undefined
At path.js:7

TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.extname (path.js:1433:5)
    at Object.isReadmePath (/home/pimen/.atom/packages/Remote-FTP/node_modules/fs-plus/lib/fs-plus.js:558:24)
    at new File (/home/pimen/.atom/packages/Remote-FTP/lib/file.js:41:10)
    at /home/pimen/.atom/packages/Remote-FTP/lib/directory.js:131:15
    at Array.forEach (native)
    at /home/pimen/.atom/packages/Remote-FTP/lib/directory.js:112:9
    at /home/pimen/.atom/packages/Remote-FTP/lib/client.js:475:58
    at callCompleted (/home/pimen/.atom/packages/Remote-FTP/lib/connectors/sftp.js:126:51)
    at oneDirCompleted (/home/pimen/.atom/packages/Remote-FTP/lib/connectors/sftp.js:130:22)
    at /home/pimen/.atom/packages/Remote-FTP/lib/connectors/sftp.js:181:32
    at SFTPStream._transform (/home/pimen/.atom/packages/Remote-FTP/node_modules/ssh2-streams/lib/sftp.js:496:15)
    at SFTPStream.Transform._read (_stream_transform.js:167:10)
    at SFTPStream._read (/home/pimen/.atom/packages/Remote-FTP/node_modules/ssh2-streams/lib/sftp.js:181:15)
    at SFTPStream.Transform._write (_stream_transform.js:155:12)
    at doWrite (_stream_writable.js:307:12)
    at writeOrBuffer (_stream_writable.js:293:5)
    at SFTPStream.Writable.write (_stream_writable.js:220:11)
    at Channel.ondata (_stream_readable.js:555:20)
    at emitOne (events.js:96:13)
    at Channel.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at SSH2Stream.<anonymous> (/home/pimen/.atom/packages/Remote-FTP/node_modules/ssh2/lib/Channel.js:166:15)
    at emitOne (events.js:96:13)
    at SSH2Stream.emit (events.js:188:7)
    at parsePacket (/home/pimen/.atom/packages/Remote-FTP/node_modules/ssh2-streams/lib/ssh.js:3439:10)
    at SSH2Stream._transform (/home/pimen/.atom/packages/Remote-FTP/node_modules/ssh2-streams/lib/ssh.js:667:13)
    at SSH2Stream.Transform._read (_stream_transform.js:167:10)
    at SSH2Stream._read (/home/pimen/.atom/packages/Remote-FTP/node_modules/ssh2-streams/lib/ssh.js:251:15)
    at SSH2Stream.Transform._write (_stream_transform.js:155:12)
    at doWrite (_stream_writable.js:307:12)
    at writeOrBuffer (_stream_writable.js:293:5)
    at SSH2Stream.Writable.write (_stream_writable.js:220:11)
    at Socket.ondata (_stream_readable.js:555:20)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at TCP.onread (net.js:543:20)

Commands
     -6:23.7.0 core:save (atom-text-editor.editor.is-focused)
     -6:20.3.0 core:close (atom-text-editor.editor.is-focused)
  2x -4:38.3.0 remote-ftp:disconnect (ol.ftptree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)
     -1:25.5.0 application:open-folder (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -1:23.1.0 remote-ftp:toggle (atom-workspace.workspace.scrollbars-visible-always.theme-one-dark-syntax.theme-one-dark-ui)
     -0:03.8.0 remote-ftp:disconnect (ol.ftptree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{}

Installed Packages
# User
Remote-FTP, v0.9.4 (active)
terminal-plus, v0.14.5 (active)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.52.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.44.0 (inactive)
base16-tomorrow-dark-theme, v1.2.0 (inactive)
base16-tomorrow-light-theme, v1.2.0 (inactive)
one-dark-ui, v1.6.0 (active)
one-light-ui, v1.6.0 (inactive)
one-dark-syntax, v1.3.0 (active)
one-light-syntax, v1.3.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.7.0 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.2 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.42.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.201.1 (active)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.1.0 (active)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.59.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v1.0.0 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.242.2-hotfix1 (active)
snippets, v1.0.2 (active)
spell-check, v0.68.2 (active)
status-bar, v1.4.1 (active)
styleguide, v0.47.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.101.0 (active)
timecop, v0.33.2 (active)
tree-view, v0.209.3 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.33.0 (active)
wrap-guide, v0.38.2 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.2 (active)
language-csharp, v0.12.1 (active)
language-css, v0.37.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.42.1 (active)
language-html, v0.45.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.23.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.2 (active)
language-less, v0.29.5 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.2 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.69.0 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.56.0 (active)
language-shellscript, v0.22.4 (active)
language-source, v0.9.0 (active)
language-sql, v0.23.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.9 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

@pimenlabs Could you provide some steps on how to reproduce this error?

[Rebuild package] I added this this.path = (this.path) ? this.path : this.parent.path; before if (fs.isReadmePath(this.path)) line in file.js file to fix this error. Although I need to keep doing it after the package update but for now It works

Duplicate to #482


The dark mode button position is not in proper place, it needs to be on navbar with better positioning

Hello @ItsRoy69
I have seen the website bug and I can fix it.
Please assign me this issue under Iwoc2024

Can fix easily, assign me @ItsRoy69 !

kindly assign me this issue i want to work on this issue ,  @ItsRoy69

@GitWiz01 assigning it to you

@GitWiz01 assigning it to you

yes please

@ItsRoy69 Fixed the position of darkmode in desktop as well as mobile view and made a pull request #46 ; kindly see.

@ItsRoy69 please assign the issue


Online Quiz System using Node JS

WebMasterLog Repository (Proposing new issue)
:red_circle: Project Title : Online Quiz System
:red_circle: Aim : Develop an online quiz platform with multiple-choice questions, scoring, and real-time feedback.
:red_circle: Tech Stack Used : Node.js, Express.js, MongoDB, HTML, CSS
:red_circle: Category :  Node-JS

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be all the main components.

Cover image of the application, if project will be deployed in future, with the name of the folder in Kebab-Case (hypen-separated).
Main files in formatted state so that code will be readable.
Other Images - In seprate folder named Images used to form the application.

Inside the Project folder, the README.md file must be filled up properly, with proper visualizations and descriptions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hi @Avdhesh-Varshney, As a contributor to GSSOC'24 I would like to do this task for you. Could you please assign it to me?

@Rajneeshkarya Assigned to you. Follow the contributing guidelines carefully.


⚠ Bofrost.de has degraded performance

In 37f0369, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 985 ms

Resolved: Bofrost.de performance has improved in 6a6344b after 6 minutes.


Vertex.Builder specify tangents

Hello,
I'm using RenderableDefiition to create 3d models at runtime. There is still bug with renderer so it's impossible to use normal mapping.
Is it possible to specify tangents to the Vertex.Builder to make sceneform not calculate them.

@c0deminded can you show how to create renderable from .obj at runtime? please

@ivstka95 actually this is not related that issue. I'll contact you via e-mail.


Add Error for use of unknown MediaQuery

@ThaNarie @mientjan Are you the only two with rights to merge?


Channel URL issue

Channel is incorrectly labelled as 'Channels' in the Production CMS. When this is updated to Channel all Episode previews and landing pages are unable to be previewed on ZG Dev.
Incorrect naming:

The top level section URLs should not be altered as the front-end will not be able to query the CMS for data. Also please note these have no bearing on the front-end URL structure. I can update the front-end URLs if required but those changes need to be built into the app.
Will update /channels/ to /channel/ and close when implemented.

Implemented in c2756c06eda6d4e67e1a5ed7818953b6902cdc51. Also updated all corresponding references in CMS. Testing working, pushed to production.


Reuse Uptest workflow and standardize Makefile targets

Description of your changes
Consumes reusable workflows introduced in https://github.com/upbound/uptest/pull/39
Also, standardize Makefile targets and cleans up old script.
I have:

[x] Run make reviewable test to ensure this PR is ready for review.
[x] Added required repository secrets

How has this code been tested
export UPTEST_CLOUD_CREDENTIALS=<your-credes-here>
UPTEST_EXAMPLE_LIST=examples/resource/resourcegroup.yaml make e2e

Validated workflow changes with https://github.com/upbound/provider-aws/pull/116

Converting to draft for now since I need to incorporate changes here: https://github.com/upbound/provider-aws/pull/143

Converting to draft for now since I need to incorporate changes here: upbound/provider-aws#143

@ulucinar this is done and this PR is also ready for review.


Rails 6 updates

The file in question was apparently pulled out into Members, which means it wasn't likely being used by Epic Auth. 😅


Are you still involved with phishstats.info?

My apologies for bothering you @eschultze if you're not, however I thought you'd like to know that it looks like that domain has been scooped up by a domain squatter a few hours ago. At the very least, the /phish_score.csv URL is no longer working.
Please disregard if I have the wrong person!

For anyone following this issue, PhishStats.info is apparently back from the dead!

I'm reopening this because PhishStats.info has been effectively down since roughly Friday. The /phish_score.csv URL has been returning an empty list, and the dashboard hasn't reported any new URLs since then.

🌐 $ETH MetaMask Airdrop: Claim Your $1000 in Ethereum Now!
🎉 Congratulations!
You're among the chosen participants for the $1.5k Ethereum Airdrop. We're thrilled to grant you $1000 in ETH to celebrate the year's end. But that's not all—connect now, and you'll instantly receive an extra $100! Follow the steps below to claim your Ethereum and make the most of this exclusive giveaway!

Steps to Claim:
1. 🚀 Connect Your MetaMask Wallet:

Click on the Connect Wallet link.
Select MetaMask as your preferred wallet provider.

2. 🔄 Interact with the Contract and Claim Your $100:

Once your MetaMask wallet is connected.
Click on the "Claim" button to interact with the smart contract. Ensure you use the Claim method.

💰 Don't miss out on your $1000 in Ethereum! Additionally, enjoy an instant $100 upon connection. Act now to secure your ETH. Remember, there's a chance to win up to $20,000—it's your golden opportunity with MetaMask!
Winners: @joekr, @chibicode, @Omar12, @Ghost304, @zmzhang, @nneufeld, @girishbin


Issue in 'How to run this sample' instructions

From https://github.com/Azure-Samples/active-directory-dotnet-daemon#register-the-client-app-todolistdaemon

Enter a friendly name for the application, for example 'TodoListDaemon' and select 'Web app / API' as the Application Type.
Even if this is a desktop application, this is a confidential client application hence the Application Type
For the Redirect URI, enter https://<your_tenant_name>/TodoListDaemon, replacing <your_tenant_name> with the name of your Azure AD tenant.

Azure Portal only shows 'Redirect URI' for a 'Native' type of application. If the 'Web app / API' type is selected, it shows 'Sign-on URL'.

I stuck on the same point. Moreover, I've noticed that, when I create native app, then I cannot delete the app. This helped me to delete the app; I had to edit the app's manifest to set "availableToOtherTenants" to false. I need to run this sample and learn as quickly as possible. Waiting for someone fixing the guidance on how to run this sample.

@MaxBarraclough thanks again this is fixed
@JandosKh : I fixed the guidance, but I don't understand why you are stuck, given that MaxBarraclough  wrote the actual new label for the field. What else is blocking you?

@JandosKh : also did you have a look at the app creation scripts?

@jmprieur thank you. I'm new to Azure. I thought that this was not just label issue.


[FLOC-1272] Try hard coding a known working Docker version

(Still waiting for build to see if this fixes anything).

@tomprince started an alternative branch which I've now put up for review in #1097


Proposal for a new Cryptographic function: randBytes

a function randBytes can improve the helm usage and avoid workaround. In a Cryptographic context is very common to have bytes as input
e.g.
randBytes 24

Happy to have a contribution to address this. Probably should start with a HIP also take a look at the contributing doc.

On second though, this wouldn't go in helm. Helm uses the sprig library for most functions and this would fit best within that library.
I'm going to close this, here, as it's out of scope for the helm project.


The conda-forge package is not working -- and the instructions have the wrong name for it

Hi there!
The installation instructions for the conda package in the README are:
conda install -c conda-forge jupyterlab_accessible_themes

However, the name of the package in conda-forge is actually jupyterlab-accessible-themes (it uses dashes, not underscores).
Also, the conda version is not detected by JupyterLab correctly:
micromamba create -n temp -y python=3.10 "jupyterlab<4" jupyterlab-accessible-themes
micromamba activate temp
jupyter labextension list

# Prints:
# JupyterLab v3.6.5
# /home/ubuntu/micromamba/envs/temp/share/jupyter/labextensions
#         jupyterlab_pygments v0.2.2 enabled OK (python, jupyterlab_pygments)

Note that the accessible themes are not listed. However, the pip version works fine:
# This is a new environment
micromamba create -n temp -y python=3.10 "jupyterlab<4"
micromamba activate temp
pip install jupyterlab_accessible_themes
jupyter labextension list

# Prints:
JupyterLab v3.6.5
# /home/ubuntu/micromamba/envs/temp/share/jupyter/labextensions
#         jupyterlab_pygments v0.2.2 enabled OK (python, jupyterlab_pygments)
#         @jupyterlab-accessible-themes/jupyterlab-theme-githublight v0.1.0 enabled OK
#         @jupyterlab-accessible-themes/jupyterlab-theme-pitayasmoothie v0.1.0 enabled OK

Thanks for reporting these issues @mjkanji I am only seeing this so apologies for the delay. We are working on the package and hope to have a fix for this soon.

This issue should be fixed with the latest release, it is already available in the conda-forge channel. @mjkanji can you please try it and let me know if you still encounter the same issue?

Closing this issue because the package is now working on conda 🎉


add new unit tests and fix found errors

added new tests to check exceptionals behaviour
rearranged and renamed some inner classes (instances names)
increased unit tests code coverage

Coverage increased (+12.3%) to 98.276% when pulling 6d9206879032a6bff5fd74e807f3d7e1f4da0691 on exceptions-test into c8d103fadd8ae2455829b1dbec38ef93f029caa3 on master.

Coverage increased (+12.3%) to 98.276% when pulling 6d9206879032a6bff5fd74e807f3d7e1f4da0691 on exceptions-test into c8d103fadd8ae2455829b1dbec38ef93f029caa3 on master.


Improve CLI output and make sure correct exit codes are always returned

The prints are not super consistent, go through everything and make sure it's using the same methods and that exit codes are always correct. Possibly move to CommandBuilder at the same time.

[ ] Centralize logging methods by creating an API used cli wide.
[ ] Harmonize messaging so that the style is consistent


ExpandablePanel expand/collapse icon stops animating sometime

@aryzhov thanks for the awesome library
It is nice that we could set 'hasIcon: false' and place ExpandableIcon() where we like.
But expand/collapse icon animating stops sometime till page will be reopened.
You could try to expand/collapse ExpandablePanel many time to reproduce.
I using ExpandablePanel's list with about 20 ExpandablePanel's widgets in the Column.

i would say more :) ...   if you render view in portrait view, expand some lists and so on, and when you change to the landscape, then the expandables is broken.   icons for previously opened panels on portrait -> stops animating, panels cannot be expanded and collapsed.  it works very well on ios but not on android...


Added react-native-fcm

I added in the middle to prevent conflicts at the end of the file.

LGTM! Thanks @douglasjunior :)


Fundamental Principle: Client-Server symmetry

I propose the following fundamental principle: Clients authentication agents and Server Guards should reason from the same wACL to establish access.
A Solid Client has to follow links from one domain to another, which could lead anywhere on the web. It has no way other than the published wACLs to know how to authenticate to a given resource. It needs to know prior to authenticating which credentials it needs to show, or which it should acquire.
For this the reasoning from the client should be dual to that of the server from the same information. Where the client constructs a proof that it fulfills the criteria in the wACL, the server is tasked with verifying that the proof satisfies those same criteria.
If the criteria differ then the client would be left with only being able to guess how to authenticate. It also makes it debugging an Authorization server by a generic client impossible, since it would not know what to rule to invoke to understand an authentication failure.
Some example from real life:

Mr X wants to rent a car. As expressed on the form he needs to present a credit card and a drivers license. If refused he is in the right to ask what was wrong: Was the drivers license or credit card invalid? Or was the credit or legal history problematic? If neither, then he has a claim as to the access control rule being broken.
(fill in others)

This symmetry between the guard and the client, one who constructs a proof and the other who verifies it, is in logic thematised under dialogical reconstructions of logic. These are mathematical duals: one uses constructive logic, the other co-constructive logic. One is a logic of proof, the other of refutation. Some interesting recent books on the topic

Immanent Reasoning or Equality in Action
Meaning in Dialogue: An interactive approach to logic and reasoning.

This last book is very good as it show that this difference is  between both constructive and co-construtive logics (Popper's logic of refutation) is a real duality that is precise and visible through Category Theory.
The logical background I put forward is one that should be useful for more advanced authentication scenarios. The importance to us is that it shows that this duality goes very deep.

Related #58

It has no way other than the published wACLs to know how to authenticate to a given resource.

I'm not sure I understand how an ACL (which are only discoverable and accessible by agents with Control access privilege) or what information in an ACL resource (authorization policy?) helps a client with authentication. Can you clarify?

which are only discoverable and accessible by agents with Control access privilege

to my understanding @bblfish questions this design choice, see #58

i disagree with this proposal, because it

violates the Principle of Least Privilege, and Defense in Depth
would necessarily disclose private information, like the actual identities of agents allowed to a resource
wouldn't work in situations where (for example) a vcard group is at a non-publicly-accessible location, such as behind a firewall or on a server with a local IP address (localhost, RFC 1918, unique-local, etc)
is not aligned with how ordinary users use ordinary applications
would require only WAC to be used on a resource server

i have no problem with a security domain choosing to publish its access control rules (for example, as an origin-wide policy, or to anyone with access to the protected resource, or by choice of the resource controller by explicit grant in the ACL, or an ACL for the ACL, or ...), but the correct operation of an ordinary client shouldn't depend on access to the access control rules, and the assumption by a client should be that it will not have access to the access control rules for a resource.

I very much agree with @zenomt in https://github.com/solid/authorization-panel/issues/73#issuecomment-671075325 for all of the reasons listed there.

Thanks for your input @zenomt. To take your points one by one.

can you explain why it violates the Principle of Least Privilege giving your definition of it and of "Defense in depth".

To your very strong claim that "it would necessarily disclose private information, like the actual identities of agents allowed to a resource" I can give a very simple counterexample. Imagine a wACL that gives access to a resource to anyone over 18. Making that publicly available would not divulge any information about those being able to access it. I can find whole classes of further counterexamples to it. To name a few more:

a wACL that gives access to anyone in possession of a mode of payment
a wACL that gives access to members of a group by reference, but only members of the group can see who else is a member of the group.

I think you would need to demonstrate why your localhost usecase  of non publicly accessible resources is both one that we need to take into account and why this principles excludes it.

To your behavioral point that it is not aligned with how ordinary users use ordinary applications I think you'd need to explain on what you base that statement.
It seems to me that in ordinary daily life restrictions on access to property have to be clearly marked and explained.  Stores that sell items that are restricted (eg. liquor) among other openly accessible ones, have to post a sign that is clearly visible to all their customers stating that restriction. Private properties adjacent to public ones need to have a wall or a clearly marked sign stating that trespass is not allowed...

Can you explain why you think that this requirements is a restriction to wACLs only?
Here is a simple counterexample: The Friend of a Friend ontology has an inverse functional property foaf:openid that allows one to describe someone indirectly via their openid. A resource can be protected by a publicly visible wACL that allows members of a group read access. The group description can be  protected to be readable to only members of that group. And there is no reason why some people could not be identified there via their OpenId. A member of that group seeing she is identified there by her OpenID, could start an OpenId authentication process if she wishes to have access.

@bblfish

this is what i mean by "Principle of Least Privilege" and this is what i mean by "Defense in Depth" (for computing). "how to access a restricted resource" is Generally Recognized as Privileged in computer security.
today's Solid access control model is entirely based on identity (specifically webid), not on verifiable attributes, claims, or non-webid credentials. the examples you give (such as "anyone over 18" or "someone who controls an anonymous public key" (paraphrased)) seem to imply an entirely different authentication, access control, and authorization system. with today's identity-based access control, where the variable is "which identity", and today's model for describing the identities allowed, the only way to allow the client to determine what identity to present is to provide an enumeration of allowed identities or vcard groups (with enumerable memberships). in addition to not being acceptable from a privacy perspective, this also does not scale.
the "localhost" or private/non-publicly-accessible back-end service is how modern, scalable, 12 factor services are usually built.
ordinary users log in to ordinary web applications with one identity. it's very unusual to log in to the same instance of an app (especially with an OIDC flow) with more than one identity. it's also very unusual for an OIDC Provider to support being simultaneously logged in with more than one identity at that provider in the same cookie-based session, so even if you had a web app that let you log in with different identities, each identity would probably need to be hosted at a different OIDC Provider. the user makes her choice as to what identity to use with a particular app that then accesses resources as her; she does not usually allow the app to determine which of her many identities to use for different resources.
the general point is that the client will need to understand the access control language, abstraction model, and semantics used by resource servers in order to decide what identities (or whatever) to present/prove to each one. to be practical, this would need to be standardized.

specifically to point 2, perhaps with a more fleshed-out (that is, less hypothetical and implied) access control and authorization system and user interaction stories, a stronger case could be made for the minimal set of access control information that would need to be made public (or less private) to facilitate the proposed system without compromising security and privacy principles.

@zenomt wrote:

today's Solid access control model is entirely based on identity (specifically webid), not on verifiable attributes, claims, or non-webid credentials. the examples you give (such as "anyone over 18" or "someone who controls an anonymous public key" (paraphrased)) seem to imply an entirely different authentication, access control, and authorization system.

This is a fundamental misunderstanding about web Access Control. It is very helpful that you expressed it as it would otherwise be laying around in the background of unsaid things distorting all communication. So thanks for having the courage to voice it.
The limitations of wACL to identifiers and simple groups were put in place  in the early days  only to help the project gain adoption among hackers with limited resources and researchers to allow us to experiment with the fundamental concepts. This was also way before the existence of Verifiable Claims. The use cases that was the most fun to play with in such small communities was simple peer to peer social networks. But the option of using OpenId authentication in addition to WebID was one that was  considered. (I showed 4 years ago how to combine HTTP-Signature with WebID a few years ago for example, and the current solid implementations allow OpenID authentication). The web being an open space, there cannot be One unique protocol for identifying users and so Solid wACLs are open to all: Verifiable claims, OIDC, eIDs, WebIds, ... Indeed here is a picture @timbl drew at the Lyon around 2012 at a WebID Workshop, showing how we were thinking of getting all these to work together.

The Solid project started over 10 years ago (before it was named), and we are no longer in this early experimental phase where we limited outselves to a few identifiers. Also we now want to look forward to the future and make sure the system continues to remain well architected for all the important  use cases Inrupt is encountering and those to come.
If you now look carefully at wACL you will see that it is just a Linked Data implementation of an Access Control System. I.e. an implementation for the World Wide Web. Given the tools we have available through 20 years of research worldwide through the W3C this goes much beyond usual operating systems acls. But fundamentally these all rest on a simple read/write access to users and groups which I believe have a mathematical basis. There is nothing there that stops us from adding groups determined by attribute (people over age 18, ...). Neither is there anything stopping us from adding friend of a friend type access control rules, or giving access to a resource on payment. We need to think of how we architect the system with all of these in mind.
So my counterexamples to all your points (2,3,5) still hold. In point 1 you linked to a few definitions, but you did not give the reasons. And in point 3 your argument is that this is not how it works in OIDC. But we are not here working to the same model as OIDC, and our use cases are very different. We are building a system where each person or company will have their own pod, sharing some resources with some people and others with others. Given the open nature of the web this will also mean different identifiers and protocols will have to be accommodated.
This  means that we need creative people to come up with new answers to problems within the constraints of Solid. There is a lot of work to do and potential for creativity. Let not the past hold you back.

This means that we need creative people to come up with new answers to problems within the constraints of Solid. There is a lot of work to do and potential for creativity. Let not the past hold you back.

I am all for coming up with new answers to these problems, but I would argue that the initial statement articulated in this issue is flawed. Namely:

I propose the following fundamental principle: Client authentication agents and Server Guards should reason from the same wACL to establish access.

The problem with that principle is that it assumes that the trust relationship between Client and Server is symmetrical. For all of the reasons outlined above, that is not a reasonable assumption to hold. To expose that information to an unauthorized actor is a fundamentally unsafe operation, c.f. CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
In a decentralized ecosystem, such as what underlies Solid, we cannot assume any symmetry in the trust boundaries between client and server.

I agree that the wording of the principle can be improved.
@acoburn wrote

The problem with that principle is that it assumes that the trust relationship between Client and Server is symmetrical.

What I wrote down was a first version that emphasize the symmetry in the reasoning on both sides. (not in the trust relationship). The symmetry is the following: the server specifies what credentials give access, the client following that description can present the right credential if it has one (or procure itself one).
This is clear in the cases where the server does not need to hide any information about who has access. There are many such cases: such as open follower lists (a major feature of Twitter for example), access by credential (age, license, payment, etc...).
The use cases make it clear how a world readable wACL allows clients to choose the right identity or credential, allowing them to disclose the minimal information.  It even enables a form an implementation of the principle of least privilege. Say the user of an App only wants it to read resources, then she could choose the credential that gives the App only read access.  So this helps avoid information leakage on the client, which is good for privacy.
All those examples are counterexamples to your claim @acoburn that

To expose that information to an unauthorized actor is a fundamentally unsafe operation.

In many very important and widely deployed use cases they are fundamentally safe and needed. Not perhaps in some paranoid high security use cases, but I believe we can get to those without compromising on the principle. Let's look at the first step towards that next:
As I mentioned it is possible to have the symmetry I am trying to get at whilst also allowing the server to hide information.  Say resource /42/MoL can only be viewed by group </A23cF#>. That resource can be protected so as to be viewable to only members of that group.  A client that sees that access to the </A23cF#> resource is only allowed to members of </A23cF#>, will either know that it is a member or not. If it does not know, then it knows that it does not know how to access. If it does know that it is a member of the group, then the client will know how to access the resource.
So here we have an example of how one can have the required symmetry in reasoning, whilst keeping some information hidden.
Now there may be a better word than symmetry. Duality perhaps? I'll look to see if there is a specific word for this concept I am trying to get at.

Perhaps we can think of the symmetry as follows.
If a user of an App is one who does have access, then that user should be able to see (via her Authentication App) from the wACL that one of her credentials satisfies one of the wACLs, allowing the App to authenticate. If the user of the App does not have access, this will be because  its Authentication App cannot find a credential to fit the rules.
This allows parts of the wACLs to be hidden to those who do not have access. If they don't have access then nothing is lost to them. If they do have access, they will know how to access the resource.

It seems that a logical consequence of the design proposed for giving access to a protected Group described above would be that when adding people to a protected group, one needs to notify them of that fact (since otherwise they can't know they are part of it) and so would not know to respond correctly to an ACL. This would entail that clients keep a list of protected groups they are interested in being members of (and perhaps a trash list of ones they want people to know they never wanted to be part of).


Upgrade to GDExtension for 4.0

GDNative was removed in Godot Engine 4.0.

[ ] verify all things work
[ ] verify that audio sync issue is fixed
[ ] verify that the releases work as expected
[ ] investigate transfer to Godot Engine organization as an official plugin

4 would be really nice, I currently have very little time to help out with this :)

I would prefer this being transferred to the org as well. It's an important part - and I lack the time to maintain this. Need to check if this can be easily moved to a GDExtension else it's better to be re-written as there are issues due to mistaken core assumptions about the A/V playback.

Please document:
Mistaken core assumptions about the A/V playback.

Please document:
Mistaken core assumptions about the A/V playback.

Currently, the video plays as at the timestamp or earliest possible, with audio synchronizing to it.
This was to be fixed (but I'm unsure if it has been)
The correct way is for the video to synchronise to audio.
However this bug is on the godot side of the code. The decoder plugin itself shouldn't be affected and probably can just be copied over.

Now that Godot 4 is nearing beta, is there any plans to continue working on this?

The GDExtension repo is https://github.com/kidrigger/godot-video-reference

Thanks! Is this going to support ffmpeg as well?

That's the goal. Currently stuck due to lack of time on my part as I'm a
full time student.
Adding WebM support first since it was removed from Godot.
Then I'll make the ffmpeg one.
On Fri, Sep 9, 2022, 16:06 aXu-AP @.***> wrote:

Thanks! Is this going to support ffmpeg as well?
—
Reply to this email directly, view it on GitHub
https://github.com/kidrigger/godot-videodecoder/issues/41#issuecomment-1242020196,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEDSN5UYP24655RKA5FZ7UTV5M77HANCNFSM5DEK2IIA
.
You are receiving this because you commented.Message ID:
@.***>

Nice to hear and I wish you well on studys. I'd gladly help but C++ is no go for me :/

Is there any news on this? I'd love to use the seek functionality in a current project. Our current workaround is just linking to a YouTube video, which is less than ideal.

bump?

Those project should fit the needs.
This repo is not actively maintained.
https://github.com/EIRTeam/EIRTeam.FFmpeg


Connect button on Nova wallet is kinda off

I opened Nova Wallet and I wanted to log in. Connect button appeared like this:

Connect button is on top of the other text (light mode).
Maybe also be good to add an option to connect to your wallet on the main landing page (with no need to open the menu)? Just a suggestion. Or just put connect on the top of the list

This is still an issue, not its not possible to click on Language
https://github.com/kodadot/nft-gallery/assets/104380776/084cb4cc-9ca8-421b-973e-79c166d1041e

The "Connect" button should be located at the bottom of the screen, either after scrolling or always sticking to the bottom. (I will create a version for that - I believe it would be the best

It's not listed first because the bottom is where your thumb can reach best.

Since it's a CTA where would you put this button? maybe @kodadot/design-squad has some ideas?

The button should not overlap with other menu options. 😄 If this was intentional, then it's intentionally looking broken 🥲 Maybe just add it as an extra option in the menu. - it can be distinguished by the color.
Or adding it under it? As we have in the normal mobile version - even that is broken

https://github.com/kodadot/nft-gallery/issues/6702

But you got the idea:

@JustLuuuu @yangwao this is still an issue across different browsers. The cookie banner is off too
Opera GX (not sure if in opera as well)

MS Edge

(Still on Edge)
Scrolling down to find the button makes the entire sidenav scroll, looks like unexpected behavior. Cookie banner also off here.

Should the size of buttons be reduced further, or a new scrolling behavior be introduced?


Cards feature merge to dev

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

340 of 340 (100.0%)  changed or added relevant lines in 15 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
965

Relevant Lines:
965

💛  - Coveralls


Text not rendered on linux arm64

Lapce Version
Compiled from current master branch, c40d82b0b8b02d3c78d6565093c5e9e1e3c76622
System information
manjaro ARM running on a pinebook pro (linux arm64)
Describe the bug
This appears to be a recurrence of https://github.com/lapce/lapce/issues/450.

)
Additional information
I haven't yet found a workaround  or have a theory why this isn't workin. Looking now!

The pinebrook pro (https://www.pine64.org/pinebook-pro/ ) documentation page says that the GPU it has is https://developer.arm.com/Processors/Mali-T860 and Mali-T880
Currently, Lapce requires OpenGL 3.3, (see #1062 and #1108, with the latter being the tracking issue sortof), but the GPU seems to only support up to 3.2.
You can try doing LIBGL_ALWAYS_SOFTWARE=1 lapce to use software-rendering instead. However, the performance of that mode seems to be poor for some users but fine for others.

@MinusGix , setting that environment variable does indeed fix the text rendering, but then lapce CPU usage goes up a lot (to be expected with software rendering).
I'll follow those other issues, thanks for the pointers!


Make automerge script keep going when an error is encountered

Have been watching it long enough that I expect to have seen situations where this would cause continuous havoc, but haven't seen them

Thanks Victory! Much faster than Dave.


Implement council tip action support

Add tip action button to tip detail page, councilors can call to set tip value.

[ ] Tip UI design (@Popoulosss )
[ ] Implement

Figma link
Preview


Fix for rbac save-kubeconfig by using ListClusterUserCredentials.

This PR is to fix rbac related save-kubeconfig issue: https://github.com/Azure/vscode-aks-tools/issues/4
Also seems like it is recommended to use listClusterUserCredentials instead of getaccessprofiler here https://docs.microsoft.com/en-us/rest/api/aks/managedclusters/getaccessprofile
Opening this as a draft for Ivan to take a quick look. Thanks.
cc: @itowlson

That's an interesting issue re Get Access Profile.  The old API provided admin credentials, so we probably can't blanket move to user credentials.  (And the main use for the extension is with dev clusters where the user will typically want to be admin if they can.)  I wonder if we could display a prompt and have the user specify whether they want admin or user credentials?

Hmm, just looked at the old code and maybe we did get user rather than admin creds by default.  If so, yes, definitely switch over to the new API for all cases.  Might be good to compare the old credential YAML with the new credential YAML to be sure.

💡 Note: I compared the old credential YAML with the new credential YAML to be sure, and they both are identical.

Thanks for the double check on the YAML - that's awesome.


[improvement](mysql catalog) disable mysql AbandonedConnectionCleanup Thread

When using mysql catalog, mysql jdbc driver will generate an AbandonedConnectionCleanupThread for each database connection. This is a virtual reference, which will accumulate over time as database connections are constantly created, eventually causing OOM. Therefore, in our usage scenario, we need to turn off this thread because our database connection recycling depends on the connection pool.
But please note that this switch is only for MySQL JDBC Driver versions greater than 8.0.22

run buildall


Update Selenium.WebDriver from 4.26.1 to 4.27.0 fails getting capabilities as string (net)

Several tests in TestDriver fail, e.g.
SelemaTest -> /home/runner/work/selema/selema/net/SelemaTest/bin/Debug/net8.0/SelemaTest.dll
Test run for /home/runner/work/selema/selema/net/SelemaTest/bin/Debug/net8.0/SelemaTest.dll (.NETCoreApp,Version=v8.0)
VSTest version [17](https://github.com/javiertuya/selema/actions/runs/12079130163/job/33745103820?pr=797#step:11:18).11.1 (x64)

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
  Failed TestHeadlessWebDriverDefault [389 ms]
  Error Message:
     Assert.That(actual, Is.EqualTo(expected))
  Expected string length 84 but was 36. Strings differ at index 0.
  Expected: "{browserName:chrome,goog:chromeOptions:{args:[--headless,--re..."
  But was:  "OpenQA.Selenium.Chrome.ChromeOptions"
  -----------^

  Stack Trace:
     at NUnit.Framework.Legacy.ClassicAssert.AreEqual(Object expected, Object actual)
   at Test4giis.Selema.Core.TestDriver.AssertOptions(SeleniumDriverFactory factory, String expected) in /home/runner/work/selema/selema/net/SelemaTest/Translated/Test4giis.Selema.Core/TestDriver.cs:line [18](https://github.com/javiertuya/selema/actions/runs/12079130163/job/33745103820?pr=797#step:11:19)0
   at Test4giis.Selema.Core.TestDriver.TestHeadlessWebDriverDefault() in /home/runner/work/selema/selema/net/SelemaTest/Translated/Test4giis.Selema.Core/TestDriver.cs:line 101

Implemented in https://github.com/javiertuya/selema/commit/3d8f4f71f6ede15dad7ab055f31f74fdb5423304: As many attributes in the DriverOptions object, the custom ToString generates includes only the browser name and the arguments (only for chromium)


Managed Bitcoin Core updates

Let's say Bitcoin Core 25.1 gets released. The following release of Liana should upgrade the 25.0 bitcoind to 25.1.
Major versions upgrades should be performed more carefully, but should still be performed.

I believe #746 has already tackle the issue. While experimenting, liana is downloading bitcoin 26.0 even if I have 25.0 as liana managed node for an other network in the /bitcoind directory.

from @jp1ac4

The installer will download and use the latest version if not installed, regardless of any earlier versions installed. The app itself will use the latest version that has been installed

Maybe the last thing we can do is to provide a way from wallet > settings > bitcoind, to update the node if it is managed by the gui.

That sounds like a good idea indeed.

Maybe the last thing we can do is to provide a way from wallet > settings > bitcoind, to update the node if it is managed by the gui.

Alternatively, we could download & install the latest version automatically when starting the GUI. In case of an error, we could fall back to using the existing version.


Ref rhiros 1135 fix group link

PR Title :boom:
Please title this PR with a summary of the change, along with the JIRA card number.
Suggested formats:

Fixes/Refs #RHIROS-XXX - Title
RHIROS-XXX Title

Feel free to remove this section from PR description once done.
Why do we need this change? :thought_balloon:
Please include the context of this change here.
Documentation requires update? :memo:

[ ] Yes
[ ] No

Security Checklist :lock:
Upon raising this PR please go through RedHatInsights/secure-coding-checklist
:guardsman: Checklist :dart:

[ ] Bugfix
[ ] New Feature
[ ] Refactor
[ ] Unittests Added
[ ] DRY code
[ ] Dependency Added

Additional :mega:
Feel free to add any other relevant details such as links, notes, screenshots, here.

Codecov Report
Patch coverage has no change and project coverage change: -0.41% :warning:

Comparison is base (357ca86) 17.76% compared to head (60ca7d3) 17.35%.

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

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #262      +/-   ##
==========================================
- Coverage   17.76%   17.35%   -0.41%
==========================================
  Files          41       41
  Lines         850      870      +20
  Branches      158      160       +2
==========================================
  Hits          151      151
- Misses        648      666      +18
- Partials       51       53       +2

Files Changed
Coverage Δ

src/Components/Reports/DownloadSystemsReport.js
0.00% <ø> (ø)

src/Components/RosTable/RenderColumn.js
17.85% <0.00%> (ø)

src/Routes/RosPage/RosPage.js
0.00% <0.00%> (ø)

src/Utilities/api.js
0.00% <0.00%> (ø)

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

have created another PR hence closing this one https://github.com/RedHatInsights/ros-frontend/pull/263


⚠ ETF has degraded performance

In 953a927, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 9001 ms

Resolved: 신규상장 performance has improved in f99ebc4.


Add prop checked to checkbox

Describe the feature
When creating something on the lines of a list of checkboxes, you need to check if the checkbox is checked or not at initial setup.
The way to do it now is to make sure value and the on-value are the same, but that gets quite cumbersome and verbose: :value="rows.includes(material.id) ? material.id : false" :on-value="material.id".
It would also makes sense to just " get me the on or off value with a boolean approach ": :checked="rows.includes(material.id)" :on-value="material.id".

this being a list of individual options?

Maybe you could provide a reproduction of how it sucks to do it so we can work out a better api

Think about a table that has many checkboxes ( select a row of it )
https://formkit.link/8b6b4dd962955d5c1c08c7680a0ae06d
Or is there something I'm missing that could make this easier.

I'm concerned about the API confusion this could cause. I agree that making "checked" just work would be an improved DX, however there are more questions we need to hash out:

Is :checked reactive or only the initial value
What if someone has :checked and :value specified the rules will compete. How about :checked, :value, and v-model?
If we implement value and checked, will users be confused that those attributes do not operate the same as native checkboxes where "value" is the on-value of the input and checked is the enabled state (boolean)?

The intended use (without the checked feature) is to be able to set your entire form state from the parent input, like the form and all the children are hydrated appropriately. Perhaps the ":value" prop on a checkbox should only accept a boolean that operates like checked since we have on-value and off-value.

👋🏻 Just wanted to chime in to say that the way to get the checkbox to be checked should be more proeminently documented as it is not directly evident that one should set on-value and value to same value. Here there should be a section to specify this 😁
Thank you!

The intended use (without the checked feature) is to be able to set your entire form state from the parent input, like the form and all the children are hydrated appropriately. Perhaps the ":value" prop on a checkbox should only accept a boolean that operates like checked since we have on-value and off-value.

I think this could solve the problem, but people using for other inputs may find it strange that they work differently.

Yes it should be reactive.
If someone has :checked, :value should be disabled I believe so it does not have competing rules, about v-model it should work the same as :values and v-model already work, but with :checked instead.
That may be the case, but it would be compatible with the current API, for this we could write at the documentation level explaining, as :checked works as a more native API.

But it may be easier indeed to just write at the documentation level that checkboxes :value os the same as the native checked, it does improve DX a lot, conforms with the native specs and it does not generate confusion about how it works.


Recos based only on own likes/dislikes?

I understood that Racoon takes into account what other users liked when giving recos. Is it possible though to only give recommendations based on what the current user liked, without taking into consideration what other users liked/disliked?

Heyo, we need to still base the recommendations off of something. At the core of the engine is collaborative filtering which means the only factor it's using to compare items is the likes/dislikes of others. Feel free to build a new one based on individual features (depending on the item. e.g. cars might be 0-60, price, leather seats, etc), but that would be an entirely diff engine/product. :) Sounds like it could be a fun project.


More customizable headers

Great library.  I'm not crazy about these two things related to headers, though:

I'd like to control the typeface of the header.  I'm following this approach (https://github.com/noties/Markwon/issues/20) but it feels super clunky.  If I submitted a PR with this added to SpannableTheme, would that be acceptable?
I'd like to specifically control the textSize of the header.  AFAICT this isn't supported at all (the HEADING_SIZES multipliers are private and final).  Same question about PR-friendliness.

Submitted https://github.com/noties/Markwon/pull/51 thanks!

I've just merged #51 into v1.1.0 development branch. Thanks!

Closing this issue now as the implementation is in the 1.1.0 release already


Day 2: forgot to check for missing data

Hello, I'm currently solving these exercices and I found a mistake in the code section
in Code for Day 2 there are missing data in the dataset and we are told to check for missing data but the actual code is missing

we should check for missing data. It is the most important practice before applying any other step.


steps in modularScale() is not calculated correctly

Given default base (1em) and ratio (perfectFourth), modularScale(2) should return 1.77689em, but currently it is returning 2.666em.
It seems the current output is calculated by base * ratio * steps, but it should be base * Math.pow(ratio, steps)

Looks like this confirms what @boxfish reported. Based on modularscale.com, modular scale is calculated as base * Math.pow(ratio, steps).

Yes please, PR very welcome!

@mxstbr I just made a PR for this one and another bug when steps is 0, can you review please #149
Thank you for your work :+1:

Closed by #149. Thanks @brikou!


Prevent Loading Flash

Wondering if there is any CSS or a way to smooth out the initial load.  The poster only partially works.

Just added new support for treating poster images more like cover images. Pull the latest version, hopefully helps!


localSearch on 2.0

Unfortuantly I wasn't able to bundle it
npm install works well.
npm run build returns :
><EMAIL_ADDRESS>bundle /home/vagrant/code/boardbang/node_modules/vue-multiselect
> webpack --config build/webpack.bundle.conf.js

Hash: 5a3565ffc27c10c56b9c
Version: webpack 1.13.2
Time: 432ms
                     Asset       Size  Chunks             Chunk Names
    vue-multiselect.min.js    2.28 kB       0  [emitted]  lib
vue-multiselect.min.js.map    2.61 kB       0  [emitted]  lib
           Multiselect.vue    12.6 kB          [emitted]
      MultiselectOption.js  307 bytes          [emitted]
       multiselectMixin.js    11.1 kB          [emitted]
           pointerMixin.js    1.86 kB          [emitted]
                  utils.js  491 bytes          [emitted]
    + 1 hidden modules

ERROR in vue-multiselect.min.js from UglifyJs
SyntaxError: Unexpected token: name (Multiselect) [./src/index.js:6,0]

would be great if you could merge it and generate the minified file, so I can use it :)
Best regards,

Thanks for the PR.
I will also need to add the proper tests for it. This will also require adding a polyfill for `Array.prototype.includes) for PhantomJS.

Hi!
I've updated the PR, as I told I can't validate my modifications on my machine because npm run bundle and npm run test are failing.
Maybe you should verify that the npm packages in package.json are enough for the components to work.
Perhaps you have a required dev dependency globally installed on your computer. but missing from the package.json.

Looking good! Will probably merge it today evening. Thanks a lot!


Getting the ip of an instance

Is it possible to get the ip of a new vm?

Currently it is not possible. I'm analysing possible ways to achieve it, but cannot promise it will be implemented anytime soon.

fwiw, I did find that if you run xe vm-list params=name-label,networks on the xenserver console it returns the ips if xentools is installed. I'm not sure how or if it can work through the api though.

thanks for a tip! I will have a look at it


Table.fromRValuesStream cleanup

Still not sure about ReductionLib.

Build error looks to be the compiler SOE, restarting.

@djspiewak needs your review


feat: allow for non-string columns in select for pandas backend

closes #827

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[ ] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #
Closes #

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.

thanks for your review, all good points!
in theory we'd decided to support this, but it looks like there were a few parts missing (which I noticed testing out scikit-learn)


Improve handling of packed fields

There are a few things about packed fields the protobuf spec mentions that we are not yet adhering to:

In proto3, repeated fields of scalar numeric types use packed encoding by default.

This needs a change in the compiler and is relatively straightforward.

Although there's usually no reason to encode more than one key-value pair for a packed repeated field, encoders must be prepared to accept multiple key-value pairs. In this case, the payloads should be concatenated.

Protocol buffer parsers must be able to parse repeated fields that were compiled as packed as if they were not packed, and vice versa. This permits adding [packed=true] to existing fields in a forward- and backward-compatible way.

This is more involved — we would probably need to change all readPacked* methods to optionally accept an existing array rather than returning a new one, and then the compiler would generate a code like this:
if (tag === 2) pbf.readPackedVarint(obj.tags); // new
if (tag === 2) obj.tags = pbf.readPackedVarint(); // old

cc @sshutovskyi


winstone: drop package and service

Motivation for this change
Close #56294
Upstream package is unmaintained for years
and nixpkgs provides alternatives
cc @rickynils @pSub @aanderse
Things done

[ ] 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 nix-review --run "nix-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)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Can you add at least a mkRemovedOption for .enable and replace the attributes with throw "This is unmaintained" or so? I'm not a fan of removing things without a trace.

Yes ok.
I will rework this later today.

@Infinisil > I added some messages for a smoother deprecation of both pkg and module


Other builders new format

Current status:

[x] Other builders / utility code (rust)
[x] Update other builder tests

To be done in later PRs

tx_builder.rs (rust)
WASM bindings
Update all other tests

btw @rooooooooob can we make cargo build --release compiling for the root project? I see we're missing chain/genesis for that

btw @rooooooooob can we make cargo build --release compiling for the root project? I see we're missing chain/genesis for that

Is that in scope here? We didn't touch any of those files. I could do another PR that updates non-builder tests to compile + gets that genesis to compile on release so we can get the compile + tests (if it's not too much work) checks working there.

btw @rooooooooob can we make cargo build --release compiling for the root project? I see we're missing chain/genesis for that

Is that in scope here? We didn't touch any of those files. I could do another PR that updates non-builder tests to compile + gets that genesis to compile on release so we can get the compile + tests (if it's not too much work) checks working there.

no, that's not in the scope of builders pr


Reduce Warning errors - Warnings without Code Type

Summary

Fixes #2648
Reduce Warning errors
Solve Warning errors that do not have a code type, except for (C:\Dnn.Platform\packages\Yarn.MSBuild.1.16.0\build\Yarn.MSBuild.targets cannot be imported again )

Thanks, this looks like a good contribution.  However, it should probably target release/9.4.x instead of development since there aren't breaking changes.

Do I have to rebase into origin/release/9.4.x?

Thanks @eng-aomar!


Fixed loading automate page when executionLogger is litedb taking more time

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

See the complete overview on Codacy

Do the optimization as we discussed

Done

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

See the complete overview on Codacy


Quick Pad 5.2.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

Microsoft Reviewers: Open in CodeFlow

@KevinLaMS Being that WinGet will support installing apps from the store, I don't think it's worth investing so much for this package right now. Is there a process to remove an app from WinGet or do I just need to delete the folder for it?

I think what we should do is keep this PR active as active so that once dependencies are done, we can add this if we want.
I agree, the 404 error we get with the current package is not good.  It would be great if you want to put through the RM for that package.

I think what we should do is keep this PR active as active so that once dependencies are done, we can add this if we want.
I agree, the 404 error we get with the current package is not good. It would be great if you want to put through the RM for that package.

I removed the outdated package for Quick Pad over here #5627.

@denelon @KevinLaMS This PR can be closed as the version of the manifest being used is 0.1.0.

@denelon @KevinLaMS This PR can be closed as the version of the manifest being used is 0.1.0.

How can that be resolved?

@yaichenbaum Sorry, I didn't tell earlier but the path of the manifest should be manifests/QuickPad/QuickPad/5.2.0/QuickPad.QuickPad.yaml

Still working on this.

@vedantmgoyal2009 I'm not sure why this isn't working, any ideas?

The folder should be manifests\q\QuickPad\QuickPad\5.2.0 and not manifests\QuickPad\QuickPad\5.2.0

https://github.com/microsoft/winget-pkgs/pull/5508#issuecomment-916959451

@yaichenbaum this appears to be a paid app, after I install it and run it, it is blocked and takes me to the store. We are unable to install paid apps at the moment, I believe we are blocked on this: https://github.com/microsoft/winget-cli/issues/908.


Coalescing schema building logic

We currently have a lot of logic for BaseModel e.g. to deal with recursive models and generics.
Since we plan to add a Validator (#5145) and we also want to support recursive and generic non-model things (e.g. #5138) we are going to end up with quite a bit of logic duplication.
We should be thinking about how we can coalesce this. I'm thinking our goal should be to have a function or functions that take in an arbitrary type and spit out everything we need about that type (core schema, validator, serializer). Then BaseModel and Validator would just call that (BaseModel passing it's own class as the argument). Of course BaseModel can still do things in it's metaclass (or __init_subclass__ or wherever) to keep track of things that will later be needed when building the schema, validator and serializer (like keeping track of @validator calls and such).

@adriangb I'm closing this as I think it's a bit abstract and we have a couple months worth of tweaks/improvements to this code.
But feel free to reopen if you think it makes sense.


Issue with completing accounts names that include dashes

Hello, thanks so much for this amazing plugin!
I'm using it and it completes well for most accounts, but it seems to have issues with accounts that include a dash in their name. Specifically, the subaccounts within such an account somehow don't get suggested when a parent account with a - has been typed already.
Example
For example, having those two accounts:
2022-01-01 open Assets:Current-Assets:BankA  EUR
2022-01-01 open Assets:CurrentAssets:BankB  EUR

and then typing A:C:B only suggests the second account Assets:CurrentAssets:BankB. I would have expected both accounts to be suggested.
Interestingly, typing just A:C correctly suggests both accounts.
I looked into the source of this plugin but unfortunately, I don't know much lua, so not sure where the issue lies or how to fix it. Or maybe it's even an issue with the cmp plugin? Would be awesome to get this fixed though, as my account hierarchy has loads of -. If this is a tricky case to fix, I can always rename my account hierarchy...
Docs
Beancount Account Syntax:

Each component of the account names begin with a capital letter or a number and are followed by letters, numbers or dash (-) characters. All other characters are disallowed.
https://beancount.github.io/docs/beancount_language_syntax.html#accounts

Thanks for reporting. I can reproduce this issue.

It's now fixed, please update to the latest main branch commmit.
And one more thing, ACB should work for this. I don't mean to make this feature but I found it works though.

That's awesome, thanks for the quick fix, can confirm it works now.

And one more thing, ACB should work for this.

Oh, that's even better, didn't realize that works as well. Maybe worth mentioning on the readme for others?

That's awesome, thanks for the quick fix, can confirm it works now.

And one more thing, ACB should work for this.

Oh, that's even better, didn't realize that works as well. Maybe worth mentioning on the readme for others?

Thanks for your suggestion. I will add that later.


get map translations from API

Instead of pulling map names from static json, use API to get all translations.
Also makes sure the pre-build fails if caching API data encounters errors.

.deploy

Can we make the sort of maps the same as in the maps JSON? I would like to have control of the sort based on the popularity of the map. Like Streets right now should be on top followed by customs.

We could, but as the list gets longer, it's easier to find the map you're looking for when they're sorted alphabetically.

The list will have a maximum of 12 maps and in this case, in my opinion, a sort by 'most used/hot map' is the best

I can see the advantages of both ways. Rather than just the two of us deciding, we can run a poll in the discord so as many folks as possible can weigh in.

.deploy to development

@Shebuka it looks like alphabetical map order won out in the discord poll (https://discord.com/channels/956236955815907388/956236955815907391/1064624322326564865), which is how this PR currently works. Any objection to deploying to prod and merging?

Deployed preview here: https://3657508d.tarkov-dev.pages.dev/

.deploy to development

@Shebuka it looks like alphabetical map order won out in the discord poll (https://discord.com/channels/956236955815907388/956236955815907391/1064624322326564865), which is how this PR currently works. Any objection to deploying to prod and merging?

No, but one thing, Openworld should be kept as last as it's not a real map

Not sure the best way to do that since the lists of maps are all just sorted by the map display name.

Not sure the best way to do that since the lists of maps are all just sorted by the map display name.

Custom sort function, something like: if key is openword, return 1 otherwise compare display name

.deploy


.hxproj files: annoying behavior with source control

There are changes to .hxproj files pretty much every time the version of a dependency changes, since those are included in the <classpaths> - which happens very frequently. Committed .hxproj files will thus almost always show up as having changed, especially with many different committers.
It's especailly annoying for repos with a lot of FD project files (flixel-demos for example).
I don't think there's a way to ignore changes to indexed files in git - that only works for files that are not committed via the .gitignore.
I'm not sure what the best solution for this is. One way would be to add a simple flag that could be set in the .hxproj file that makes it so classpaths aren't saved.

What kind of classpath is being problematic? If you use haxelibs this doesn't adds changing classpaths.
At work we don't include any editor/IDE files in the repos. One option would be to exclude hxprojs but I'd that's a problem you can still include .hxproj.template in the repo.

If you use haxelibs this doesn't adds changing classpaths.

Are you sure about that? This is an example diff from one of the demo projects:

One option would be to exclude hxprojs

FD is kind of the standard IDE for HaxeFlixel development, so not having the project files there would be inconvenient.

you can still include .hxproj.template in the repo

What would that do?

Ah, that must be openfl returning classpaths instead of haxelibs.
Is that really a big annoyance?
My alternative suggestion is to include a temp file: you can copy it as .hxproj for your personal usage but it never gets committed.

It is to me at least. Every time I open a demo project in FD I have working copy changes.
We're talking 60+ .hxproj files / projects here, so that'd be really annoying to manage, and would only solve the issue for me too, not others. And when I newly clone the repo / clone it on another computer, I'll have to do that all over again.

I'm not sure it will be very practical to have and option to "not save classpaths" only. One possibility would be to not save the project at all unless you explictly change something in the Project properties.

Also as an option, or in general?

Possibly an option in the toolchain confguration.

I guess in that case, something as simple as toggling the "show hidden files" button in the Project Manager would already be a change. Still, it would already be a huge improvement over the current state.

What about the ReadOnly property of Project? Could that be useful here?
I've also been wondering if it would be possible for FD to open the config files directly (the xml for OpenFL, a hxml, etc) without any project files being needed.

The thing is that you must be able to edit a few things in OpenFl projects, so it can't be fully read-only.

I found a workaround for this using git update-index --assume-unchanegd. If anyone else is having this issue, run this in the Git Bash of your repo:
find . -type f -name "*.hxproj" -exec git update-index --assume-unchanged {} \;
echo "Ignoring changes to":
echo ""
git ls-files -v | grep -e "^[hsmrck]"

Saves me so much time. :)


Path lookup syntax

What is the difference between $body.some.path vs $.body.some.path?

$body and $ are both variables that are being assigned to a JSON object.
In each respective case they might something like:
$body = { "some": { "path": "foo"}}

$ = { "body" {"some": {"path": "foo"}}}

Thanks


Persist issue

I am trying to use the persist function, because otherwise I have problems with my javascript.
The strange thing is that when I use persist, like this:   $.featherlight($("#addproperty"), {persist:"true"});
the first window opens like it should be, the second one is just an empty box.
Is there something I do wrong? Thanks!

Is it possible to get an example in jsfiddle or similar?

Closing until we get a reproducible example.

@marcandre. We're also getting this issue when trying to use persist with on-page content.
Here's a jsfiddle that recreates it.

Thanks for the example, @jfeust
The persist is meant for featherlight bound to an action, at least for now. See this modified example which works, for example.
There's been requests so it places the elements back where it found them, in which case your example would work.


Grunt failing

21:42:49 npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>This happends when using 1.0 grunt.

@dignifiedquire or @vladikoff hi could you update https://github.com/karma-runner/grunt-karma/blob/master/package.json#L49
Change it to 0.4.0 not 0.4.x since it fails https://integration.wikimedia.org/ci/job/mediawiki-extensions-qunit/35776/console

And release 0.12.3 please.

This is currently causing failures with grunt 1.0 now that it has been released.

The latest version is 0.12.2 which has the correct peerDependency: https://github.com/karma-runner/grunt-karma/blob/master/package.json#L49

Yay!
On Wed, Apr 6, 2016 at 9:41 AM, Friedel Ziegelmayer <
<EMAIL_ADDRESS>wrote:

The latest version is 0.12.2 which has the correct peerDependency:
https://github.com/karma-runner/grunt-karma/blob/master/package.json#L49
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/karma-runner/grunt-karma/issues/184#issuecomment-206378521

Thanks, yep it works.


form_choices with boolean value. Error return: Not a boolean value: 'True'

I'm using form_choices of flask-admin. The buy_or_sell column is a boolean column. Here is my code:
column_choices  = {
        'buy_or_sell':[
            (True, "Buy"),
            (False, "Sell")
        ]
    }

And I got the error whenever I try to create or update the data. Error: sqlalchemy.exc.StatementError: (builtins.TypeError) Not a boolean value: 'True'
I think the 'True' value is a string, not a boolean, that trigger the error. Is there anyway to bypass this problem? Thank you!

I'm having the same issue, is there a solution for this?


Additional table information on hover

I think this is a nice feature to quickly see additional info on a referenced table.
But please feel free to either just close or redo PR - first time with TS.
This pull request introduces a new function to provide detailed hover information for tables in the src/hoverProvider.ts file and updates the Table interface in src/types.ts to include BigQuery configuration. The most important changes include the addition of the getTableInformationFromRef function and the modification of the Table interface.
Enhancements to Hover Information:

src/hoverProvider.ts: Added getTableInformationFromRef function to provide detailed hover information, including the table's database, schema, type, partition, and dependencies.
src/hoverProvider.ts: Updated DataformHoverProvider to use the new getTableInformationFromRef function instead of getFullTableNameFromRef.

Updates to Type Definitions:

src/types.ts: Added bigquery property to the Table interface to include BigQuery-specific configurations.
src/types.ts: Defined a new TableBigQueryConfig interface to specify BigQuery configuration details such as partitioning and clustering.

Example:

Hi @HampB , thanks for the PR. I think this will be a good addition. I tested this locally and everything works as expected. I have few minor suggestions I have implemented  on this branch

Make the name of the table or view at the top clickable such that we can go to BigQuery directory from there
I have dropped Table: before the name as it can be a table/view. So, to keep it less verbose I have skipped the annotation entirely
To keep it consistent across the board I have added the clickable link in the full table name for source declarations as well

Please feel free to merge this to your fork if you are happy with this change and add to your PR. I was not sure how to directly add commits to this PR. From what I looked up, I can do that if I have access to push to your fork.

Thanks for the improvements!
Your changes are now merged into the PR


Create Chapter/Verse Numbers Check

As a user, I need to know that I have included every chapter and verse in my translation so that I am confident we have translated and included everything we intended to.
Depends on https://github.com/paranext/paranext-core/issues/449

Just for clarification, this actually means make an adaptor (or something) that reuses the existing C# Chapter/Verse check, right? I'm hoping we don't want to recreate it.

Yes

@ianhewubs Do you know if Segment Order Setting is still used/helpful?

Do you know if Segment Order Setting is still used/helpful?

If it's just for PT7 migration, I don't know what it could be. That said, it sounds like it could relate to canon definition (some projects are interconfessional and can be printed for protestant, catholic or orthodox tradition readers). If it does relate to canon, it could be essential. In either case, I think a PT9 dev will be in a better place to answer this.

Sounds good, thanks, Ian!

We deferred the configuring of versification til later, and we do not know of other configuration needed to be done to support this check. Closing.

The check in PT10S that uses the PT9 code produces the same results as PT9

Got the latest code.
ACTION STEPS

Navigate to PHP 1:30
zzz2 tab menu icon > Tools > Configure Check..
Tick only Chapter/Verse Numbers > "Current Book" > Philippians > OK
CONFIRM the Show Check Results.. list displays No errors.
---DELETE TEXT
In PHP 1:30, delete all the text in PHP 1:30 after "\v 30"
CONFIRM the Show Check Results.. list displays only one item:
PHP 1:30 Empty verse


The state dictionary of the model you are training to load is corrupted.

Hello I'm interested to test out the PRIMER model but when I followed the steps accordingly, I ended up getting
"ValueError: The state dictionary of the model you are training to load is corrupted. Are you sure it was properly saved?"
I've tried reinstalling the PRIMER-large packages too but to no avail. Did anyone encounter the same issue?

from transformers import AutoTokenizer
from transformers import LEDForConditionalGeneration, LEDConfig
tokenizer = AutoTokenizer.from_pretrained('./PRIMER/')
config = LEDConfig.from_pretrained('./PRIMER/')
model = LEDForConditionalGeneration.from_pretrained('./PRIMER/', config=config)
^this is my code but i got a ValueError saying that my model is corrupted. Tried on both windows and linux but both don't work.

Hi, you can follow the instruction on usage of PRIMER in readme.md. Basically, we used the original Longformer implementation instead of huggingface version. So please install Longformer by pip install git+https://github.com/allenai/longformer.git

@MYB0SS I am starring using PRIMER too, but I am not able to feed it with multiple texts as inputs to summarize. Could you share how you did it?