Open the viewer automatically

Hello good day.
Is there any way to automatically open the viewer , displaying the first image in the gallery?
Thanks for the support and congratulations for the work .
Regards,
Marcelo

Why not read the documentation first? Didn't you see the show method?

Hi, thanks by the answer. I read the documentation and I try use the show method, but doesn`t works.
I will try with another way.
Thanks by help and congratulations for the work!
Regards,
Marcelo


Update expression normalization to support LicenseRef

Closing in favor of https://github.com/clearlydefined/service/pull/1148


fix service monitor selector

What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

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

/area falco-chart

/area falco-exporter-chart

/area falcosidekick-chart

/area falco-talon

/area event-generator-chart

/area k8s-metacollector

What this PR does / why we need it:
This PR fixes a bug that would not set the selector in the serviceMonitor
Which issue(s) this PR fixes:

Fixes #
#790
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

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

Needs approval from an approver in each of these files:

OWNERS [alacuku]

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


Unusable mobile view (iPhone X)

Congrats on the Smashing Magazine feature.
I wanted to try the tool on my iPhone X, but the canvas is barely visible, and I couldn't maximize it by collapsing the menu. Am I missing something?

The demo isn't really optimized for mobile, but I suppose I could try to make it work better for that. Indeed the sidebar can't be collapsed, I know I added a button there which is a bit stupid, but I wanted to make sure people didn't randomly close the sidebar and be confused as to where to get the blocks.
I could add that tiny functionality though, it's honestly not a big deal and a bit of an oversight from my part.

Closing this issue as even if the panel did collapse, the user then would be unable to drag the blocks onto the canvas. Might explore another way to implement this eventually - but ultimately it is not a problem of the library, rather how it is implemented (and furthermore a mobile-friendly solution could be thought out by the developer).


Stop checking non-edurange containers

Celery log repeatedly displays Error: No such container:path:
Suggested fix: only check for containers from the edurange2 Docker repository. Basically, any image name that starts with edurange2/.

look Docker image tags or look in database


First steps of OpenSSL::Digest

This is good enough to make the specs pass, even though there are a couple more interfaces to these objects

Nice!!


20200402 Feilong meeting notes

Signed-off-by: Mike Friesenegger<EMAIL_ADDRESS>

thanks @mfriesenegger ! :)


Added refresh events to MetricsEndpointProvider

Added ingress events to the refresh_events input parameters to the MetricsEndpointProvider constructor. This causes the charm to reconfigure its integration with the Prometheus charm every time the events in refresh_events are called. The default for this value is the update_status.

Currently we set the external_hostname so prometheus uses the ingress to fetch the metrics, I suppose this make sense if you cos stack is in another cluster, but not otherwise. Perhaps we should remove the external_hostname part.
If ingress is needed, it makes sense to refresh the relation data when the ingress relation changes.
@bencekov I don't understand why we need to refresh on update_status?

if we use the ingress then not all the pods get scraped, only the ones that the load balancer redirects u, so ideally Prometheus should be in every cluster otherwise it's kinda self defeating


CORTX-30792: Cluster IP service for HA Pod

Description

Breaking change

Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds new functionality)
[ ] Breaking change (bug fix or new feature that breaks existing functionality)
[ ] Third-party dependency update
[x] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates

Applicable issues

This change fixes an issue: #
This change is related to an issue: #

CORTX image version requirements

This change requires the following images:

cortx-all:<version>
cortx-rgw:<version>

How was this tested?

Additional information

Checklist

[x] The change is tested and works locally.
[x] New or changed settings in the solution YAML are documented clearly in the README.md file.
[x] All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change addresses a CORTX Jira issue:

[x] The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

Please fill out the PR template completely. Description and CORTX image version requirements in particular are necessary for us to properly review this. Thanks.

As per the Discussion with HA team, the Cluster IP service is not required currently, hence closing this PR.


Debug failure in TSServer autocomplete

Bug Report
I've noticed that in the devtools-frontend codebase (https://chromium.googlesource.com/devtools/devtools-frontend), autocompletion suggestions work once and then do not work again when typing. I suspected at first it was a problem with my editor (Vim) but I've also been able to recreate the issue in VSCode, and have delved into the logs to find a "Debug Failure" error reported from TSServer.
🔎 Search Terms
autocomplete, no autocomplete entries
🕗 Version & Regression Information
I'm not exactly sure, but I suspect it started happening at some point in TS 4.4.X's lifespan. It's happening currently for me on TS 4.4.3.
This is also occurring on @next, which at the time of writing is 4.5.0-dev.20210923.

This is a crash

To reproduce
(Appreciate this is a lengthy repro but it's clearly something in our project causing the issue).

Pull down the latest devtools-frontend repo
Load up ElementsBreadcrumbs_test.ts in the test/unittest folder (picking this file rather randomly - seems to happen in most files)
Go to line 403, below it start typing leftB. See how the autocomplete suggests leftButton as you'd expect. Accept this suggestion.
(This is where I'm less confident), but keep trying below line 403 now to insert new lines and start typing leftB. At some point (not sure what the exact trigger is) you will see that the autocomplete falls back to just text matches because something has gone wrong in the server:

Looking at the logs from the server, I see:
"Request textDocument/completion failed with message: Error processing request. Debug Failure. Could not find symbol 'newDefaults' by key 'newDefaults' in module \"/usr/local/google/home/jacktfranklin/src/devtools-frontend/front_end/third_party/marked/package/src/defaults\"\nError: Debug Failure. Could not find symbol 'newDefaults' by key 'newDefaults' in module \"/usr/local/google/home/jacktfranklin/src/devtools-frontend/front_end/third_party/marked/package/src/defaults\"\n    at rehydrateCachedInfo (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:124229:66)\n    at Array.map (<anonymous>)\n    at /usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:124177:33\n    at Map.forEach (<anonymous>)\n    at Object.forEach (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:124175:28)\n    at /usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:127920:32\n    at resolvingModuleSpecifiers (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:126505:26)\n    at collectAutoImports (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:127919:17)\n    at getGlobalCompletions (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:127831:17)\n    at tryGetGlobalSymbols (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:127737:25)\n    at getCompletionData (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:127508:22)\n    at Object.getCompletionsAtPosition (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:126570:34)\n    at Object.getCompletionsAtPosition (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:157807:35)\n    at IOSession.Session.getCompletions (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:169269:64)\n    at Session.handlers.ts.Map.ts.getEntries._a.<computed> (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:168116:61)\n    at /usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:169918:88\n    at IOSession.Session.executeWithRequestId (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:169909:28)\n    at IOSession.Session.executeCommand (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:169918:33)\n    at IOSession.Session.onMessage (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:169944:35)\n    at Interface.<anonymous> (/usr/local/google/home/jacktfranklin/src/devtools-frontend/node_modules/typescript/lib/tsserver.js:172549:31)\n    at Interface.emit (events.js:375:28)\n    at Interface._onLine (readline.js:364:10)\n    at Interface._normalWrite (readline.js:509:12)\n    at Socket.ondata (readline.js:216:10)\n    at Socket.emit (events.js:375:28)\n    at addChunk (internal/streams/readable.js:290:12)\n    at readableAddChunk (internal/streams/readable.js:265:9)\n    at Socket.Readable.push (internal/streams/readable.js:204:10)\n    at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)"

Clearly something in third_party/marked is causing problems. Looking at third_party/marked/src/defaults.js, we see:

I then decide that maybe the implicit any is causing issues, so added the explicit any param:
/**
* @param newDefaults {any}
*/
function changeDefaults(newDefaults) {
  module.exports.defaults = newDefaults;
}

But unfortunately it doesn't seem to fix the issue. I'm therefore assuming that something in the oddity of the module.exports.defaults = newDefaults is throwing TSServer off, but that's as far as I can get.
If I can provide any more info or debugging, please let me know!

Forgot to say, if I delete the module.exports.defaults = newDefaults line, autocomplete is back and everything works as expected.

Thanks for the detailed repro! Would you be able to try the version of TypeScript that @typescript-bot packed in #45792 and see if that fixes it?

Thanks for trying it @jackfranklin. An alternate version of that fix has now made it into nightly, but it does sound like maybe the root cause is something different. I can give it a try with the repro instructions you left. Thanks!


rework LimitedImageWMS class

fixes #1868

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

21 of 21 (100.0%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 99.475%

Files with Coverage Reduction
New Missed Lines
%

src/modules/olMap/handler/measure/OlMeasurementHandler.js
1
96.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
10119

Relevant Lines:
10122

💛  - Coveralls


Rollup Plugin?

Hello @bergie
I just found out about FBP and I think it is awesome :) Luckily NoFlow allow me to code in the most greatest programming language i.e. Javascript :smile:
I am trying to find a Rollup plugin for bundling browser based components but I only manage to find webpack loader. It would be helpful if anyone can point me to an existing Rollup plugin and if there is none, I would be nice if someone can point to noflo docs so that I can build this plugin.

I haven't used Rollup, but would be nice to create a plugin that would handle the component loader stuff for NoFlo.
Seems Rollup plugins are not that complicated: https://github.com/lautis/rollup-plugin-coffee-script/blob/master/index.js


LH messages can get retried indefinitely

Describe the bug
LH messages can get retried indefinitely
To Reproduce
Steps to reproduce the behavior:

Go to '...'

Additional context
There are a few options:

Let publisher retry, so client can drop
If client retries, (as of right now), it should timeout after each attempt

3 Using retry counts like in sequencer to try a max number of times before dropping it.

Additional context:
https://app.datadoghq.com/logs?query=host%3Aip-172-17-1-246.us-west-1.compute.internal service%3Alighthouse-prover-subscriber container_id%3A4cf2357956b1475297c7b354a919cc1c-2228731739 task_arn%3A"nxtp-ecs-core-testnet-production%2F4cf2357956b1475297c7b354a919cc1c"&cols=host%2Cservice&context_event=AYjlqdU6AAAuncAXeOKISAAA&index=*&messageDisplay=inline&stream_sort=time%2Cdesc&viz=&from_ts=1687468309990&to_ts=1687482709990&live=true

Would you post the brief explanation why it throwing with !MessageStatus.None here?

retry mechanism is not always robust enough and we self-dos sometimes. still working, but slower
fixing this to meet throughput goals

Merged, monitoring testnet prod. Might need to add another mechanism to limit retry count. Once it gets queued, it shouldn't get re-queued again, need to add a status.

Its fixed by the message cache implementation


ceph-infra: Remove restart firewalld handler

There's no need to restart firewalld service when a new rule is
added due to the usage of the immediate flag.
Signed-off-by: Dimitri Savineau<EMAIL_ADDRESS>

jenkins test pipeline

jenkins test dev-centos-non_container-all_daemons

jenkins test pipeline


Release/value class/v1.0.2

Pre-launch Checklist (Required)

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I listed at least one issue that this PR fixes in the description above. Or a simple fix.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

Issue (Optional)
Nothing.

Can't wait for Dart 2.18.0 😢
Package validation found the following error:
* Your pubspec.yaml must not override non-dev dependencies.
  This ensures you test your package against the same versions of its dependencies
  that users will have when they use it.
Sorry, your package is missing a requirement and can't be published yet.


[KYUUBI #360] Correct handle getNextRowSet with FETCH_PRIOR FETCH_FIRST

       ❨?❩

Why are the changes needed?

close #360
Ref: https://github.com/apache/spark/pull/30600
How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

thanks, merged to master for v1.1.0


Any chance this works without using Node in the server side ?

I love React and would like to use this framework. But I do not want to use Node in the server side. Any chance this will work without using Node ?
Edit: Sorry, this seems to have been asked before. I saw some comments about compiled libraries being available from 0.8 onwards. But I still see Node being required in the getting started example. Can anyone clarify this ?

is there a link between node and material-ui?
Material only need a browser to work.

@cgestes - In the Usage section of this page(http://material-ui.com/#/get-started), the code is written in Node. Maybe I am wrong, but this seems that material-ui needs Node.

It doesn't.
You need npm to easily install it and compile it, but node is not required as far as I know. (I'am using it on mobile for example).
just launch webpack and use the resulting JS as you desire.

@agnivade  The code in the examples is not server-side code, and it's written in a style like Node mainly because npm is the preferred way of managing your dependencies like React. They are JavaScript after all.
You can use build tools like browserify, webpack, requirejs or whatever tools to your liking to build it and make it actually run in the browser.

Perfect. Thanks a lot guys !

we miss starter kits, and examples.
(we have a bug about it)
On Thu, Jul 23, 2015 at 10:35 AM, Agniva De Sarker<EMAIL_ADDRESS>
wrote:

Perfect. Thanks a lot guys !
—
Reply to this email directly or view it on GitHub
https://github.com/callemall/material-ui/issues/1249#issuecomment-124021930
.

Totally agree.
Sorry to be a bother again, seems like I am stuck. (First time using browserify and React, sorry if this seems simple)
Here's what I am doing - I am trying to browserify the js files from the /build folder after doing the npm install.
cd material-ui/lib/index.js
browserify  index.js -o components.js
Now I have included components.js in my html file.
And inside a React class of my own, I am trying to use the AppBar component like this -

But when loading the page, the browser says AppBar is not defined.
I am using the example html from the React website.
<!DOCTYPE html>

    <title>Hello React</title>

    <link rel="stylesheet" href="css/base.css" />

      <--- I have added this

This is my code in example.js
 var CommentBox = React.createClass({
     render: function() {
           return (

Comments

                 <AppBar  title="Title"  iconClassNameRight="muidocs-icon-navigation-expand-more" />
                 <CommentList data={data}/>
                 <CommentForm />

                  );
    }
 });

Any help is highly appreciated. Thanks !

Hello dears,
I am gonna integrate angularJS and react together, I used react just as view in whole of application, now everything is fine but the question is how could I integrate it with Material UI cause I have to use react by JSX inside of my angular controllers and finally by gulp and browserify handle it and if I wana use Material UI I have to use npm and so on, is there any tips please?


Upgrade react-apollo to the latest version

We're currently running react-apollo 1.4.16. This version is not maintained anymore and it starts to be difficult to find the documentation for it. The best I could find: https://s3.amazonaws.com/apollo-docs-1.x/api.html
The latest stable version is 2.1.4 but unfortunately the API is different and upgrading would need a lot of attention.
We might actually skip version 2, because version 3 is coming (3.0.0-alpha.2 is already available https://www.npmjs.com/package/react-apollo/v/3.0.0-alpha.2).
Also, important to note, we're keeping right now graphql to 0.12.3 and graphql-tag to 2.6.1 to keep the versions consistent with react-apollo.

There is a new interesting pattern in Next.js 6 that we could use.
https://zeit.co/blog/next6#app-component
https://github.com/zeit/next.js/tree/canary/examples/with-apollo

Implemented in: https://github.com/opencollective/frontend/pull/528


added batch file processing sample

@orizohar  Hi Ori, thanks a lot for testing the deployment! I fixed all the issues that you mentioned.


All the crates use edition 2018 now except for the cmsis-ffi

hi @Yatekii Thanks for the hard work on this! Sorry I have been AFK for the past week. Let me know if you would like me to make the changes I requested.

Heh, yeah, sorry, there was so many changes, it got kinda messy ... Sorry for that!


pytest-splinter does not work with splinter>=0.18.0

    def patch_webdriverelement():  # pragma: no cover
        """Patch the WebDriverElement to allow firefox to use mouse_over."""

        def mouse_over(self):
            """Perform a mouse over the element which works."""
            (
                ActionChains(self.parent.driver)
                .move_to_element_with_offset(self._element, 2, 2)
                .perform()
            )

        # Apply the monkey patch for Firefox WebDriverElement
>       firefox.WebDriverElement.mouse_over = mouse_over
E       AttributeError: module 'splinter.driver.webdriver.firefox' has no attribute 'WebDriverElement'

.venv/lib64/python3.10/site-packages/pytest_splinter/splinter_patches.py:21: AttributeError

Hmmm somehow I thought that I already patched it.
Can you submit a pull request?

Should we really keep patch_webdriverelement?
After all, it's implementation, while still being different parameters than pytest-splinter, is expected to work?
Meanwhile, the workaround is to short circuit patch_webdriverelement ie.:
  9 def patch_webdriverelement():  # pragma: no cover
 10     """Patch the WebDriverElement to allow firefox to use mouse_over."""
 11     return

Unfortunnately, I don't have anything with mouse_over to test my project without the monkey patch.

@mpasternak yes, you fixed it in 0f9cae60
But it's not in pypi

@jpic looks like it's time for a new release then.

Just confirmed this locally with dal
Thanks :pray:
Keep up the gr8 work :tophat:

@jpic how do you feel about testing pytest-splinter 3.3.2

Working for me! Thanks!

"No... you're breathtaking!" Thanks!


Coverage reporting hangs for C++ tests on X86 qemu

Describe the bug
When C++ related tests are executed with coverage reporting on X86 Qemu, Qemu will end up in endless loop when dumping coverage results to UART.
To Reproduce
Steps to reproduce the behavior:

Remove platform_exclude: qemu_x86_coverage from tests/application_development/libcxx/testcase.yaml
sanitycheck -N -p qemu_x86_coverage -s tests/application_development/libcxx/misc.app_dev.libcxx

Expected behavior
C++ tests can run with coverage enabled on Qemu X86 without hanging.
Impact
No coverage reports can be generated for C++ test cases
Environment (please complete the following information):

OS: Linux - Ubuntu 18.04.3
Toolchain: Zephyr SDK 10.03
Commit SHA: 86461ac559a

Additional context
Quick look with gdb reveals that the while loop in gcov_coverage_dump is an endless loop
https://github.com/zephyrproject-rtos/zephyr/blob/6d9af839074ee70da0897450a62463e58a7515f9/subsys/testsuite/coverage/coverage.c#L223

@nashif any ideas about this one?

well, we never got c++ code to work with coverage, Zephyr is all C and the intention of coverage is C code primarily, so closing. If someone has time, patches to support C++ code are welcome.


refactor: simplify an if-statement

https://wiki.c2.com/?ReturnBooleanEvaluations

Thx, good catch 😄


[1.19.2] Crash on server startup

https://gist.github.com/BugmanBugman/c19f4535d4b1e49dfd6b3539d1e5de48

Same error, seems like it's asking for a client-side only library, is this mod abandoned? if that's the case at least put that on the main page :/


Narrowing overload for filter

In TS, Array.filter has an extra overload that supports narrowing the input type with a type predicate:
https://github.com/microsoft/TypeScript/blob/29c4b5e231e499cf506ea1c585d979b4d9d0459f/src/lib/es5.d.ts#L1234-L1245
Could wonka's filter do the same?  I wonder what flowgen would have to say about it, at least.

Cheers!


fix: try_unify no longer binds types on failure

Description
Problem*
Resolves #3089. This issue also affected impl search which uses try_unify to compare against every impl candidate. In some programs this could cause invalid type bindings, eventually leading to various mismatched/unexpected types panics during SSA.
Summary*
I've refactored try_unify to instead return a set of type bindings which must be applied afterward if the function was successful. Each caller of try_unify must do this manually now. Additionally, lookup_trait_implementation must now juggle several sets of type bindings and only commit to those that are not instantiation bindings (otherwise the generic trait would be permanently bound to another type), and even then only commit to them on success.
Additional Context
Documentation*
Check one:

[ ] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

can you add a regression test?

@kevaundray added a regression


#143: testing all routes for sufficient assigned roles

Closes https://github.com/Daimler/sechub/issues/143

Albert Weißert<EMAIL_ADDRESS>Daimler TSS GmbH, imprint

Review has been done, PR will be merged

Albert Tregnaghi<EMAIL_ADDRESS>Daimler TSS GmbH, imprint


Consider exporting AuthenticationError constructor?

First, thanks, passport is sooo handy :).
I'm asking about this just as a convenience in generic error handling code. It can be nice to switch on the error constructor:
// some-auth-module.js

const passport = require('passport')
const { AuthenticationError } = passport

// ...

module.exports = {
  authenticate: passport.authenticate('somestrategy', {
    failWithError: true
  }),

  handleAuthenticationError: (error, request, response, next) => {
    if (error.constructor === AuthenticationError) {
      return response.status(401).send({
        message: error.message
      })
    }

    return next(error)
  }
}

// my-app.js

app.post('/protected', authenticate, routeHandler)

app.use(handleAuthenticationError)
app.use(handleSomeOtherError)
// ... etc

Right now I'm requiring it from lib/errors from within Passport, which feels a little like a private api I'm digging around in.
Happy to continue doing so, if that's ok? Just thought I'd mention it. Happy to submit a PR if deemed a good idea.
Thanks, again.

I considered using it to check if something was a passport error (instanceof) instead of another error type, it should be safer than checking for a property that could not exist.


RYA-41 Fixed a bug where AccumuloIndexSet assumes the first node of a…

… ParsedQuery is always a Projection node.

Looks good.  I'll merge this on Sunday unless there are other concerns.


Pull request for allow-dynamic-fish_right_prompt-value

related: #186

v3.0.0: Support dynamic content for right prompt
:bomb:  Breaking Change
pure_right_prompt is now a function so its value can be re-evaluated on each rendering.
function pure_right_prompt
end

Some examples are available in fish_right_prompt.test.fish.
:information_source:: This is considered a major updated as we change the existing configuration API.

Todo:

[x] create 3.0.0 release note based on this content
[ ] merge
[ ] tag bump to 3.0.0 commit as v3.0.0 (can be done by github on merge?)
[ ] communicate

@edouard-lopez does it mean that instead of using
set pure_right_prompt 'something'

now this needs to be set as:
function pure_right_prompt
    something
end

?

@filipebarros once it's merged, yes. That's the only way I was able to re-evaluate the value.

Should that be part of the readme?

@filipebarros you are absolutely correct, readme need to be updated

Excellent point, I got carried away while trying to fix this but kept a weird feeling about it.
I will update, in coming days, the PR to remove the variable entirely and fall back to native behaviour.

@edouard-lopez @schrodincat any eta on this feature being merged?

🏓

🏓

@filipebarros sorry for the delay😓, I’ll update the PR tomorrow🤝


Fixing grammar error

Docs Build status updates of commit 5cd93f7:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/voice-commands/interact-with-a-background-app-in-cortana.md
:warning:Warning
View
Details

docs/voice-commands/interact-with-a-background-app-in-cortana.md

Line 10: [Warning-h1-not-first] Markdown content is not allowed before H1.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a11ddd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/voice-commands/interact-with-a-background-app-in-cortana.md
:bulb:Suggestion
View
Details

docs/voice-commands/interact-with-a-background-app-in-cortana.md

Line 48, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Feedback strings''. Each second level heading (H2) in an article must be unique.
Line 54, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Feedback strings''. Each second level heading (H2) in an article must be unique.
Line 60, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 67, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a11ddd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/voice-commands/interact-with-a-background-app-in-cortana.md
:bulb:Suggestion
View
Details

docs/voice-commands/interact-with-a-background-app-in-cortana.md

Line 48, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Feedback strings''. Each second level heading (H2) in an article must be unique.
Line 54, Column 1: [Suggestion-duplicate-headings] Duplicate heading: 'H2 'Feedback strings''. Each second level heading (H2) in an article must be unique.
Line 60, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 67, Column 1: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Bump apprise to 1.0.0

Changelog: https://github.com/caronc/apprise/releases/tag/v1.0.0
Compare: https://github.com/caronc/apprise/compare/v0.9.9...v1.0.0
For me especially interesting due to https://github.com/caronc/apprise/pull/627 (enabling better notifications to Home Assistant)

Thanks!


[Hooks] - stop further execution of definitions

Provide a method with public visibility that will stop execution of further definitions, for that particular hook.

Resolved.


Default IAM Groups to Require MFA

what

require_mfa should be true

https://github.com/cloudposse/terraform-root-modules/pull/26


nixos/yazi: add to module-list.nix

Description of changes
I'm so sorry. I forgot to add the file to the module-list in https://github.com/NixOS/nixpkgs/pull/253071.

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Probably needs meta.buildDocsInSandbox = false; in nixos/modules/programs/yazi.nix.

Yes, the version is used in the doc.

Fixed, thanks!


update dataset docs

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
The documentation has been modified accordingly, like docstring or example tutorials.

There 5 more comments in load more

There 5 more comments in load more

already added

new PR: https://github.com/open-mmlab/mmdetection/pull/8602


The creator of this open-source project has not been thanked sufficiently for their excellent contribution.

This is both well designed and well documented, and a wonderful example of an outstanding open source project.  My whole build went very smoothly thanks to your effort and your generosity, and of course the community of contributors who've chipped in / supported you.
A thousand thanks! Please close this whenever you like. But feel free to re-open it if you ever need a little encouragement for your efforts. They deserve to be acknowledged!

Completely agree! I have been following the activity for this project and Thomas is doing an amazing job.
I haven't built a Cheapino... yet... but I would like to do it sometime.

Thank you so much! I will keep the issue open a bit ;)

I 1000% agree. I have been always trying to spread the word to those who haven't used the board. Thomas, you make it so easy for beginners to build this board and give awesome instructions and support. I have been selling them for pretty much cost to those who don't want to build their own and everyone I speak with after loves their Cheapinos. I adore this little board and have gotten some of the best sounds of it the case of any of my ergo boards. Can't wait to see what you do next.

OK, this was thanks enough ;)


Error when packaging a contract

Hi,
I run below script to package smart contract:
docker exec -e CHANNEL_NAME=tradechannel -e CC_LANGUAGE=node -e CC_LABEL=trade -e CC_VERSION=v1 trade_cli cli_scripts/chaincode.sh package
There is error as:
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "cli_scripts/chaincode.sh": stat cli_scripts/chaincode.sh: no such file or directory: unknown
Any idea how to fix this?
Thx in advance,

It means your container doesn't have the cli_scripts/chaincode.sh file (i.e., it wasn't synced) in the expected location.


Dependency injection?

Hi! Sorry if this is a stupid question, but I've searched the documentation and it's very unclear to me how I can pass objects from outside Grape::API's scope through, say, a constructor, for dependency injection purposes?
I've tried using a bog-standard constructor, but a class derived from Grape::API doesn't seem to like being initialized:
class Foo < Grape::API
  def initialize(baz)
    @baz = baz
  end

  get :bar do
    @baz
  end
end

run Foo.new('hello') # ArgumentError

If I remove the .new call so it's just run Foo the constructor isn't even called, so @baz is obviously nil.
It seems configuration would be able to do this but it's incredibly unclear to me how to use it outside of mount, or, for that matter, when initialising the object which is what I want to do :)
There's also another, less related question. Are routes supposed to use symbols or strings? Or either? If it's either, is there a convention? That also isn't clear to me.
Thank you and I hope I'm not being too dense lol :p

The API is not the class being instantiated, you can check out the code in https://github.com/ruby-grape/grape/blob/45b12881f0a886f33d99f2f1d942a1ce9ef81171/lib/grape/api/instance.rb for how instances of the API get created, it's ... tricky.
It's a good question and we should write tests around this and document it. If you start on a PR and get blocked we can help you @unleashy.

@dblock what do you mean by env? just bog-standard ruby ENV?

Isn't Rack#run calling API#call(env)?

Yes. Well, it's called for every HTTP request. What about it?

It's a way to inject something, no? At least Rack uses that as default? I am not saying we should not do configure, but i would like to hear some opinions on why we shouldn't "just use ENV"?

I'm not sure how that would work. I can't see any way of injecting Rack's actual env without using a middleware (which is kinda onerous in my opinion). Of course, using ENV works fine:
# config.ru
require 'grape'

class API < Grape::API
  format :txt
  get '/' do
    ENV['hello']
  end
end

ENV['hello'] = 'bread'

run API

A GET / yields bread, as expected. Wait, actually, this could work fine lol so I think I see what you mean. Maybe #configure can use ENV:
API.configure do |config|
  config[:hello] = 'bread' # sets, idk, ENV['grape.config.hello'] = 'bread'
end

# ...

get '/' do
  configuration[:hello] # checks ENV['grape.config.hello'] as a last resort and tada, it exists
end

This would also fix the "non-inheritability" of the configure thingamajig. But, hmm, I'm not sure how elegant this API is; I mean, ENV is basically working as a kludgy dependency injection container. Thoughts?

Yes, ENV is a kudgy dependency injection container. I just wanted to bring this up as a thought, but I am not advocating for it.


DEMO: Gut the psbt module leaving just a POD type

The remaining type is still PSBTv0 but with this done it is easier now to port the stuff from psbt-v2 crate (which I used to do all the error stuff on this branch).
This took me a bunch of time and the likely can be improved, I tried to find a balance between showing something useful and ensuring the old logic was maintained.
You can just look at the final state, I wanted to keep it building during development and have an easy way to see what was done. (cargo test --all-features should work on every commit.)

This is too severe, trying something different.


Migrate utils/legacy.py::get_or_deploy_token to Transaction Service

Migrate the following function to the transactions service:
https://github.com/raiden-network/scenario-player/blob/5c0f7a9d0661c864e7a662591d6a08d5cb44cda9/scenario_player/utils/legacy.py#L193
Specifically, Lines https://github.com/raiden-network/scenario-player/blob/5c0f7a9d0661c864e7a662591d6a08d5cb44cda9/scenario_player/utils/legacy.py#L214 and  https://github.com/raiden-network/scenario-player/blob/5c0f7a9d0661c864e7a662591d6a08d5cb44cda9/scenario_player/utils/legacy.py#L232 need to be moved. The function itself may remain.

implemented with release 0.2.0


Bug: Eqmac attempts to mount its disk image whenever the application icon is clicked

This gets annoying, because whenever I eject it, it reopens when I try to change an eq setting. Please fix

I am having this issue too. Copied the app to my applications folder and unmounted the disk image. Always remounts the image when I load the app.

fixed by quitting app, unmounting image, and deleting the image from within /volumes

Hey everyone. Excuse me for the lack of updates. I have been really busy on the new version of eqMac. I am happy to announce an open beta release.
You can download it here: https://eqmac.app
There are a lot of known bugs that I could not fix just yet:

Driver not installing from the first try. Sometimes need to restart eqMac a couple times.
Complex Device switching logic is not perfect (for example when switching off the device that's currently playing, plugging in new device etc.)
UI takes long to load (a lot can be done to improve that)
UI dimensions are not synching properly
There's a noticeable audio delay in the playback, so not suitable for video yet (I know where the problem lies just haven't had the time to fix yet)
Sometimes the playback doesn't start, in that case please try to switch the output to the device you want and eqMac should try and build the audio pipeline again.

So as you can see there's still some work to be done but at least it's a completely modern tech stack that I am fully willing to work on: 100% Swift, User Space driver and a Web UI, instead of C++, Kernel Drivers. As I said, should work on Catalina and should not have any pesky ear drum blasting volume bugs (at least I didn't come across any).
I'm open to feedback and issue reports here: https://github.com/bitgapp/eqmac
That repo will become the main repo for eqMac and this repo will be archived eventually.
And yes it's called just eqMac, not eqMac3 :) And it will stay that way forever.

Hey everyone 👋
I will be open sourcing the new version of eqMac, therefore, I am closing this issue and repository as I will be transfering nodeful/eqMac2 repo to bitgapp/eqMac
Please bear with me for the next couple of days as I setup that new repo. The eqMac2 code will be living in the old-eqMac2 branch if anyone is interested in referencing it for whatever reason.
Please try out the new version and report bugs to the new repo.
Thanks for using eqMac.


Minimal bundle luaLibImport option

This adds the option "require-minimal" to luaLibImport.
With this, the emitted lualib_bundle.lua only contains used features.
This does a text search on all resolved (lua) files to determine which lualib features were used, so that projects which import lua libraries using lualib features still work.

is it expensive? if not, then should we have it turned on unconditionally?

is it expensive? if not, then should we have it turned on unconditionally?

Omitting part of the lualib has a higher chance of breaking things and causing runtime errors. Maybe after a while we can make this the default, but for now I think this is correct as opt-in.

@GlassBricks It needs to be added to the webpage too: https://typescripttolua.github.io/docs/configuration


Add authentication module

This adds an authentication module to be included into API controllers and allows for tokens to be provided using one of:

Query string parameter token
Authorization: Bearer <token> header
X-Token header

Eep, race conditions. Will have a look at this :+1:


video Background Scroll

Project title
Scroll Video
Project Description
(Describe the project over here)
Stack:
And in order to tick the check box just but x inside them for example - [x] like this. Please delete options that are not relevant.

[x] Html
[x] CSS
[x] JavaScript
[] ReactJS

/assign


Cluster creation failed

Hi,
Tried to provision standard cluster using below template and failed after some time as shown below. Any inputs really helps. Thank you
resource "confluentcloud_kafka_cluster" "cluster" {
name             = var.cluster_name
service_provider = "azure"
region           = "westus2"
availability     = "HIGH"
environment_id   = module.environment.environment_id
deployment = {
sku = "STANDARD"
}
}

_....
confluentcloud_kafka_cluster.cluster: Still creating... [18m30s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [18m40s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [18m50s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [19m0s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [19m10s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [19m20s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [19m30s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [19m40s elapsed]
confluentcloud_kafka_cluster.cluster: Still creating... [19m50s elapsed]
Error: Error waiting for cluster (lkc-132dv) to be ready: context deadline exceeded
on main.tf line 40, in resource "confluentcloud_kafka_cluster" "cluster":
40: resource "confluentcloud_kafka_cluster" "cluster" {
Makefile:149: recipe for target 'apply_dev1_westus2_confluent_kafka_test' failed
make: *** [apply_dev1_westus2_confluent_kafka_test] Error 1_

Cluster was created. But, not sure why terraform apply got timed out/failed with below error
Error: Error waiting for cluster (lkc-132dv) to be ready: context deadline exceeded

Could some one assist on this please ? Tried with below version (Terraform 0.13v)
terraform {
required_providers {
confluentcloud = {
source = "Mongey/confluentcloud"
}
kafka = {
source  = "Mongey/kafka"
#version = "0.2.11"
}
}
}

While trying to create a dedicated Confluent cluster, I get the same timeout at around 20 minutes into creation. Similarly to the case of @NareshAnaparthi, cluster got created in the end, but Terraform failed.
Parameters:

dedicated cluster
2 ckus
high availability
AWS, us-east-1
TF version: 0.13
provider version: 0.0.12

As per Confluent documentation, it can take up to 24 hours in order to provision dedicated clusters. @Mongey, is it possible to parametrize timeout for cluster types in order to allow more time for creation of dedicated clusters? @NareshAnaparthi, did you end up finding a way to work around this issue?
Console output:
19:42:53  confluentcloud_kafka_cluster.cluster: Still creating... [19m20s elapsed]
19:43:02  confluentcloud_kafka_cluster.cluster: Still creating... [19m30s elapsed]
19:43:11  confluentcloud_kafka_cluster.cluster: Still creating... [19m40s elapsed]
19:43:23  confluentcloud_kafka_cluster.cluster: Still creating... [19m50s elapsed]
19:43:32
19:43:32  Error: Error waiting for cluster (lkc-123abc) to be ready: context deadline exceeded
19:43:32
19:43:32    with confluentcloud_kafka_cluster.cluster,
19:43:32    on confluent-cluster.tf line 7, in resource "confluentcloud_kafka_cluster" "cluster":
19:43:32     7: resource "confluentcloud_kafka_cluster" "cluster" {

Since the PR, which fixes the issue, has been accepted, the only thing remaining is a new release.
@Mongey, could you tell us when we can expect one?


Not finding "related" service for a pod

I have a service:
Name:                     kubeview-nginx
Namespace:                kubeview
Labels:                   app=kubeview
                          app.kubernetes.io/managed-by=Helm
                          chart=kubeview-1.0.0
                          heritage=Helm
                          release=kubeview
Annotations:              meta.helm.sh/release-name: kubeview
                          meta.helm.sh/release-namespace: kubeview
Selector:                 app=kubeview-nginx
Type:                     LoadBalancer
IP:                       <IP_ADDRESS>
IP:                       <redacted>
LoadBalancer Ingress:    <redacted>
Port:                     http  80/TCP
TargetPort:               http/TCP
NodePort:                 http  30445/TCP
Endpoints:                <IP_ADDRESS>:80
Port:                     https  443/TCP
TargetPort:               https/TCP
NodePort:                 https  30345/TCP
Endpoints:                <IP_ADDRESS>:443
Session Affinity:         None
External Traffic Policy:  Cluster
Events:                   <none>

...that I think should be counted as "related" this pod:
Name:         kubeview-nginx-6b64cdc4f5-2zg86
Namespace:    kubeview
Priority:     0
Node:        <redacted>
Start Time:   Thu, 11 Mar 2021 12:54:34 -0500
Labels:       app=kubeview-nginx
              pod-template-hash=6b64cdc4f5
              role=nginx
<snip>

Is there something we should do to make them link up?
(Neat plugin, thanks!)

Here "related" means related k8s resources, such as: ingress, service, HPA, etc.
I understand that what you describe is more of a pod info.

Ah, ok.  I may be misunderstanding what causes a pod to be "related" to a service.  In this case, the service has a selector of app=kubeview-nginx and the pod has that label.  Is there another criteria that makes them related?

The currently supported label are: app, release, k8s-app, app.kubernetes.io/name, and custom labels will be supported later.
Also, English is not my native language, so maybe my description is confusing, can you help me to describe the plugin better?

I think that @lhankinsgdl had the same/similar assumption as myself.
Where related would be that label selectors for a service for an example match the pod in question.
What in fact the plugin is doing is looking for resources sharing the same/similar labels as the pod its self.


Master

Docs Build status updates of commit 557b36e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

DocsLegal/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


CodecUnsupported

Hi, there is a way to add compatibility to other codecs for flv files that do not have H264 + AAC encoding?
error found:
[TransmuxingController] > DemuxException: type = CodecUnsupported, info = Flv: Unsupported codec in video frame: 4
Error: Uncaught, unspecified "error" event. (MediaError)

the library does not work with internet explorer(11): I tested with a video.flv with h263 encoding and mp3 audio; the same video file converted to h264 video & mp3 audio is played correctly with firefox, chrome, edge but not msie; I converting the file to h264 + aac and no browser reproduces audio

同样遇到此问题


[BULK] - DocuTune remediation - Sensitive terms with GUIDs (part 29)

Applying sensitive terms with GUID changes as part of Content SFI and outlined in Overview - Writing content securely - Platform Manual. Changes are part of the Microsoft-wide SFI effort. Point of contact: @CelesteDG
DocuTune v<IP_ADDRESS>
CorrelationId: ac15aa43-4e2b-437f-ab1c-fdd7e79cd4db
#docutune

#docutune-review

LGTM


Added comment explaining discrepancy in the field names.

When changing the crypto keys back from bn254 to bls12_381, we forgot to rename the proto fields as well. It is not feasible to do it now, because of backward compatibility, so I've just added comments to explain the discrepancy.

Why can't we change it in a backwards compatible way?

Also, is the field name visible only in code? I guess not, it's probably visible in logs too.

we store commitqc in postgres in jsonb format

Ok. But why can't we change the name?

because the commitqc contains a signature which contains this field. Jsonb uses the text names in encoding.


Fix runner saving

This fixes #225 by not saving unless asked to.

As commented on https://github.com/sustainable-processes/summit/issues/225#issuecomment-1344191996, this seems working for me.


Containers should fail when can_connect is false

This currently passes:
import ops

import scenario

class MyCharm(ops.CharmBase):
    def __init__(self, framework):
        super().__init__(framework)
        framework.observe(self.on.config_changed, self._on_config_changed)

    def _on_config_changed(self, event):
        self.unit.get_container("example").replan()

ctx = scenario.Context(
    MyCharm,
    meta={"name": "my-charm", "containers": {"example": {"resource": "ubuntu-22.04"}}},
)
container = scenario.Container("example", can_connect=False)
state = scenario.State(containers=[container])
out = ctx.run("config-changed", state=state)

However, if the container can't be connected to (can_connect=False), then the replan() should really fail, because that's what would really happen.
The current system works if you have code like:
def _handle(self, event):
    if not self.container.can_connect():
        event.defer()
    try:
        self.container.replan()
    except ops.pebble.ConnectionError:
        event.defer()

But it does not if you adjust that to be like this, avoiding the pointless can_connect call:
def _handle(self, event):
    try:
        self.container.replan()
    except ops.pebble.ConnectionError:
        event.defer()

If you're only testing the positive case, then it doesn't matter, but to test the negative case, you'd currently have to mock the replan() call.
It seems to me that the scenario.Container attributes/methods should fail when can_connect is false, if they would also fail if Pebble was not working in a deployment. Not sure if you agree @PietroPasotti?

I definitely agree and I cannot reproduce that locally. What scenario version are you running?
This test passes on main:
def test_pebble_operations_fail_if_container_cannot_connect():
    ctx = Context(
        CharmBase,
        meta={
            "name": "my-charm",
            "containers": {"example": {"resource": "ubuntu-22.04"}},
        },
    )
    container = Container("example", can_connect=False)
    with ctx.manager("update-status", State(containers=[container])) as mgr:
        container = mgr.charm.unit.get_container("example")
        assert not container.can_connect()

        for call, args in (
            ("start", ("foo",)),
            ("restart", ("foo",)),
            ("stop", ("foo")),
            ("autostart", ()),
            ("replan", ()),
        ):
            with pytest.raises(pebble.ConnectionError):
                getattr(container, call)(*args)

Sorry, my bad :disappointed:. I only did a very quick check (while working on docs that discourage always guarding with can_connect() and missed that Scenario absorbs exceptions silently.
ie. in Harness I can do this:
h = ops.testing.Harness(MyCharm, meta="""
name: my-charm
containers:
  example:
    resource: ubuntu-22.04
""")
h.begin()
try:
    h.charm.on.config_changed.emit()
finally:
    h.cleanup()

And run it directly and it'll output a traceback to stderr and exit non-zero. With Scenario, there's no output (although the exit code is non-zero - I missed that).
Lesson learned: I will properly do pytests even when quickly checking something in the future :smile:.

Well maybe that's one thing to fix then, should we add some error logging?

Well maybe that's one thing to fix then, should we add some error logging?

Yeah, maybe. What's happening is that ops.log.setup_root_logging() sets up an except hook to redirect any unhandled exceptions to Juju's log, and Scenario captures everything that should go to the Juju log.

Well maybe that's one thing to fix then, should we add some error logging?

Yeah, maybe. What's happening is that ops.log.setup_root_logging() sets up an except hook to redirect any unhandled exceptions to Juju's log, and Scenario captures everything that should go to the Juju log.
I'm not sure that's really desired behaviour? You don't get to inspect the output state .logs because the process has crashed. When doing things the proper way and running under pytest, pytest catches the error and handles it appropriately.
Maybe after Scenario calls setup_root_logging it could do a sys.excepthook = sys.__excepthook__?

mmm, I was hoping to keep scenario testing framework agnostic

mmm, I was hoping to keep scenario testing framework agnostic

Resetting sys.excepthook would keep it agnostic. Or I think it might be ok to have setup_root_logging have an argument to avoid setting it - but I would need to convince the team of that (including completely convincing myself).


reduce time for testing the benchmark plots

... by reducing the data in aggret_res_test1 and 2
It still needs to be tested if all lines of code are still hit using this test results.

Codecov Report

Merging #197 (91636c1) into master (b612b57) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #197   +/-   ##
=======================================
  Coverage   95.31%   95.31%
=======================================
  Files         124      124
  Lines        4158     4158
=======================================
  Hits         3963     3963
  Misses        195      195

Flag
Coverage Δ

unittests
95.31% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fixing MISRA violations for FreeRTOS_TCP* files

Fixing MISRA violations for FreeRTOS_TCP* files
Description

Test Steps

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run uncrustify


Work on task without being signed in

I cannot work on a task without being signed in.
I checked, osm.org allows you to modify (or, to be more specific, to open the area in JOSM) without being signed in. Would it be possible to do the same with MapRoulette? I kind of strongly dislike being identified on every site I visit.

MapRoulette is a tool for fixing things in OSM. You can't fix things in OSM without being signed in.
Technically you wouldn't need to be signed in to MapRoulette to see tasks and then edit them in OSM itself. MR benefits from users being signed in in a few different ways:

You can see who last changed the task status and get in touch with that user.
You can see who created a challenge and get in touch with that user.
We can see how many unique OSM users participate in challenges

Please note that we don't store anything about you in MapRoulette that is not already public through the OSM API (here's me) except for your actions in MR (changing statuses for tasks, mainly).
If you want you can retrieve tasks through the MapRoulette API to work on them:
curl -X GET -H "Content-Type: application/json" -H "Cache-Control: no-cache" -H "Postman-Token: 21cc7491-83c5-7fcf-2358-eaf51d023b90" "http://maproulette.org/api/v2/challenge/2419/tasks?limit=100"


reproducibility of paper

Hi Felix,
comparing the architectural details of Structure by Architecture: Disentangled
Representations without Regularization with the base configuration, there's no yaml configuration yet which reproduces the paper, is there? The latter creates an MLP w/o any convolutional blocks, also the activation function is ELU instead of Mish.

The demo config does not reproduce the paper results because it is primarily meant for users to check whether their environments are setup correctly. However, by modifying some of the other commands in the readme, you should be able to reproduce the results. For example, to train an SAE-12 model on 3D-shapes, you just have to replace the dataset: fig train hybrid a/e/conv12 a/d/strc/12 m/ae d/3ds (assuming you already have the dataset downloaded/formatted as discussed in the readme). Generally, all the dataset-specific information is in "config/d/" and can be referenced in a command with "d/".

I executed both
fig train hybrid a/e/conv12 a/d/strc/12 m/ae d/3ds --model.nonlin mish --download

and
fig train hybrid a/e/conv12 a/d/strc/12 m/ae d/3ds --model.nonlin mish --model.optim.lr 0.0005 --download

see notebook.
The latter should be the exact training setup of the paper.
The training loss does not seem to converge as expected.
On the other hand one cannot inspect the fid to verify this because there seem to be a bug:
failed to compute the Rec FID
Traceback (most recent call last):
  File "/usr/local/bin/fig", line 33, in <module>
    sys.exit(load_entry_point('omnifig', 'console_scripts', 'fig')())
  File "/usr/local/lib/python3.7/dist-packages/omnifig/top.py", line 42, in entry
    main(*argv, script_name=script_name)
  File "/usr/local/lib/python3.7/dist-packages/omnifig/top.py", line 62, in main
    out = project.run(config=config)
  File "/usr/local/lib/python3.7/dist-packages/omnifig/organization.py", line 324, in run
    return mode.run(config.sub('_meta'), config)
  File "/usr/local/lib/python3.7/dist-packages/omnifig/modes.py", line 47, in run
    return script_fn(config)
  File "/usr/local/lib/python3.7/dist-packages/omnilearn/op/training.py", line 395, in iterative_training
    output = run.evaluate()
  File "/usr/local/lib/python3.7/dist-packages/omnilearn/op/runs.py", line 713, in evaluate
    eval_out = model.evaluate(self, config=config)
  File "/usr/local/lib/python3.7/dist-packages/omnilearn/op/framework.py", line 193, in evaluate
    return self._evaluate(info, config, out=out)
  File "/home/learn_rep/src/methods.py", line 221, in _evaluate
    out = super()._evaluate(info, config, out=out)
  File "/home/learn_rep/src/methods.py", line 113, in _evaluate
    self._compute_fid(fid, generate_fn=_rec_gen, name='rec', out=out)
  File "/home/learn_rep/src/methods.py", line 87, in _compute_fid
    dist = out[key]
KeyError: 'rec_fid'


Question - How to render vision-camera-resize-plugin with useSkiaFrameProcessor

Hey, I have been playing around and trying to render the output of resizing the frame but unfortunately my implementation is returning null and I am not completely sure why.
I have this:
const resized = resize(frame, {
      scale: {
        width: 256,
        height: 256
      },
      crop: {
        y: 0,
        x: 0,
        width: frame.width,
        height: frame.width
      },
      pixelFormat: 'rgb',
      dataType: 'uint8'
    });

    const data = Skia.Data.fromBytes(resized);
    const img = Skia.Image.MakeImage(
      {
        width: 256,
        height: 256,
        alphaType: AlphaType.Opaque,
        colorType: ColorType.RGBA_8888,
      },
      data,
      4 * resized.length
    )

I can't figure out what should be the right 3rd parameter of MakeImage. And I guess that is why it is returning an error
This is the Skia Doc about that: https://shopify.github.io/react-native-skia/docs/images/#makeimage

I think RN Skia should throw useful errors (with messages) instead of swallowing it and returning null. Would be great if that can be changed.
But yea I guess you can only debug this via Skia logs, check the native adb logcat/Xcode logs to see what kind of error Skia throws.


Add x64 Linux build

Hi. I don't know if your Linux release is 32 or 64 but it exits with error code 139 (I call it via nodegin/tglib library) on my Ubuntu18.04 64bit
BTW the one form Bannerets works for me without problems.

Yas, I very much consider my linux binaries 64 bit:
$  objdump -f ./libtdjson.so | grep ^architecture
architecture: i386:x86-64, flags 0x00000150:

It looks like you have some other issue with the binary. Could you please help me to diagnose it?

@ForNeVeR Yes of course! just tell me what to do.
And thanks for objdump

Could you please share the code you run to reproduce the issue? I'll check it in my environment with my build of tdlib.
For now, we have some complaints from Debian users, but I still haven't enough time to research the situation. I was checking the binary on my Linux VM (it was Ubuntu 18.04 x64 I think), but the check procedure was convoluted enough, so I could easily miss something.

I don't run any special code. Even a basic auth doesn't work:
`const { Client } = require('tglib')
void async function() {
const client = new Client({
apiId: '269276',
apiHash: 'abcdefg2d7054557f8f8f80e7d3ea66e',
auth: {
type: 'user',
value: '+98123456789',
},
})
await client.ready
)}
`

I tested that binary with your code on Ubuntu 18.04 inside docker, it works for me.
https://github.com/Bannerets/tdlib-binaries/tree/master/1.2.0/linux64 is for different tdlib version (1.2.0), this may be the reason why it works.
Maybe try to increase verbosity level?
// ...
  const client = new Client({
    apiId: '269276',
    apiHash: 'abcdefg2d7054557f8f8f80e7d3ea66e',
    auth: {
      type: 'user',
      value: '+98123456789',
    },
    verbosityLevel: 5 // <--
  })
// ...

If you use tglib wrapper, logs should be somewhere in __tglib__/.../logs.txt file.

Hi @Bannerets , I'm aware about version difference but I thought it may be caused by some incompatibility with my system.
This is the log with high verbosity:
[ 3][t 4][1549531708.382018805][Td.cpp:4238][!Td][&td_requests]	Sending update: updateAuthorizationState {
  authorization_state = authorizationStateWaitTdlibParameters {
  }
}

[ 3][t 4][1549531708.448084831][Td.cpp:3308][!Td][&td_requests]	Receive request 1: setTdlibParameters {
  parameters = tdlibParameters {
    use_test_dc = false
    database_directory = "/home/morteza/td/__tglib__/1123450312/database"
    files_directory = "/home/morteza/td/__tglib__/1123450312/files"
    use_file_database = false
    use_chat_info_database = false
    use_message_database = true
    use_secret_chats = true
    api_id = 269276
    api_hash = "a370bba2d7054557c75eaf0e7d3ea66e"
    system_language_code = "en"
    device_model = "tglib"
    system_version = "2.1.1"
    application_version = "1.0"
    enable_storage_optimizer = true
    ignore_file_names = false
  }
}

[ 3][t 4][1549531708.658349752][Binlog.cpp:368][!Td]	Load: init encryption
[ 3][t 4][1549531708.696191549][Td.cpp:4238][!Td][&td_requests]	Sending update: updateAuthorizationState {
  authorization_state = authorizationStateWaitEncryptionKey {
    is_encrypted = true
  }
}

[ 3][t 4][1549531708.696281910][Td.cpp:4253][!Td][&td_requests]	Sending result for request 1: ok {
}

[ 3][t 4][1549531708.710051537][Td.cpp:3308][!Td][&td_requests]	Receive request 2: checkDatabaseEncryptionKey {
  encryption_key = bytes [0] { }
}

[ 3][t 4][1549531708.710254669][Binlog.cpp:368][!Td]	Load: init encryption

Hi @Bannerets , I'm aware about version difference but I thought it may be caused by some incompatibility with my system.
This is the log with high verbosity:
[ 3][t 4][1549531708.382018805][Td.cpp:4238][!Td][&td_requests]	Sending update: updateAuthorizationState {
  authorization_state = authorizationStateWaitTdlibParameters {
  }
}

[ 3][t 4][1549531708.448084831][Td.cpp:3308][!Td][&td_requests]	Receive request 1: setTdlibParameters {
  parameters = tdlibParameters {
    use_test_dc = false
    database_directory = "/home/morteza/td/__tglib__/1123450312/database"
    files_directory = "/home/morteza/td/__tglib__/1123450312/files"
    use_file_database = false
    use_chat_info_database = false
    use_message_database = true
    use_secret_chats = true
    api_id = 269276
    api_hash = "abcdba2d7054557c75eaf0e7d3ea66e"
    system_language_code = "en"
    device_model = "tglib"
    system_version = "2.1.1"
    application_version = "1.0"
    enable_storage_optimizer = true
    ignore_file_names = false
  }
}

[ 3][t 4][1549531708.658349752][Binlog.cpp:368][!Td]	Load: init encryption
[ 3][t 4][1549531708.696191549][Td.cpp:4238][!Td][&td_requests]	Sending update: updateAuthorizationState {
  authorization_state = authorizationStateWaitEncryptionKey {
    is_encrypted = true
  }
}

[ 3][t 4][1549531708.696281910][Td.cpp:4253][!Td][&td_requests]	Sending result for request 1: ok {
}

[ 3][t 4][1549531708.710051537][Td.cpp:3308][!Td][&td_requests]	Receive request 2: checkDatabaseEncryptionKey {
  encryption_key = bytes [0] { }
}

[ 3][t 4][1549531708.710254669][Binlog.cpp:368][!Td]	Load: init encryption

OpenSSL version incompatibility causes this. See https://github.com/tdlib/td/issues/259#issuecomment-397348244 and https://github.com/Bannerets/tdl/issues/7#issuecomment-397334932.

So to work with this binary I should test some downgrades in nvm node version...
Thank you for your detailed help @Bannerets . I'll be watchful if ForNeVeR wanted brought us a new compiled binary :)

I tested Node 8.9.4 . It is compiled against openssl 1.0.2n and it works properly with this binary. Not sure about 9.x versions.

One possible idea is to link static openssl.

Hello there
Toady at the morning I had an unsuccessful login attempt(cuz of 2 step login proccess). I had installed binaries from more than one repository so not sure about the source of this security threat. Here I just wanted to warn people about running recompiled binaries by third parties. Always run them by your responsibility.

Yes, that's a right idea anyways.
In defense of my repository, I could only mention that all the sources and the build infrastructure are open source, and I build official tdlib sources cloned from the official repo. Everyone are welcome to reproduce my binaries using the same sources and scripts (unless Appveyor build infrastructure or tdlib sources themselves got compormised, the resulting binaries should be more or less identical).

@ForNeVeR I have already tried Appveyor but didn't manage to compile. It seems that it doesn't have the build dependency 'gperf' installed. Could you please help me to compile it myself?

x64 Linux build has been added, for any additional problems please open new issues, and I am willing to accept any help in maintaining these.

Hello there Toady at the morning someone had an unsuccessful login attempt into my telegram account (cuz of 2 step login process). I had installed binaries from more than one repository so not sure about the source of this security threat. Here I just wanted to warn people about running compiled binaries by third parties. Always run them by your own responsibility.

I accidentally remembered of this old issue. Here I just wanted to mention: After this time, I had another similar observation (about a year ago). Finally turned out it was some unsuccessful spying activity from the state guys (IR). I'm not a so called activist or something. Their behavior regarding regular citizens is offensive and malicious.
Sorry for possible annoying, if any. @Bannerets @ForNever

@mortezae,
First of all, this is a strange place to report that.
Second: if you suspect the binaries from tdlib.native are compromise, then… well, technically that's possible. I am working to establish a very transparent process of building and uploading them (where everything is automated, built and tested on clean images and then published, so that anyone may check that the binaries weren't tampered with at any stage), but we aren't there yet, and we were even farther from there in 2019.
And yet, to the best of my knowledge, all the builds were fully automated even then (though some manual intervention was required and is still required for me to upload the resulting binaries, so there's that), and nobody approached me in these years about anything about these binaries being compromised.
As of now, I see no reason to consider tdlib.native's build process to have a security breach of any kind, at any moment in the past even.
If anything changes and I'm made aware of any such problems, I'll make sure to publish this information in a responsible way (as quickly as possible, while considering the safety of existing users).
Again, at the present day, there were no security incidents (or anything alike) reported to me. So, it is very possible that you were supposedly hacked via some other ways.
Lastly, if somebody was able to tamper with the binaries, wouldn't they be able to upload your cloud password to their servers? I'm not sure protocol allows that, but most likely, if someone owns the binaries, then they could make sure to do a successful attempt to breach into your account. While you have only reported an unsuccessful one.


[docs] 6.4.0 housekeeping

First pass. I'll come back to kitchen sink on another PR.

Woah thats cool ... Nice work @petecooper ...

Follow up with ImageOptim specifics:

That's all for this PR.

Wow @petecooper this is great! Thanks for the needed optimizations here!

@rafibomb - no sweat, happy to help.

@rafibomb @IamManchanda - is there a docs style guide, internal or public?

@petecooper There's some basic stuff here but it hasn't been updated in a while—it could use some work from other collaborators.
Any specific questions you have?

@gakimball Thank you - I'll take a closer look. No specific questions, just some proposals that may help uniformity overall.

Maybe we can try to use the best availble tool. At least PNGGauntlet produces some better results:

ImageOptim is not the best out there ;-)

Alright, @DanielRuf might be onto something here, so here's what I'm going to do:

close this PR, with a view to…
splitting the docs housekeeping into multiple PRs for sanity and avoid the current merge conflict
using >1 image optimiser for maximum refreshment in another PR


Introduce dedicated html based email template

Addresses #9
PR Checklist
Please fill in the appropriate checklist below (delete whatever is not relevant). These are the most common things requested on pull requests (PRs).

[x] This comment contains a description of changes (with reason)
[x] Referenced issue is linked

Description of changes
Since we want to include custom styling(bold text and hyperlinks) simply sending a text-based email is not going to cut it anymore. Therefore we need a dedicated HTML template containing the requested email message.
This template will be later filled via jsoup similiar to the offer pdf generation in tomato 🍅
Technical information
The underlying process (mailutilx or sendmail) expect the file content to be piped as a an input. For this reason the most convienient solution is to have a dedicated html file.

Current display:


BUG: "windows firewall" test looks for rule existance, but does not check firewall/rule states.

OS: Windows 7 Enterprise 64bit
Disclaimer: I'm an admin managing systems for multiple clients, so this is lightly colored by the need to securely allow this for a few client systems without requiring manual intervention on every system.
Issue summary:
The firewall test at app start is not properly verifying API access, and is  assuming that the existence of the "GPMDP PlaybackAPI" rule in the windows firewall means that it is properly configured, whether the windows firewall is in use or not.
Detailed Issue Description:
Every time users open the app with the playback api enabled and no windows firewall rule in place, the following message appears.

Just a heads up
The PlaybackAPI failed to start because Windows Firewall is blocking it. We can unblock it for you if you want, be warned, this may require admin privileges

However, not all users have access to the admin account to add this firewall rule; want to give a random app downloaded from the internet local admin access; or want to allow the local network to access the playback api (while still using it with a local script).
From testing, the app is only testing whether or not a firewall rule named "GPMDP PlaybackAPI" exists, does not look to see if the rule is enabled, and does not verify if the firewall itself is enabled. .
Adding a rule with this name to the windows firewall completely disables the popup message
Considerations and use cases:
Users should not need to add a rule to the windows firewall configs to stop the popup even when the firewall is disabled, and the app should give a warning when the rule is in place but not enabled or incorrectly configured.
Users with third party firewalls should still be able to use the api without needing to add a rule to the windows firewall.
Local users without local admin privileges and a third party firewall should not require the admin to add a rule to the unused windows firewall.
Lastly, if the above logic is corrected, users would need a way to explicitly disable the popup.
(for unusual configurations, such as restricting the playback API to programs running on the local machine, restricting control to specific systems on the local network, or when using a different firewall solution.)
Steps to Reproduce:
Preparation:

If not installing GPDMP for the first time

access windows firewall advanced menu (start > RUN > "wf.msc")
remove inbound rule "GPMDP PlaybackAPI"

Install GPDMP
In desktop settings: check  "enable playback API"
select "not right now"
close GPDMP

Testing - Firewall disabled:

disable windows firewall completely

open GPMDP
Expected result: No popup, since api is NOT restricted
Result: popup message stating that playback api is still blocked

Testing - Firewall enabled, rule disabled

Open GPMDP

Click "let's do this" (creating firewall rule)

close GPMDP

in wf.msc, disable firewall rule (right click: disable rule)

Open GPMDP
Expected result: Popup, since api is blocked
Result: No popup, leaving API only accessible to local loopback subnet (<IP_ADDRESS>/24)

Testing third party firewall:

System appears to do no verification other than the windows firewall rule, and the popup does not provide port numbers or any usable diagnostic information for users to configure their actual firewall.

Suggested solutions:
1) Correct testing logic to verify firewall rule is configured correctly
2) add an "i'm aware, now go away" option for users who are intentionally changing the config
3) Add a "more info" link to the popup that provides the port numbers required for the PAI to function.

OK so to TLDR this for me later
Use Case 1:
Firewall disabled, shouldn't popup
Use Case 2:
Rule disabled, should popup
Use Case 3:
Third party firewall, should somehow tell the user something??????
Use cases 1 and 2 I can handle quite easily.
Use case 3 seems a little harder to manager as I can't easily check whether the port is accessible externally and therefore can't warn the user if it is blocked by a third party firewall.  Any suggestions on how to handle this use case?

My initial thought is that you can mix case 1 and 3 together into a single instance, since most third party firewalls automatically disable the windows firewall.
So Firewall disabled: popup once with message including the port numbers and mentioning the firewall is off.
example message:
Just a heads up: GPMDP can't detect any firewall software running on this machine.
The playback API requires port 5672 to be open to your local network.
We normally offer to set this up for you, but since you don't appear to be using the windows firewall you may need to allow that port in your firewall or antivirus software if it isn't already working.
I've been up all night, so forgive me if I missed something obvious.

I manually added a firewall rule (because the german translation of the popup says it'll disable the firewall - which I didnt want to do). So addition to the TLDR:
Use Case 4: Manual Firewall Rule exists with "wrong" name
Can / Should this be detected?


Fix .main-trackInfo-artists not targetting the correct element

For context - seemingly after a Spotify update, .main-trackInfo-artists is not used for the currently playing song artist list (noticed since a plugin adding the next song as well still uses this class, and the date was misplaced). Replaced with classes that work, although might change in the future after a Spotify update.

Before class edit:

After class edit:

Hmm, strange. I have the latest version, and I don't currently have this issue. I do have a different issue on Linux that I am trying to fix as well.
I kind of wanted to refrain from using the weird jamble of letters as id or class as I heard that spotify wants to change them to words in the future. Maybe it has to be targeted more precisely.
If I may ask, what operating system are you using?

Currently on Windows 11, latest Spicetify version.
As for the hashes, it could be some CSS pre-processor or something else that Spotify uses? These do change just like on Discord, or any modern web app which uses some styling libraries. Not 100% Spotify uses those, but it's possible it's some webpack stuff.

I was also thinking the same thing, that was the exact reason why I didn't want to use those and just be more precise with the css selectors.
I did just committed some changes, so I'm hoping it changed something, It'll probably be updated in the marketplace tomorrow.
I'll also test the settings on both linux and windows to see if there are still some differences

It isn't fixed yet, i'll look into it later

Just noticed something else came up?

Yeah, that was because I added a separator option. If you change it, it will go back, but I forgot to add a default for that setting. Sorry😅

Just noticed, but the separators are a tad bit misplaced

Yeah I saw that as well, but I cannot seem to get the spacing just right, because it is very different on other devices, but i'll keep trying

Also, about the selector the extension uses... it seems to not work at all? .main-trackInfo-name seems to not be used by the current playing track anymore, while it is still used by the next track extension. There is no reference to it in the DOM except the extension

I don't really know what you mean by the selector not being used at all as I am on the latest version of both spotify and spicetify and I still have that selector.

And for the spacing, it is using this part as a reference where it uses 8px as spacing but it is a different spacing on linux for example:

I have changed some things regarding the spacing but haven't really testen on other devices and I think I am satisfied with the current configuration. I have also made the selectors more specific so I hope I have fixed the issue now, I think you can try it again tomorrow

Well, for the latest version of Windows, I have these values which fit nicely:

Song name - .main-nowPlayingWidget-nowPlaying:not(#upcomingSongDiv) .main-trackInfo-contentWrapper - padding-left: 4px;


Test: Sanity check vscode-pwa

Smoke tests and getting 👀 on the PWA extension. (cc @roblourens )

[ ] macOS @sandy081
[ ] linux @weinand
[ ] windows @chrmarti

Complexity: 4
Prerequisite

Install the latest js-debug-nightly extension from the marketplace.
Be on Insiders, of course :)

Node.js testing

Pick any Node.js project you have configured for debugging with VS Code
Prefix its launch config type with pwa-
Verify that you can launch the program and debug as usual:

The program launches
You can set breakpoints before and while the program is running, and they get hit
You can step into, out of functions.
Stack traces etc. display correctly.
Restarting the program works
Stopping the program works

Verify that you can attach to this Node.js process running in debug mode, and debug as usual.

Chrome testing

Pick any browser/Chrome project you have configured for debugging with VS Code
Prefix its launch config type with pwa-
Verify that you can launch the project and debug as usual:

The browser launches and opens your project
You can set breakpoints before and while the program is running, and they get hit
You can step into, out of functions.
Stack traces etc. display correctly.
Restarting the program should refresh the page
Stopping the program should close the browser

Verify that you can attach to a running browser with your project open.

Note that you need to launch Chrome with special flags for this, on my machine: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222 --user-data-dir=/tmp/chrome-debug

Extension Host testing

Pick any extension you have configured for debugging with VS Code
Prefix its launch config type with pwa-
Verify that you can launch the extension and debug as usual:

The extension host launches with your extension
You can set breakpoints before and while the program is running, and they get hit
You can step into, out of functions.
Stack traces etc. display correctly.
Restarting the extension reloads the extension host window
Stopping the program closes the extension host window

Please file issues at https://github.com/microsoft/vscode-pwa/
You can get a log using "trace": true in the launch config if needed

After 5 hours of testing vscode-pwa with node.js and extension debugging I've decided to stop because I had reached the Complexity level of 4.
I suggest that the other testers start with Chrome testing.


Possible race condition with loading components on startup

Home Assistant release (hass --version):
0.16.0.dev0
Python release (python3 --version):
Python 3.4.3
OSX
Component/platform:
sensor.template
switch.template
binary_sensor.template
Description of problem:
I seem to have a weird problem where sometimes my template components don't load.
I may have seen this with other components - but not 100% sure.
The two logs are moments apart with the same configuration.yaml
Working
$ grep ".template" home-assistant.log.working | grep loader
16-03-17 13:13:51 homeassistant.loader: Loaded sensor.template from homeassistant.components.sensor.template
16-03-17 13:13:57 homeassistant.loader: Loaded switch.template from homeassistant.components.switch.template
16-03-17 13:14:29 homeassistant.loader: Loaded binary_sensor.template from homeassistant.components.binary_sensor.template
16-03-17 13:14:33 homeassistant.loader: Loaded automation.template from homeassistant.components.automation.template

Not Working
$ grep ".template" home-assistant.log.not_working | grep loader
16-03-17 13:10:26 homeassistant.loader: Loaded binary_sensor.template from homeassistant.components.binary_sensor.template
16-03-17 13:11:00 homeassistant.loader: Loaded automation.template from homeassistant.components.automation.template

Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
binary_sensor: !include devices/binary_sensors.yaml

switch: !include devices/template_switch.yaml

sensor: !include devices/sensors.yaml

Full log (until all components have been loaded)
Working: http://pastebin.com/wtLSr4rg
Not working: http://pastebin.com/euz40n2m
Traceback (if applicable):

Additional info:

This is very weird. The templates are all Python code, no dependency on devices so I cannot see where we would get the flakiness from.

I've now also seen this with components other than templates. Has to restart my system multiple time to get all my components loaded.
The ones I noticed missing were (usually just one on each restart):-
switch.template
light.hue / discovery
vera

Seemed pretty random what was missing.
I rebooted the machine - and looks like things got better. So I guess it could be some type of resource issue.
Sadly no errors I can see in the log.
Was about to report discovery was broken in latest build until it randomly came back :-)

Restarting HA either using the resatart service or with ^C wasn't working.
I rebooted and everything came back fine.

We are having some issues with config right now - I added a fix last night that should resolve some issues. This has not to do with a race condition but the order of the config items which is not always following YAML order anymore. Will have a look at that later.

Looking more reproducible, reloading using the re-start service doesn't work - rebooting the machine - and the auto started hass is fine.
Haven't tried killing and restarting the whole hass service yet.

I was wrong - rebooting didn't load everything. In this case it failed to load sensor.template and discovery.
I restarted by stopping the hass service and everything started fine.
Current thinking is that the most likely services not to load are templates and discovery. Which I guess don't talk to devices on load...


drag&drop import panel

Add  drag&drop-behavior to import Text, URL or Files as VectorResources

as discussed reaching first steps of implementation (mimick further data-handling with emitting notifications) and is ready for a intermediate review

suggestion for the next step (store):
Slice: import
import.action:
* function: `importUrl(url)` -> `new EventLike({cdata:null,file:null, url:url})`

* function: `importFile(data)` -> `new EventLike({cdata:null,file:fileData, url:null})`

* function: `importText(data)` -> `new EventLike({cdata:data,file:null, url:null})`

import.reducer:
* IMPORT_ADDED -> store/import/latest -> (payload)->` {cdata:[string|null],file:[string|null], url:[string|null]}`

Wouldn't be two fields for (c)data and URL enough currently?
But If we would support binary data later, a mime-type field will be mandatory.

Just no to forget: we have to add an e2e test for <ba-dnd-import-panel> in page.spec.test


Reimburse tankbottoms.eth for jmill work

🍌 proposal to reimburse tankbottoms $5,000(in ETH) for past jmill reimbursement
(May 14, 2022)
action

reimburse tankbottoms.eth 0x5d95baEBB8412AD827287240A5c281E3bB30d27E for prior weeks of payment to jmill. US5,000(in ETH).
amount reflects jmill's estimates sans non-peel activity

rationale

transaction-hashes from etherscan

https://etherscan.io/tx/0x25e37ed285eb4e9387375e5a57da39ba0333449cff5e7d7386843b2e9c47beed
https://etherscan.io/tx/0xae38e81be6c40f87ac9ecdbe936abfbc7e225831be851b6ca95f7f140d4b9c2f

references to previous discord discussions

https://discord.com/channels/939317843059679252/974852790054690886/974853250178248864

additional discussions

https://discord.com/channels/775859454780244028/942522503258054686/966831596198051880
https://discord.com/channels/775859454780244028/942522503258054686/966835218994561045
https://discord.com/channels/775859454780244028/942522503258054686/968141363629674516
https://discord.com/channels/775859454780244028/942522503258054686/968652992452628521

support for jmill's work

https://discord.com/channels/939317843059679252/940436144997433356/970447513477865564

risks

tankbottoms' feelings are hurt and he follows up all future posts with a cartoon of a puppy dog with sad eyes
tankbottoms' uses the funds to level up Peel's discord with stickers of vegetables and fruits without traditional peels, thereby offending the community
tankbottoms' pretends to not have understood that retroactive reimbursements are not favored and does this continuously just to be annoying
jmills turns out to be a complete knob and actually subtracts value thereby being a complete waste of time and ETH

cc @Peeler (core team)

updated the proposal slightly. still contains the core points.

@tankbottoms thanks for the updates - I added them to the PR!
Also added you as a collaborator to the GitHub repo - you should be able to push changes directly to this branch now 🙏

Adding my support for this proposal ✅
(I'm the author of the PR and can't approve it)


using TFlite: ModuleNotFoundError: No module named '_tensorflow_wrap_interpreter_wrapper'

System information

Windows 10:
TensorFlow installed from pip:
TensorFlow version 1.12.0:
Python 3.6.8:

Failed when trying to run a mobilenet_v1_1.0_224.tflite model using tflite. So I copy the interpreter_test.py and run it. End up with 10 fails in 12 tests, all with the same error of '_tensorflow_wrap_interpreter_wrapper'.
Also, my D:\Python 36\Lib\site-packages\tensorflow\contrib\lite\python\interpreter_wrapper folder only has :
/pycache , tensorflow_wrap_interpreter_wrapper.py , __init__py
I rename the tensorflow_wrap_interpreter_wrapper.py and uploaded it to see if some one can help me.
tensorflow_wrap_interpreter_wrapper.txt
Error log
Traceback (most recent call last):
File "D:\Python 36\lib\site-packages\tensorflow\contrib\lite\python\interpreter_wrapper\tensorflow
_wrap_interpreter_wrapper.py", line 18, in swig_import_helper
fp, pathname, description = imp.find_module('_tensorflow_wrap_interpreter_wrapper', [dirname(f
ile)])
File "D:\Python 36\lib\imp.py", line 297, in find_module
raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named '_tensorflow_wrap_interpreter_wrapper'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "run_tflite.py", line 52, in
tflite_output = run(model_file, image_data)
File "run_tflite.py", line 16, in run
interpreter = interpreter_wrapper.Interpreter(model_path=model_file)
File "D:\Python 36\lib\site-packages\tensorflow\contrib\lite\python\interpreter.py", line 52, in _
init_
_interpreter_wrapper.InterpreterWrapper_CreateWrapperCPPFromFile(
File "D:\Python 36\lib\site-packages\tensorflow\python\util\lazy_loader.py", line 53, in __getattr
__
module = self._load()
File "D:\Python 36\lib\site-packages\tensorflow\python\util\lazy_loader.py", line 42, in load
module = importlib.import_module(self.name)
File "D:\Python 36\lib\importlib_init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 994, in _gcd_import
File "", line 971, in _find_and_load
File "", line 955, in _find_and_load_unlocked
File "", line 665, in _load_unlocked
File "", line 678, in exec_module
File "", line 219, in _call_with_frames_removed
File "D:\Python 36\lib\site-packages\tensorflow\contrib\lite\python\interpreter_wrapper\tensorflow
_wrap_interpreter_wrapper.py", line 28, in
_tensorflow_wrap_interpreter_wrapper = swig_import_helper()
File "D:\Python 36\lib\site-packages\tensorflow\contrib\lite\python\interpreter_wrapper\tensorflow
_wrap_interpreter_wrapper.py", line 20, in swig_import_helper
import _tensorflow_wrap_interpreter_wrapper
ModuleNotFoundError: No module named '_tensorflow_wrap_interpreter_wrapper'

I faced the same error.
You can try pip install tf-nightly.
It solved the issue in my case.
You may also need to change tf.contrib.lite.Interpreter to tf.lite.Interpreter

I faced the same error.
You can try pip install tf-nightly.
It solved the issue in my case.
You may also need to change tf.contrib.lite.Interpreter to tf.lite.Interpreter

It works in my case too ! Thanks a lot !

I think it was resolved. I am closing the issue. Please open a new ticket if you see similar issue again. Thanks!

So you need to install tf to use tfLite ?
I have followed the instructions from here to install tfLIte on a RBPi https://www.tensorflow.org/lite/guide/build_rpi
But, when I try to run some example code I get an "ImportError: No module named 'tensorflow' error  "

I'm not sure this is related, but when I installed tensorflow lite using https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/tools/pip_package
I needed to add the following files to Extension(sources=[...]):
'interpreter_wrapper/numpy.cc',
'interpreter_wrapper/python_error_reporter.cc',
'interpreter_wrapper/python_utils.cc',

https://github.com/tensorflow/tensorflow/blob/master/tensorflow/lite/tools/pip_package/setup.py#L125

I faced the same error.
You can try pip install tf-nightly.
It solved the issue in my case.
You may also need to change tf.contrib.lite.Interpreter to tf.lite.Interpreter

This works! You saved me. Thank you.


[BUG]: Typescript doesn't recognize One-To-One Relation

What version of drizzle-orm are you using?
^0.29.1
What version of drizzle-kit are you using?
^0.20.13
Describe the Bug
I'm encountering a TypeScript error when trying to access a related object property through Drizzle ORM relations. Although the runtime behavior is as expected and I receive the correct object in response, TypeScript reports an error indicating that the property does not exist.
Drizzle Schema of relevant tables and relation

TRPC Procedure and Correct Console Output for relational Object

Type Inspect

This could also just be a skill-issue due to this being the first time using drizzle. But I read the docs extensively and think my relations and tables should be fine.
Thanks for your help.
Expected behavior
Typescript should recognize that the field "tag" does indeed exist on "sticker" and not throw a type error.
Also, I don't get autocomplete when specifying the "with" relation.
Environment & setup
T3 Stack (App Router, Next 14), MySQL on Planetscale

If you're using Planetscale as the database, you cannot use foreign key constraints like you're doing here. Instead, you should just use the emulated relations that are already there. @philparzer

The line .references(() => tags.id) is a foreign key constraint
Code below is the emulated relation:

export const tagStickersRelation = relations(stickers, ({ one }) => ({
	tag: one(tags, {
		fields: [stickers.tagId],
		references: [tags.id],
	}),
}));

Maybe this also fixes your issues with Typescript.
More info here: https://planetscale.com/blog/working-with-related-data-using-drizzle-and-planetscale

I also tried your code with mysql2 and sqlite driver, but didn't get any issues with Typescript or what so ever. 😄

@LukaHietala thanks for the reply. Strange that you didnt get any errors, what setup did you use?
Regarding FK constraints. Planetscale recently added support for FK constraints

Do you have any other relations like this in your schema that are working?

Nah, TS breaks for all relational querys using "with" in the same way.

@philparzer, can you show the part of the code where you're creating the db object using the drizzle() function? Just to be sure that your setup is 100% correct and it's not a drizzle issue

@AndriiSherman

@philparzer Can you try adding the other side of the relation to your schema as well? Just to check if that solves the issue.
Meaning:
export const tagRelations = relations(tags, ({ one }) => ({
  sticker: one(stickers, {
    fields: [tags.id],
    references: [stickers.tagId]
  }
});

@Angelelz that suggestion didn't solve the problem.

I'm encountering the same issue using the pg-core driver. Getting TS errors with one-to-one relations for relational queries using "with," and the suggestions above also did not solve this issue for me.
<EMAIL_ADDRESS><EMAIL_ADDRESS>


e2e tests folder restructure

This PR reorganizes the e2e tests for better structure and reuse of helper functions.
Changes

New test_suite Package:

Moved all helpers, types, and non-test files to a new test_suite folder.
Split suite_helpers.go into several context-specific files in test_suite.

Transfer Test Update:

Now runs three times to cover each version of the CW721 contract.

Test File Refactor:

Replaced full_test.go with basic_test.go, using the new test suite structure.

@magiodev great job! thx a lot!