SDL migration including function definition fails on commit with "InternalServerError: relation ... does not exist"

EdgeDB Version: alpha 4
OS Version: Ubuntu 20

On an empty database run the following migration:
START MIGRATION TO {
module default {
	type User {
		optional property name -> str;
	}

	function get_user(name:str) -> User
	USING EdgeQL $$
		select User {
			name,
		}
		filter {
			.name = name
		}
		limit 1
	$$;
}

};
POPULATE MIGRATION;
COMMIT MIGRATION;

The commit fails with the following error:

InternalServerError: relation "edgedb_22db0c59-d1e6-11ea-bd31-efd5a96c52d1.a7cb9161-d4ab-11ea-8e37-2d90af0bf1de_t" does not exist

Same issue:
START TRANSACTION;
START MIGRATION TO {
    module default {
        type User;

        function create_user() -> SET OF User
        {
            using EdgeQL $$
            SELECT User
            $$;
        }
    };
};

POPULATE MIGRATION;

Temp fix: CREATE TYPE User; before migration.

There's more to this:
START TRANSACTION;
CREATE TYPE User;
START MIGRATION TO {
    module default {
        type User {
            required property nickname -> str;
        }

        function create_user() -> SET OF User
        {
            using EdgeQL $$
            SELECT User
            FILTER .nickname = 'test'
            $$;
        }
    };
};

POPULATE MIGRATION;
COMMIT MIGRATION;
# ERROR: InternalServerError: column User~2.nickname does not exist

The same error also happens when type referenced by function is updated in the same migration.
I encountered this when I renamed one of the fields in type and also created function referencing this type.
If I remove function definition from migration, run it, add function back and run again, it works fine.
Creating function before migration using DDL also fixes this.

Yeah, this is an issue with internal SQL command ordering, I'll look into it soon.

The issue here is that the function references the type's inheritance view and not the table, and inheritance views are always all updated at the end of the ddl script. So even if the table is created/updated before the function, the view still isn't.

This is fixed


Create Merge_Sort.java

Need to Update Contribution.md too.

Welcome to HacktoberFest-22
@codecode12345  ..😊😊🚀🚀


Release 1.10.1

We already have Camel Quarkus 2.12.0 released, we should a quick release for 1.10.1 and camel-k-runtime 1.15.0, so we could leverage 3.18.1 release, there is also 3.18.2 on vote, but we don't have the related camel quarkus released for it, so I'd like to have a camel-k release for each LTS 3.18.x release. Thoughts?

We have some troubles with vertx and knative at the moment: https://github.com/apache/camel-k-runtime/pull/886

would be good to include #3657 in 1.10.1

#3671 should be included. I'll open a backport PR

Camel-K-runtime 1.15.0 Staged: https://repository.apache.org/content/repositories/orgapachecamel-1472/

Camel-Kamelets 0.9.1 staged: https://repository.apache.org/content/repositories/orgapachecamel-1474/

If we're not in a hurry, I'd like to fix and backport #3674

No rush. The runtime and kamelets was more or less prepared, for camel-k we can have a release next week.

I think we are in good shape, when everything is in place I'll start the release process.

What is still missing for starting release process?

I've merged #3692. We may want to rebase #3718 to make sure that the fix is correct. Then, I think we're ready to go.

Thanks.

Just created #3721 if it can make it.

I think this one too should go in 1.10.x https://github.com/apache/camel-k/pull/3723
I'll start the release on Monday. Just give me green light.

@oscerd I am going to backport that one as well.
I've merged all the other standings PRs. We should be good to go. We eventually need to have a deeper look at the native tests as they are not stable.

Backport at #3724

All changes are merged now. We will have to review the suite of native test: follow up issue in #3726
:green_circle: for me

I'm starting the release process.

on vote.


Fix CR

Fix

Display  "Encrypted message" if the message is encrypted.
check on locale decimal separator before compare value.

Encrypted message - working
Validation is not working because it's always max amount as<PHONE_NUMBER> where I have mosaic with supply<PHONE_NUMBER>000000000

After change we go back to original problem:

After fixes it seems fine :)


Use is not syntax part 2

PR Summary

More !(foo is T) -> foo is not T
Convert boolean logic to DNF form

PR Context
Follow-up #13323
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[NA] Experimental feature(s) needed

[NA] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[NA] Documentation needed

[NA] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[NA] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[NA] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

@anmenaga Can you please review?

@xtqqczze Yup; it was marked for Review - Maintainer;  we'll take a look at it.

@PowerShell/powershell-maintainers reviewed this PR and agreed to accept it for 7.2-preview based on the following reason(s):

The changes make the code more readable, but the chance of regression due to potentially incorrect changes are relatively high and thus we should delay merging it until after the 7.1-RC1 release branch is created.

Ser to Draft till 7.2 Preview1.

@iSazonov Please reopen.

@anmenaga @daxian-dbw Can we merge to 7.2 Preview1?

rebased


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

Coverage remained the same at 91.489% when pulling 465cc15929e4838f59ec4f624e311d63617e0097 on template-sync-1 into 7475200ef176391b9029cc6181add734dbc01ac8 on master.


"Synchronization is currently in progress" comes up in confusing situation

Hi team,
I moved this from here: https://github.com/MicrosoftDocs/azure-docs.nl-nl/issues/548
@valentijnscholten commented 8 hours ago — with docs.microsoft.com
Hi,
The "Synchronization is currently in progress" is also shown when somebody else has left the Azure AD Connect wizard open (when used on a server, multiple users can be logged in - even in disconnected state).
Today I spent quite some time trying to the kill the alleged "in progress sync" only to find out there was some wizard open in somebody else disconnected session :)
Ideally the (error) message should be changed, but in the mean time it might be good to mention this scenario on this page as the wizard will lead you here when you click "Learn more" in the error message.
Valentijn

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

ID: c2026376-29c3-49fe-c0e4-a766e46aab68
Version Independent ID: 0803163d-8b43-4d27-c0ef-14db64ff2061
Content: Azure AD Connect sync: Scheduler
Content Source: articles/active-directory/hybrid/how-to-connect-sync-feature-scheduler.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@CeciAc Thanks for your feedback! We will investigate and update as appropriate.

hey @valentijnscholten thank you for your feedback, we're currently looking into this and will let the product team know about this issue further accordingly.
That being said we will look into adding a note here to let people know that check if there are any other sessions that may have AAD Connect wizard open.
Thanks for letting us know about this!
cc : @billmath

I will follow up with engineering.  If there is a need to add a supportability note here we will address this.  Thanks!
#please-close


Software PLL issues and configuration for LMS4xxx

Problem description
We are using an LMS4xxx and we have set Laser in Software mode (using sopas) to be able to switch on and off the laser according to our need. However, we have notice this warning:
[WARN] [1699952842.940003742] [sick_scan]: 400 of 28578224 packets dropped (0.0 perc.), maxAbsDeltaTime=0.000
[WARN] [1699952842.940072885] [sick_scan]: More packages than expected were dropped!!
Check the network connection.
Check if the system time has been changed in a leap.
If the problems can persist, disable the software PLL with the option sw_pll_only_publish=False  !
[WARN] [1699952907.894838182] [sick_scan]: Timeout during waiting for new datagram

This is our configuration file:
<launch>
    <arg name="hostname" default="<IP_ADDRESS>"/>
    <arg name="cloud_topic" default="cloud"/>
    <arg name="frame_id" default="L3"/>
    <node name="sick_lms_4xxx" pkg="sick_scan" type="sick_generic_caller" respawn="false" output="screen" required="true">

        <!-- default values: -->
        <!--
          <param name="scanner_type" type="string" value="sick_tim_5xx" />
          <param name="min_ang" type="double" value="-2.35619449" />
          <param name="max_ang" type="double" value="2.35619449" />
          <param name="intensity" type="bool" value="True" />
          <param name="skip" type="int" value="0" />
          <param name="time_offset" type="double" value="-0.001" />
          <param name="publish_datagram" type="bool" value="False" />
          <param name="subscribe_datagram" type="bool" value="false" />
          <param name="device_number" type="int" value="0" />
          <param name="range_min" type="double" value="0.05" />
        -->
        <param name="scanner_type" type="string" value="sick_lms_4xxx"/>

        <!-- -20 deg Up -->
        <!--<param name="min_ang" type="double" value="-0.34906585"/>-->

        <!-- +35 deg  Buttom -->
        <!--<param name="max_ang" type="double" value="0.34906585"/>-->

        <param name="min_ang" type="double" value="-0.34906585" />
        <param name="max_ang" type="double" value="0.34906585" />

        <param name="use_binary_protocol" type="bool" value="true"/>
        <param name="range_max" type="double" value="3.5"/>
        <param name="range_min" type="double" value="0.3"/>
        <param name="intensity" type="bool" value="True"/>

        <param name="hostname" type="string" value="$(arg hostname)"/>
        <param name="cloud_topic" type="string" value="$(arg cloud_topic)"/>
        <param name="frame_id" type="str" value="$(arg frame_id)"/>
        <param name="port" type="string" value="2112"/>
        <param name="timelimit" type="int" value="5"/>
        <param name="min_intensity" type="double" value="0.0"/> <!-- Set range of LaserScan messages to infinity, if intensity < min_intensity (default: 0) -->
        <param name="sw_pll_only_publish" type="bool" value="true"/>
        <param name="use_generation_timestamp" type="bool" value="true" />

        <param name="start_services" type="bool" value="True" />                  <!-- Start ros service for cola commands, default: true -->
        <param name="message_monitoring_enabled" type="bool" value="True" />      <!-- Enable message monitoring with reconnect+reinit in case of timeouts, default: true -->
        <param name="read_timeout_millisec_default" type="int" value="5000"/>     <!-- 5 sec read timeout in operational mode (measurement mode), default: 5000 milliseconds -->
        <param name="read_timeout_millisec_startup" type="int" value="86400000"/>   <!-- 120 sec read timeout during startup (sensor may be starting up, which can take up to 120 sec.), default: 120000 milliseconds -->
        <param name="read_timeout_millisec_kill_node" type="int" value="250000"/> <!-- 150 sec pointcloud timeout, ros node will be killed if no point cloud published within the last 150 sec., default: 150000 milliseconds -->
        <param name="client_authorization_pw" type="string" value="F4724744"/>    <!-- Default password for client authorization -->

    </node>

</launch>

In this setup, the read_timeout_millisec_kill_node parameter causes the ROS node to restart if no pointcloud is received within 25 seconds. This situation arises when the laser stops. After restarting, the software enters PLL mode and generates a warning. This error does not occur when the laser is in free-running mode.
Questions

Do you think this have an impact on the timestamp generated by the software pll?

There is a way to disable the timeout? (all the timeout, timer_kill_node, timeout_startup and timeout_default?

What is the correct way to use the software pll?  How this parameters should be set:

        <param name="sw_pll_only_publish" type="bool" value="true"/>
        <param name="use_generation_timestamp" type="bool" value="true" />

Note
We are using ROS2 humble and this is commit of sick_scan_xd we are using:
sick_scan_xd
commit d3fb67d703866a8e0f22650bbd1178f43bac511e (HEAD -> master, tag: 2.10.2, origin/master, origin/HEAD)

Thanks for your feedback and sorry for the late reply. sick_scan_xd converts the lidar timestamp to the ROS system time using a Software PLL. The difference between the lidar timestamp and the ros timestamp when receiving the scan data is computed and a linear regression between lidar and ros time is continously calculated. See https://github.com/SICKAG/sick_scan_xd/blob/master/doc/software_pll.md for details.
If a TCP packet is delayed due to network traffic, the distance between lidar and ros timestamp can differ from the values calculated so far. In this case, the packet is not used to adjust the Software PLL. If this happens occasionally like 400 of 28578224 packets dropped (0.0 perc.), it will have very little or no impact on the timestamps generated. If this happens often, this indicates too high network traffic and may cause inaccurate timestamps.
The default settings, i.e. both sw_pll_only_publish and use_generation_timestamp set true, are correct and should not be modified unless for special applications.
To disable all timeouts, you can disable message monitoring and set all timeouts to max values:
<param name="message_monitoring_enabled" type="bool" value="False" />         <!-- Enable message monitoring with reconnect+reinit in case of timeouts, default: true -->
<param name="read_timeout_millisec_default" type="int" value="2147483648"/>   <!-- 5 sec read timeout in operational mode (measurement mode), default: 5000 milliseconds -->
<param name="read_timeout_millisec_startup" type="int" value="2147483648"/>   <!-- 120 sec read timeout during startup (sensor may be starting up, which can take up to 120 sec.), default: 120000 milliseconds -->
<param name="read_timeout_millisec_kill_node" type="int" value="2147483648"/> <!-- 150 sec pointcloud timeout, ros node will be killed if no point cloud published within the last 150 sec., default: 150000 milliseconds -->


add blog shenzhen meetup

Fixes # .
Make sure these boxes are checked before creating your pull request -- thank you!

[x] Add Blog Header, including title, author, date.
e.g.

---
 title: "'Score Your Face Photo' a ML&Wechaty practice"
 date: 2017-09-18 09:00 +0800
 author: huyingxi
 ---
 > Author: [@huyingxi](https://github.com/huyingxi/wechaty_selfie) enjoying ML&Wechaty at BUPT

[x] Keep all filenames & url as lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor instead of 2017-10-06-WeChat PC Impactor,
[x] Embed the photo & video before publishing, save all external file to the blog /download/2018 directory.
[x] Add <!--more--> section to just show the abstract in blog homepage.
[x] Add teaser image for the blog
[x] Add your self as an author to the author data file at https://github.com/wechaty/wechaty.github.io/blob/master/_data/authors.yml with your GitHub username. And please also remember to reference yourself with the Github username in your blog post, so that we can have nice author information besides your blog after we published it!

See more

Since we change the template or wechaty blog, we have a break change:
Before
You should add your profile at author.yml
After

You should create a file at _developers named as yourname.md
the file should begin with:

---
name: Jiarui LI (李佳芮)
site: https://lijiarui.github.io
bio: 句子互动创始人 & CEO，微软人工智能最具价值专家 (AI MVP)
avatar: /assets/developers/lijiarui/avatar.png
email<EMAIL_ADDRESS>twitter: https://weibo.com/u/2175505900
---

For example:

lijiarui.md: https://github.com/wechaty/wechaty.github.io/blob/master/_developers/lijiarui.md
It will shown like this on wechaty blog: https://wechaty.github.io/developers/lijiarui/

Looking forward to your profile file at the _developers folder!

ping @dchaofei

@lijiarui done.


Fix a thinko.

I was working on c20abe570d5a163805f01dce4991b32834e208c5 and 03bfadea60278281b9f1a641109d87e8614cc0eb at the same time and I forgot to update to use the new API in 03bfadea60278281b9f1a641109d87e8614cc0eb before I commited c20abe570d5a163805f01dce4991b32834e208c5. Sorry!
To be clear the thinko was just I used something that is only around in asserts builds in code that also builds without asserts. = /.

@swift-ci smoke test


Help text for concrete sections

Describe the bug
Release 2.02, concrete_sections.py
The arguments b and d in concrete_rectangular_section and concrete_tee_section represent the section width and depth respectively, and that is how they are used in the documentation and the function description in the help text, but the function parameter help text says:
:param float b: Concrete section depth
:param float d: Concrete section width
The tee_section also has:
:param float b_f: Concrete section flange depth
:param float d_f: Concrete section flange width

Thanks again @DougAJ4!
Fixed with 6446cb9.


If a chain is specified in [[accounts]] or [[validators]] but no [[chains]] section, then it panics

If a chain is specified in [[accounts]] or [[validators]], for example:
[[validators]]
name = "ceph-val-cosmos"
valoper = "cosmosvaloper16k579jk6yt2cwmqx9dz5xvq9fug2tekvlu9qdv"
chain = "cosmoshub"

but no [[chains]] section with a name = cosmoshub, then the application panics when running

Closed by #65


Settings file creates new asset if moved

Heya again,
I just thought of this because I just ran across it again.  I would say this is more of a nuisance probably than a bug, but if you try to relocate the HierarchyDecorator folder from Asset/HierarchyDecorator to something like Assets/Standard Assets/HierarchyDecorator, or anywhere at all aside from just Assets/ it will automatically create a new Asset/HierarchyDecorator/Settings.asset and reference that. I am guessing that it is hardcoded for that path as even if I try to take my old settings file that I had a bunch of changes in, delete the new one and move my old one there, it will just create a new one again right away. So then I had to recreate all my settings, and I was stuck with a standalone file within the Asset/HierarchyDecorator folder when I wanted the whole thing moved to a subfolder.
The separation of the main files from the settings file is really only a concern since I have the actual files in the project instead of added as a package, but being able to move the settings file/folder is definitely something most folks like to do. I try to keep my top level folder clean and put third party assets and what not in the /Standard Assets/ folder.
Should you be interested, I came up with a decent way to handle this a while back that I have used in a few projects and it has done pretty well for me. Here is a link to my settings ScriptableObject, then I just have my main static class check the location of the settings object and update its location.
It kicks off here.
https://github.com/instance-id/AboveAverageInspector/blob/16c8295c6317ee11c8e1d947020ca9f7e9962504/Assets/instance.id/Scripts/idConfig.cs#L92
and here is where it determines it's path.
https://github.com/instance-id/AboveAverageInspector/blob/16c8295c6317ee11c8e1d947020ca9f7e9962504/Assets/instance.id/Scripts/System/AAIConfiguration.cs#L192
Now that I think about it though, I am not quite sure how it will react when it is located in a package. It may end up not being useful at all, actually, lol. I may have to make some adjustments once I actually go that route and test it out.
Thanks,
-MH

Hey there MostHated, I apologize for the lack of content or versions for this, been more busy than expected.
So I've setup settings to now be free to be moved anywhere in the project.
This was on the cards to be fixed for a while and I knew it really had to change.
You made a good point of packages too in which I personally wasn't sure how it handles them.
So settings are stored locally within your assets rather than packages. I don't see any problem with this currently, unless they really should be within the package.
I've set it up to:

Look for settings at a saved path stored within EditorPref
If that exists, load those settings to use
If not, look through the entire project with the settings type for a settings asset (then load the first found)
Finally, if no settings are found create one.
Store the new path if required in EditorPrefs

This will be part of the next push along with some other changes
I'll keep this comment open for now, just in case are still not working to some degree after the push

I'm assuming this is all working now, so I'm going to close this, but if any problems come up again I'll reopen it if required

It's been discovered that when this is installed via packages, it'll not recreate settings,
making a fix for the next push

Actually, after further testing, it does seem to work fine, and was potentially due to there being settings within the package itself
I'm going to handle default settings with the next push by storing into JSON then parsing back to a settings instance if one is deleted. This way the default settings as they are right now can be updated easily and stored somewhere flexible

I apologize for opening this again, then closing


Image for Docker App on Docker Hub

Description
It'd be helpful if there was an image for Docker App on Docker Hub, just like the docker/compose image for Docker Compose. I'm experimenting with Docker App in my GitLab CI pipelines, but I have to create my own image for it, right now.
Steps to reproduce the issue:

Go to https://hub.docker.com/r/docker/app/.
Sad face.

Describe the results you received:
There is no Docker App image on Docker Hub.
Describe the results you expected:
An image for Docker App, perhaps at docker/app.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
N/A
Output of docker-app version:
N/A
Output of docker info:
N/A
Additional environment details (AWS, VirtualBox, physical, etc.):

Thanks for the suggestion, definitely a good idea.

Thank you @kinghuang for filling this issue!

I, too, am interested in this exact scenario. Looking to build/consume app images in CI builds.

In the meantime, I do have my own image at mikesir87/docker-app and will update as new releases are made. Feel free to use/send PRs if the need arises.
I will gladly dispose of it once an official one is created. 👍


Failed to run the inference test step for Vi-en but training completed without error.

python -m nmt.nmt  --out_dir=nmt_model/ --inference_input_file=nmt_data/tst2013.vi --inference_output_file=nmt_model/output_infer.en
Job id 0
Loading hparams from nmt_model/hparams
saving hparams to nmt_model/hparams
saving hparams to nmt_model/best_bleu/hparams
attention=
attention_architecture=standard
batch_size=128
beam_width=0
best_bleu=5.809653463551168
best_bleu_dir=nmt_model/best_bleu
bpe_delimiter=None
check_special_token=True
colocate_gradients_with_ops=True
decay_factor=0.98
decay_steps=10000
dev_prefix=None
dropout=0.2
encoder_type=uni
eos=
epoch_step=0
forget_bias=1.0
infer_batch_size=32
init_op=uniform
init_weight=0.1
learning_rate=1.0
learning_rate_warmup_factor=1.0
learning_rate_warmup_steps=0
length_penalty_weight=0.0
log_device_placement=False
max_gradient_norm=5.0
max_train=0
metrics=['bleu']
num_buckets=5
num_embeddings_partitions=0
num_gpus=1
num_layers=2
num_residual_layers=0
num_train_steps=12000
num_translations_per_input=1
num_units=32
optimizer=sgd
out_dir=nmt_model/
override_loaded_hparams=True
pass_hidden_state=True
random_seed=None
residual=False
share_vocab=False
sos=
source_reverse=False
src=vi
src_max_len=50
src_max_len_infer=None
src_vocab_file=nmt_data/vocab.vi
src_vocab_size=7709
start_decay_step=0
steps_per_external_eval=None
steps_per_stats=100
test_prefix=None
tgt=en
tgt_max_len=50
tgt_max_len_infer=None
tgt_vocab_file=nmt_data/vocab.en
tgt_vocab_size=17191
time_major=True
train_prefix=None
unit_type=lstm
vocab_prefix=None
creating infer graph ...
num_layers = 2, num_residual_layers=0
cell 0  LSTM, forget_bias=1  DeviceWrapper, device=/gpu:0
cell 1  LSTM, forget_bias=1  DeviceWrapper, device=/gpu:0
cell 0  LSTM, forget_bias=1  DeviceWrapper, device=/gpu:0
cell 1  LSTM, forget_bias=1  DeviceWrapper, device=/gpu:0
start_decay_step=0, learning_rate=1, decay_steps 10000, decay_factor 0.98, learning_rate_warmup_steps=0, learning_rate_warmup_factor=1, starting_learning_rate=1
Trainable variables
embeddings/encoder/embedding_encoder:0, (7709, 32),
embeddings/decoder/embedding_decoder:0, (17191, 32),
dynamic_seq2seq/encoder/rnn/multi_rnn_cell/cell_0/basic_lstm_cell/kernel:0, (64, 128), /device:GPU:0
dynamic_seq2seq/encoder/rnn/multi_rnn_cell/cell_0/basic_lstm_cell/bias:0, (128,), /device:GPU:0
dynamic_seq2seq/encoder/rnn/multi_rnn_cell/cell_1/basic_lstm_cell/kernel:0, (64, 128), /device:GPU:0
dynamic_seq2seq/encoder/rnn/multi_rnn_cell/cell_1/basic_lstm_cell/bias:0, (128,), /device:GPU:0
dynamic_seq2seq/decoder/multi_rnn_cell/cell_0/basic_lstm_cell/kernel:0, (64, 128), /device:GPU:0
dynamic_seq2seq/decoder/multi_rnn_cell/cell_0/basic_lstm_cell/bias:0, (128,), /device:GPU:0
dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/kernel:0, (64, 128), /device:GPU:0
dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias:0, (128,), /device:GPU:0
dynamic_seq2seq/decoder/output_projection/kernel:0, (32, 17191),
2017-09-29 16:36:42.991156: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2
Traceback (most recent call last):
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1323, in _do_call
return fn(*args)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1302, in _run_fn
status, run_metadata)
File "/home/bharaj/anaconda3/lib/python3.6/contextlib.py", line 89, in exit
next(self.gen)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/errors_impl.py", line 467, in raise_exception_on_not_ok_status
c_api.TF_GetCode(status.status))
tensorflow.python.framework.errors_impl.InvalidArgumentError: Assign requires shapes of both tensors to match. lhs shape= [128] rhs shape= [512]
[[Node: save/Assign_3 = Assign[T=DT_FLOAT, _class=["loc:@dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias"], use_locking=true, validate_shape=true, _device="/job:localhost/replica:0/task:0/cpu:0"](dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias, save/RestoreV2_3)]]
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/bharaj/anaconda3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/bharaj/anaconda3/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/bharaj/nmt/nmt/nmt.py", line 518, in
tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "/home/bharaj/nmt/nmt/nmt.py", line 511, in main
run_main(FLAGS, default_hparams, train_fn, inference_fn)
File "/home/bharaj/nmt/nmt/nmt.py", line 490, in run_main
trans_file, hparams, num_workers, jobid)
File "/home/bharaj/nmt/nmt/inference.py", line 110, in inference
hparams)
File "/home/bharaj/nmt/nmt/inference.py", line 136, in single_worker_inference
infer_model.model, ckpt, sess, "infer")
File "/home/bharaj/nmt/nmt/model_helper.py", line 407, in load_model
model.saver.restore(session, ckpt)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 1662, in restore
{self.saver_def.filename_tensor_name: save_path})
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 889, in run
run_metadata_ptr)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1120, in _run
feed_dict_tensor, options, run_metadata)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1317, in _do_run
options, run_metadata)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1336, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: Assign requires shapes of both tensors to match. lhs shape= [128] rhs shape= [512]
[[Node: save/Assign_3 = Assign[T=DT_FLOAT, _class=["loc:@dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias"], use_locking=true, validate_shape=true, _device="/job:localhost/replica:0/task:0/cpu:0"](dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias, save/RestoreV2_3)]]
Caused by op 'save/Assign_3', defined at:
File "/home/bharaj/anaconda3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/home/bharaj/anaconda3/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/home/bharaj/nmt/nmt/nmt.py", line 518, in
tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 48, in run
_sys.exit(main(_sys.argv[:1] + flags_passthrough))
File "/home/bharaj/nmt/nmt/nmt.py", line 511, in main
run_main(FLAGS, default_hparams, train_fn, inference_fn)
File "/home/bharaj/nmt/nmt/nmt.py", line 490, in run_main
trans_file, hparams, num_workers, jobid)
File "/home/bharaj/nmt/nmt/inference.py", line 102, in inference
infer_model = model_helper.create_infer_model(model_creator, hparams, scope)
File "/home/bharaj/nmt/nmt/model_helper.py", line 205, in create_infer_model
extra_args=extra_args)
File "/home/bharaj/nmt/nmt/model.py", line 186, in init
self.saver = tf.train.Saver(tf.global_variables())
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 1214, in init
self.build()
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 1223, in build
self._build(self._filename, build_save=True, build_restore=True)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 1259, in _build
build_save=build_save, build_restore=build_restore)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 747, in _build_internal
restore_sequentially, reshape)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 435, in _AddRestoreOps
assign_ops.append(saveable.restore(tensors, shapes))
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/training/saver.py", line 160, in restore
self.op.get_shape().is_fully_defined())
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/ops/state_ops.py", line 276, in assign
validate_shape=validate_shape)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/ops/gen_state_ops.py", line 57, in assign
use_locking=use_locking, name=name)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/op_def_library.py", line 787, in _apply_op_helper
op_def=op_def)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 3090, in create_op
op_def=op_def)
File "/home/bharaj/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 1638, in init
self._traceback = self._graph._extract_stack()  # pylint: disable=protected-access
InvalidArgumentError (see above for traceback): Assign requires shapes of both tensors to match. lhs shape= [128] rhs shape= [512]
[[Node: save/Assign_3 = Assign[T=DT_FLOAT, _class=["loc:@dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias"], use_locking=true, validate_shape=true, _device="/job:localhost/replica:0/task:0/cpu:0"](dynamic_seq2seq/decoder/multi_rnn_cell/cell_1/basic_lstm_cell/bias, save/RestoreV2_3)]]

@bharathichezhiyan
I think the override_loaded_hparams should set to False when doing inference so we don't accidentally update the model configuration to default.
I just update the master branch, so it should be turn off by default. Using the training and inference instructions with a fresh output dir should work now.

I tried to give flags --override_loaded_hparams=False in inference hoping to not to train the model. It didnot work. Downloaded the master branch again and Training again. It takes all the processes in the server.

@bharathichezhiyan
What is the error you see this time? Can you share it here? Especially the error log of the one synced with the master.
If you just give --override_loaded_hparams=False to a previous failed model, it won't work because the hparams on the disk has been updated by the previous failed runs to incorrect value with the checkpoints.

Thanks @oahziur oahziur
I rerun the model it is working now.
I still could not figure out how to control the maximum number of processes. Do I have to change it the code? I could not find any flags in nmt.py relating to the maximum number of process. Even with the number of GPU flags, it does not seem to be working.

Hi @bharathichezhiyan , I have answered the GPU and processes related question in #136.


Keep getting requests for my location, even after allowing it.

Not sure if this is an upstream bug or not. When I use reroute.it I keep getting asked for my location. This is in Firefox 9 on linux.

did you 'share' it? or set it to 'always share'?
For me, I can reproduce the bug in Firefox on linux only 'sharing' it, but if I select 'always share', it doesn't ask me any more for location.


[Input Group] Flexbox input group overflows the width of parent containers

The flexbox input group overflows the width of any parent container that is smaller than the input group thinks it should be.
Desired behavior (max-width: 120px;):

Actual behavior (max-width: 120px;):

Here is a Codepen that demonstrates the issue and includes a fix: http://codepen.io/johnbacon/pen/xOKdNG
The root cause is the width: auto that was applied to the flexbox-based .input-group-field in this commit. I'm not sure sure why it was there (if it was done for a reason), so I don't feel comfortable submitting a pull request without further testing. However, removing the width: auto; appears to to fix the issue.

I stumbled on this issue as well. However its not just max-width that it overflows, it will overflow any parent that is smaller than it thinks it needs to be.
http://codepen.io/OverFlow636/pen/zBajyo

Thanks for the update on this, @OverFlow636. I've modified the title and content of the issue to match.

Fixed via #8907, will be in 6.2.4


Is it possible to change the speed dynamically?

If I want to change the speed for a few seconds is that possible? Somthing like
scope.speed = 100; //really fast
$timeout(function() {
scope.speed = 1400; //back to normal
},4000);
Doesn't look oike angular-slick picks up the changes?

I'm having the same issues, for the record - can't seem to work it out.


adding docker source, documentation, and Jenkinsfile

This documentation should be generalizable to other vizzies etc that we use docker with.  Maybe there is a better place to put it?

@aappling-usgs I just added the gist and corresponding documentation.  If that is ok, this is ready to merge I think.


setupGlobal global not available when running multiple tests

🐛 Bug Report
I took inspiration from this: https://facebook.github.io/jest/docs/en/mongodb.html in order to run my MongoDB+Mongoose in memory. When I run the test command on for a specific file:
npm run test User.test.js

everything works fine and the globals are properly assigned.
When i run the test command for all my files:
npm run test

the globals are always undefined in my custom environment setup() method.
To Reproduce
Steps to reproduce the behavior:
my global setup file looks like this:
const MongodbMemoryServer = require('mongodb-memory-server')

const mongoServer = new MongodbMemoryServer.MongoMemoryServer()

module.exports = async () => {
  global.__MONGO_URI__ = await mongoServer.getConnectionString()
}

and then my custom environment:
// mongo-environment
const NodeEnvironment = require('jest-environment-node')

class MongoEnvironment extends NodeEnvironment {
  constructor(config) {
    super(config)
  }

  async setup() {
    console.log(global.__MONGO_URI__)
    this.global.__MONGO_URI__ = global.__MONGO_URI__

    await super.setup()
  }

  async teardown() {
    await super.teardown()
  }

  runScript(script) {
    return super.runScript(script)
  }
}

module.exports = MongoEnvironment

Expected behavior
I should see a console.log() with a string of the mongo uri in the output but I get undefined when running with
npm run test

Run npx envinfo --preset jest
Paste the results here:
npx: installed 1 in 1.044s

  System:
    OS: Linux 4.15 Ubuntu 18.04 LTS (Bionic Beaver)
    CPU: x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 9.2.0 - ~/.nvm/versions/node/v9.2.0/bin/node
    Yarn: 1.3.2 - ~/.nvm/versions/node/v9.2.0/bin/yarn
    npm: 5.5.1 - ~/.nvm/versions/node/v9.2.0/bin/npm
  npmPackages:
    jest: ^23.0.0 => 23.1.0

Duplicate of #6007

That does remind me that the example is wrong though - it only works with runInBand. @rickhanlonii thoughts on how to best handle it? Maybe write the host and port to disk or something (similar to what jest-puppeteer does), then the custom environment can pick it up and provide it as globals.

@SimenB thanks for the quick answer. The example should propably not advocate to use global in the globalSetup?

I've come across this exact issue too, and the solution was to store mongo URI in the env.
- global.__MONGO_URI__ = mongoURI;
+ process.env.__MONGO_URI__ = mongoURI;


Fastboot compatibility

Thanks for the addon!
jQuery doesn't work in node-land. Including scripts that assume it is loaded will cause crashing when server-side rendering.

:+1: Thanks! Merging...


[DOCS] docs - update icons in readme

Description
As prime icons got replaced with react icons,
Some new icons got added as well .
But docs are  still not updated yet , These are the newly added icons :
1.instagram
2.linkedin
3.twitch
4.dev.to
5.codewars
6.hashnode
7.graduation-hat
Screenshots
No response
Additional information
No response

I think we also need to add ticktok to the list.


test: Add tests with self-hosted label for #953

I've added tests with the self-hosted label, which changed behavior in #953, which is for #951. Also with the typo fix.
Confirmed that this tests fail before 0c34196d87ea740ed09a6bfbb2a26afc514f76e5.
By the way, is there any plan to make a release after v0.20.4? I'm really looking forward to declaring Runner without explicitly configuring the self-hosted label.

it will get released chart wise as part of the v0.22.0 milestone in which the last remaining issue is #859


03-configure-data-model-in-power-bi-desktop.md(Global)

English:
Browse Reports
Current Translation:
レポートを参照
Suggested Translation:
レポートの参照

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

No locfile in iCMS, So I Re-index the file, waiting for result. ICMS QUERY

Run bugfix tool and waiting for result. ICMS QUERY.

fixed.


manifest: openthread upmerge up to commit 0e8005e

Cleanup of Kconfig and CMakeLists for openthread module.
Added build flags:

OT_15_4
OT_ANYCAST_LOCATOR
OT_BACKBONE_ROUTER_DUA_NDPROXYING
OT_BACKBONE_ROUTER_MULTICAST_ROUTING
OT_BORDER_ROUTING
OT_BORDER_ROUTING_COUNTERS
OT_FIREWALL
OT_MESSAGE_USE_HEAP
OT_NAT64_TRANSLATOR
OT_TX_BEACON_PAYLOAD

Renamed flags:

DATSET_UPDATER to DATASET_UPDATER
CONFIG_OPENTHREAD_BORDER_ROUTING_NAT64 to CONFIG_OPENTHREAD_NAT64_BORDER_ROUTING

Rearranged flags in alphabetical order.
Signed-off-by: Maciej Baczmanski<EMAIL_ADDRESS>

Is the commit mentioned in the title correct? It doesn't seem to be OT commit.

Shouldn't the new platform specific functions get an implementation?
// include/openthread/platform/crypto.h
otPlatCryptoPbkdf2GenerateKey

// include/openthread/platform/radio.h
otPlatRadioAddCalibratedPower
otPlatRadioClearCalibratedPowers
otPlatRadioSetChannelTargetPower
otPlatRadioGetRawPowerSetting

Is the commit mentioned in the title correct? It doesn't seem to be OT commit.

Right, it should be a1979fd.

Shouldn't the new platform specific functions get an implementation?
// include/openthread/platform/crypto.h
otPlatCryptoPbkdf2GenerateKey

// include/openthread/platform/radio.h
otPlatRadioAddCalibratedPower
otPlatRadioClearCalibratedPowers
otPlatRadioSetChannelTargetPower
otPlatRadioGetRawPowerSetting

otPlatCryptoPbkdf2GenerateKey has a weak implementation that should work for any platform.
The power calibration feature is optional, IMO it could be implemented in a separated PR.

Is the commit mentioned in the title correct? It doesn't seem to be OT commit.

Right, it should be a1979fd.

I've copied wrong hash, sorry. Should be ok now.


Update statsdata.php

The hook "createAccount" is deprecated, please use "actionCustomerAccountAdd" instead in module "statsdata".
PS 8.1.X
PHP 8.2.10
Just look in full error log of webserver.
[proxy_fcgi:error] [pid 29439:tid<PHONE_NUMBER>8] [remote <IP_ADDRESS>:9822] AH01071: Got error 'PHP message: PHP Deprecated:  The hook "createAccount" is deprecated, please use "actionCustomerAccountAdd" instead in module "statsdata". in /usr/local/www/mysite.com/www/classes/Hook.php on line 914', referer: https://mysite.com/registration

Hello @metacreo
It makes sense, but you'd need to unregister the old hook, and register the new one in the upgrade file like this:
https://github.com/PrestaShop/statsdata/blob/dev/upgrade/upgrade-2.1.1.php
The next version will be 2.1.2

What would happen if a 1.7 user were to upgrade to this?  Do your changes have to be made sensitive to pre-PS8 users?

@watou I tested on <IP_ADDRESS>. Nothing bad. Module steel work.

@watou I tested on <IP_ADDRESS>. Nothing bad. Module steel work.

That's great!  My only point was, is the version of PrestaShop that introduced  theactionCustomerAccountAdd hook later than <IP_ADDRESS>, because this proposed change could have a problem on previous supported versions.

I am dragging my resource from the <IP_ADDRESS> branch with all the modules and my own modules.
The transition to version 8 took me 1 day and even production stopped for only 5 minutes. Sooner or later you will have to drop old versions.

Looking further it appears it's only a PrestaShop 8 issue that the deprecated notice is printed when hook aliases are used, so your change to set the min PS version to <IP_ADDRESS> is not needed.  Your previous code change should be good for all PS versions since 1.5.

Basically this is good; should have gotten rid of aliases earlier. Moreover, now there is a description of hooks in the docs.

Where are the steps to reproduce ?
Is this supposed to be tested by a dev ?

To reproduce this need read top of this page. ;)
https://github.com/PrestaShop/statsdata/pull/32#issue-1906752767

@metacreo ,
I don't have the error "Got error 'PHP message: PHP Deprecated:  The hook "createAccount" is deprecated, please use "actionCustomerAccountAdd" instead in module "statsdata"." in my log file.

@metacreo ,
I don't have the error "Got error 'PHP message: PHP Deprecated: The hook "createAccount" is deprecated, please use "actionCustomerAccountAdd" instead in module "statsdata"." in my log file.

@florine2623  Nice. What PHP version you use? What is value of 'error_reporting' param in your php.ini file? Have you professional php config or just as is? If you not see deprecation error it means your php not configured to show it or php version is older.

@florine2623 Hello,
My PHP version 8.2.10.
Well, I suspect that you have a lot of PHP errors, but you will never see them. You are not using production PHP.INI, your PHP is not configured, or rather configured to hide compiler errors.
You are using MAMP, which has never been used on production servers. This is extremely unprofessional. Production servers usually run on Linux with PHP-FPM.
"In my php.ini file, I haven't changed anything.", "Am I doing something wrong ?"
; Common Values:
;   E_ALL (Show all errors, warnings and notices including coding standards.)
;   E_ALL & ~E_NOTICE  (Show all errors, except for notices)
;   E_ALL & ~E_NOTICE & ~E_STRICT  (Show all errors, except for notices and coding standards warnings.)
;   E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR  (Show only errors)
; Default Value: E_ALL
; Development Value: E_ALL
; Production Value: E_ALL & ~E_DEPRECATED & ~E_STRICT
; https://php.net/error-reporting
error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT

For testing you must use error_reporting = E_ALL
Hooks not changed, because you need clean PS cache before update module. function upgrade_module_2_1_2 not works because in fact you install same module 2.1.1 from ps repo.

@florine2623 After update check ps_module table. Last record must be statsdata 1 2.1.2
statsdata.php and config.xml must have $this->version = '2.1.2'; and <version><![CDATA[2.1.2]]></version> values.
Just now tested again on my server, all works as expected.

@metacreo Error reporting levels is overridem from the app side. @florine2623 has the environment correctly set.
And also, it shoud NOT be required to delete cache before upgrading, it has to work.
@florine2623 I had some issues with upgrading modules, could you try it on 8.1.3, so we know if it's a core issue? :-)

@Hlavtox

Error reporting levels is overridem from the app side. @florine2623 has the environment correctly set.

In DEV mode only ... with true PS_DISPLAY_COMPATIBILITY_WARNING

And also, it shoud NOT be required to delete cache before upgrading, it has to work.

It required to delete cache before upgrading if you  want manually init update from update TAB


W0622: Redefining built-in 'hex'

Not a big problem, but pylint makes a valid point. Maybe hexdump or similar would be a better name?

Not sure I get your meaning - do you mean it shadows a system binary called hex? You can rename the file to anything you like if that's the case.

Not a system binary, but the python built-in hex. I imagine this could be confusing for someone.


[Feature Request] Variables are not supported to use in Rows/Root

Variables are not supported to use in Rows/Root

This is now available in master and released as v0.7. Download from https://grafana.com/plugins/yesoreyeram-infinity-datasource


Update: update and remove some old code

Please provide Issues links to:

Issues: #

Provide test code:

Description
...

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


Create IdentifiersDotOrgID.schema.tpl.json

related to #335
@olinux could you double check especially the regex in consideration of the identification scheme of Identifiers.org ?
If it is okay I would add it to the possible list of digital identifiers for DSVs

due to the clean up I'll redo this PR


Search does not find "docsVersionDropdown"

📚 Documentation
Pasted "docsVersionDropdown" into search box at top right of the docs page & hit enter, nothing happens. Search seems broken?
Have you read the Contributing Guidelines on issues?
yes

Hi,
Search is not broken, it does not look up inside code blocks, and this string only appears in a codeblock.
https://v2.docusaurus.io/docs/theme-classic/#navbar-docs-version-dropdown
So it's more a docs issue: we should add every options available in code blocks documented outside of code blocks, so that search can find it. Do you want to improve the doc of these items?

See also
https://github.com/facebook/docusaurus/issues/3172#issuecomment-669740260
Algolia says searching in code blocks is likely to degrade the search experience, so I guess we should follow his recommendations.
@s-pace as you can see this problem is quite common :) if Algolia could search in Docusaurus 2 code blocks that would likely be very helpful. Not sure you can do about it right now, just wanted to let you know about this new issue ;)

Actually, yes, search was broken. I could not search at all last night. Today I can search again.
It wasn't even popping up saying "no results found", literally nothing happened just like I said. Maybe Algolia was down & there is insufficient feedback to the end user if it is down?

Ah, I see the problem. If you paste a search term that simply has 0 results, you get no feedback. If you type the term in character by character, you at least have a chance to see some results & then see them go away.
Ideally there should be a popup that says "no results found for 'docsVersionDropdown'", right now it just acts like the search is broken.

To me it does exactly that, no?

Same as @slorber
I couldn't reproduce this issue. I can confirm you that the search was up last night.

https://youtu.be/5YCfHz_R4j0
video showing the reproduction.

@joshribakoff this is docusaurus v1, v1 does not even have docsVersionDropdown feature 🤪

Yes the issue is only on docusaurus v1. There is no "no result" dropdown.

@slorber that also explains the "no results" :)
@s-page this seems correct, up to you all whether to backport that or not, just figured I'd make you aware.

@joshribakoff I am finding this issue open. But the functionality of the dropdown is working as required. For "docsVersionDropdown" it is showing me "No results for docsVersionDropdown". What am I missing here?


.Net: SemanticKernel package was not working in Winforms .NetFramework.

Describe the bug
We are utilizing the Microsoft.SemanticKernel package in a .NET Framework 4.8 Winforms sample to retrieve responses from ChatGPT. However, when invoking kernel.GetRequiredService(), it consistently returns null. As a result, we are unable to use the ChatCompletionService to fetch AI responses. Notably, the same code functions correctly in a .NET80 environment.
To Reproduce
Steps to reproduce the behavior:

Run the sample
Click Initialize button

Expected behavior
Sample needs to be run properly without exception.
Screenshots

Sample Link - SemanticKernel (2).zip
Platform

OS:Windows 11
IDE: VS2022 version 17.12.0
Language: C#
Source:Microsoft.SemanticKernel package version 1.21.1

Additional context
We saw that this package was compatible for WPF .NetFramework.

@ChidanandMurugaiah, can you check if this works with our latest version? 1.29
Please provide more details about the stack trace you getting.
We had a bug 2 weeks ago related to Null reference exception when using function calling and can be related to your example

https://github.com/microsoft/semantic-kernel/issues/9313

@RogerBarreto,
1) can you check if this works with our latest version? 1.29

When we try to install the latest version of the KS package we are facing the below issue.

2) Please provide more details about the stack trace you getting.
Below is the Stack trace
at Microsoft.SemanticKernel.ChatCompletion.ChatCompletionServiceExtensions.GetChatMessageContentsAsync(IChatCompletionService chatCompletionService, String prompt, PromptExecutionSettings executionSettings, Kernel kernel, CancellationToken cancellationToken)
at Microsoft.SemanticKernel.ChatCompletion.ChatCompletionServiceExtensions.d__1.MoveNext()
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at SemanticKernel.AIService.d__10.MoveNext() in D:\Samples\Winforms\SemanticKernel\Form1.cs:line 57

3) We had a bug 1 month ago related to Null reference exception when using function calling and can be related to your example
https://github.com/microsoft/semantic-kernel/issues/9313

We referred the query you mentioned but it was not similar to our problem. The same code works in .Net80 sample but not works in .NetFramework sample.

@ChidanandMurugaiah Thanks for the added context.
On the first I could not replicate your issue, all the packages were installed without a problem, maybe suggest clearing any caches or a clean build.

For the error to ensure is not related to the #9313, please make sure you are using a reference to System.Memory.Data forcing it to use >= 8.0.0 version.

@RogerBarreto, Now, I am able to install the latest version of Microsoft.SemanticKernal package but for that I need to install the below packages alone.

Microsoft.Extensions.VectorData.Abstractions
Azure.AI.OpenAI
Microsoft.Extensions.AI.Abstractions

Because these packages are in pre-release. So, when installing the SK package, these package not installed automatically in .NetFramework
Let me come to the point, even after installing the latest version of the SK, the issue still occurs.


Having this issue? can someone help?

Your item needs to have a property called "droppeditem" which indicates the scene of a 3d/2d item that is dropped from your inventory, check the demo items and you can see that they all have this property.


Cache apn private key and header

Solves #46.
This takes care of caching the APN private key (instead of re-parsing it for each message, possible hundreds of thousands of times per second...).
It keeps everything thread safe, and will update the cache if the associated settings have mutated.
NOTE: This is based on #45. So that one should be merged first. If #44 is merged instead, I will rebase on it.

I just got that you are caching the tokens in a dictionary, so this is redundant.


Option for Camel Cased words:  ctrl + backspace should delete part of word instead of whole word

A lot of the time I am modifying variable or function names. when the name of the variable or function is camel cased or pascal cased a ctrl + backspace deletes the whole word. If there was an option to just delete till the last Capital word on the word on ctrl + backspace that would be really handy. Same applies for ctrl+delete.
Example:
My function name getSomeVeryExcitingDataFromApi and I want to change it to getSomeVeryExcitingInfoFromApi. I would expect after this feature comes, ctrl + backspace thrice from the end of getSomeVeryExcitingDataFromApi  should get me to getSomeVeryExciting|   and then I would type the remaining.
Another example (this is the one I will really use and looking forward to) I can use the extension Camel Case Navigation by maptz to go back twice from the end of getSomeVeryExcitingDataFromApi and I will be at getSomeVeryExcitingData|FromApi. now I want to press ctrl+backspace and get to getSomeVeryExciting|FromApi and now I can type Info and get to getSomeVeryExcitingInfo|FromApi. Or the other way works too: going back thrice then ctrl+delete to get to getSomeVeryExciting|FromApi

This feature is already available with the Camel Case Navigation Extension. My VSCodeVim wasn't latest after I updated that one this started working.
I am closing this.

This feature is already there in vscode. This doesn't work with VSCodeVim extension. With Camel Case Navigation this works with VSCodeVim


[BBC's Wraith]: No implicit conversion of string into integer

Hey folks,
I run capture, these are my results:
/Users/montana/wraith/lib/wraith/wraith.rb:172:in `[]': no implicit conversion of String into Integer (TypeError)
    from /Users/montana/wraith/lib/wraith/wraith.rb:172:in `verbose'
    from /Users/montana/wraith/lib/wraith/wraith.rb:11:in `initialize'
    from /Users/montana/wraith/lib/wraith/validate.rb:10:in `new'
    from /Users/montana/wraith/lib/wraith/validate.rb:10:in `initialize'
    from /Users/montana/wraith/lib/wraith/cli.rb:132:in `new'
    from /Users/montana/wraith/lib/wraith/cli.rb:132:in `block in capture'
    from /Users/montana/wraith/lib/wraith/cli.rb:28:in `within_acceptable_limits'
    from /Users/montana/wraith/lib/wraith/cli.rb:131:in `capture'
    from /Users/montana/.rvm/gems/ruby-2.2.1/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
    from /Users/montana/.rvm/gems/ruby-2.2.1/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
    from /Users/montana/.rvm/gems/ruby-2.2.1/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
    from /Users/montana/.rvm/gems/ruby-2.2.1/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
    from /Users/montana/.rvm/gems/ruby-2.2.1@global/gems/wraith-3.1.2/bin/wraith:5:in `<top (required)>'
    from /Users/montana/.rvm/rubies/ruby-2.2.1/bin/wraith:23:in `load'
    from /Users/montana/.rvm/rubies/ruby-2.2.1/bin/wraith:23:in `<main>'
    from /Users/montana/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `eval'
    from /Users/montana/.rvm/gems/ruby-2.2.1/bin/ruby_executable_hooks:15:in `<main>'

I've looked at this: https://github.com/bbc/wraith/blob/4f6eb0b7625d468bb9e3061fd2628f48df4c4e37/lib/wraith/wraith.rb#L172 I then tried to debug, but still nothing. So then I added an export to my bashrc and yet still no luck, any ideas?
export PATH=/Users/User_Name/.rvm/gems/ruby-2.3.0/bin/wraith:$PATH

Cheers,
Montana Mendy

Any update on this?


I can't find the "mapamok.app" or "model.dae" files.

Hi,
I have downloaded the Mapamok zip folder, but I can not seem to find the mapamok.app or model.dae file. However, I do see the shader.frag and shader.vert files in mapamok > bin > data. Can someone please help?
I am using Mac OSX 10.6.8.
Thanks,
Johnny
<EMAIL_ADDRESS>

they should definitely be there. i just re-downloaded it myself (also on 10.6.8) and checked.
can you post a screenshot of what things look like immediately after you've unzipped them?

I re-downloaded the file and it is working now. Thanks

I re-downloaded the file and it is working now. Thanks.
Here's what it looked like before.
On Tue, Mar 6, 2012 at 9:12 AM, Kyle McDonald <
<EMAIL_ADDRESS>
wrote:

they should definitely be there. i just re-downloaded it myself (also on
10.6.8) and checked.
can you post a screenshot of what things look like immediately after
you've unzipped them?

Reply to this email directly or view it on GitHub:
https://github.com/YCAMInterlab/ProCamToolkit/issues/9#issuecomment-4345920


v1.3.0 - New mini player options and volume adjustments

New feature to customize the look of mini player - you can now choose from 2 styles
You can now hide mini player window by right-clicking and choosing Hide window option
Mini player is now easier to move around
Volume slider now adjusts Apple Music/Spotify instead of a system volume

/release


Remove document attribute doctype from asciidoctor-gb

The IsoDoc doctype attribute is superseded by the GB combination of:

:scope:
The scope of the GB standard (national, sector, professional, local, enterprise). Defaults to national.

:mandate:
The mandate of the GB standard (mandatory, recommended, guidelines). Defaults to mandatory.

It is currently inherited from asciidoctor-iso, but we should remove the doctype attribute from asciidoctor-gb.

I disagree that doctype is overridden by scope + mandate; I think it is only mandate.
Cf in ISO:
BibItemType |=
     "international-standard" | "technical-specification" |
     "technical-report" | "publicly-available-specification" |
    "international-workshop-agreement" | "guide"

And in CSD:
BibItemType |= "governance" | "standard" | "guide"

I don't see why we need 5*3 types, when we're already encoding scope anyway; only mandate is comparable to the other standards.

I'm not suggesting we do 5*3 types -- I'm saying that we already have mandate and scope so we don't need doctype anymore.
Are you proposing we re-purpose the ISO BibItemType terms when used with GB for GB mandate like this mapping?

ISO
GB

"international-standard" => "standard"
"standard"

"guide"
"guidelines"

??
"recommendation"

Semantically both GB, GB/T prefixes designate "standards" though.
What is "??" then?

Well, that's what I thought you wanted, and that would make "recommendation" a new standard type. But if you're ok to stick with "standard" and "guide", that's fine by me.

No, the wording "international standard" is prescribed by ISO, so we should not change it there.


upgrade firebase-tools to version 11.30.0

Describe your changes

Issue ticket number and link
Closed #708
Motivation and Context
This change is important because it fixes the Emulator UI has exited with code: 1 error
ticket number #708
How Has This Been Tested?
This was tested on the local environment

Closed this PR because the version has been updated already. Thank you for opening a PR!


Provide Modules with the ability to reject CONFIG SETs on module configurations

Today, Modules using valkeymodule-rs can create configs using the valkeymodule macro.
Modules can provide a callback that gets triggered on configuration change (after CONFIG SET).
But we do not have a way for Modules to reject CONFIG SET operations on Module configurations.
In Core valkey, we can do this by having the SDK accept a config_set callback, just like we allow modules to provide a on_configuration_change call back. If the Module returns an Error, the config set operation should be rejected. Else, it can be applied.
Current Usage:
    configurations: [
.....
        string: [
            ["string", &*CONFIGURATION_STRING, "default", ConfigurationFlags::DEFAULT, Some(Box::new(on_configuration_changed::<String, _>))],
        ],
......

Hello - I am currently implementing a change for this issue and will push out a PR soon

@KarthikSubbarao - so the use case is to prevent user from EVER changing special config that was defined in module?  Or to restrict it config changes to certain values (like ENUM)?  Or only enable during configs to be set during start like  raw::REDISMODULE_CONFIG_IMMUTABLE?  I am trying to understand the use case

@dmitrypol - I have implemented this functionality here: https://github.com/valkey-io/valkeymodule-rs/pull/144/
You can take a look when you get a chance


Traverse() does not abort if NavigateSiblingChain() aborts

This is a bug found inside Traverse(), and might be triggered when value_p == nullptr. In this case NavigateSiblingChain() will be called and this function could abort. However, the status of context_p->abort_flag is not checked and therefore important state changes are probably missed

Solved. This is caused by NavigateInnerNode() ignoring the leftmost element in the right branch of a merged node


[Bug] Can't use spaced skills in /forceskill command

When using the '/class forceskill' command, only skills without spaces (possibly other special characters) can be used.
I think it would be a nice quality-of-life fix if spaces could be included, or at least replaced in the command with underscores.

This actually appears to be implemented already. Both forceskill and forcecast show


Elephantify the inputs/outputs of GPFA

I created a directory "gpfa_elephant" and copied all Python codes in it.
We should do all elephantification works only in this directory and keep the codes under "gpfa_v0203" intact.

@Junji110  Actually a new branch would be better to work on this issue. Also it would be nice to have both versions available as fallback alternatives.

I created the branch gpfa_elephant. Please use this branch for further elephant developments.

I think, at least for the moment, we should have the two versions in a same branch so that we can easily check the results of the two versions during the development.
If they are in separate branches, we need to go back and forth between the brunches every time we want to check the consistency between the two versions, which I think quite cumbersome.

For implementing the unittests we will move the branch to inm-6 github


[BUG][Dashboard] Application details crashed

http://localhost:8000/#/ApplicationList/appconfig-scaler/Components

×
Error: Objects are not valid as a React child (found: object with keys {condition, enabled, name, type}). If you meant to render a collection of children, use an array instead.
in p (at ComponentDetail/index.jsx:444)
in div (created by Context.Consumer)
in Col (at ComponentDetail/index.jsx:443)
in div (created by Context.Consumer)
in Row (at ComponentDetail/index.jsx:421)
in div (at ComponentDetail/index.jsx:385)
in div (created by Context.Consumer)
in Col (at ComponentDetail/index.jsx:378)
in div (created by Context.Consumer)
in Row (at ComponentDetail/index.jsx:279)
in div (created by TabPane)
in TabPane (at ComponentDetail/index.jsx:278)
in div (created by TabPanelList)
in div (created by TabPanelList)
in TabPanelList (created by ForwardRef(Tabs))
in div (created by ForwardRef(Tabs))
in ForwardRef(Tabs) (created by Tabs)
in Tabs (at ComponentDetail/index.jsx:277)
in div (at ComponentDetail/index.jsx:272)
in div (created by Context.Consumer)
in div (created by Context.Consumer)
in Spin (at ComponentDetail/index.jsx:271)
in div (at ComponentDetail/index.jsx:270)
in TableList (created by Connect(TableList))
in Connect(TableList) (at Components/index.jsx:171)
in div (at Components/index.jsx:158)
in div (at Components/index.jsx:132)
in div (created by Context.Consumer)
in div (created by Context.Consumer)
in Spin (at Components/index.jsx:131)
in div (at Components/index.jsx:117)
in TableList (created by Connect(TableList))
in Connect(TableList) (created by LoadableComponent)
in LoadableComponent (created by Context.Consumer)
in Route (created by Context.Consumer)
in Switch (created by Context.Consumer)
in main (created by Basic)
in Basic (created by Context.Consumer)
in Content (created by WrapContent)
in ConfigProviderWarp (created by WrapContent)
in WrapContent (created by BasicLayout)
in section (created by Context.Consumer)
in BasicLayout (created by Context.Consumer)
in Layout (created by BasicLayout)
in section (created by Context.Consumer)
in BasicLayout (created by Context.Consumer)
in Layout (created by BasicLayout)
in div (created by BasicLayout)
in Provider (created by BasicLayout)
in BasicLayout (at BasicLayout.jsx:87)
in BasicLayout (created by Connect(BasicLayout))
in Connect(BasicLayout) (created by LoadableComponent)
in LoadableComponent (created by Context.Consumer)
in Route (created by Context.Consumer)
in Switch (created by Context.Consumer)
in SecurityLayout (created by Connect(SecurityLayout))
in Connect(SecurityLayout) (created by LoadableComponent)
in LoadableComponent (created by Context.Consumer)
in Route (created by RouterComponent)
in Switch (created by RouterComponent)
in Router (created by RouterComponent)
in RouterComponent
in Provider (created by _DvaContainer)
in _DvaContainer
in Unknown
in _LocaleContainer
in Unknown
▶ 39 stack frames were collapsed.
_callee$
./src/pages/ApplicationList/ComponentDetail/index.jsx:63
60 |   },
61 | });
62 | if (res) {
63 |   this.setState({
| ^  64 |     compDetailData: res,
65 |   });
66 |   const traits = await this.props.dispatch({
View compiled
▶ 5 stack frames were collapsed.
This screen is visible only in development. It will not appear if the app crashes in production.
Open your browser’s developer console to further inspect this error.  Click the 'X' or hit ESC to dismiss this message.

fixed


Fixes top and bottom border cut off on status bar item border

For the bottom border:

The window border wasn't taken into account when calculating the layout

For the top border:

This is tricky because the border  is an absolute positioned pseudo-element
I could change the outline-offset to -2px though not sure if it looks good enough

This PR fixes #101525

Thanks for the PR. I think this makes sense, however also assigning to @sbatten so he gives it a review since he owns the layout code

@sbatten friendly ping on this? Do you pan to review this?
@jeanp413 for the slow response this got out of date. If you are still interested in this is it possible that you get rid of merge conflicts and then I can look into merging this? Thanks a lot for great PRs!

@jeanp413 thanks! I plan to review this week. Let's give some time for @sbatten to responde before that though.

I tried this PR and it looks good and the changes make sense.
However the issue seems to be fixed already in vscode insdiers.
That is in insiders with HC theme the bottom border already gets nicely rendered. At least on my machine
Let me know if I am missing something here

@isidorn I looked at the linked issue and it seems this fix the hover border case, not the focus case. I can reproduce the original issue in insiders and the behavior is different with the PR. However, I don't like that we don't show the top border. I think we should, in both focus and hover, show the top and bottom border.

@isidorn I can also reproduce in insiders, in your screenshot the status bar does not have a white bottom border, for that the window should not be maximized.

@jeanp413 thanks for clarifying
However based on @sbatten will not merge this in, since he owns this code.

Is this still relevant?


Create test helper package

Create a package for helping developers test the applications they build using Machete. Some things that are immediate needs are as follows:

[ ] Setting up the parser
[ ] Formatting HL7 messages for comparisons
[ ] Comparing messages/documents
[ ] Reading/loading messages/documents

The approach for this should be similar to the approach taking for MassTransit. A testing namespace that makes it unit test framework agnostic, but allows for the easy setup of tests.

That is what I had in mind. Question though, would that be a separate project/package with a testing namespace? I am thinking that it would be but wanted to confirm.

Same assembly. Just a namespace. For the core testing bits, not any sample data or anything.

Chris Patterson

On May 15, 2017, at 10:36 AM, Albert Hives<EMAIL_ADDRESS>wrote:
That is what I had in mind. Question though, would that be a separate project/package with a testing namespace? I am thinking that it would be but wanted to confirm.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

So, I am thinking the right place to put it is in the Machete project. We can call it something like Machete.Testing

That's essentially what I did with MT:
https://github.com/MassTransit/MassTransit/tree/develop/src/MassTransit/Testing
Makes it simple to setup an in-memory bus for testing all aspects of MT, but could have a similar approach for Machete.
https://github.com/MassTransit/MassTransit/blob/develop/src/MassTransit.Tests/Testing/ConsumerTest_Specs.cs#L30

We have the infrastructure for this setup now. Closing.


Is the box ap equal to the Map @ 50:95  ??

Hi
Is the box ap equal to the Map @ 50:95  ?? Or just the Map @50??

It is mAP@50:95.


Add information about how link checking is going

Just realized I forgot to add an issue for that.
When testing the tool, I realized I missed some kind of idea of what was gonna happen.
So I added number of files and links as extra info.
It could inform the user how much there is to check, as well as whether he is in the right location.
See feat: #32

This is how it looks like now :

This is how it looks like now :

thx again for implementing this 🙇♂


Add examples with update parameter for secretsmanager secret

Description of your changes

Adds tests which fail because of the bug #1128, which can be used to validate the fix in #1144
I have:

[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/secretsmanager/v1beta1/secret.yaml"
This should fail because #1128 hasn't been fixed yet in this branch.

/test-examples="examples/secretsmanager/v1beta1/secret-withreplica.yaml"
This should fail because https://github.com/upbound/provider-aws/issues/1128 hasn't been fixed yet in this branch.

secret-withreplica.yaml This should fail because #1128 hasn't been fixed yet in this branch.

This is actually expected to pass (and it passed ), because the bug is relevant only when replica is not specified in the resource config.

@mbbush thanks so much for the contribution! as mentioned in https://github.com/upbound/provider-aws/pull/1144#issuecomment-1945670878 I cherry-picked your change to #1144, so we can close this and continue there


Change colour in force plot if Matplotlib = True

Is there a way to change the colours of the Force Plot if you are using Matplotlib = True?

Try playing around with the plot_cmap argument in force.plot
[force_plot documentation])https://shap.readthedocs.io/en/latest/generated/shap.plots.force.html?highlight=force_plot#shap.plots.force)
Here are some potential colour map options
Also if you want to do it per class this

Try playing around with the plot_cmap argument in force.plot
[force_plot documentation])https://shap.readthedocs.io/en/latest/generated/shap.plots.force.html?highlight=force_plot#shap.plots.force)
Here are some potential colour map options
Also if you want to do it per class this

That does not work is Matplotlib = True is set. The colours will be the default even if you have put plot_cmap to a class.

That does not work is Matplotlib = True is set. The colours will be the default even if you have put plot_cmap to a class.

Hey Guys,
it seems like this is still not fixed. I looked into the source code and this looks like a really quick and useful fix, as the color plays a big role in the semantic of the plot. You can ee here, that it is still hardcoded for bars and text:


could you release the finetune performance with fewer epoch on glue?

could you release the finetune performance with fewer epoch on glue, such as epoch 3 the same as bert or roberta?

Using Roberta hyper-parameter to fine-tune the released checkpoint can achieve:

MNLI
QNLI
QQP
RTE
SST-2
MRPC
CoLA
STS-B

86.9
92.6
91.6
85.4
94.4
89.3
60.5
89.7

We will update the results when our training is finished.


Better Define De-id Behavior for Overlapping Annotations

The first draft of the de-identifier endpoint doesn't specify how it handles overlapping annotations. An annotation can also end up getting applied multiple times across multiple deidentificationConfigs, which is not desired behavior.

Got a working-ish solution for now (see PR #27 ); all characters that should be de-identified are de-identified, but there might not be a good visible output for this if they are overlapping (i.e. annotations can end up "swallowing" each other if they're processed first-to-last).

@cascadianblue Can you post an update here regarding this ticket?

@cascadianblue Can you post an update here regarding this ticket?

@cascadianblue Can you post an update here regarding this ticket?
Is this (still?) a breaking issue or could that lead to situations that may confuse the user? If yes, please list specific example, e.g.
Person name and physical address overlap
Input: "The patient is treated at James' Hospital"
Annotations:

"James" (person name)
"James' Hospital" (physical address)
Deidentifier output: ...

@cascadianblue Can you post an update here regarding this ticket?
Is this (still?) a breaking issue or could that lead to situations that may confuse the user? If yes, please list specific example, e.g.
Person name and physical address overlap
Input: "The patient is treated at James' Hospital"
Annotations:

"James" (person name)
"James' Hospital" (physical address)
Deidentifier output: ...

I don't know if I would say there is a "breaking issue", since the deidentifier always does something reasonable, but I'm not sure that it's exactly the reasonable thing that we want it to do.
In order to stay sane while de-identifying these notes, I have come up with a paradigm where every de-identification involves shifting character addresses to make up for the change in text length. E.g. suppose our note says "James Smith is in Seattle" and the name annotations are [{content: "James", start: 0, length: 5}, {content: "Smith", start: 6, length: 5}] while the address annotations are [{content: "Seattle", start: 18, length: 7}].
If we apply the annotationType de-id method, like so:
{
    "note": {
        "text": "James Smith is in Seattle",
        ...
    },
    "deidentificationConfigurations": [
        {
            "deidentificationStrategy": {"annotationTypeConfig": {}},
            "annotationTypes": ["text_person_name", "text_physical_address"]
        }
    ]
}

the de-identifier needs to make sure it updates the character address ranges for those annotations as it goes. After de-identifying the first person name note, the note text will look like this:
"[TEXT_PERSON_NAME] Smith is in Seattle"
and the annotations will now look like this:
Names: [{content: "James", start: 0, length: 18}, {content: "Smith", start: 19, length: 5}]
Addresses: [{content: "Seattle", start: 31, length: 7}]
The character addresses for every annotation will have to be shifted each time we de-identify one of our three total annotations. Hopefully this is all making sense so far.
Overlapping Annotations
This of course gets tricky when we have overlapping annotations. Here is an example:
Note text: "The patient was on Martin James Street"
Name annotations: [{content: "Martin James", start: 19, length: 12}]
Address annotations: [{content: "James Street", start: 26, length: 12}]
Here is a visual display of the original text and its annotations:
1:                          >|          |<
2:                   >|          |<
  "The patient was on Martin James Street"

Suppose we de-identify this note with the following request:
{
    "note": {
        "text": "The patient was on Martin James Street",
        ...
    },
    "deidentificationConfigurations": [
        {
            "deidentificationStrategy": {"annotationTypeConfig": {}},
            "annotationTypes": ["text_physical_address", "text_person_name"]
        }
    ]
}

Now, here is a visual representation of the note and its annotations after we de-identify the first annotation, but before updating the character addresses on the annotations:
1:                          >|          |<
2:                   >|          |<
  "The patient was on Martin [TEXT_PHYSICAL_ADDRESS]"

I think it is pretty uncontroversial that the right-bound of the address annotation (annotation 1) needs to be shifted to the right 11 characters. But what about the right-bound of the name annotation (annotation 2)? It can't stay where it is (let me know if you disagree or don't know why I'm saying this), but which way should it be moved?
The current policy is to shift all addresses left if they are inside a region that is being de-identified. Therefore, after the first de-identification and updating the character addresses, the note text and annotation address ranges would look like this:
1:                          >|                     |<
2:                   >|     |<
  "The patient was on Martin [TEXT_PHYSICAL_ADDRESS]"

The second annotation (the person name) would then get applied, and the annotation addresses would get shifted again (without controversy this time, since there's now no overlap), and the note and annotation addresses would now look like this:
1:                                     >|                     |<
2:                   >|                |<
  "The patient was on [TEXT_PERSON_NAME][TEXT_PHYSICAL_ADDRESS]"

This seems like very reasonable behavior to me. But something weird happens if you apply the same policy but just reverse the order of annotations:
Overlapping Annotations in a different Order
{
    "note": {
        "text": "The patient was on Martin James Street",
        ...
    },
    "deidentificationConfigurations": [
        {
            "deidentificationStrategy": {"annotationTypeConfig": {}},
            "annotationTypes": ["text_person_name", "text_physical_address"]
        }
    ]
}

Here is the original note and annotation address ranges (note I switched 1 & 2):
1:                   >|          |<
2:                          >|          |<
  "The patient was on Martin James Street"

After de-identifying one annotation (notice how addresses that point inside the de-identified area get shifted left!):
1:                   >|                |<
2:                   >|                       |<
  "The patient was on [TEXT_PERSON_NAME] Street"

Now we apply the second annotation (the physical address) and shift the annotation address ranges appropriately:
1:                   ><
2:                   >|                     |<
  "The patient was on [TEXT_PHYSICAL_ADDRESS]"

This behavior seems pretty reasonable, too, but the result also looks very different from the one we had before, for reasons that don't seem super intuitive to the user. Recall how just reversing the order of the de-identifications (see earlier section) got us a result which had two bracketed [ANNOTATION_TYPE]'s.
An alternative policy
We could try another policy where character addresses get shifted left if they are start's, or right if they are lengths's. This comes with its own weird behavior, though, and before I get into it, I'd hope to hear back from you on my above explanation on why overlapping. Let me know if the above explanation makes sense. Maybe I am missing some obvious solution.

I don't know if I would say there is a "breaking issue", since the deidentifier always does something reasonable, but I'm not sure that it's exactly the reasonable thing that we want it to do.
In order to stay sane while de-identifying these notes, I have come up with a paradigm where every de-identification involves shifting character addresses to make up for the change in text length. E.g. suppose our note says "James Smith is in Seattle" and the name annotations are [{content: "James", start: 0, length: 5}, {content: "Smith", start: 6, length: 5}] while the address annotations are [{content: "Seattle", start: 18, length: 7}].
If we apply the annotationType de-id method, like so:
{
    "note": {
        "text": "James Smith is in Seattle",
        ...
    },
    "deidentificationConfigurations": [
        {
            "deidentificationStrategy": {"annotationTypeConfig": {}},
            "annotationTypes": ["text_person_name", "text_physical_address"]
        }
    ]
}

the de-identifier needs to make sure it updates the character address ranges for those annotations as it goes. After de-identifying the first person name note, the note text will look like this:
"[TEXT_PERSON_NAME] Smith is in Seattle"
and the annotations will now look like this:
Names: [{content: "James", start: 0, length: 18}, {content: "Smith", start: 19, length: 5}]
Addresses: [{content: "Seattle", start: 31, length: 7}]
The character addresses for every annotation will have to be shifted each time we de-identify one of our three total annotations. Hopefully this is all making sense so far.
Overlapping Annotations
This of course gets tricky when we have overlapping annotations. Here is an example:
Note text: "The patient was on Martin James Street"
Name annotations: [{content: "Martin James", start: 19, length: 12}]
Address annotations: [{content: "James Street", start: 26, length: 12}]
Here is a visual display of the original text and its annotations:
1:                          >|          |<
2:                   >|          |<
  "The patient was on Martin James Street"

Suppose we de-identify this note with the following request:
{
    "note": {
        "text": "The patient was on Martin James Street",
        ...
    },
    "deidentificationConfigurations": [
        {
            "deidentificationStrategy": {"annotationTypeConfig": {}},
            "annotationTypes": ["text_physical_address", "text_person_name"]
        }
    ]
}

Now, here is a visual representation of the note and its annotations after we de-identify the first annotation, but before updating the character addresses on the annotations:
1:                          >|          |<
2:                   >|          |<
  "The patient was on Martin [TEXT_PHYSICAL_ADDRESS]"

I think it is pretty uncontroversial that the right-bound of the address annotation (annotation 1) needs to be shifted to the right 11 characters. But what about the right-bound of the name annotation (annotation 2)? It can't stay where it is (let me know if you disagree or don't know why I'm saying this), but which way should it be moved?
The current policy is to shift all addresses left if they are inside a region that is being de-identified. Therefore, after the first de-identification and updating the character addresses, the note text and annotation address ranges would look like this:
1:                          >|                     |<
2:                   >|     |<
  "The patient was on Martin [TEXT_PHYSICAL_ADDRESS]"

The second annotation (the person name) would then get applied, and the annotation addresses would get shifted again (without controversy this time, since there's now no overlap), and the note and annotation addresses would now look like this:
1:                                     >|                     |<
2:                   >|                |<
  "The patient was on [TEXT_PERSON_NAME][TEXT_PHYSICAL_ADDRESS]"

This seems like very reasonable behavior to me. But something weird happens if you apply the same policy but just reverse the order of annotations:
Overlapping Annotations in a different Order
{
    "note": {
        "text": "The patient was on Martin James Street",
        ...
    },
    "deidentificationConfigurations": [
        {
            "deidentificationStrategy": {"annotationTypeConfig": {}},
            "annotationTypes": ["text_person_name", "text_physical_address"]
        }
    ]
}

Here is the original note and annotation address ranges (note I switched 1 & 2):
1:                   >|          |<
2:                          >|          |<
  "The patient was on Martin James Street"

After de-identifying one annotation (notice how addresses that point inside the de-identified area get shifted left!):
1:                   >|                |<
2:                   >|                       |<
  "The patient was on [TEXT_PERSON_NAME] Street"

Now we apply the second annotation (the physical address) and shift the annotation address ranges appropriately:
1:                   ><
2:                   >|                     |<
  "The patient was on [TEXT_PHYSICAL_ADDRESS]"

This behavior seems pretty reasonable, too, but the result also looks very different from the one we had before, for reasons that don't seem super intuitive to the user. Recall how just reversing the order of the de-identifications (see earlier section) got us a result which had two bracketed [ANNOTATION_TYPE]'s.
An alternative policy
We could try another policy where character addresses get shifted left if they are start's, or right if they are lengths's. This comes with its own weird behavior, though, and before I get into it, I'd hope to hear back from you on my above explanation on why overlapping. Let me know if the above explanation makes sense. Maybe I am missing some obvious solution.

@cascadianblue Thanks for the detailed answer!
Just to double-check, there is no issue regarding overlapping annotation when using only a masking character, right?
Solving this is not required for the release. This is typically a problem that we can keep open for discussion with the users of the NLP Sandbox.

@cascadianblue Thanks for the detailed answer!
Just to double-check, there is no issue regarding overlapping annotation when using only a masking character, right?
Solving this is not required for the release. This is typically a problem that we can keep open for discussion with the users of the NLP Sandbox.


Modified README(s) for typos

Modified README(s) for typos

@hemastutibaruah, mind to update your PR to a mergeable state? It has conflicts right now.

Will fix the conflict and submit later to my forked area


Add retransmission subsystem in channel link

[ ] ask Laolu about counter persistence, and add it.
[ ] check the generateRevocation function and make sure that we are passing right indexes.

Coverage decreased (-0.7%) to 73.298% when pulling 49aa23a263861a1a9c116ecdbac36406fd9284cf on AndrewSamokhvalov:retransmission_in_channellink into 2e6800e1ed65c4c2d5b681612976834aed3d822c on lightningnetwork:master.

Coverage decreased (-0.5%) to 73.52% when pulling e2eaf0cddaa4d720d7443941f54cb43d7bc3b937 on AndrewSamokhvalov:retransmission_in_channellink into 2e6800e1ed65c4c2d5b681612976834aed3d822c on lightningnetwork:master.

Coverage decreased (-0.5%) to 73.528% when pulling ade906540d38e3d4bbd360d47db0b2c8ed7819c5 on AndrewSamokhvalov:retransmission_in_channellink into 2e6800e1ed65c4c2d5b681612976834aed3d822c on lightningnetwork:master.

Closing at this has been taken over and fully implemented.


StyleCopAnalyzers ignoring the //  tag

I have a project where I have five web service references. Each of these service references creates a reference.cs file. At the top of each of these files is the following header:
//------------------------------------------------------------------------------
// <auto-generated>
//     This code was generated by a tool.
//     Runtime Version:4.0.30319.42000
//
//     Changes to this file may cause incorrect behavior and will be lost if
//     the code is regenerated.
// </auto-generated>
//------------------------------------------------------------------------------

I am getting 508 style cop warnings all from the reference.cs files generated for these services. As I looked at other questions like issue#1145 it is recommended to put // <auto-generated/>. I manually put that at the very top even in front of the header (Just because the auto generated has data in it). It still gives me the warnings. Nothing seems to stop these files from being stylecopped. As for the files I do want style cop to analyze, it is working fine.
Other environment information is as follows:
Visual Studio 2015 Update 3
C# .net 4.6 Class Library project
Nuget StyleCop.Analyzers v1.0.2
Used the built in Add Service Reference to create the service reference.
The web services are using a singlewsdl
Using a StyleCopRuleSet.ruleset file that is common to the whole solution
Is there anything I else I can do? So far I can fix all the issues until I only see messages from the references.cs files. Then disable the analyzer so I don't get any warnings. It would be nice to be able to keep it going all the time. Thanks for providing this tool.

Based on questions asked from issue #1573 I can add:
Stylecop warning is Warning	CS1591	Missing XML comment for publicly visible type or member.
Now that I see that, it isn't an SA warning, it appears that it isn't necessarily a style cop issue. I guess I am just used to getting these types of errors from StyleCop.

@Cthclain See the documentation for SA0001 for tips on how to deal with this compiler error.

The way I got around this was to wrap the code with:
#pragma warning disable CS1591 // Missing XML comment for publicly visible type or member
namespace xxxx
{
   .....
}
#pragma warning restore CS1591 // Missing XML comment for publicly visible type or member


updated node source

Description
This issue no longer appears to be a functional workaround for pinning to a specific nodejs version. Attached is a new apt source where we install the desired version 18.13.0 instead of downloading specifically only 18.13.0. I could not find an explicitly hosted version, but made sure to add hash security for the setup file.
This will hopefully fix our build in the CircleCI pipeline.
Changelog or Releases
Same Node.js version, just sourcing from a new URL

Node.js

Whelp, build isn't fixed quite yet then..


Make rate limit header available in ChatCompletionCreateResponse

Is your feature request related to a problem? Please describe.
For some task, OpenAI have relatively small token per minute and token per day limit.
They do keep track of the usage and give us information about it.
But that information is lost when the library de-serialize to nice objects.
https://platform.openai.com/docs/guides/rate-limits/rate-limits-in-headers
Describe the solution you'd like
A general solution would be a dictionary of response header.
Or even a pointer to the original HttpResponseObject
Describe alternatives you've considered
The alternative is to manipulate HttpClient directly.
But then this library is not used at all.
Another alternative is to use the usage part of the response to implement our own throttling code.
But then the boundary of what is a day, what is a minute for the purpose of those limit may not be in sync.
Additional context
https://platform.openai.com/docs/guides/rate-limits/rate-limits-in-headers
https://platform.openai.com/docs/guides/rate-limits/usage-tiers

Sorry, but the rate limit should already be in BaseResponse. Are you looking for a field that is not present there?

OK updating from 7.3 to 7.4 fixed my issue I think.
This was newly added
public ResponseHeaderValues? HeaderValues { get; set; }


Feature: Persistent kv store

The motivation for this is as follows:
Sidebar should load cached values for scope and exclude. Therefore we should have the ability to persist these values in the user's home folder as follows
cat ~/aderyn-vs-code-tests.json
{
  "/absolute/path/to/project1": {
    "scope": "src/",
    "exclude": "lib/"
  },
  "/absolute/path/to/project2": {}
}

This PR gives tools for doing so. (later if sidebar PR is approved, then this might  also make sense)

Is this a new json format that only the extension will know how to handle?
I'd rather define the json KV store on the CLI level, not the extension.