Polygon with more holes

Hi, I'm trying to append a polygon with more holes. With one hole is everything fine, but with two, it renderes badly. Is it an issue or am I doing something wrong?
http://jsbin.com/fuleterere/2/
Thanks a lot!

Your code is correct! This is a huge oversight in testing and, I believe, a regression. Here is your code working with the latest test build:
http://jsbin.com/hicapi/2/edit
This will be fixed in rc1 which, even though we just release b2, isn't far away.
Thank you for testing!

Hi Ryan, thanks a lot, it works now as I expected.

Great to hear!


Enhancement Request: Introduce Default Theme Option in quartz.config.ts for Seamless Website Theming

Is your feature request related to a problem? Please describe.
Currently, there is no straightforward way to set a default theme for the website in the Quartz application. It becomes challenging to manage and apply consistent themes, especially when dealing with the theme of custom components.
Describe the solution you'd like
I propose adding an option to quartz.config.ts that allows site owners to specify a default theme for the website. This new configuration option would also serve the purpose of setting the default theme for custom components, providing more flexibility in theme management.
Additional context

When the theme isn't specified in the local storage, the custom component's theme defaults to dark.
A theme mismatch will occur if the user's machine theme is light.

How are you reading the theme?

see what darkmode does here: https://github.com/jackyzha0/quartz/blob/b22bcd17b4301c6ef398124eec11f6dff0c2d37d/quartz/components/scripts/darkmode.inline.ts#L1-L3

Nice, problem solved, thanks!


Check is incorrect for index

based on recent change in Ecto SQL 3.9.x , it seems that it s not working correctly anymore this check. They added an advisory pg lock. per  https://hexdocs.pm/ecto_sql/Ecto.Migration.html#index/3-adding-dropping-indexes-concurrently
I tried creating a migration that has a config of advisory lock but the check complained incorrectly until I added the following
@disable_migration_lock true
to my migration. This is wrong because the point of the advisory lock is to avoid removing all completely the lock?
  use Ecto.Migration

  @disable_ddl_transaction true

  def change do
    create table(:mytable) do
      add(:some_field, :uuid, null: false)

      timestamps()
    end

    create(unique_index(:mytable, [:some_field], concurrently: true))
end

I get an a credo error with "Index concurrently without disable ddl transaction"

so then I have to fix it by added @disable_migration_lock true but based on the way it s supposed to work, I should not have to turn it off at all

I would be happy to help but not sure how this works

Not sure if I'm encountering the same exact issue as @epinault , but shouldn't this alone pass the excellent migrations checks?
defmodule MyMigration do
  use Ecto.Migration

  def change do
    create table(:mytable) do
      add(:some_field, :uuid, null: false)

      timestamps()
    end

    create(unique_index(:mytable, [:some_field]))
end

Why do I need to concurrently create an index on a newly created table? The table is new, and therefore doesn't contain any data, so creating the index should be fast.


Support CSRF check using CsrfCookie

Since CsrfHeader exists, it would be interesting to have the possibility to check the cookie. For JavaScript SPA, it would be interesting to avoid cookies manipulation.
The code would look like this:
/// Validates a json endpoint that has a CSRF token.
#[post("/login")]
async fn login(
    _: Csrf<CsrfCookie>,
    json: Json<Request>,
) -> impl Responder {
    // ...
}

This way, no need to change headers or add the token inside the JSON object while making requests. (i.e. with fetch API)

Hey, I don't think that works. This crate implements CSRF protection via the Double-submit pattern. Only using cookies is not sufficient for CSRF protection.

Ok, then I will try to look how to submit the token from my app using headers (which use NextJS).
Thank you for your quick response.


Create AD stream characteristic issue for stream packaging teams

As a digital analyst I want to understand how much video content provided with audio description is consumed so that I can report and discuss to/with our stakeholders.
Hints
See related JIRA issue.
Acceptance criteria

The need has been clarified with stream packaging teams and dedicated issues have been created in their backlog if needed.

Tasks

[x] Create an issue for the SRF packaging team.
[ ] Create an issue for RSI packaging team.

Issue created for SRF: https://srgssr-ch.atlassian.net/browse/AIS-25603


DEGIRO: stock dividend interpreted as SELL

When using the DEGIRO conversion STOCK DIVIDEND is marked as a SELL:
14-09-2023,08:49,14-09-2023,STOCK,NLID,STOCK DIVIDEND: Koop 999 @ 0 EUR,,EUR,0.00,EUR,9999.99,

Results in:
    {
      "accountId": null,
      "comment": null,
      "fee": 0,
      "quantity": 999,
      "type": "SELL",
      "unitPrice": 0,
      "currency": "EUR",
      "dataSource": "YAHOO",
      "date": "2023-09-14T08:49:00.000Z",
      "symbol": "STOCK"
    }

This should be marked as 'BUY'.

Thanks for reporting this. Did you run this with the default DEGIRO converter (v3)?

I used the version 2 as version 3 gives me other problems: https://github.com/dickwolff/Export-To-Ghostfolio/issues/127

What stock should this apply to then? STOCK of course isn't a symbol, and NLID also does not yield a result on Yahoo Finance.

@dickwolff It's Prosus:
14-09-2023,08:49,14-09-2023,PROSUS NV,NL0013654783,STOCK DIVIDEND: Koop 999 @ 0 EUR,,EUR,0.00,EUR,9999.99,


On the "Request Timeline Page' "the back navigation arrow is not working".

Describe the bug
On the "Request Timeline Page' "the back navigation arrow is not working".
To Reproduce**
Steps to reproduce the behavior:

Go to 'https://reach4help-staging-web-2. client.firebaseapp.com/timeline/ryjNLSLAGB2fqPZHV8uM...'
Click on 'back' arrow.
The back navigation arrow is not working
It brings back to the same page.

Screenshot:

Expected behavior:
The back navigation arrow should be working.
Desktop (please complete the following information):
OS: [Windows]
Browser chrome
Version [ 83.0.4103.97 (Official Build) (64-bit]
Additional context
N/A

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

@PhilArsHermit added the same issue in #705:

Describe the bug
After a request is done, the Person in Need is unable to leave the Request Timeline screen, even after he completed the review.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://reach4help-staging-web-client.firebaseapp.com/' with 2 users
Create a request, and complete it
The Volunteer then review the user, and automatically leave the Timeline screen and land in the map section
Have the Person in Need reviews
We see the loading screen, but he lands back into the Timeline page.  If he tries to go back (by pressing the arrow), we briefly see the loading symbol, but it just goes back to the Timeline page.

Expected behaviour
The Person in Need should automatically leave the Timeline page after reviewing the Volunteer, similar to the flow of the Volunteer.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: W10 Pro
Browser Chrome
Version 83.0.4103.97

ZenHub Information
This information is updated automatically. To modify it, please use ZenHub.

Fixed and deployed in production, closing.


update CHANGELOG more frequently

On CHANGELOG.md the last release mentioned is version 0.2.0 from March 2022, but on PyPI I see we have a few more recent releases:

0.3.5 (Jul 1, 2022)
0.3.4 (Jul 1, 2022)
0.3.3 (Jul 1, 2022)
0.3.2 (Jun 27, 2022)
0.3.1 (Jun 24, 2022)
0.3.0 (Jun 23, 2022)

We should list all releases on the CHANGELOG. And ideally we should also detail what are the most important things that happened in each of them.
I'll update this now.

I shouldn't have said "I'll update this now." :-P
Anyway... now we have a few more releases also not listed on CHANGELOG.md:

0.3.9 (Oct 23, 2022)
0.3.8 (Oct 10, 2022)
0.3.7 (Oct 10, 2022)
0.3.6 (Oct 7, 2022)

I'll update this now. (really!)

As promised, I just "did it now" 3 days ago ;-)


[1.21] Can't put Addons in machines

Industrial Foregoing Version: 3.6.15
Titanium Version: Sorry I'm noob and don't know that :(
Crashlog If Applicable (Upload to pastebin/gist):
I tried with mob crusher and mob slaughter factory and can't put any range/speed addons into the addon-slots. Tried it with different Tiers too. In case that info helps I'm playing minecraft version 1.21.1 with the modpack craftoria 1.5.0

Did you cheat the items in? You need to craft them or get them from the creative menu

Yes I did. Didn't think that would matter. Thank you very much :)


Why does selectolax ship Cython as install dependency?

Hi there,
Thanks for creating selectolax. Is there any particular reason that you have cython as install dependency?
https://github.com/rushter/selectolax/blob/422b3ef1c98f58f3caed1962ed5254fc44572727/setup.py#L157

To compile old version of selectolax on a newer versions of Python. Some people pin their version of selectolax.
Every new major version of Python usually is not compatible with old C extensions.

Hi,
Thanks for quick response.

To compile old version of selectolax

Cant we have a minimum and maximum supported python version for a given version of selectolax?
Dependencies like frozenlist has a minimum python requirement

Ok, I will think about it

Related issues cause by third party library https://github.com/rushter/selectolax/issues/38#issuecomment-861529400

Thanks for listening to my advice


Can we have timestamp+incrementing mode in the source connect

All the other jdbc source connectors support the timestamp+incrementing mode, can we have the same feature in the SAP HANA source connect?

Does this feature exists?

Does this feature exists?

No, JDBC connector supports SAP and it has that feature,  so you can use that connector.


Updated documentation

Changes made

links are now in an unordered list
fixed any markdown violations

Happy to hear and discuss any feedback

Always a pleasure ❤


How to add checkpoint models?

How can I load local models/extensions easily like webuiautomatic1111, the workflow is great, but when I start and run, I can use very little, is there any tutorial, thank you！

You can currently load models from Hugging Face. For example, if you want to load Dreamshaper, you can use Lykon/DreamShaper when calling dream.
If there is a model that's available on Civit, for example, but not on Hugging Face, you should first download and upload it to Hugging Face. You can then pull it from there.


port interpretation draft

Closing due to inactivity. Please re-open if you can spare time to get this functionality in. That would be awesome!


[1.20.1] WTHIT mod compatibility issue

Behaviour
Looking down can cause WTHIT to display like this...
Screenshots

Environment

Minecraft Version: 1.20.1
Installed Mods: WTHIT & 99+ mods

1: MTR 1.20 is not Recommended
2: That us Likely mtr:seat


Don't panic if driverRows.Next is called after Close

Previously this would panic with an index out of range error. Which was misleading as the indexing itself wasn't the problem. The problem was that fetch returns a nil error if the error channel was closed, which led the Next function to believe there was more data ready to be processed, but this was not the case.
The error channel is only closed if Close is called on driverRows or driverStmt, so this panic was caused by a premature closing of the rows or statement, but that hard to tell from the panic message.
This commit changes removes the panic and instead returns an io.EOF error if we detect that fetch was called on a closed statement or rows.
Closes #65.

Done, though you might want to squash the commits. As for the CLI my company, Slight, should have signed it. But I'll ask internally what the status of that is.

Done, though you might want to squash the commits. As for the CLI my company, Slight, should have signed it. But I'll ask internally what the status of that is.

Please squash commits yourself. The PR is small so it's easy to track requested changes.

Done.

The CLAs gets processed every two weeks or so. I hope you don't mind if this PR will stay open for a bit. Thanks a lot for the contribution!

No problem.

Alright, CLA signed and approved.

@clabot check

@cla-bot check

@losipiuk PTAL, it should be ready to be merged.


Platform.cs -> Registry is not supported by mac

Hi , In Platform.cs static constructor , Registry class is used to find .net framework version if current runtime is not a mono runtime . In mac and in .net core application , this code throws exception when we want to create a beneficiary .
Could you add a code block to handle .net core runtime in this class .

Here is a .NET Standard version https://github.com/tluyben/currencycloud-net

Thank you for your help and input. We will look at this change you have made.

Take a look at my PR Support .NET Standard 2.0, should now support both.


Code quality improvement needed in Analytics frontend code.

Currently, the codebase for the Analytics frontend is having redundant code and repetitive calculations in many places.
The Analytics codebase needs to be refactored -

Remove the redundant code.
Provide comments for code blocks.
Repetitive calculations need to be removed.

One Example -
In this file https://github.com/litmuschaos/litmus/blob/9f2b475ae54a5cf2286cdc5643da65fb9aa08520/litmus-portal/frontend/src/pages/AnalyticsPage/index.tsx#L145
From line 145-170
The 3 if-else conditions can be refactored with 1 if-else condition like given below -
ExperimentTestResult = 0;
if (chaosData.experimentVerdict === "Pass") {
  ExperimentTestResult = weightage.weightage * parseInt(chaosData.probeSuccessPercentage, 10)) / 100;
  totalExperimentsPassed += 1;
}
experimentTestResultsArray.push(ExperimentTestResult);
experimentTestResultsArrayPerWorkflowRun.push(ExperimentTestResult);
weightsSum += weightage.weightage;
isValid = true;

In this file - https://github.com/litmuschaos/litmus/blob/master/litmus-portal/frontend/src/views/AnalyticsDashboard/LitmusDashboard/WorkflowComparisonTable/index.tsx
We are calculating this below code block twice
resilience_score: experimentTestResultsArrayPerWorkflowRun.length
                  ? (experimentTestResultsArrayPerWorkflowRun.reduce(
                      (a, b) => a + b,
                      0
                    ) /
                      weightsSum) *
                    100
                  : 0,

                value: experimentTestResultsArrayPerWorkflowRun.length
                  ? (experimentTestResultsArrayPerWorkflowRun.reduce(
                      (a, b) => a + b,
                      0
                    ) /
                      weightsSum) *
                    100
                  : 0,

In line 317 -  https://github.com/litmuschaos/litmus/blob/9f2b475ae54a5cf2286cdc5643da65fb9aa08520/litmus-portal/frontend/src/views/AnalyticsDashboard/LitmusDashboard/WorkflowComparisonTable/index.tsx#L317
and 329 - https://github.com/litmuschaos/litmus/blob/9f2b475ae54a5cf2286cdc5643da65fb9aa08520/litmus-portal/frontend/src/views/AnalyticsDashboard/LitmusDashboard/WorkflowComparisonTable/index.tsx#L329
There are many places, where such improvements can be done.

Thanks @Jonsy13 for creating the issue, we will be tracking it and fixing it with beta releases on a feature branch till GA as the files mentioned are to be deprecated and refactored / redesigned.


Upgrading ingest-attachment dependencies

Signed-off-by: Kartik Ganesh<EMAIL_ADDRESS>Description
Multiple dependencies under ingest-attachment have been upgraded:

Tika libraries upgraded from 1.24.1 to 2.3.0

The major version upgrade requires an explicit dependency on tika-parsers-standard-package to import the parser implementations, and an update to the namespace of RTFParser.
Also, LanguageIdentifier has been deprecated and replaced by LanguageDetector.
This upgrade also required an update of Apache Commons-IO from 2.7 to 2.11.0, and PDFBox to 2.0.25 as per Tika release notes

xmlbeans libraries updated from 3.0.1 to 5.0.2
xmlbeans is now a subproject of Apache POI, so the POI libraries were upgraded from 4.1.2 to 5.2.2
With POI 5.x the ooxml-schemas library has been moved to ooxml-lite / ooxml-full. Since ooxml-schemas no longer exists, the LICENSE and NOTICE files in the licenses/ directory have been removed.

Issues Resolved
Once this is merged, the dependabot PR #2138 can be closed
Check List

[ ] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

start gradle check

start gradle check

Test failures look legit.

org.opensearch.ingest.attachment.AttachmentProcessorTests > testEnglishTextDocument FAILED
    java.lang.IllegalStateException: No language detectors available
        at __randomizedtesting.SeedInfo.seed([346CD47C4FE8213C:CE265966D8557F82]:0)
        at org.apache.tika.language.detect.LanguageDetector.getDefaultLanguageDetector(LanguageDetector.java:67)
        at org.opensearch.ingest.attachment.AttachmentProcessor.execute(AttachmentProcessor.java:138)
        at org.opensearch.ingest.attachment.AttachmentProcessorTests.parseDocument(AttachmentProcessorTests.java:333)
        at org.opensearch.ingest.attachment.AttachmentProcessorTests.parseDocument(AttachmentProcessorTests.java:323)
        at org.opensearch.ingest.attachment.AttachmentProcessorTests.testEnglishTextDocument(AttachmentProcessorTests.java:85)```

Test failures look legit.

Yup, need to figure out how to configure the language detectors. Flipping to draft PR.

More failures around non-determinism of language recognition - this time in IngestAttachmentClientYamlTestSuiteIT. Repro commands:
./gradlew ':plugins:ingest-attachment:yamlRestTest' --tests "org.opensearch.ingest.attachment.IngestAttachmentClientYamlTestSuiteIT" -Dtests.method="test {yaml=ingest_attachment/30_files_supported/Test ingest attachment processor with .doc file}" -Dtests.seed=1E07D222039A022B -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=es-ES -Dtests.timezone=CNT -Druntime.java=17

./gradlew ':plugins:ingest-attachment:yamlRestTest' --tests "org.opensearch.ingest.attachment.IngestAttachmentClientYamlTestSuiteIT" -Dtests.method="test {yaml=ingest_attachment/30_files_supported/Test ingest attachment processor with .docx file}" -Dtests.seed=1E07D222039A022B -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=es-ES -Dtests.timezone=CNT -Druntime.java=17

Looks like the failure are limited to doc/docx file processing, and the assertion failure is the same in all cases:
expected String [pl] but was String [en]

This is an error with the test case, and the new output is more accurate.
The two files are represented as Base64 encoded strings in the yml test file. Decoding them and opening as Word documents shows the contents to be:
Test opensearch

Previously, language detection was incorrectly identifying this as Polish (pl) - likely due to the phrase being so short. With the upgraded libraries, the result has changed to en which is an accurate value

@kartg should we backport this to 2.x?

@owaiskazi19 Yes, looks like it is blocking this backport.
I'll dig into @reta 's comment above and make sure any fixes for that get backported too.


[WIP] - Added support for the sandbox endpoint

I added support the existing library for the sandbox environment that is provided by Investec, for my development purposes I thought this is crucial.

#6

Thanks for this @shailen-naidoo, I appreciate the effort!
I'm going to close this PR in favour of #8.

We can make the baseUrl more configurable by allowing the consumer to pass it in as a value when creating the Client
We can make things a bit more readable and maintainable by instantiating an API client that uses the baseUrl, so that the callers do not need to pass the URL for every call.

This PR also lacks documentation, and introduce dist/ and .nvmrc to git (though I'm guessing this was for testing purposes!)

Hi @FrikkieSnyman I added /dist to the commit history as I ended up using the library directly or my version of the lib in my project directly until you support the feature request. I always add a .nvmrc file to all Node project to fix the Node version to prevent breaking changes from occurring.


[Backport release-24.05] librewolf-unwrapped: 129.0-1 -> 129.0.1-1

Description of changes
Combined backport of #336304 and #335892
This qualifies for backport because #335892 is a version update, and #336304 is a necessary fix for the build.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

cc @mweinelt


Top and bottom on mobile Logseq looks different

Sorry, I'm not sure is it theme issue or Logseq issue itself.
The system top an bottom panel has another color scheme on mobile

Logseq 0.9.4
Android 12
Samsung A41.
My custom.css
@import url("https://cdn.jsdelivr.net/gh/bad3r/logseq-nord-theme@latest/custom.min.css");

.recent {
    display: none;
  }

hmm this might be an android only issue

Sorry, I'm not sure is it theme issue or Logseq issue itself.
The system top an bottom panel has another color scheme on mobile
Logseq 0.9.4 Android 12 Samsung A41.
My custom.css
@import url("https://cdn.jsdelivr.net/gh/bad3r/logseq-nord-theme@latest/custom.min.css");

.recent {
    display: none;
  }

HI! Looks awesome on mobile phone!!!
how did you do that? If you look at the code, you imported a link, but what kind of knowledge is not enough to understand (Can you do the same on other topics? Please explain:)

Sorry, I'm not sure is it theme issue or Logseq issue itself.
The system top an bottom panel has another color scheme on mobile

Logseq 0.9.4
Android 12
Samsung A41.
My custom.css
@import url("https://cdn.jsdelivr.net/gh/bad3r/logseq-nord-theme@latest/custom.min.css");

.recent {
    display: none;
  }

one mines, white line on top(
Android 13

I think this is a Logseq upstream issue which has been fixed. Feel free to reopen if otherwise.


creat ledger timeout and thread BookKeeperClientWorker in stuck

Describe the bug
we found many timeout logs when creating producer or sending message.like this,we creat a new topic and then build a producer to send message:
java.util.concurrent.CompletionException: org.apache.pulsar.common.util.FutureUtil$LowOverheadTimeoutException: Failed to load topic within timeout
        at java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source) ~[?:?]
        at java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source) ~[?:?]
        at java.util.concurrent.CompletableFuture$UniApply.tryFire(Unknown Source) ~[?:?]
        at java.util.concurrent.CompletableFuture.postComplete(Unknown Source) ~[?:?]
        at java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source) ~[?:?]

we check the stack trace of create ledger and found that when creating ledger complete it can't get the thread BookKeeperClientWorker  to do callback's work

we dump tread stack, BookKeeperClientWorker-OrderedExecutor-0-0 is always BLOCKED
"BookKeeperClientScheduler-OrderedScheduler-0-0" #26 prio=5 os_prio=0 cpu=61864.97ms elapsed=268089.10s tid=0x00007f88598ef800 nid=0x17b in Object.wait()  [0x00007f87fa5e1000]
   java.lang.Thread.State: WAITING (on object monitor)
        at<EMAIL_ADDRESS>Method)
        - waiting on <no object reference available>
        at<EMAIL_ADDRESS>Source)
        at io.netty.util.concurrent.DefaultPromise.awaitUninterruptibly(DefaultPromise.java:275)
        - waiting to re-lock in wait() <0x00000000cb13f9c0> (a io.netty.channel.DefaultChannelPromise)
        at io.netty.channel.DefaultChannelPromise.awaitUninterruptibly(DefaultChannelPromise.java:137)
        at io.netty.channel.DefaultChannelPromise.awaitUninterruptibly(DefaultChannelPromise.java:30)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.closeInternal(PerChannelBookieClient.java:1081)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.disconnect(PerChannelBookieClient.java:1034)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.disconnect(PerChannelBookieClient.java:1029)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.failTLS(PerChannelBookieClient.java:2555)
        - locked <0x00000000b8293218> (a org.apache.bookkeeper.proto.PerChannelBookieClient)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.access$2900(PerChannelBookieClient.java:154)
        at org.apache.bookkeeper.proto.PerChannelBookieClient$StartTLSCompletion.errorOut(PerChannelBookieClient.java:1961)
        at org.apache.bookkeeper.proto.PerChannelBookieClient$CompletionValue.timeout(PerChannelBookieClient.java:1614)
        at org.apache.bookkeeper.proto.PerChannelBookieClient$CompletionValue.maybeTimeout(PerChannelBookieClient.java:1606)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.lambda$static$3(PerChannelBookieClient.java:1011)
        at org.apache.bookkeeper.proto.PerChannelBookieClient$$Lambda$596/0x00000001006f8440.test(Unknown Source)
        at org.apache.bookkeeper.util.collections.ConcurrentOpenHashMap$Section.removeIf(ConcurrentOpenHashMap.java:411)
        at org.apache.bookkeeper.util.collections.ConcurrentOpenHashMap.removeIf(ConcurrentOpenHashMap.java:172)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.checkTimeoutOnPendingOperations(PerChannelBookieClient.java:1015)
        at org.apache.bookkeeper.proto.DefaultPerChannelBookieClientPool.checkTimeoutOnPendingOperations(DefaultPerChannelBookieClientPool.java:132)
        at org.apache.bookkeeper.proto.BookieClientImpl.monitorPendingOperations(BookieClientImpl.java:572)
        at org.apache.bookkeeper.proto.BookieClientImpl.lambda$new$0(BookieClientImpl.java:131)
        at org.apache.bookkeeper.proto.BookieClientImpl$$Lambda$163/0x000000010038e840.run(Unknown Source)
        at org.apache.bookkeeper.util.SafeRunnable$1.safeRun(SafeRunnable.java:43)
        at org.apache.bookkeeper.common.util.SafeRunnable.run(SafeRunnable.java:36)
        at com.google.common.util.concurrent.MoreExecutors$ScheduledListeningDecorator$NeverSuccessfulListenableFutureTask.run(MoreExecutors.java:705)
        at<EMAIL_ADDRESS>Source)
        at<EMAIL_ADDRESS>Source)
        at<EMAIL_ADDRESS>Source)
        at<EMAIL_ADDRESS>Source)
        at<EMAIL_ADDRESS>Source)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at<EMAIL_ADDRESS>Source)

"BookKeeperClientWorker-OrderedExecutor-0-0" #27 prio=5 os_prio=0 cpu=616668.69ms elapsed=268089.10s tid=0x00007f88598f3000 nid=0x17c waiting for monitor entry  [0x00007f87fa4e0000]
   java.lang.Thread.State: BLOCKED (on object monitor)
        at org.apache.bookkeeper.proto.PerChannelBookieClient.connectIfNeededAndDoOp(PerChannelBookieClient.java:631)
        - waiting to lock <0x00000000b8293218> (a org.apache.bookkeeper.proto.PerChannelBookieClient)
        at org.apache.bookkeeper.proto.DefaultPerChannelBookieClientPool.obtain(DefaultPerChannelBookieClientPool.java:121)
        at org.apache.bookkeeper.proto.DefaultPerChannelBookieClientPool.obtain(DefaultPerChannelBookieClientPool.java:116)
        at org.apache.bookkeeper.proto.BookieClientImpl.addEntry(BookieClientImpl.java:329)
        at org.apache.bookkeeper.client.PendingAddOp.sendWriteRequest(PendingAddOp.java:152)
        at org.apache.bookkeeper.client.PendingAddOp.safeRun(PendingAddOp.java:278)
        at org.apache.bookkeeper.common.util.SafeRunnable.run(SafeRunnable.java:36)
        at<EMAIL_ADDRESS>Source)
        at<EMAIL_ADDRESS>Source)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at<EMAIL_ADDRESS>Source)

To Reproduce
i don't known how to reproduce
Additional context
version：2.9.1

Since upgrading from 2.7.1 to 2.9.1 we also have been hitting issues where our producers will begin failing. Typically we'll have one broker that isn't responding to requests and restarting it will fix the issue. From looking at the broker logs we see a similar error to what is describe in this issue:
2022-02-18T17:35:06,772+0000 [pulsar-io-4-7] WARN  org.apache.pulsar.broker.service.ServerCnx - [/<IP_ADDRESS>:51632][persistent://prod/voltron-general/871_2b2d84be150dcf9c_MAID_DELETE_6333758_4bb66664126194f7-partition-0][voltron] Failed  to create consumer: consumerId=0, Failed to load topic within timeout                                                                                java.util.concurrent.CompletionException: org.apache.pulsar.common.util.FutureUtil$LowOverheadTimeoutException: Failed to load topic within timeout                                                                                ...                                                                                at org.apache.pulsar.common.util.FutureUtil.lambda$addTimeoutHandling$1(FutureUtil.java:141) ~[org.apache.pulsar-pulsar-common-2.9.1.jar:2.9.1]                                                                                at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98) [io.netty-netty-common-4.1.72.Final.jar:4.1.72.Final]                                                                                ...                                                                                Caused by: org.apache.pulsar.common.util.FutureUtil$LowOverheadTimeoutException: Failed to load topic within timeout
This seems to be happening randomly every 4-7 hours since we upgraded. We typically write to a lot of topics in a given namespace. We'll try to capture thread state next time it happens.

@fu-turer thanks for opening this issue and providing the thread dumps. It looks like the blocked thread is in the bookkeeper client. Based on your thread stack, I'm assuming you're running with TLS enabled, is that correct? Do you see a log line with TLS failure on in it? It should end with a number, and that number is a bk error code.

@fu-turer is there anything in the logs related to not being able to connect to bookies because of e.g. a TLS issue? Or attempt to use TLS 1.3? see https://github.com/apache/bookkeeper/issues/2711
@fistan684 are you rotating TLS certificates every few hours? any chance that certificates occasionally expire before new ones deployed on the bookie nodes?

@dlg99 i use TLSv1.2.
@michaeljmarshall there are 3 bookies, 2 brokers in my test environment. before problem happen, 3 bookies are all down, after all bookies recover, one broker's thead in stuck, and the anther one is normal

before problem happen, 3 bookies are all down

this would explain failTLS in the stack :) Why are they all going down?
will the thread unblock after some time (some timeouts can be in the range of 30sec or so by default)
did the bookie IP address change after the bookie came back up? JVM caches dns lookups etc.
bookie client (pulsar broker side) should log what it is doing, trying to connect/failing, certificate errors etc.
I recommend checking the log (at least to make sure that bookie client logs there). With that please attach a full log from the client side and from the bookies and a full thread dump.


RNGoogleSignInButton.h - GoogleSignIn/GoogleSignIn.h file not found

Hi!
I try to migrate my project from v1.0.0-rc7 by following all the steps for iOS (without cocoapod).
I unlink the lib, upgrade to latest version (1.0.2), re-link the lib, use the latest sdk, etc.
But I've got an error at build
Lexical or Preprocessor Issue Group

/RNGoogleSignin/RNGoogleSignInButton.h:1:9: 'GoogleSignIn/GoogleSignIn.h' file not found

/path-to/my-project/node_modules/react-native-google-signin/ios/RNGoogleSignin/RNGoogleSignInButton.m:2:9:
In file included from
/path-to/my-project/node_modules/react-native-google-signin/ios/RNGoogleSignin/RNGoogleSignInButton.m:2:

All previous issues I found about it seems to be related to a missing path in Header Search Paths in Build Settings, but I've got the correct one $(SRCROOT)/../node_modules/react-native-google-signin/ios/RNGoogleSignin (non-recursive).
And others issues doesn't seems to be related to the RNGoogleSignInButton
In Build Settings I've got the good path in Framework Search Paths.
In Build Phases I've got RNLibGoogleSignin.a, GoogleSignIn.framework, GoogleSignInDependencies.framework in Link Binary With Libraries and GoogleSignIn.bundle in Copy Bundle Resources.
In AppDelegate.m I try the old #import "RNGoogleSignin.h" and the new #import <RNGoogleSignin/RNGoogleSignin.h> but this doesn't change the result.
I don't think I can provide a reproduction of a migration. Based on the issue can you suggest a potential issue ? Did you need more informations on a specific part ?
Thank's
Environment

react-native : 0.57.8
react-native-google-signin : 1.0.2
cocoapods and GoogleSignIn pod version (if applicable) : Google Sign-In SDK 4.4.0

@peterholcomb I had this problem with non-cocoapods install on 1.10.
I've done a workaround base on how Facebook's SDK handles framework location.
To resolve this, I had to add a Framework Search Path to the location where I put my Google Frameworks (for me it is ~/Document/GoogleSDK) in the RNGoogleSignIn.xcodeproj in my project.
Just point to the folder where the GoogleSignIn.framework and GoogleSignInDependencies.framework sit.

Here's what i did to resolve this issue :
-Copy GoogleSignIn.framework and GoogleSignInDependencies.framework to ../node_modules/react-native-google-signin/ios
-remove googlesignin.bundle from copy bundle resource
-remove googlesignin.framework and googlesignindependencies.framework from framework folder, thus unlinking it from binary resource.

Same issue here, for install without cocoa pods. I think the reason is that RNGoogleSignin.xcodeproj has framework search paths that expect pods, or direct placement in ios folder.

I've tried almost every combination of header paths and the only thing that made a difference was moving my GoogleSignIn.framework from /ios/Frameworks folder to the /ios root itself. Which I don't like to have cluttered. Any idea why that is? And how to fix it? Thanks.

I did a workaround like @simonso3 -- with a post-install script that makes sure the Frameworks/Header paths are correct for my custom location for those Frameworks

I did a workaround like @simonso3 -- with a post-install script that makes sure the Frameworks/Header paths are correct for my custom location for those Frameworks

@fbartho What is in your pot-install script?
Someone with conflict with react-native-firebase? No one workaround works for me for an app with<EMAIL_ADDRESS>

I mount a clean app to reproduce this issue with my environment.

Hi, I may have a fix for non cocoapods installs. I think the expected GoogleSigin framework location was long, I made a PR643

had the same issue and when I installed using cocoapods everything worked fine.

this should be fixed in v1.2.3
please open a new issue if the problem persists, thanks.


[BUG] Counter app icons(+/-) should response when clicked

Changes to be made

The plus and minus key should response when clicked
Responses like - color changes / scaling a bit / make a sound / can be anything else

Link : https://master-web-development.netlify.app/projects/counter/
Screenshot :

Please add hactoberfest and GSSoC24 tag. You can assign me for this issue @iamrahulmahato

Hi, @4F24L can you check now, I think It's solved in issue #230

Hello, @Tapabrata-Goswami
I checked that issue and PR. But this issue is different.
I talked about CSS improvement, the plus minus icon should give a response when clicked. Responses like - color changes / scaling a bit / make a sound / can be anything else.

@4F24L ok, you can start work on this.


Cloudflared connection via account

Hello, I would like to start a cloudflare argo tunnel through my cloudflare account and application that is well configured.
As I see from the code it's not possible to do so correct? (only free anonymous tunnels?)
I would like to request to have an option to do so?
https://developers.cloudflare.com/cloudflare-one/tutorials/ssh
$ cloudflared tunnel login
$ cloudflared tunnel create <NAME>

add the config.yml file example from the tunnel above:
tunnel: 6ff42ae2-765d-4adf-8112-31c55c1551ef
credentials-file: /root/.cloudflared/6ff42ae2-765d-4adf-8112-31c55c1551ef.json

ingress:
  - hostname: tunnel.example.com
    service: ssh://localhost:22
  - service: http_status:404
  # Catch-all rule, which responds with 404 if traffic doesn't match any of
  # the earlier rules

 $ cloudflared tunnel run <NAME>

I just made a fork that should do it (if you provide a tar.bz2 with all the same certificates and configurations (as in my initial post).
My plan would be to separate the download of cloudflared etc, and then have another function to do like yours do, and a 3rd to do it with a personal domain config!
https://github.com/joaomamede/colab-ssh


fzf: 0.33.0 -> 0.34.0

Description of changes
https://github.com/junegunn/fzf/releases/tag/0.34.0
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 193341 run on x86_64-linux 1

1 package marked as broken and skipped:

kakounePlugins.kak-fzf

28 packages built:

adl
arsenal
fishPlugins.forgit
fishPlugins.fzf-fish
fontpreview
fzf
fzf-zsh
kakounePlugins.fzf-kak
navi
neuron-notes
python310Packages.pyfzf
python39Packages.pyfzf
spacevim
sway-launcher-desktop
sysz
tmuxPlugins.extrakto
tmuxPlugins.tmux-fzf
unipicker
vimPlugins.fzf-hoogle-vim
vimPlugins.fzf-lua
vimPlugins.fzf-vim
vimPlugins.fzfWrapper
vimPlugins.telescope-zoxide
vimPlugins.vim-fzf-coauthorship
vimPlugins.zoxide-vim
xmloscopy
ytfzf
zoxide

Confirming successful build and quick tests for aarch64-darwin.

FWIW this update broke fzf for me.
❯ fzf
fatal error: mallocgc called without a P or outside bootstrapping
runtime: panic before malloc heap initialized

FWIW this update broke fzf for me.
❯ fzf
fatal error: mallocgc called without a P or outside bootstrapping
runtime: panic before malloc heap initialized

Reverting this commit makes it work. I'm on nixos-unstable-small (bd9f4f3).

Same for me. I think this PR should be reverted until the problem is resolved, it renders the program useless.

Sorry to hear that @andresilva and @IvarWithoutBones. Mind sharing some details about your environment/setup (os, distrib, etc.)?
Unfortunately searching for mallocgc in the fzf repo  did not yield any results…
The error messages seems to originate from Go's malloc.go

Sorry to hear that @andresilva and @IvarWithoutBones. Mind sharing some details about your environment/setup (os, distrib, etc.)?

Thanks for the quick reply. I'm personally on an x86_64-linux machine running NixOS rev f586d35a11ec07ced41d9d62c125c6ca0006141f with kernel 5.19.11. Not sure what other information would be useful.
I imagine its the same issue on any other NixOS installation, but just in case, heres the commit from my dotfiles which should allow you to reproduce the issue when building the nixosConfigurations.nixos-pc flake output: https://github.com/IvarWithoutBones/dotfiles/commit/9cd8fc283a3a77e71903eb26e1d4914cae94cef4.
I have an overlay to revert this PR, figured id share it here as overriding buildGoModule derivations is a bit of  a pain:
  fzf =
    let
      version = "0.33.0";
      src = fetchFromGitHub {
        owner = "junegunn";
        repo = "fzf";
        rev = version;
        sha256 = "sha256-3ZRU5fyb9fG09hG5RkajUW9fl3ukRLN3md+J6O6HosE=";
      };
      vendorSha256 = "sha256-U9cttigqzyy+kQ0YJoV0/2tZJHipNgSSkZyuXGVLoPw=";
    in
    callPackage "${path}/pkgs/tools/misc/fzf" {
      buildGoModule = args: buildGoModule (args // {
        inherit src version vendorSha256;
      });
    };

I'm sorry that you're facing this error. fzfdoes work fine on the commit from this pr (c411ab6084d9c301a2ba92774d2d10046f802234). I can reproduce the error on master. A quick bisection indicates that 8ba120420fbdd9bd35b3a5366fa0206d8c99ade3 is the first bad commit.

Doesn't seem to be an issue on darwin but I can reproduce it on nixos at current master.
Switching to go 1.19 seems to fix it, can someone confirm? https://github.com/NixOS/nixpkgs/pull/193868

Switching to go 1.19 seems to fix it, can someone confirm? #193868

Yes, that commit fixes it.


ClearRoute method doesn't work

Trying to use clearRoute method, I got nothing. Any idea?

#253 fixes it but trying to resolve the numerous linter errors


fix(Button): removing arrays with keyless components

cibuild was failing on warnings due to keyless components being within arrays in the render of Button.jsx.

:+1:

LGTM

:wave:😥:+1:


/en-US/docs/Web/XML/XML_introduction

Request type

[] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x ] Correction or update

Details

Grammar mistakes/Odd grammar in the section on the XML documentation page attached in the screenshot:

An example of better readability:
For an XML document to be correct the following conditions must be fulfilled:
It must be well-formed.
It must conform to all XML syntax rules.
It must conform to semantic rules which are usually set in an XML schema or a
DTD (Document Type Definition).

Fixed. Thanks for reporting!


pypa packaging compliance

@radoering @neersighted stashing pandora's box here; thoughts welcome

Rebased on current main and dropped first commit because it was controversial, not related to pypa packaging compliance and tracked in #399 anyway.


Automatic linking broken on Android

Not sure if I should report the issue here or on the RN main repo.
Versions:
react-native: 0.36.0
react-native-svg: 4.3.1
What I did:
On an existing project, that already has other dependencies which have been linked manually:
npm install react-native-svg --save
react-native link react-native-svg

Then included a sample SVG from the readme of this project in the code as appropriate, after which:
cd android && ./gradlew assembleRelease

What I expected to happen:
The build to succeed.
What happened instead:
FAILURE: Build failed with an exception.

* Where:
Build file '/Users/etheryte/GitHub/project/android/app/build.gradle' line: 141

* What went wrong:
A problem occurred evaluating project ':app'.
> Project with path ':react-native-svg' could not be found in project ':app'.

The problem:
The file ./android/app/build.gradle was modified correctly:
dependencies {
    compile project(':react-native-svg')
    ...
}

However the file ./android/settings.gradle was not modified.
The solution:
Adding the appropriate lines in ./android/settings.gradle as if doing the linking manually solves the problem.
include ':react-native-svg'
project(':react-native-svg').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-svg/android')

Further details:
I haven't tested if the issue occurs on a vanilla set-up without any other linked modules added. The automatic linking works fine for iOS.
The automatic linking reported to have succeeded for both platforms.

Thanks for documenting this, helped me out with the temporary solution

This had been fixed in the latest react-native version.
I'm closing this now.


Uses<EMAIL_ADDRESS>+ include api demo button

This change updates to<EMAIL_ADDRESS>+ includes apidemo functionality built along with the app.
Contributing to Twilio

All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.

[ ] I acknowledge that all my contributions will be made under the project's license.

Pull Request Details
JIRA link(s):

AHOYAPPS-0000

Description
A description of what this PR does.
Burndown
Before review

[ ] Updated CHANGELOG.md if necessary
[ ] Added unit tests if necessary
[ ] Updated affected documentation
[ ] Verified locally with npm test
[ ] Manually sanity tested running locally
[ ] Included screenshot as PR comment (if needed)
[ ] Ready for review

Before merge

[ ] Got one or more +1s
[ ] Re-tested if necessary

closed and reopened as https://github.com/twilio/twilio-video-app-react/pull/257


Custom ViewType

It would be awesome if we could provide custom view types when registering a view. Right now they get generated as soon as a view needs to become available, and this makes impossible for example to prevent the recycling of a certain  kind of items.

Could show me some code to use the custom viewtype feature，thanks～

Please I need example of using a custom view lets say like a map view


Implements the EXISTS filter

After the following discussion and a meeting with @gmourier and @loiclec; https://github.com/meilisearch/product/issues/22
The first version of the filter should be implemented with the following syntax;
The keyword is postfixed
       vvvvv
 price EXISTS
^     ^
A NOT can be prefixed or infixed
vvv       vvv
NOT price NOT EXISTS

With the following set of documents;
{ "id": 1, "product": "T-shirt", "price": 20, "color": "yellow" }
{ "id": 2, "product": "T-shirt", "color": "red" }

The filter price EXISTS will select the first document.
The filter price NOT EXISTS or NOT price EXISTS will select only the second document.

If a field contains an empty array or a null value, it's considered as existing:
{ "id": 1, "product": "T-shirt", "price": 20, "color": "yellow" }
{ "id": 2, "product": "T-shirt", "price": [], "color": "red" }
{ "id": 3, "product": "T-shirt", "price": null, "color": "red" }
{ "id": 4, "product": "T-shirt", "color": "red" }

Here price EXISTS matches documents 1, 2 and 3.

This will ease the handling of incomplete documents. For example, if you want to return all T-shirt that cost less than 20€ or that doesn't have a price specified, you will be able to write product = "T-shirt" AND (price < 20 OR price NOT EXISTS).
That was not possible previously.

For people following this issue, we have already published a docker tag to test the feature
docker run -it --rm \
    -p 7700:7700 \
    getmeili/meilisearch:v0.29.0-filter.beta.0

Or you can compile the source code on the filter/field-in branch on this repo
All the information about the new addition is detailed here
Any feedback is more than welcome!! ❤

I am curious, if my field got value null, does this EXISTS work? I am trying to do a filter UI with the operator option named "Is empty" and "Is not empty" sort of like Notion filter. But it seems like this is not possible.

Will there be any support in the works or we need to put a value like field = '__SPECIAL_NULL__' fake value to circumvent it?

Hey @mech,
Currently, the exists filter matches the documents where the field exists.
Existing means the field in the JSON being equal to null doesn't change anything about its existence.

If a field contains an empty array or a null value, it's considered as existing.

What you're asking for would be another feature we've already thought about. It's not planned currently, but I'm going to open a discussion on our product repository, and it would be nice if you could answer me over there so we don't lose any information!
https://github.com/meilisearch/product/discussions/539


Adds the connection to the backend

This adds the connection from the frontend to the backend
so that we can use the database to use CRUD operations on the backend
database

There are 7 functions added that will allow us to get the data from the backend. We can then write JS code to filter through and get what we need so that we aren't backing up the backend with a ton of queries.


Failed to guess integer column with extra space

embulk guess can't handle integer column with extra space correctly.
I know basically space should be considered part of a column, but some programs like MS Excel creates such a csv file.
http://www.mrexcel.com/forum/excel-questions/4143-csv-space-problem-resolved.html
http://tburette.github.io/blog/2014/05/25/so-you-want-to-write-your-own-CSV-code/
http://q.hatena.ne.jp/1355281826 (Japanese)
I'm not so sure if embulk should support it.  Could you try this?:

add trim_if_not_quoted: true to parser config
run guess

If it works, I think embulk can run guessing with both of try_if_not_quoted: true and try_if_not_quoted: false and then take appropriate config.

It works fine to me.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1816 ms

Resolved: Bofrost.at performance has improved in e851950 after 8 minutes.


plans to use collections

was wondering if there's any plans to use ansible collections.

Yes, we plan. We are waiting on more information how to migrate to the collections.
@mwperina @mnecas

awesome! I been using the vm create role a lot and a freeipa role maintain by their team. They have added theirs as a collection.

I migrated all modules here https://github.com/ovirt/ovirt-ansible-collection and put it to ansible-galaxy. On RPM version I'm still working.


Use PackedStruct to store optional timeouts in Route

In #24659 optional Route timeouts were optimized by using a struct instead of absl::optional. Since then, a more efficient PackedStruct was introduced, that provides even more efficiency, especially in the cases when some timeouts are set, but not all. The PackedStruct is  storing only set values, and not waisting 8 bytes on each of them being optional.
This PR is switching Routes from using a internal struct to using PackedStruct.
This is a step towards more memory efficient config data structures. Issue #24154.

 Also should think about @pradeepcrao's comment, and applying to the other PR that is using PackedStruct

Addressed @pradeepcrao's comment here, and will also apply to Cluster timeouts.

PTAL

/retest

/retest


Feature Request: Multisig support

Hello, it looks like anchor does not support the token program multisig as described here.  I see there are some TODOs in the code that are very old.
Is there a workaround to support this?  If not can this feature be added?

Correct, the wrappers in anchor-spl don't support spl-token multisigs, but you should be able to just copy the functions you'd like to use from the file you've linked and specify the signers array as a workaround.

Yea I did that and it's working.  To use this in any production grade code though we'd want to avoid this workaround.
I think it wouldn't be too difficult to add, just need a new field in the struct and then reference that.  Wdyt?

I don't know what the initial reasoning was for not supporting multisigs, but adding a new field for all these wrapper instructions would break pretty much everyone's code.
Given most people don't or won't use this feature (I don't think anyone asked about it before even though these functions are quite popular), it would be better to find a way to add this functionality without causing breakage.

Ah right struct fields in rust are required.  That definitely makes the backwards compatibility a bit trickier.  Any suggestions on how this could be achieved?


weekly testing failed on AWS

Description
Weekly all platform test run has failed on AWS. As far as I can tell, all instances failed to boot. I've managed to capture the following boot log (only the last 64KB is available): m4.xlarge-boot.log, which points at disk corruption.
Additional information
Failing job: http://jenkins.infra.kinvolk.io:8080/job/os/job/kola/job/aws/124/
Please add any information here that does not fit the above format.

Initially thought this was m4 instance related, but t3 instances have the same issue. Re-running prerelease/aws job to see if it fixes the disk corruption.

Will close now as I think we will address any issues without this ticket - I wonder if it was related to the vmdk corruption we found a workaround for.


docs(GUI): explain why some drives are not bootable out of the box

The usual case is images requiring special treatment. We recommend the
users to use specialised tooling for those cases.
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

Is it worth also explaining that Etcher doesn't set up "persistent" partitions like Unetbootin can do? (or should that come under a separate PR?)

you may want to include specific problematic cases, as well as the specific
tools? if we start listing them here, we will have them ready when we want
a list of what to include in our warnings feature.
--
Alexandros Marinos
Founder & CEO, Resin.io
+1<PHONE_NUMBER>
@alexandrosm
On Fri, Oct 28, 2016 at 9:02 PM, Juan Cruz Viotti<EMAIL_ADDRESS>wrote:

@jviotti commented on this pull request.
In docs/USER-DOCUMENTATION.md
https://github.com/resin-io/etcher/pull/783:

@@ -3,6 +3,15 @@ Etcher User Documentation

This document contains how-tos and FAQs oriented to Etcher users.
+Why is my drive not bootable?
+-----------------------------
+
+Etcher copies images to drives byte by byte, without doing any transformation
+to the final device, which means images that require special treatment to be
+made bootable, like Windows images, will not work out of the box. In these
+cases, the general advice is to use tooling specific to those kind of images,
Fixed!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/etcher/pull/783, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCHlfgzYvBlXzgDG8SWRyuoOGhPqIks5q4sVJgaJpZM4KjktU
.

@alexandrosm Done!
@lurch Good idea! I'll do it in a separate PR.

It also looks like "Windows 10 IoT Core Dashboard" is needed for writing Windows 10 IoT to a SD card
https://developer.microsoft.com/en-us/windows/iot/Docs/GetStarted/rpi3/sdcard/stable/GetStartedStep1.htm


Some embeds only get handled the second time they're sent

For example, youtube video links

This seems to be caused by JDA itself not giving AstralBot the embeds: https://github.com/discord-jda/JDA/issues/2611

As mentioned in the referenced issue, this is a problem with Discord's API itself, so it can't be easily solved.


Fix unit of measurement resolution

This fix uses the most popular unit of measurement for a given device class and leaves to the group converter to deal with unit conversions. This means if your sensors are in one unit but you have a few stragglers, those should get converted and properly aggregated.
Removed the bit that checked for the first entry on list(DEVICE_CLASS_UNITS[device_class])[0] because the new option is just better (again, this integration is heavily opinionated).
This bug was originally reported by @tbrasser on Discord. His PR #391 and his research behind it were paramount on coming to this. Thanks a lot ❤ !

Working great over here!


Multi submitted input step was not handled correctly

What happened?
If we submit input step twice, we will got the following response from devops-apiserver:
{"allow":"false","message":"<nil>"}

It is worth mentioning that there is no any related error log found.
I guess this process is handled at code below:
https://github.com/kubesphere/ks-devops/blob/c96f7386e7cc716e7d2d9269c7376cd56921f07a/pkg/kapis/devops/v1alpha2/devops.go#L453-L458
Expected response
Actually, we expect the result as below:
{
  "message" : "Error processing Input Submit request. This Run instance does not have an Input with an id of 'Deploy-to-prod'.",
  "code" : 400,
  "errors" : [ ]
}

See also https://github.com/kubesphere/ks-devops/issues/363.
/kind enhancement

/close


LW-6950 projected blocks buffer

Context
Our projector needs some speed improvement
Proposed Solution
Implemented a blocks buffer between ogmios and the projector, parallelizing more requests to ogmios.

Replaced by #848


Create, Edit and Delete host

Enables Create and Delete host under inventories to work also under standalone hosts. Also add edit test.

Amazing work improving the code!!!!
approved!


Localstack support

Is your feature request related to a problem? Please describe.
Localstack requires to use custom endpoint url. Lack of aws endpoint configuration introduces a huge complexity for steampipe + localstack integration testing.
Describe the solution you'd like
It wil be great if custom endpoint url can be specified through plugin configuration mechanism.

@cbruno10 Thank you for the quick response.
For my limited Integration testing use case it should be enough to have just one generic endpoint-url  being provided on per connection basis.
As far as I know there is no extra requirements from Localstack.  But AWS provides different regional endpoints for the sake of compliance.  AWS Go lang SDK (googled fro this) has ability to provide custom resolver, here is several useful links:

https://www.linkedin.com/pulse/how-setup-golang-aws-sdk-v2-localstack-local-phuc-hai-huynh/
https://aws.github.io/aws-sdk-go-v2/docs/configuring-sdk/endpoints/

I have never used any of those, so I definetly not the right guy to decide how it can looks like.
Therefore what I can suggest/request for the simple case I have:
There can be a way to set up a default endpoint for all connections, that can be done by supporting environment variable AWS_ENDPOINT (not sure why that is not done by official SDK) (1).
And, nevertheless, should be a way to override default one provided  via AWS_ENDPOINT by specifing endpoint-url for teh parcicular connection (2).

@cbruno10 Thank you for pointing out exact place in the code, I've create a PR for the fix. One thing about that - I'm not sure how that change can be tested automatically, I've checked both options: AWS_ENDPOINT env variable and config with endpoit_url -- both seems to me working.

Thank you for working on and opening a PR so quickly @srgg, great stuff!
While looking around to see if AWS had an environment variable of their own today for the CLI or SDKs for setting an endpoint URL, I came across https://github.com/aws/aws-sdk/issues/229, which contained a proposal from the AWS team on how to handle setting custom endpoints overall. Interestingly, they proposed adding config and environment variable support per service, with some alternative solutions for setting a global endpoint URL (among others).
We like to be as close and consistent with AWS as we can be, though sometimes we do need to deviate from their design principles due to the way plugins are designed. We're closely monitoring how they're thinking of implementing endpoint URLs beyond what they have today (the --endpoint-url CLI argument).
While using LocalStack, or other local AWS environments, do you ever have different endpoints per service, e.g., DynamoDB vs. S3 vs. EC2? Does LocalStack make all of these services available on the same endpoint? Also, do you ever use other local environments, like DynamoDB Local together with LocalStack?
A per service endpoint only design does not seem like it'd work well with LocalStack, assuming that all AWS services are available on the same endpoint in LocalStack.
Look forward to your thoughts on this!

Thanks @srgg for adding your suggestion, I like the idea of having a global endpoint URL with the ability to override per service.
In regards to the AWS plugin, I think following a similar design would be helpful, so here are my proposed ideas on custom endpoints:

Add a config argument, endpoint_url, which is a global custom endpoint and can be set like endpoint_url = "http://localhost:4566"
Add an environment variable, AWS_ENDPOINT_URL, which aligns with the proposed AWS environment variable and our config arg.
As required, add service specific config args and environment variables, similar to what's in the AWS proposal. I don't believe we need these yet, but we should watch when/how AWS implements these custom service endpoints and also prioritize adding them based on user requests.
Order of precedence when evaluating which service endpoint URL to use:

Service specific config argument, e.g., dynamodb_endpoint_url, s3_endpoint_url
Service specific environment variable, e.g., AWS_DYNAMODB_ENDPOINT_URL, AWS_S3_ENDPOINT_URL
Global config argument, e.g., endpoint_url
Global environment variable, e.g., AWS_ENDPOINT_URL

There are plans to move this plugin to use AWS Go SDK v2 as well, and I believe that SDK should support the above proposal as well per Configuring Client Endpoints.
@srgg @johnsmyth - Any thoughts on the proposal above? Thanks!

@cbruno10 Proposed changes make a lot of sense to me. Moreover, I have updated PR that covers the following parts of the proposal you have made:

Add a config argument, endpoint_url, which is a global custom endpoint and can be set like endpoint_url = "http://localhost:4566"

Add an environment variable, AWS_ENDPOINT_URL, which aligns with the proposed AWS environment variable and our config arg.
....

Order of precedence when evaluating which service endpoint URL to use:

Global config argument, e.g., endpoint_url
Global environment variable, e.g., AWS_ENDPOINT_URL

Can you please review the PR one more time, and, hopefully, accept it?


Decrease bundle size by 150kb

Because we sometimes use prismic API functions on the client, we were pulling in cookies, which uses bits and pieces from the Node built-in library, crypto. Next.js (un)helpfully polyfills those for us which results in a rather huge bundle addition.

Might be interesting to add a note on how I found that this was the problem:

Looked at the bundle analysis charts and saw loads of stuff to do with crypto-browserify and bn.js
Did a bit of yarn whying and couldn't see any explicit dependencies, so it must've been some kind of webpack polyfilling magic.
Imported the bundle stats into https://webpack.github.io/analyse/ and found one of the problem modules, then followed back the cjs require links via the interface, which took me through keygrip and cookies until eventually I made it out of node_modules into services/prismic/api.js where I could see cookies being used

🚀


MODULE_NOT_FOUND

Hi! Does anyone know how to solve this error code by any chance?

Run yarn install

i have the same issue @deltaforce99 did you fix it?

when I comment (node index.js ) then errorr shows

MODULE_NOT_FOUND.how can solve it


Camera X Issue

Hey,
I haven't actually tried your code, but wanted to ask for help.
After the latest update with Sentry mode, have you been able to get the Tesla to write to the raspberry pi without showing the "Camera with X" icon

Sentry hasn't been released in my region yet so I'm not sure. This aside, I have noticed on recent updates the power the USB ports can provide appears to have dropped meaning the Pi becomes unstable.


ImportError: cannot import name 'escape' from 'jinja2'

Environment:

Python version: 3.7
Jinja version: 3.1.0

Sounds like a library you use is attempting to do from jinja2 import escape, which was previously deprecated and now removed. You'll need to open a bug with that library.

You really should be doing these types of breaking changes when releasing a new major version, nor a minor version. This is odd, really, to see removal of deprecated API across a minor version.

See https://hynek.me/articles/semver-will-not-save-you/, https://snarky.ca/why-i-dont-like-semver/, and https://bernat.tech/posts/version-numbers/, which go in depth on why pinning is the only valid solution to these types of issues, regardless of any project's version scheme.

When the cause is hidden somewhere in your dependency tree, as in my Flask app, you can workaround for the moment by adding explicit dependecy to your requirements.txt
jinja2==3.0.3

Jupyter maintainer here. Thanks for the heads up on the nbconvert repository.
Would you considering adding a shim back in a patch release? I think that this will break a lot of downstream use cases.
In general, I think it would be better for complete removal of deprecated APIs to only happen at major releases. It seems that these were deprecated with jinja2 3.0 and completely removed in jinja2 3.1, which is quite a short span of version for downstream packages to adapt to the change.

I don't plan to add any removed code back in. From past experience, it allows users who are not pinning or testing with warnings to defer, because suddenly they don't see the error anymore. Then they raise the same issue when I remove the shim later anyway.
We do not use semver, and have never indicated that we do. See https://hynek.me/articles/semver-will-not-save-you/, https://snarky.ca/why-i-dont-like-semver/, and https://bernat.tech/posts/version-numbers/. 3.0 was released in May last year, I do not consider 10 months a short span of time. From past experience I don't believe that any particular amount of time would have had a different result.
Deprecations have entries in the change log and warnings in the code. Use a tool like pip-tools to pin your dependencies and control when you get updates. Be sure to run your tests with deprecation warnings treated as errors so that you get notified of these types of changes early.
It looks like many of your users use nbconvert during documenation builds. For an example of how to pin for docs builds, see Jinja itself. This allows us to have a reproducible environment, and address upgrades on our schedule. For nbconvert itself, if you test with warnings as errors, you could address these before they become an issue, allowing your users to continue to ignore pinning for a bit longer.

Use a tool like pip-tools to pin your dependencies and control when you get updates

I am sorry, this only work if you have one package that depends on Jinja. You can very well end up with multiple dependencies that themselves depend on Jinja, if they all pin the specific Jinja version they need, you end up with an impossible to resolve environment at best (if using a package manager that solves the version constraints) or a completely broken environment at worst. This solution does not scale unfortunately.

I can see why Quart/Flask/whatever library won't pin to a Jinja2 version. And I usually don't pin to any specific version of dependencies of libraries I use because it turns it into a maintenance hell (figuring out new dependency versions when we upgrade library versions).
But this was pretty messy... all of the sudden libraries that depended on Jinja2 got broken without any change in version or their code. And apps that depended on those libraries pinned to versions known to work. I agree with @cculianu that this could have been better handled by not breaking API's in minor version updates.
On the app developer's side, I'm thinking that maybe this can be prevented in a similar way the JavaScript community uses package.json vs package-lock.json.

I certainly feel for any maintainer with tons of downstream users and who has to put up with long deprecation cycle. That said, in this case, for such a crucial library the deprecation cycle definitely felt too short as shown by the fact that many major libraries like sphinx, jupyterhub and a few others (including one I maintain) Panel did not adapt in time. In practice semver is indeed a dream most libraries can't live up to but this change in a minor version left a lot of people scrambling to catch up. I'm not in a place to ask anything of you, not knowing what the maintenance team looks like, but I would implore longer deprecation cycles for such major deprecations.

Would you considering adding a shim back in a patch release? I think that this will break a lot of downstream use cases.

I think with a module level getattr, this can be done cleanly.
Personally, I prefer what the Java world does. Deprecation yes, removal never, it just hurts too many people/users/developers.

Personally, I prefer what the Java world does. Deprecation yes, removal never, it just hurts too many people/users/developers.

Indeed. In this case I would estimate tens of thousands, if not hundreds or millions of dollars worth of developer time has been needlessly wasted, worldwide, due to all the breakages in public and private projects.  I know our group spent about $2000 in developer time troubleshooting this and updating our docker images for CI to pin jinja2 to 3.0.0.  And likely our predicament has been repeated globally thousands of times...

And yet, if downstream applications took on the responsibility of pinning their dependency tree, and testing with warnings as errors, they would have been able to control exactly when they received updates and been able to respond proactively to any changes. This is universal, it's not specific to Jinja. If you pin at least one dependency you have to pin the whole tree otherwise any library at any time could update while another remains pinned.
I'm locking this now as I don't see this discussion continuing productively.


NoMethodError: undefined method `compatible?' for nil:NilClass

When I run  rails aws_record:migrate I keep getting  the below error.
NoMethodError: undefined method compatible?' for nil:NilClass`
Have I missed anything?

The problem was that I generate model myself. I generate model with the aws_record and everything is working just fine.


_ready from instantiated .tscn within EditorPlugin won't be called (neither _init or _enter_tree)

Godot version:
fa02453
OS/device including version:
Arch Linux
Issue description:
When adding a Control to bottom panel with add_to_bottom_panel within a EditorPlugin, the _ready() function won't ever be called neither _init() or _enter_tree().
Steps to reproduce:

Create a new plugin.
Within the _enter_tree() of the main script, instantiate a .tscn file.
The _ready() function won't be called, neither _init() or _enter_tree().

Minimal reproduction project:
Plugin Issue.zip

you need to add tool keyward in Control.gd
tool

extends Label

func _ready():
	print("Label Loaded")

@volzhs Still not working, here.

@volzhs Ok, I swear I tried it before but it didn't work, but now it's working. Please, forgive my dumbness.

@volzhs, I just noticed what is the problem: the _ready() function will only get called when opening the project. If I desactivate and reactivate the plugin, it won't be called. Is this behaviour expected?

Closing as duplicate of #16974.


add partmc to music-box

Allows music-box to simulate aerosols using PartMC particle-resolved aerosol representation

#147 is removing all of the fortran based components and moving to python. @jcurtis2 either we need to close this or merge in that branch and use pypartmc

Great! With the creation of PyPartMC, utilizing that python API to run PartMC should be rather straightforward and the best way to proceed.

Closing for now. We are currently including pypartmc as part of music box interactive (so not music box). But, once that work is complete, and pypartmc can handle camp configuraiton files, we could pull pypartmc down from the api server into here and include it directly


Always "heating to"

Using this DeviceHandler (thank you for creating it!) on my new Stelpro Orleans Convector Wall heater.
Even when setpoint is lower than room temp, Smartthings App shows as "heating". See screenshot.

Also, the "configure" tile doesn't do anything

Hi Kevin,
When you are seeing this behavior, is the Orlean Convector really heating?

Is your Orlean Convector running at the specified setpoint?
If not, it could be a connection issue between the device and the SmartThings hub.

I don't believe it's running but I'm unable to easily check now as I installed the heater in a vacation rental property of ours. I'll see if I can reset the hub or if there are other options which I can do remotely.

Thanks for the quick response, btw.

I have a related issue in that the set temperature between the up and down arrow is blank (I didn't know there should be one until I saw this post).  I have to go to the "Recently" screen to see the set temp.  If i increase the temp enough to start the heater, the "heating to xx" appears but otherwise I cannot see the set temperature. If I get the heating to message and the color turns to orange, it will not return to green once I bring the temp down below the set temp. It continues to show "heating to 74" when the room temp is 79. The heater is Not on in this condition though it says "heating to xx"  BTW I also have the Z-Wave version of this thermostat.  The "Heating to" and color works fine but it also does not show the set point temp between the up and down arrows. It would be very convenient to have a slide bar to raise and lower the temp rather than hitting an up or down arrow to make the change.  I am not typically making a minor adjustment but rather a much larger change when I arrive or depart my cottage.

Hi Paul, since you refer to the Z-Wave version, please post on the appropriate thread.
Despite being very similar, both device handlers are different and must not be mixed

I will.
Thank you
Paul

On Jul 11, 2017, at 7:22 AM, stelpro<EMAIL_ADDRESS>wrote:
Hi Paul, since you refer to the Z-Wave version, please post on the appropriate thread.
Despite being very similar, both device handlers are different and must not be mixed
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Greetings. I reset/restarted my Smartthings hub and tried everything I could remotely, but the ST App still continues to say "Heating to x" (and the tile is orange) even when the unit is not actually heating because the room temp is greater than the set point. Is there anything else I can try/check (remotely)?

Please try to power cycle your convector.

Is there a way to do this remotely? If not, I will have to find someone near the vacation rental property (where the convector is installed) to flip the breaker box off and on.

No, you cannot power cycle the unit remotely (and since you have connection issue, it's most likely that it wouldn't work anyway).
You need to go to the physical location.

I am having the same issue as kevnord  but  unlike him, my cottage is equipped with a remote power cycler; my wife :)
Once she cycled the breaker on and off the"Heating to xx" cleared and the status tile reverted to green with "Comfort".

Hey Paul, do you have to recycle it often or did one recycle fix it?

Kevin, My wife shutoff the breaker, gave it a 10 count and turned it back on.  I have 2 hubs in 2 homes so to be safe I toggled to my other location and back before I checked the status. I did not reboot or do anything else.

The cycling of the power on & off cleared the "heating to xx" issue but did not resolve the fact that I still do not have a set temp showing between the up and down arrows as Kevin's screen shot shows.

Thanks for the info, Paul! I'll give that a shot. Appreciate the help!
Do you have any other interesting devices setup in your homes that you recommend?
I updated all of the (baseboard/convector) thermostats to Stelpro Kis and added door and water (crawlspace) sensors. I want to add some zwave light switches but that's about it.

Kevin,
I have a Schlage door lock, garage door opener, numerous water/leak & temp/humidity sensors, a water main valve and a 220V contractor to shutoff my water heater and z-wave lights, outlets dimmers & paddle fan switches.
With one home in RI and the other in FL, I can pre-heat or pre-cool or shut down either home before I arrive or upon departure.  For example my "Shutdown" automation  locks the front door, closes the garage, turns off various lights and water heater, shuts the water main, and sets the temp to either standby heating in the winter or standby cooling/dehumidification of my FL home when we are away.
I have also integrated each home with Alexa so certain features can be controlled verbally; Lights on/off, or dimmed, change the temperature, lock the front door, etc.  Until I added Alexa, my wife didn't use Smartthings other than what I automated.  Now she uses it more.
 Paul
  From: Kevin Nord<EMAIL_ADDRESS>
To: stelpro/Ki-ZigBee-Thermostat<EMAIL_ADDRESS>Cc: paullsoucy<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Tuesday, July 11, 2017 3:43 PM
Subject: Re: [stelpro/Ki-ZigBee-Thermostat] Always "heating to" (#2)
Thanks for the info, Paul! I'll give that a shot. Appreciate the help!
Do you have any other interesting devices setup in your homes that you recommend?
I updated all of the (baseboard/convector) thermostats to Stelpro Kis and added door and water (crawlspace) sensors. I want to add some zwave light switches but that's about it.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Nicely done! I thought about getting a 220V contractor to shut off my water heater... may need to make that a priority. Our cottage is on San Juan Island here in WA State. It's completely booked from June'ish through Sept and hardly rented the rest of the year. We could likely save some $ by shutting down the water heater during the off-season.
 I work only a few blocks from Amazon HQ... so becoming a Prime member is unavoidable. :-)

Well hmmm....
I was able to find someone to off/on the heaters braker switch.
Initially, things looked great! Setpoint at 60, Temp at 70, tile green, no "heating to..." perfect!
I set the setpoint to 75, tile turned orange, "heating to 75" was displayed... again, perfect!
Then, I dropped the setpoint back to 60... tile renamed orange and "heating to 60" was displayed even though it's clearly below 70.
Not sure to go from here other than taking a look at the device handler code and/or forking off my own version.

Kevin,
This is what I found as well.  Cycling the breaker clears the "heating to" but the issue returns after the condition for heating happens again. Paul
  From: Kevin Nord<EMAIL_ADDRESS>
To: stelpro/Ki-ZigBee-Thermostat<EMAIL_ADDRESS>Cc: paullsoucy<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Thursday, July 13, 2017 3:40 PM
Subject: Re: [stelpro/Ki-ZigBee-Thermostat] Always "heating to" (#2)
Well hmmm....
I was able to find someone to off/on the heaters braker switch.
Initially, things looked great! Setpoint at 60, Temp at 70, tile green, no "heating to..." perfect!
I set the setpoint to 75, tile turned orange, "heating to 75" was displayed... again, perfect!
Then, I dropped the setpoint back to 60... tile renamed orange and "heating to 60" was displayed even though it's clearly below 70.
Not sure to go from here other than taking a look at the device handler code and/or forking off my own version.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I'll see if I can make sense of the 600+ lines of code in the handler and come up with a fix. I'm not a javascript expert but am a software engineer by day (allrecipes.com) so there's a chance I can get it to work.

I'm currently working on it.
SmartThings made a lot of changes in their platform since I produced the device handler.
Some commands are broken

Splendid! Thanks "stelpro" for you help... it's greatly appreciated! Let me
know if there's anything else I can do to help.
On Thu, Jul 13, 2017 at 2:33 PM, stelpro<EMAIL_ADDRESS>wrote:

I'm currently working on it.
SmartThings made a lot of changes in their platform since I produced the
device handler.
Some commands are broken
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stelpro/Ki-ZigBee-Thermostat/issues/2#issuecomment-315208303,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGL4prDdNR3EusLeK1zFlJD1OBtug3Yks5sNo0ngaJpZM4OTJ7k
.

I have created a branch with a test version.
Give it a try and let me know the outcome.
I'm out for the day.
https://github.com/stelpro/Ki-ZigBee-Thermostat/blob/BugFix-Always-"heating-to"/Stelpro-SmartThing Device Handler(MultiAttribute).txt

The test version seems to fix the issue! The up down setpoint buttons seems slow to respond but I've noticed that before and it seems to improve somehow
Thanks

Branch merged with trunk.
Issue closed


Bump egui version 0.30

If you want to create a release commit, then please also change the CHANGELOG.md in it!


Support for overriden column types

Fixes #42
Still need to add tests, but like some feedback on the code.

@mdesmet could you please also add an info about your change in CHANGELOG.md?


Add support for file watchers

Example implementation:
/**
 * Start a file watcher in the background.
 *
 * @param path is the path that should be watched.
 * @param func receives the file system events.
 * @returns a structure for closing the watcher.
 */
export function watch(
  path: string,
  func: (event: Deno.FsEvent) => void | Promise<void>,
) {
  const watcher = Deno.watchFs(path, {
    recursive: true,
  });
  (async () => {
    for await (const event of watcher) {
      await func(event);
    }
  })();
  return {
    close: () => {
      watcher.close();
      return Promise.resolve();
    },
  };
}

Implemented with #26


Replicating xunit test example

I trying to replicate your test example and I am getting the following error
The following constructor parameters did not have matching fixture data: DbContextOptions`1 contextOptions

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

ID: 5589fb47-8773-6ed5-e152-136bfee49da3
Version Independent ID: c9f5b694-d1a0-479e-43f2-5dc1fe74590b
Content: EF Core testing sample - EF Core
Content Source: entity-framework/core/miscellaneous/testing/testing-sample.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @ajcvickers
Microsoft Alias: avickers

@devLarka Can you compare your code to the downloaded complete sample to see what you might be doing differently?

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


Sometimes posts video twice

I have been using a script to loop the script, which looks like:
#!/bin/zsh
while true
do
    python3 main.py
    sleep 60
done

However - sometimes, singular videos added to the playlist sometimes get posted twice. I am unsure why this happens, and it requires further investigation.
Just leaving this issue here for myself (whenever I get time to work on it).

An update: this does not only apply to singular videos, but entire batches. Will investigate…

No clue if it's because of #11, but… videos no longer send twice. Huh.
Closing for now.


it seems to be wrong progbar when verbose = 1 in the model.fit function

Hi,
I am a keras rookie. I have installed the keras and theano successfully at the latest version with the following command :

pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps
And I run some toy code, and got a strange output like that.

from keras.models import Sequential
from keras.layers import Dense
import numpy
seed = 7
numpy.random.seed(seed)
X = numpy.random.random((768,8))
Y = numpy.random.randint(2,size=(768,1))
model = Sequential()
model.add(Dense(12, input_dim=8, init='uniform', activation='relu'))
model.add(Dense(8, init='uniform', activation='relu'))
model.add(Dense(1, init='uniform', activation='sigmoid'))
model.compile(loss='binary_crossentropy', optimizer='adam', metrics=['accuracy'])
model.fit(X, Y, nb_epoch=150, batch_size=10, verbose=1)
scores = model.evaluate(X, Y, batch_size=40,verbose=1)
print("%s: %.2f%%" % (model.metrics_names[1], scores[1]*100))
the output is as follows:
768/768 [==============================] - 0s - loss: 0.6738 - acc: 0.5846
Epoch 147/150
768/768 [==============================] - 0s - loss: 0.6742 - acc: 0.5885
Epoch 148/150
768/768 [==============================] - 0s - loss: 0.6728 - acc: 0.5846
Epoch 149/150
768/768 [==============================] - 0s - loss: 0.6741 - acc: 0.5859
Epoch 150/150
768/768 [==============================] - 0s - loss: 0.6750 - acc: 0.5859
40/768 [>.............................] - ETA: 0sacc: 59.37%
The progbar just run 1 batch and breaked.
After some limited debugging, I think it' wrong with the model.fit when verbose is set to 1.
So what I should do to solve it? It's seem to be OK just setting verbose to 0.

Hi @cyzhangAThit, did you figure what was the reason? I have the same problem. It just stops after certain number of batches.
Thanks


refactor: add icons module

Move icon sets, specific icons, and icon-related functions to their own module.

This is in preparation for #4, and it declutters battery.lua


RoW/DS Update

Just wanting to see how these events look on the timeline...

@jofwu I've opened PR #130 to sync with en.


How to send failure details using webhook option

as per readme file, Sending failure details in a thread is not supported when using webhooks. You will need to use Option B below.
This doesn't answer that can it be sent in any other way or sending failures is not supported at all?
Do you have an example to resolve this?

I came across this thread. Can you answer that could I send failed tests inside the main slack notification?

@aakashgupt webhooks does not support threads

Can you answer that could I send failed tests inside the main slack notification?

thats the default behaviour. Can you elaborate what exactly you are trying to do?


Broken link in README

The link to the new location should be https://github.com/aptly-dev/aptly/tree/master/completion.d, not https://github.com/aptly-dev/aptly/tree/master/bash_completion.d

Thanks, fixed!


Ledger Support Errors

I have found the following error when using `import
{ setupLedger }
from "@near-wallet-selector/ledger";`. Particularly, the error is:
@parcel/core: Failed to resolve '@ledgerhq/devices/hid-framing' from<EMAIL_ADDRESS>To reproduce simply add the ledger package and try to use it.

A discord user has reported another error: https://discord.com/channels/490367152054992913/542945453533036544/1009482022290464819

Hey, @gagdiez thank you for raising this issue.
After some investigation yesterday in the issue we found that this error is showing up only with parcel and not in other bundlers.
This issue seems to be on the latest version of @ledgerhq/hw-transport-webhid  which  internaly depends on @ledgerhq/devices and also is a dependency in our @near-wallet-selector/ledger package.
We found this suggestion here to be a good solution: https://github.com/LedgerHQ/ledger-live/issues/763#issuecomment-1211834941.
Basically this si what is being suggested there: adding parcel-style alias to the package.json seems to help:
{
  ...
  "alias": {
    "@ledgerhq/devices": "@ledgerhq/devices/lib-es"
  }
}

See their docs on using these packages with parcel: https://developers.ledger.com/docs/transport/web-hid-usb/#packagejson

About the reported issue on discord, there was not enough information to know what the exact issue was so I asked them to open a new issue here in this repo.

Thanks, adding the alias resulted in a different error, which I solved by adding a second alias:
"process": {
			"global": "{}"
		}

Maybe it would be useful to add that in the README? Also, we could add a "known errors" in the README.md

Was the error about process caused by @near-walllet-selector/ledger ?
The error about process might be related to something else, can you please share more details or a screenshot?

I further tested it, and the error was not being originated from the wallet-selector/ledger.
I saw your comment in the PR, with the Known Issue being added to the Ledger page. I would still recommend to bring it to the front README.md so people can find it easier.

Hey, @gagdiez after more investigation on the issue which was happening with dApps that use parcel as a bundler I found that removing the caret (^) symbol from @ledgerhq/hw-transport-webhid and @ledgerhq/hw-transport on our side avoids these errors which are caused by the latest versions of these dependencies.
I also addressed the issue reported on discord.
I believe we will need to publish a minor release.
Thank you for your feedback again.


Ship v3.3.2

Preps release for v3.3.2. Changes include only the version bump.
/cc @twbs/team

:dancers:


Fixed #24751 -- Fixed HStoreField isnull lookup.

https://code.djangoproject.com/ticket/24751

LGTM


nodePackages.gtop: init at 1.0.0

Motivation for this change
This PR adds gtop to the nodePackages list. It is a system monitoring dashboard for the terminal.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

I need to (and will) rebase this, but is there anything that keeps this from being merged? I would like to avoid rebasing this every few weeks.

rebased

@globin @Ma27 @domenkozar @adisbladis any chance of merging this?

Built and tested locally on x86_64 NixOS, appears to work fine.

@ivan thx for the suggestion! done.

@GrahamcOfBorg build gtop