❓ How-To Use JQ to Extract .results output

I'm trying to work with the results output via JQ, but am having difficulty extracting the results.
All of the other outputs (ie. plugins_used and filters_used) are array objects, and easily referenced via JQ commands such as .plugins_used[].name or .filters_used[].path.
I'm struggling to reference any of the objects/values from the .results output since it is not an array, it's a list of objects. Is there an option to change the output so it's consistent with the other 2 listed? Or, can anyone provide some guidance on the correct JQ query format for .results extraction?
Example .secrets.baseline file
{
  "version": "1.2.0",
  "plugins_used": [
    {
      "name": "ArtifactoryDetector"
    },
    {
      "name": "AWSKeyDetector"
    },
    {
      "name": "AzureStorageKeyDetector"
    },
    {
      "name": "Base64HighEntropyString",
      "limit": 4.5
    },
    {
      "name": "BasicAuthDetector"
    },
    {
      "name": "CloudantDetector"
    },
    {
      "name": "GitHubTokenDetector"
    },
    {
      "name": "HexHighEntropyString",
      "limit": 3.0
    },
    {
      "name": "IbmCloudIamDetector"
    },
    {
      "name": "IbmCosHmacDetector"
    },
    {
      "name": "JwtTokenDetector"
    },
    {
      "name": "KeywordDetector",
      "keyword_exclude": ""
    },
    {
      "name": "MailchimpDetector"
    },
    {
      "name": "NpmDetector"
    },
    {
      "name": "PrivateKeyDetector"
    },
    {
      "name": "SendGridDetector"
    },
    {
      "name": "SlackDetector"
    },
    {
      "name": "SoftlayerDetector"
    },
    {
      "name": "SquareOAuthDetector"
    },
    {
      "name": "StripeDetector"
    },
    {
      "name": "TwilioKeyDetector"
    }
  ],
  "filters_used": [
    {
      "path": "detect_secrets.filters.allowlist.is_line_allowlisted"
    },
    {
      "path": "detect_secrets.filters.common.is_ignored_due_to_verification_policies",
      "min_level": 2
    },
    {
      "path": "detect_secrets.filters.heuristic.is_indirect_reference"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_likely_id_string"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_lock_file"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_not_alphanumeric_string"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_potential_uuid"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_prefixed_with_dollar_sign"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_sequential_string"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_swagger_file"
    },
    {
      "path": "detect_secrets.filters.heuristic.is_templated_secret"
    }
  ],
  "results": {
    ".git/FETCH_HEAD": [
      {
        "type": "Hex High Entropy String",
        "filename": ".git/FETCH_HEAD",
        "hashed_secret": "58a55e98794b8084b7b62818130161602192aa0g",
        "is_verified": false,
        "line_number": 1
      }
    ],
    "docker-example-app/AWS_Creds.txt": [
      {
        "type": "Base64 High Entropy String",
        "filename": "docker-example-app/AWS_Creds.txt",
        "hashed_secret": "d70eab08607a4d05faa2d0d6647206599e9abc65",
        "is_verified": false,
        "line_number": 2
      },
      {
        "type": "Secret Keyword",
        "filename": "docker-example-app/AWS_Creds.txt",
        "hashed_secret": "d70eab08607a4d05faa2d0d6647206599e9abc65",
        "is_verified": false,
        "line_number": 2
      }
    ],
    "docker-example-app/app/src/static/js/react-bootstrap.js": [
      {
        "type": "Secret Keyword",
        "filename": "docker-example-app/app/src/static/js/react-bootstrap.js",
        "hashed_secret": "075e612807abd3769475e780d17be2ba935a6ec1",
        "is_verified": false,
        "line_number": 7843
      }
    ]
  },
  "generated_at": "2022-06-24T15:56:49Z"
}

If you want the keys for results.
cat .secrets.baseline | jq -c -r '.results | keys[]'

Hey @eddiez9 and @jpdakran, thanks for that example. It solves the issue partially (in that I can get the first-level item from the object array), but I still need to extract Key's array of objects, and their respective properties (ie. filename, line_number, etc.).
I would expect it to be relatively simple, but I'm stills struggling with it. I would expect it to be similar to .results | keys[].filename, keys[].line_number but that doesn't work.
Any other thoughts/suggestions?

@AErmie If you want the values
cat .secrets.baseline | jq -c -r '.results | values[][].filename'

Thanks @eddiez9 for the clarification. This looks to be resolved. If there are any additional queries - feel free to open a new issue.


Bug fix leave table

Leave table now shows leaves in correct order after deleting and adding leaves

Codecov Report

Merging #140 (3d13fd3) into master (b3b86ed) will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #140      +/-   ##
============================================
- Coverage     61.01%   60.94%   -0.07%
  Complexity      499      499
============================================
  Files            89       89
  Lines          1980     1982       +2
  Branches        239      239
============================================
  Hits           1208     1208
- Misses          705      707       +2
  Partials         67       67

Impacted Files
Coverage Δ

src/main/java/coydir/model/person/Person.java
69.74% <0.00%> (-1.20%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


a problem on routing iteration

Hi,
If the routing iteration is greater than 1, the loss will become nan. What can I do to modify it?

Besides, the transformation matrix W_ic seems fixed in your code, which I think that need  to learn during the training process?

I found that the NaN is caused by small sigma, which led to a large likelihood. You may try to calculate log(P) instead p and calculate r by tf.reduce_logsumexp @www0wwwjs1

Thanks a lot for the suggestion!

@www0wwwjs1
Is the suggestion resolved?

There's still some problems, I print out the activation of the class capsules layer, it seems that all of the activation is 1., I guess it's caused by a large -log(sigma_h) so the logits are so large. It seems that decrease the temperature(lambda) to 1e-3 will work. I don't know if it is reasonable, what's your idea? @www0wwwjs1  Thanks!

@rtz19970824
Could you please mark the particular lines that you're improving? Thanks!

\lambda = 0.01 is already used in the latest version of the code and it helps the robustness. Another implementation also adopts similar parameter. It looks like a reasonable configuration here, however the original paper rarely mentioned the specific value of such parameters.

@yhyu13
I change the e-step into
p_c_h = -0.5 * tf.log(2 * math.pi * sigma_square) -tf.square(votes - miu) / (2 * sigma_square)
p_c = tf.reduce_sum(p_c_h, axis=3)
a1 = tf.log(tf.reshape(activation1, shape=[batch_size, 1, caps_num_c]))
ap = p_c + a1
sum_ap = tf.reduce_logsumexp(ap, axis=2, keep_dims=True)
r = tf.exp(ap - sum_ap)

Thanks for the suggestion of stability, bigger number of iterations is supported now.

I'm still a little confused. Is this necessary:
log_p_c_h = log_p_c_h -
(tf.reduce_max(log_p_c_h, axis=[2, 3], keep_dims=True) - tf.log(10.0))
@www0wwwjs1 @yhyu13

@rtz19970824
Yes. If you comment that line, it gives NaN gradient & loss during training immediately on both dataset. Let me know if this happens on your machine too

@rtz19970824
The purpose of this line is only to help the numerical stability, as shown in @yhyu13's comment. It does not correspond to any part of the algorithm in the original paper.

Thanks.
It seems that if the results on mnist don't perform like your report, maybe there should be a check?@www0wwwjs1

The experiment on MNIST was casted with an old version of the code. After the experiment, we added more things to further improve the performance especially for the more challenging smallNORB dataset. These auxiliary parts may impact the performance on the MNIST as well, however I think it will be positive influence. I also plan to recast the experiments on MNIST after we finished current experiments on smallNORB. If negative influence is observed, please let us know, many thanks.

I clone the latest version and run it without change any hyper-parameters. The loss is decreasing. However, the test accuracy cannot improve. I also try to set the "is_train" flag false, the test accuracy don't improve as well. I just run the command "python3 train.py "mnist"" and "python3 eval.py "mnist"". If there's anything wrong on my experiment settings, please let me know. Thanks!

Sorry, that's my bad. I pushed some experimental configurations without solid validation. You can clone the project again. The latest version of configuration should be valid. The same hyper-parameters are also used in our newest experiments. Although the final results is still incoming, the test accuracy is already growing up.

Thanks! it can perform well know.

Did anyone manage to get this to work with 3 or more iterations?

In em-routing's m-step, why not updating mean in the first two iterations? capsule_em.py L352? (the else part does not clear), can you give some explaination here, thanks


Please add any kind of license

MIT or Apache or even BSD. Or of course anything else, it's your code after all. :P Just anything to get a handle on this because as it stands, this code is "look don't touch", which is really a shame. :)

I am not sure if I can because the University of Tübingen filed a patent on this.
My apologies!
Leon

Wow, didn't see that one coming. For reference: I guess this is the (first) patent in question?
https://patents.google.com/patent/DE102015009981A1/en
Well, if you ever figure this out, I'm sure it would be appreciated. :)

I am not sure if I can because the University of Tübingen filed a patent on this.

The University of Tübingen's FAQ about patent law is very relevant here. See Die häufigsten Irrtümer über Patente - 17. Patente und Open-Source-Software schließen sich aus. Unfortunately, the website is currently broken and clicking on the question does not expand the answer. But you can probably contact any member of their team to get this issue sorted out.
Anyway, thank you for at least making the code public, even if the license thing should not work out.


Add support for inlined base64 source maps

i.e. to support Browersify's source maps: browserify(debug: true)

very nice thanks! I'll try to get this in some time this week


Fix problem of wrong shaped array. See issue #119

This is the pull request you were asking me to do in issue #119. Sorry took me a while to do it. I thought it would be more complicated

Great, thanks!

Looks like the tests are failing. Probably a bug in the changes somewhere

I belief now it is fixed


Latest master doesn't compile

As of 69cbc57d
error[E0596]: cannot borrow `h` as mutable, as it is not declared as mutable
   --> crev-lib/src/util/mod.rs:172:5
    |
162 |     let h = crev_recursive_digest::RecursiveDigest::<crev_common::Blake2b256, _, _>::new()
    |         - help: consider changing this to be mutable: `mut h`
...
172 |     h.get_digest_of(root_path)
    |     ^ cannot borrow as mutable

For some super weird reasons, it works here.

Oh. Are you on Windows? I think it was a problem in the crev-recursive-digest library. I upgraded it, and hopefully it will be gone now.

I'm on macOS.

But yeah, it works now.


watchdog ignore closed_no_write

Ignore file closed_no_write events in the Watchdog Reloader.
fixes https://github.com/pallets/werkzeug/issues/2945

Watchdog 5.0.0 drops support for python 3.8. Two options

werkzeug can also drop support
change the watchdog event reload from opt-out of events to opt-in events that should trigger a reload

The second option is probably better. Thoughts @davidism?


Error No such file or directory

These errors occur during the course download process. I'm using the latest version of your program.

@Drovosek01 i cannot explain the error which is already discussed so many times on windows you will face all the time same problem if the path is longer then specified path convention. read on Microsoft for that or check the older issues. closing this as dupliacte


confusing for the io.copy operation

In the xtaci/kcptun/server/main.go:
func handleClient(p1, p2 io.ReadWriteCloser, quiet bool) {
	if !quiet {
		log.Println("stream opened")
		defer log.Println("stream closed")
	}
	defer p1.Close()
	defer p2.Close()

	// start tunnel
	p1die := make(chan struct{})
	go func() { io.Copy(p1, p2); close(p1die) }()

	p2die := make(chan struct{})
	go func() { io.Copy(p2, p1); close(p2die) }()

	// wait for tunnel termination
	select {
	case <-p1die:
	case <-p2die:
	}
}

what's the effect of the p1die and p2die?
I just see close operation and empty select clause. I wonder what will happen if I get rid of the two channels.

just try it


Procurement for Pen Testing

Prepare and run pen testing procurement to penetration test of metadata.nhs.uk.

Still needs doing unless it will be done by the supplier.

This has been completed by the Security Assurance.
Related issue - https://github.com/NHSDigital/DataDictionaryPublication/issues/330


fix: Allow fillAlpha for bar charts. Closes #12

@danmana did you by chance also work on make it working for chart.js v3?

@Rello no, unfortunately, I did not update to v3 yet, so I don't know what the differences might be

Thank you for your contribution!


Testing dep check report output

Short description outlining key changes/additions
JIRA Ticket Number
Type of change

[ ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

Closing PR - no longer needed

CI: No security warnings found


brew cask outdated does not do what is described

General troubleshooting steps

[x] I have checked the instructions for reporting bugs (or making requests) before opening the issue.

[x] None of the templates was appropriate for my issue, or I’m not sure.

[x] I ran brew update-reset && brew update and retried my command.
[x] I ran brew doctor, fixed as many issues as possible and retried my command.
[x] I understand that if I ignore these instructions, my issue may be closed without review.

Description of issue
brew cask outdated does not work as described. From the help section of the client (brew cask help) "outdated - list the outdated installed Casks". Does this mean that it will display a list of software that is outdated? If so, then the current version is not doing that.
Output of your command with --verbose --debug
$ brew cask outdated --verbose --debug
==> Checking update info of Cask alfred
==> Checking update info of Cask docker
==> Checking update info of Cask docker-toolbox
==> Checking update info of Cask filezilla
==> Checking update info of Cask firefox-beta
==> Checking update info of Cask flycut
==> Checking update info of Cask gimp
==> Checking update info of Cask google-chrome-beta
==> Checking update info of Cask intellij-idea
==> Checking update info of Cask iterm2-beta
==> Checking update info of Cask itsycal
==> Checking update info of Cask java
==> Checking update info of Cask mattermost
==> Checking update info of Cask postage
==> Checking update info of Cask postgres
==> Checking update info of Cask postman
==> Checking update info of Cask sourcetree-beta
==> Checking update info of Cask the-unarchiver
==> Checking update info of Cask virtualbox-beta
==> Checking update info of Cask visual-studio-code

$ brew cask outdated

Output of brew cask doctor
$ brew cask doctor
==> Homebrew-Cask Version
Homebrew-Cask 1.3.0-15-g2ad03b8
caskroom/homebrew-cask (git revision 43e55; last commit 2017-08-02)
==> Homebrew-Cask Install Location
<NONE>
==> Homebrew-Cask Staging Location
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads
~/Library/Caches/Homebrew/Cask (28 files, 2.2GB)
==> Homebrew-Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask (3670 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-drivers (107 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-eid (6 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-fonts (1107 casks)
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-versions (159 casks)
==> Contents of $LOAD_PATH
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib
/Library/Ruby/Gems/2.0.0/gems/psych-2.0.17/lib
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin15
/Library/Ruby/Site/2.0.0/universal-darwin15
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin15
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin15
==> Environment Variables
LC_ALL="en_US.UTF-8"
LC_CTYPE=""
PATH="/usr/local/bin:/usr/local/sbin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/Homebrew/Library/Homebrew/shims/scm"
SHELL="/bin/zsh"

Please post the output of brew cask outdated --greedy

Does this mean that it will display a list of software that is outdated?

No. It means (like it says) that it’ll show a list of outdated casks. I.e. it only knows if the version you installed is outdated in relation to the latest version we know about. Also, it does not check for casks that auto update themselves, unless you pass --greedy. That is all described in the man page, where we can be verbose. help is for quick reference only.

@commitay @vitorgalvao This is exactly what I was looking for. I must have missed it in the man pages. I guess I did not know exactly what I was looking for. Thank you.


Support for SKPaymentTransactionObserver

Hello,
As part of an IAP product submission into App Store, there is the option to include IAP promotion and feature it in the store. More details available via this link https://help.apple.com/app-store-connect/#/dev84b80958f.

Does RN IAP package implements or supports SKPaymentTransactionObserver?
Ty

Yes it looks like RNIapIos interface implements SKPaymentTransactionObserver.
And there's a FAQ describing how to use this: https://react-native-iap.dooboolab.com/docs/faq#how-do-i-handle-promoted-products-in-ios

Thank you for the reference @phillip-kic. Closing this issue


Unable to Access postgres.new

I have been trying for days to access postgres.new in my Chrome browser, and I have been getting this error in my browser:
This site can’t be reached
postgres.new took too long to respond.
Try:

Checking the connection
[Checking the proxy and the firewall](chrome-error://chromewebdata/#buttons)
[Running Windows Network Diagnostics](javascript:diagnoseErrors())
ERR_CONNECTION_TIMED_OUT

What do you suggest could be the cause? Thanks

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

What URL is this?

@Ifeanyi55 do not click that
this is a virus and I was tricked by it

Thanks!

Hey @Ifeanyi55 thanks for reporting. This is the first I've heard of this - just tried connecting and everything loads on my end. Can you confirm whether or not you are behind any firewalls that might prevent access?

Hi @gregnr , it now works from my end. Turns out my Internet connection was the culprit all along. Thanks!


Cleanup unused methods

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.3%) to 76.765%

Totals

Change from base Build<PHONE_NUMBER>:
0.3%

Covered Lines:
1566

Relevant Lines:
2040

💛  - Coveralls


Support for "multi lingual" versions of office

Hi,
I really like the approach and can help myself with the sourcecode but I would recommend that you make the text of the Window is configurable because the german versions title has the caption "1 Erinnerung(en)" instead of "1 Reminder(s)" and thus, your tool is not working.

Hey @schlaubstar v1.1.0 now has Advanced settings that allows you to specify the window title text to match against, so you should be able to adjust that for non-English Windows. I believe that should get you going :)


ReferenceError thrown on assigning to undeclared global in script file (as if in strict mode/module)

After 8cd59bf7c439e337 qjs throws ReferenceError for an undeclared global assignment in a script file.
Consider a js file with this code
a=1;console.log(typeof a);
This used to output "number" earlier but now without --script argument before the file path, an error is thrown.
ReferenceError: a is not defined
It seems the file is considered to be a module and strict mode is enforced if --script is not specified.
Shouldn't this work as it did before (raising the error only if strict mode is specified) ?

Yes, that would be a side effect of https://github.com/quickjs-ng/quickjs/pull/610
Honestly, I think thr current approach is better than before, as in, use modules by default unless we can detect otherwise.
@bnoordhuis I wonder if it would make sense to make the test "heavier" by checking twice, once as a script, once as a module and if both succeed, use module, otherwise pick the correct one. WDYT?

That won't work. a=1;console.log(typeof a); is not obviously a classic script or a module, it parses fine either way.
Editorial: that's why I wrote in the commit log that the premise of auto-detection is wrong - no matter what choices you make, it's always going to be wrong some of the time.

Ah, right. Shall we close this then?

Yes. Working as intended / as well as possible.


onSlide or currentSlideIndex aren't working

I need to change the slide index from 0 to 5 with the click of a card, but it doesn't seem to be working. Here is my code:
const Cards = ({ col, i, setIndex }) => {
  const { toggle } = useModal();
  return (

 {
        toggle('my-modal');
        setIndex(i);
      }}
      key={i}
    >
      ...content

  );
};

const SliderComponent = ({ myContent, sliderIndex }) => (

    <SliderProvider
      onSlide={sliderIndex}
      slidesToShow={1}
    >
      <SliderButton direction="prev">
        Prev
      </SliderButton>
      <SliderTrack>
        {
            myContent?.map(
              (col, i) => (
                <Slide
                  index={i}
                  className={classes.carousel_item}
                >
                  ..content
                </Slide>
              ),
            )
          }
      </SliderTrack>
      <SliderButton direction="next">
        Next
      </SliderButton>
    </SliderProvider>

);

export const Component: React.FC<Type> = ({
  myContent,
}) => {
  const [sliderIndex, setIndex] = useState(0);
  return (

      <ModalProvider transTime={250}>

          <ModalContainer />
          <Modal slug="my-modal">
            <SliderComponent
              myContent={myContent}
              sliderIndex={sliderIndex}
            />
          </Modal>

        <GridContainer>

            {myContent?.map((col, i) => (
              <Cards
                col={col}
                i={i}
                setIndex={(index) => setIndex(index)}
              />
            ))}

        </GridContainer>
      </ModalProvider>

  );
};

So when I am clicking on the card, it triggers the onclick function to open the modal and changes the slider index corresponding to the clicked card. But when the index is updated, the slide isn't changing. Any suggestions? Documentation doesn't have anything.
I double-checked that SliderComponent is getting the correct sliderIndex.

Hi @abhij89 this should be possible, but I do see a couple strange areas in your code. You shouldn't need to maintain sliderIndex, but instead, should read this from slider context. You can either use the useSlider hook or pass a child function to the slider provider like this:
<SliderProvider>
  {(sliderContext) => (
    ...
  )}
</SliderProvider>

The other strange part is that onSlide method on the sliderProvider is being used a prop. You should omit this line.
Lastly, set the new slide index using the goToSlideIndex method.
This should get you there, but let me know if you need more help!

@jacobsfletch thank you for the answer. I will definitely improve the code based on your suggestions. Though do you have any examples of how to use or call the goToSlideIndex method?

Here's a quick snippet based on your use case:
export const Card = ({ index }) => {
  const { goToSlideIndex } = useSlider();
  const { open: openModal } = useModal();

  return (

 {
        open('my-modal');
        goToSlideIndex(index);
      }}
    >
      {`This is card ${index + 1}`}

  )
}

I tried this, but it didn't work. I wrapped the card component inside of sliderProvider and then onClick I used this method goToSlideIndex(index); to change the index..it didn't change it when the modal was open it was still at index 0.

Here is my updated code..
const Cards = ({ col, i, setSliderIndex }) => {
  const { toggle } = useModal();
  const { goToSlideIndex, goToNextSlide } = useSlider();
  return (
    <div
      data-aos="fade-up"
      data-aos-once="true"
      data-aos-delay={`${i}00`}
      onClick={() => {
        setSliderIndex(i);
        toggle('my-modal');
        goToSlideIndex(7);
        goToNextSlide();
      }}
    >
      ..content

  );
};

const SliderComponent = ({ myContent, sliderIndex }) => {
  return (

    <SliderProvider
      onSlide={sliderIndex}
      slidesToShow={1}
    >
      <SliderButton direction="prev">
        Prev
      </SliderButton>
      <SliderTrack>
        {
            myContent?.map(
              (col, i) => (
                <Slide
                  index={i}
                  className={classes.carousel_item}
                >
                  ..content
                </Slide>
              ),
            )
          }
      </SliderTrack>
      <SliderButton direction="next">
        Next
      </SliderButton>
    </SliderProvider>

  );
};

export const Component: React.FC<Type> = ({
  myContent,
}) => {
  const [sliderIndex, setSliderIndex] = useState(0);
  return (

        Roadmap

      <ModalProvider transTime={250}>

          <ModalContainer />
          <Modal slug="my-modal">
            <SliderComponent
                roadmap={roadmap}
                sliderIndex={sliderIndex}
              />
          </Modal>

        <GridContainer>
          <SliderProvider>

              {myContent?.map((col, i) => (
                <Cards
                  col={col}
                  i={i}
                  setSliderIndex={(index) => setSliderIndex(index)}
                />
              ))}

          </SliderProvider>
        </GridContainer>
      </ModalProvider>

  );
};

export default Roadmap;

Yea it still isn't quite as I described. I went ahead and wrote this out for you:
const modalTransTime = 250;

const Card = ({ index }) => {
    const { goToSlideIndex } = useSlider();
    const { open: openModal } = useModal();

    return (

 {
                openModal('my-modal');
                setTimeout(() => {
                    goToSlideIndex(index);
                }, modalTransTime); // the modal has to open first
            }}
        >
            {`This is card ${index + 1}`}

    )
}

const SliderComponent = ({ myContent }) => {
  return (

        <SliderProvider slidesToShow={1}>
            <SliderButton direction="prev">
                Prev
            </SliderButton>
            <SliderTrack>
                {myContent?.map((content, i) => (
                    <Slide
                        index={i}
                        key={i}
                        className={classes.carousel_item}
                    >
                        <Card index={i}>
                            {...content}
                        </Card>
                    </Slide>
                ))}
            </SliderTrack>
            <SliderButton direction="next">
                Next
            </SliderButton>
        </SliderProvider>

  );
};

export const Component: React.FC<Type> = ({
  myContent,
}) => {

  return (

        Roadmap

      <ModalProvider transTime={modalTransTime}>

          <ModalContainer />
          <Modal slug="my-modal">
            <SliderComponent myContent={myContent} />
          </Modal>

        <GridContainer>
          <SliderComponent myContent={myContent} />
        </GridContainer>
      </ModalProvider>

  );
};

export default Roadmap;

@jacobsfletch yeah, I tried the timeout, but it didn't work. To make sure that setTimeout is working I added console.log in it and that worked fine and logged the message but function goToSlideIndex didn't work.

@abhij89 this should work, so something must be getting lost in implementation. If you can spin up CodeSandbox, I am more than happy to help get it in a working state for you there.

I can get you access to the repo which has the above code. @jacobsfletch is the username, right? Is it ok to send you an invite?

I would prefer a SandBox, this way your issue is isolated and I wouldn't have to spin up your app. The snippet above is 99% of the what is needed to make that happen. It should be pretty easy to set up, but if you're having troubles I might be able to do this for you at some point.

Hey @abhij89! I just published a new version with fixes to both currentSlideIndex props and the goToSlideIndex method. Go ahead and run yarn add<EMAIL_ADDRESS>and let me know if that helps you out.
I am also working on example sliders that I will publish to the website once ready. This will include various types of sliders along with their source code. This will help everyone tremendously.
Let me know how it goes with v1.1.5!

Hey @abhij89! As promised, here's a live working example.

@jacobsfletch source code link is wrong on the live working example page. You probably linked it with private repo instead of the public one, can you update that?

Thank you for the fix and updating the code. @jacobsfletch

@abhij89 good catch, got that linked fix up now 😄 . Give it another shot!

@jacobsfletch hey, I tried the example but it still didn't work, I have the same code as yours but it still doesn't change the index. I can see the currentSlideIndex changing for the slider inside the modal when clicking the slide of the slider outside but it still isn't scrolling to the right index..can you suggest why it would do that? I have the latest version.

Hi @abhij89 found the problem and published a v1.1.8 just now! Thank you for reporting that. Install that version, and all should be well. To make sure of this, I made this CodeSandbox. It's a live, working demo of a lightbox slider.
Hope this helps!!

@abhij89 ok wow v1.1.8 isn't quite there yet either, my apologies. I'm publishing another version shortly.

Finally!!!! It's working now. Thank you for fixing this. Appreciate it. @jacobsfletch

@abhij89 CodeSandbox appears to be slow in getting the latest version, so I went ahead and deployed the a similar example to the docs directly.

Thank you, I already tried locally and it works.


BUG

Searching for left and right hand controllers
left and right hands found
selecting default
Traceback (most recent call last):
File "open-vr-pad.py", line 6, in
steam_vr_wheel.wheel.main('pad')
File "C:\Users\NAME\Desktop\steam-vr-wheel-master\steam_vr_wheel_dist\steam_
vr_wheel\wheel.py", line 132, in main
do_work(vrsystem, left_controller, right_controller, wheel, poses)
File "C:\Users\NAME\Desktop\steam-vr-wheel-master\steam_vr_wheel_dist\steam_
vr_wheel\wheel.py", line 26, in do_work
left_controller.update(poses[left_controller.id.value])
File "C:\Users\NAME\Desktop\steam-vr-wheel-master\steam_vr_wheel_dist\steam_
vr_wheel\vrcontroller.py", line 32, in update
self.yaw = 180 / math.pi * math.atan(pose_mat[1][0] / pose_mat[0][0])
ZeroDivisionError: float division by zero

fixed in 2.5.0-alpha3 - Oculus has some problems with pose rotation?


Penalty for reopened issues

There is an issue for which we had to pay twice because it was not correctly implemented for the 1st time. Here is how it happened. While proper QA eliminates such cases we should also add a penalty for a bounty hunter.
What should be done:

If issue is reopened and permit was earlier generated then subtract "penalized" issue reward from the next bounty hunter's solved issue (if there is one). Penalty should only be applied within the repository where the original issue is reopened.
The bot should post a "penalty" message on issue reopening event:

"@user please be sure to review this conversation and implement any necessary fixes. Unless this is closed as completed, its payment of XXX USD will be deducted from your next bounty."

Could you propose architecture for this?
For example, at the time of new payment permit generation, we need to check:

the issues that bounty hunter is assigned to
If any of those have been reopened
The permit amount

If we communicate the debit ONLY at the time of payment permit generation, due to mismatched expectations (they see the bounty price being much higher than what they actually receive) the bounty hunter can be upset/disappointed and quit.
Is there a clearer way to manage expectations before they get to complete the second bounty?

Could you propose architecture for this?
For example, at the time of new payment permit generation, we need to check:

the issues that bounty hunter is assigned to (what if they un assign themselves after it's been reopened?)
If any of those have been reopened
The permit amount

If we communicate the debit ONLY at the time of payment permit generation, due to mismatched expectations (they see the bounty price being much higher than what they actually receive) the bounty hunter can be upset/disappointed and quit.
Is there a clearer way to manage expectations before they get to complete the second bounty?

I actually thought that this "penalty" data could be written to a DB. This way we don't need to parse all the issues on permit generation.
So if an issue is reopened then:

Find permit comment
Find the latest assignment before the permit generation
Save bounty hunter's id, penalty amount, issue id
On some other permit generation apply the penalty

This schema is cross-repo so it is possible to get a penalty in one repo but have it applied in another one.

Is there a clearer way to manage expectations before they get to complete the second bounty?

We can soften the penalty a little bit, for example by applying a rule "penalize not more than 50% of a bounty reward"

the bounty hunter can be upset/disappointed

And we are upset because the previously implemented issue didn't match the spec

And we are upset because the previously implemented issue didn't match the spec

lol
Here's an idea for a new flow:

An issue is re-opened due to unsatisfactory work.
At this moment, if the bounty hunter is working on another issue, the bot will immediately post a warning comment. For example:

"@user a prior task you worked on, #9876, has been re-opened. Please be sure to review its conversation and implement any necessary fixes. Until that issue is closed again, a penalty of that issue amount will be included in your next payment."

I kind of like the idea of isolating repositories (or at least organizations) for this because what if the review board of one repository (or organization) is not competent?

Ok, so we need to keep a penalty in boundaries of a single repo.

At this moment, if the bounty hunter is working on another issue, the bot will immediately post a warning comment

We could post this penalty warning message in the reopened issue. So if issue is reopened then post smth like:

"@user this task has been reopened. Please be sure to review its conversation and implement any necessary fixes. Until this issue is closed again, a penalty of this issue amount will be included in your next payment."

"@user please be sure to review this conversation and implement any necessary fixes. Unless this is closed as completed, its reward of XXX USD will be debited from your next payment."

"@user please be sure to review this conversation and implement any necessary fixes. Unless this is closed as completed, its payment of XXX USD will be debited from your next bounty."

Updated description

If the second bounty is smaller than the first bounty we won't be made whole by the way.

If the second bounty is smaller than the first bounty we won't be made whole by the way

Then we will be made whole on the next bounty

This approach is "optimistic" but if we do "pessimistic" then we can automatically issue only e.g. half the bounty up front and if its not re-opened within a e.g. week then issue the second half payment permit.

This complicates payouts because we would somehow need to maintain 2 unique nonces per a single issue. Anyway proper QA eliminates most of poor PRs so I would not split payouts.

/assign

What about a situation where an issue is reopened but in the mean time the bounty hunter completes another issue and gets a penalty but after that fixes the reopened issue.
I guess the warning solves this to some extent by warning the user not to finish other bounties before fixing the reopened issue.

where an issue is reopened but in the mean time the bounty hunter completes another issue and gets a penalty but after that fixes the reopened issue

Good catch. So if a bounty hunter solves another issue and the penalty is applied then there is no incentive for a bounty hunter to solve a reopened issue.
Perhaps we should apply a progressive penalty rate (like -10% reward for each reopened issue) on all solved bounties in the future until all reopened issues are solved.
@pavlovcik what do you think?

Also what if the payment token has changed? How do we calculate the penalty on new permit generation with new token?

Also what if the payment token has changed? How do we calculate the penalty on new permit generation with new token?

I guess payment tokens are always(?) USD pegged so it doesn't really matter which token to use for penalty calculation, DAI or WXDAI.

So the penalty should be written in database and restricted to one repo?

So the penalty should be written in database

yes, unless there is a way to save it somehow in github comments

restricted to one repo?

yes

where an issue is reopened but in the mean time the bounty hunter completes another issue and gets a penalty but after that fixes the reopened issue

Good catch. So if a bounty hunter solves another issue and the penalty is applied then there is no incentive for a bounty hunter to solve a reopened issue.

Economically, I think that the partner is made whole (they are paid back for non-performance) so it doesn't matter. Let's continue with the original specification.

The delays are on us. We should help get @Venoox work merged in asap can you guys help @ubiquity/development

@ubiquity/software-development has anybody seen this debt system work in production? I have not once seen it.

I haven't seen such cases yet. Perhaps that's because the bot's core team is fixing things all the time without reopening issues because it is simpler to fix the bug themselves compared to finding the root cause PR and waiting for a fix from a bounty hunter.

Issues can certainly be opened retroactively. I've done it a few times.
I suspect that the debt system doesn't work because in our current implementation: even if worker A had their issue re-opened, and B fixed it; A should still have debt for their next bounty.

Found one https://github.com/ubiquity/ubiquibot/issues/680#issuecomment-1715253580

@ubiquity/software-development has anybody seen this debt system work in production? I have not once seen it.

yes during the test in ubiquibot/production


⚠ Bofrost.de has degraded performance

In 4635ddf, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1511 ms

Resolved: Bofrost.de performance has improved in 9a6d1eb after 9 minutes.


Create delete_chats_of_all_contacts() in contacts.py

do as follow

go through all contacts chats same as in exit_from_all_groups()
NOTE: by using CONTACTS__NAME_IN_CHATS  you can get all chats of contacts.
open chat options by using CHATROOM__OPTIONS
press on Delete chat and wait for the chat to be deleted by using self._close_info()

can I work on this? I will submit PR soon


Add more sophisticated and through specs

Currently the specs doesn't verify the request of the client.

Done by https://github.com/dtaniwaki/akka-pusher/pull/16


Change md/geom parsing to frame function for easier use.

Fix issue with reading all frames of MD/Geom files
Add a function to parse a single frame of an MD calculation from a block enabling generator approaches.
Makes Block.__bool__ verify it contains non-whitespace data.

I think if curr and curr["ions"] is the only thing left, now


Reset recurring task completion state per schedule instead of everyday

Fixes #74 to only reset count / completion state for recurrent tasks when they are done and it's time for the next iteration per the recurrent schedule.
I've tested all combinations manually, but if there's a place where I can add unit tests or if I there are specific steps I should follow to test thoroughly, happy to do so!
Thank you!

Makes sense. Thanks.

This doesn't look right: I didn't run this code, but I installed the new version and it seems to change how recurring (non-count) items to not have overdue tag anymore:

I've reverted this commit: https://github.com/usernamehw/vscode-todo-md/commit/62f278390dda22f54314057b62782bcaeb039137
If you want - you can make another PR, but with a minimal change (no refactoring - I know that code I wrote is terrible and it doesn't have tests / and it should ONLY affect tasks that have {count:...} tag, not all tasks.

A lot of this logic, as has been before, is dependent on the lastVisit state. In my tests, I had to manually hardcode to a few values to test different scenarios. Would the test above mock that correctly that as well?

This extension doesn't support a "defer" https://github.com/usernamehw/vscode-todo-md/issues/60 or "schedule" https://github.com/usernamehw/vscode-todo-md/issues/59 (seems to be the same issue).
When you make a recurring due date - extension expects you to complete it at EXACT date, like:
🧹 Vacuum the floor {due:2023-08-05|e5d}

It doesn't mean that you can do it at any day - before or after, but at one specific day only. If you fail to do the task on the day it was due - it should transform into overdue.

Also, screenshots don't show "lastVisit" state. That's from a different extension - it simply displays current/today's date.


Homebridge Hue Accessories Keep Failing to Default Room

Hi there
Over the last few days my Homebridge Hue accessories have moved to Default Room several times.
Previously I thought this was to do with Homebridge Hue starting before Phoscon had, but I have the lightlink resource in place.  Other than that I've not changed anything.  I'm not restarting Phoson either.
Any thoughts?
Thanks

homebridge-hue.json.gz

Just happened again.  It seems to be a common occurrence that coincides with all my 2.4GHz accessories going offline at the same time whereas my 5GHz wifi stays connected.
Sadly, once everything reconnects it seems Homebridge-Hue and deconz get muddled.  Homebridge is showing updates from all my deconz-attached devices, but they disappear completely from HomeKit.  Restarting Homebridge brings them back, but by then all the config has been lost and they appear back in Default Room.

Accessories exposed by Homebridge Hue cannot disappear from HomeKit, unless  Homebridge restarts.  If the network between HomeKit and Homebridge fails, accessories show as Not Responding, but don't disappear.
Your lightlist resourcelink only contains a single /lights resource.  You might need to update it (by running ph lightest again, after deCONZ has re-exposed all /lights resources).  Are you only losing lights (and plugs), or also sensors and switches?
The lights and plugs would disappear when Homebridge starts before, or quickly after deCONZ.

Thanks for the reply.  When I say that everything disappears from HomeKit, it really does - there's no Default Room yet all my sensors have gone from their allocated rooms and are nowhere to be found.  Homebridge looks to be running, but when I restart it, the devices come back and at the same time Default Room reappears with them all in it.
In terms of what disappears, it's everything: bulbs, smart plugs, buttons, a single leak sensor and about 14 temperature sensors.😊 Most frustrating is that the smart buttons disappear and then need to be reconfigured each time.
I did have a more expansive lightlist but this caused Homebridge-Hue to completely stop Homebridge on startup so I trimmed it back to just the one light.  I really use Homebridge-Hue for my Xiaomi/Aqara devices more than  for lights, although I do have two Zigbee bulbs configured.

I did have a more expansive lightlist but this caused Homebridge-Hue to completely stop Homebridge on startup

That would be the case if the lightlist still contains a deleted a light.  deCONZ doesn't update the resourcelinks when resources are deleted.

In terms of what disappears, it's everything: bulbs, smart plugs, buttons, a single leak sensor and about 14 temperature sensors

The only way (I can think of) that this would happen is when you somehow manage to start Homebridge without Homebridge Hue enabled.  Are you sure you have only one installation of Homebridge, and only one user directory (with config.json)?
If you're using Docker, make sure the user directory is persisted across restarts.  If you're on a Raspberry Pi, check the filesystem on the uSD card.

That would be the case if the lightlist still contains a deleted a light. deCONZ doesn't update the resourcelinks when resources are deleted.

That did happen once, but that was a long time ago when I had more bulbs in use.  Since then I've trimmed it back to just this one which is always powered.

The only way (I can think of) that this would happen is when you somehow manage to start Homebridge without Homebridge Hue enabled. Are you sure you have only one installation of Homebridge, and only one user directory (with config.json)?

If you're using Docker, make sure the user directory is persisted across restarts. If you're on a Raspberry Pi, check the filesystem on the uSD card.

I'm using the official Homebridge image running directly on a RPi 3.  No Docker.  I'm deliberately keeping my setup as simple as possible to try to avoid these types of issues.  For info as well, deCONZ is running on a different Pi with a USB Conbee 2 stick attached (on a USB extension cable).  Both Pi have static IP addresses, although they can be accessed via DNS as well of course. 😄

I would need to see a debug log file from the moment Homebridge starts up to where the accessories disappear.  Best enable debug in the Homebridge UI and download the log file from the UI.

I too have this problem.  Thought I had cracked it with some updating but alas exactly the same story as this.   I have extensive bulbs and xiaomi sensors connected through a usb Conbee stick.   All sensors and bulbs working correctly in the homebridge UI - just disappear from home app (restart brings them back but they fall to default and you lose assignments and button configs).

I too have this problem.  Thought I had cracked it with some updating but alas exactly the same story as this.   I have extensive bulbs and xiaomi sensors connected through a usb Conbee stick.   All sensors and bulbs working correctly in the homebridge UI - just disappear from home app (restart brings them back but they fall to default and you lose assignments and button configs).

I share your pain but I'm kind of glad it's not just me!

I would need to see a debug log file from the moment Homebridge starts up to where the accessories disappear.  Best enable debug in the Homebridge UI and download the log file from the UI.

Will do.  I will try to see if there's anything else I can check as well.  It does seem to follow the same pattern where everything (not just Homebridge devices) connected to 2.4GHz WiFi lose connectivity while anything on 5GHz keeps working.  I've only noticed this recently as I separated the two networks not long ago and now only my home automation stuff is on 2.4GHz.

I have the same issue with device falling back to the default room. All devices (Phillips Dimmer and Osram Smart Plugs) connected to the RaspBee II. Running on a Pi4 both deconz and homebridge running in Docker containers as provided by the links from the respective homepages. I did not reboot.. (though I need to check if the Pi did. by itself.. unlikely though.. this happened 3 times now) The devices vanished from their rooms after a few hours uptime. The dimmers also „forgot“ the scenes I assigned in the Eve HomeKit app. I‘ll check the documentation and see how I can create a dump and a log..

These "me too" comments are not helpful.  Please provide a debug log file from the moment Homebridge starts to the moment the accessories disappear.  Without proper logs there's nothing I can do, and I will close this issue.
As I said before, technically, Homebridge Hue cannot make accessories disappear.  They can disappear only when Homebridge (re-)starts without Homebridge Hue exposing the accessories.  This is a known issue with deCONZ, not exposing the /lights resources after it starts.  For this issue the lightlist workaround is available.  If you have multiple bridges/gateways, make sure to use fixed IP addresses and list them under hosts in config.json, as Homebridge Hue might still allow Homebridge to start when it only discovers one bridge/gateway.
If all your Homebridge accessories disappear, including those exposed by other plugins, the issue is not related to Homebridge Hue.  If you only have one bridge/gateway or listed all of them under hosts and your sensors also disappear, the issue is probably not related to Homebridge Hue either.

mhh. deconz did not restart when this happened. Today I just re-added a dimmer and a plug from the default room  to my living room again. Within one hour  they disappeared again. This time completely, together with all devices attached to raspbee that showed up in the default room before. Eve reported "no devices available" on the homebridge. But they re-appeared in the default room after restarting homebridge (leaving deconz untouched).
I don't see anything unusual in the logfile (see attachment). Though I don't know what to look for, either :-/
I am not using IP addresses in the configuration but DNS names... but a good tip to make sure they are fixed .
homebridge.log

There's something funny with your Homebridge installation.  The first time it seems to start using a different setting, not including Homebridge Hue.  This causes your Homebridge Hue accessories to disappear.
[11/17/2020, 4:37:28 PM] [HB Supervisor] Adding missing UI platform block to /homebridge/config.json
[11/17/2020, 4:37:28 PM] [HB Supervisor] OS: Linux 5.4.72-v7l+ arm
[11/17/2020, 4:37:28 PM] [HB Supervisor] Node.js v14.15.0 /usr/local/bin/node
[11/17/2020, 4:37:28 PM] [HB Supervisor] Homebridge Path: /usr/local/lib/node_modules/homebridge/bin/homebridge
[11/17/2020, 4:37:28 PM] [HB Supervisor] UI Path: /usr/local/lib/node_modules/homebridge-config-ui-x/dist/bin/standalone.js
[11/17/2020, 4:37:28 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /homebridge/node_modules
[11/17/2020, 4:37:28 PM] [HB Supervisor] Started Homebridge v1.2.3 with PID: 408
[11/17/2020, 4:37:29 PM] Loaded config.json with 0 accessories and 1 platforms.
```
On subsequent startups, Homebridge Hue is loaded, causing your accessories to re-appear, but with HomeKit treating them as new accessories.

[11/17/2020, 5:18:02 PM] [HB Supervisor] Restarting Homebridge...
[11/17/2020, 5:18:02 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /homebridge/node_modules
[11/17/2020, 5:18:02 PM] [HB Supervisor] Started Homebridge v1.2.3 with PID: 754
[11/17/2020, 5:18:03 PM] Loaded config.json with 0 accessories and 2 platforms.
[11/17/2020, 5:18:03 PM] ---
[11/17/2020, 5:18:05 PM] Loaded plugin<EMAIL_ADDRESS>[11/17/2020, 5:18:05 PM] Registering accessory 'homebridge-dummy.DummySwitch'
[11/17/2020, 5:18:05 PM] ---
[11/17/2020, 5:18:08 PM] Loaded plugin<EMAIL_ADDRESS>[11/17/2020, 5:18:08 PM] Registering platform 'homebridge-hue.Hue'
[11/17/2020, 5:18:08 PM] ---
[11/17/2020, 5:18:08 PM] Loaded plugin<EMAIL_ADDRESS>[11/17/2020, 5:18:08 PM] Registering platform 'homebridge-config-ui-x.config'
[11/17/2020, 5:18:08 PM] ---
[11/17/2020, 5:18:08 PM] Loading 2 platforms...
[11/17/2020, 5:18:08 PM] [Config] Initializing config platform...
[11/17/2020, 5:18:08 PM] [Config] Running in Service Mode
[11/17/2020, 5:18:08 PM] [Hue] Initializing Hue platform...
Here something fishy happens:

[11/17/2020, 7:54:41 PM] [Hue] Phoscon-GW: gateway request 78: get /sensors
[11/17/2020, 7:54:41 PM] [Hue] Phoscon-GW: gateway communication error: <IP_ADDRESS>:80: cannot connect: ECONNREFUSED
[11/17/2020, 7:54:41 PM] [Hue] Phoscon-GW: heartbeat error: <IP_ADDRESS>:80: cannot connect: ECONNREFUSED
Homebridge Hue can no longer reach deCONZ.  Note the IP address: `<IP_ADDRESS>` instead of `<IP_ADDRESS>`.  WTF?!

When Homebridge Hue re-connects, deCONZ no longer accepts the API key:

[11/17/2020, 7:54:51 PM] [Hue] Phoscon-GW: gateway request 80: get /sensors
[11/17/2020, 7:54:51 PM] [Hue] Phoscon-GW: gateway request 80: error 1 unauthorized user
Next, you restart Homebridge, but on restart, deCONZ still doesn't accept the API key.  Apparently this hits a bug in Homebridge Hue, causing it to allow Homebridge to start without exposing any Hue accessories, causing them to be removed by HomeKit.

[11/17/2020, 7:56:52 PM] [HB Supervisor] Restarting Homebridge...
[11/17/2020, 7:56:52 PM] [HB Supervisor] Starting Homebridge with extra flags: -I -P /homebridge/node_modules
[11/17/2020, 7:56:52 PM] [HB Supervisor] Started Homebridge v1.2.3 with PID: 2698
[11/17/2020, 7:56:53 PM] Loaded config.json with 0 accessories and 2 platforms.
[11/17/2020, 7:56:53 PM] ---
[11/17/2020, 7:56:54 PM] Loaded plugin<EMAIL_ADDRESS>[11/17/2020, 7:56:54 PM] Registering accessory 'homebridge-dummy.DummySwitch'
[11/17/2020, 7:56:54 PM] ---
[11/17/2020, 7:56:56 PM] Loaded plugin<EMAIL_ADDRESS>[11/17/2020, 7:56:56 PM] Registering platform 'homebridge-hue.Hue'
[11/17/2020, 7:56:56 PM] ---
[11/17/2020, 7:56:56 PM] Loaded plugin<EMAIL_ADDRESS>[11/17/2020, 7:56:56 PM] Registering platform 'homebridge-config-ui-x.config'
[11/17/2020, 7:56:56 PM] ---
[11/17/2020, 7:56:56 PM] Loading 2 platforms...
[11/17/2020, 7:56:56 PM] [Config] Initializing config platform...
[11/17/2020, 7:56:56 PM] [Config] Running in Service Mode
[11/17/2020, 7:56:56 PM] [Hue] Initializing Hue platform...
[11/17/2020, 7:56:56 PM] [Hue] homebridge-hue v0.12.0, node v14.15.0, homebridge v1.2.3
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: dresden elektronik deCONZ gateway v2.5.88, api v1.16.0
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: warning: not using recommended deCONZ gateway version 2.5.84
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: gateway request 1: get /
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: gateway request 1: error 1 unauthorized user
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: gateway request 2: get /groups/0
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: gateway request 2: error 1 unauthorized user
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: TypeError: Cannot set property '0' of undefined
at HueBridge.getFullState (/homebridge/node_modules/homebridge-hue/lib/HueBridge.js:330:19)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at HueBridge.accessories (/homebridge/node_modules/homebridge-hue/lib/HueBridge.js:102:19)
at async Promise.all (index 0)
at HuePlatform.accessories (/homebridge/node_modules/homebridge-hue/lib/HuePlatform.js:308:29)
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: 1 accessories
[11/17/2020, 7:56:56 PM] [Hue] masked debug info dumped to /homebridge/homebridge-hue.json.gz
[11/17/2020, 7:56:56 PM] Initializing platform accessory 'Phoscon-GW'...
[11/17/2020, 7:56:56 PM] [Hue] Phoscon-GW: 2 services
I think you removed the API key from config.json and restarted Homebridge, after which Homebridge Hue created a new key, continuing to work normally, re-exposing the accessories, which Homebridge once again treats as new accessories.  Subsequent restarts seem to work normally.

Luckily, you enabled debug mode later, which causes Homebridge Hue to log the Hue section in config.json:

[11/20/2020, 12:22:18 PM] [Hue] config.json: {"name":"Hue","anyOn":true,"hosts":["pi4"],"lights":true,"nativeHomeKitLights":true,"nativeHomeKitSensors":true,"nupnp":true,"resource":true,"sensors":true,"users":{"00212EFFFF061CBA":"*********1"},"platform":"Hue"}
You specify the host as `pi4`.  I don't know how that's resolved into `<IP_ADDRESS>`, but I would specify `<IP_ADDRESS>` in config.json to insulate against any resolver issues.

I have the same issue, I believe it's related to: https://github.com/ebaauw/homebridge-hue/issues/802
And https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2473 as you've previously mentioned @ebaauw

That's a different issue @simplenotezy.  Different symptoms (only lights are effected) and different cause.

Please don't close this ticket.  I will get my debit logs over as well.

Thank you for taking so much time... I think what you saw in the log files are my attempts to make a fresh start and setting up deconz and homebridge anew.. The event when the accessories disappeared happened later.. (without me fuzzing around).
I try to better track when the incident occurs next time... :-/
I am glad, that this uncovered an edge case in the startup process ;-). Maybe that could help making the startup more robust. Actually that inspired me to manually delete the api key from the deconz API to see if that might help provoke and reproduce the issue which it did... well no surprise.
I could recover from the situation by removing the "hue" platform from the config.. But then of course the devices show up as new devices. It might be a silly question, but I wonder, why the devices are re-exposed as new devices and homekit does not recognize them as the ones it has seen before. I mean, the devices have unique ids...  Is that a limitation of homebridge?
The weird IP address actually seem to be pretty normal on Debian based systems (https://askubuntu.com/questions/754213/what-is-difference-between-localhost-address-127-0-0-1-and-127-0-1-1). And it's defined in the /etc/hosts.. But it doesn't harm using <IP_ADDRESS> in homebridge-hue, i guess.

thank you :-)

@ackoch I do have native Hue as well, but so far as I'm aware that's all completely separate from HomeBridge.
My HoneBridge-Hue config only points to my Conbee2 stick, not to the Hue bridge.
As an aside, my Pi crashed this morning so I've reinstalled and restored from backup and will monitor how things go.

HomeKit is perfectly happy to have the same device exposed by the Hue bridge and by Homebridge Hue.  It sees them as separate accessories, because they are bridged by separate HomeKit bridges.  You can even expose the same devices twice using different Homebridge instances, each with the Homebridge Hue plugin.  Eve might get confused as it stores the history under the accessory UUID, without considering the HomeKit bridge, but the Hue bridge doesn’t expose Eve history, so no harm there.
If Homebridge Hue exposes multiple bridges and/or gateways from one Homebridge instance, make sure to delete the device from the old bridge/gateway before adding it to the other.  If you don’t, you’ll be treated to a “cannot add another accessory with the same UUID” error.  By design Homebridge Hue generates the accessory UUID from the Zigbee mac address, so your HomeKit configuration is preserved when deleting and re-pairing the device, and when moving the device from one bridge/gateway to another.

Just noticed a crash of sorts, but it hasn't affected my HomeKit setup this time so only posting if the below helps, or makes sense at all.  Chunk of log follows.  There are two ETIMEDOUTs, then suddenly HomeBridge is sent a SIGTERM, but I didn't initiate this, is it possible for something else to be doing that?
What happens next is HomeBridge restarts, the Nest plugin gets unhappy, HomeBridge restarts again and everything settles back down.  Looking at the web console, the Pi and Process uptimes both still read as 6 hours and running uptime via the console confirms that.
I can post the rest of the log if it helps.  Timestamps are UK (GMT):
22/11/2020, 13:48:29] [deCONZ] Study Bookcase: set homekit humidity from 68% to 67%
[22/11/2020, 13:48:51] Error: read ETIMEDOUT
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
[22/11/2020, 13:48:51] Error: read ETIMEDOUT
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
[22/11/2020, 13:48:51] Got SIGTERM, shutting down Homebridge...
[22/11/2020, 13:48:51] [Apple TV Platform] Shutting down Apple TV clients...
[22/11/2020, 13:48:51] Error: read ETIMEDOUT
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
[22/11/2020, 13:48:54] [Homebridge UI] Terminal session ended.
[22/11/2020, 13:48:55] Error: read ETIMEDOUT
    at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
[22/11/2020, 13:48:56] [deCONZ] goodbye
[22/11/2020, 13:49:02] [HB Supervisor] Homebridge Process Ended.

Homebridge sends itself a SIGTERM in case of a non-recoverable error (typically an unchecked error by a plugin) to do a clean shutdown.  Unfortunately, the log gives no clue as to what is timing out, and which plugin should have handled that error.

Thanks - I did wonder if it was HomeBridge-Hue as that was what immediately preceded the SIGTERM, but that's just a guess.  I'll have a go disabling all plugins except one and see if I can narrow down which is the culprit.

v0.12.1 now stops Homebridge's HAP server from starting when full bridge state cannot be loaded.

Installed 0.12.2 last night.  Also uninstalled Apple-TV-Remote plugin as I no longer use it.
One observation is that my Samsung SmartThings Plug was renamed to "Power 35" in the Home app (original name 'showed through' if I deleted the HomeKit name).  My other Zigbee plugs were left unaltered.
All my HomeBridge accessories went to "no response" for about 30 seconds but then recovered.  As of 09:03 the HomeBridge logs look healthy - will continue to monitor. 👍🏼

There seems to be an issue with renaming smart plugs, see #826.

@fullphat out of interest - how is your pi connected to network.   I normally have mine connected to a mesh router via ethernet cable - this is then connected to the main router via wifi - I can't be sure yet, but have noticed that the issue appears to happen when the mesh router loses connection to the main router briefly.
I have now connected Pi to main router and restarted - will report back if this makes a difference.
I have also started in debug mode so will provide this if helpful @ebaauw

Issues with your network topology tend to result in Not Responding accessories, because the Bonjour announcements by Homebridge no longer reach your iDevice.  Losing (and re-exposing) Homebridge Hue accessories is only possible technically, when Homebridge restarts.

Since today same problem for me too. Devices keep disappearing in Homekit after a short while after a Homebridge reboot. Only 2 Homebridge Delay Switches remain.
homebridge.log

What devices by which plugin(s) are disappearing?
The first part of the log file, right after starting Homebridge is missing.  You seem to have a Hue bridge and a Phoscon gateway, but other than the bridge accessory, you're not exposing anything connected to the Hue bridge?  Did you specify deCONZ' IP address under hosts in config.json?

Indeed not exposing anything connected to the Hue bridge, I have connected the Hue bridge directly to Homekit. If now added the DeCONZ IP:port in the config.json and removed the Hue username. Same result, everything but the delay switches is removed:

Ikea plug and motion sensor
hue light and dimmer
Aqara sensors: temp, button, vibration, door, light

homebridge.log

It seems that an old iPad running iOS9 which was turned off for months and turned on yesterday again, was causing the problem. After disabling the Homekit iCloud sync on this device, the situation is stable again. So far so good.
Next thing is to put all the automations back in place.....
Thanks for the support.

Using different iOS/tvOS/... version on the same HomeKit home is generally a bad idea.  There used to be issues where HomeKit configuration changes wouldn’t sync well between devices, causing changes to be reversed automagically.  One of the nastiest effects was that automations wouldn’t sync to the home hub, and therefore wouldn’t run.  Haven’t seen those issues for a long time; but so is iOS9.

Interestingly I too have an old iPad mini running iOS9 as a baby monitor - this had HomeKit enabled in settings (didn’t realise iOS9 even had HomeKit) - I have now turned this off, will monitor.

@fullphat out of interest - how is your pi connected to network.   I normally have mine connected to a mesh router via ethernet cable - this is then connected to the main router via wifi - I can't be sure yet, but have noticed that the issue appears to happen when the mesh router loses connection to the main router briefly.
I have now connected Pi to main router and restarted - will report back if this makes a difference.
I have also started in debug mode so will provide this if helpful @ebaauw
Update: it didn't change anything :(  Will get logs and post

Sorry for the delay: both Pis are via WiFi (2.4GHz) with static IP addresses.  I've amended the hosts files on each to point to each other directly rather than rely on my Sky router.
I have no mesh network - the broadband router acts as gateway/wan router/firewall/DHCP server.

As OP, just a quick update from me to say that - so far - things have been stable.
What I've done:

Removed Apple-TV-Remote Homebridge plugin as I no longer use it

Updated to Homebridge-Hue 0.12.2

Moved kids' iPads to use 5GHz WiFi

Amended lightlist is deCONZ to include smart plugs as well as lights

Some of the above may have resolved my issue, or maybe I've just been lucky 😊 but I've not had any Homebridge crashes recently, which seem to be the start of the wider problem.

Update from my side... My setup was stable for a while. But I wanted to test some hypotheses of what might happen based on the model I made of my network.. And I could provoke a little bit of what I saw happening..
My setup (basically)

Hue and deCONZ+HB Hue connected individually to HomeKit.
I.e. HomeBridge Hue is not aware of the native Hue Bridge ... they are connected through HomeKit
I have both the Hue App and the Eve App running on my phone

See diagram for a graphical representation.
Now,
a) In Hue, I changed the name of "Living Room" to "Living Room X" - The change was visible immediately in Eve. But: All devices from HomeBridge were now moved to the default room. The devices connected to the Hue bridge remain in the assigned room.
b) I have a few "mixed" scenes, that turn on lights from both bridges.. These scenes stop working.
c) In Eve, I changed "Bedroom" to "Bedroom Y" - the change appears after a few minutes on my other iDevices... but not in the Hue App. I remember, that sometimes I see Hue notifying me, that it needs to resync -  but not this time.
So - here is my hypotheses:

The Hue app synchronizes the full room configuration to HomeKit with all devices it knows (deleting the devices connected to deCONZ that it does not know)..

The Hue app is polling the status of HomeKit for new room configurations only once in a while and may run out of sync in between.

So .. in my mental model, It's the Hue app messing with the status. My other iPhone seems to synchronise quite fast on changes I make..
@fullphat: My understanding is, that HomeKit is running on my phone(s) and the phones synch over the iCloud (or my appleTV?) .. s that correct?
In contrast, it seems that the Hue Bridge seems to store it's own version of the configuration in the bridge (and partly as a copy in the app)...
I am thinking of either

delete all rooms in the hue app. delete all instances of the hue app on all devices. reconfigure in Eve from scratch..

remove the HomeKit connection in the Hue App and route the Hue Bridge through HomeBridge Hue.

retire the Hue bridge completely and connecting all bulbs to deCONZ.. Only I will miss the slow wakeup-routine in the morning... But I have already found the article on using the "timer service".. maybe that substitutes

In Hue, I changed the name of "Living Room" to "Living Room X" - The change was visible immediately in Eve. But: All devices from HomeBridge were now moved to the default room. The devices connected to the Hue bridge remain in the assigned room.

Do you mean: you changed the name of the Room group on the Hue bridge (using the Hue app, or something)?  And that change was reflected in Eve how?
When you say "all devices from Homebridge", does that include accessories for /sensors resources?  And from other plugins than Homebridge Hue?

I have a few "mixed" scenes, that turn on lights from both bridges.. These scenes stop working.

HomeKit scenes?  What do you mean by "stop working"?  The Homebridge accessories are no longer controlled by the scene or all accessories, Homebridge and Hue bridge are no longer controlled by the scene?

So .. in my mental model, It's the Hue app messing with the status. My other iPhone seems to synchronise quite fast on changes I make..

The Hue app does sync Hue bridge rooms, groups, scenes, with their HomeKit equivalent.  I think that's configurable in the app.  It should only mess with HomeKit accessories exposed by the Hue bridge, afaik.
Note that the Hue bridge, like any HomeKit accessory, incl. Homebridge, has no clue about HomeKit rooms, groups, scenes, and automations.  These are visible only to HomeKit apps (incl. the Hue app).  Was the Hue app active (or did you change the room using the Hue app)?

The Hue app synchronizes the full room configuration to HomeKit with all devices it knows (deleting the devices connected to deCONZ that it does not know)..

I would theorise that the Hue app deleted and re-created the HomeKit room, causing the accessories in it to revert to the default room.  Would be interesting to see if native non-Hue HomeKit accessories would be effected as well.

My understanding is, that HomeKit is running on my phone(s) and the phones synch over the iCloud (or my appleTV?) .. s that correct?

Each device running HomeKit communicates with WiFi accessories directly.  The HomeKit config is synced between devices, incl. your home hub over iCloud.  If HomeKit cannot connect to an accessory (not in Home Wifi; out of bluetooth range) it will connect to the home hub over iCloud.

In contrast, it seems that the Hue Bridge seems to store it's own version of the configuration in the bridge (and partly as a copy in the app)...

The is no "the configuration".  The Hue bridge (as well as deCONZ) has its own set of Zigbee groups, scenes, rules; HomeKit has its own set of rooms, zones, groups, scenes, automations.  As I said before: HomeKit accessories cannot see nor access these.  The Hue app is both a HomeKit client as well as a Hue API client, and syncs the two configurations (or tries to).

I am thinking of either

I think it might be enough to deny the Hue app access to HomeKit, so it can no longer mess with the HomeKit rooms, etc.  That should be independent from exposing accessories natively by the Hue bridge.
I only use my Hue bridge for testing and reverse engineering (e.g. the adaptive lighting stuff).  I rarely use the Hue app, and I never let it sync rooms, etc.  I've never encountered anything like you described.

As an update.   It’s now 4 days since I turned HomeKit off on the old iOS 9 iPad - all seems well and stable.

@davidjforsyth My Homebridge was updated 3-4 days ago, and it got rebooted in the weekend, but I lost all lights, again..
What do you mean by turning off HomeKit?

Losing all lights is a symptom of https://github.com/dresden-elektronik/deconz-rest-plugin/issues/2473.  See https://github.com/ebaauw/homebridge-hue/issues/246 for a workaround.  If you have multiple gateways (or bridges), be sure to assign them fixed IP addresses and list them in config.json, under hosts.

As an update. It’s now 4 days since I turned HomeKit off on the old iOS 9 iPad - all seems well and stable.

In case it's helpful to anyone,  I had an old iPad running iOS 9 that was used for viewing nursery cameras - in the settings on this iPad I have now turned off 'Use iCloud' under HomeKit.   It appears that this was playing games with the iCloud sync and removing any platforms from my home app including any Homebridge-Hue lights and sensors (these platforms remained intact in the Homebridge UI).
iOS9 was prior to the Home app being released but still had HomeKit integration (setups were completed in dedicated hub apps - Phillips hue, eve etc... if I remember correctly).   I believe iOS 10 introduced ‘platforms’ to HomeKit, not sure if this is the route cause or not?   My ‘accessories’ remained active in the home app, but my ‘platforms’ did not.
Interested in thoughts on this.

I believe iOS 10 introduced ‘platforms’ to HomeKit, not sure if this is the route cause or not?

I have no idea what you mean by that.  Platform vs accessory plugins are a Homebridge thing, completely invisible to HomeKit.  Homebridge Hue has been a platform plugin from the very start; I think this was in the iOS 8 days, but I don’t quite remember.
HomeKit recognises standalone vs bridged accessories.  Almost all accessories exposed by Homebridge are bridged (what’s in a name...), except external accessories, like TVs, that need to be paired separately.  The native Hue bridge HomeKit function also exposes bridged accessories, from the very start.  I seem to remember this was before iOS 10, but it’s been a long time.

This started happening for me this week. Strange that there’s actually an open case.
I did make a change and for the first time I started using Sensors:true to expose my Hue Labs formulas for my holiday scenes.
I’m going to do some testing and report back.

I created a separate instance just for homebridge-hue to do some testing. Debug Logs don't show anything at all and if I followed the  I stared with just my lights went a full 24 hours with no issues and enabled sensors again. Within a few hours the devices were gone and reset back to default. Going to let it run without sensors again, but leave it for several days (or until/if it re-occurs).

Let me re-iterate that there have been no cases where Homebridge Hue or Homebridge, while running, has caused accessories to disappear.   Technically, the only possibility for accessories to disappear at the Homebridge side, is for Homebridge to start its server, without Homebridge Hue exposing the accessories.  So far we’ve seen (in order of likelihood):

On system reboot, Homebridge starts before deCONZ has exposed all /lights resources.  This only causes lights to disappear, and only when exposed by deCONZ.  Remedy: use a lightlink resourcelink so Homebridge Hue delays Homebridge server startup until deCONZ has exposed all lights;
On Homebridge startup, Homebridge Hue fails to discover all bridges and/or gateways and allows Homebridge to start only exposing accessories for devices from the discovered bridges/gateways.  This can only happen when you have multiple bridges and/or gateways.  Remedy: bypass discovery by listing the bridges/gateways under hosts in config.json;
A bug in Homebridge Hue would allow the Homebridge server to start when the API key in config.json is not / no longer valid.  This was a bug in Homebridge Hue and is fixed in v0.12.2 and later.

All other cases of disappearing accessories are caused at the HomeKit side, beyond control of Homebridge Hue or Homebridge.  So far, we’ve seen:

An old iOS version would cause the sync over iCloud between iDevices to fail;
The Hue app being overzealous in syncing between HomeKit and the Hue bridge.

If you think you’ve hit a bug in Homebridge Hue allowing Homebridge to start without exposing all accessories, please enable Homebridge debug mode, and attach the debug log file and the debug dump file (see README).

Hi there, I quickly wanted to report, that my setup is now stable. I removed the Hue bridge completely and now running on raspBee/deCONZ/Homekit/Homebridge-Hue. Thanks to all who helped me understand how HomeKit works... that helped my rule out issues.  In retrospect, I think it was the HueApp`s HomeKit implementation that caused the interference. And probably it might have sufficed to just turn off the HomeKit support in the HueApp. But I decided for a clean setup - and the HueBridge did not provide any service I would require.

I still have issues with lights dissapearing or not showing up in Homebridge / Homekit at all (although in Phoscon app just fine)


Edit ReadMe file

Hacktoberfest

Sorry, but this is kind of ridiculous. This is not the purpose of Hacktoberfest by any means. Goal is to push open source projects and not to grab a shirt by doing useless (sorry, no offense) pull requests.

@n1try If you label this as invalid, it won’t count for their contributions.


ARMv7 target

Hello!
First of all thanks for this very easy to use cross-compiler magic-bag-of-tools-that-just-work!
Then, my question is, could you add an option to target ARMv7?

Thank you!
You can already execute code compiled for ARMv6 on an ARMv7 device.
But I agree with you that specific ARMv7 optimizations will be missing.


Error during load 'eslint.config.js'

When I trying to run npx @eslint/config-inspector
I get an error: Error: Dynamic require of "fs" is not supported
Env: Node.js 20
Config
import globals from 'globals';
import pluginJs from '@eslint/js';
import tseslint from 'typescript-eslint';

export default [
  { languageOptions: { globals: globals.node } },
  pluginJs.configs.recommended,
  ...tseslint.configs.recommended,
  {
    files: ['__tests__/**/*'],
    plugins: ['jest'],
    env: {
      'jest/globals': true,
    },
  },
  {
    rules: {
      'prefer-const': 'error',
      'max-len': ['error', { code: 120, ignoreComments: true }],
    },
    files: ['**/*.ts'],
  },
];

I suppose plugins: ['jest'] isn't even valid in flat config

We temporarily closed this due to the lack of enough information. We could not identify whether it was a bug or a userland misconfiguration with the given info.
Please provide a minimal reproduction to reopen the issue.
Thanks.

Why reproduction is required


517: Generator for OptionalLong

Changes:

Added generator for OptionalLong
Unit tests for OptionalLongGenerator
Refactored OptionalIntGenerator to final and reduced the visibility of OptionalLongGenerator constructor (LMK if you feel this should be a separate refactoring PR)

@armandino This one is in the same line as that of #663 and it is up for your review

Looks good, thanks!


Fix build on nightly

Hi, @Amanieu.
https://github.com/rust-lang/rust/pull/42894 makes some compatibility lints in rustc deny-by-default and regression testing found that this crate is affected. Here's a patch fixing the deprecated code (see https://github.com/rust-lang/rust/issues/37872 for more information about the issue).

Thanks, published in v0.3.4.


Make a new, daemonized "listen" command

Running whim daemon leaves you looking at a foregrounded process dumping its log messages to the terminal. That's fine for development, but not for production.
If you instead run hypnotoad [/path/to/whim], then the listener automatically backgrounds itself. That's production-appropriate behavior, but what an awkward thing to type.
I would very much like the former command -- or a new command, with similar syntax -- to work like the latter.

Let's call the new command whim listen, and allow whim daemon to continue using the default mojo command of that name.
I experimented with making a listen command that used Mojo::Server::Hypnotoad directly, but that module doesn't like being used outside of the hypnotoad command line program, per se.
I made a trivial copy of Mojo::Server::Daemon that added a single line of $daemon->daemonize;, and it did the right thing -- only with no feedback, and no way to stop it (other than finding the PID yourself and issuing a kill).
The solution seems to be somewhere in between.

Fixed with #30.


Private Repo Authentication: use auth token from ~/.dockercfg

Is it be possible to use auth token from ~/.dockercfg (or ~/.docker/config.json) instead of using plain username/password authentication?
https://github.com/docker/docker/pull/12009

@olkulyk It's certainly possible. What's the use case or problem you're looking to solve?

+1
This is necessary to allow access to Google Container Registry:
gcloud docker -a
mvn docker:push
The first command updates the .dockercfg with temporary access tokens for *.gcr.io. Currently these are not picked up by the docker-maven-plugin, so there is an auth error when accessing the registry.

+1
my group is using Artifactory as our local docker repository with a service account that only a certain number of users should have access to.  Requiring the info in the settings.xml exposes this information unnecessarily.
In addition, I can't get the authentication to work with the edits to settings.xml, fails with "{"error": "Unauthorized getting repository images"}".

We're definitely open to PRs on this :)

+1

+1

+1

https://github.com/spotify/docker-client/pull/219 should help provide this.

This should be addressed by https://github.com/spotify/docker-client/pull/268. I'll close this for now. We can reopen if there are more issues.


Add watcher to gulpfile

Added watcher to gulp

Few issues raised, but pretty much looks ok.

[Current coverage][cc-pull] is 49.58%

Merging [#115][cc-pull] into [master][cc-base-branch] will increase coverage by +<.01%

@@           master       #115   diff @@
========================================
  Files          10         10
  Lines         119        119
  Methods         0          0
  Branches        0          0
========================================
  Hits           59         59
  Misses         60         60
  Partials        0          0

Powered by Codecov. Last updated by [0426892...8b4237e][cc-compare]
[cc-base-branch]: https://codecov.io/gh/komitywa/wysadzulice.pl/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/komitywa/wysadzulice.pl/compare/04268929962074abdddcd4f41a96faa110954ccb...8b4237e572ed2a9ed52458af4616d4a9faf91e29
[cc-pull]: https://codecov.io/gh/komitywa/wysadzulice.pl/pull/115?src=pr


problem with other config since the last patch

Hi,
since the last update (1.5) i can't use arkmanager useconfig pve
alternate configs
example for config name "ark1":
configfile_pve="/etc/arkmanager/arkmanager-pve.cfg"
configfile_pirate="/etc/arkmanager/arkmanager-pirate.cfg"
i tried arkmanager useconfig pve status but nothing
/usr/local/bin/arkmanager: ligne 1481:  No such files or folders of this type

#329 should fix that.

thanks


Update k8s.gcr.io to registry.k8s.io

This PR updates k8s.gcr.io to registry.k8s.io
Part of https://github.com/kubernetes/k8s.io/issues/4780

Related: https://github.com/longhorn/longhorn/issues/5432

cc @yangchiu

@Mergify backport v1.4.x v1.3.x


Question: individual instructions on a task level with GeoJSON

I assume there is already a way to do so, since I have seen distinct instructions per task. I doubt that those were added manually, though for the unlikely case that there is no way see it as a feature request and not a request for documentation.
How should a geoJSON be structured to make use of the fields in MapRoulette that can be changed on task level and not only challenge level.
(I hope I didn't miss already existing documentation and wasting your time with not finding it.)

I don't believe we currently will set individual task instructions from GeoJSON, but we do support referencing task properties in the challenge instructions using mustache tags, which I would guess is what you are seeing on those other challenges. Truly task-specific instructions tend to be somewhat rare, but can be set either manually or through the API.
Here's what we say about those mustache tags for the Challenge Instructions:

You can also reference feature properties from your GeoJSON with simple mustache tags: e.g. {{address}} would be replaced with the value of the address property, allowing for basic customization of instructions for each task

Let me know if that is sufficient for your needs.

@nrotstan That's great. And in theory, if I weren't happy with that I could just use {{instructions}} as the instructions. It is definitely sufficient for me. Thank you!


Padding sent1 hurts the performance of sentence pair tasks

Padding the first sentence to make it a fixed-sized vector hurts the accuracy of sentence pair tasks. My input representation for BERT is as follows,
Input_ids   : <CLS><...Sent_1_tokens...><SEP><PAD>...<PAD> | <SEP><...Sent_2_tokens...><SEP><PAD>...<PAD>
Segment Ids :  0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 | 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0
Input Mask  :  1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 | 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0

When I do not pad sent1 and directly append it with a separator token followed by sent2 (as suggested in the paper), I am getting great accuracy score. However, the inputs to BERT for my specific usecase are already padded, which puts me in a tough spot. Is there any reason why fine tuning might not be working for this representation and can you suggest a solution to this problem?

Never mind, resolved this issue!!
To those who might be stuck in a similar issue, replace the [PAD] tokens between sentence 1 and sentence 2 with [unused] tokens from BERT's vocab.txt file. I am guessing that the reason this works is that the [PAD] tokens between sentence 1 and sentence 2 represents a slightly different meaning as opposed to the original [PAD] tokens used during BERT's training (which generally comes at the end of input sequence, hinting the network to not waste any attention to what follows beyond). Using an  [unused] token helps BERT learn a meaningful embedding for the [PAD] present between sentences while also focussing on achieving the objective of the training simultaneously. It is actually awesome how seamlessly BERT does it.

A more elegant solution is to use the input_mask to mask the [PAD] tokens between the sentence pair. Note: The input_length is computed as the distance from the start before encountering the first token (which in my case occurred in between the sentence pair). If you are following my procedure then you must also explicitly adjust the input_length tensor, else the implicit masking in Bert would mask anything that comes after the first  token.


Choose better types for the ci_sessions table

Description
Choose better types for the ci_sessions table:

for Postgres, use type BYTEA for binary data. Compared to storing base64-encoded text, this takes less space
update the user guide to suggest using type INET for storing IP addresses in Postgres. This type offers input error checking and specialized operators and functions
for both MySQL and Postgres, use type timestamp instead of integer. This type is easier to work with when analyzing session activity.

Checklist:

[X] Securely signed commits
[ ] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[X] User guide updated
[X] Conforms to style guide

Sorry about that, I've made a new PR for this.


[Bug]: Running shopify theme package creates an empty zip file

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?

Previously reported here, but the fix didn't solve the issue. Rolling back to 3.48.4 doesn't solve the issue. Last time it was reported to be a Windows only issue.
Actual behavior
The command generates empty zip file.

Reproduction steps

Run shopify theme package
Zip is created.
It is empty.

Operating System
Windows 11
Shopify CLI version (check your project's package.json if you're not sure)
3.49.3
Shell
Git Bash
Node version (run node -v if you're not sure)
v18.17.1
What language and version are you using in your application?
No response

@gonzaloriestra @isaacroldan Can you guys take a look again? Thanks!

Hi! Thanks for opening the issue. I'm trying to reproduce with Git Bash and the same versions of CLI, Windows and Node, but it works for me...
Could you remove the created zip file and share the output of shopify theme package --verbose?

@gonzaloriestra Thanks for the reply. Here's the output:
$ shopify theme package --verbose
2023-09-15T15:49:33.445Z: Running command theme package
  shopify:theme:package init version<EMAIL_ADDRESS>argv: [ '--verbose' ] +0ms
2023-09-15T15:49:33.455Z: Reading the content of file at config/settings_schema.json...
2023-09-15T15:49:33.460Z: Zipping C:\Users\user\Desktop\Work\paper into Paper-6.1.1.zip
╭─ success ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│                                                                                │
│  Your local theme was packaged in Paper-6.1.1.zip                                                                                │
│                                                                                │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

2023-09-15T15:49:33.569Z: Obtaining the dependency manager in directory C:/Users/user/Desktop/Work/paper...
2023-09-15T15:49:33.584Z:
Running system process:
  · Command: ruby -v
  · Working directory: C:/Users/user/Desktop/Work/paper

2023-09-15T15:49:33.771Z: Request to https://monorail-edge.shopifysvc.com/v1/produce completed in 152 ms
With response headers:
 - x-request-id: 85876f48-d58a-4687-bf78-ce09dccc9d20

2023-09-15T15:49:33.772Z: Analytics event sent: {
  "command": "theme package",
  "time_start":<PHONE_NUMBER>446,
  "time_end":<PHONE_NUMBER>565,
  "total_time": 119,
  "success": true,
  "cli_version": "3.49.3",
  "ruby_version": "3.2.2",
  "node_version": "18.17.1",
  "is_employee": false,
  "uname": "windows amd64",
  "env_ci": false,
  "env_plugin_installed_any_custom": false,
  "env_plugin_installed_shopify": "[\"@shopify/cli\",\"@shopify/plugin-did-you-mean\",\"@shopify/theme\"]",
  "env_shell": "C:\\Program Files\\Git\\usr\\bin\\bash.exe",
  "env_device_id": "3e050dcf8088fd5af51bb7868986b4b424d0b023",
  "env_cloud": "localhost",
  "env_package_manager": "npm",
  "cmd_all_launcher": "unknown",
  "cmd_all_topic": "theme",
  "cmd_all_plugin": "@shopify/theme",
  "args": "--verbose",
  "env_plugin_installed_all": "[\"@shopify/cli\",\"@shopify/plugin-did-you-mean\",\"@shopify/theme\"]",
  "metadata": "{\"extraPublic\":{},\"extraSensitive\":{}}"
}
2023-09-15T15:49:33.773Z: Completed command theme package

Does it work if you run shopify theme package --path . as a workaround?

Still relevant I guess. Workaround works, but it's a workaround.


polymorphic's control block does not construct the object using the allocator

https://github.com/jbcoe/value_types/blob/a7fa0db8f4710853f9c4469c6749102a3906e7b1/polymorphic.h#L70
This just constructs the object by passing the args directly, but the spec says the object should be constructed using the allocator's construct function. That is used to create the control block:
https://github.com/jbcoe/value_types/blob/a7fa0db8f4710853f9c4469c6749102a3906e7b1/polymorphic.h#L142
But that doesn't allow a scoped allocator to pass itself to the U object.

My solution is for the control block to have a union { U u; } which is not initialized in the control block constructor, then you can construct a U into that location using the allocator's construct function.


Testing stripe flake

See https://chat.zulip.org/#narrow/stream/273-kandra-billing/topic/Testing.20stripe
Opened to ask for help.

Closing as no longer required after help from @laurynmm in https://chat.zulip.org/#narrow/stream/273-kandra-billing/topic/Testing.20stripe


Amortized costs for PAYG subscription

Hi, please can you make it clear in documentation if Amortized costs view is supported for PAYG subscription ?
From my experience we are getting same data int Amortized cost view as Actual costs.
Docs link https://docs.microsoft.com/en-us/azure/cost-management-billing/costs/cost-analysis-common-uses#view-your-reservation-charges

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

ID: dbc00258-0efb-0589-34f5-c14c9660ee04
Version Independent ID: c2671d6c-0a35-2c67-4e0d-2fc9461bef4e
Content: Common cost analysis uses in Azure Cost Management
Content Source: articles/cost-management-billing/costs/cost-analysis-common-uses.md
Service: cost-management-billing
Sub-service: cost-management
GitHub Login: @bandersmsft
Microsoft Alias: banders

@jjindrich Thank you for your post. We will look into it and get back to you soon.

@jjindrich RI should not be available for Pay-As-You-Gp on Azure Cost Management (ACM), its only available for EA and MCA.

This should give the exact answer to your question - Understand Azure Cost Management data | Microsoft Docs
@bandersmsft For doc update!

Hi, but in PAYG subscription you can buy reservations. I have my own PAYG subscription and I can buy reservations without problems.

Yes you can buy reservations. But RI's don't show up in ACM for Pay-As-You-Go.

Ok, now clear.

@SadiqhAhmed-MSFT
I consider this as a bug:
As a PAYG user:

I can purchase RI without any warning
I can see options to switch from actual costs to amortized costs in Cost Management
but it gives me misleading costs (actual = amortized)
now I am in situation where I cannot calculate costs per subscription for internal reporting

I could not prevent this from happening. What can I do now? reservation purchased for 3 years...

@damovsky Thanks for raising this issue. It helped identify a gap we have with Cost Analysis. I'ved updated the article section you linked above with the following information:

Although you can buy a reservation with a pay-as-you-go (MS-AZR-0003P) subscription, Cost Analysis doesn't support viewing amortized reservation costs. If you try to view costs with the Amortized cost metric, you'll see the same results as Actual Cost.

As for the reservation that you now have (and seems you don't want). You can cancel your reservation. Check out https://docs.microsoft.com/azure/cost-management-billing/reservations/exchange-and-refund-azure-reservations. If that won't work for you, you can create a support request at https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest
#please-close


Issue 40659: correct jQuery references

Rationale
Removes the jQuery from timeline and refers from internal
Related Pull Requests
https://github.com/LabKey/commonAssays/pull/194
https://github.com/LabKey/targetedms/pull/213

Verified this by Running TimelineTest, it is passing locally. Let me know if more testing could be done to verify.

We probably are doing this in other places for client-side dependencies, but we should try to minimize the referencing of files from other modules.  It makes it not possible to build modules independently and we're seeing more people want to do that. Here there's really no ill effects since internal and timeline are both in the same git repo so you would have to try very hard to have the source for timeline without having the source for internal, but if we're reaching over to internal from non-platform modules we should try to find a different solution.

@labkey-susanh I was giving Ankur the opposite guidance. Aren't we guaranteed that API and Internal will be present on all deployments? We don't ship extra copies of ExtJS in non-platform modules - can we not take a similar approach? Or should we promote jQuery from Internal to API?

@labkey-susanh I was giving Ankur the opposite guidance. Aren't we guaranteed that API and Internal will be present on all deployments? We don't ship extra copies of ExtJS in non-platform modules - can we not take a similar approach? Or should we promote jQuery from Internal to API?

Yes, we are guaranteed they will be in all deployments (server won't run without them), so if this is a change for run-time use then we should be ok.  It's only if it's necessary for the build to happen that we might have a problem.  But, yes, treating it like we do ExtJS should be find.

Please double-check that the TimelineTest is still happy after this change, but I hope we're happy and don't have duplicates checked in now

Timeline test is still happy


support curved meshes for DGMulti with VolumeIntegralWeakForm

This enables curved meshes for DGMulti solvers with VolumeIntegralWeakForm.
It also implements a "weight-adjusted" mass matrix inversion trick for curved meshes with dense mass matrices.

@ranocha fixing conflict with merged PR https://github.com/trixi-framework/Trixi.jl/pull/1382 dismissed your old review 😞

@ranocha Windows MPI tests failed 3 times. Pretty sure the failures are spurious; OK if I merge?

Yes - that's been happening for a while


App: Safari

Question- How will you manage the CORS policies? That seems to be the biggest issue with having a "browser in a browser"

hey
i have a idea

use https://www.google.com/search?q= (your search here not have () )

p

use

716847e4cbb0aee94db8b2ee12d2c11dc7afdd97


[Reference Architecture] Fix headers

في الأربعاء، ١٩ يوليو ٢٠٢٣ ٢:٥٦ ص Patricia Santa Ana <
@.***> كتب:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/cloudflare-docs/pull/9938#pullrequestreview-1536043948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWV6NCUPXHMVOPUYDZNSOQ3XQ4PCLANCNFSM6AAAAAA2PCWU7E
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[5.6] Add products(ofType:), targets(ofType:), and sourceFiles(withSuffix:) utilities to PackagePlugin API

SwiftPM 5.6 nomination of https://github.com/apple/swift-package-manager/pull/4094

@swift-ci please test