Using songbird standalone

Hi,
I am using a Mac Catelina
This is what I did when installing
conda create -n songbird_env python=3.6 numpy=1.15.4 scikit-bio=0.5.5 seaborn pandas=0.23.4 -c conda-forge
source activate songbird_env
conda install tensorflow=1.30 tqdm nomkl
conda install biom-format h5py -c conda-forge
conda install jupyter notebook
conda install songbird -c conda-forge

I keep getting the following warnings when I run model as simple as this
songbird multinomial \
	--input-biom ./data/redsea.biom \
	--metadata-file ./data/redsea_metadata.txt \
	--formula "1" \
	--epochs 10000 \
	--differential-prior 0.5 \
	--training-column Testing \
	--summary-interval 1 \
	--summary-dir results-redsea/redsea-results-null

Below are warnings

WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/bin/songbird:145: The name tf.Session is deprecated. Please use tf.compat.v1.Session instead.
2020-08-05 13:59:42.889984: I tensorflow/core/platform/cpu_feature_guard.cc:145] This TensorFlow binary is optimized with Intel(R) MKL-DNN to use the following CPU instructions in performance critical operations:  SSE4.1 SSE4.2 AVX AVX2 FMA
To enable them in non-MKL-DNN operations, rebuild TensorFlow with the appropriate compiler flags.
2020-08-05 13:59:42.890306: I tensorflow/core/common_runtime/process_util.cc:115] Creating new thread pool with default inter op setting: 8. Tune using inter_op_parallelism_threads for best performance.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:75: multinomial (from tensorflow.python.ops.random_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.random.categorical instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:86: The name tf.random_normal is deprecated. Please use tf.random.normal instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:91: Normal.init (from tensorflow.python.ops.distributions.normal) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use tfp.distributions instead of tf.distributions.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/tensorflow/python/ops/distributions/normal.py:160: Distribution.init (from tensorflow.python.ops.distributions.distribution) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use tfp.distributions instead of tf.distributions.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:100: Multinomial.init (from tensorflow.python.ops.distributions.multinomial) is deprecated and will be removed after 2019-01-01.
Instructions for updating:
The TensorFlow Distributions library has moved to TensorFlow Probability (https://github.com/tensorflow/probability). You should update all references to use tfp.distributions instead of tf.distributions.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:115: The name tf.summary.scalar is deprecated. Please use tf.compat.v1.summary.scalar instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:121: The name tf.train.AdamOptimizer is deprecated. Please use tf.compat.v1.train.AdamOptimizer instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/tensorflow/python/ops/clip_ops.py:286: add_dispatch_support..wrapper (from tensorflow.python.ops.array_ops) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.where in 2.0, which has the same broadcast rule as np.where
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:129: The name tf.summary.histogram is deprecated. Please use tf.compat.v1.summary.histogram instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:130: The name tf.summary.merge_all is deprecated. Please use tf.compat.v1.summary.merge_all instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:132: The name tf.summary.FileWriter is deprecated. Please use tf.compat.v1.summary.FileWriter instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:136: The name tf.global_variables_initializer is deprecated. Please use tf.compat.v1.global_variables_initializer instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:163: The name tf.train.Saver is deprecated. Please use tf.compat.v1.train.Saver instead.
0%|                                                                                | 0/80000 [00:00<?, ?it/s]WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:172: The name tf.RunOptions is deprecated. Please use tf.compat.v1.RunOptions instead.
WARNING:tensorflow:From /usr/local/anaconda3/envs/songbird_env/lib/python3.6/site-packages/songbird/multinomial.py:174: The name tf.RunMetadata is deprecated. Please use tf.compat.v1.RunMetadata instead.

In addition, when I try to load tensorboard, I keep getting these warnings (which goes longer than this but similar)
 tensorboard --logdir .

 Here are the warnings when I try to load hparams

E0805 14:09:00.260663<PHONE_NUMBER>35008 hparams_plugin.py:108] HParams error: Can't find an HParams-plugin experiment data in the log directory. Note that it takes some time to scan the log directory; if you just started Tensorboard it could be that we haven't finished scanning it yet. Consider trying again in a few seconds.
I0805 14:09:00.262099<PHONE_NUMBER>35008 _internal.py:113] ::ffff:<IP_ADDRESS> - - [05/Aug/2020 14:09:00] "POST /data/plugin/hparams/experiment HTTP/1.1" 400 -
I0805 14:09:00.263484<PHONE_NUMBER>90176 _internal.py:113] ::ffff:<IP_ADDRESS> - - [05/Aug/2020 14:09:00] "GET /data/plugins_listing HTTP/1.1" 200 -
E0805 14:09:00.280741<PHONE_NUMBER>35008 hparams_plugin.py:108] HParams error: Can't find an HParams-plugin experiment data in the log directory. Note that it takes some time to scan the log directory; if you just started Tensorboard it could be that we haven't finished scanning it yet. Consider trying again in a few seconds.
I0805 14:09:00.280971<PHONE_NUMBER>35008 _internal.py:113] ::ffff:<IP_ADDRESS> - - [05/Aug/2020 14:09:00] "POST /data/plugin/hparams/experiment HTTP/1.1" 400 -
E0805 14:09:00.289092<PHONE_NUMBER>35008 hparams_plugin.py:108] HParams error: Can't find an HParams-plugin experiment data in the log directory. Note that it takes some time to scan the log directory; if you just started Tensorboard it could be that we haven't finished scanning it yet. Consider trying again in a few seconds.
I0805 14:09:00.289318<PHONE_NUMBER>35008 _internal.py:113] ::ffff:<IP_ADDRESS> - - [05/Aug/2020 14:09:00] "POST /data/plugin/hparams/experiment HTTP/1.1" 400 -
E0805 14:09:00.324394<PHONE_NUMBER>35008 hparams_plugin.py:108] HParams error: Can't find an HParams-plugin experiment data in the log directory. Note that it takes some time to scan the log directory; if you just started Tensorboard it could be that we haven't finished scanning it yet. Consider trying again in a few seconds.
I0805 14:09:00.324654<PHONE_NUMBER>35008 _internal.py:113] ::ffff:<IP_ADDRESS> - - [05/Aug/2020 14:09:00] "POST /data/plugin/hparams/experiment HTTP/1.1" 400 -

This is what I see

hmm. We'll need more information in order to debug. How did you run the tensorboard command? Did you run everything in the same folder? Do you have any files generated in your results folder?

Thanks for the response! Here are responses.
How did you run the tensorboard command?

Yes and this is what I did tensorboard --logdir .

Did you run everything in the same folder?

Yes. I am staing in the same folder.

Do you have any files generated in your results folder?

Yes and saved here https://www.dropbox.com/sh/3sxl94dh9xhirt5/AADLzmVwihtaAvb9IYyjezV4a?dl=0

I am not sure but I think it may have a relationship with the tensorflow version? when i install and use 1.10. Everything goes fine; the  only issue is that I cannot see the HPARAMS tab, which was not available in that version.

Got it. Have you tried Tensorboard version 1.15.2?
On Wed, Aug 5, 2020, 3:34 PM coralzhang<EMAIL_ADDRESS>wrote:

Thanks for the response! Here are responses.
How did you run the tensorboard command?
Yes and this is what I did tensorboard --logdir .
Did you run everything in the same folder?
Yes. I am staing in the same folder.
Do you have any files generated in your results folder?
Yes and saved here
https://www.dropbox.com/sh/3sxl94dh9xhirt5/AADLzmVwihtaAvb9IYyjezV4a?dl=0
I am not sure but I think it may have a relationship with the tensorflow
version? when i install and use 1.10. Everything goes fine; the only issue
is that I cannot see the HPARAMS tab, which was not available in that
version.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/biocore/songbird/issues/134#issuecomment-669524275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXOTVMJNFXXBHJ2G36DR7HF7FANCNFSM4PV4TZ3Q
.

That is part of my question.. How do I upgrade tensorborad itself properly? I have never used conda and tensor flow before. As you see, the way I installed tensorborad, I guess, is through installing of tensorflow version=xx, and I tried to simply uninstall tensorboard and upgrade, but end up with messing up stuff with tb-nightly as well. So, I end up trying to use a higher version of tensorflow, say 1.15.
In addition, since the key results are the differentials.tsv, if I run a multinomial regression somewhere else, will I be able to reproduce the results, at least largely?

Try conda install tensorboard=1.15.2
There were no breaking changes between versions, so you should be able to
reproduce the results
On Wed, Aug 5, 2020, 3:48 PM coralzhang<EMAIL_ADDRESS>wrote:

That is part of my question.. How do I upgrade tensorborad itself
properly? I have never used conda and tensor flow before. As you see, the
way I installed tensorborad, I guess, is through installing of tensorflow
version=xx, and I tried to simply uninstall tensorboard and upgrade, but
end up with messing up stuff with tb-nightly as well. So, I end up trying
to use a higher version of tensorflow, say 1.15.
In addition, since the key results are the differentials.tsv, if I run a
multinomial regression somewhere else, will I be able to reproduce the
results, at least largely?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/biocore/songbird/issues/134#issuecomment-669530974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75VXNU4FZLUPYM2D4Y7R3R7HHUPANCNFSM4PV4TZ3Q
.


Add retry mechanism to AccumuloReloadingVFSClassLoader.

Also addresses issues mentioned in ACCUMULO-1507.

The full integration tests have passed on this test:
https://jenkins.revelc.net/job/Accumulo-PR-Build/86/


Fix LIGHT token

After the token listing on the frontend we got some issues: -1#Light is not showing correct number quantity. (2.000.000 = 2.000) Maybe getting price from new pool 1009 fix this? -2# When trying to trade light for any other token in Swap front page it takes a lot of RAM memory and crash the browser. What may be causing this?

In the chain registry, LIGHT also shows 6.

Ok done. I hope this fix the wrong decimal in osmosis front end


freebsd sctp support part 3

@bors r+

:pushpin: Commit 4bda84f158f169cb5ff3af20f96c29c2c5ba3148 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 4bda84f158f169cb5ff3af20f96c29c2c5ba3148 with merge 78d774fbc1c256d6cfae8ea71082b4dc68724634...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 78d774fbc1c256d6cfae8ea71082b4dc68724634 to master...


Fix the backward prop in DDE

Run reverse DDE on h_pe_rev instead of h_pe

Nice catch! Thank you so much for the fix.

I double checked my original implementation for the manuscript, which was correct. I introduced this bug accidentally in cleaning up the codebase.


Undefined Properties Error After Adding New Columns in Laravel Model

Larastan Version: v2.9.7
Laravel Version: v10.48.12

Description
I am encountering an issue with undefined properties in a Laravel model. I added new columns to an existing table using Laravel's after closure. However, I am now receiving errors related to undefined properties.
Steps to Reproduce:

Add new columns to an existing table using Laravel's after closure.
Attempt to access the new columns in the model.

Expected Behavior:

The new columns should be accessible in the Laravel model without any errors.

Actual Behavior:

An undefined property error occurs when accessing the newly added columns.

Additional Information:
Upon investigation, it appears that the after-closure is not being considered correctly, which is causing the undefined property error.
Laravel code where the issue was found
Schema::table('users', function (Blueprint $table): void {
    $table->after('status', function () use ($table) {
        $table->string('city')->nullable();
        $table->string('area_code')->nullable();
    });
});

It will work if I will do something like this.
Schema::table('users', function (Blueprint $table): void {
    $table->after('status', function (Blueprint $table) {
        $table->string('city')->nullable();
        $table->string('area_code')->nullable();
    });
});

$table->after('status', function (Blueprint $table) {

This is the correct form.
Mayba add : void ...

Got it. As per the laravel documentation, it is right. But I think it will create a new object for the Blueprint class.


wasm-pack build hangs with no output for over 3 minutes

🐛 Bug description
I ran the following:
$ wasm-pack build

It hung, and I left it for long enough to decide that it was a bug. I then ran it again and left it long enough to write out half of this bug report, before it miraculously eventually did something:
$ wasm-pack build
[INFO]: 🎯  Checking for the Wasm target...
...

It took at least 3 minutes to print something.
🤔 Expected Behavior
It should tell me what it's doing, and give some indication that it's not stuck in an infinite loop. I imagine you're losing many first-timer users who just assume this tool is broken, Ctrl-C, and move on.
👟 Steps to reproduce
Follow the quickstart until step 5.
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.10.3
rustc version: 1.67.1 (d5a82bbd2 2023-02-07)
macOS

I'm also having this issue, but I don't even get as far as the initial [INFO], I'm getting no output whatsoever
environment:
wasm-pack version: 0.11.1
rustc version: 1.60.0
windows

Please try out v0.12.0 from one of the following ways:

https://github.com/rustwasm/wasm-pack/releases/tag/v0.12.0
https://crates.io/crates/wasm-pack/0.12.0
https://www.npmjs.com/package/wasm-pack/v/0.12.0

facing same issue using v0.12.0 on macOS, with no output.
environment:
wasm-pack version: 0.12.0
rustc version: 1.69.0
macOS

facing same issue using v0.12.0 on macOS, with no output.
environment: wasm-pack version: 0.12.0 rustc version: 1.69.0 macOS

Okey, I found that's probably a network issue. After downloading wasm32-unknown-unknown target the problem disappeared.

I was just following this page here: https://developer.mozilla.org/en-US/docs/WebAssembly/Rust_to_Wasm
I just had wasm-pack build --target web hang on me for over 30 minutes.
I was under the impression this would take a long time because of this:
https://developer.mozilla.org/en-US/docs/WebAssembly/Rust_to_Wasm#building_the_package
I went searching and came here.
Went here and installed: https://rustwasm.github.io/wasm-pack/installer/
(I already had it installed though from the Mozilla doc I was reading)
Reinstalled it
Ran wasm-pack build --target web again and ran instantly.
OS: Windows
wasm-bindgen = "0.2.92"
rustc 1.79.0 (129f3b996 2024-06-10)

I'm having this problem. I've verified that target wasm32-unknown-unknown is installed, and I tried using wasm-pack installer pages, so the solutions in https://github.com/rustwasm/wasm-pack/issues/1231#issuecomment-2246614729 and https://github.com/rustwasm/wasm-pack/issues/1231#issuecomment-1606692036 didn't apply. I've tried disabling wasm-opt as described in https://github.com/rustwasm/wasm-pack/issues/921. No amount of --verbose, or --log-level flags seem to cause it to generate any messages indicating that it's doing anything.
Arch Linux
wasm-pack 0.13.0
wasm-bindgen 0.2.95
rustup 1.27.1
rustc 1.81.0


Transferred HNT instead of burning to vote

I accidentally transferred HNT to the wallet specified on heliumvote.com instead of burning it.
https://explorer.helium.com/accounts/134UcXhcGD1fxR3XrA3rgXXiQCjNFiB8MbnxsTX8z1iv3CQ52Zs
Turns out that doesn't work. Can someone at least register this as a vote?
(my apologies for opening a github issue for this, but I didn't know where else to ask)

Payment has been reversed, minus the transaction fee.
Thanks for filing the issue here.


annotations are not properly parsed.

double quotes are missing

this is actually not the real issue. ComposeActions ignores annotations.


⚠ ClamAV has degraded performance

In 00a59a5, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 93 ms

Resolved: ClamAV performance has improved in b2d515e.


Grab specs during "registry add", don't wait until "list" is run

https://github.com/automationbroker/sbcli/pull/60


429 almo and bcfw changes

This pull request contains:

Add ALM header for ouput
Remove infeasibility from BCFW output
Add update order to BCFW output
Add print callback extension allowing to add custom columns to the output of any algorithm
-- minimal changes to make_print_callback and make_trajectory_callback needed
-- Applied for ALM to print infeasibility
Add BCFW example with showcase of custom update order

probably need to rerun the formatter after this


 To top it off im highly unsure if I am running this in the right fashion. from the command line im attempting to $node main.js while in the file and directory js/main.js.

Which version are you trying to run? (There are two: the original one, and the recently released v2 beta.)

original

In that case I suggest you try v2, which is much easier to install and offers a lot more possibilities.
https://github.com/MichMich/MagicMirror/tree/v2-beta

Do you plan to merge v2-beta into master?

Eventually yes. First want to fix most of the bugs (the calendar seems to have persistent issues).
Also want to find a beter solution to reference to the latest node version in the installer script.


Generalize WindowBuilder::with_title

The pull request makes the usage of with_title a bit more convenient for static titles.
Regards,
Ivan

Thanks


Use specified device type to use CPU only

What is the way to specify the device type, for example, if I want to specifically use the CPU, how can I change the code to fit this?

We officially only support CUDA. I believe it should not be too hard to hack it to work on CPU, e.g., by changing https://github.com/hkchengrex/Cutie/blob/e869fab5e653b118c475cbafe0b2322b37a7e320/cutie/utils/get_default_model.py#L23
and other .cuda() calls in the scripting demo.

Please feel free to re-open if there are any updates.


Icons are broken in Sketch

I have yet to find an icon that works when pasting it into Sketch. Everything works great in the browser, but this is how it looks in Sketch:

I have just copied the first three icons as an example, but this happened with every icon I have used so far. Anybody else who has this problem?

Steve, would love to use these, but facing the same issue here.
Mono icons which uses a similar concept of "copy svg" works without any issues.
See: https://icons.mono.company/

When copying these icons from Figma to Sketch, by copying SVG code and paste it to Sketch, there's no problem. But if you copy the .svg file directly, facing the same issue here.

I think icons are broken because of SVG optimization, which changes the format of d="" path attr.

Yeah unfortunately this is just the nature of importing optimized SVGs into design tools. No plans to prioritize trying to figure out a way to both optimize the SVGs while still importing correctly into Sketch I'm afraid as we don't use Sketch ourselves and we have a separate Figma version of the icons for when we need them for designing.

Alright, fair enough.


Support Authorization header

I am trying to pass my user credentials to my websocket server using the url<EMAIL_ADDRESS>Unfortunately on the server side I don't see any Authorization header.
I initially thought about an old chromium issue but I have the exact same issue on FIrefox.
It would be very nice to support HTTP basic auth during upgrade request or even better, allow us to pass additional headers (maybe in the low level API).

This seems to be unsolvable, as the JS API itself doesn't support setting any headers:
https://stackoverflow.com/questions/22383089/is-it-possible-to-use-bearer-authentication-for-websocket-upgrade-requests/26123316#26123316


Cyclic schema definitions still don't work

Hi,
It seems the latest release broke cyclic schemas again. The following cyclic schema still doesn't work
graphql.AssertException: type Widget not found in schema

interface Node {@GraphQLID val id: String }
class User: Node {
@GraphQLID
override val id = ...
fun widget(@GraphQLContext context: Context): Widget = ...
}

class Widget: Node {
@GraphQLID
override val id = ...
fun user(@GraphQLContext context: Context): User = ...
}

I need to traverse User -> Widget -> User, and both are implementing Nodes.
It only works if I drop one of the cyclical references.

@Togrias We fixed a bug that we had with GraphQLTypeReferences in our latest release. Can you test version 0.2.1 to see if you are still having issues with your graph.
If you are having a problem, you can post here with the data classes, query classes, and configuration and we can reopen the issue


How to install with the Passenger module?

In the nginx formula, there is an option for installing the Passenger module.  It requires passing an argument --with-passenger.  How does one pass an argument with Puppet/Boxen?

FYI updated to work with newer puppet-ruby ... would be great to get that in as nginx::passenger or so to make this less weird ... not sure if anyone got this working without these hacks (and having a global ruby that is not system ruby)


add conv-related layers

For using convolutional networks, we need some more layer types

[ ] Convolutional Layer
[ ] ReLu Layer
[ ] Pooling Layer
[ ] Dropout Layer

Refactored those layer implementations into specific issues.
#18
#19
#20
This issue becomes therefore obsolete and can be closed.


Complete software spec

Action Items

[ ] Port over information from EOI to software spec
[x] Ask for User Stories from PI
[ ] Port over User Stories to software spec
[ ] Create a software design specification [RSE]

As of 6/10/2024 we received MVP Discussion Notes, User functions list, and User stories.
Key note from slack:

note that our discussion is not yet finished and we need to identify from this list of functions on what shall be included in MVP for each account category. We are scheduled to have another discussion next week and pls stay tuned.

Links to slack conversation:

https://escience-institute.slack.com/archives/C0717F2RK2P/p1718060187582179?thread_ts=1717699328.370999&cid=C0717F2RK2P
https://escience-institute.slack.com/archives/C0717F2RK2P/p1718074803239759?thread_ts=1717699328.370999&cid=C0717F2RK2P

Done


Comments backend

@RubenGeo It seems you hadn't merged these changes yet. Could you fix the conflicts and merge it in?

 (I haven't looked that closely, but I didn't see it in the CommentEntity)

Yes, the timestamp is in BaseEntity :+1:


Reimplement MathJax

MathJax has been (soon to be) removed  in #186 because it was formatting challenge descriptions with no maths formula, making new concepts like SASS and RegEx nearly impossible to grasp because syntax was missing in the instructions.
See #185 for details
@scissorsneedfoodtoo is there a way to only implement MathJax for maths formula?

@Bouncey
The inline config on line 44 of src/templates/Challenges/components/Side-Panel.js seems to be the issue:
tex2jax: { inlineMath: [['$', '$'], ['\(', '\)']] }
I suggest we select alternate delimiters and amend the inline config and the rosetta code challenge json as necessary.
documentation here: https://docs.mathjax.org/en/latest/options/preprocessors/tex2jax.html#configure-tex2jax

@Bouncey, dang, I'm sorry about that. Didn't think to check if SASS and other things would be affected.
@johnkennedy9147 is exactly right. I think for now it's better to remove that line and use the default config, which should look for $$...$$ delimiters rather than single $'s.

What about Katex?

@scissorsneedfoodtoo Are you working on this? Any progress?

@tchaffee, yes, I've been working on this slowly. Been playing around with both Katex like @Flarp suggested and MathJax, trying to see which is faster/better supported.
Using the $$...$$ delimiters now and going through the challenges trying to make sure it doesn't break any other challenge descriptions.

@scissorsneedfoodtoo That's good news. In terms of delimiters, is there any reason to not choose a delimiter so specific that it would be almost guaranteed to be unique? $$inLineMathBegin\...$$inLineMathEnd\?

@tchaffee, that's a good point. It's mostly just a matter of how much can be done quickly and easily. I could certainly change the delimiters to something like $$inlineMath$$ and retest.


Proposed extensions: textDocument/selectionRange

Implementation for https://github.com/Microsoft/language-server-protocol/issues/613

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

Status: I've got the code to compile, but I haven't actually tested it with my server. Not sure how all proposed bits, in the VS Code and in the lsp client library, should fit together.

Status update: I've successfully (after fiddling with npm quite a bit) built my extension with selectionRanges feature enabled. Will try to implement server side soon.

The server impl is read, and server and client successfully work together: https://github.com/rust-analyzer/rust-analyzer/commit/fffa0695dd7772efa82dbac652223bbdc51c62d3!
The only quirk is that current insider's does not have the latest version of proposed API (it uses Range instead of SelectionRange), so I had to tweak client library a bit to work with old API.

I merged the PR in and made new next version:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>@aeschli @octref

@jrieken I am a little confused about VS Code state here. Are you switching to multi-position in the end? The current proposed API is still single-position.

Yeah, switching to multiple positions is the current plan. Not sure why @dbaeumer already merged this...

@matklad @jrieken It's probably @dbaeumer feels that the LSP API itself will not change so he would like adopters to start trying out and using the LSP API.
Or do we now anticipate the LSP API changing also?

This got released as a next version (*-next.1) to get feedback on the LSP level as well. Normal adopters will not see that version and we are free to change the LSP API to multiple positions which I suggest to do.

In addition the feature is in proposed state and users need to opt in using it.

@dbaeumer FYI, the vscode API changed again:

kind is dropped
parent-child relationship are now established using parent pointers

https://github.com/Microsoft/vscode/commit/b61768007d5c1e91f96096565ba60db3d04b4b86

@matklad I noticed that as well. Are you willing to work on a adoption PR. We can merge it in as soon as we have another stabled release with the new API.

@dbaeumer yeah, I'll most likely handle this withing a week

done: https://github.com/Microsoft/vscode-languageserver-node/pull/474#pullrequestreview-219371694


Add badge for android-gems.com

Added badge for android-gems: http://www.android-gems.com/lib/f2prateek/rx-receivers , it looks like this:

Thanks, but not really sure I want these badges crowding the Readme.

Well, that's OK. :)


Runtime check only works with npm

Today we only prompt the user to update the func cli if they installed it through npm. Obviously that doesn't work a lot of the time if the user installed through other methods.
We can use the template feed to get the latest version of the cli and we can run 'func' (or func --version once this is released) to get the local version and completely bypass npm.

Fixed in https://github.com/Microsoft/vscode-azurefunctions/pull/339 and https://github.com/Microsoft/vscode-azurefunctions/pull/346


URL.toString works inconsistently

Hi!
Recently I found a strange behavior with my worker.
This is different from Chrome/Firefox/Node.js and looking at spec, seems like the spec describes a different behavior.
https://github.com/cloudflare/workerd/blob/17a927f2f98e5115c643729725076b00f0e7d3b1/src/workerd/api/url-standard.c%2B%2B#L2081
The parameters are percent-encoded during the toString invocation.
So, if we evaluate:
new URL("https://mytest.workers.dev/?h=e3Rlc3QhfQ==").toString()

Chrome/Firefox/Node.js output:
https://mytest.workers.dev/?h=e3Rlc3QhfQ==
Workerd output:
https://mytest.workers.dev/?h=e3Rlc3QhfQ%3D%3D
I know, from rfc3986 angle it all makes sense. However, the spec which describes toString behavior does not tell to percent-encode parameters, if I'm not mistaken:

https://url.spec.whatwg.org/#dom-url-href
https://url.spec.whatwg.org/#url-serializing

Can this be changed somehow? Maybe some additional flag?

What is your compatibility date? Make sure that you're compatibility date is 2022-10-31 or later or that you have the url_standard compatibility flag enabled to use the standardized URL implementation (https://developers.cloudflare.com/workers/platform/compatibility-dates/#new-url-parser-implementation).
Also, FWIW, Node.js' implementation of URL is more standards compliant than either Chrome or Firefox's so be sure to use that as the baseline.

@jasnell you are right, the compatibility date was 2022-10-21 😄
So, seems like there is already such possibility.
Thanks! Closing as stale...


Don't warn when kotlin projects redundantly set the allowed usage on the test fixtures runtime configuration

The user can't do anything about these warnings, so suppress them.  This was a case missed during the original work on this feature.

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

SHould this be targeting release?

Ah, right, we already branched for 8.2.  Let me fix that.

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

I've triggered a build for you.


Refactor transaction handling

Coverage decreased (-0.1%) to 90.517% when pulling 77323e744c50cb2aa0210d853b8f6b5d323ad674 on bmihelac:refactor-transaction-handling into af3583544c3302d31b4d1c4c343ba63f83424434 on django-import-export:master.

@bmihelac Could you fast-forward this (it's still showing diffs in the CHANGELOG file for instance) please?  Also, I see that this is assigned to "django-import-export/maintainers" for code review, but it appears you're the only person in that group? ;)

@mgrdcm rebased it to master branch.sorry for  misleading review request

Coverage increased (+0.6%) to 91.255% when pulling dd1c0852bac0a499693a2b31a42457e2134d266c on bmihelac:refactor-transaction-handling into 859641a61f6ad9d18bf449e3a85454b7bb1af08e on django-import-export:master.

No worries!  I'll try to take a look tonight, though anyone else who can should go ahead!

Not sure when I'm going to be able to do a thorough review of this, might be a few days.  @manelclos or @shaggyfrog can you take a look?

Coverage increased (+0.6%) to 91.255% when pulling dd1c0852bac0a499693a2b31a42457e2134d266c on bmihelac:refactor-transaction-handling into 859641a61f6ad9d18bf449e3a85454b7bb1af08e on django-import-export:master.

LGTM, tests are passing (including Django 2.0 and master), plus coverage increases 0.6% Whoo-hoo!

merged, thanks for review


Star Wars Saga Edition (New Features/Bug Fixes)

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[x] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Settings:
Fixed Custom NPC skills checkbox in settings.
Added DR/SR/Immune toggle for NPCs.
Move DR/SR/Immune/Custom Skills/Show Hide Armor settings for PC/NPC to Character tab.
NPC:
Added Armor statblock to NPCs (Everything appears working)
Attack block has been updated to the PC variant. For older sheets, use settings to disable new attack block.
New Defense statblock added. Best attempts have been made to salvage old formulas and to identify stock formulas and replace. Use the override block to override complete formula.
PC:
Reorganized/cleaned up Attacks section.
Added Target Defense in repeated attacks section (Enables targetted attacks and just good for noting what def your attack hits).
Completely reorgnized Common skills grapple/initiative/perception/status into a two column format and made them highlight when hovered and expandable. Initiative gets notes now.
Armor Hide functionality restored. Now if Armor is enabled in settings, you can still compress the armor section but it doesn't disappear completely.
Armor/Defense/Skills/Attack Options/Etc/All except Attacks) are now collapsible with their header text. Highlights when hovered. Need to look at doing attacks was having issues with it.
Rearranged HP/Total HP/Bonus HP to align with second wind. Looks better and actually makes more sense flow wise to have Bonus HP first.
Condition Tracker now has radial type looks. They have a changing palette from Green to dark purple as you go down the tracker. Also does speed.
Force Powers modified from a text area to a repeating attacks list. Add Force Powers formulas in the box, name and hit the roll button. Premade roll20 formulas for force powers are available on Saga subreddit.
Sheet workers:
Reflex/Fort/Will Sheetworkers with formula override. Going to bring PC defenses over to NPC defenses today. (Decent backwards compatibility based on Dawn of Defiance. I will try to improve it before release.)
Auto set max HP when Max HP set to 0 and you increase current HP. (No more filling out both for a new NPC)
Grapple selects the highest mod when stats change.
Total Experience automatically calculated when sheet opened and when level changes. No more filling in Total XP. Its already done. (I'd consider adding homebrew rules to this if needed)
CT Tracker will now reduce speed by half and zero for -10 and helpless. This works by storing speed value when the sheet first opens. If you change speed value while at -10 or helpless and open/close the sheet it will not save as new speed is only recorded at -5 or above. This is an edge case and otherwise works perfectly. This was actually pretty hard to code because of how it all works together.
Attribute calculation handed over to sheetworkers from autocalcs.
Grapple Modifier moved to sheet worker. Currently when you increase STR/DEX it will not increase unless you open or close the sheet. That is because of the selectable mod type box. We had to add a new attribute to store that variable and then pass it to a sheetworker to calculate dex/str mod and pass that into grpmod. Any auto-calc formula that is receiving an attribute type (dex_mod) and not a value (2) will not calculate until the sheet is open. This is why skills and defense also suffer from these issues. Looking at fixing all of them but it's difficult because we don't want to change the formulas and break old sheets. We either need version control and an update sheetworker that moves variables around for old version sheets or we have to reuse what attributes are already in the formulas and make new attributes to store the type modifier and pass it through a sheetworker. Sheetworker then takes type modifier and calculates and passes the #value to the old grpmod/refmod attribute.
Roll template:
Added Character name to the top of the roll template.
Crits changed to aqua from green.
Misc:
Tons of little tweaks to uniformity. Hover-over texts on many items made uniform to eachother. Added missing [Descriptors] to roll templates for many items.
WIP: Highlights when you hover over anything that is clickable. (Still more to do)
Tons of misc alignments and overlaps/formatting fixes. More to do.
Knowledge skills note descriptor fixes. GalacticLore = Galactice Lore
Tons of HTML errors syntax fixes.
Updated aaron sheet. Not important but at least you know.

Character Sheet Info Roll20 Internal Use only.

Hi @nwg5817 !

Thanks for submitting the overhaul to this sheet, as this seems to be under active development, we’re going to invite the original sheet author to weigh in on these changes.

@LilLiteralist, would it be possible for you to please review these changes and provide any necessary instructions for the author?
We will permit 21 days for a response from the original author before we proceed with merging the changes.

Many thanks!

Nora, @LilLiteralist and I have been in communication throughout these changes and I've been working directly with them. They are in the loop with these changes as well as all attempts to communicate with the Saga community through Roll20/Discord/Reddit. @LilLiteralist has ceased active development of the sheet for now.

I have been consulting with him on this. I can't confirm that everything works perfectly, but I had a few changes myself which had some bugs. We're also monitoring feedback from multiple SWSE communities.


loading screen

Would be perceived as a lot snappier if we show an immediate loading screen that just streams CLI output until the render shows up.
Or perhaps an overlay so that subsequent renders don't jump from image to text.
https://user-images.githubusercontent.com/3120367/228016174-a3aae9ff-ce4a-4a1d-873e-82c4e89150ea.mp4
D2's CLI also spits out periodic messages when it takes a long time https://github.com/terrastruct/d2/pull/1058

# d2 -w C:\Users\x\Documents\!misc\fridge_modded.d2 -h localhost -p 42069
# d2 -w C:\Users\x\Documents\!misc\fridge_modded.d2 -h localhost -p 42069 --theme=300 --dark-theme=200 -l elk --pad 0

# *.style.stroke: "white"

Lava: {
	shape: parallelogram
	style: {
		stroke: "#FF3300"
		stroke-width: 4
	}
}
Lava -> Alchemist.Netherrack:{
	style.stroke: "#FF3300"
}
Lava -> Alchemist.Blaze Cake:{
	style.stroke: "#FF3300"
}

Quarry: {
	style: {
		stroke: "#828282"
		stroke-width: 4
	}

	Igneous Extruder.shape: parallelogram
	Igneous Extruder -> Cobblestone

	Cobblestone
	Cobblestone -> Stone
	Cobblestone -> Gravel
	Cobblestone -> _.Forging.Gravel:{
		style.stroke: "#828282"
	}
	Cobblestone -> Diorite
	Cobblestone -> Andesite

	Stone

	Gravel
	Gravel -> Sand

	Sand
	Sand -> Glass
	Sand -> Soul Sand

	Glass
	Glass -> _.Apiary.Glass Bottle:{
		style.stroke: "#828282"
	}

	Soul Sand
	Soul Sand -> Nether Quartz

	Nether Quartz
	Nether Quartz -> Diorite

	Diorite
	Diorite -> Andesite

	Andesite
	Andesite -> _.Forging.Andesite Alloy:{
		style.stroke: "#828282"
	}
}

Woodcutting: {
	style: {
		stroke: "#AD7D00"
		stroke-width: 4
	}

	Spruce Log
	Spruce Log -> Stripped Spruce Log

	Stripped Spruce Log
	Stripped Spruce Log -> _.Forging.Andesite Casing:{
		style.stroke: "#AD7D00"
	}
	Stripped Spruce Log -> Spruce Plank

	Spruce Plank
	Spruce Plank -> Stick

	Stick
	Stick -> _.Forging.Toolsmith.Iron Sword:{
		style.stroke: "#AD7D00"
	}
}

Forging: {
	style: {
		stroke: "#D6B656"
		stroke-width: 4
	}

	Gravel
	Gravel -> Sand
	Gravel -> Clay Ball
	Gravel -> Iron Nugget

	Sand
	Sand -> Clay Ball

	Clay Ball
	Clay Ball -> Clay

	Clay
	Clay -> Terracotta

	Terracotta
	Terracotta -> Red Sand

	Red Sand
	Red Sand -> Gold Nugget

	Gold Nugget
	Gold Nugget -> _.Alchemist.Golden Carrot:{
		style.stroke: "#D6B656"
	}
	Gold Nugget -> _.Alchemist.Glistering Melon:{
		style.stroke: "#D6B656"
	}

	Iron Nugget
	Iron Nugget -> Iron Ingot
	Iron Nugget -> Andesite Alloy

	Iron Ingot
	Iron Ingot -> Toolsmith.Iron Sword
	Iron Ingot -> Toolsmith.Shears
	Iron Ingot -> Iron Bars

	Iron Bars
	Iron Bars -> _.Fishery.Water Strainer:{
		style.stroke: "#D6B656"
	}

	Toolsmith: {
		style: {
			stroke: "#D6B656"
			stroke-width: 4
		}
		Iron Sword
		Iron Sword -> _._.Animal Farm.Kill:{
			style.stroke: "#D6B656"
		}
		Iron Sword -> _._.Mob Grinder.Kill:{
			style.stroke: "#D6B656"
		}

		Shears
		Shears -> _._.Animal Farm.Shear:{
			style.stroke: "#D6B656"
		}
		Shears -> _._.Apiary.Shear:{
			style.stroke: "#D6B656"
		}
	}
}

Apiary: {
	style: {
		stroke: "#FFCC99"
		stroke-width: 4
	}

	Bee.shape: parallelogram
	Bee -> Honey Bottle
	Bee -> Shear

	Glass Bottle
	Glass Bottle -> Honey Bottle

	Honey Bottle
	Honey Bottle -> Honey

	Honey.shape: cylinder
	Honey -> _.Confectionary.Mashmallow:{
		style.stroke: "#FFCC99"
	}

	Shear.shape: hexagon
	Shear -> Honeycomb

	Honeycomb
}

Vanilla Crop Farm: {
	style: {
		stroke: "#82B366"
		stroke-width: 4
	}

	Wheat.shape: parallelogram
	Wheat -> Wheat Item
	Wheat -> Seed
	Wheat Item: "Wheat"
	Wheat Item -> _.Animal Farm.Cow:{
		style.stroke: "#82B366"
	}
	Wheat Item -> _.Animal Farm.Sheep:{
		style.stroke: "#82B366"
	}
	Wheat Item -> _.Slime Cube.Wheat Flour:{
		style.stroke: "#82B366"
	}
	Seed

	Carrot.shape: parallelogram
	Carrot -> Carrot Item
	Carrot Item: "Carrot"
	Carrot Item -> _.Animal Farm.Rabbit:{
		style.stroke: "#82B366"
	}
	Carrot Item -> _.Alchemist.Golden Carrot:{
	 style.stroke: "#82B366"
 }

	Potato.shape: parallelogram
	Potato -> Potato Item
	Potato Item: "Potato"
	Potato Item -> _.Animal Farm.Pig:{
		style.stroke: "#82B366"
	}

	Bamboo.shape: parallelogram
	Bamboo -> Bamboo Item
	Bamboo Item: "Bamboo"
	Bamboo Item -> _.Fishery.Water Strainer:{
		style.stroke: "#82B366"
	}

	Melon.shape: parallelogram
	Melon -> Melon Item
	Melon Item: "Melon"
	Melon Item -> _.Alchemist.Glistering Melon:{
		style.stroke: "#82B366"
	}

	Pumpkin.shape: parallelogram
	Pumpkin -> Pumpkin Item
	Pumpkin Item: "Pumpkin"

	Cactus.shape: parallelogram
	Cactus -> Cactus Item
	Cactus Item: "Cactus"
	Cactus Item -> _.Slime Cube.Green Dye:{
		style.stroke: "#82B366"
	}

	Sugar Cane.shape: parallelogram
	Sugar Cane -> Sugar Cane Item
	Sugar Cane Item: "Sugar Cane"
	Sugar Cane Item -> _.Confectionary.Sugar:{
		style.stroke: "#82B366"
	}
	Sugar Cane Item -> _.Confectionary.Paper:{
		style.stroke: "#82B366"
	}

	Cocoa Beans.shape: parallelogram
	Cocoa Beans -> Cocoa Beans Item
	Cocoa Beans Item: "Cocoa Beans"
	Cocoa Beans Item -> _.Confectionary.Crushed Cocoa:{
		style.stroke: "#82B366"
	}
	Cocoa Beans Item -> _.Confectionary.Chocolate:{
		style.stroke: "#82B366"
	}
	Cocoa Beans Item -> _.Confectionary.Dark Chocolate:{
		style.stroke: "#82B366"
	}
	Cocoa Beans Item -> _.Confectionary.Ruby Chocolate:{
		style.stroke: "#82B366"
	}

	Beetroot.shape: parallelogram
	Beetroot -> Beetroot Item
	Beetroot -> Beetroot Seeds
	Beetroot Item: "Beetroot"
	Beetroot Seeds

	Brown Mushroom.shape: parallelogram
	Brown Mushroom -> Brown Mushroom Item
	Brown Mushroom Item: "Brown Mushroom"
	Brown Mushroom Item -> _.Alchemist.Fermented Spider Eye:{
		style.stroke: "#82B366"
	}

	Red Mushroom.shape: parallelogram
	Red Mushroom -> Red Mushroom Item
	Red Mushroom Item: "Red Mushroom"
}

Fishery: {
	style: {
		stroke: "#6C8EBF"
		stroke-width: 4
	}

	Water Strainer
	Water Strainer -> Catch Fish

	Catch Fish.shape: hexagon
	Catch Fish -> _.Animal Farm.Raw Fish:{
		style.stroke: "#6C8EBF"
	}
	Catch Fish -> Pufferfish

	Pufferfish
}

Animal Farm: {
	style: {
		stroke: "#E356D0"
		stroke-width: 4
	}

	Cow.shape: parallelogram
	Cow -- Kill

	Pig.shape: parallelogram
	Pig -- Kill

	Rabbit.shape: parallelogram
	Rabbit -- Kill

	Sheep.shape: parallelogram
	Sheep -- Kill
	Sheep -> Shear

	Chicken.shape: parallelogram
	Chicken -- Kill
	Chicken -> Egg

	Kill: {
		shape: hexagon
		style.multiple: true
	}
	Kill -> Raw Beef
	Kill -> Raw Pork
	Kill -> Raw Rabbit
	Kill -> Raw Mutton
	Kill -> Raw Chicken

	Raw Beef
	Raw Beef -> Minced Beef

	Raw Pork
	Raw Pork -> Minced Pork

	Raw Rabbit
	Raw Rabbit -> Minced Rabbit

	Raw Mutton
	Raw Mutton -> Minced Mutton

	Raw Chicken
	Raw Chicken -> Minced Chicken

	Raw Fish
	Raw Fish -> Minced Fish

	Minced Beef

	Minced Pork

	Minced Rabbit

	Minced Mutton

	Minced Chicken

	Shear.shape: hexagon
	Shear -> Wool

	Egg -> _.Alchemist.Blaze Cake Base: {
		style.stroke: "#E356D0"
	}
	Egg -> _.Confectionary.Mashmallow: {
		style.stroke: "#E356D0"
	}
}

Alchemist: {
	style: {
		stroke: "#11D6B5"
		stroke-width: 4
	}

	Netherrack
	Netherrack -> Cinder Flour

	Cinder Flour
	Cinder Flour -> Netherrack
	Cinder Flour -> Blaze Cake Base
	Cinder Flour -> Glowstone Dust
	Cinder Flour -> Gunpowder
	Cinder Flour -> Redstone Dust

	Blaze Cake Base
	Blaze Cake Base -> Blaze Cake

	Blaze Cake

	Glowstone Dust

	Gunpowder

	Redstone Dust

	Blaze Powder
	Blaze Powder -> Apothecary.Strength

	Nether Wart.shape: parallelogram
	Nether Wart -> Nether Wart Item

	Nether Wart Item: "Nether Wart"
	Nether Wart Item -> Apothecary.Awkward Potion

	Golden Carrot
	Golden Carrot -> Apothecary.Night Vision

	Glistering Melon -> Apothecary.Healing

	Fermented Spider Eye
	Fermented Spider Eye -> Apothecary.Potion of Harming

	Apothecary: {
		style: {
			stroke: "#11D6B5"
			stroke-width: 4
		}

		Water.shape: parallelogram
		Water -> Awkward Potion

		Awkward Potion.shape: cylinder
		Awkward Potion -> Night Vision
		Awkward Potion -> Healing
		Awkward Potion -> Strength

		Night Vision: "Potion of Night Vision\n(3:00)" {
			shape: cylinder
		}
		Night Vision -> _.Glowstone Dust

		Healing: "Potion of Healing" {
			shape: cylinder
		}
		Healing -> Harming

		Harming: "Potion of Harming" {
			shape: cylinder
		}
		Harming -> _.Gunpowder

		Strength: "Potion of Strength" {
			shape: cylinder
		}
		Strength -> _.Redstone Dust
	}
}

Mob Grinder: {
	style: {
		stroke: "#B85450"
		stroke-width: 4
	}

	Skeleton.shape: parallelogram
	Skeleton -- Kill

	Zombie.shape: parallelogram
	Zombie -- Kill

	Spider.shape: parallelogram
	Spider -- Kill

	Blaze.shape: parallelogram
	Blaze -- Kill

	Kill: {
		shape: hexagon
		style.multiple: true
	}
	Kill -> Bones
	Kill -> Rotten Flesh
	Kill -> String
	Kill -> Spider Eye
	Kill -> Blaze Rod

	Bone
	Bone -> Bonemeal

	Bonemeal
	Bonemeal -> _.Slime Cube.White Dye: {
		style.stroke: "#B85450"
	}

	Rotten Flesh

	String

	Spider Eye
	Spider Eye -> _.Alchemist.Fermented Spider Eye: {
		style.stroke: "#B85450"
	}

	Blaze Rod
	Blaze Rod -> _.Alchemist.Blaze Powder: {
		style.stroke: "#B85450"
	}
}

Slime Cube: {
	style: {
		stroke: "#336600"
		stroke-width: 4
	}

	White Dye
	White Dye -> Lime Dye

	Green Dye
	Green Dye -> Lime Dye

	Lime Dye -> Slime Ball

	Water.shape: parallelogram
	Water -> Dough Ball

	Wheat Flour
	Wheat Flour -> Dough Ball

	Dough Ball
	Dough Ball -> Slime Ball

	Slime Ball
	Slime Ball -> _.Confectionary.Mashmallow: {
		style.stroke: "#336600"
	}
}

Confectionary: {
	style: {
		stroke: "#9673A6"
		stroke-width: 4
	}

	Sugar
	Sugar -> _.Alchemist.Fermented Spider Eye: {
		style.stroke: "#9673A6"
	}
	Sugar -> Caramel
	Sugar -> Chocolate
	Sugar -> Dark Chocolate
	Sugar -> White Chocolate
	Sugar -> Ruby Chocolate
	Sugar -> Mashmallow
	Sugar -> Mundane Potion
	Sugar -> Candy Cane

	Water.shape: parallelogram
	Water -> Caramel
	Water -> Mundane Potion
	Water -> Candy Cane
	Water -> Mashmallow

	Caramel.shape: cylinder
	Caramel -> Mashmallow

	Mundane Potion: "Mundane Potion\n(Sugar)" {
		shape: cylinder
	}
	Mundane Potion -> Candy Cane

	Candy Cane

	Crushed Cocoa
	Crushed Cocoa -> Cocoa Powder
	Crushed Cocoa -> Cocoa Butter

	Cocoa Powder

	Cocoa Butter
	Cocoa Butter -> Dark Chocolate
	Cocoa Butter -> White Chocolate

	Hot Chocolate.shape: cylinder
	Hot Chocolate <- Sugar #I should have done it this way initially
	Hot Chocolate <- Cocoa Powder
	Hot Chocolate <- Milk

	Cow in a Jar.shape: parallelogram
	Cow in a Jar -> Milk

	Milk.shape: cylinder
	Milk -> Chocolate
	Milk -> Dark Chocolate
	Milk -> White Chocolate
	Milk -> Ruby Chocolate

	Chocolate.shape: cylinder
	Chocolate -> Chocolate Bar

	Dark Chocolate.shape: cylinder
	Dark Chocolate -> Dark Chocolate Bar

	White Chocolate.shape: cylinder
	White Chocolate -> White Chocolate Bar

	Ruby Chocolate.shape: cylinder
	Ruby Chocolate -> Ruby Chocolate Bar

	Paper
	Paper -> Full Chocolate Bar
	Paper -> Full Dark Chocolate Bar
	Paper -> Full White Chocolate Bar
	Paper -> Full Ruby Chocolate Bar

	Chocolate Bar
	Chocolate Bar -> Full Chocolate Bar

	Dark Chocolate Bar
	Dark Chocolate Bar -> Full Dark Chocolate Bar

	White Chocolate Bar
	White Chocolate Bar -> Full White Chocolate Bar

	Ruby Chocolate Bar
	Ruby Chocolate Bar -> Full Ruby Chocolate Bar

	Full Chocolate Bar

	Full Dark Chocolate Bar

	Full White Chocolate Bar

	Full Ruby Chocolate Bar
}


Change LLM to Free Model

No longer priority since the API keys are not going to be an issue for them (given role based access control)


Navigation plugin

Currently we bundle the Navigation SDK for Android (https://github.com/mapbox/mapbox-navigation-android) with no explicit dependencies on the Map SDK. This makes the Navigation SDK light-weight, well-contained, and suitable of a wide range of applications.
However, there're some specific features that a navigation app would build on top of the Maps SDK (like route layers updated as the user navigate, or traffic https://github.com/mapbox/mapbox-plugins-android/issues/4). Let's bring this functionality as a navigation-focused plugin.
cc: @mapbox/navigation

Picking this ticket up, the plugin should be called something like navigation-viewport and begin by handling two different occurrences that depend on the MapboxMap object. The route line can be drawn in runtime styling with a casing. The other feature being camera adjustments for speed, maneuver zones, etc.

the plugin should be called something like navigation-viewport

Why not simply NavigationPlugin? Unless we envision more than one navigation plugin, that name seems the clearer option.

A great feature to have would be to give users the possibility of having the puck centered so the camera animates automatically when receiving indications.

@Guardiola31337 the navigation pucks independent from the navigation plugin, the puck can be found in the location layer plugin. For the camera animating as the user traverses along the route, this navigation plugin has the intention to handle this, though it's still in its early days.

The Navigation UI Plugin makes this ticket obsolete since it will depend on the map sdk. https://github.com/mapbox/mapbox-navigation-android/tree/master/navigation/libandroid-navigation-ui
closing.

@cammace is there a ticket on https://github.com/mapbox/mapbox-navigation-android where we could track the release of the new libandroid-navigation-ui module?

Not really, i'm a bit confused on how we will be tracking projects now with the new issue tracking through ZenHub. I'll work with @ericrwolfe on getting something setup.


Portuguese Translation [Work in progress]

Initial translation to PT

[x] 404 messages
[x] bitstream messages

Please tell me if i need to translate everything before merge, i can keep updating this PR until there.

Hi @vitorsilverio - many thanks for your translation! If you are willing to translate the entire catalog, yes, please, do it as multiple commits to this pull request & we'll finalize the review and the merge when you are done.
You're also welcome to contribute it in smaller pieces, but definitely preferred if you can do it entirely in the scope of a single pull request.

OK @bram-atmire i ll translate everything and ping you when i finish

@bram-atmire i finished the translation

I think i done something wrong when merge, a lot of files were added to my PR

Closing this, the translation is PR #525

@vitorsilverio I think it's because of some changes that were applied to master in the meanwhile. I think a the owner of the pull request, you should have a button somewhere that says REBASE.
Otherwise, it's also possible to close this pull request and start a new one.


Extended Property Commands needed

https://www.red-gate.com/simple-talk/sql/database-delivery/reading-writing-creating-sql-server-extended-properties/

Do you have any ideas on how this would be implemented? Would they be specific to each scope or would there be a generic set of extended property commands?
Generic

[Add/Remove/Get/Set]-DbaExtendedProperty

Specific

[Add/Remove/Get/Set]-DbaDbExtendedProperty
[Add/Remove/Get/Set]-DbaLoginExtendedProperty
[Add/Remove/Get/Set]-DbaDbUserExtendedProperty
...

Since in SMO I believe these are all based on one calls it would fall into the generic and then we may have to have an Object parameter that specifies which one you are dealing with... https://docs.microsoft.com/en-us/dotnet/api/microsoft.sqlserver.management.smo.extendedpropertycollection
However, doing this in SMO will likely be good bit of work considering there are likely no examples out there in docs. So if we go the T-SQL route it will still be generic because you only deal with one stored procedure: sp_addextendedproperty

I could see us making it easier on the user because the LevelTypes on that stored proc only accept a certain value based on what object. So we could have an ObjectType parameter and then ask for the name of it, then auto-fill in all the level parameters? You could either accept  a multi-part name (e.g. database.dbo.table) or we'd have multiple parameters to accept each one, but I see that as complex.

I did some more research on this. Turns out the SqlSmoObject has an ExtendedProperties property which makes the implementation of this pretty easy (see Example Code below) so it's just a matter of how to design it. Let me know what you think about my proposal below.
Proposal

Single set of commands named Get-DbaExtendedEvent, Set-DbaExtendedEvent, Add-DbaExtendedEvent, Remove-DbaExtendedEvent
ObjectType parameter with the below valid values (or some form of them)

AGGREGATE
ASSEMBLY
COLUMN
CONSTRAINT
CONTRACT
DATABASE
EVENT NOTIFICATION
FILEGROUP
FUNCTION
INDEX
LOGICAL FILE NAME
MESSAGE TYPE
PARAMETER
PARTITION FUNCTION
PARTITION SCHEME
PROCEDURE
QUEUE
REMOTE SERVICE BINDING
ROUTE
RULE
SCHEMA
SERVICE
SYNONYM
TABLE
TRIGGER
TYPE
VIEW
XML SCHEMA COLLECTION

Example Code
Get Database Extended Properties
# database level
$smo.Databases['WideWorldImporters'].ExtendedProperties['MyExtendedProperty']

# table level
$smo.Databases['WideWorldImporters'].Tables[0].ExtendedProperties['Description']

Creating Extended Property
$extendedProperty = New-Object Microsoft.SqlServer.Management.Smo.ExtendedProperty ($parent, 'Description', 'This is my description')
$extendedProperty.Create()

Removing Extended Property
$smo.Databases['WideWorldImporters'].ExtendedProperties['Description'].Drop()
$smo.Databases['WideWorldImporters'].ExtendedProperties.Refresh()

Updating Extended Property
$extendedProperty = $smo.Databases['WideWorldImporters'].ExtendedProperties['Description']
$extendedProperty.Value = 'MyNewValue'
$extendedProperty.Refresh()

ohhh that is so fantastic. i love it. sorry for the delay, been on vacation 🇨🇦 🍟
a -Type parameter with a validateset would be great. I'm not so sure about the name tho. Did you mean to say ExtendedEvent? I associate that with XEs. Also, are there any extended properties not associated with Databases? If not, can we go with -DbaDbExtendedProperty
Any interest in blogging about the set of commands after they are done for dbatools.io/blog?

ohhh that is so fantastic. i love it. sorry for the delay, been on vacation 🇨🇦 🍟
a -Type parameter with a validateset would be great. I'm not so sure about the name tho. Did you mean to say ExtendedEvent? I associate that with XEs. Also, are there any extended properties not associated with Databases? If not, can we go with -DbaDbExtendedProperty
Any interest in blogging about the set of commands after they are done for dbatools.io/blog?

Definitely did not mean ExtendedEvent! I'll take a further look to see if any reside outside a database and get back to you. I'd love the opportunity to throw out an article when they're done, thanks!


Debug adapter doesn't send pathMappings to local container

Issue Type: Bug
This is how isLocalHost() function is implemented: https://github.com/microsoft/vscode-python/blob/411d1d4ae7e3884a8ef9294a0aa1688dc05d0f37/src/client/debugger/extension/configuration/resolvers/base.ts#L108-L111
However, in my scenario, the python app I'm attaching to runs inside a docker container, and my dev laptop is the docker host. This means that I have to connect to localhost to debug the app, but localhost is not my local host; it's the container.
My guess is that there's a false positive in this code: https://github.com/microsoft/vscode-python/blob/411d1d4ae7e3884a8ef9294a0aa1688dc05d0f37/src/client/debugger/extension/configuration/resolvers/attach.ts#L123-L126
This is my launch configuration (there are several; the one that affects this issue is called "Attach Python debugger to running container"). You can see that it has lots of path mappings because this is a complex multi-root project. Also you can see that it connects to "host": "localhost".
If I enable debugpy logging inside the container, I will be able to see this attach request. Obviously, the breakpoints cannot resolve while debugging:

I can see that if I change my launch configuration to attach to "host": "<IP_ADDRESS>" instead of "host": "localhost" (which also happens to resolve to localhost but will return isLocalHost() -> false), this is the attach request that debugpy reports.
This looks more like what it should be. Now my breakpoints appear as properly mapped while debugging:

Note: randomly the problem just disappears and it connects properly with path mappings to localhost. Some colleagues with my same OS, the same project, commit and VSCode+extensions versions cannot reproduce. CC @joao-p-marques. However, I have noticed that it seems to work 100% of the time when using "host": "<IP_ADDRESS>". Weird bug... :dizzy_face:

Extension version: 2020.11.371526539
VS Code version: Code 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f, 2020-11-10T23:31:29.624Z)
OS version: Linux x64 5.9.8-200.fc33.x86_64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 4000)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: enabled_onvideo_decode: unavailable_offvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
15.48GB (0.51GB free)

Process Argv
--no-sandbox --unity-launch --crash-reporter-id 1b07b1f6-f187-42fc-aa9e-516fd1a4c83e

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome

XDG_SESSION_TYPE
x11

@Yajo I am assuming you are launching the debugger with python -m debypy --listen 5678, and mapping the port from the container to host using docker's port mapping.
As a workaround you should be able to use host as loopback. This should work in most cases, it will skip the naïve local host check.

I am assuming you are launching the debugger with python -m debypy --listen 5678, and mapping the port from the container to host using docker's port mapping.

Indeed.

As a workaround you should be able to use host as loopback. This should work in most cases, it will skip the naïve local host check.

That doesn't resolve:
$ ping loopback
ping: loopback: Name or service not known

@karthiknadig Does pydevd still need the path mappings for localhost case?

@int19h But this is in the container, so mapping is needed right?

Yes, but if I understand the issue correctly, the problem is that the fix-up code kicks in and replaces the manually configured path mappings. So if we don't actually need the fix-up anymore, removing it would fix this issue also.
But I'm not so sure about it... looking at the fix-up code, what it actually does is expand {workspaceFolder}, and also ensure that drive letters are lowercased in pathnames. This all sounds sensible, but then the question is: why are we only doing this for localhost attach? I suppose one could argue that C:/ is also a perfectly legal Unix path, so we don't want to touch that unless we know for sure that it's for Windows; but variable expansion is surely useful in all attach scenarios?
Anyway, I think the problem here is that it the fix-up code immediately returns an empty array if defaultLocalRoot is blank, instead of returning the original mappings. We must have regressed at some point, because it wasn't always doing that:
https://github.com/microsoft/vscode-python/blob/24365d193de0020af56ed8bd53f02a035b1703ea/src/client/debugger/extension/configuration/resolvers/attach.ts#L86-L126

Please notice that, after applying the workaround explained above, I hit https://github.com/microsoft/debugpy/issues/482 which also has relation with some wrong path mappings. May both be related?
I appreciate a lot your interest in these issues, such a powerful tool like this is becoming a nightmare when debugging. :crying_cat_face:

I don't think the two are directly related - it's just that unblocking you on this issue means that now debugpy gets to see the entirety of your path mappings, and we weren't handling the prefixes quite right when it's a complicated hierarchy. That issue already has a PR to fix it.

Nice, and it seems it got fixed already.
OK, then regarding thisissue, my question is: if you're developing locally (without containers), why in the world would you ever need any path mappings? 🤔
If there's no use for that, then possibly the best you can do is apply the mappings always, regardless it's localhost or not.

If the app being debugged is running on the same file system as VSCode, you do not need them, generally speaking. But you can still use path mapping to translate filenames in that case - e.g. if you're running your code from site-packages, but want the editor to show the original repo.

I think that's weird, but in any case it seems that removing the specific restrictions for localhost is the way to go.

Closing as stale


Selection area is invisible after update to >= 1.5

Do you want to request a feature or report a bug?
a bug
What is the current behavior?
After updating Selection to any version, greater then 0.1.4, I do not see the selection area on selection.
If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
It is quite difficult to extract the page I'm using Selection on out of the whole project.
But it seems to me that change is behaviour is caused by the that._clippingElement added after 0.1.4
How it worked before (v0.1.0):

How it works now (v0.1.5, same on 0.2.1):

Are there any restrictions on the style of html/body tags?
Your environment:
Selection-version: 0.1.5
Browser-version:  Chrome Version 73.0.3683.103
Operating-system:  macOS Mojave 10.14.4

I'm not aware of any, there was #29 where selectables was removed. The html and body  elements shouldn't be used as boundaries since selectionjs should be restricted to a specific area.
No problem, but cuold you provide your selection.js config? I'll try to reproduce it.
_clippingElement is used to restrict the visible area if the container element is scrollable.
Minor version indicated some kind of braking changes, I'll try to fix these as soon as possible :)

Wow, that was fast!
Thank you for the reply.
My config is as follows:
const selectionOptions = {

            class: 'policy-consumers-selection-area',

            selectables: ['.policy-consumers-list__consumer'],
            singleClick: false, // handled by the ng-click callback
            disableTouch: true,
            boundaries: ['.policies-editor-content__right', '.policies-editor-footer__right'],

            onSelect(evt) {
                // Check if clicked element is already selected
                const selected = evt.target.classList.contains(selectedConsumerClass);

                if (!evt.originalEvent.shiftKey) {
                    // Remove class from every element which is selected
                    evt.selectedElements.forEach(s => s.classList.remove(selectedConsumerClass));

                    // Clear previous selection
                    this.clearSelection();
                }

                if (selected) {
                    // Unselect element
                    evt.target.classList.remove(selectedConsumerClass);
                    this.removeFromSelection(evt.target);
                } else {
                    // Select element
                    evt.target.classList.add(selectedConsumerClass);
                    this.keepSelection();
                }
            },

            onStart(evt) {
                if (vm.dragStarted) {
                    // selection.cancel() is a wrapper
                    // for the selection._onTapStop()
                    // which throws an error almost every time (due to a bug)
                    this._onTapStop(evt);

                    const areaEl = evt.areaElement;

                    if (areaEl) {
                        areaEl.hidden = true;

                        $timeout(() => {
                            areaEl.hidden = false;
                        });
                    }

                    return;
                }

                // Remove class if the user don't pressed the shift key
                if (!evt.originalEvent.shiftKey) {
                    vm.deselectSelectedConsumers();
                    this.clearSelection();
                }
            },

            onStop(evt) {
                [...evt.selectedElements].forEach(x => {
                    const $e = angular.element(x);

                    const consumer = _.get(
                        vm,
                        [
                            'policiesToShowConsumersFrom',
                            Number($e.attr('policy-idx')),
                            $e.attr('item-prop'),
                            Number($e.attr('item-idx'))
                        ]
                    );

                    if (!consumer) {
                        return;
                    }

                    const consumerId = consumer[constants.ID_PROP_BY_POLICY_PROP[$e.attr('item-prop')]];

                    consumer.isSelected = !consumer.isSelected;

                    if (consumer.isSelected) {
                        vm.selectedConsumers[consumerId] = consumer;
                        vm.selectedConsumersCount++;
                    } else {
                        delete vm.selectedConsumers[consumerId];
                        vm.selectedConsumersCount--;
                    }
                });

                this.clearSelection();

                if ($scope.$root.$$phase !== '$apply' && $scope.$root.$$phase !== '$digest') {
                    $scope.$apply();
                }
            }
        };

and .policy-consumers-selection-area:
.policy-consumers-selection-area {
    background: rgba(0, 0, 255, 0.1);
    border-radius: 0.1em;
    border: 0.05em solid rgba(0, 0, 255, 0.2);
    z-index: 20;
}

Your lib is really awesome, by the way.

You're welcome :)
Okay, that's strange... If mounted, could you send me a screenshot of the selection-area container which is responsible for the clipping? After this I can investigate why it's clipped / invisible :) Like so:

red - Clipping element
green - Actual selection area

Here's the clipping element on page load:

And here it is after selecting a bunch of elements:

Selection area after selecting a bunch of elements:

I can provide you with a remote access to the working demo if that's ok

Yeah, solving this problem directly on the application itself would be the fastest way to examine the problem. This would be great! Furthermore, if the second image was taken after a selection (the area element has display: none), there's at the first view nothing suspicious in your Environment which would cause this problem.

I think I've got it working. Please try to open the following URL: demo.selection.keenetic.limited.
If it opens successfully (that can take a bit of time & reloads) use selection as login and as password.
I use Selection on the second tab ("Policy bindings") of the controlPanel/policies page.

This is a temporary build, living on my machine. I can make a more permanent solution if this one is too hard to use. Thank you once again for wanting to help.

Well, thank you for providing this demo and great communication to find it :) I found the problem, the clipping area don't have any z-index property, so the applied z-index on the selection-area element don't even take effect. After adding z-index: 1 to the clipping element it works.
Until I published a new version (will be very soon since this looks like a serious bug to me) you can use this piece of code in your selectionjs config to fix this:
onStart({selection}) {
        selection._clippingElement.style.zIndex = 1;
}

Well, thank you for providing this demo and great communication to find it :) I found the problem, the clipping area don't have any z-index property, so the applied z-index on the selection-area element don't even take effect. After adding z-index: 1 to the clipping element it works.
Until I published a new version (will be very soon since this looks like a serious bug to me) you can use this piece of code in your selectionjs config to fix this:
onStart({selection}) {
        selection._clippingElement.style.zIndex = 1;
}

WoW! This is so great ^_^
Thank you so much. I can't express how excited I am 🔥

Oh, GitHub discovered the fix-commit: dd9926bae52dad5f3c8eeb5a026b9c89dca4bdaa :D

@dsechin Thought I'll inform you I published v0.2.2 where this fix takes action :)

@Simonwep I know, that this issue is closed, but I would like to point out that I get the same behavior in my setup with the latest release.
I found a simple fix for it: wrap zIndex value in quotes:
            css(that._clippingElement, {
                overflow: 'hidden',
                position: 'fixed',
                transform: 'translate3d(0, 0, 0)', // https://stackoverflow.com/a/38268846
                pointerEvents: 'none',
                zIndex: '1' // <----------------------
            });

This way it work perfectly. Hope this helps.

Huh, now this is strange, the value of zIndex should be an integer as mentioned here in the official w3 draft 🤔
Is there any way to get hand on a reproduction in a JSFiddle? Because, even if the type for zIndex is still integer, if you use style.zIndex = '1' gives the same result as style.zIndex = 1.
Okay this is an actual a bug in the .css function. If I pass a integer in it it will get unified (with px as standard). So it'd result in zIndex: 1px which is invalid.
I'll fix this later today and roll out 1.4.1, I should pay attention to how my own utils work 😅

@dsechin Fixed in 5539f8b :) I've published 1.4.1 where this fix is applied!

@dsechin Fixed in 5539f8b :) I've published 1.4.1 where this fix is applied!

Thank you for the quick fix! ^_^


Swift-tools-version bump to 5.0

This fixes minimum deployment target version error when project generated in Xcode 12

@vvghost1 thanks for the fix. What are the steps to reproduce the "deployment target version error" in Xcode 12? I just want to check that the bug exists locally and confirm that it goes away with your update. Thanks 👍

@vvghost1 thanks for the fix. What are the steps to reproduce the "deployment target version error" in Xcode 12? I just want to check that the bug exists locally and confirm that it goes away with your update. Thanks 👍

@evgenyneu sorry for delayed answer. Steps to reproduce (using Xcode 12, swift-tools-version:5.x):

create empty package, swift package init
add KeychainSwift as package and target dependency
add import KeychainSwift to any source file (template one is ok)
generate Xcode project using swift package generate-xcodeproj

Now, if you will try to build generated project, you will have error "Compiling for iOS 9.0, but module 'KeychainSwift' has a minimum deployment target of iOS 14.x"

Thanks for instructions, yes I can reproduce the issue. A recommended way of adding KeychainSwift package to an Xcode project is by using the menu File > Packages > Add Package Dependency. This does not result in any errors for me, I just tested in Xcode 12.3, see project attached. Do you think you can use this approach, or do you still need to create Xcode project from command line?
DemoKeychainSwift.zip

@evgenyneu thank you for attention to this issue! I have already found a workaround, and, moreover, I had investigated that generate-xcodeproj is being deprecated: https://github.com/apple/swift-package-manager/pull/3062
However, I still think that bumping swift-tools-version is a good thing to reduce possible bugs in the future. Maybe you could do it with some additional changes later, it's up to you

Hello! What about current status with Xcode 13.2.1?

I'm using it in a native Swift (UIKit) app (version 19.0.0 -SPM).
It works fine (latest Xcode/Swift 5.5).

It'sI'm using it in a native Swift (UIKit) app (version 19.0.0 -SPM).

That's also the problem because SPM sees this lib as version 19.0.0 which is wrong because on GitHub there is a release 2.0.1. The mismatch is because 19 it's a tag in git and SPM cares only about tags. However this is different issue addressed here: https://github.com/evgenyneu/keychain-swift/issues/148

It works fine (latest Xcode/Swift 5.5).

Yeah, it works fine but Xcode displays a yellow warning because it wants to update this package into Swift 5. It's just outdated.

I generally don't run prerelease Xcode, unless there's an explicit reason.

I see but Xcode 13.2.1 was released on AppStore about 1 week ago.

Ah. I see. I have 13.2.1. I was wondering if there was an issue with a prerelease.
 I was wondering what caused it.
That release is a few years old, and very much out of date. It should probably be deleted, or a bunch of new releases, set to various tags, should be added (at least the 19.0.0 tag).
Thanks!

Done


Test finalized drop in editor api

Test for #142990

[ ] Mac @alexdima
[ ] Linux @karthiknadig
[x] Windows @andreamah

Complexity: 5
Create Issue

Summary
The drop into editor api has been finalized! This api lets extension hook into when something is dropped on a text editor
Testing
Use the drop into editor sample extension to test this API. Some things to test:

Check the documentation of the various api types
Check that you can handle drops from the VS Code explorer and from the OS
Try returning a workspace edit on DocumentDropEdit (for example, creating a new file)
Check that setting workbench.editor.dropIntoEditor.enabled disabled dropping into the editor
Try dropping into notebook cells

Works super well! 😊


chore: make it straightforward

ls /home may be a straightforward equivalent to get the list of users.

Thanks, @lucmaa


Tappable/clickable semantic nodes should have reasonable fallback role

Some framework widgets, such as ExpansionTile and Tab (via InkWell), and widgets authored by developers, would add a tap action to their respective semantics node, but would not pick a concrete role for the node, such as button, checkbox, radiobox, text field, combobox, link, etc.
On the web this translates to an element with a click event listener but without an ARIA role attribute. Some screen readers would look for the listener and say "double-tap to activate" (or whatever is appropriate for the form factor of the device). Some will not communicate that the node is interactive (https://github.com/flutter/flutter/issues/143852), prompting custom solutions such as this.
Proposal
When a tap action is present the framework always assigns a role to the node. If the developer does not specify one, the framework fallback to the most reasonable default (e.g. "button"). For the cases where it's preferable to communicate the role using a custom hint (like in the ExpansionTile case) we introduce a special role for that, in which case the engine would know that the role is communicated using means other than the ARIA role.
Taking this proposal to extreme, perhaps we should introduce a formal concept of "role" in the semantics tree. Currently the role is described using various flags that the engine pattern-matches on to assign it a formal role internally. Here's how the web engine does it. A formal role enum could improve the following:

Remove the guesswork from the engine.
All engine implementations would be in agreement about what role a particular semantics node plays.
Enable better validation/testing of nodes. For example, should a checkbox have the paste action?
Allow the engine to pick the best fallback when there platform does not directly support a role. Let's say we want to have a special role for Tab. ARIA does not define a formal "tab" role. However, there might be a combination of ARIA attributes that approximate it quite well. Right now, there's no way to tell if something is a tab, and the web engine just falls back to GenericRole that's also used for paragraphs of static text (which also doesn't have a role, and is pattern-matched onto "leaf node with a label").

Another use-case for a formal concept of role is when merging framework-side semantics node it would provide an unambiguous signal when two nodes can and cannot be merged. Essentially, if two nodes each has a role, the nodes are not merged. For example, something that claims to be a "button" would not be merged with something that claims to be a "paragraph". Today, they might.


[BUG]: [Crisis Communication] "chat" button on the adaptive card in Teams

Describe the bug
"chat" button on the adaptive card in Teams does not work as expected. When I click on the "Chat" button, it opens the chat with the Flow itself and not with the user who sent the request message.
Expected behavior
We expect the "Chat" button to open the chat with the user who sent the request, just like the "Email" button as it opens the new email to that user.

Hi,
This happens when you try to start a chat with yourself. It will return to the current view of your chat.

Hey Brian,
Good to see your message. Thanks and that makes sense. I was actually trying to open the chat from the message I sent myself. It works as expected with other users.


add VSR-I chassis type to support network functions based on the isa card

tested on 21.10.R3 and 22.10.R1

Just bringing my two cents, I have realized that my colleagues and myself
were using VSR-I a lot specially when we need to work with network
functions based on the ISA card normally on KVM but our labs were
completely manually created now available on vrnetlab. By the other hand
actually I was not aware about this function looks like is new and I think
that is a really good Idea.
I am the guy that just need to say thanks to you for all your great stuff!!!
BUILD-CONQUER-REPEAT
On Fri, 25 Nov 2022, 14:31 Roman Dodin, @.***> wrote:

Merged #97 https://github.com/hellt/vrnetlab/pull/97 into master.
—
Reply to this email directly, view it on GitHub
https://github.com/hellt/vrnetlab/pull/97#event-7893622564, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AUU3IVJVEQFBWCIJ54WSIGTWKDEU3ANCNFSM6AAAAAASK6Q4CY
.
You are receiving this because you were mentioned.Message ID:
@.***>


chore: InstallUnlockedPackageCollection missing space

Checklist
All items have to be completed before a PR is merged

[x] Adhere to Contribution Guidelines
[x] Updates to Decision Records considered?
[x] Updates to documentation at flxbl-sfp Guide considered?
[x] Tested changes?
[x] Unit Tests new and existing passing locally?

Thanks @alanjaouen


Let slack use an external logger

I wanted to supply a logger to your lib so I could fold in api debug logs with my chatbots logs. If you'd rather it be a struct member of api, I could do that; there are only a couple of places in the code that don't use api.DebugX.
Thanks for the great lib, made it pretty easy to get gopherbot going.

Thanks!


restart-workflows-fix

Issue was, the DELETE request needed a data field for it to work as we set the "Content-Type": "application/json"
Fix:
Since the requests library automatically adds "Content-Type": "application/json" if the data field is present. I removed this field from the default headers

Thanks, AFAIU from the docs it's only when we are using json instead of data. With a quick look, it think that's the case for us.

You're right, I got the terms mixed up


Publish replaced Save As

Followed the steps but found a doc bug under the Manual migration section.  Step 4 in the current doc says to:

Open each report in Power BI Report Builder, and then:
Verify all data sources and datasets are embedded in the report definition, and that they're supported data sources.
Preview the report to ensure it renders correctly.
Choose the Save As option, and then select Power BI service.

When you choose Save As, there is no option to select Power BI Service, it appears now the option should be Publish rather than Save As.  The doc should say:

Open each report in Power BI Report Builder, and then:
Verify all data sources and datasets are embedded in the report definition, and that they're supported data sources.
Preview the report to ensure it renders correctly.
**4. Choose the Publish option and then select Power BI service
Select your workspace
Provide a file name and click Save**

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f8c868cc-a15f-f870-ed4e-7b3d9dbd3ec0
Version Independent ID: 1c353bbb-038f-5ea9-eb10-98401dd0fddb
Content: Migrate SQL Server Reporting Services reports to Power BI - Power BI
Content Source: powerbi-docs/guidance/migrate-ssrs-reports-to-power-bi.md
Service: powerbi
Sub-service: powerbi-resource
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @tomattto2 -- thanks, good catch! I've updated the article. Change will be live tomorrow afternoon Pacific time Sept 8.


R200 start fails on Windows 8.1

I thought I'd share an experience I just had with the R200 so that others who run into this problem wouldn't have to figure it out themselves.
I had a problem with an R200 sensor on one Windows 8.1 computer where my own application and all of the provided samples failed with the message "no matching media type" (this comes from the set_subdevice_mode function in uvc-wmf.cpp). On other Win 8.1 computers (also Win 10) the same sensor with the same DCM version works perfectly. (I tried nearly all of the available DCM versions as well while trying to figure this problem out without any difference to the result.)
After many hours of searching the only difference between the computers I found was that in device manager the Microsoft UVC driver for the R200 devices (Depth, Left-Right, RGB) had a different version. The computer with the problem had the version 6.3.9600.16384 (21.6.2006), while the computers that worked had the version 6.3.9600.17217 (same date 21.6.2006 though). I normally have automatic Windows updates turned off on the problematic computer, so as a last resort I thought to apply all important and recommended available windows updates. To my surprise after the updates the sensor started working perfectly and the UVC driver version had also changed to match the other computers.
Summary: All samples fail on Win 8.1 with the message "no matching media type". Reason is most probably the UVC driver version 6.3.9600.16384, which doesn't play nicely with the R200 sensor. Windows update fixes the issue and changes UVC driver version to 6.3.9600.17217.

Required Info

Camera Model
R200

Firmware Version
1.0.72...

Operating System & Version
Windows 8.1 Pro

Build System
VS2013

We had similar problems on vanilla Windows 8.0 -- thanks for the update and glad you found a way to fix it!


input type="text" readonly class="form-control-plaintext" doesnt work in real life.

Unless I'm missing something (which is very possible).
<input type="text" readonly class="form-control-plaintext">

Just doesn’t really work in real life.
If it’s long and the screen is made smaller (mobile etc) it simply doesn’t show the whole text.
I would normally use something like a display list, but I liked the idea of inputs that became readonly instead.
I attempted a few work arounds but they all just didn’t really work. I turned all the text inputs to textarea inputs, but various CSS and raw JS resizing just wouldn’t play (and were bodges being honest).
This should be either updated to work everywhere (not hiding long inputs on smaller screens, textarea’s not working either with all its scrollbars and resize stuff). Or be simply documented out and use a display list (or whatever).
There really is no point having a display field that cuts off the text.

Bug reports must include a live demo of the issue. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and operating system details.

This is a saved reply.

.form-control-plaintext simply removes the visual styling of form controls (the border around them etc.) - nothing more, nothing less. the readonly part is the default browser behavior when it comes to readonly form controls. so it seems that your main issue/problem here is with how browsers handle readonly, rather than bootstrap's extra style that removes the borders etc.

^ Fwiw that was my assumption as well, pending a live demo reproducing the problem.

As I understand, the problem is when the text is longer than the input width. The text is cut. Using inputs for such cases will just not work. Of course, you can use span/div instead.
To reproduce, goto the first input on https://getbootstrap.com/docs/4.4/components/forms/#readonly-plain-text and set its width to 100px.

Thinking this is a won't fix. If you need complete normal text behavior, you likely should be using normal text elements instead of a modifier of the form-control, or using some text utilities as needed.
Open to revisiting if the @twbs/css-review team thinks it necessary.

tend to agree this is more an author choice thing. regardless of bootstrap or not, this is something that authors would need to decide for themselves even if they were using pure vanilla HTML.

Hi all, Sorry for my late response I've just been very busy.
My point really isn't about how it can be done, it's more about the Bootstrap documentation isn't clear about what this is for (and it's drawbacks).
I would normally use an HTML Description Lists to display Key : Value type data which (debatably) is how it should be done.
I noticed the hidden border text input way in the Bootstrap documentation and it seemed an interesting idea.
As this in truth doesn't really do (what Bootstrap seems to imply) it can be used for, due to the actual limitations of HTML itself I think better class naming or a clearer description should be added to the documentation.
I myself wasn't initially sure if it was something from Bootstrap that would override the HTML rules that I had overlooked.
As a fix this can be done with textareas and some JS to size (which I have managed to get to work now) but it wasn't really about fixing it as such being honest.
As I said in my original post "There really is no point having a display field that cuts off the text."
Hopefully that makes sense.


[T2] workloadnomitor 2020 10 28

https://github.com/Azure/sdk-release-request/issues/888

/azp run prepare-pipelines


[vcpkg] Add swig acquire

SWIG is a interface compiler that allows binding C and C++ to scripting languages like Python, Ruby, Tcl and others. It's purely a compile-time tool to generate the bindings agaisnt your code.
I have a future port that will use this however, even end-user applications may find it handy to just vcpkg_find_package_acquire_swig for windows instead of needing a separate system install.

also included in #11208

add SWIG_VERSION ?
  elseif(VAR MATCHES "SWIG")
    set(PROGNAME swig)
	set(SWIG_VERSION "4.0.2")
    set(PATHS "${DOWNLOADS}/tools/swig/swigwin-${SWIG_VERSION}")
    set(URL
      "https://jaist.dl.sourceforge.net/project/swig/swigwin/swigwin-4.0.2/swigwin-${SWIG_VERSION}.zip"
      "https://sourceforge.net/projects/swig/files/swigwin/swigwin-4.0.2/swigwin-${SWIG_VERSION}.zip/download"
    )
    set(ARCHIVE "swigwin-${SWIG_VERSION}.zip")
    set(HASH b8f105f9b9db6acc1f6e3741990915b533cd1bc206eb9645fd6836457fd30789b7229d2e3219d8e35f2390605ade0fbca493ae162ec3b4bc4e428b57155db03d)

add SWIG_VERSION ?
  elseif(VAR MATCHES "SWIG")
    set(PROGNAME swig)
    set(SWIG_VERSION "4.0.2")
    set(PATHS "${DOWNLOADS}/tools/swig/swigwin-${SWIG_VERSION}")${SWIG_VERSION}
    set(URL
      "https://jaist.dl.sourceforge.net/project/swig/swigwin/swigwin-${SWIG_VERSION}/swigwin-${SWIG_VERSION}.zip"
      "https://sourceforge.net/projects/swig/files/swigwin/swigwin-${SWIG_VERSION}/swigwin-${SWIG_VERSION}.zip/download"
    )
    set(ARCHIVE "swigwin-${SWIG_VERSION}.zip")
    set(HASH b8f105f9b9db6acc1f6e3741990915b533cd1bc206eb9645fd6836457fd30789b7229d2e3219d8e35f2390605ade0fbca493ae162ec3b4bc4e428b57155db03d)

Yea actually that'll be better

@BillyONeal
Remove-Item : Cannot remove item D:\downloads\tools\msys2\msys64\usr\bin\msys-2.0.dll: Access to the path

@Neumann-A
?

   if(CMAKE_HOST_WIN32)
...
       set(PATHS "${DOWNLOADS}/tools/swig/${SUBDIR}/${SUBDIR}")
...

...\vcpkg\downloads\tools\swig\swigwin-4.0.2\swigwin-4.0.2\swig.exe
enough of this, why so many extra nested folders?
 set(PATHS "${DOWNLOADS}/tools/swig/${SUBDIR}")
...\vcpkg\downloads\tools\swig\swigwin-4.0.2

Please fix it if you know how and where. It the strange zip extraction which creates the subfolders. Paths is just a hint where to find it.

   if(CMAKE_HOST_WIN32)
...
       set(PATHS "${DOWNLOADS}/tools/swig/${SUBDIR}/${SUBDIR}")
...

Can be closed ITK PR was merged.


Button opens in new window

We need to allow people to open the button link in a new window (like the one in the image block).

Pr: https://github.com/kitconcept/volto-button-block/pull/10


CI workflow: Canonical 'Headless' usage of the CLI

Which Category is your question related to?
Headless usage of the CLI
While setting up CI workflow I followed headless_configure_project with a simple usecase of pushing the backend resources changes with amplify push.
Presented example:
REACTCONFIG="{\
\"SourceDir\":\"src\",\
\"DistributionDir\":\"dist\",\
\"BuildCommand\":\"npm run-script build\",\
\"StartCommand\":\"npm run-script start\"\
}"

AWSCLOUDFORMATIONCONFIG="{\
\"configLevel\":\"project\",\
\"useProfile\":true,\
\"profileName\":\"default\",\
\"accessKeyId\":\"$AWS_ACCESS_KEY_ID\",\
\"secretAccessKey\":\"$AWS_SECRET_ACCESS_KEY\",\
\"region\":\"ap-southeast-1\"\
}"

AMPLIFY="{\
\"projectName\":\"headlessProjectName\",\
\"defaultEditor\":\"code\"\
}"
FRONTEND="{\
\"frontend\":\"javascript\",\
\"framework\":\"react\",\
\"config\":$REACTCONFIG\
}"

PROVIDERS="{\
\"awscloudformation\":$AWSCLOUDFORMATIONCONFIG\
}"

./node_modules/.bin/amplify configure project --amplify $AMPLIFY --frontend $FRONTEND --providers $PROVIDERS

fails with SyntaxError: Unexpected end of JSON input.
Changing $FRONTEND to project_config.json exact structure also fails:
JAVASCRIPT_CONFIG="{\
\"framework\":\"react\",\
\"config\":$REACTCONFIG\
}"

FRONTEND="{\
\"projectName\":\"magicproj\",\
\"version\":\"2.0\",\
\"frontend\":\"javascript\",\
\"javascript\":$JAVASCRIPT_CONFIG,\
\"providers\":[\"awscloudformation\"]\
}"

Not specifying --frontend $FRONTEND would have this error gone, now CLI would complain about non-existence of ./amplify/.config/local-env-info.json and ./amplify/backend/amplify-meta.json (using default amplify initialized project with default .gitignore).
After committing ./amplify/backend/amplify-meta.json to git and generating ./amplify/.config/local-env-info.json it does work with:
REACTCONFIG="{\
\"SourceDir\":\"src\",\
\"DistributionDir\":\"dist\",\
\"BuildCommand\":\"npm run-script build\",\
\"StartCommand\":\"npm run-script start\"\
}"

AWSCLOUDFORMATIONCONFIG="{\
\"configLevel\":\"project\",\
\"useProfile\":false,\
\"accessKeyId\":\"$AWS_ACCESS_KEY_ID\",\
\"secretAccessKey\":\"$AWS_SECRET_ACCESS_KEY\",\
\"region\":\"ap-southeast-1\"\
}"

AMPLIFY="{\
\"projectName\":\"magicproj\",\
\"defaultEditor\":\"code\"\
}"

PROVIDERS="{\
\"awscloudformation\":$AWSCLOUDFORMATIONCONFIG\
}"

echo '{"projectPath": "'"$(pwd)"'","defaultEditor":"code","envName":"dev"}' > ./amplify/.config/local-env-info.json
./node_modules/.bin/amplify configure project --amplify $AMPLIFY --providers $PROVIDERS --yes
./node_modules/.bin/amplify env pull --yes
./node_modules/.bin/amplify push --yes

My question is: Am I doing a right thing here? It looks a bit cumbersome and I wasn't actually able to find any documentation on this except headless-usage-of-the-cli. Another question: why is ./amplify/backend/amplify-meta.json is in default .gitignore.?

@ambientlight
you might want to take a look at some sample headless scripts out here - https://github.com/aws-amplify/amplify-cli/blob/master/packages/amplify-cli/sample-headless-scripts/headless_push.sh

@kaustavghosh06: yeah I have followed them. It wonder if scripts for configure project are outdated.
we can store all the jsons needed by configure projects into ci_config.json in the repository and then feed it to amplify configure project with jq, but isn't it's what should be done on amplify side, it feels a bit strange feeding jsons to cli, so I wondered if this is the only way to do this?

@ambientlight Thanks for the feedback. What we could probably do is introduce a flag -c which accepts a config file path and read the JSON from the that file. Something like amplify push -c <file-path>. Do you think that would be a better approach?

@kaustavghosh06: yes, that would be an improvement definitely.
Also another possibility would be to have all minimal configuration consolidated in /amplify/.config/project-config.json. Then we won't need to pass anything to amplify push at all.
Say without AWSCLOUDFORMATIONCONFIG set cli can use AWS_PROFILE or AWS_ACCESS_KEY_ID , AWS_SECRET_ACCESS_KEY , AWS_DEFAULT_REGION environment variables.


Remove or invalidate Daycodes

Class control page may be useful if it has a remove daycode functionality.

What exactly does this mean? Why is this useful? Like remove the day-code if it is distributed too much?

Done


Add ability to turn on and off progress bars

Not everyone wants to see progress bars when downloading models/datasets as tqdm can clog the logs pretty easily. That's why we have a mode in Transformers to deactivate tqdm when setting some env variable using these utils.
Currently, Transformers enforces huggingface_hub uses this tqdm class by calling hf_hub_download under a contextmanager that monkey-patches huggingface_hub.file_download.tqdm. It would be much nicer if we could rely on any solution huggingface_hub implements instead :-)

Hi @sgugger, thanks for creating this issue. Seems legitimate to do this in huggingface_hub. From an API point of view, how would you see it ?
From a usability perspective, how would you prefer it ?
Either directly via a HF_HUB_DISABLE_PROGRESS_BARS env variable ? If you already have an env variable for it in transformers, we should align on the name.
Either have an helper to globally disable tqdm ? For example:
def disable_progress_bars() -> None:
   (...)

def enable_progress_bars() -> None:
   (...)

Or have a context manager to temporary disable tqdm ? Something like:
def some_function_in_transformers(...):
    (...)
    with huggingface_hub.no_progress_bars():
        hf_hub_download(my_file)

Implementation-wise, the EmptyTqdm class seems nice but we would need to adapt it for huggingface_hub to have some.close() or .update() methods used here or here. Otherwise, what do you think about the proposition mentioned in this comment to replace the EmptyTqdm ? Do I miss a use case that is not handled by it ?

I think offering options 1 and 2 would be nice: the env variable for individual users, and the helpers for libraries using huggingface_hub like transformers (I can patch an env variable from Transformers but that does not feel clean ;-) )
The context manager seems less useful as I feel users will either want progress bars all the time or never. I used this solution when monkey-patching huggingface_hub just to make sure the monkey-patch was properly undone.
The suggestion in the forcing disable in a subclass to replace EmptyTqdm works well I believe.

Thanks for the feedback :)
Seems reasonable. Will try to make a PR about it soon

Closed by https://github.com/huggingface/huggingface_hub/pull/987