Info about hazelcasr parameter hazelcast.max.no.heartbeat.seconds

Adding "troubleshoot": killing node makes cluster unbalanced (hazelcasr parameter hazelcast.max.no.heartbeat.seconds)

maybe we should add a more sensible value to the default config too WDYT?

Duplicate of #45

@pmlopes I err on the side of not overriding Hazelcast defaults. Besides I suppose that they chose this default value on purpose. Also note that if you change the heartbeat timeout, you must make sure the heartbeat interval is set accordingly (10 sec by default)

Yes it's a duplicate of #45 - let me check if we can improve the current documentation

I've made a manual merge to include the missing info in the documentation.
Thanks !


Update to serde 0.9

https://github.com/serde-rs/serde/releases/tag/v0.9.0

I am going to look into doing the update. :-)

Great. We'll do ndarray 0.8 with this, and that's fine.


Fix NPM issues causing errors

This PR fixes some issues caused by npm by:

Removing unsupported test library for fabric that depends on packages that fail to compile
Bumps nodejs version from 12 to 16 at samples/chaincodes/chaincode-kv-node/.nvmrc
Removing non-crucial tests from the sample chaincode

Possible fix for #348

Possible fix for #328

Will be resolved in https://github.com/hyperledger-labs/fablo/pull/403


checkpoint with necks

Thanks for your contribution in self-supervised learning. Now I want to train a model with the pretrained model in ImageNet. Could you please release the checkpoint with related necks, such as NonLinearNeckSimCLR in SimCLR?

The pre-trained weights for related necks are not available since they are discarded when transferred to downstream tasks. You may pre-train by yourself to obtain the weights.


Push setting - HTTP 3 (GET) - doesn't send all the data

When I use HTTP 3 (GET) push setting, it truncate the end of the XML data
configure push setting HTTP 3 (GET) Ex : http://<IP>:<PORT>/<TOKEN>?content=
and configure format editor "HTTP option 3 GET" with this template for ex :
<prtg><result><channel>Densite</channel><float>1</float><value>${gravity}</value></result><result><channel>Batterie</channel><float>1</float><value>${battery}</value></result><result><channel>Temperature</channel><float>1</float><value>${temp}</value></result></prtg>
should return (as the test button do) :
<prtg><result><channel>Densite</channel><float>1</float><value>31.7695</value></result><result><channel>Batterie</channel><float>1</float><value>4.28</value></result><result><channel>Temperature</channel><float>1</float><value>21.5</value></result></prtg>
But it truncate the end of the message like this :
<prtg><result><channel>Densite</channel><float>1</float><value>31.7695</value></result><result><channel>Batterie</channel><float>1</float><value>4.28</value></result><result><channel>Temperature</channel><float>1</float><value>21.5</value></re

See wireshark capture :

if I add dummy char at the end it truncate the dummy char and it works but it's not always "truncating" the same amount of chars.
Software:

Platform esp8266
Browser chrome
Version 1.2.0 (..90a5cb)

Goal is to send HTTP push notification to PRTG Monitoring server.

Sorry for the late reply but I never got a notification on this issue.
HTTP get is not intended to be used to send XML it used the format ?token1=value&token2=value2 according to the specification. In theory you can send an xml document as a value if you URL encode the value (which is not a feature that is implemented in gravitymon)
If you want to send XML you can do this using HTTP Post in the body of the message. So use HTTP 1 or 2. Depending on the receiving service you might need to set the right content header to tell the server that you are sending an XML document.

Its a little strange that the data is truncated, i will have a look what causes this. Its not strange that you get a different result on the test button since this is don in the web browser and not in the device.

Hi,
First thanks a lot for sharing your great job with this firmware.
I know it's a bit strange to encode the XML in the URL but it's how the
PRTG sensor works according to the documentation
[image: image.png]
I don't find other sensor where I could send the data in the body that's
why I tried this workaround.
And yes it's even more strange that it doesn't truncate the same amount of
character. I don't find any logic.
Regards,
Le mar. 17 janv. 2023 à 22:40, Magnus @.***> a écrit :

Its a little strange that the data is truncated, i will have a look what
causes this. Its not strange that you get a different result on the test
button since this is don in the web browser and not in the device.
—
Reply to this email directly, view it on GitHub
https://github.com/mp-se/gravitymon/issues/124#issuecomment-1386092950,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A5CIK4NSODRX63D2GASAOILWS4GU7ANCNFSM6AAAAAATQQ5LVA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--

Corentin WAUTHOZ

Thanks for the feedback. The playload should not be truncatated so i will treat this as a bug.
I could not spot anything strange in the code so I hope this is not a limitation in the arduino code

Can you try this build and see if it works for you ? https://github.com/mp-se/gravitymon/blob/dev/bin/firmware.bin

Thank you for the new version of the firmware, for the moment it looks like it solved the issue.
I will try JSON format and multiple reboot asap to make sure.

Its just a small code change that should not affect but i will run through some tests to make sure it works

I've just released the official tested version, should be the same as the one that you tested.


chore(ci): use actuated get-kernel-sources action.

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area CI
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.37.0

CI Build / test-dev-packages-arm64 / test-packages (pull_request) In progress — This check has started...

I don't get why yesterday it was working, and today it is not (it's just hanging).

/hold

/close
Since the test-dev-packages-arm64 falco-driver-loader part is troublesome, i am going to revert it and drop it.

@FedeDP: Closed this PR.

In response to this:

/close
Since the test-dev-packages-arm64 falco-driver-loader part is troublesome, i am going to revert it and drop it.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


How to transform the pretrained models to '.onnx' file, and render it by onnxruntime.

How to transform the pretrained models to '.onnx' file, and render it by onnxruntime.

looks like you could use something like this: https://pytorch.org/tutorials/advanced/super_resolution_with_onnxruntime.html
but keep in mind that the dynamics scripts are outside the model


Multi-expression matching support

Would it be possible (and useful) to have match accept multiple expressions? Each match expression will match the corresponding case expression and evaluated as an and for each expression in a case.
local a, b = 2, 5
match a, b+1 {
  case 1,   a   => { print 'no' }
  case 2,   4   => { print 'neither' }
  case b-1, 6   => { print 'nay' }
  case 2,   a*3 => { print 'THIS CASE will be selected' }
}

If implemented, will probably be neater to have "passthrough" case expressions too, that technically works as a wildcard that always matches for that case expression, albeit it might be difficult to come up with a symbol (or existing keyword) for it.

There is no case in clue

Oops, fixed that. Also unknowingly removed the print parentheses.
As for the latter concern, they do work and end up being if (_internal0 == b-1), etc. The precedence is another story, but in this case it's not a worry (yet)

Oops, fixed that. Also unknowingly removed the print parentheses.
As for the latter concern, they do work and end up being if (_internal0 == b-1), etc. The precedence is another story, but in this case it's not a worry (yet)

this is if statement is basically unintended behavior, since b won’t be defined to what you would expect it to be?

match branches can have any expression for its pattern, even if it's a useless one


Sending empty parameter hashmap in case of retried execution

When a job is retried, it makes a dummy getCurrentRunParameter call to dr. elephant. In this way tuneIN knows that there was a failure with earlier parameters and penalize the parameters accordingly. In current implementation, best parameters are returned as an output of this dummy call even though we don’t apply these parameters and a new entry is made in tuningJobExecutionParamSet which is not correct.
In this change, empty parameter hash map will return as an output of retried dummy getCurrentRunParameter call and make entry in tuningJobExecutionParamSet only for non-tried executions.

@dushyantk1509  Can you mention the problem statement in the Description section of the PR as it will provide more context about the PR. Also the doc link you mentioned above is not accessible for me using my external email-id, can you have a look so that it would be available to all.

@dushyantk1509 Can you mention the problem statement in the Description section of the PR as it will provide more context about the PR. Also the doc link you mentioned above is not accessible for me using my external email-id, can you have a look so that it would be available to all.

Now you won't need docs.


flyctl: 0.0.308 -> 0.0.310

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/flyctl/versions.
meta.description for flyctl is: "Command line tools for fly.io services"
meta.homepage for flyctl is: "https://fly.io/"
meta.changelog for flyctl is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/ssb7p73yp6xxzskpg6y6rh7qwpb1ds2q-flyctl-0.0.310/bin/flyctl had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.0.310 in filename of file in /nix/store/ssb7p73yp6xxzskpg6y6rh7qwpb1ds2q-flyctl-0.0.310

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
flyctl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ssb7p73yp6xxzskpg6y6rh7qwpb1ds2q-flyctl-0.0.310 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A flyctl https://github.com/r-ryantm/nixpkgs/archive/060c73abb96c2c23a907056aef2999e49b3fc545.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ssb7p73yp6xxzskpg6y6rh7qwpb1ds2q-flyctl-0.0.310
ls -la /nix/store/ssb7p73yp6xxzskpg6y6rh7qwpb1ds2q-flyctl-0.0.310/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

flyctl

Maintainer pings
cc @aaronjanse @jsierles @kalbasit for testing.

Result of nixpkgs-review pr 166854 run on aarch64-darwin 1

1 package built:

flyctl


add separators between files/folders to type organization

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
I want files and folders to be separated as it happens in File Explorer/Finder, when organised by type.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?

Merging with #1874

Merging with #1874


Add namespace_packages parameter to find_packages

The user must pass any implicit (PEP 420) namespace packages in this parameter. Packages in this list will be recognized as such, despite not having any __init__.py.
Closes #97

While still discussing this in #97, I'm going to close this here. Since a change like this will have substantial effects on end-users, I want to be sure to get it right. If we end up settling on this approach, I'll be sure to pull the implementation from here.


GH-1351 changed to Step meters

Codecov Report

Merging #1352 into master will not change coverage.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master    #1352   +/-   ##
=========================================
  Coverage     61.74%   61.74%
  Complexity      825      825
=========================================
  Files           136      136
  Lines          3929     3929
  Branches        550      550
=========================================
  Hits           2426     2426
  Misses         1225     1225
  Partials        278      278

Impacted Files
Coverage Δ
Complexity Δ

...ter/DefaultDestinationPublishingMeterRegistry.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


need Information message like Bullets in Hotspot

Hi all,
I have a requirement like below. In hotspots i am showing information message, but i need requirement like Bullets some points.  so i had used '\n\u2022' for bullets in my JSON file. but when displaying its displaying normal message. in element it's displaying as bullets. i have uploaded image below. can you please suggest here. thanks in advance.

above message in image, is it possible to display like this below?
Reception desk is your first point of contact. Do not forget to carry your essential documents like
•	ID/passport
•	Driver’s license
•	Photo
•	Residence permit
Also don’t forget to carry your great attitude!

This was a bug, which was fixed in ab3c3d9fe09da7b28dbf0f1997b33d8b3b7c7bb6. Before the fix, only the first line break would work. The fix hasn't made it into a release yet.

Thanks mpetroff...
when can i expect this release?

The next release will happen when it's ready.

Hi mpetroff,
Please let me know if it's released.
Thanks

Hi mpetroff,
is there any solution for this? can you please suggest me to get this?
Thanks in advance..


Make Box: use react-select to choose Category+Product

The list of categories and products will be quite long, so react-select enables typing to search.
That would be a good way to be able to postpone making the real visual elements that we have sketched.

For tomorrow, I will probably switch all the category/product selects to native selects instead of the material UI overlay. That'll make it much easier to skip through a long list on mobile.
Also: they should be ordered!

@barto74 are you still working on this or shall I pick it up?

@bfirsh you should probably take that, will be faster.

Taking this one (from TA)

Just noting that on this box we show category / product and this would be on the whole category / product string - fine?

@sforz Yep - same as current select, I think.

I did not find the time to finish this one this morning, whoever is going to work on this next might find this link useful though: https://material-ui.com/demos/autocomplete/

I'm on this one.

@bfirsh could you checkout the branch 93/search_to_select_products? I'm stuck. The reason is in the last commit message.


support node 0.12 as well

related to https://github.com/pebble/yieldb/pull/8

Coverage remained the same at 100.0% when pulling af2d087fe4694a0a4fad2a93b9344833eb39b29f on node_0_12_support into c0133197a2ae84a8fde39a7014993e9d261a02de on master.

Coverage remained the same at 100.0% when pulling af2d087fe4694a0a4fad2a93b9344833eb39b29f on node_0_12_support into c0133197a2ae84a8fde39a7014993e9d261a02de on master.

+1


OomError(OutOfHostMemory) When Creating Instance

Version of vulkano: 3518268b7f8080f44c06daf33c90c5b8cb4986d4
OS: Void Linux with Linux 4.19
GPU (the selected PhysicalDevice): Nvidia GTX 780
GPU Driver: nvidia-418.43
Upload of a reasonably minimal complete main.rs file that demonstrates the issue: triangle.rs

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: OomError(OutOfHostMemory)', src/libcore/result.rs:997:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
   1: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at src/libstd/sys_common/backtrace.rs:59
             at src/libstd/panicking.rs:197
   3: std::panicking::default_hook
             at src/libstd/panicking.rs:211
   4: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:474
   5: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:381
   6: rust_begin_unwind
             at src/libstd/panicking.rs:308
   7: core::panicking::panic_fmt
             at src/libcore/panicking.rs:85
   8: core::result::unwrap_failed
             at /rustc/7c19e1eed5418b8c02be65d678417b241ee01a3e/src/libcore/macros.rs:16
   9: <core::result::Result<T, E>>::unwrap
             at /rustc/7c19e1eed5418b8c02be65d678417b241ee01a3e/src/libcore/result.rs:798
  10: triangle::main
             at examples/src/bin/triangle.rs:49
  11: std::rt::lang_start::{{closure}}
             at /rustc/7c19e1eed5418b8c02be65d678417b241ee01a3e/src/libstd/rt.rs:64
  12: std::panicking::try::do_call
             at src/libstd/rt.rs:49
             at src/libstd/panicking.rs:293
  13: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:87
  14: std::rt::lang_start_internal
             at src/libstd/panicking.rs:272
             at src/libstd/panic.rs:388
             at src/libstd/rt.rs:48
  15: std::rt::lang_start
             at /rustc/7c19e1eed5418b8c02be65d678417b241ee01a3e/src/libstd/rt.rs:64
  16: main
  17: __libc_start_main
             at ../csu/libc-start.c:308
  18: _start
             at ../sysdeps/x86_64/start.S:120

https://github.com/vulkano-rs/vulkano/blob/3518268b7f8080f44c06daf33c90c5b8cb4986d4/examples/src/bin/triangle.rs#L49
Issue
System and gpu both have enough memory. I haven't investigated further at this time.

This might be an issue with the graphics installation of my distro. If I manually set the VK_ICD_FILENAMES environment variable vulkan will correctly work.

I'll just add an export to /etc/profile.d/.


Tap Netsuite

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/152
Originally created by @jschatz1 on 2018-11-02 18:33:45

View 7 previous comments from the original issue on GitLab


Added conditional check on 'atexit' event function: the Python interp…

…reter may remove the '_State' class before running the 'atexit' event actions, which yields a stacktrace with a 'NoneType has no _transation attribute' error. Checking on the existence of the '_State' class, and then on its attributes ensures the NoneType error does not appear.

Fixes issue #102


Count users messages as part of user stats

Dependent on new DB https://github.com/EddieJaoudeCommunity/EddieBot/issues/263

This was started but not completed https://github.com/EddieJaoudeCommunity/EddieBot/blob/develop/src/chatty.ts

Hi @eddiejaoude 😃. I'd like to work on this, but I'm not aware of the current status of the database collections. I saw in this issue #32 that usersGithub exists, but there are no references to it on this codebase.
For this issue, would we have another collection for the user's stats, or use an existing collection? Something like this:
import { db, incrementFieldValue } from './firebase';
export const chatty = async (message: Message) => {
    //.....
    await db
        .collection('usersStats')
        .doc(message.author.id)
        .update({ messageCount: incrementFieldValue });
}

From the MEE6 bot, that counts the messages and assigns levels, it doesn't mean we dont do it too in our DB.
Not sure if this should wait until we move to another DB otherwise it will be more data to migrate or drop

you're right, it's better to postpone this after the DB switch since this API will change 👍

I have updated the description to say it is dependent on the DB https://github.com/EddieJaoudeCommunity/EddieBot/issues/263

Would this be integrated in ^bio ?

Or perhaps we could have a server user card (another command), with all this info and profile progress?
Context:
#396

Hi @Vyvy-vi, integrating with the bio command is a great idea 👍, or any UI to show this information (like your user card idea)

Hi @Vyvy-vi, integrating with the bio command is a great idea 👍, or any UI to show this information (like your user card idea)

Nice 👍

Nice 👍

I think this is still needed, stalebot ._.

Since we shifted to the API for data collection, and are re-making the bot, I think it's safe to close this issue


Complete the guide about how to observe the result of stress chaos

Feature Request
Now we already have a document about stress chaos https://github.com/pingcap/chaos-mesh/blob/master/doc/stress_chaos.md, however, this document doesn't tell much about how to observe the result of CPU stress and Memory stress.
It would be much clear to users if we can enrich the document with the observation part.

Still valid.

I am working on #685 (actually it's waiting for review), so that users can observe the stress-ng process easily by htop or ps.
But I think the document is still needed, because in the parent process of stress-ng will be PID 0 in the container, so htop will regard it as "kernel threads" and will not show by default. The users have to turn off "hide kernel threads" to see these process.


WIP Active topic management

Purpose of Changes and their Description
Currently active topics are in one large keyset that must be parsed in pages in order to find topics.
This is not scalable as the number of topics increases.
Furthermore, there are some minor issues with respect to how topic weight is calculated -- and EMA is often used where the non-EMA may be more appropriate.
This PR attempts to address these concerns by segmenting the list of active topics by block height of the next epoch.
So, there is no longer 1 keyset for all active topics.
Instead, we map block height to a bounded list of topics.
When a topic is (re)activated, we append it to this list but knock off the topic of lowest weight to maintain a bounded set size.
We also introduce a cache for topic weight and lowest topic weight per "active set for a block" to minimize compute.
Link(s) to Ticket(s) or Issue(s) resolved by this PR
https://linear.app/upshot/issue/ORA-2068/patch-active-topic-parsing
Are these changes tested and documented?

[ ] If tested, please describe how. If not, why tests are not needed.
[ ] If documented, please describe where. If not, describe why docs are not needed.
[ ] Added to Unreleased section of CHANGELOG.md?

Still Left Todo
Fill this out if this is a Draft PR so others can help.

Approved changes I have coming in: https://github.com/allora-network/allora-chain/pull/557

Will also do changelog in a batch to add even more color to all recent PRs including this one


frontend: add attachment button + editor theme update

This PR implements the changes from an earlier PR to add an attachment button to the frontend. It also updates the Monaco editor's theme to match the overall UI theme for a consistent look and feel.

LGTM, thanks!


[DH-541] Support Elasticsearch 5.5.

Biggest difference is that Elasticsearch 5 has fielddata set to False by default. It means that we have to set it to True for the string fields we want to sort by.

Codecov Report

Merging #439 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           develop    #439      +/-   ##
==========================================
+ Coverage     95.9%   95.9%   +<.01%
==========================================
  Files           94      94
  Lines         3074    3075       +1
  Branches       272     272
==========================================
+ Hits          2948    2949       +1
  Misses          86      86
  Partials        40      40

Impacted Files
Coverage Δ

datahub/search/dsl_utils.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Do we have ES 5.5 instances on standby ready to switch to? Should we change the name of the ES_URL environment variable to e.g. ES5_URL, just thinking it might make deployment easier.

I don't know exactly why you started to use fielddata but the docs say that we should really avoid them as

fielddata can consume a lot of heap space

As I understand, fielddata is just for rare cases. Most of the times, if you need sorting or aggregations on text, it's better to use keywords which support doc_values.
Why don't we use raw https://www.elastic.co/guide/en/elasticsearch/guide/master/multi-fields.html for sorting?

@marcofucci in 2.4 fielddata is enabled by default on those fields. I think the first step would be to get compatibility first and then do optimisations specific to the platform.
Regarding multi fields we just use multiple fields in the model as this was more convenient (in a fieldname_variation format. As a next step we could add a keyword field for the purpose of sorting.
But if we want to have case insensitive sorting, then we need to keep fielddata, as Keyword is case sensitive.

@reupen I don't know about instance. But having new env variable sounds good. I will add that.

@elcct 👍  makes sense to refactor in steps.
In 5.x there seem to be a new normalizer thing which we could use.


Java CQL->ELM compiler seems to use FHIR types or bindings that do not exist.

In the file AntithromboticTherapyByEndofHospitalDay2FHIR.cql we find:
define "Reason for Not Administering Antithrombotic":
  ["MedicationAdministrationNotDone": medication in "Antithrombotic Therapy for Ischemic Stroke"] MedicationAdm
    where ( MedicationAdm.statusReason in "Medical Reason for Not Providing Treatment"
        or MedicationAdm.statusReason in "Patient Refusal"
    )
    return {
      id: MedicationAdm.id,
      authoredOn: MedicationAdm.recorded
    }

According to the generated ELM, the type of  authoredOn in the returned tuple is {http://hl7.org/fhir}NotDoneRecorded, which is not a known type.
I will remove this statement to continue.

This is probably related to how QICore datatypes/bindings are translated to FHIR types in issue #194.

Idem for {http://hl7.org/fhir}EncounterProcedureExtension in IntensiveCareUnitVenousThromboembolismProphylaxisFHIR


slow moving to next image or play button

hi
i have last cvat install on server and docker
i am using 4k images
the cvat next image  button, after i press it 4-6 times the cvat stop and wait for 10s and then move to next image
the same with play button the cvat play about 20-30 frames and then halt for 20s and again

Hi,
The web application does not store all your images in a browser (actually it is impossible because of different browsers limitations). It stores only small parts of them you recently requested.
So, when you navigate it sometimes goes to the server to fetch new images and decode them, what might take significant time in case with 4k images.
If you press play, additionally to the requested frame it also fetches and decodes a buffer beforehand. It is why it takes more time.

You can try to decrease image quality when create a task, if you annotate large objects.

I am having the same issue with the player being slow for high resolution images. Decreasing the image quality is not an option since the user needs to be able to view the fine details to annotate each frame in the movie.


Trouble installing, starting gitdocs

I've had to reinstall the system where I was previously successfully running gitdocs (pre3, 4 or so).
First try is to do: gem install gitdocs --pre
This results in a gitdocs executable which, when I do: gitdocs start, I get:
"Daemonized process couldn't be started, Failed to start gitdocs". And I don't know how to get further debug information. No --debug?
Another attempt is cloning this very repository, and trying to "rake", but then I run into a lot of problems like "... Unable to activate coveralls-0.7.2, because thor-0.14.6 conflicts with thor (= 0.18.1)". And so on. One might think that the above try would have installed all neccessary gems of the right version, but perhaps that is the actual problem above as well!
I would be happy to start running gitdocs again! : )

As outlined here: https://github.com/nesquena/gitdocs#starting-gitdocs start gitdocs in debug mode and let us know what the logs say.

This results in a gitdocs executable which, when I do: gitdocs start, I get:
"Daemonized process couldn't be started, Failed to start gitdocs". And I don't know how to get further debug information. No --debug?

@quite the failure to daemonize message can mean that another copy of gitdocs is already running. You can check this by running:
gitdocs stop
ps ax | grep gitdocs

If the output is empty, then you should be able to start
If it is not empty then kill the stray gitdocs processes first, and then try to re-start.
If this still does not work then you can try starting in debug mode with:
gitdocs start -D

(as described in the docs that @nesquena mentioned) and let us know what messages are displayed.

Another attempt is cloning this very repository, and trying to "rake", but then I run into a lot of problems

You do need to use bundler to run things in the repository, but this is not documented. I really should add a section about this. So if you want to clone and then see the possible rake tasks you would do the following:
gem install bundler
git clone git@github.com:nesquena/gitdocs.git
cd gitdocs
bundler install # which should install all the dependencies
bundle exec rake -T # which should show the available rake tasks

At this point you would be able to run the from the repository with:
bundler exec gitdocs start

(again being careful that you are not already running another copy of gitdocs already)
Sorry for the late reply, but I hope that this information is help.
And I look forward to hearing about any progress you make.

Sorry, I've not had the time to try and set up gitdocs again after running
into this problem. Probably what you both write will help me solve this,
once I do get the time (apparantly my need for gitdocs isn't very big
currently :) So I think it's safe to close this.

Cool. I will close it for now. But I'll follow up on the bundler docs and see about adding more details to the failure to start message.


Fix stack-card integration test

There was an integration test that was not being set a proper environment to the tested component .

Merged!


Window resize events are flooding the breadcrumbs log

Platform
Flutter Desktop
Obfuscation
Disabled
Debug Info
Disabled
Doctor
[√] Flutter (Channel stable, 3.16.0, on Microsoft Windows [Version 10.0.19045.4046], locale en-GB)
    • Flutter version 3.16.0 on channel stable at C:\Users\barabas\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision db7ef5bf9f (4 months ago), 2023-11-15 11:25:44 -0800
    • Engine revision 74d16627b9
    • Dart version 3.2.0
    • DevTools version 2.28.2

[√] Windows Version (Installed version of Windows is version 10 or higher)

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at C:\Users\barabas\AppData\Local\Android\sdk
    X cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    X Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Professional 2022 17.7.6)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Professional
    • Visual Studio Professional 2022 version 17.7.34221.43
    • Windows 10 SDK version 10.0.22621.0

[√] Android Studio (version 2023.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-b2043.56-10550314)

[√] IntelliJ IDEA Community Edition (version 2023.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2023.2.3
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19045.4046]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 103.0.5060.53
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 122.0.2365.66

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Version
7.13.2
Steps to Reproduce

Integrate sentry with the app
Resive the window
Submit an event (Sentry.captureMessage)

Expected Result
Some resize breadcrumbs are visible, other breadcrumbs also visible
Actual Result
hundreds of resive events are added within a second, can't find other breadcrumbs in the noise
The window resize events should be debounced at a rate of 1 per second or so.
Are you willing to submit a PR?
No

This seems like a duplicate of https://github.com/getsentry/sentry-dart/issues/400


build(deps): bump Yarn to 3.7.0

@deivid-rodriguez We can start with this one as #8265 will need more work


Contact us block

Almost all pages have a contact us block with a background image and a round cutout:

this should be possible using the feature implemented in #40 - can you verify?

There are a couple things missing:

h1 font invert
center content
increase padding at the bottom

currently looks like this:


[backport] Fix Decorrelated Batch Normalization tests

Backport of #8260

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 531b7a33d9319c77b499ab10706095607c790d4d, target branch v6) succeeded!

Jenkins, test this please

Jenkins CI test (for commit 531b7a33d9319c77b499ab10706095607c790d4d, target branch v6) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 531b7a33d9319c77b499ab10706095607c790d4d, target branch v6) succeeded!


Removed list of 100 passwords and replaced it with the 100k list of m…

…ost common passwords

@CapellaBlue , which list of 100k did you use?


Use CHAINER_READTHEDOCS instead of READTHEDOCS

I set CHAINER_READTHEDOCS=1 in RTD configuration (only Chainer maintainers can access this page): https://readthedocs.org/dashboard/chainer/environmentvariables/
Note: it seems environment variables cannot be controlled via readthedocs.yml.

Closing as #7363 is better than this PR.


Create a streamlit tool to define map brackets in explorers

Choosing map brackets is painful. At an individual chart level, at least we have a visual tool to achieve this (however, it can be improved, there is an issue on how to achieve this, and another issue on what should be the default strategy).
But for explorers we don't have any tool in the grapher admin. So, creating file-based or indicator-based explorers means manually going view after view and manually setting each of the numeric bins.
To begin with, we could have a tool in streamlit that:

ingests a variable id,
fetches the data from https://api.ourworldindata.org/v1/indicators/{variable_id}.data.json,
shows a grapher map chart,
lets the user pick the map brackets,
returns the bracket values.

Then, instead of ingesting one variable, it could get a list of variables, and the tool would let the user tweak the brackets one by one (with a similar layout to chart-diff).
So, the user would go to an explorer admin, select the variable ids from a column, copy them to the clipboard, paste them in the streamlit input, tweak all brackets, copy the resulting list of brackets to the clipboard, and then paste them back in the explorer.

Is this done for now, from your perspective @pabloarosado ?

Yes, @larsyencken I think we can close this for now. We can improve it little by little as we use it.


ci: add all builds tag

/claim #1375
/fixes #1375
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

Summary by CodeRabbit

New Features

Added a feature to trigger builds on all supported platforms by using the new label "ci: build all."
Enhanced the CI workflow by introducing a new job that builds on various platforms based on pull request conditions and labels.

Please review @tusharmath

@tusharmath can you please re-review this?

@Bhavyajain21 Thanks for the change. Can you make a quick change here? Let's run the test all on platforms always, irrespective of the labels.
Also you can use & to reduce duplication in YAMLs, check this cheatsheet out https://quickref.me/yaml.html

@Bhavyajain21 Thanks for the change. Can you make a quick change here? Let's run the test all on platforms always, irrespective of the labels.
Also you can use & to reduce duplication in YAMLs, check this cheatsheet out https://quickref.me/yaml.html

Hey @tusharmath , are we expecting a change anywhere else?

@Bhavyajain21 Thanks for the change. Can you make a quick change here? Let's run the test all on platforms always, irrespective of the labels.
Also you can use & to reduce duplication in YAMLs, check this cheatsheet out https://quickref.me/yaml.html

Got your point, making the change

@tusharmath made the changes, please review.

@Bhavyajain21 This PR isn't making much sense anymore. What have you done? Labels change still exists.
Closing this PR for the sake of reducing noise. Feel free to create a new one whenever you think it's ready.


Fn::Cidr should support Fn::GetAtt (E1024)

cfn-lint 0.6.1
I get the following error:

E1024 Cidr ipBlock should be Cidr Range, Ref, or Select for Resources/MySubnet/Properties/CidrBlock/Fn::Select/1/Fn::Cidr/0/template.yml:123:7

Resources:
  MySubnet:
    Properties:
      CidrBlock: !Select
        - 0
        - !Cidr
          - !GetAtt 'MyVPC.CidrBlock'
          - 16
          - 8

Although the documentation doesn't mention the Fn::GetAtt in the list of supported functions, it is used in the CloudFormation examples on the same page.
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/intrinsic-function-reference-cidr.html

Guess we should have a documentation update too.


Edit pass on article.

Category

[ ] Content fix
[ ] New article
[x] Example checked item (delete this line)

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
(DELETE THIS PARAGRAPH AFTER READING)

Related issues:

fixes #issuenumber
partially #issuenumber
mentioned in #issuenumber

If this fixes (aka: closes) or references an issue, please reference it here. This helps maintaining the issue list as it will (1) link the PR to the issue & (2) automatically close the issue when this PR is merged in.
(DELETE THIS PARAGRAPH AFTER READING)

What's in this Pull Request?

Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
(DELETE THIS PARAGRAPH AFTER READING)

Guidance

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.
(DELETE THIS PARAGRAPH AFTER READING)

This PR has conflicts if merged... please fix these before submitting.
Also as a policy, this repo requires contributors to complete the issue & PR template that is created on new entries prior to submitting. Please complete this form in the future as all issues & PRs that don't complete the template will be automatically closed.


Handle nested fp8 autocasts

Fixes the case of handling nested fp8_autocasts as well as moving from fp8 → high precision training. See comment for example.

/te-ci


feat: compare contractAddress and chainId in PrimaryDashboardButton component

PR-Codex overview
This PR updates the condition in primary-dashboard-button.tsx to compare both contract address and chain ID.
Detailed summary

Updated condition to compare contract address and chain ID
Added check for chain ID equality with chain?.chainId

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#2655  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


Cannot update icon and cover

The problem
In the new version, Notion added an icon and image cover support and consequently fields in API, but the SDK doesn't support this feature (and fields) yet.
Possible solution
I suppose the problem is here in line 147:
https://github.com/ramnes/notion-sdk-py/blob/4dc60c491b51d152fdb93caa0efd00d91f30adb9/notion_client/api_endpoints.py#L135-L149
I guess It should be changed like that:
# "icon" and "cover" fields were added
body=pick(kwargs, "parent", "properties", "children", "icon", "cover"),

👋 looking forward to have this in a release 🎉
Thank you @fedor-ivn @al1p 👏


Refactor tests to facilitate additions

The tests are very repetitive with copied/pasted snippets. We need to refactor many of them as for loops with types.

Fixed on master.


minor change to module initGenesis

related to https://github.com/cosmos/sdk-tutorials/issues/275

lol I just did the opposite of this: https://github.com/cosmos/sdk-tutorials/pull/279/commits/800d8943df63f728ec9173f42f6ef5146f67819e
Which is more standard? to have func InitGenesis return the validators or just func (am AppModule) InitGenesis return them?

for modules that do not return any validator update they dont return []abci... so this pr can be closed


[BUG] Undesirable performance warnings

Describe the bug
The upgrade to Cython 3.0.3 on the Apache Arrow CI suddenly produces a lot of similar warnings when compiling our Cython files. Example:
  [1/129] Compiling Cython CXX source for _compute...
  performance hint: pyarrow/_compute.pyx:380:39: Exception check will always require the GIL to be acquired. Possible solutions:
        1. Declare the function as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.

https://github.com/apache/arrow/actions/runs/6452131883/job/17513702248#step:6:3712
The warning is legitimate in itself (that is, the analysis is right), it's just that it produces no actual value for us, and we get hundreds of instances of this warning simply because it flags a very common and convenient construct in the Arrow Cython source code (that construct unpacks a C++ result-or-error type and raises a Python exception on error).
Several complaints here:

I skimmed through the docs and I haven't found how to disable the warning (in particular, it does not seem mentioned here). It should be possible to disable warnings selectively, because they otherwise can obscure other more important pieces of information.

I also find weird that the warning message seems to introduce several "Possible solutions" but only one is displayed. Is the message truncated?

Code to reproduce the behaviour:
No response
Expected behaviour
No response
OS
No response
Python version
No response
Cython version
3.0.3
Additional context
No response

cc @AlenkaF

cc @danepitkin

There is compiler options for that:
https://github.com/cython/cython/blob/459f7c6236b7507b664703e6a20aafafe22f8a21/Cython/Compiler/Options.py#L153C8-L153C8
The reasy why it is not present in documentation is that currently there is only documentation of Cython 3.0.2 not sure why.

There is compiler options for that:

Is there a corresponding command-line option?

currently there is only documentation of Cython 3.0.2 not sure why.

Build failure in readthedocs due to API changes on their side. I'll try to fix it.

2. I also find weird that the warning message seems to introduce several "Possible solutions" but only one is displayed. Is the message truncated?

No. It's a template that can output different numbers of options depending on the context, and you're (correctly) only getting one. I suspect it's worth tweaking the grammar a bit in that case though.

It's obvious a bit tricky - we want the message to be visible (because otherwise nobody will benefit from it, and it is a slightly unintuitive performance change) but don't want it to be disruptive. I'd deliberately made it "not a warning" so it wouldn't trip with -Werrors. But maybe it could be a bit easier to turn off.
The other thing we could might be able to change is to only show it on implicitly except * functions, and to assume that people who've manually added except * know what they're doing and don't need to see it.

The other thing we could might be able to change is to only show it on implicitly except * functions, and to assume that people who've manually added except * know what they're doing and don't need to see it.

Hmm, this is in a with nogil block, so I don't see where we would add a except * block.

Hmm, this is in a with nogil block, so I don't see where we would add a except * annotation.

On the function.
cdef Something func1() nogil except *:
   ...

# later
with nogil:
  func1()

and explicitly putting it on the function definition would turn it off. (To be clear, this is something we could do - I don't think it's something we've done)

I wasn't really saying anything about inner functions. Your declaration of GetResultValue looks to be https://github.com/apache/arrow/blob/ad26f3ff2348292be8d723be64f443553c3703f3/python/pyarrow/includes/common.pxd#L167.
I was suggesting that the explicit extern * on that declaration would tell Cython that you know about the exception behaviour and be enough to turn off the warnings for the calls.

I was suggesting that the explicit extern * on that declaration would tell Cython that you know about the exception behaviour and be enough to turn off the warnings/hints for the calls.

Ah, thank you for the clarification. Yes, that would work for us.

... doesn't mean you shouldn't have a command-line option or similar to turn it off too. Just thinking about ways that it could be made a little more targeted to only the people who need it.

By the way, I can't seem to be able to pass the relevant option on the command line:
$ python -m cython --version
Cython version 3.0.3
$ python -m cython -X show_performance_hints=0
Traceback (most recent call last):
  [...]
ValueError: Unknown option: "show_performance_hints"
$ python -m cython -X show-performance-hints=0
Traceback (most recent call last):
  [...]
ValueError: Unknown option: "show-performance-hints"

It seems that documentation even after update still missing show-performance-hints option. I created PR fixing it.

By the way, I can't seem to be able to pass the relevant option on the command line:

I am afraid that currently it is not possible. If I am not wrong the only way how to turn it off is by setting it programatically as showed in example: https://cython.readthedocs.io/en/latest/src/userguide/source_files_and_compilation.html#compiler-options

I am afraid that currently it is not possible. If I am not wrong the only way how to turn it off is by setting it programatically as showed in example

Ouch...

There is discussion to expose it as directive see #5759


Users banned as "Sock puppet" for no reason

As previously reported at https://github.com/arduino/forum-issues/issues/177#issuecomment-298292857 @Andy2No and I have both been permanently banned from the forum and both of us believe this was an error rather than a result of our actions. My user name on the Arduino forum is pert. There was one other report of this happening after the website update on 2017-04-27 near the start of this forum thread:
http://forum.arduino.cc/index.php?topic=473506
I'm unable to link to the exact reply in that thread because I can't even browse the forum now (https://github.com/arduino/forum-issues/issues/177)!
I get this same message when I try to visit the forum:

Hi Pert!
It was you I was trying to thank - for the advice about using Github too,
which has been a bit of a mystery to me, for some time.
I was just about to press the submit button on another post on the Github
issue, so I'll do that next, but it seems the solution (maybe temporarily)
is to clear your browser history.  It might just be cookies, if not try site
preferences etc.  I did and it let me back in, without needing to log in.
I'm feeling a bit shell shocked :)  I hope it works for you too.
Best Regards,
Andy
----- Original Message -----
From: per1234
To: arduino/forum-issues
Cc: Andy2No ; Mention
Sent: Monday, May 01, 2017 7:55 AM
Subject: [arduino/forum-issues] Users banned as "Sock puppet" for no reason
(#233)
As previously reported at #177 (comment) @Andy2No and I have both been
permanently banned from the forum and both of us believe this was an error
rather than a result of our actions. My user name on the Arduino forum is
pert. There was one other report of this happening after the website update
on 2017-04-27 near the start of this forum thread:
http://forum.arduino.cc/index.php?topic=473506
I'm unable to link to the exact reply in that thread because I can't even
browse the forum now (#177)!
I get this same message when I try to visit the forum:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey, that's cool that I helped you and now you are helping me. Thanks!
I cleared the browser cache and still couldn't get in. Then I cleared my cookies and that solved the problem. So it may be that you only need to clear cookies. I'll leave this issue open for a while since I'm sure others are having the same problem and they will be more likely to see this issue if it's open.

Cool.  I'm glad to hear it.  I just hope it stops at having to do that, and doesn't mean it stops working all together in one browser, as mentioned in the link I posted in the other thread:
http://forum.arduino.cc/index.php?topic=211822.0
Sorry.  Still tired, and slightly shell shocked.  I hope this isn't to disjointed.

It just happened to me again, and I was able to solve it again by deleting cookies.

I deleted my cookies in Firefox but I am still unable to use the forum while logged in. Without logging in it works.

I haven't heard any new reports of this issue so I'm going to assume it's fixed.


Kanban Board

Below is the link to the Kanban Board for this project:
Recipe App: Kanban Board
This is a 2-person project and the authors are:
@peterdtitan
@Santosh-Konappanavar

Done and resolved ✅ ✅

Hi team,
Your project is complete!  🥳
Congratulations! 🎉
Status: Approved✔
Highlights

No linter errors
Descriptive PR
Great job adding the missing tasks to the Kanban board
Great follow-up with the previous reviewer.

Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Fix USB armory reference

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@832444b). Click here to learn what that means.

Additional details and impacted files
@@          Coverage Diff           @@
##             main    #162   +/-   ##
======================================
  Coverage        ?   0.00%
======================================
  Files           ?      20
  Lines           ?    1437
  Branches        ?       0
======================================
  Hits            ?       0
  Misses          ?    1437
  Partials        ?       0

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


Fix asset path in stylesheets

Closes #129. For real.
Move package path to its own variable. Apply to images, font, and npm packages.

+1

+1


Accordion hide/display for Header Tags and Categories

This theme consists of a header, the one which appears on the homepage with the author avatar etc., which contains the tags and categories. These categories and tags are hidden if the viewport height is insufficient and a button appears on the top-right of the header.
Currently, the tag/category hide/show action is based on display property and hence quite primitive. It would be better to use accordion for the hide/show action.

The required code can be found in header.html.


Creation of ballot paper needs lot of time

create an election with e.g. 25 candidates and project it
start a ballot
create the PDF for the ballot paper

result: it takes on my PC 10 seconds until I get a PDF. On my Laptop it takes even 16 seconds.
I am wondering about this long time because there is not much to calculate.

duplicate, see #3116


Detected that custom integration 'ge_home' calls async_forward_entry_setup for integration

There was an issue on this, #271 however it was marked closed. I'm still seeing this as of v0.6.12 on 2024.9.3, so I do not believe this issue is actually resolved.
2024-09-26 04:43:56.357 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'ge_home' calls async_forward_entry_setup for integration, ge_home with title<EMAIL_ADDRESS>and entry_id: ***, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/ge_home/update_coordinator.py, line 180: await self.hass.config_entries.async_forward_entry_setup(, please report it to the author of the 'ge_home' custom integration

That's right. This was not the correct fix. #273 has the correct fix.

This should be done as of 0.6.13, please let me know if it's not fixed.


Upload build assets to a release if tag push

Detect if the build is from a tag. If so:

Generate a new release
Upload binary build assets to release

Tidy up old builds, keeping the 10 most recent.

Superceded.


Improper behaviour of z_clock_announce() when ticks argument is greater by 1

The z_clock_announce() unconditionally adjust dticks of first timeout in the list:
if (first() != NULL) {
	first()->dticks -= announce_remaining;
}

However this adjustment is not always valid:

If the adjusted timeout was on the list before call to z_clock_announce(), we have to do such correction in order to not delay next timeout.

If the adjusted timeout belongs to periodic k_timer which was handled during current z_clock_announce() execution, we should do such correction if we would like to not accumulate error.

If the adjusted timeout was added during current z_clock_announce() execution but it is not related periodic timer which was handled, we have to skip the adjustment. If we perform it, the newly scheduled timeout will fire earlier than expected.

This issue has been initially mentioned in https://github.com/zephyrproject-rtos/zephyr/issues/11722.
Affected use case is presented here: https://github.com/zephyrproject-rtos/zephyr/issues/12247#issuecomment-451456702

@andyross, @pabigot, @carlescufi: FYI

@pizi-nordic, this is getting out of hand.  Not.  A.  Bug.  I don't know how else to explain it.  Existing tests require the behavior as implemented.  What you are worrying about is an untested edge case that results from an an API convention issue and happens only in latency crisis situations where interrupts have been delayed more than a tick.
It can be fixed via API (and worked around right now), but it requires design and ideas and discussion.   I tried to isolate that discussion in #12247.  But not it's leaked out as a "bug" and I genuinely don't know what to do.
If you have code that actually fails and has no workaround, submit it as a test first and then submit the bug.  But for now... I just don't know how else to deal with this.  Stop this senseless argument.  Please do not resubmit this without an exercising test case (and not a whiteboxed one!)

We need consensus on whether this is a bug, since @pizi-nordic and I disagree with your assessment.  If it is a bug, it may very well require API and other changes to resolve.  That's fine, and not a motivation for closing it until we have consensus.

(And yes, I know you think you understand this better and that I'm missing something important.  But without a failing test case it's not a bug, and I'm tired of typing about it)

Without a failing test case, it's not a bug.  Please stop this senseless fight.  There's a perfectly good discussion elsewhere.


dts: arm: nordic: Add qdec label for nRF5340 and nRF54L15

The "qdec" label allows referring default QDEC in consistent way.

Discussed offline with @anangl. qdec label was introduced only for backwards compatibility and should not be used for new SoCs with multiple QDEC instances. I will think about another solution.


#3 provide mappers to map common HTTP errors

This PR adds exception mappers for common HTTP errors. The mappers
are registered with higher priority then the default mappers provided
by Quarkus.


[Potential] error in computing attention and final word probability

Hi,
In the attention_decoder.py, you compute attention scores over the encoder states from L92 - L103.
I can't seem to find where you've masked the encoder features of size - (batch_size,attn_length, attention_vec_size). Without masking, the computed attention score will be incorrect. It will assign values to encoder states that correspond to PAD tokens upon taking softmax.
Also, the word probability over the extended vocabulary is computed using tf.scatter_nd. This does not work in case of duplicate indices as the output will be non-deterministic and not summed up.. So, if the source text had more than occurence of an OOV word then it will become a problem.

Hi @hashbangCoder, thanks for the questions.
About the encoder padding: yes I think you're right. As the code stands, each encoder hidden state (including those corresponding to PAD tokens) receives an attention score, and the softmax  calculation on this line will include those PAD locations. So the attention distribution sums to 1.
To fix this, I think it would be as simple as just inserting a line here and here that applies a mask to e, setting e to zero in the PAD locations.
I just ran a quick experiment to see to what degree this has an effect when you run the code with the default settings and data. Firstly, all articles are truncated to first 400 tokens, but almost all articles have more than 400 tokens, so they have no padding. This means that for almost all examples, this error does not make a difference. Second, I observe that for those examples that are shorter than 400 tokens, the attention on the PAD locations starts small and then quickly decreases to zero.
About scatter_nd: I don't understand your question. Why does it not work if there are duplicate instances of an OOV word?

Thanks for the reply!
I have a solution for the attention bug. You could just mask with (-inf) before applying softmax. This will ensure the padded states are assigned 0 probability. Don't know you'd do it in TF, but am sure its possible.
Well, I'm using Pytorch and the scatterin that doesn't work with duplicates and overwrites to the last instance of the index. I looked up Tensorflow's scatter and while it made no mention of this, I wasn't sure if it indeed sums all instances of the index.
Sorry about that.

Yes, I just realized that setting to zero before softmax is not correct. You either need to set to -inf before softmax (that feels pretty hacky though) or set to zero after softmax, then re-normalize. I've implemented the latter and am testing it out.
tf.scatter_nd performs addition; see this discussion.

I would disagree about -inf feeling hacky for example openNMT in their Pytorch implementation use it for masking. Im curious as to how you're renormalizing after SoftMax i.e how you're redistributing the probability of masked out values to the remaining elements.
Also, I've implemented your model in Pytorch and am training it currently. I'm surprised by how you managed to fir the entire model (50,000 vocab_size, 256 hidden_size, 140 max_abstract and 400 max_article) on one GPU.
I had to reduce my vocabulary to 25,000 to accommodate the other parameters on an Nvidia TitanX with 12G of memory.  Maybe it has to do with the fact that you're using Adagrad which might be using less memory than Adam (not sure of this since both track param history)

@hashbangCoder The matter of masking the encoder states before taking attention has been fixed in the latest commit.

@abisee
Thanks for the bug fix! It would be helpful if you could answer the memory intensive nature of the model above.

@hashbangCoder I also had problems fitting everything in GPU memory, and as far as I can remember the most important hyperparameters were max_enc_steps and vocab_size. Is your word embedding size the same too? Perhaps the GPU we were using has a greater memory capacity than the one you're using? Unfortunately I am not an expert in understanding how GPU memory works, but I believe it's often be more complicated than you might think.
Good luck!


bluesky: no domain redirection?

Hi hello
I have the mastodon account<EMAIL_ADDRESS>that I bridged to https://bsky.app/profile/zy.masto.bike.ap.brid.gy/
is that normal htpps://zy.masto.bike.ap.brid.gy/ doesn't redirect to the bsky.app profile as it does with any normal *.bsky.social account?

Interesting idea! You're right, we don't implement that right now. We could consider it, but it's unlikely. For one thing, it'd be very difficult to do over HTTPS; details in https://github.com/snarfed/bridgy-fed/issues/744


Changelog

Start making versions/changelogs?

I think this would be included in #347 , closing issue


shades_colorGenerator by Ukesh-dev

Description
Shades_ColorGenerator

A website with the functionality to generate and copy the different shades of colors to your clipboard.
Made with Reactjs.

Closes #51
Add GIF/ScreenShot

Task Checklist
Put x in between the square brackets without any spaces to tick your Task.

[x] You have created a new branch for contribution.
[x] Added README.md for your project in a specified folder.
[x] Add Demo in GIF or Screenshot form.
[x] You are Registered Officially for HacktoberFest 2021 as Partcipant.
[x] Followed Contribution Guidelines.

Issue
Mention your issue no. #51
Author name:Ukesh Shrestha

Thank you @Ukesh-dev  For contributing @Tenet-Coding


Update postgresql to 42.2.18

Updates org.postgresql:postgresql from 42.2.14 to 42.2.18.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.postgresql", artifactId = "postgresql" } ]

labels: library-update, semver-patch

Codecov Report

Merging #491 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #491      +/-   ##
==========================================
- Coverage   89.47%   89.43%   -0.05%
==========================================
  Files         121      121
  Lines        2708     2707       -1
  Branches       82       82
==========================================
- Hits         2423     2421       -2
- Misses        285      286       +1

Impacted Files
Coverage Δ

...scala/hydra/kafka/ingestors/KafkaTopicsActor.scala
96.42% <0.00%> (-3.58%)
:arrow_down:

...main/scala/hydra.ingest/http/SchemasEndpoint.scala
92.53% <0.00%> (-0.06%)
:arrow_down:

Continue to review full report at Codecov.

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

Postgres has since been removed.

Postgres has since been removed.


Set the SDL hint to minimize on focus loss in fullscreen

The default value for SDL_HINT_VIDEO_MINIMIZE_ON_FOCUS_LOSS has changed in SDL 2.0.14
The change was made in https://github.com/libsdl-org/SDL/commit/1947ca7028ab165cc3e6cbdb0b4b7c4db68d1710
Setting it to true restores the expected behavior, which we had before the bump of SDL libraries.
This PR also reverts the change made in #4344 as it's not needed, and that change created more problems.
Closes #4346 because of the revert.

Will probably fix https://github.com/ppy/osu/issues/12260

Doesn't fix the mentioned issue.

Nice catch. I actually saw this change and forgot to test whether it is something we wanted. Seems like a weird default to change, but I guess they were doing testing with it. We'd want to report our results back to upstream so they are aware of the new issues introduced by this change.

Looks to work great on windows, but not fix the macOS issue. Probably makes sense since I think that one has always been an issue, even before the recent version bump.


Cancel the async openAI.chatsStream(query: query)

Is your feature request related to a problem? Please describe.
Simple use case:
let task = Task {
    for try await result in openAI.chatsStream(query: query) {
        print(result)
    }
}

During the streaming, if I cancel the task manually (e.g. The stop generation button in the official ChatGPT app), I expect the stream to be stopped.
task.cancel() // Expecting the network connection to be cancelled too.

Unexpectedly, by monitoring the network activity, the generation does not stop even if the task has been cancelled.
This is due to (by my poor understanding) the underlying StreamingSession does not stop alongside with the task accordingly.
// func performStreamingRequest<ResultType: Codable>(request: any URLRequestBuildable, onResult: @escaping (Result<ResultType, Error>) -> Void, completion: ((Error?) -> Void)?)
let session = StreamingSession<ResultType>(urlRequest: request)
// ...
session.perform() // Once initialized never stopped

Describe the solution you'd like
Use the onTermination method to handle cancellation from the outside task.
This pull request might also help
Describe alternatives you've considered
Empty
Additional context
Empty

This might be useful to you @thekoc
https://github.com/longseespace/OpenAI/commit/a290a1a119fc465cdb1740472242fbfca57069b9

I also need this feature, and would like to be able to proactively cancel stream requests.
Why hasn't the developer handled this issue?

I needed this feature, but nobody responded, so I implemented it myself, thanks   https://github.com/longseespace/OpenAI/commit/a290a1a119fc465cdb1740472242fbfca57069b9 .
In case others need it too, I submitted a  PR https://github.com/MacPaw/OpenAI/pull/214 .


when click the menu button, a piceture of Java flash on full screen

Use non-ajax button for navigation to fix it


Update TrustChainManager.cs

Fixed opConf.AuthorityHints issue. With real endpoint the result can be null.

i agree


⚠ Digital Ocean - https://status.digitalocean.com/ has degraded performance

In 499205d, Digital Ocean - https://status.digitalocean.com/ (https://status.digitalocean.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 86 ms

Resolved: Digital Ocean - https://status.digitalocean.com/ performance has improved in ad11699.


Plugin icons

[x] Display icons next to built-in plugins
[ ] Display icons next to third-party plugins


Fix Self SignUp Issue on the Response Message

Message comes from IS product. Since we are directly registering users when self sign up, our passing prop for IS is wrong. Changed it the appropriate one.
New Screenshot -

Closing this PR as this will be addressed in a different fix


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.13 to before v5.15.11",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=1b3e7ede1365a24db1b4fd837e58a595f52fa4ad",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=23311b92755ffa9087332d1bb8c71c0f6a10cc08"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "1b3e7ede1365a24db1b4fd837e58a595f52fa4ad",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "23311b92755ffa9087332d1bb8c71c0f6a10cc08",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "mptcp: fix deadlock in __mptcp_push_pending()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.15.11 by commit 23311b92755ffa9087332d1bb8c71c0f6a10cc08, it was introduced in version v5.13 by commit 1b3e7ede1365a24db1b4fd837e58a595f52fa4ad. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2021-1002749


Failed to collect dependencies at org.eclipse.mdht:org.eclipse.mdht.uml.hl7.vocab:jar:<IP_ADDRESS>805310501

I am suddenly unable to compile project due to below issue: is the site properly working?
I am using Version: 1.0.33
Could not resolve dependencies for project org.sitenv:referenceccdavalidator:jar:1.0.33: Failed to collect dependencies at org.eclipse.mdht:org.eclipse.mdht.uml.hl7.vocab:jar:<IP_ADDRESS>805310501: Failed to read artifact descriptor for org.eclipse.mdht:org.eclipse.mdht.uml.hl7.vocab:jar:<IP_ADDRESS>805310501: Could not transfer artifact org.eclipse.mdht:org.eclipse.mdht.uml.hl7.vocab:pom:<IP_ADDRESS>805310501 from/to java-net-public (https://maven.java.net/content/groups/public/): maven.java.net: Unknown host maven.java.net -> [Help 1]

Apologies. We lost access to our repository server and are in the process of spinning up a new one. The new one should be available by EOM at the latest.

If you need the jars in the meantime they can be obtained here:
https://github.com/mdht/mdht-models/releases

any update if that is fixed ?

Unfortunately no. I had really hoped it would be but we don't have a server we can use yet. For the latest pom I updated to use my local file path, you will need to adjust accordingly to build yourself until the new server is obtained/setup.

Update: This is fixed. I have spent a good deal of time setting up a new server/migrating the old servers/creating new builds/etc. You will find that the latest pom points to this data:  https://github.com/siteadmin/reference-ccda-validator/commit/5cadc2fb51321739a73b42030b48a6f21cc91f9b
However, this is still in dev. This should be merged to master and part of the 1.0.38 ref val release on 2018 12 31 (EOM).
Thanks,
Dan


TST: adding sdist and install tests to the 2.6 regression - closes #9878

closes #9878
Adds a test for packaging and installing pandas from a tarball, inside of the 2.6 regression.
After regular nosetests complete, cython is removed from the venv, pandas is packaged with cdist command, and the package is installed via pip. Limited nosetests run once installed.
The output of this test in the log is now 'folded' via http://blog.travis-ci.com/2013-05-22-improving-build-visibility-log-folds/ by putting install_test.sh into the 'after_script' section of the travis config.
This is a new PR with squashed commits to replace the original closed PR: https://github.com/pydata/pandas/pull/9922

@ajamian awesome thanks!


blob url?

Any mention here if files written can be accessed via a bloburl to pass to, say, a video tag?

+1

@feross

I think the API is too low-level to integrate something like built in blob url generation. I think this can easily be built with a custom ReadableStream that calls read() repeatedly. Then you can stream it into a Response and turn that into a blob url.

The streaming apis are pretty limited and move a TON of logic and complexity for detecting codecs and mime types out of browser code where it can rely on native tools and into js land where support is very limited and really easy to get wrong.
Trying to implement MediaSource and stream file data looks like it might be a path forward... until you realize that you'd need to know the exact codec of the file you're hoping to stream... and then set up all the data handling to handle seeking the stream and adjusting data fetching. And on top of that, there are many video files that are just trash for streaming like avi.
If we happen to have a video in StorageFoundation, it would be really nice to be able to create an object url for it so that the browser could read the data directly from the fs without involving heavy lifting from the webapp.

FWIW, I've implemented a chunk-store for webtorrent
https://github.com/ftreesmilo/storage-foundation-chunk-store
The last thing I really need is to get a blob url for the files so I can send them to a video element and let the browser do its thing.


fixes force-complete and aborted

There seems to be a bug on workqueue which doesn't set the workqueue elements to CancelRequested when request gets canceled (aborted and force-complete) which cause jobs to run.
However, I am not completely sure why this hasn't been found so long - it seems the bug was there all the time. (only case this doesn't get affected when cancelGraceTime is set to 0)

@amaltaro, Alan, please review. I am still running the test. So I will merge this if test is successful.

Ignore this for now. Beginning pylint and unit tests.

The code was weird, indeed. Patch looks good to me.
About elements_not_requested, the reason we load the document again is to make sure we know the latest rev and so to avoid conflicts, which does not happen in updateElements(), right?

Seangchan, I tested it in my VM and it seems to be working fine in the GQ, elements get updated to CancelRequested and then they are Canceled.
I'm now looking at the LQ, there seems to be an issue canceling work from the agent side (though I see work 'being' canceled in the WQ logs...). I'm investigating this, but feel free to merge this one and cut a new tag.

About elements_not_requested, the reason we load the document again is to make sure we know the latest rev and so to avoid conflicts, which does not happen in updateElements(), right?

Actually what happens is when cancel request is fired, it checks whether workqueue element is already in LQ or not. (GQ case)
0. It sets workqueue_inbox element to CancelRequested

If WE is NOT in LQ. it sets WE to Canceled in workqueue db.
If WE is in LQ, it sets WE in workqueue db to CancelRequested. - The reason doing this is it will replicate that WE in LQ inbox and that should trigger the canceling process from LQ and agent.
When Agent is done canceling the work it will set the LQ element status to Canceled and replicate to GQ.

The problem was it never sets the GQ element to CancelRequested when there is positive value for cancelGraceTime. I am not sure how this ever worked before.
There are 2 case it could work if the cancelGraceTime is set to 0 or less, Or cancelGraceTime is expired so it canceled the work eventually.
If there is problem on killing the jobs in WMAgent, there must be a bug in how LQ is canceled and triggers job killing. I will look at that today.  However that could be only agent side problem so I will merge this code.


Use Event API instead of Statsd

Currently this code uses https://github.com/DataDog/dogstatsd-csharp-client which is only a Statsd client. The problem is, this talks to the Statsd server (usually the Datadog agent on the same host) through UDP, which can lose messages and has datagram size issues.
I've created an issue on their repo to fix this by using the Event API endpoint instead of Statsd ( https://github.com/DataDog/dogstatsd-csharp-client/issues/25 ) but they don't seem to be very interested in maintaining their .NET library.
In the meantime, this affects this Serilog integration as well, so logging isn't really reliable with this sink.

The other (related) problem is that Datadog doesn't offer a batch API for events. Each log entry needs its own HTTP request :-/

I never treated Datadog as a consistent or reliable view of my logs, I would still use SEQ/Splunk to manage logs as those tools were far better for that purpose.
I found the best use of Datadog was to just send up Errors, so that we could drive Pagerduty/Statuspage alerting and this sink fulfilled that need perfectly.
Not having a batch upload is a bit of a concern for me but I would be happy to see a PR for this that sends up the events using the API, and perhaps see with Datadog to see if a batch upload is in the pipeline.

I'm already using Datadog with monitors linked to Pagerduty for alerting, and yes, in fact Datadog themselves recommended something like Splunk. However they've also recommended a Logstash (or Fluentd) integration, which is about logging and also sends events one at a time.
This seems like a contradiction to me, and the lack of a batch event endpoint is baffling to say the least, but that's an issue with Datadog and not with this library.
Regardless of all this, Serilog is a general-purpose logging library, and I'd expect all sinks to be essentially interchangeable for the purpose of writing logs. Silently dropping log entries means this sink is not suitable for general-purpose logging, so at least I'd put a big warning in the README.
Otherwise, other people will make the same mistake I did.

Closing this one as stale


Proposal:  Set default feerate to 100 ppm

My proposal is to set the default bitcoin.feerate=100 ppm ( which is 0.01% also) instead of the current bitcoin.feerate=1 ppm.
Recently we have celebrated a five anniversary of the Lightning Network whitepaper. It became from an idea to a mature and robust payment network, which is attracting now serious business.
Anyway, each time when someone asks me "If I would to invest Bitcoins into the Lightning Network, how much I could earn on it?"   usually reply "You'll just lose a small amount, but if you will do anything right, you loses will be minimal." But this situation has been change dramatically last months. In the new reality Bitcoin Mempool is much expensive even at the most inactive hours. During the hot mempool hours even a cooperative (which is controlled) close of the channel may hurt you by spending all incomes earned for the month. These losses multiplied by the growing fiat exchange rate and become a real pain, especially for the newcomers.
While it still very important to continue development of the balanced network and circular economy of LN, the idea is very simple. We should try at least to cover a onchgain tx costs.
Here is the analysis of the costs from the bottom and top views.

The minimal channel open transaction costs 154 sat. For the small routing channel size 1-2M it means that the fee rate at 100 ppm will cover the minimal (ideal) opening cost in the scenario of the unidirection payment flow  ( which is most common case in the network now)

For the big channel of 16,7M (which was the max chan size for a long time) it will be possible to collect 1600 - 2000 seats, which could be the regular cost of a channel opening.

From the top line we could say quite safely that having 0.1% of total fees still keeps LN very attractive to the customers, comparing to all other existing methods. Assuming the everage payment path is 5 hops, it is possible to collect 100 - 500 sats for each node in the path (depending of their role).

Any kind of network optimisation for establishing a bidirection flow in channels, also investment capital to wumboo channels should provide to node operators extra profit, above the on-chain costs and force-close risks.

I had several discussion with several routing node owners. Everyone was agreed about setting proper routing fees. If we check popular and really working nodes, most of them have much higher fees than 100 ppm. In the same time a lot of big nodes with the default fees stuck in deep assymetry and have a minimal forwards. The owners of these nodes just lost incentive to enforce optimisation because it wasting of satoshis without return.
So the changing defaults will not hurt the network, but only give a chance to a newcomers to be break even while professional node operators have a chance to be profitable. I believe it will increase the growth of Lightning Network.

Globally there are several economies where 100 grains of rice might cost 1 satoshis and at other geolocation´s You can not get any rice for 1 satoshis, then by having a enforced minimum forward rate would work against the networks global usability.
So there is the prospect of being able do volumes of forwards at whatever ppm You like when You the node op also create a market to serve, just lobbying for higher enforced default forwarding settings will not grow the market where You as a node op is paramount in its functioning and are also then responsible for creating the market i.e USERS to forward.
The network is not and will not be a single market but several markets with different use and so enforce minimum defaults for all would hinder the dynamics that the network are visioned to be.
A p2p micropayments network can not enable a "fee market" without a market of USERS that do use micropayments p2p.

Globally there are several economies where 100 grains of rice might cost 1 satoshis and at other geolocation´s You can not get any rice for 1 satoshis, then by having a enforced minimum forward rate would work against the networks global usability.
So there is the prospect of being able do volumes of forwards at whatever ppm You like when You the node op also create a market to serve, just lobbying for higher enforced default forwarding settings will not grow the market where You as a node op is paramount in its functioning and are also then responsible for creating the market i.e USERS to forward.
The network is not and will not be a single market but several markets with different use and so enforce minimum defaults for all would hinder the dynamics that the network are visioned to be.
A p2p micropayments network can not enable a "fee market" without a market of USERS that do use micropayments p2p.

I do agree that fees should generally be higher to make liquidity work more efficiently, but this is probably not the best to be dictated by the protocol and base implementation developers.
There has been a similar proposal more than a year ago<EMAIL_ADDRESS>to which would worth to read the answer of @Roasbeef which I presume would still apply<EMAIL_ADDRESS>This would not stop more specific higher layer implementations and node projects to use some higher eg. 100 ppm defaults, but that should be discussed in their individual repositories.

I do agree that fees should generally be higher to make liquidity work more efficiently, but this is probably not the best to be dictated by the protocol and base implementation developers.
There has been a similar proposal more than a year ago<EMAIL_ADDRESS>to which would worth to read the answer of @Roasbeef which I presume would still apply<EMAIL_ADDRESS>This would not stop more specific higher layer implementations and node projects to use some higher eg. 100 ppm defaults, but that should be discussed in their individual repositories.

We should try at least to cover a onchgain tx costs.

Totally, routing operators should modify their fees to do this themselves. Those that don't will end up losing money, but maybe that's OK if they mainly care about helping out the network. Many routing nodes just see it as a minor hobby and don't really care about min/maxing their potential revenue earnings.

We should try at least to cover a onchgain tx costs.

Totally, routing operators should modify their fees to do this themselves. Those that don't will end up losing money, but maybe that's OK if they mainly care about helping out the network. Many routing nodes just see it as a minor hobby and don't really care about min/maxing their potential revenue earnings.

Even if we raised default fees (which I don't think makes sense see that mailing list reply of mine) people can still run negative if they mismanage their nodes. It then follows that we won't magically make new routing nodes profitable by increasing their default fees, in order to make money you need to be committed to your node and continually examine several factors. Running a profitable routing node will never be as simple as a "set and forget".

Even if we raised default fees (which I don't think makes sense see that mailing list reply of mine) people can still run negative if they mismanage their nodes. It then follows that we won't magically make new routing nodes profitable by increasing their default fees, in order to make money you need to be committed to your node and continually examine several factors. Running a profitable routing node will never be as simple as a "set and forget".

I had several discussion with several routing node owners. Everyone was agreed about setting proper routing fees.

That's great, they can do so right now and observe if either they make more routing fee revenue, or their volume drops off causing them to make less than if they used w/e their prior fee setting was.

I had several discussion with several routing node owners. Everyone was agreed about setting proper routing fees.

That's great, they can do so right now and observe if either they make more routing fee revenue, or their volume drops off causing them to make less than if they used w/e their prior fee setting was.

I have an experience with aggressive rebalancing strategy. There are some of good performing channels which drain liquidity quite fast, so i set fee rate between 100 to 250 ppm for them. In the same time I have a donor channels providing me inbound capacity. Without rebelance it stuck in some position pretty fast.
I used to run rebelancing script which is acctually trying to rebalance circulary profiable channels with the X/10 fees using keysend. The success rate was around 1%, but it was enought to increase profit 5-10x times hire.
According to my understanding of network state it is a game called "catch another fool". If someone occasually opens a channel in the right direction and  set by mistake low fee, It coudbe drained in hours or even in minutes. That is my exeprience.
My current view to the  Network is a follwing Pyramid:

Some exchanges and big shops on the top, which have huge benefits for their main business from fast and cheap LN payments. They drain liquidity continuously from the whole network.

Some good operating nodes whic care about overal balance, channel rebalancing.
The nodes with a lot of funds are here also. Thouse node drains capacity form amateurs
and have a chance to cover their on-chain cost.

Amateur and enthusiasts' nodes. All of them have no expertise for fee management
and just supply liquidity up to the pyramid. They have no chance to cover opening and closing tx costs.

So the whole pyramid based on the idea of misunderstanding of the technology  and mismanaging of the enthusiasts' node.
I believe LN is mature enough to utilize a market forces and signal for it's growing. So it could be a transition from bootstrap to reasonable defaults

I have an experience with aggressive rebalancing strategy. There are some of good performing channels which drain liquidity quite fast, so i set fee rate between 100 to 250 ppm for them. In the same time I have a donor channels providing me inbound capacity. Without rebelance it stuck in some position pretty fast.
I used to run rebelancing script which is acctually trying to rebalance circulary profiable channels with the X/10 fees using keysend. The success rate was around 1%, but it was enought to increase profit 5-10x times hire.
According to my understanding of network state it is a game called "catch another fool". If someone occasually opens a channel in the right direction and  set by mistake low fee, It coudbe drained in hours or even in minutes. That is my exeprience.
My current view to the  Network is a follwing Pyramid:

Some exchanges and big shops on the top, which have huge benefits for their main business from fast and cheap LN payments. They drain liquidity continuously from the whole network.

Some good operating nodes whic care about overal balance, channel rebalancing.
The nodes with a lot of funds are here also. Thouse node drains capacity form amateurs
and have a chance to cover their on-chain cost.

Amateur and enthusiasts' nodes. All of them have no expertise for fee management
and just supply liquidity up to the pyramid. They have no chance to cover opening and closing tx costs.

So the whole pyramid based on the idea of misunderstanding of the technology  and mismanaging of the enthusiasts' node.
I believe LN is mature enough to utilize a market forces and signal for it's growing. So it could be a transition from bootstrap to reasonable defaults

Even if we raised default fees (which I don't think makes sense see that mailing list reply of mine) people can still run negative if they mismanage their nodes.

I completely agree about node mismanaging effect. Anyway we are still talking about different kind of losses, which are higher for mismanaged nodes and lower for good managed.  The only thing I want to enforce - to provide reasonable defaults which may help to cover very basic costs like channel opening TX. It may help us to move from highly negative zone to closer to zero negative.
It is normal if the developers still consider the network as hobbyist, but not for profit project. We will just continue repeating it to potential investors and new participants ;)

Even if we raised default fees (which I don't think makes sense see that mailing list reply of mine) people can still run negative if they mismanage their nodes.

I completely agree about node mismanaging effect. Anyway we are still talking about different kind of losses, which are higher for mismanaged nodes and lower for good managed.  The only thing I want to enforce - to provide reasonable defaults which may help to cover very basic costs like channel opening TX. It may help us to move from highly negative zone to closer to zero negative.
It is normal if the developers still consider the network as hobbyist, but not for profit project. We will just continue repeating it to potential investors and new participants ;)

I believe LN is mature enough to utilize a market forces and signal for it's growing

Indeed, that can already be done by having users update their routing fees based on the view of the market and also the various expenses that make up their cost basis.

The only thing I want to enforce - to provide reasonable defaults which may help to cover very basic costs like channel opening TX. It may help us to move from highly negative zone to closer to zero negative.

There's no magic number for this. Let's say I own my hardware and have had it sitting around for years unused, in essence, I don't need to factor this into my expenses for each month for my node. On the other hand someone that's using a VPS needs to pay for CPU, disk, bandwidth, etc. There's simply no magic number that works for all cases, therefore, users need to compute their own costs and set them accordingly.

It is normal if the developers still consider the network as hobbyist, but not for profit project.

This depends on the individual. If you want to take a node seriously and earn a profit, then you need to be actively adjusting your fees and watching your chain fees to ensure that you actually make a profit. Setting the default fees to a new magic number doesn't change the current chain conditions, nor the tendency of users to not take their chain fee costs into account when attempting to bring up and maintain a new node.

@Roasbeef  Thank you for the clarification! I close this issue.


enum types can't be inserted

Reproduce:
dolt sql
test> create table test (a int primary key, t enum('a','b','c'));
test> insert into test values (1, 'a');
value "a" is not valid for this Enum
test> insert into test values (1, 'b');
value "b" is not valid for this Enum

I can't replicate this at all. Is this from the tip of master? This even looks similar to the ENUM test under types.bat, which passed. Here is my console:
C:\Users\Daylon\Documents\ztest4>dolt init
Successfully initialized dolt data repository.

C:\Users\Daylon\Documents\ztest4>dolt sql
# Welcome to the DoltSQL shell.
# Statements must be terminated with ';'.
# "exit" or "quit" (or Ctrl-D) to exit.
ztest4> create table test (a int primary key, t enum('a','b','c'));
ztest4> insert into test values (1, 'a');
Query OK, 1 row affected
ztest4> insert into test values (1, 'b');
duplicate primary key given: ((7493,1))
ztest4> select * from test;
+---+---+
| a | t |
+---+---+
| 1 | a |
+---+---+

I also tried the 64-bit Windows binary under our Dolt 0.16.0 release, and I got the same as above.

I wasn't up to date on master. Disregard!

Definitely still happens on master. Something weird is going on. It looks like the enum definition relies on quoted values.
test> create table test (a int primary key, t enum('a','b','c'));
test> insert into test values (1, 'b');
value "b" is not valid for this Enum
test> desc test;
+-------+-------------------------+------+-----+---------+-------+
| Field | Type                    | Null | Key | Default | Extra |
+-------+-------------------------+------+-----+---------+-------+
| a     | INT                     | NO   | PRI |         |       |
| t     | ENUM(''a'',''b'',''c'') | YES  |     |         |       |
+-------+-------------------------+------+-----+---------+-------+
test> insert into test values (1, "'b'");
Query OK, 1 row affected

Bats tests fail for me, not just for this type. I suspect an override of vitess. Testing now

Caused by an out of date vitess. Disregard again!

Darn it Zach lol


Timer window not showing if taskbar is positioned on the left side of screen.

If taskbar is located on the left, instead of default bottom, timer window is either not showing or positioned incorrectly (see screenshot).

If positioned on the right of the screen, the timer window does not appear at all. Using beta 4

Well, even if I reposition the toolbar on the bottom (with tomato running) the timer window does not appear. Win 10 64 bits


Resteasy 1171 add hooks for http handlers

I added a hook to insert http related handlers between the Netty and the RestEasy ones.
I also refactored the start method to remove code duplication and made it easier to read by extracting some code into separate methods.
Please note that setting the channelOptions and the childChannelOptions was previously only being executed for Https requests. I believe this is a bug and I have moved it so it executes for Http and Https requests alike.

@patriot1burke would it be possible to get this merged if you think it is appropriate to do so?


GetFriendList

Any chance you could include a new parameter for the GetFriendList method so that we can skip the GetPlayerSummaries pass through? Running GetPlayerSummaries for every friend is quite slow and I'd just like to get a list of steamids not each friends profile.

This could be added.  If you want it soon (i wont have time to do it anytime soon), you could submit a PR and we'd be happy to merge it.

Fixed by #85

Included in v2.0.15.


Please add 17.09 AMIs

Issue description
The 17.09 release has been tagged but the AMIs have not yet been updated. Please update ec2-amis.nix with AMIs.
Steps to reproduce
Technical details

System: (NixOS: nixos-version, Ubuntu/Fedora: lsb_release -a, ...)
Nix version: (run nix-env --version)
Nixpkgs version: (run nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion)
Sandboxing enabled: (run grep build-use-sandbox /etc/nix/nix.conf)

They will probably be added when the official announcement is out and the docs updated.

Thank you @edolstra!