Remove hard time limit from vf2 passes in preset passmanagers

Summary
This commit removes the hard time limit from the preset passmanager. We
were previously setting two limits on the pass a call_limit parameter,
which is used to set the limit of internal state visits the vf2
implementation in retworkx will attempt before giving up, and a time
limit which sets a hard wall time limit that is checked after each
mapping to ensure we don't spend more than a specific amount of time on
trying to find an optimal mapping. As subgraph isomorphism is
NP-complete we could spend a very large amount of time trying to find
the next isomorphic mapping and both these limits were set to avoid a
situation where we spend hours in optimization level 1 trying to find a
better layout. However, as we've seen in #8017 setting a hard time limit
limits the level of reproducibility on the output of the transpiler. It
means that setting a fixed seed is no longer sufficient to exactly
reproduce the output as it's also partially a function of the
performance of the local system we're running on. If the local
environment is slower we might get different results because we've hit
the hard time limit.
To address this, this commit removes the hard time limit so that we only
rely on the call limit parameter on the preset pass manager. While this
parameter is a bit more opaque in how it should be used because it
requires an understanding of how the VF2 algorithm works (and is
implemented in retworkx) it should be sufficient to avoid the runaway
execution problem but also means the limits are deterministically
applied. This should improve the reproducibility of the transpiler because
the pass will always try exactly up until a given point regardless of
how fast the local environment is.
For people manually instantiating the pass they can still rely on the
hard time limit parameter if they want it, but for the preset pass
managers and the transpile() function we no longer set this.
Details and comments
Fixes #8017

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.008%) to 84.349%

Files with Coverage Reduction
New Missed Lines
%

qiskit/transpiler/passes/layout/vf2_post_layout.py
2
96.28%

qiskit/pulse/library/waveform.py
3
89.36%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
54476

Relevant Lines:
64584

💛  - Coveralls


Issue with DisplayPort resolution

Maximum available resolution for an external DisplayPort display connected to Surface Dock is 3840x1080.
With the old firmware I got 5120x1440! Connecting the monitor directly to the Surface Pro 6 is a workaround for the moment.
I hope Microsoft will fix this issue.

@officedocsbot assign @jvsam

@jansppenrade2. Please send  feedback, report the issue from your laptop or desktop

Thank you for taking the time to share your feedback @jansppenrade2, we appreciate it. I  encourage you to submit this on UserVoice. This way, your feedback goes directly to the Microsoft product team and I assure you, they would love to hear what you think. If there's already a request, suggestion or feedback similar to yours, you can add your vote to the request. Thank you.

@jansppenrade2 : Please note that this site is made for reporting issues in the Microsoft documentation pages. From my experience, it is much better to report software issues using the Feedback feature on your Desktop or via UserVoice as jvsam recommended. Wishing you all the best.

Hi again @jansppenrade2, we will now close this issue, but if you have feedback or suggestions to help improve the quality of the technical documentation of Microsoft Docs, please inform us or use the doc's feedback feature.
Thank you for your feedback and for being part of the Microsoft Docs community!

@officedocsbot close


Maybe router prefix should can be regexp?

I wanna versioning API via url prefix, something like this:
/api/path
/api/v1/path
/api/v2/path

Does koa-router has design limitations about it? If not, I can figure it out and make PR.

koa-router supports prefixes out of the box. I don't think regex prefixes would add a lot of value. Prefixes are typically explicit (as versions of an api, for example). What you're describing is possible with koa-router.


Event Webhook inconsistencies

http://community.sendgrid.com/sendgrid/topics/inconsistencies_with_the_events_notification_webhook_documentation
a: I think sg_event_id is an internal tag only; I just did a Test Post, and it's not on any of the events.
b: smtp-id should be on all delivery events, and needs to be documented. This is an id attached by the originating system, so is a good way to trace the full message.
c: sg_message_id is our internal metric, and not sure why it's being transmitted,. can be safely ignored.
d: it's really 1 connection per server per second, which means it can get up to 12-15 per second. each server has it's own queue and logic, and we haven't tried to develop above that yet.

Sorry if I'm spamming. Just wanted to quickly ask (since I couldn't find any reference on the net):
My app requires to store an ID for webhook events (bounced, dropped). I was wondering what id should I prefer: if sg_event_id, or sg_message_id. Is there any meaningful difference between them? Can I query your API given one of these IDs?
For context, we are migrating away from Mandrill, and they provide an ID which we can use to later retrieve info about the failure thru their API.
Any comment will be much appreciated. Thanks.

sg_event_id will be unique to that event, and should be system unique. You can dedupe against it in the event you get double POSTs (rare, but can happen due to latency within SendGrid).
sg_message_id is unique the the message, and you should see multiple events per message.
You can't query our API either either of them. I would recommend storing both, as both are useful, but sg_event_id is your unique id if that's what you're looking for.

Thanks a lot!


WebParts not working

SPLoaderError.loadComponentError]:
***Failed to load component "89d609dd-9fb6-4353-aab4-6215ac1bb7f6" (Accordion). Original error: ***Failed to load URL 'https://spfx40fantastics.azureedge.net/spfx40fantastics/jqueryui_caedcd0d9b40346f7533890cb04acbbd.js' for resource 'jqueryui' in component '89d609dd-9fb6-4353-aab4-6215ac1bb7f6' (Accordion). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***INNERERROR:
***Failed to load URL 'https://spfx40fantastics.azureedge.net/spfx40fantastics/jqueryui_caedcd0d9b40346f7533890cb04acbbd.js' for resource 'jqueryui' in component '89d609dd-9fb6-4353-aab4-6215ac1bb7f6' (Accordion). There was a network problem. This may be a problem with a HTTPS certificate. Make sure you have the right certificate.
***CALLSTACK:
Error
at t [as constructor] (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-09-13.009/sp-pages-assembly_en-us_ec9244e0470ebea1d6ad4db7f56d00c0.js:4:53495)
at new t (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-09-13.009/sp-pages-assembly_en-us_ec9244e0470ebea1d6ad4db7f56d00c0.js:20:48986)
at Function.e.buildErrorWithVerboseLog (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-09-13.009/sp-pages-assembly_en-us_ec9244e0470ebea1d6ad4db7f56d00c0.js:20:112759)
at Function.e.buildLoadComponentError (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-09-13.009/sp-pages-assembly_en-us_ec9244e0470ebea1d6ad4db7f56d00c0.js:20:108790)
at https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-09-13.009/sp-pages-assembly_en-us_ec9244e0470ebea1d6ad4db7f56d00c0.js:20:45200
Saw this error was going around a couple of days ago and then saw it was supposedly fixed. However I am still getting this error for all of the web parts, I have tried adding them to a different tenant, removing the web parts and adding them again however I still get this error.
Is anyone experiencing this issue? And the people who managed to fix it did you have to do anything or just wait?
Cheers

Yes, all the apps have stopped working for us.Hopefully @OlivierCC is working on it.

@OlivierCC  : I think The CDN is down again :)

thanks, do you know when it will be back up?
On Fri, 27 Sep 2019 at 13:09, yazzouu<EMAIL_ADDRESS>wrote:

@OlivierCC https://github.com/OlivierCC : I think The CDN is down again
:)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/OlivierCC/spfx-40-fantastics/issues/110?email_source=notifications&email_token=AK2RDCFALE2WVFMGJJPZKHTQLXZY5A5CNFSM4I3DM5TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7YWBEA#issuecomment-535912592,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK2RDCG73VYB55GHCCYLIGLQLXZY5ANCNFSM4I3DM5TA
.

Same!!

Was fixed Yesterday but issue has returned this morning.

Same here!

Same here..I hope @OlivierCC looking into the issue...

Trying to contact @OlivierCC and asking him to make the deployed files available for download. So everyone can host the solution in their tenant to avoid the issue again.

Do you have any idea when it will come back to work properly? Thanks, Neiva

Thanks to @OlivierCC. It should back online now.

working again...Yay...Thank you @OlivierCC  @aaronmi


Update README.md: extend tested modems table

Add eSIM type and QMI APDU backend

@stich86 did you have a chance to look into?

@stich86 did you have a chance to look into?

I'm waiting other modules, so I'll add it to this PR and then merge it :)

Seems it's taking a long time.
Could we merge this already as it's about info we have already?

yes, i don't have an ETA for new modems to arrives..
so i'm merging it, then will add infos when i've done tests


Relative to the editor, not the current buffer

It would be great to have the fidget notifications shown on relative to the entire windows rather than to the current buffer.
For example, when you have two windows [NERDTree || foo.py || bar.py] and LSP messages are shown for a python buffer -- the notifications on the right bottom will move around as you switch to different windows. Even on the NERDTree windows as well (which is not a even LSP-related buffer).
Regarding this, I think showing status messages for the associated buffers only would also make sense (the current behavior is that all the messages would be shown in the current active window), but this could be tracked as a different issue.

#18 doesn't directly implement your suggestion, but should at least suppress notifications on unrelated buffers.
I was going to attempt your suggestion to make the position/alignment relative to the whole editor, until (1) I couldn't figure out how to obtain the editor height (I probably just need to dig through more documentation), and (2) it would still cause LSP messages to be overlaid on top of unrelated buffers, say if you had [foo.py || bar.py || NERDTree].
Let me know #18 addresses your problem. I'm hoping not to position the fidgets globally, because that's beginning to overstep into popups/notifications territory.

I couldn't figure out how to obtain the editor height

vim.opt.lines:get() would get you the height, and vim.opt.columns:get() gets you the width.

Ah I didn't realize about lines, I was grepping around for "row" and "height" and turning up empty lol. Thanks!


Resolve Issues 176 & 177

Added support for underscore italics and bold
Fixed bug when landing page and about topic names might collide.

🕐
GitHub doesn't recognize email on these commits.

Consider add this email to your profile as a secondary email


Daikin AC - Select "Minimum" fan speed, then automatically changes to "Medium-Low"

Hello,
Firstly, HUGE THANKS to everyone working on this project.  I can't express how useful this integration's been for my smart home setup here in Japan, having all five of my air conditioners (two Mitsubishi, three Daikin) in HA and also fed through to Apple Home app via the HomeKit integration.  I've also just begun using light switches too via the supported Panasonic switch hub, which works perfectly too!
Back to the issue... My Daikin AC units (Risora) support seven fan speeds (Auto, Minimum, Medium-Low, Medium, Medium-High, High, Very-High) which I've verified through use of Daikin's iOS app and the unit's remote control.  When selecting "Minimum" in Daikin's app, the fan speed is selected correctly and remains there.  However, when using this integration, it correctly changes to fan speed "Minimum", but after a period of a few seconds, automatically changes to speed "Medium-Low", (regardless of the previous fan setting.)
I've attached a couple photos of the HA setup and logs to show how it's working.  The bottom two commands were triggered by the iOS app (showing how "Minimum" can be selected and remain selected.)  The commands above are all from HA.
If there's more information I can provide, please let me know how.  I'm a bit tech inclined, but if given instructions, I can follow them.
Thanks again for your continued support!

@MrFusion4 The minimum airflow value of the air conditioner may be low. Try adding "low" to your settings and observing.

Just tried adding "low" and switching to it.  Unfortunately, it produced the same result.
As I noted before, "minimum" is shown as set correctly in Home Assistant when triggered by the Daikin iOS app.

This is a very strange behavior and I don't know the cause. First, please obtain a debug log and let us know.
If you enable the debug log on this integration screen in HA, perform a series of operations, and then disable the debug log, you will be able to download the log. Please upload that log file here.

Uploaded as requested.  The first image shows the HA logbook, how I switched the fan speed to Medium, then to Minimum, and then it near instantly changed to Medium-Low.  The second & third images are from HA's log.

@MrFusion4 Can you upload a text file of the log?

Sure!
Log.txt

Interesting!  Thanks for checking.
I ran debug mode again and changed the mode to Minimum using the Daikin iOS app.  I put the logs in the file below, the top portion's the Home Assistant command for Minimum, while the bottom portion's generated from Daikin's app, which successfully makes the change.  Looking at these side-by-side, are there any noticeable differences?
HA Daikin Log.txt

If the device's fan speed is set correctly when you change from HA to minimum, then I think it's a bug in the device, because the response to the device's query is incorrect.
On the other hand, if the device's fan speed is not set correctly when you change from HA to minimum, then I think it doesn't support the minimum setting in the econet-lite protocol.

Daikin's object-specific property declaration for this product can be downloaded from the following page. The declaration has properties divided into two sections, upper and lower, and the range of air volume is different between the upper and lower sections. I don't understand the meaning of this division into upper and lower sections, but this may be related.
FireShot Capture 018 -  - .pdf

https://echonet.jp/introduce/gz-000855-2/
https://echonet.jp/wp/wp-content/uploads/obj_prop/GZ/GZ-000855/Implemented_Properties_(0x013001).pdf

This is most likely a specification limitation, so I'll close this for now, you can reopen it if you find a solution to this problem.

Thank you very much for finding that information!  I was able to test your conclusion, and it turns out you're correct.  To do so, I used a different iOS app (Mitsubishi HEMS HM-ST03, which was also the default app for use with my two Mitsubishi units) to control the Daikin units.  Mitsubishi's app allowed for selection of all 8 Echonet protocol specified speeds (listed in the app as "Auto" and "1" through "8".  When I selected "1" ("Minimum" as per spec) the unit immediately defaulted to "3" ("Medium-Low") setting.  So it appears that my unit does not support "Minimum" speed via Echonet protocol, and instead is able to set it only via Diakin's remote control and iOS apps.
Now that I know this information, I've written Daikin customer support.  They still push firmware updates periodically for my units, so I've requested they update their Echonet spec to include the "Minimum" setting next time.
Much appreciated.


postgres::Row::operator[]

postgres::Row::operator[] accepts a const std::string& as an argument. A more idiomatic approach would be to accept a std::string_view instead, as implemented in userver for json and e.t.

Row::operator[](const std::string&) eventually ends up in PQfnumber which expects a null-terminated string, so for now there's no way to improve the interface, unfortunately.
However, we are planning to vendor libpq at some point, and when it happens we could add a PQfnumber overload which accepts a string size.


Move APEX documentation to Eng hub

APEX requirements: https://eng.ms/docs/products/azure-developer-experience/onboard/requirements

Migrated by @ladonnaq. Closing.


The discovery chapter of wiki have some errors

https://github.com/alibaba/spring-cloud-alibaba/wiki/Nacos-discovery

example code

EndPoint
It's http://ip:port/actuator/nacosdiscovery, it's not http://ip:port/actuator/nacos-discovery

Thanks for your feedback, can you submit a pr to fix it?

Can I submit a pr for wiki page? is the page source in the spring-cloud-alibaba-docs? if it's over there i will submit a pr to fix this issue.


Timeout issue in TOP/RETR commands.

When executing Pop3Command.TOP() or Pop3Command.RETR() with timeout specified, it becomes unresponsive if timeout occurs during reception. Probably, a mechanism is needed to abort this._stream in the callback argument of socket.setTimeout() in Connection.js if this._stream exists.
Thanks!

When executing Pop3Command.TOP() or Pop3Command.RETR() with timeout specified, it becomes unresponsive if timeout occurs during reception. Probably, a mechanism is needed to abort this._stream in the callback argument of socket.setTimeout() in Connection.js if this._stream exists.
Thanks!

Hi, have you resolved this issue? I have also encountered similar issues

PRs are welcome, especially if accompanied by tests...

Hi, have you resolved this issue? I have also encountered similar issues

This problem still occurs. I got around this by extending Pop3Command and defining a RETR function that supports timeout, as shown below.
class Pop3CommandEx extends Pop3Command {
  async RETR2(msgNumber) {
    await this._connect();

    let stream;
    this.once('end', (err) => {
      if (!!err && !!stream && !stream.closed) stream.destroy();
    );

    [,stream] = await super.command('RETR', msgNumber);
    return stream2String(stream);
  }
}

PRs are welcome, especially if accompanied by tests...

I think the following points should probably be corrected, but I would appreciate it if someone could test it.
  connect () {
    const {host, port, tlsOptions, servername} = this;
    const socket = new Socket();
    socket.setKeepAlive(true);
    // eslint-disable-next-line promise/avoid-new -- Our own API
    return new Promise((
      /** @type {(val?: any) => void} */
      resolve,
      reject
    ) => {
      if (typeof this.timeout !== 'undefined') {
        socket.setTimeout(this.timeout, () => {
          const err = /** @type {Error & {eventName: "timeout"}} */ (
            new Error('timeout')
          );
          err.eventName = 'timeout';
          reject(err);
          if (this.listeners('end').length) {
            this.emit('end', err);
          }
          if (this.listeners('error').length) {
            this.emit('error', err);
          }
          if (this._stream && !this._stream.closed) this._stream.destroy(err);       ← added here
          /** @type {import('tls').TLSSocket} */ (this._socket).end();
          this._socket = null;
        });
      }


Tuning application logging parameters for ElasticSearch

Update Docker Filebeat for Multiline Log Support
Update version of ElasticSearch Curator (?)
Enabling clean up curation of ElasticSearch application logs
Setting up ElasticSearch disk space limitation to avoid corrupting ElasticSearch indexes when running out of disk space.
Reducing App Logging noise

Not gonna pursue this anymore as we are moving to OpenSearch.


Update CustomUserRepository.php

Updating to null coalescing op. Using ?? would throw a notice if the array key was empty.

Oh! That typo was me, thanks for fixing @joshcanhelp.

@tpenaranda - No problem. I reviewed the code so I should have caught it then :)

@joshcanhelp @stevehobbsdev is this PR still valid?

Revisiting this, not sure I understand the description of the work - we're saying that "using ?? would throw a notice if the array key was empty" but that's what PR code changes. Is the notice desirable? The ways it's worded makes me think not.
Also, what's a "notice" in this context? Are we talking about an interpretor warning?

This PR is a fix for a typo for the null coalescing operator. Double pipe is used on JS, not PHP so we have a syntax error here.
Then for 'name' => $profile['name'] || '' proper PHP syntax is 'name' => $profile['name'] ?? ''
Why the null coalescing there? I don't know but my guess is 'name' key could not exist on $profile and we want to skip the php warning/notice.
Thanks! @stevehobbsdev @lbalmaceda

@tpenaranda that makes sense, thanks for taking the time to explain it. I guess if the scope is not the proper one, then yes those values could be null/empty. I'd say it doesn't hurt to add this 👍


Examples of use

Could you add an example of GRFC used on its own, and with npmpub(lish) in the Readme?

Is this clear https://github.com/stylelint/stylelint/issues/15#issuecomment-145471004 ?


Calling Inspect.toInspector can pick wrong number types

This is a bit strange. The inlined version of Inspect.inspect can pick the wrong type. If it isn't inlined, everything works fine.
Run roc test Bug.roc:
interface Bug
    exposes []
    imports []

expect
    out = fn 7i32 8i32
    out == [7, 8]

fn = \startRow, endRow ->
    List.range { start: At startRow, end: At endRow }
    |> List.map \row ->
        # Broken, selects wrong type.
        x = Inspect.toInspector row |> Inspect.apply (Inspect.init {}) |> Inspect.toDbgStr

        # Delayed and functional.
        # x = Inspect.inspect row |> Inspect.toDbgStr
        row

Error message:
── TYPE MISMATCH ──────────────────────────────────────────────── /tmp/Bug.roc ─

This 1st argument to fn has an unexpected type:

6│      out = fn 7i32 8i32
                 ^^^^

The argument is an integer of type:

    I32

But fn needs its 1st argument to be:

    Int Signed64

── TYPE MISMATCH ──────────────────────────────────────────────── /tmp/Bug.roc ─

This expression has a type that does not implement the abilities it's expected to:

7│      out == [7, 8]
        ^^^

I can't generate an implementation of the Eq ability for

    List ?

In particular, an implementation for

    ?

cannot be generated.

────────────────────────────────────────────────────────────────────────────────


pin miniconda3 to 24.1.2-0 in torchserve Dockerfile

pin miniconda3 to 24.1.2-0 in torchserve Dockerfile
this is ~1mo old as per https://hub.docker.com/r/continuumio/miniconda3/tags
without this, it fails to find torch=2.0.0. if you try bumping that to 2.3.0, then you get a different error on mim install mmcv-full==1.7.0
➜  torchserve git:(main) docker build -t docker_torchserve .
[+] Building 1.3s (12/25)                                                                                docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.44kB                                                                                0.0s
 => resolve image config for docker-image://docker.io/docker/dockerfile:1.2                                                                                0.4s
 => CACHED docker-image://docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc                                                                                0.0s
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/continuumio/miniconda3:latest                                                                                0.2s
 => [ 1/19] FROM docker.io/continuumio/miniconda3@sha256:2016f249cdae34692a20d90fdb17432d07cf312992345d0e1e492bc36a12a35b                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 394B                                                                                0.0s
 => CACHED [ 2/19] RUN mkdir -p /usr/share/man/man1                                                                                0.0s
 => CACHED [ 3/19] RUN apt-get update &&     DEBIAN_FRONTEND=noninteractive apt-get install --no-install-recommends -y     ca-certificates     curl     python3-pip     vim     sudo     default-jre     git     gcc     build-essentia  0.0s
 => CACHED [ 4/19] RUN pip install openmim                                                                                0.0s
 => ERROR [ 5/19] RUN pip install torch==2.0.0                                                                                0.5s
------
 > [ 5/19] RUN pip install torch==2.0.0:
0.427 ERROR: Could not find a version that satisfies the requirement torch==2.0.0 (from versions: 2.2.0, 2.2.1, 2.2.2, 2.3.0)
0.427 ERROR: No matching distribution found for torch==2.0.0
------
Dockerfile:22
--------------------
  20 |     # install python dependencies
  21 |     RUN pip install openmim
  22 | >>> RUN pip install torch==2.0.0
  23 |     RUN mim install mmcv-full==1.7.0
  24 |     RUN pip install mmdet==2.27.0
--------------------
ERROR: failed to solve: process "/bin/sh -c pip install torch==2.0.0" did not complete successfully: exit code: 1
➜  torchserve git:(main) vim Dockerfile
➜  torchserve git:(main) ✗ git diff | cat
diff --git a/torchserve/Dockerfile b/torchserve/Dockerfile
index e02861e..e849b16 100644
--- a/torchserve/Dockerfile
+++ b/torchserve/Dockerfile
@@ -19,7 +19,7 @@ RUN apt-get update && \

 # install python dependencies
 RUN pip install openmim
-RUN pip install torch==2.0.0
+RUN pip install torch==2.3.0
 RUN mim install mmcv-full==1.7.0
 RUN pip install mmdet==2.27.0
 RUN pip install torchserve
➜  torchserve git:(main) ✗ docker build -t docker_torchserve .
[+] Building 0.6s (13/25)                                                                                docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.44kB                                                                                0.0s
 => resolve image config for docker-image://docker.io/docker/dockerfile:1.2                                                                                0.2s
 => CACHED docker-image://docker.io/docker/dockerfile:1.2@sha256:e2a8561e419ab1ba6b2fe6cbdf49fd92b95912df1cf7d313c3e2230a333fdbcc                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => [internal] load metadata for docker.io/continuumio/miniconda3:latest                                                                                0.1s
 => [ 1/19] FROM docker.io/continuumio/miniconda3@sha256:2016f249cdae34692a20d90fdb17432d07cf312992345d0e1e492bc36a12a35b                                                                                0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 39B                                                                                0.0s
 => CACHED [ 2/19] RUN mkdir -p /usr/share/man/man1                                                                                0.0s
 => CACHED [ 3/19] RUN apt-get update &&     DEBIAN_FRONTEND=noninteractive apt-get install --no-install-recommends -y     ca-certificates     curl     python3-pip     vim     sudo     default-jre     git     gcc     build-essentia  0.0s
 => CACHED [ 4/19] RUN pip install openmim                                                                                0.0s
 => CACHED [ 5/19] RUN pip install torch==2.3.0                                                                                0.0s
 => ERROR [ 6/19] RUN mim install mmcv-full==1.7.0                                                                                0.2s
------
 > [ 6/19] RUN mim install mmcv-full==1.7.0:
0.170 Traceback (most recent call last):
0.170   File "/opt/conda/bin/mim", line 5, in <module>
0.170     from mim.cli import cli
0.170   File "/opt/conda/lib/python3.12/site-packages/mim/__init__.py", line 10, in <module>
0.170     import setuptools  # noqa: F401
0.170     ^^^^^^^^^^^^^^^^^
0.170   File "/opt/conda/lib/python3.12/site-packages/setuptools/__init__.py", line 16, in <module>
0.171     import setuptools.version
0.171   File "/opt/conda/lib/python3.12/site-packages/setuptools/version.py", line 1, in <module>
0.171     import pkg_resources
0.171   File "/opt/conda/lib/python3.12/site-packages/pkg_resources/__init__.py", line 2172, in <module>
0.172     register_finder(pkgutil.ImpImporter, find_on_path)
0.172                     ^^^^^^^^^^^^^^^^^^^
0.172 AttributeError: module 'pkgutil' has no attribute 'ImpImporter'. Did you mean: 'zipimporter'?
------
Dockerfile:23
--------------------
  21 |     RUN pip install openmim
  22 |     RUN pip install torch==2.3.0
  23 | >>> RUN mim install mmcv-full==1.7.0
  24 |     RUN pip install mmdet==2.27.0
  25 |     RUN pip install torchserve
--------------------
ERROR: failed to solve: process "/bin/sh -c mim install mmcv-full==1.7.0" did not complete successfully: exit code: 1
➜  torchserve git:(main) ✗

i do not know enough to fix these dependencies forward, but by pinning miniconda3 i can get it running

possible 2.2.x will work, didn't try it

LGTM! Thanks for your contribution


[SECURITY] Fix Zip Slip Vulnerability

Security Vulnerability Fix
This pull request fixes a Zip Slip vulnerability either due to an insufficient, or missing guard when unzipping zip files.
Even if you deem, as the maintainer of this project, this is not necessarily fixing a security vulnerability, it is still, most likely, a valid security hardening.
Preamble
Impact
This issue allows a malicious zip file to potentially break out of the expected destination directory, writing contents into arbitrary locations on the file system.
Overwriting certain files/directories could allow an attacker to achieve remote code execution on a target system by exploiting this vulnerability.
Why?
The best description of Zip-Slip can be found in the white paper published by Snyk: Zip Slip Vulnerability
But I had a guard in place, why wasn't it sufficient?
If the changes you see are a change to the guard, not the addition of a new guard, this is probably because this code contains a Zip-Slip vulnerability due to a partial path traversal vulnerability.
To demonstrate this vulnerability, consider "/usr/outnot".startsWith("/usr/out").
The check is bypassed although /outnot is not under the /out directory.
It's important to understand that the terminating slash may be removed when using various String representations of the File object.
For example, on Linux, println(new File("/var")) will print /var, but println(new File("/var", "/") will print /var/;
however, println(new File("/var", "/").getCanonicalPath()) will print /var.
The Fix
Implementing a guard comparing paths with the method java.nio.files.Path#startsWith will adequately protect against this vulnerability.
For example: file.getCanonicalFile().toPath().startsWith(BASE_DIRECTORY) or file.getCanonicalFile().toPath().startsWith(BASE_DIRECTORY_FILE.getCanonicalFile().toPath())
Other Examples

CVE-2018-1002201 - zeroturnaround/zt-zip
CVE-2018-1002202 - srikanth-lingala/zip4j
CVE-2018-8009 - apache/hadoop

:arrow_right: Vulnerability Disclosure :arrow_left:
:wave: Vulnerability disclosure is a super important part of the vulnerability handling process and should not be skipped! This may be completely new to you, and that's okay, I'm here to assist!
First question, do we need to perform vulnerability disclosure? It depends!

Is the vulnerable code only in tests or example code? No disclosure required!
Is the vulnerable code in code shipped to your end users? Vulnerability disclosure is probably required!

For partial path traversal, consider if user-supplied input could ever flow to this logic. If user-supplied input could reach this conditional, it's  insufficient and, as such, most likely a vulnerability.
Vulnerability Disclosure How-To
You have a few options options to perform vulnerability disclosure. However, I'd like to suggest the following 2 options:

Request a CVE number from GitHub by creating a repository-level GitHub Security Advisory. This has the advantage that, if you provide sufficient information, GitHub will automatically generate Dependabot alerts for your downstream consumers, resolving this vulnerability more quickly.
Reach out to the team at Snyk to assist with CVE issuance. They can be reached at the Snyk's Disclosure Email. Note: Please include JLLeitschuh Disclosure in the subject of your email so it is not missed.

Detecting this and Future Vulnerabilities
You can automatically detect future vulnerabilities like this by enabling the free (for open-source) GitHub Action.
I'm not an employee of GitHub, I'm simply an open-source security researcher.
Source
This contribution was automatically generated with an OpenRewrite refactoring recipe, which was lovingly handcrafted to bring this security fix to your repository.
The source code that generated this PR can be found here:
Zip Slip
Why didn't you disclose privately (ie. coordinated disclosure)?
This PR was automatically generated, in-bulk, and sent to this project as well as many others, all at the same time.
This is technically what is called a "Full Disclosure" in vulnerability disclosure, and I agree it's less than ideal. If GitHub offered a way to create private pull requests to submit pull requests, I'd leverage it, but that infrastructure, sadly, doesn't exist yet.
The problem is that, as an open source software security researcher, I (exactly like open source maintainers), I only have so much time in a day. I'm able to find vulnerabilities impacting hundreds, or sometimes thousands of open source projects with tools like GitHub Code Search and CodeQL. The problem is that my knowledge of vulnerabilities doesn't scale very well.
Individualized vulnerability disclosure takes time and care. It's a long and tedious process, and I have a significant amount of experience with it (I have over 50 CVEs to my name). Even tracking down the reporting channel (email, Jira, etc..) can take time and isn't automatable. Unfortunately, when facing problems of this scale, individual reporting doesn't work well either.
Additionally, if I just spam out emails or issues, I'll just overwhelm already over-taxed maintainers, I don't want to do this either.
By creating a pull request, I am aiming to provide maintainers something highly actionable to actually fix the identified vulnerability; a pull request.
There's a larger discussion on this topic that can be found here:  https://github.com/JLLeitschuh/security-research/discussions/12
Opting Out
If you'd like to opt out of future automated security vulnerability fixes like this, please consider adding a file called
.github/GH-ROBOTS.txt to your repository with the line:
User-agent: JLLeitschuh/security-research
Disallow: *

This bot will respect the ROBOTS.txt format for future contributions.
Alternatively, if this project is no longer actively maintained, consider archiving the repository.
CLA Requirements
This section is only relevant if your project requires contributors to sign a Contributor License Agreement (CLA) for external contributions.
It is unlikely that I'll be able to directly sign CLAs. However, all contributed commits are already automatically signed off.

The meaning of a signoff depends on the project, but it typically certifies that committer has the rights to submit this work under the same license and agrees to a Developer Certificate of Origin
(see https://developercertificate.org/ for more information).
- Git Commit Signoff documentation

If signing your organization's CLA is a strict-requirement for merging this contribution, please feel free to close this PR.
Sponsorship & Support
This contribution is sponsored by HUMAN Security Inc. and the new Dan Kaminsky Fellowship, a fellowship created to celebrate Dan's memory and legacy by funding open-source work that makes the world a better (and more secure) place.
This PR was generated by Moderne, a free-for-open source SaaS offering that uses format-preserving AST transformations to fix bugs, standardize code style, apply best practices, migrate library versions, and fix common security vulnerabilities at scale.
Tracking
All PR's generated as part of this fix are tracked here: https://github.com/JLLeitschuh/security-research/issues/16

@JLLeitschuh I've no idea if it fixes somethings... but I know it didn't break things 😉

What files were being unzipped? Something that could be controlled by a user of TestNG, or was the file always something that could be verified to be safe?

The files are xml that are directly parsed

Can you elaborate a bit more here, I don't understand where the XML files come from

It comes from a jar produced by the user and available in the classpath at runtime during the tests run.

So, this file could theoretically come from an untrusted source? In that case, I would probably consider this a security vulnerability worth issuing a CVE number for.
Can you detail the scenario under which this logic is executed? I can reach out and have snyk issue a CVE number from there for you.

So, this file could theoretically come from an untrusted source? In that case, I would probably consider this a security vulnerability worth issuing a CVE number for.

What makes you think "a jar produced by the user" is an untrusted source?

Can you detail the scenario under which this logic is executed? I can reach out and have snyk issue a CVE number from there for you.

This is CVE-2022-4065, issued by VulDB.

Vulndb doesn't issue CVE numbers AFAIK.
Someone else must have done this

Do you believe the contents of the vulnerability disclosure as it reads currently is accurate?

They very certainly did, and they are indeed a CNA.
Based on the conversation here, mainly that the file that would exploit this vulnerability comes form the user, I do not agree that this is a 'critical' vulnerability which can be executed remotely, at least not without caveats. Though, correct me if I'm wrong.

If it can be exploited remotely, Zip Slip is considered critical in most scenarios because it can be used to achieve remote code execution. Remote code execution is possible because zip slip allows an attacker to write the contents of executable files into executed files/directories. For example, on windows there are files that, if placed in the correct directory, will automatically execute on login.

They very certainly did, and they are indeed a CNA.

I stand corrected, and I learned something new this evening.
Just a FYI, this is going to trigger a massive number of PRs from Dependabot, probably tomorrow.
This is why I asked the TestNG maintainers to be involved in the disclosure process multiple times. Because now someone else (Vuln DB) has come along and now controls the messaging going out about this vulnerability. Ideally this information should be coming from the maintainers directly to help provide the most clear information.

If it can be exploited remotely

Very big 'if'.
If you're worried about coordinated disclosure, why don't you begin by coordinating disclosure yourself rather than apparently automatedly filing PRs to fix vulnerabilities that you can't be sure are actually exploitable?

In any case, if anyone thinks the CVE is inaccurate, they can ask VulDB to correct it. They are receptive to feedback in my experience. In the worst case, the CVE still informs the public about the vulnerability and the patch for it even if the CVE description is less than accurate, so I'm not that concerned about it.

If you're worried about coordinated disclosure, why don't you begin by coordinating disclosure yourself rather than apparently automatedly filing PRs to fix vulnerabilities that you can't be sure are actually exploitable?

Vaild response. Touché. Given the number of cases of this vulnerability across open source (GitHub's CodeQL flags 900+ cases), and I'm attempting to actually fix these vulnerabilities at scale, (I've automatically generated 165 PRs for Zip Slip alone so far) it's unfortunately impractical to attempt to coordinate disclosure at that kind of scale.
I've often thought about attempting to automate the CVE issuance process, but I haven't yet, and I'm beginning to think that having a human in the loop in the general case for CVE issuance is better than attempting full automation.
I see what you're saying, and I welcome suggestions.

It would be useful if a release incorporating this change could be made. I am not sure I see this security fix as a critical issue, but Github has started spamming maintainers of packages that use testng whenever they push. Realise that its a pain to do so, but 7.6.2 would be appreciated.
Thanks for the work on testng, whatever you decide to do.

@bradh -We have done a release candidate build release and some of our early adopters are helping out with vetting it out as we speak. Once I hear back on them the release 7.7.0 will be done.
Please check here https://github.com/cbeust/testng/issues/2665#issuecomment-1339138206 for more details.

Is this really a security issue? It appears that this method is only used for handling the -testjar flag. I haven't used -testjar personally, but the docs (https://testng.org/doc/documentation-main.html#running-testng) indicate that "[...] all the test classes found in this jar file will be considered test classes."
If an attacker can feed a malicious jar into -testjar, they've already won. They don't need to craft a special zip file with a bad file header that causes a write to a file on disk that will executed at some random time in the future; they can just include a malicious test in said jar (which testng will happily run immediately).
(There's some discussion above, but not really a definite "this isn't a real issue")
Ref: https://github.com/cbeust/testng/blob/c0e1e772f1fc0ab2142f3a4114a2b8cfe60fa7e1/testng-core/src/main/java/org/testng/TestNG.java#L414-L420; m_jarPath in that context is fed from https://github.com/cbeust/testng/blob/c0e1e772f1fc0ab2142f3a4114a2b8cfe60fa7e1/testng-core/src/main/java/org/testng/TestNG.java#L1641

Did some testing with -testjar (using Java 8, since that's what I happen to have installed right now):
<!-- pom.xml -->
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>test</groupId>
  <artifactId>test</artifactId>
  <version>1.0</version>

  <properties>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
  </properties>

  <dependencies>
	  <dependency>
		  <groupId>org.testng</groupId>
		  <artifactId>testng</artifactId>
		  <version>7.5</version>
	  </dependency>
  </dependencies>
</project>

// src/main/java/EvilTest.java
import org.testng.annotations.Test;

public class EvilTest {
	@Test public void doEvil() {
		System.out.println("Hello, World!");
	}
}

$ mvn package exec:java -Dexec.mainClass=org.testng.TestNG -Dexec.arguments="-testjar,target/test-1.0.jar"
<snip>
[INFO] --- exec-maven-plugin:3.1.0:java (default-cli) @ test ---
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Hello, World!

@bradh - Just letting you know. TestNG 7.7.0 which contains this fix, is released to maven central.

Are there any plans to add a fix to the 7.5 release?

@starnowski - Not sure if we would be doing a patch for the earlier released versions. This is fixed in 7.7.0 Can you please upgrade to that instead ?

Hmm, currently one of our projects is built by maven and compiled with the java version. Fortunately, a project that uses the testng is a separate module that contains only tests and has a dependency on the main code. So I guess I could use a toolchain and change the compilation version to 11. Although I guess my case might not be the only one that uses java 8 in the project and in some cases it might be harder to update the java version.

Okay, I was able to solve my problem by using the maven toolchain (project pull-request) but I would still considered adding a patch to the testng version that works with java 8.

@cherylking I understand but we don't have enough free time or contributors to support many version branches.
But any contribution is welcome and we will enjoy helping if you or your company want to assume the support of a dedicated version branch.

Hey folks,
The CVE behind this issue was reported against Gradle build tool. We took the time to analyze it and you can read our findings.
tl;dr:

Only applicable to TestNG [6.13, 7.6.1]
Severity feels really inflated, planning to follow up on this. Conclusion in agreement with the comment from @jeffreytolar

Hi @ljacomet
Thanks for the analyze. You confirm what we supposed.
The good part is it forced some users to upgrade 😅
I'm glad to see you plan to upgrade too 👍 https://github.com/gradle/gradle/issues/24930
Could you explain why testng is embedded and not used from the classpath?
I remember an issue where it was a problem (@krmahadevan do you have the issue number in mind?)

@ljacomet - Here's the issue that @juherr is referring to https://github.com/gradle/gradle/issues/10507
This got closed automatically because it turned stale :(
And here's another one that I have created in TestNG, which is also due to Gradle bringing in an old version of TestNG as an embedded dependency
https://github.com/cbeust/testng/issues/2766


Make duckdb a Julia package

It would be great if duckdb is available for Julia users. Julia has a DBI interface:
https://github.com/JuliaDatabases/DBInterface.jl

See #208


Integrate hid-playstation for extended DualSense support?

Now that am officially available kernel module is available, has anyone discussed the possibility of integrating it into GamerOS? Im sure at some point, the kernel module will be in the mainline kernel, but it seems to me it would be worth including in an update to GamerOS without waiting for mainline kernel integration.

A DKMS package is available in the AUR, so it would indeed be very easy to add in the future release :
https://aur.archlinux.org/packages/hid-playstation-dkms/

A DKMS package is available in the AUR, so it would indeed be very easy to add in the future release :
https://aur.archlinux.org/packages/hid-playstation-dkms/

Yeah, I should have mentioned that, I did see that and tried it on my laptop, and it works very well! I’d install it on my HTPC if it also ran just straight arch, but since it’s running on GamerOS, I cant. The drawback of a super stable release system, I suppose.
Anyway, yeah, it should be easy, and that would get it some nice functionality.

Yeah, I should have mentioned that, I did see that and tried it on my laptop, and it works very well! I’d install it on my HTPC if it also ran just straight arch, but since it’s running on GamerOS, I cant. The drawback of a super stable release system, I suppose.
Anyway, yeah, it should be easy, and that would get it some nice functionality.

If you want to try it on GamerOS, you can access a shell with these instructions : https://github.com/gamer-os/gamer-os/wiki/GamerOS-Troubleshooting#how-can-i-access-a-shell
Then, run $ sudo frzr-unlock to get out of read-only mode, and you'll be able to install it like on regular Arch. We'd love some feedback !

If you want to try it on GamerOS, you can access a shell with these instructions : https://github.com/gamer-os/gamer-os/wiki/GamerOS-Troubleshooting#how-can-i-access-a-shell
Then, run $ sudo frzr-unlock to get out of read-only mode, and you'll be able to install it like on regular Arch. We'd love some feedback !

Oh, neat! I’ll try that out in the meantime, I didn’t know I could do that lol. I’ll leave my impressions here when I do :>

Oh, neat! I’ll try that out in the meantime, I didn’t know I could do that lol. I’ll leave my impressions here when I do :>

hid-playstation is mainlined since Linux 5.12, this can be closed.


Move most of the functionality of sound manager to sound system

Since the inception of the sound manager. The architecture has slightly changed.
Most of the functionality should probably go into a sound system.

"slightly" changed 😉

@feliwir We can use this ticket to discuss architecture with @GlPortal/technical-officers-engine

is this still active

@einsteinreloaded Nobody is working on it atm. and it might clash with what @ElementW is working on atm. so make sure to coordinate with him.

@einsteinreloaded However discussion and Design suggestions are already open so don't hold back on this.

While it might clash with my work if audio stuff is migrated to an ECS system (which I'm getting rid of), it probably will not if it is refactored/moved to basically any another class.


terraform-provider-flux_v1.0.0-rc.4 plugin crashes when importing flux_bootstrap_git.this

Unsure if the root cause is directly related to #487 and similar issues or not, so creating a separate issue.
I am attempting to run terraform import on an existing bootstrapped cluster which is created by an older version of the flux terraform provider, data "flux_sync" "this. and related resources.
Terraform version 1.4.6
flux provider version terraform-provider-flux_v1.0.0-rc.4.
Current in-cluster flux config is on  Version v1.0.0-rc.3
Relevant tf config:
provider "flux" {}

locals {
  base = file("${path.module}/fluxcd/templates/kustomization-base.yaml")
}

resource "flux_bootstrap_git" "this" {
  path                   = "clusters/${var.cluster_id}"
  network_policy         = false # some issues on AKS if set to true, likely due to git auth proxy.
  kustomization_override = local.base
  toleration_keys = [
    "CriticalAddonsOnly"
  ]
  disable_secret_creation = false # tbd
}

Output:

terraform import -var-file=config-dev.tfvars flux_bootstrap_git.this flux-system
Acquiring state lock. This may take a few moments...
flux_bootstrap_git.this: Importing from ID "flux-system"...

(...)
(various sucessful read operations)
(...)
╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the
│ plugin6.(*GRPCProvider).ValidateDataResourceConfig call. The plugin logs
│ may contain more details.
╵

╷
│ Error: Plugin did not respond
│
│ The plugin encountered an error, and failed to respond to the
│ plugin6.(*GRPCProvider).ValidateDataResourceConfig call. The plugin logs
│ may contain more details.
╵

╷
│ Error: Request cancelled
│
│ The plugin6.(*GRPCProvider).ImportResourceState request was cancelled.
╵

Releasing state lock. This may take a few moments...

Stack trace from the terraform-provider-flux_v1.0.0-rc.4 plugin:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x1a95bd8]

goroutine 13 [running]:
github.com/fluxcd/terraform-provider-flux/internal/provider.(*providerResourceData).GetKubernetesClient(0x416090?)
	github.com/fluxcd/terraform-provider-flux/internal/provider/provider_resource_data.go:64 +0x18
github.com/fluxcd/terraform-provider-flux/internal/provider.(*bootstrapGitResource).ImportState(0xc000130050, {0x221e8c0, 0xc000694570}, {{0xc0004e24a0?, 0x1f44e25?}}, 0xc000526960)
	github.com/fluxcd/terraform-provider-flux/internal/provider/resource_bootstrap_git.go:667 +0x6c
github.com/hashicorp/terraform-plugin-framework/internal/fwserver.(*Server).ImportResourceState(0xc000414840, {0x221e8c0, 0xc000694570}, 0xc0000a9c80, 0xc0004fd620)
	github.com/hashicorp/terraform-plugin-framework@v1.2.0/internal/fwserver/server_importresourcestate.go:104 +0x462
github.com/hashicorp/terraform-plugin-framework/internal/proto6server.(*Server).ImportResourceState(0xc000414840, {0x221e8c0?, 0xc000694420?}, 0xc0005101e0)
	github.com/hashicorp/terraform-plugin-framework@v1.2.0/internal/proto6server/server_importresourcestate.go:44 +0x30b
github.com/hashicorp/terraform-plugin-go/tfprotov6/tf6server.(*server).ImportResourceState(0xc0000c15e0, {0x221e8c0?, 0xc00050fad0?}, 0xc0005266e0)
	github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov6/tf6server/server.go:846 +0x1f6
github.com/hashicorp/terraform-plugin-go/tfprotov6/internal/tfplugin6._Provider_ImportResourceState_Handler({0x1e21060?, 0xc0000c15e0}, {0x221e8c0, 0xc00050fad0}, 0xc00036d180, 0x0)
	github.com/hashicorp/terraform-plugin-go@v0.14.3/tfprotov6/internal/tfplugin6/tfplugin6_grpc.pb.go:403 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0xc00052a[78](https://github.com/myorg/myrepo/actions/runs/5132276480/jobs/9233362858#step:11:79)0, {0x2228178, 0xc00044a680}, 0xc00041c240, 0xc00064[79](https://github.com/myorg/myrepo/actions/runs/5132276480/jobs/9233362858#step:11:80)20, 0x31822d8, 0x0)
	google.golang.org/grpc@v1.51.0/server.go:1340 +0xd33
google.golang.org/grpc.(*Server).handleStream(0xc00052a7[80](https://github.com/myorg/myrepo/actions/runs/5132276480/jobs/9233362858#step:11:81), {0x222[81](https://github.com/myorg/myrepo/actions/runs/5132276480/jobs/9233362858#step:11:82)78, 0xc00044a680}, 0xc00041c240, 0x0)
	google.golang.org/grpc@v1.51.0/server.go:1713 +0xa36
google.golang.org/grpc.(*Server).serveStreams.func1.2()
	google.golang.org/grpc@v1.51.0/server.go:965 +0x98
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.51.0/server.go:963 +0x28a

Error: The terraform-provider-flux_v1.0.0-rc.4 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Error: Terraform exited with code 1.
Error: Process completed with exit code 1.

This issue you are facing is caused by the provider not containing any Git or Kuberentes configuration. I thought i fixed the panic that you are seeing but apparently not. Will have a look at that.

Thanks for clarifying. Originally I only wanted to specify the git block, but this was not allowed, so attempted removing both blocks.


Can access CVAT over LAN but not Internet

Having followed the instructions here https://github.com/opencv/cvat/issues/1011
(using local IP and default port 8080) I am able to access CVAT across the LAN. I would like to be able to access CVAT from anywhere using the public IP address and port. What config changes should I make? and how should the NAT port forward be configured?
I did try the above but with our public IP address and an 8080 port forward on the firewall but it didn't work :/
(I have successfully set this up with a previous version of CVAT but I'm a bit confused as to how it works now re. different ports, HOSTS etc.)
My working LAN config.
base.py.txt
docker-compose.override.yml.txt
react_nginx.conf.txt

@LukeAI
Sure. It would be great.
I would recommend to create a section (something like: Setup for LAN/Internet) here in advanced installation topics and provide some steps, config examples, short explanations.
I believe it's a valuable contribution.

I'm not sure if I'm qualified to make this addition :/
My setup was working on Friday and has been up over the weekend continuously but today, Monday I am getting the same old "authorization failure" login error on both LAN and WAN.
Tried pulling the latest from the repo and rebuilding everything and I still get the error messages but am now able to login again.

Using this config

@LukeAI
I agree it might confuse a little
For example we have these ports:
Port over the Internet 	LAN port 	Port inside Docker
REST API 	8060 	8070 	8080
UI SERVER 	7060 	7070 	80
Than config file should be:
services:
  cvat:
    ports:
      - "8070:8080"
    environment:
      ALLOWED_HOSTS: '*'
      UI_SCHEME: http
      UI_HOST: <your external ip address>
      UI_PORT: 7060
  cvat_ui:
    build:
      args:
        REACT_APP_API_HOST: <your external ip address>
        REACT_APP_API_PORT: 8060
      dockerfile: Dockerfile.ui
    ports:
      - "7070:80"

Also you need to trigger port on a router:
Internet 8060 => Local 8070
Internet 7060 => Local 7070

And setup your firewall for these ports.

@LukeAI I agree it might confuse a little For example we have these ports:
Port over the Internet	LAN port	Port inside Docker
REST API	8060	8070	8080
UI SERVER	7060	7070	80
Than config file should be:
services:
  cvat:
    ports:
      - "8070:8080"
    environment:
      ALLOWED_HOSTS: '*'
      UI_SCHEME: http
      UI_HOST: <your external ip address>
      UI_PORT: 7060
  cvat_ui:
    build:
      args:
        REACT_APP_API_HOST: <your external ip address>
        REACT_APP_API_PORT: 8060
      dockerfile: Dockerfile.ui
    ports:
      - "7070:80"

Also you need to trigger port on a router:
Internet 8060 => Local 8070
Internet 7060 => Local 7070

And setup your firewall for these ports.

@LukeAI I agree it might confuse a little For example we have these ports:
Port over the Internet	LAN port	Port inside Docker
REST API	8060	8070	8080
UI SERVER	7060	7070	80
Than config file should be:
services:
  cvat:
    ports:
      - "8070:8080"
    environment:
      ALLOWED_HOSTS: '*'
      UI_SCHEME: http
      UI_HOST: <your external ip address>
      UI_PORT: 7060
  cvat_ui:
    build:
      args:
        REACT_APP_API_HOST: <your external ip address>
        REACT_APP_API_PORT: 8060
      dockerfile: Dockerfile.ui
    ports:
      - "7070:80"

Also you need to trigger port on a router:
Internet 8060 => Local 8070
Internet 7060 => Local 7070

And setup your firewall for these ports.

Hi, i did all but http://localhost:7070/auth/login dont login and show message "Could not check authentication on the server
Open the Browser Console to get details" on WAN also http://myip:7060  i have same state. can you help me?


Add trap shot option to operator controller

Apparently this works in testing.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#38  👈
#37
#36
#35
#32
#31
#34
#33
#30
#29
#28
#27
#26
#25
#24
#23
#22
#21
main

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

Join @BruceMcRooster and the rest of your teammates on  Graphite

Merge activity

Mar 15, 9:11 AM EDT: @BruceMcRooster started a stack merge that includes this pull request via Graphite.


Bug: for loop over iter()

Hi,
I'm working on the python re.finditer function implementation and there seems to be an issue with the code generation for the for-loop over an iterable object generated by the iter() function.
Python Code:
a = 0
vals = [1,2,3]
ret = iter(vals)
for m in ret:
	a += m

Javascript Code:
		var a = 0;
		var vals = list ([1, 2, 3]);
		var ret = py_iter (vals);
		var __iterable0__ = ret;
		for (var __index0__ = 0; __index0__ < __iterable0__.length; __index0__++) {
			var m = __iterable0__ [__index0__];
			a += m;
		}

The issue is that ret returned by the py_iter(vals) returns an object of the form:
__PyIterator__ {iterable: Array[4], index: 0}
index:0
iterable:Array[4]
next:__jsUsePyNext__()
Symbol(Symbol.iterator):()
__proto__:Object

which gets assigned to __iterable0__but what we really want is for the value ret.iterable to be assigned to __iterable0__.

Hi,
Call to iter () requires iterator support on the JS side, so -e 6 switch. Minified code will run on es5 anyhow, through Google Closure polyfills.
Will put this in the docs!
KR
Jacques
PS Rationale: When the 'universal iterator model' was added to Transcrypt, es 6 was just released. Since Closure can generate es5 from es6 and the model was quite complicated in itself, I decided not to retrofit for es5.

From what you have described, it sounds like this is something that can be determined at compile time, no? If so, I think it would be better if the compiler were to throw an error in this case. Currently, it silently completes the compilation phase and generates a js file with faulty implementation. I think updating the documentation is good too, but failing fast in the compilation stage is better.


Fix fatal error on HHVM  due to Memcached::deleteMulti() being undefined

I fixed a fatel error when calling the deleteMulti function of Memcached on HHVM. Then this function is not available, the delete function is called instead for each entry.
I also removed the sudo command line from the .travis.yml, because the command is failing because sudo is disabled (sudo: false in .travis.yml) and memcached will work on HHVM now.
Additional to that I added some docblocks for better Code completion.

@mimmi20 :+1: Thank you for this.
I will merge this manually.


[BUG] Stuttery auto-scroll to the bottom of the page when outputting code

Describe the bug
When writing long multi-line code blocks, the interface stutters a lot.
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
A clear and concise description of what the bug is.
To Reproduce
Filling out this field will help us investigate the issue efficiently. Providing detailed information allows us to set the appropriate priority. We appreciate your cooperation.
Steps to reproduce the behavior:

Start a new chat
Ask a question that invokes a code response.

screen recording
https://github.com/user-attachments/assets/438a05ca-8c48-4a72-8ef2-c5205533b667
Additional context
It seems like this bug occurs more often on my 2nd monitor than on my my Macbook screen..

@conradg
Is the version of the application you are checking the latest?

Hmm, no this is from a forked repo forked at this commit about 2 months ago.  https://github.com/aws-samples/bedrock-claude-chat/pull/303
I can see a lot has happened since then, so I will try and upgrade to the latest changes

The following code is the relevant section
The useLayoutEffect is used so that the chat no longer bounces while it is being generated.
However, they are no longer followed during chat generation.
If you need this, modify it to scroll with delayed evaluation.
frontend/src/pages/ChatPage.tsx
  useLayoutEffect(() => {
    if (messages.length > 0) {
      scrollToBottom();
    } else {
      scrollToTop();
    }
  }, [messages, scrollToBottom, scrollToTop]);

@conradg
https://github.com/aws-samples/bedrock-claude-chat/pull/450
Improved.
would you check this PR ?

Close issue because fixed by #450


How login to Ikariam??

Not work Ikabot, wrong login ar password :( how login??

This might help : https://github.com/physics-sec/ikabot/issues/105#issuecomment-1492956469

On Windows this not working
2023-04-01, št 15:25, Florian @.***> rašė:

This might help : #105 (comment)
https://github.com/physics-sec/ikabot/issues/105#issuecomment-1492956469
—
Reply to this email directly, view it on GitHub
https://github.com/physics-sec/ikabot/issues/106#issuecomment-1492956833,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A63SLASE4OSZSOQTA2CRWA3W7ANENANCNFSM6AAAAAAWNYNZ4A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ainda tenho problemas para logar, mesma situação que citaram acima, alguem consegue auxiliar, já reinstalei e atualizei, nada de dar certo


layer/agent: add control of network interface to use

Ok looks like the tests need to be adapted and the CHANGELOG formatted.

Question: Why not a CLI argument also?
Thanks!
I don't see how it's relevant for most people so I prefer less arguments.

General thought: looks like ephemeral container and job pod creation could share some code (but it should not hold back this PR).
Agree

bors r+

bors r+


Ensure the professor can also edit the class descriptions even if their email isn't in the course section's white-list.

Parent Issue: #106
Hours: 1 hour

Small thing we didn't include in our logic last sprint. Currently only users whose email appears in a course section's white list can edit the description of classes. Of course, the professor's email shouldn't need to be added to the white list for him/her to edit the class. They should be given the right as soon as their email matches with the one associated to the course section's professor's email.

Alternatively, this issue could also be resolved by ensuring the the professor's email is indeed added to the white-list the first time the course section is added by a user.

The prof can now edit the description field, so I am closing the issue.
Number of hours: 0.5


Copy Recorded tests to appropriate directories

Tests recorded are copied to bin/**/SessionRecords/* directory, there should be a way to copy over the generated files to the appropriate test directories in the local repo.
Ideas:

set an env flag?
pass an arg while running the xunit tests?

PR merged.


fix: Omit enums from sidebar in v2.

Omits enum members from the sidebar since they don't have their own page generated by API Documenter.
This PR ports https://github.com/gabrielcsapo/docusaurus-plugin-api-extractor/pull/26 to v2.

Thank you!


Session.run() hangs in child thread if something was executed in main thread first

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Confirmed on Mac OS X (10.12.6) + Ubuntu 16.04 on GCP
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): v1.4.0-rc1-11-g130a514 1.4.0
Python version: Anaconda Python 3.6.1
GPU model and memory: no gpu

Describe the problem
Session.run() hangs in thread if it has executed something in the main thread. If we don't execute the first calculate_something() in the main thread- or execute it after we submitted to the pool, everything works. Only when first calculating something in the main thread, and then in the child thread does tensorflow hang.
Reproducing example
from concurrent.futures import ProcessPoolExecutor as ProcessPool

def calculate_something():
    import tensorflow as tf

    with tf.Session() as sess:
        a = tf.constant(2)
        b = tf.constant(3)

        print("a=2, b=3")
        print("Addition with constants: %i" % sess.run(a+b))
        print("Multiplication with constants: %i" % sess.run(a*b))

calculate_something()

pool = ProcessPool(1)
pool.submit(calculate_something)

I assume ProcessPoolExecutor uses fork() internally, and forking after the TensorFlow runtime creates internal threads is unsafe. Fortunately, there are two workarounds:

Use ThreadPoolExecutor instead of ProcessPoolExecutor.
Use tf.Session(config=tf.ConfigProto(use_per_session_threads=True)) instead of tf.Session().

Thanks, that tip works!

Hi @JosPolfliet,
Which of the two workarounds mentioned by @mrry worked for you?  I am facing the same problem.

FWIW I found that both 1 and 2 were necessary to prevent hang.


reqwest tls feature

try to fix https://github.com/mibes/couch-rs/issues/10

Thanks for this!
I did a quick test specifying --features rustls-tls and this seems to work fine. I wasn't able to confirm any impact on behaviour for the other flags.
Since this change does not change the default behaviour, I'll merge it in develop.


An empty topic can be created

Let's put in a check to prevent the creation of a topic with fewer than three characters in the name.

Fixed


Dragonrage: Watch shoistic.com

Dragonrage requests the watch of the watch_keyword shoistic\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

shoistic\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by cigien in Charcoal HQ


Consider not using all-caps for navigators

I'd like to respectfully push back on the decision to use all-caps for navigators (terminology?).
I understand the reasoning behind the decision - to clearly distinguish between filter functions and navigators, but I don't find this a compelling reason to abandon well established Clojure style idioms. The programmer must always understand, in a given context, what kinds of things symbols are bound to - it is impossible to read code otherwise. Symbols can be bound to many kinds of things - functions, values, record types, channels (core.async) etc etc.
I'll be using Specter either way : )

Well, a naming convention for global navigators has benefits without having any drawbacks. When you work on a larger project with lots of custom navigators, it helps a lot with understanding a path even if you don't know the particulars.
Clojure does use a few naming conventions – records are camel case and dynamic vars use ... syntax. And generally the context of where the symbol is used helps you determine what it is.

Having ? after function names sometimes helps with distinguishing filter functions, but not always. Otherwise, everything looks the same and the context is not helpful for distinguishing.
I'd be open to a different naming convention, but not to dropping a naming convention altogether. The nice thing about all caps is it does not require any extra characters to be typed as part of the naming convention.

Closing this issue but still open to proposals for alternate naming conventions.

So is the convention to use caps only for the navigators that have no parameters?
FWIW I'm still unconvinced that the departure from Clojure norms is warranted, but it's not my call.
Perhaps this issue could be left open, to make it a bit more visible and invite others to comment.

My mistake, wrote that too fast.

If there's ever a justification for a naming convention, it's when you have a new independent concept in which a naming convention helps with comprehending code. Records/types fit that description when they were introduced, and Specter navigators fit just as well or better.
I'll re-open, but I'll need to see a really compelling argument to change something which is all benefit and no drawback.

This has been open for awhile with no activity, and my position has not changed from my earlier comments, so am closing this issue.

I support having a naming convention that distinguishes between different roles.  For me, though, all-caps is ... shocking every time I see it.  It has an established function for constants in C and Java, but in Clojure, it feels out of place.  Maybe you could use prefixes (e.g. n-all or nav-all) or a legal punctuation character as a suffix, by analog with "?".  :, $, &, - are options, for example.  (I have a personal convention of naming vars containing atoms with a final "$", which I find very useful.)

Now that Specter 1.0 is out, backwards compatibility is a top priority for the project. So at this point, the names cannot be changed.

I agree that it wouldn't make sense to get rid of the existing names.  I was thinking rather of the of adding alternate names.
(I don't have a complete understanding of the intuitions that were driving recent comments in the Google group suggesting that a different syntax for Specter would be more "Clojure-ey", but I wondered whether the all-caps convention contributed to those folks' discomfort.  I don't really see what's inappropriate about the syntax otherwise.  Anything like Specter is going to have to have its own special syntax.)
Just my 2c, anyway.  I expect to use Specter regardless.  I imagine I'll get used to the all-caps names in the end.
I suppose that given that the all-caps operators are just symbols referencing values in a first-class way, anyone can provide their own alternate set of names for the same objects.  I wouldn't do that unless a standard convention developed, though.  Idiosyncratic abbreviations just makes it hard for someone else to read your code.

I think having two sets of names would be very confusing. Also, I like the current naming convention. I think you'll get used to it pretty quick.

Thanks for the replies.  I look forward to further experimentation.

If capitalized letters is jarring to the eye, would the use of keywords be better aesthetically?
Something like:
(def some-nav (comp-paths :all srange :all even?))

Keywords would look nice, but that would be a big shift, since navigators are functions.


Implement np geoswitching

Task/Issue URL: https://app.asana.com/0/488551667048375/1205651876758229/f
Description
See attached task description.
Steps to test this PR
See attached task description.

Current dependencies on/for this PR:

develop

PR #3650   👈

This comment was auto-generated by Graphite.


Add minimal compilation macro for builder2 version

Should only support CreateDevice and GetLastError, and only detect the adapter, create the device and check RT support.

Implemented in dev


Handle validation of non expiring tokens in jwt_authn filter

For an explanation of how to fill out the fields, please see the relevant section
in PULL_REQUESTS.md
Description: Handle validation of non expiring tokens in jwt_authn filter
Risk Level: Low

@vvinod1310 Please fix DCO https://github.com/envoyproxy/envoy/blob/dc03a9a4196204c13aaa192694acf67f3fc09ce8/CONTRIBUTING.md#dco-sign-your-work
And is there a test that can be added?

Hi,
Could I request for this change to be reviewed and merge if appropriate?
Many thanks!

@lizan @qiwzhang PTAL

@lizan Sure added comment please merge thanks!

@lizan & @zuercher - thank you for approving!

@vvinod1310 please update the description to include all the required fields from the pull request template.

@zuercher  done thanks!


Have cmdLine operate on bytes and passthrough non-transformed

ModSecurity operates on bytes (not passing locale here)
https://github.com/SpiderLabs/ModSecurity/blob/v3/master/src/actions/transformations/cmd_line.cc#L73
After
goos: darwin
goarch: arm64
pkg: github.com/corazawaf/coraza/v3/transformations
BenchmarkCMDLine
BenchmarkCMDLine/#00
BenchmarkCMDLine/#00-10         	567355544	         2.116 ns/op
BenchmarkCMDLine/test
BenchmarkCMDLine/test-10        	120188966	         9.981 ns/op
BenchmarkCMDLine/C^OMMAND_/C_DIR
BenchmarkCMDLine/C^OMMAND_/C_DIR-10         	26129725	        45.35 ns/op
BenchmarkCMDLine/"command"_/c_DiR
BenchmarkCMDLine/"command"_/c_DiR-10        	25364616	        46.85 ns/op
PASS

Before
goos: darwin
goarch: arm64
pkg: github.com/corazawaf/coraza/v3/transformations
BenchmarkCMDLine
BenchmarkCMDLine/#00
BenchmarkCMDLine/#00-10         	462339478	         2.582 ns/op
BenchmarkCMDLine/test
BenchmarkCMDLine/test-10        	33723297	        35.12 ns/op
BenchmarkCMDLine/C^OMMAND_/C_DIR
BenchmarkCMDLine/C^OMMAND_/C_DIR-10         	13380872	        89.04 ns/op
BenchmarkCMDLine/"command"_/c_DiR
BenchmarkCMDLine/"command"_/c_DiR-10        	13457377	        89.63 ns/op
PASS

Codecov Report
Base: 78.28% // Head: 78.34% // Increases project coverage by +0.06% :tada:

Coverage data is based on head (b49666a) compared to base (f507750).
Patch coverage: 100.00% of modified lines in pull request are covered.

:exclamation: Current head b49666a differs from pull request most recent head c5c34f3. Consider uploading reports for the commit c5c34f3 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           v3/dev     #543      +/-   ##
==========================================
+ Coverage   78.28%   78.34%   +0.06%
==========================================
  Files         145      145
  Lines        6884     6905      +21
==========================================
+ Hits         5389     5410      +21
  Misses       1263     1263
  Partials      232      232

Flag
Coverage Δ

default
73.56% <100.00%> (+0.08%)
:arrow_up:

examples
27.09% <0.00%> (-0.09%)
:arrow_down:

ftw
56.43% <100.00%> (+0.13%)
:arrow_up:

tinygo
71.63% <100.00%> (+0.09%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

internal/strings/strings.go
100.00% <100.00%> (ø)

transformations/cmd_line.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Autocomplete not working

Hi everyone,
not sure what I missed in the documentation, but I want to use autocomplete for the 'username' of ALL registered users (i.e. Meter.users collection). I'm new to Meteor, so I assume it's something very obvious.
Here is my code:
HTML input field
{{> inputAutocomplete settings=settings id="msg" class="input-xlarge" placeholder="Add Collaborator..."}}
JS helper
Template.modalAddCollaborators.helpers({
    'addedCollaborators': function () {
        return Courses.find().fetch();
    },

    settings: function() {
        return {
          position: "bottom",
          limit: 5,
          rules: [
            {
              collection: Meteor.users,
              field: "username",
              matchAll: true,
              template: Template.userPill
            }
          ]
        };
    }
});

Issue 1: So far autocomplete only matches the search field to the currently logged in user, not to ALL users.
Issue 2: The drop down list with matches looks like this: http://snag.gy/1gDOE.jpg
Can anyone hint me in the right direction?
Thanks so much!
Julian

@Julian-Th Meteor by default only publishes (and subscribes to) the currently logged in user to the client. You'll need to set up a new publication/subscription that passes the usernames (and any other related data) to the client for that to work.

Hi guys,
I've created in template:
{{> inputAutocomplete name="postcode" settings=settings }}

... and settings in template's helpers :
settings(){
        return {
            position:"bottom",
            limit:5,
            rules:[{
                collection:"PostcodeLocations",
                field:"postcode",
                subscription:"app.postcodelocations.autocomplete",
                matchAll: true,
                template:Template.testTmpl
                }]
        };
    }

... also I have added some staff into template's  code for debug purposes :
var autoPostcodeLocations = new Mongo.Collection("autoCompleteLocations");
...
Template.createLocationModal.onRendered(function () {
...
// print received data
this.autorun(()=>console.log(autoPostcodeLocations.find({}).fetch()));
...
});

my publishing:
Meteor.publish('app.postcodelocations.autocomplete', function (selector, options) {
    check(selector, Object);
    check(options, Object);
    var sub = this;

    options.limit = Math.min(10, Math.abs(options.limit));

    var handle = PostcodeLocations.find(selector, options).observeChanges({
        added:function(id, fields) {console.log('added - %s', id);
            sub.added("autoCompleteLocations", id, fields);
        }
    });

    sub.ready();
    sub.onStop(function(){ handle.stop(); });
});

when I try to type into textbox, publishing works (I see console output on server side). Also client has that data received (output in browser's console - print received data section), but widget is always claims 'No matches'.
In other case - when I have configured autocomplete control to use a local collection (see samples below), it works fine:
// this is template's behind code
// import collection definition
import { PostcodeLocations } from '/imports/api/postcodeLocations/collection';
...
Template.createLocationModal.onRendered(function () {
...
// simple subscribe
    Meteor.subscribe('app.postcodelocations.autocomplete');
...
});
...
//helpers
Template.createLocationModal.helpers({
    schema: () => locationSchema,
    settings(){
        return {
            position:"bottom",
            limit:5,
            rules:[{
                collection:PostcodeLocations,
                field:"postcode",
                template:Template.testTmpl
                }]
        };
    }
});

// my simple publication
Meteor.publish('app.postcodelocations.autocomplete', function () {
    return PostcodeLocations.find({ postcode: { '$regex': '^a', '$options': 'i' } }, {limit:10});
});

What I have missed here? any idea?

For me it works with these elements:
Publication of users:
// Publish users
Meteor.publish('usersList', function() {
    return Meteor.users.find({}, {
        fields: {
            'emails': 1,
            'username': 1,
        }
    });
});

These are the settings for the autocomplete
Template.MyTemplate.helpers({
    autocompleteSettingsUser: function() {
        return {
            position: "bottom",
            limit: 8,
            rules: [{
                    token: '@',
                    collection: Meteor.users,
                    field: "username",
                    template: Template.UserPill,
                    noMatchTemplate: Template.NotFoundPill
                },
            ]
        };
    },
});

And subscribe to the publication in the userPill template (Template.UserPill):
Template.UserPill.onCreated(function () {
    Meteor.subscribe("usersList");
});


Super Square

http://scratch.mit.edu/projects/167583082
http://phosphorus.github.io/#167583082
Error: Failed to execute 'getImageData' on 'CanvasRenderingContext2D': The source height is 0.
    at Sprite.touching (https://phosphorus.github.io/phosphorus.js:1643:37)
    at eval (eval at scopedEval (https://phosphorus.github.io/phosphorus.js:4014:14), <anonymous>:2:41)
    at Stage.P.runtime.P.Stage.step (https://phosphorus.github.io/phosphorus.js:3938:15)

I am trying to make scratch to work with apk


Automate tweets for new issues

I've never used the twitter API, so I don't have much experience with this.
If we could integrate with travis-ci, that would be awesome.

Maybe we can use https://ifttt.com for this?

Yeah, probably! And you would want to connect it to receiving the already automated mail?

Hm... not sure how that would work. I was hoping we could have IFTTT listen for changes in the RSS feed, then tweet based on that. (Which is actually how to the emails work, too.)

Didn't think of that, but that's an even better idea!

Something like this should do the trick:

Can I help with this?

@BasThomas sure! I've been slacking here 😄

Let me see if I can this running on a dummy account and see how it does. :)

I've been testing this over the past few weeks and it seems like it's working with IFTTT. In your IFTTT Settings though, make sure to disable link shortening to prevent the usage of ift.tt urls instead of swiftweekly.github.io

This is the recipe I am using. Obviously, we would not want to send a DM, put to post a tweet. ☺
This posts eg. Issue #68 swiftweekly.github.io/issue-68 written by Bas Broek... only thing is it uses the author name, not the Twitter name. I think this can be changed?

This is great! 💯
@BasThomas -- thanks so much for looking into this. I'll get this setup over the weekend.
Still need to create an IFTTT account 😅  lol
I'm not sure about author name vs twitter handle.
IFTTT uses the rss/atom tags right?

Yes, the {{EntryTitle}} stuff just hooks into the RSS feed.

lol forgot to do this 😢 will definitely do it this week!

ok! just set this up. not sure if it's working. i guess we'll see next week 😅

Woo, nice! If you're not sure - I tested it for two weeks just sending myself a Twitter DM instead of tweeting. :)

it works!
https://twitter.com/swiftlybrief/status/865638949384994818

Yay!

The only thing we should still try to figure out is if we can use the author's Twitter handle instead of the author's full name. 🤔


Static $HOST and $PORT in production build

Environment

Operating System: Linux
Node Version:     v18.12.0
Nuxt Version:     3.6.1
Nitro Version:    2.5.2
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      mode, editor, runtimeConfig, head, loading, css, modules, devServer, build, devtools
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
All reproduction on nuxt3 app:
Reproduction 1:

Write into file .env content  HOST=<IP_ADDRESS>
yarn build
node .output/server/index.mjs gives output Listening http://[::]:3000

Expected result: Listening <IP_ADDRESS>
Actual result: nuxt webapp listening on all public interfaces, circumventing reverse proxy (nginx)
Reproduction 2:

Write into nuxt.config.js: runtimeConfig: { NITRO_HOST: "<IP_ADDRESS>", HOST: "<IP_ADDRESS>" }
yarn build
node .output/server/index.mjs gives output Listening http://[::]:3000

Expected result: Listening <IP_ADDRESS> or Listening <IP_ADDRESS>
Actual result: nuxt webapp listening on all public interfaces, circumventing reverse proxy (nginx)
Describe the bug
When run without any environment variables node .output/server/index.mjs will listen on all available interfaces.
This is a security concern, because in production environment webapps will be run behind a reverse proxy such as nginx (caching, ssl stripping) and/or behind a web application firewall such as cloudflare.
Sysadmins easily forget to use HOST=<IP_ADDRESS> node .output/server/index.mjs.
I think nuxt3 production builds should have a fail-safe default configuration, e.g. limiting exposure of the web application.
At a minimum, there should be an option for nuxt3 users to hard-code the $HOST and $PORT in the production build, so that the environment variables $NITRO_HOST and $HOST can be set to a reasonable default value (e.g. localhost).
Additional context
No response
Logs
No response

Would you raise this as an issue to https://github.com/unjs/nitro directly? 🙏

closing to track in https://github.com/unjs/nitro/issues/1400


No stacks found message in SST Console and missing stackMetadata directory in S3

Hi.  Some info:

We're using sst 2.1.31
We're running sst with npx sst dev
When opening the SST Console, we are getting the message: No stacks found for app example-app and stage example-stage

Looking in the Network tab for the SST Console in Chrome, I can see a request to:

http://localhost:13557/proxy/https://sstbootstrap-example.s3.example-region.amazonaws.com/?list-type=2&prefix=stackMetadata%2Fapp.example-app%2Fstage.example-stage%2F

The response for this request is:
<?xml version="1.0" encoding="UTF-8"?>
<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Name>sstbootstrap-example</Name><Prefix>stackMetadata/app.example-app/stage.example-stage/</Prefix><KeyCount>0</KeyCount><MaxKeys>1000</MaxKeys><IsTruncated>false</IsTruncated></ListBucketResult>

Looking at the S3 bucket in the AWS console, I can see that the stackMetadata directory does not exist.  Instead I can see a appMetadata directory

Temporarily disabling a network scanner app on one of our machines, the SST Console seems to start working again

We didn't see any sort of error message in the npx sst dev terminal when the SST Console was broken.  Is there a way we could diagnose how things are failing when the network scanner is enabled and would maybe see if an error can be logged by sst dev when something like this happens?  Thanks!

Hmm yeah it's not really connected to the CLI that way. But what is this network scanner app? Maybe we should document it on our side.

Hi @jayair.  After digging into it a bit more, we think the issue may have been caused by running node.js 16 locally but targeting node.js 18.  We're going to do a bit more testing on that though, to confirm it really was the cause.  Does that seam plausible given when the issue might be occurring?  Is the issue likely occurring in the SSTBootstrap stack rather than in the sst CLI?
We've had issues before with SST console (permanently) displaying the message "No stacks found".  That previous time, I didn't think to check the browser Network tab though.  Is there anyway a part of SST (e.g. CLI) could make it more obvious that an error has occurred and what the nature of it is?  When this happens (both this time and previous time), there were no errors in the sst CLI.  Everything on the CLI side (when running npx sst start) seemed normal and successful.  The only clue was the "No stacks found" message in the SST Console.
We're on sst v1.x with this codebase at the moment, perhaps thinks might be better when we've completed an upgrade to sst v2.x?
The change between the S3 key prefix between stackMetadata and appMetadata, is that a difference between particular versions of sst?  E.g. between sst 1.x and sst 2.x?
Thanks

Hmm this could be worth looking into. Can you open a new thread in #help on Discord and link to this? I can pull the team in.

I having this exact issue as well. I tracked down the files in the S3 bucket as @simondean described, and I have an appMetadata folder. I only recently started doing sst development, so started with version 2, so it may not be a version mismatch between 1 and 2.

I'm having this issue as well. I've tried multiple SST and Node versions, but the SST console always tells me that no stacks exist.

Can you open a new thread in #help on Discord and link to this? I can pull the team in.


Add csi external-resizer deployment

Adds csi external-resizer along with the csi helpers deployment.
k8s version check is performed and this is added in k8s 1.16+ clusters
only.
Passes the CSI volume expand credentials to the node container as env
var from a secret reference.

e2e tests on k8s 1.16+ would fail because the csi helper deployment won't be healthy until a new node container that supports csi resize is used.

The CI failure is due unhealthy csi-helpers. The external resizer tries to connect to the CSI driver but fails with error:
CSI driver neither supports controller resize nor node resize

Once the support is added, the CI should pass.


Promatik image viewer

The DEMO project incorporates the Promatik image viewer for the gallery, but my implementation doesn't. I don't see a switch to throw in the config file.
How do I embed the promatik viewer on my site?
Thanks

Hey @comstock! When you click on an image in the demo gallery you'll see the image file open in your browser window. Is this the behaviour you mean?

When I viewed the images from the local test instance, I had the experience you describe. But when I viewed the live demo, I getting a nice set of [viewing tools]("Better Image Viewer": https://chrome.google.com/webstore/detail/better-image-viewer/kmokinipfahjbfaicnjnmlobmbfiedmp). I think I was appreciating the tools in a plug-in which, for some reason, wasn't kicking in when I viewed the images in the test instance. Thanks for taking the time to reply. I appreciate it.

Gotcha. Glad it's sorted out!


4.1

QUESTION 1
This question requires that you evaluate the underlined text to determine if it is correct.
When you are implementing a software as a service (SaaS) solution, you are responsible for configuring high availability.
Instructions: Review the underlined text. If it makes the statement correct, select "No change is
needed". If the statement is incorrect, select the answer choice that makes the statement correct.
A. No change is needed.
B. defining scalability rules
C. installing the SaaS solution
D. configuring the SaaS solution

D


Pull remaining string as note for score

Can store that in the event journal as well

Done in c7d2926b2b5e42f5e8584a6afa120fd80f96eaf7


add documentation

Sorry i missed your last comment, here is some documentation

no worries, thanks a lot!


Game Aliases

What's your idea?
Hi there, I was having this problem with some games where some minor name changes between what was requested (for example from playnite) and the name on the manifest causes the game not to back up.
Examples like a dash " - " before a "Definitive Edition" missing, or a ":" in a different spot
Not to mention suffixes one may add.
We can use custom games for this, but that's not our intention, it's the same game, any update to folders on the manifest are not used for example.
I was thinking it would be better to define game aliases for detected games, where if the name matches one of your defined entries then it will use that same config on the manifest.

Sorry I just found that this alias is in "look-up with another title" from the client, in this case the playnite addon context menu.
I was looking it from the main ludusavi app before as all game config is there.
Will close it now.


Typo Error: dim Parameter in MeshAutoencoder

Hi Phil,
I've noticed a potential typo error. A few days ago, you removed the dim parameter in the MeshAutoencoder, but I still see it being used here. Is this a typo error?
for _ in range(local_attn_encoder_depth):
    self.encoder_local_attn_blocks.append(nn.ModuleList([
        LocalMHA(dim = dim, **attn_kwargs, **local_attn_kwargs),
        nn.Sequential(RMSNorm(curr_dim), FeedForward(curr_dim, glu = True, dropout = ff_dropout))
    ]))

Best regards,
Xueqi

@qixuema yes, my bad, thank you


[excel] (Tutorials) Adding note about PA UTC

Fixes #531.
A comment was raised that it's potentially confusing that the tutorial produces a different time than the user's current time-zone-adjusted time. Hopefully, this PR clears that up.

Docs Build status updates of commit 373174d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/power-automate-tutorial-10.png
:white_check_mark:Succeeded
View

docs/tutorials/excel-power-automate-manual.md
:white_check_mark:Succeeded
View

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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


First version of the Logtalk pluging for IntelliJ IDEA.

Created the plugin in coding/idea.
I called the folder "idea" instead of "intellij" since the former is the folder name that IntelliJ uses by default.
Needed to modify a bit .gitignore to correctly ignore non-relevant Java or IntelliJ files.

Thanks for the contribution. Sent you two mails with missing built-in directives, predicates, and operators w.r.t. syntax coloring. After adding them, simply commit in your fork and the changes will be added to this pull request automatically.

thanks for your feedback !
I think the operators are recognized as such, but I just need to change the
color of them.
But the other keywords were indeed omitted.
Sergio
On Mon, Jan 30, 2017 at 10:24 PM, Paulo Moura<EMAIL_ADDRESS>wrote:

Thanks for the contribution. Sent you two mails with missing built-in
directives, predicates, and operators w.r.t. syntax coloring. After adding
them, simply commit in your fork and the changes will be added to this pull
request automatically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LogtalkDotOrg/logtalk3/pull/32#issuecomment-276195256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1yTELagGK2d3Fnd25e6BXvNAUBSjcEks5rXlUDgaJpZM4Lx7L9
.

Pushed. Will deploy a new version now.
Btw, it looks quite better with the theme Darcula (change the tem in the
appearence menu in the IntelliJ settings).
Sergio
On Mon, Jan 30, 2017 at 10:25 PM, Sergio Castro<EMAIL_ADDRESS>wrote:

thanks for your feedback !
I think the operators are recognized as such, but I just need to change
the color of them.
But the other keywords were indeed omitted.
Sergio
On Mon, Jan 30, 2017 at 10:24 PM, Paulo Moura<EMAIL_ADDRESS>wrote:

Thanks for the contribution. Sent you two mails with missing built-in
directives, predicates, and operators w.r.t. syntax coloring. After adding
them, simply commit in your fork and the changes will be added to this pull
request automatically.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/LogtalkDotOrg/logtalk3/pull/32#issuecomment-276195256,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1yTELagGK2d3Fnd25e6BXvNAUBSjcEks5rXlUDgaJpZM4Lx7L9
.

Superseded by #33.