Error running project after creating with latest Analog installer: Failed to resolve import index.page.ts

Please provide the environment you discovered this bug in.
Windows 11 machine using a command prompt and node 18.13.0, npm  9.8.1.
Which area/package is the issue in?
create-analog
Description
Followed the getting started instructions for npm and selected the Angular v16 template.  I get an error when running the project.
Please provide the exception or error you saw
[plugin:vite:import-analysis] Failed to resolve import "../../../../../../../../c:/code/demo/angular-analog/src/app/pages/index.page.ts" from "node_modules\@analogjs\router\fesm2022\analogjs-router.mjs?v=875b5aa3". Does the file exist?
../../../../packages/router/src/lib/routes.ts:11:44
143|
144|  /// <reference types="vite/client" />
145|  const FILES = /* #__PURE__ */ Object.assign({"/src/app/pages/index.page.ts": () => import("../../../../../../../../c:/code/demo/angular-analog/src/app/pages/index.page.ts")
   |                                                                                ^
146|
147|
    at formatError (file:///c:/code/demo/angular-analog/node_modules/vite/dist/node/chunks/dep-df561101.js:43993:46)
    at TransformContext.error (file:///c:/code/demo/angular-analog/node_modules/vite/dist/node/chunks/dep-df561101.js:43989:19)
    at normalizeUrl (file:///c:/code/demo/angular-analog/node_modules/vite/dist/node/chunks/dep-df561101.js:41801:33)
    at async file:///c:/code/demo/angular-analog/node_modules/vite/dist/node/chunks/dep-df561101.js:41945:47

Other information
No response
I would be willing to submit a PR to fix this issue

[ ] Yes
[X] No

I tried using PowerShell instead and I don't get an error.

Ok. PowerShell or a WSL environment is recommended.


Break scripts.py and core/scripts.py out

Description
Both scripts.py and core/scripts.py are huge, so this PR breaks them out into smaller files. This makes no changes other then moving the classes around.
Motivation and Context
With the Celery work, a lot of our scripts are going to end up being updated or removed. It seems like a good time break up the files, before these changes go in.
How Has This Been Tested?

Running tests

Checklist

[X] I have updated the documentation accordingly.
[X] All new and existing tests passed.

This is failing on patch coverage, but its really just highlighting our current lack of coverage for some of our scripts.


Support for dotnet core ILogger

Logging is currently done via the FtpTrace.AddListener() Method or hooking into the OnLogEvent-Event.
Are there plans to support the dotnet core ILogger implementation?
Currently we can hook calls to ILogger into the OnLogEvent and write the logs based on FtpTraceLevel, it is just an easier way if the tool uses it automatically.

Do you have any reference code with ILogger to help out?

Since you have a variation of your code that is used for when compiling for dotnet core, it should be as easy as using ILogger<FtpClient> as a constructor parameter that will be filled via Dependency Injection.
How ILogger is configured, where it logs to etc all is handled by the dotnet core framework and the appsettings.x.json files.
One Repository that uses ILogger is the HealthChecks System for dotnet core.
https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/blob/master/src/HealthChecks.UI/Core/HostedService/HealthCheckReportCollectorHostedService.cs#L15

Thanks. Maybe we can support a public or public static ILogger<FtpClient> inside our FtpTrace class? That way if you don't specify a logger it will use its own system, or if you specify one then it will only pass all messages to the external logger. Will that be ok?

Implemented in v40.


feat: add hard constraints

included binned encodings in discrete scales
added zero property in scale

have a few things to fix before the review


Upgrade commons-text

Upgrade of commons-text to 1.10.0

Replaces https://github.com/apache/camel-quarkus/pull/4197


Update Page “about”

Automatically generated by Netlify CMS

👷 Deploy Preview for stunning-swan-6c3484 processing.

Name
Link

🔨 Latest commit
d3f40a4120e34ac52e67d297bec70323ecbb3775

🔍 Latest deploy log
https://app.netlify.com/sites/stunning-swan-6c3484/deploys/6390132550a131000ab66e40


Enyaq enable/disable charging does not work

When trying to toggle switch__charging I always get an error message saying "Charging action already in progress".  I tried to stop an active charging (failed) and also starting a new charge - no luck :(
2022-07-01 14:14:38 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [140130499686848] Charging action already in progress
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 193, in handle_call_service
    await hass.services.async_call(
  File "/usr/src/homeassistant/homeassistant/core.py", line 1704, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1741, in _execute_service
    await cast(Callable[[ServiceCall], Awaitable[None]], handler.job.target)(
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
    await service.entity_service_call(
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 680, in entity_service_call
    future.result()  # pop exception if have
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 964, in async_request_call
    await coro
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 717, in _handle_entity_call
    await result
  File "/config/custom_components/skodaconnect/switch.py", line 57, in async_turn_on
    await self.instrument.turn_on()
  File "/usr/local/lib/python3.9/site-packages/skodaconnect/dashboard.py", line 558, in turn_on
    await self.vehicle.set_charger('start')
  File "/usr/local/lib/python3.9/site-packages/skodaconnect/vehicle.py", line 396, in set_charger
    raise SkodaRequestInProgressException('Charging action already in progress')
skodaconnect.exceptions.SkodaRequestInProgressException: Charging action already in progress

Have you tried restart of Home Assistant? Might be that it got hung up on a finished action.

Thanks, it works most of the time - other times there might be issues with the Skoda servers :(
One more question: how can I set the charging current? On the Enyaq the value is "Reduced A" which is not numeric.
I'd like to create a virtual switch that can toggle between reduced and full but it does not work as the plugin uses non-numeric values...

One more question: how can I set the charging current? On the Enyaq the value is "Reduced A" which is not numeric.

Use a service call (yaml mode and not gui mode) and send "Reduced" or "Maximum" as current:
service: skodaconnect.set_charger_max_current
data:
  device_id: xxxxxxxxxxxxxxxxxxxx
  current: Reduced


Remove drafts from Ready column

This will filter out draft pull requests out from the Ready column
Closes https://github.com/iFixit/pulldasher/issues/393

CR :+1: but I wouldn't oppose another PR to clean up the functions some way or other.

@kthaler I resolved the external block if you'd like to test this one out

QA 🎬
Draft pulls are no longer showing up in the Ready column in pulldasher.


manifest.json becomes a folder with index.html instead of a JSON file

Environment

Operating System: Darwin
Node Version:     v18.18.2
Nuxt Version:     3.8.1
CLI Version:      3.9.1
Nitro Version:    2.7.0
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      app, sourcemap, spaLoadingTemplate, ssr, devtools, devServer, nitro, modules, plugins, build, vite, pinia, runtimeConfig
Runtime Modules:
Build Modules:    -

Reproduction
Put manifest.json in your public folder, run nuxt generate on version 3.8.1 or 3.8.2. Instead of .output/public/manifest.json you'll have .output/public/manifest.json/index.html.
Downgrading to 3.8.0 and changing nothing else in the project fixes the problem.
Describe the bug
manifest.json inside public becomes a folder in .output/public with an index.html file in it instead of the expected JSON file.
Additional context
No response
Logs
ℹ ✓ built in 12.07s
✔ Client built in 12086ms
ℹ Building server...
ℹ vite v4.5.0 building SSR bundle for production...
ℹ ✓ 1 modules transformed.
Inspect report generated at <redacted>
ℹ .nuxt/dist/server/styles.mjs  0.07 kB
ℹ .nuxt/dist/server/server.mjs  0.10 kB │ map: 0.22 kB
ℹ ✓ built in 346ms
✔ Server built in 352ms
ℹ Initializing prerenderer
ℹ Prerendering 4 initial routes with crawler
  ├─ /200.html (15ms)
  ├─ / (15ms)
  ├─ /index.html (14ms)
  ├─ /404.html (15ms)
  ├─ /manifest.json (1ms)  // I'm guessing this is the issue. Edit: No, this still prints on 3.8.0, but it works then.
✔ Generated public .output/public
✔ You can preview this build using npx serve .output/public

Are you using any custom config by any chance? Tried on a minimal nuxt app (Nuxt 3.8.2 with Nitro 2.8.0) and .output/public is as expected:

https://stackblitz.com/edit/nuxt-starter-p8dqvx?file=public%2Fmanifest.json,package.json

Tried with nuxt upgrade --force to 3.8.2. It does the same thing.
I wouldn't know what custom config you refer to. I'm assuming there's something, or you would be able to reproduce it, but the fact that I can change nothing at all except to downgrade to 3.8.0 to fix it indicates that it's not just my project misbehaving.
The string manifest.json appears nowhere in my project except where you'd expect it to; in compiled index.html and as { rel: 'manifest', href: '/manifest.json' } in the linksection of nuxt.config.ts.

It shouldn't happen but in order to fix the root cause, i need to reproduce same problematic output as you have. Do you after upgrading when trying npx nuxi info (or in CLI header) see Nitro 2.8 now? Also, what is under nitro config you have in nuxt.config?


ODistributed exception caused by Cluster name mastership

I have 3 nodes in a cluster.
I connect to node 1 and create some connected nodes. I then connect to node 2 and try to create some other nodes using the same classes but I get an error saying
com.orientechnologies.orient.server.distributed.ODistributedException: Error on inserting into cluster 'country' where local node 'node2' is not the master of it, but it's 'node1'
I noticed that ODatabase method GetClusterIdFor always returns the same Id independent of which machine I am connected to.

Yea, driver have some problem with cluster / class management.
#8


Fixed next step link's title on service-fabric-how-to-specify-environment-variables.md

Removed the unnecessary word "articles".

#sign-off


Finalize Layout Patterns thumbnail illustrations

As an IBM.com library adopter, I need to see not only the list but the image of the layout pattern so I can quickly find what I need on the Layout Patterns overview pages.
Tasks

[x] Review the images with Wonil and Linda for feedback via issue: carbon-design-system/ibm-dotcom-library#488
[x] Make changes as needed.
[x] Finalize wireframes images.

Acceptance criteria

[x] Images are ready for publishing.

Jacob and I shared the wireframe images in the DGC Design Critique and the feedback from the designers can be viewed here.

Meeting schedule with Linda & Wonil on 24th.

@jacobottesen-dgc Once the images are ready, please share the link to the images here. Thank you.

Wonil is currently reviewing the patterns thumbnails in box: https://ibm.box.com/s/he8ralj1i0u9siwdijxwstya30cppgxi

Images exported and uploaded to Box: https://ibm.box.com/s/hx2xg8kp7hardtzjstgypcda3qjzcccd


Re-add foundry activity analytics

Now that we are computing analytics using transactions, we can compute the foundry output activity analytics alongside the nft and alias activities.

Should be part of #1061


Issue with DOOM = "bin/doom" in branch develop on windows

On windows 10, make install in develop fails with
'bin' is not recognised as an internal or external command,
operable program or batch file.
make: *** [Makefile:25: install] Error 1
Changed it to DOOM = "bin\doom" and then make install only installed 45 packages:

Running emacs then loads 45 packages:

There are two separate issues here.

'bin' is not recognised as an internal or external command,

I'll look into a fix for this.

Changed it to DOOM = "bin\doom" and then make install only installed 45 packages:

It sounds like you do not have a private directory (or Emacs cannot find it). Did you run make quickstart first? If not, have you copied =~/.emacs.d/init.example.elto~/.doom.d/init.el`?

Yes you are correct, got carried away after the initial issue in the Makefile :)
Just tried this:

clone into .emacs.d; checkout develop
change first line in Makefile to DOOM = "bin\doom"
create .doom.d folder; copy init.example.el into it and rename to init.el
run make install
packages install with no errors
when I run emacs 'Doom loaded 45 packages' appears at the bottom:

If I repeat the same steps in master, when I run emacs a few hundred packages are loaded, albeit with one error that has been fixed in develop.
This is the issue: https://github.com/hlissner/doom-emacs/issues/146

I have also tried this guide:
https://github.com/hlissner/doom-emacs/wiki/Getting-Started
doom quickstart runs without error.
When I run Emacs the following error appears:

On windows this is probably caused by the forward slashes in
modules/feature/evil/config.el
The config.el file is actually at that path.


Github organization authorization access failed

Rancher Version:
master image
Docker Version:
1.12.2
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 16.04
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Enable github authentication
follow instructions to add client id and secret
select "Restrict access to only Authorized Users and Organizations"
add organization with one or more member
save and try to authenticate and login with any user in this organization.

Results:
Can't login with this user, and it is responding with "Unauthorized"

This is what is causing the login failure:
When a new org is created on Github, by default the access to this org is restricted. So any member's application that tries to list that org will not find it under that member account.
So for the newly created org, the owner of the org should set the Policy to No restrictions:

Login on GIthub as the owner of that org
Go to the Organization Settings for that org
Go to:
https://github.com/organizations//settings/oauth_application_policy
Change the "Third-party application access policy" to No restrictions
Make sure it shows:
Policy: No restrictions
Now this org should get listed for all members
Try login to Rancher as a member of this org an dit should work (assumed here that this org is given access in Rancher)

@galal-hussein @sangeethah let us document the above "about new org creation" in the Github Test plan.

Github test plan is updated with those steps .. and the steps tested and worked, thanks.


chore(config): ensure Sentry captures console.error calls

Description

Follow-up to #382
Context: Sentry will not capture explicit console.error calls by default unless specifically configured to do so.
Adds CaptureConsole integration with only error log level being captured. Context: https://docs.sentry.io/platforms/javascript/guides/nextjs/configuration/integrations/captureconsole/
Additionally: updates @sentry/react to latest
Tested that Sentry still triggers as expected on the preview

Alternatives Considered

Rewiring all the catch statements touched in #382 to throw. This is risky 1 day before launch bc it will bail on the remaining function and may cause unwanted/unexpected changes to the app's behaviour if not done carefully.
Adding Sentry.captureException alongside the added console.error() calls. This will create unnecessary clutter and will leave gaps over time where we forget to add Sentry.captureException. Effectively achieving a more cluttered and less reliable version of this top-level configuration.

Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

This is good as a solution for near launch but I think the alternatives are better long term solutions as this will likely cause unnecessary spam on our sentry (false positives).

Completely agree. I will help you triage the Sentry this week btw, but I'd rather we have too much coming in than missing something important that users are seeing.
Long term I think:

move to simply throw to rethrow an error in a controlled way with a useful error message when this is appropriate (i.e. unrecoverable state or we want to bail out of the remaining function)
Add a self-encapsulated error handler. E.g. in Cloud we always show a toast and then rethrow to top level (hence why this console.error detail hasn't been an issue there before)


Merge the ourairquality fork

This is a combined patch set, which has been necessary due to the dependencies.

Since that's a lot of stuff to merge and it's possible it won't be merged at all, I think we should ask maintainers (@kanflo, @projectgus) on what conditions this can be commited to master. Perhaps we could collect feedback from 2-3 people using e-o-r and I assume @ourairquality has a number of devices running constantly.
I have a couple of devices running MQTT clients 24/7 and I can test this PR with them.

@resetnow That's a good idea. I can volunteer as a tester and give some feedback. I've recently adopted these patches in my robotics project which uses quite intensive networking via websockets and also takes advantage of the RTOS features.
Right now I'm investigating an issue where the TCP thread apparently gets stuck somewhere, but that might be a bug in my code. I'll get back when I've got that issue resolved and give the patches some testing.

@flannelhead Enabling the tWIP_TCPIP_CORE_LOCKING_INPUT is causing problems for some projects, e.g. mdns, so please try this with the appended patch.
I am still interested in feedback and consider improvements, but people in my community need the revision history so I need to stop all the rebasing and this patch set is probably the cleanest it will ever be.

I think there's a lot of improvements in this PR. Hopefully I will find the time this weekend to start reviewing and testing. Regarding LWIP2 support, I see you point that submodule to your own repo @ourairquality. I am afraid I have not kept up with the progress of LWIP2 but is there any reason not to use the SuperHouse master for LWIP2?

@kanflo Thank you. It is not possible to point to the SuperHouse lwip repo because it has not changed in a long time. Also my lwip repo is a fork off the main lwip repo git://git.savannah.nongnu.org/lwip.git with just a few changes and I have been working to minimize that set of changes and work to get fixes into the upstream code. I suggest you fork off lwip and create a branch for esp-open-rtos specific changes as I have done, you could just cherry pick the esp-open-rtos branch.
My hope is that by closing the gap between the esp-open-rtos lwip and the upstream code that it will help bring these communities closer. So when we find problems they are discussed and pushed upstream, and that perhaps some people from the wider lwip community will consider using esp-open-rtos.

In case it helps get other people interested in this, and helps get it across the line, IPV6 can be enabled, it is not the default and not well tested but simple examples work for me, just define LWIP_IPV6 in your project.

If that helps, I think we could update SuperHouse LWIP2 fork and coordinate the merge across different projects.

@resetnow If the SuperHouse master branch can be updated to the upstream lwip git repo then that might work, otherwise I suggest just opening a fresh repo to track the upstream lwip with a branch for the few remaining patches specific to esp-open-rtos. If the barrier to having people tracking the upstream code can be lowered then that would be good.
I also created a repo for newlib to update that, and one for FreeRTOS, but it seemed easier to just bundle in a specific version of these.

@ourairquality - #151 has been open for a while, any thoughts on if this PR will help address it?  If so I'm happy to test it out.

@recursify This is a big update to lwip so it may well help. If you could re-test then that would be good to know. Might the lwip issue https://savannah.nongnu.org/bugs/?50837 be related to this problem, it talks about a client downloading and with delays? With this patch set it should be much easier for you to cherry-pick that proposed change and to see if it helps.

I've been testing these changes now for a while. Things seem to be working fine otherwise, but I'm having a problem with httpd WebSocket communication hanging up after a while. I'll try to come up with a minimal repro application during this week, so perhaps we'll get this fixed. I remember not having this issue though when I used the LwIP 2 PR code in late July, though.
It would be nice to get the WebSocket support in httpd introduced by lujji merged into the upstream LwIP httpd code. I see that code has got some improvements in upstream so it would make sense not to maintain an outdated version in esp-open-rtos. That would probably be quite an effort but I'm willing to lend a helping hand if I can spare some time for that.

@flannelhead @recursify The latest upstream lwip version has been merged and appears to include some improvements that would help avoid hung connections. If you could find an example to reproduce the problem then that would help.

@ourairquality It seems my problem is related somehow to TCP_QUEUE_OOSEQ. It's enabled by default in this PR and it isn't enabled in current master. When use this patch and set TCP_QUEUE_OOSEQ=0, the hanging doesn't happen anymore... I wonder what should I do next to debug this further. For one, I'm not sure if it's something wrong with my code, httpd or LWIP.

@flannelhead Thank you for narrowing this down. Could you please try adding the following to esp_interface.c:ethernetif_input() just before the call netif->input(p, netif). It will make a copy of the rx pool buffer (which are limited) and free that pool buffer immediately, and if that fixes the problem then it is likely that that rx pool is becoming exhausted, otherwise it is more likely a problem in lwip and the logic is likely in tcp_in.c.
    {
        struct pbuf *q = pbuf_clone(PBUF_RAW, PBUF_RAM, p);
        pbuf_free(p);
        if (q == NULL) {
            return;
        }
        p = q;
    }

Making a copy might not be the best solution as it increase peak memory usage, and it might still oom if there oos buffers are not well bound. There is code in lwip to limit the size of the oos buffers but it appears to be per-pcb and perhaps your app is building them up across multiple pcbs and a global limit might need to be added too. But firstly try narrowing it down using the code above.

Thanks for the suggestion. This addition indeed seems to fix the hangups. To the small extent I understand the issue, it is reasonable to expect that the buffer would be exhausted - the application is doing signal processing at 1 kHz at a higher priority than the TCP thread but should be also receiving WebSocket frames 10 Hz.
In my application there is only one pcb involved at a time.
Please tell me if I can provide any further useful information. I'm not yet very deep into the LWIP internals myself.

@flannelhead There is the TCP_OOSEQ_MAX_PBUFS option, that defaults to just 2, that appear to be intended to avoid this problem per-pcb. Could you confirm further that the rx pool is becoming exhausted, perhaps by adding a counter for how many lwip holds and increasing this counter in ethernetif_input() and decreasing it in pbuf.c: pbuf_free() around the call to sdk_system_pp_recycle_rx_pkt() which returns these to the internal pool. If such a counter is going over 4 then there is a problem, and perhaps you can track it down in tcp_in.c.

@flannelhead I can now reproduce this problem with oos buffers. One problem was that I made a mess of the lwipopts TCP_OOSEQ_MAX_BYTES and TCP_OOSEQ_MAX_PBUFS and these were not being defined, but even with those set it's still not running very smoothly. Let me explore the problem further.

@ourairquality Ok, thanks for digging deeper into this. I did some experiments myself yesterday but didn't get very far. I'm still available for testing so let me know when there's something to test.

@flannelhead If you are prepared to retest then could you please try the updated patch set. The management of TCP OOSEQ buffers has been improved, and I found that the TCP SACK support also helps and enabled that too. The OOSEQ support alone, without SACK, performed really badly and I could not find a fault there. Filed an upstream bug for feedback see https://savannah.nongnu.org/bugs/index.php?51925 Perhaps OOSEQ support will just be disabled by default, but with SACK it seem significantly better, so feedback is welcomed.

Hi,
That looks like some great work to be honest! At least it seems now more reliable, but still I managed to get it to hang by e.g. reloading a couple times the page which opens the websocket connection. I should finish the minimal repro which I've been making though... Which kind of test are you currently using for development?

@flannelhead Found some more suspect errors in lwip. It was dropping pcbs due to errors maintaining the list. Filed a buf upstream for feedback https://savannah.nongnu.org/bugs/index.php?51930 This probably caused a lost of memory and importantly any rx pool buffers associated with the pcb which would bring the rx path to a halt. It appears to have only occurred when running multiple interfaces.
Apart from that, I might need more feedback on your problem as I can not yet reproduce it now. I had adapted the http_get example to download a large file over and over. Some code has been added to ethernetif_input() to simulate packet loss which you might want to try, and that had reproduced the problem here but it seems to keep running now. Could you please try a more conservative target in ooseq_max_pbufs(), lower the target number of ooseq buffers from 3 to 2, and see it that helps? Could you also print the level of pp_rx_pool_usage in ethernetif_input() to see that it does not get too hight, not over 4?

@ourairquality Yes, let me test it for a couple of days and I'll report back to you. Thank you for your work so far, I hope to be able to help.

@resetnow Thank you. The intention was to set a practical limit, just forget to change that back after testing the limit.

@ourairquality I don't know what I was doing wrong before, but now it seems I don't get those hangs anymore. The websocket connection seems to persist now, and I didn't manage to hang it despite trying like I did before (refreshing the page on the mobile phone etc.) Page refresh seems to have sometimes a small delay though, probably a timer then frees some buffers.
I will still do the checks you suggested to see there indeed isn't anything fishy going on.

After some more testing, it seems that reverting the two latest commits 893f715 and 730a0f4 the problem appears again and I can reproduce the hanging. So, it seems the hanging problem is finally fixed by these latest changes.

Okay, took a while to upgrade to the latest LWIP / FreeRTOS, but I'm now getting frequent errors with mbedtls_ssl_read returning 0x004c (MBEDTLS_ERR_NET_RECV_FAILED).  Usually it fails after a few successful reads/writes over a secure websocket connection.  Any pointers on how to debug this further?

@recursify I would take a look at the packets with wireshark to see if there are any clues there, see if there are any problems visible at the tcp/ip layer. Lwip also has some debug output that can be enabled, see lwipopts.h, and I would setup a test for which that log can be recorded. I don't use mbedtls and are not going to be working on problem reports at that layer.

FWIW, I've been now testing this changeset for a good while. After the fixes to lwIP done by @ourairquality, it's been working very well in my project.
It seems to me that it would probably be a good idea to merge these changes soon - after all, there are bugs in lwIP 1.4.1 in master as well, and lwIP 2 in this branch would fix some of them. The code would also get more exposure after merging and any potential bugs could be found out. But of course, all of this is up to the maintainers :)

I have tested with my Esparducam project and so far I only see issues with read(...) as mentioned in #445. Eg. examples/terminal buffer the entire line. I will dig further into this.

@kanflo There have been some changes to the newlib output buffering for the standard output streams and perhaps that is causing some confusion, and perhaps that path needs some attention. Newlib added an option to make these streams global rather than per-thread, but that option is not used, but it is there now in the update. Personally per-thread streams seems good, to limit the thread conflict a little (to the extent that they write to different buffers before flushing these). I don't think the actual output to the uart was ever thread safe and that needs some attention. Often these streams are used for debug dumps, and it is often important that this work when the image can be in a bad state, so a robust best effort solution for this thread safety issue might be best (rather than calling into FreeRTOS).
The newlib master branch has also moved to a 64 bit time_t and does anyone have thoughts on that?

Thanks for the pointer @ourairquality, a time saver! I will look into fixing the input buffering. Concurrency protection on the UART would be nice but can be left out for the time being, I think.
Moving time_t to 64 bit is +2 for me :)

@kanflo The initialization of the streams is in newlib/libc/stdio/findfp.c The initialization of stdout has not actually changed, but previously the reent structure was not even being switched on task switches so all tasks were using the same stream, really broken. With that fixed the stdout line buffering becomes visible. I am still not aware of an input buffering problem.
Newlib has been update to the master with the 64 bit time_t, so at least it is the latest code to work on.

Hello all...
Are there any chances that this patch will be integrated soon?
Or i should use ourairquality fork right now to test them?

Going to merge this one if no objections

One note: I just noticed esp_interface.c in this branch fails to build if TCP_QUEUE_OOSEQ=0. TCP_QUEUE_OOSEQ is now on by default but it would be good if the code would build without it.


No response found - No responses show up but request goes through

Describe the bug
A "No response found" log is printed in the console whenever I send any request (Error "No responses for request"). The response section still flashes "Loading..." but it says the response is never received or updated. I know the request is valid though, plus the console shows response status codes.
To Reproduce
Things broke after I enabled the plugin system and installed four plugins (default headers, faker, response eval, and save access token). I'm not sure at what point it happened after or during that because I tried out the plugins for a couple of requests and it was fine.
Out of nowhere, requests stopped working. After deleting the plugins and restarting this issue persisted. I updated to version 2020.2.0 today which didn't help.
Steps to reproduce the behavior (from what I remember):

Install the plugins mentioned above and use them (set an environment variable to a Response=BodyAttribute using a function from plugin response-eval.
Open the developer console. Send a request that you know works.
See the response and console logs.

Expected behavior
A regular response.
Screenshots
This is when using an invalid bearer token (status code = 401)

This is with a valid bearer token (200)

Desktop (please complete the following information):

OS: [e.g. macOS 10.15.1]
Installation Method: homebrew (original) and dmg (when updated)
App Version v7.1.1 (original) and 2020.2.0 (after update)

Hi @nataliamelissas,
It looks like the Response tag is failing to find any responses. Can you check in the app to see if there are any responses visible in the request that it's referencing?

@gschier
I'm actually not using a template tag of any sort for the particular request shown in the screenshots. I was originally (4 days ago) when it stopped working, but removed it to see if that causing it.
The example GET request only has a URL and manually inserted Authorization header.

@nataliamelissas do you have one in your environment? That would also affect things.

@nataliamelissas do you have one in your environment? That would also affect things.

Oh okay, I did have one in my environment which I removed. The console prints out less now but I still don't see the response preview.

This is a bit of a long shot, but can you try clearing all responses for your workspace from the workspace settings dialog?

Also, can you let me know if you have the "filter responses by environment" setting enabled?

I cleared all the responses but the problem is still there. :/
Yes, I have the "filter responses by environment" setting enabled.

And the problem is still there even after disabling it?

That worked! Interesting because I never changed the workspace settings. Also, this particular workspace only has a Base Environment.

I think there was a release in the past that enabled that setting by default, but has since been reverted. Thanks for your help debugging this issue. That should narrow it down enough to figure out what the problem is 👍

Many apologies for rehashing an old thread!
But I found this because I've been banging my head against the wall with this problem for a long time and interestingly the fix was similar but the complete opposite - UNCHECKING this made things suddenly work. Just in case it can help someone else.. button mash that setting and cross your fingers...


Types Aliases

Fixes #183
Add all Aliases types and tests for this types in different queries.

Codecov Report

Merging #229 into master will increase coverage by 0.01%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##           master     #229      +/-   ##
==========================================
+ Coverage   61.34%   61.35%   +0.01%
==========================================
  Files          68       68
  Lines        6327     6345      +18
==========================================
+ Hits         3881     3893      +12
- Misses       1933     1936       +3
- Partials      513      516       +3

Impacted Files
Coverage Δ

sql/scanner/token.go
22.22% <ø> (ø)

sql/parser/expr.go
77.81% <77.77%> (-0.77%)
:arrow_down:

sql/parser/create.go
69.23% <100.00%> (+0.60%)
:arrow_up:

Continue to review full report at Codecov.

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

@tzzed I think there was a rebase or merge error, the commits seem wrong. Could you take a look?

@tzzed I think there was a rebase or merge error, the commits seem wrong. Could you take a look?

seems good now.


'run' hangs on large output

Using version 4.0.0 this commad hangs: run(bash: "for i in {1..100000}; do echo -n =; done")

This is a very interesting bug.

"for i in {1..100000}; do echo -n =; done" works fine in the terminal.
the program hangs when run in SwiftShell if we wait for the command to finish before reading from its output. "run" does this. "runAndPrint" does not and works fine. So does "runAsync". Unless you run it like this:

let l = runAsync(bash: "for i in {1..65537}; do echo -n =; done")
try l.finish()
print(l.stdout)

If we change the number to 65536 it works fine. If we increase it to 65537 it hangs. This means the bug only occurs if the output contains more than 2^16 characters, or in other words has a count that cannot be stored in 2 bytes.
I have no idea why that is.

I think this bug is the same as #15. We can't use the same fix used then because "run" has been redesigned since then and has to finish before reading its output. I want it to be possible to use "run" without reading any output at all.
Here is a workaround:
_ = runAsync(bash: "for i in {1..65537}; do echo -n =; done").stdout.read()

This will make sure the output of the command has been closed (and therefore the command has finished running) before continuing.

The problem is described here: https://stackoverflow.com/a/39281558/96587
And here: https://github.com/lroathe/PipeTest
It happens when the output pipe from the command is full. So the problem is with Foundation's Process and FileHandle classes. Not really much we can do about it in SwiftShell except for informing users about it. I'll add it to the README.

I want it to be possible to use "run" without reading any output at all.

Would it be possible to read the output, but not necessarily return it unless requested? Perhaps it'd incur a small performance hit, but this issue makes run pretty dangerous to use. We don't know the limit at which it'll hang, and it may be extremely difficult for users to predict future output sizes when choosing to use this method. IMO your library should "just work" vs. causing developers lost sleep when their program startings hanging randomly in the middle of the night 😉

You’re right, this is pretty dangerous. There doesn’t seem to be any way of increasing the buffer size either.
To reduce overhead we could store the output as just Data, and convert to String only upon request.
One problem though: we might have to read from stdout and stderror simultaneously. Because if we try to read all output from stdout in one go and the command fills up stderror (or the other way around), the command will still hang.
I won’t be able to implement this for a couple of weeks, any pull requests are welcome if you want to do it.

@ileitch Actually i don’t think stderror should ever contain more than 65KB (I mean how much error information can a command produce?). Do you think it would suffice to just read all Data from stdout before waiting for command to finish?

I don't think it's safe to make assumptions about what amount of stderr output might be produced. I'm of the opinion that this method should not hang under any circumstance.

@ileitch  I have tried to fix this problem in #54, can you try it out and see if it works? This is probably not the most efficient way of doing this, but I want to be absolutely sure we don't run into any multi threading issues.

I think I too have been running into this issue when using Swift Shell to run some Handbrake transcoding commands (there's a whole lot of output even without it running verbosely). I am ending up with several zombied Handbrake processes and my program is left hanging. I have verified that it is not issuing a log command immediately after my SwiftShell.run() and so I suspect I too am hitting this problem.
Because of how I am using the result of the SwiftShell.run(), it would not be easy for me to use the runAsync workaround.
I am testing the fix in #54 right now to see if it resolves my issue.

I was previously using my own homemade class for running shell commands which worked, but I wanted a bit more power/functionality and didn't want to build it myself. That's when I found this framework and just recently started using it instead. It has the same clean usage as my homemade solution, but it far more powerful/organized and meant I've got one less thing to manage myself.
As soon as I switched to this though, I started noticing my handbrake commands were frequently hanging or becoming zombies and my program would hang. Due to my busy schedule I hadn't had time to look into it until today, which is when I saw this issue and thought it may be related to my problem.

@ileitch @Ponyboy47 Have you had a chance to test out pull request 54? Did it work?

Sorry I forgot to respond after testing this.
Yes the fix in #54 did allow my program to continue execution as expected :)
Thank you for identifying and creating this fix!

Sorry I haven't tried it. I stopped using SwiftShell when I discovered this issue. The PR looks good though 👍🏼

Excellent, I have merged the PR and will release a new version as soon as the CI tests pass.

The finish command says this:

However, when i do a asyncCommand?.stdout.read() as instructed, it takes a very long time to read and complete. Essentially, it still hangs the app. After like about 2 mins, it finally returns.

Could you post the code, including the shell command?

let asyncCommand = SimulatorCommand.executeBuild(xctestrunFilePath, onSimulatorWithId: self.simulator.id) { value in
    print("The command has truly ended")
}
asyncCommand.stop()
_ = try? asyncCommand.finish()
_ = asyncCommand.exitcode()
asyncCommand.stdout.read()
asyncCommand.stderror.read()

This is the code i ran.
The file that is running is in the command is the xcode simulator.
Basically, i wanted the stop command to stop immediately so that the print statement will be printed.
But it hangs a but on the both read commands. Before exiting.

The first line runs your runAsync commmand under the hood.

OK it looks like this had something to do with it.
Ignore my previous text.


HPI Q1 22

Objective:
targeting better stability of the widgets
Success metrics:

Community issues are resolved and at a low number
widgets should be stable and old issues must not regress
increase in the test coverage while resolving the issues

RACI Matrix:

Responsible
Accountable
Consulted
Informed

@vibhandikyash @wmdev0808 @techbhavin @Tooluloope @vicky-primathon
@Tooluloope

@somangshu @dilippitchika

Notes HPI Q1 22:

60 issues total
all need defined estimate 😢
18 issues in needs info, should be divided between the team
the team further decides if the issues should be picked up, if all relevant information is available, if picking up add the estimate and move the issue to product backlog, else drop a relevant comment, remove it from the epic and move it back to icebox, you could also choose to assign me / @dilippitchika here
5 issues in needs design / PRD, @momcilo-appsmith / @dilippitchika to revert
9 issues in product backlog needs to be assigned and estimated

Ongoing work roster:
check ongoing work for everyone on the roster

Author
PR

Vicky
3

Paul
4

Tolulope
2

Yash
7

Bhavin
5

Actionable items:

Estimation for all the tasks from product backlog to done.
Issues assigned to somangshu or unassigned in product/sprint backlog need to be assigned
If have multiple issues in backlog reassign to another developer internally with fewer tasks.
Product backlog is not fully estimated. Devs are responsible to assign.

Action items HPI 3 Feb

Camera enhancements #10077 to be assigned as Paul is occupied
#10771 - Tolu to talk to Satish

Action Items

Paul to Truncate text as POC for #10771
Vicky to clear out items in Product - Done columns (High Priority for QA)

Move issues from Icebox to Product backlog (Set Estimate)
Set definite issues per sprint for better visibility and clarity
@dilippitchika should drop issues in the Needs PRD pipeline on Slack for discussion

HPI

Bhavin has a lot of bandwidth
Close 10696 - It’s stuck since long
Needs info pipeline needs to be cleared

Wid


feat: --shm-size 8G to the docker run

Description
Torch dataloader gives errors. Need to be able to add more memory.
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

SGTM.
Thanks for the issue!


Should we change gridsearch downsample default?

Top is downsample at 5 milliseconds, bottom is every 2ms. While 2ms clearly reveals another spike at 35ms (which is very good), it does so at the cost of messier STL (for the moment, this may change if we improve preprocessing).

The downsampling adds a speed cost of  t*log(t).

Going up to 9 derangement improves this:

We can go to:

6 Derangements and resampling of 200 Hz; or
5 derangement and resampling of 250 Hz

Before we run out of memory.


Unable to Create EcsDocument in Powershell 5.1

ECS integration/library project(s) (e.g. Elastic.CommonSchema.Serilog):Elastic.CommonSchema.Serilog,
ECS .NET assembly version (e.g. 1.4.2): 1.5.3
.NET framework / OS: netstandard2.0
Description of the problem, including expected versus actual behavior:
I have a Powershell script that I attempt to run that creates an Ecs Text Formatted Log and either outputs that log to the console or to a file.  I have found that this package works as expected when I am running in PowerShell 7, but it throws the following error when I attempt to run the same script in PowerShell 5.1.
System.NullReferenceException: Object reference not set to an instance of an object.
at Elastic.CommonSchema.EcsDocument.GetAssemblyVersion(Assembly assembly)
at Elastic.CommonSchema.EcsDocument.GetService()
at Elastic.CommonSchema.EcsDocument.CreateNewWithDefaults[TEcsDocument](Nullable1 timestamp, Exception exception, IEcsDocumentCreationOptions options)
at Elastic.CommonSchema.Serilog.LogEventConverter.ConvertToEcs[TEcsDocument](LogEvent logEvent, IEcsTextFormatterConfiguration1 configuration)
at Elastic.CommonSchema.Serilog.EcsTextFormatter1.Format(LogEvent logEvent, TextWriter output)
at Serilog.Sinks.SystemConsole.ConsoleSink.Emit(LogEvent logEvent)
Digging into the code, the issue originates with this call in the EcsDocument.cs -> GetService() method on the line
var entryAssembly = Assembly.GetEntryAssembly();
When calling assembly.GetName(); on this Assembly object in the GetAssemblyVersion(Assembly assembly) method, it throws a null exception.
In PowerShell 7, if I output that value, it will read: pwsh, Version=<IP_ADDRESS>0
Any idea why the Assembly.GetEntryAssembly(); is not compatible with PowerShell 5.1?

Thank you for bringing this to my attention!
I created: https://github.com/elastic/ecs-dotnet/pull/295 which will treat Assembly.GetEntryAssembly(); as something that can return null (e.g in IIS it might do as well).
It also brings the default service discovery in line with what we do in https://github.com/elastic/apm-agent-dotnet

Awesome!  Any idea when we could expect a release with this change?


Inconsistent formatting of new Error().stack

Bug description
My use-case
I've written a very simple test-framework, which uses new Error().stack to locate call sites in tests - like this:
        const location = new Error().stack!
          .split("\n")[2]
          .replace(/^\s+at /, "");

As you can see, I rely on the formatting of the stack string, which has so far been consistent for me under ts-node, as well as with node without TypeScript, as well as in the browser.
Framing the problem
With tsx, I found this format deviates, by including a source location and citing the source-code line. While this preamble usually appears in the console when node prints an unhandled error, this is not normally included in the stack property.
While (to my knowledge) there is technically no standard mandating any specific format, using new Error().stack for this purpose is currently the only widely available means we have of obtaining call sites in JS - it's therefore important this be consistent with other platforms.
Reproduction
I've created a minimal example to demonstrate the issue:
https://github.com/mindplay-dk/tsx-bug
(Note that this reproduction cannot come in the form of a code-snippet you can copy/paste, as this issue only occurs when loading an actual module.)
To run the example, clone the repository locally, then run the run.sh script, which will:

Package hello_a into a tarball.
Install hello_a from the tarball as a dependency in hello_b.
Run the test script in hello_b.

The test script in hello_b will run hello.ts, which will call a simple function in hello_a:
export function run() {
  return new Error().stack;
}

It will print the return value from this function to the console with some delimiters:
import { run } from "hello_a";

console.log("-----");
console.log(run());
console.log("-----");

The actual output of the script is:
-----
/home/mindplay/workspace/tsx-bug/hello_b/node_modules/hello_a/dist/index.js:4
  return new Error().stack;
         ^

Error
    at null.run (/home/mindplay/workspace/tsx-bug/hello_b/node_modules/hello_a/dist/index.js:4:10)
    at null.<anonymous> (/home/mindplay/workspace/tsx-bug/hello_b/hello.ts:4:13)
    at Object.<anonymous> (/home/mindplay/workspace/tsx-bug/hello_b/hello.ts:5:20)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.v (/home/mindplay/workspace/tsx-bug/hello_b/node_modules/@esbuild-kit/cjs-loader/dist/index.js:1:901)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
    at async Promise.all (index 0)
-----

The expected output (without the preamble) would be:
Error
    at null.run (/home/mindplay/workspace/tsx-bug/hello_b/node_modules/hello_a/dist/index.js:4:10)
    at null.<anonymous> (/home/mindplay/workspace/tsx-bug/hello_b/hello.ts:4:13)
    at Object.<anonymous> (/home/mindplay/workspace/tsx-bug/hello_b/hello.ts:5:20)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.v (/home/mindplay/workspace/tsx-bug/hello_b/node_modules/@esbuild-kit/cjs-loader/dist/index.js:1:901)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:168:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
    at async Promise.all (index 0)

Note that this issue does not affect packages with "type": "module" - to demonstrate this, you can add "type": "module" to hello_b/package.json to see that the output does not have the preamble:
-----
Error
    at run (file:///home/mindplay/workspace/tsx-bug/hello_b/node_modules/hello_a/dist/index.mjs:2:10)
    at null.<anonymous> (/home/mindplay/workspace/tsx-bug/hello_b/hello.ts:4:13)
    at ModuleJob.run (node:internal/modules/esm/module_job:197:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:337:24)
    at async loadESM (node:internal/process/esm_loader:88:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)
-----

Environment
System:
    OS: Linux 5.10 Ubuntu 16.04.7 LTS (Xenial Xerus)
    CPU: (8) x64 Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
    Memory: 5.13 GB / 6.13 GB
    Container: Yes
    Shell: 4.3.48 - /bin/bash
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: 1.22.4 - ~/.npm-global/bin/yarn
    npm: 8.5.5 - ~/.npm-global/bin/npm
  npmPackages:
    tsx: ^3.10.0 => 3.10.0

Can you contribute a fix?

[ ] I’m interested in opening a pull request for this issue.

Under those specific conditions, in a nutshell, yes.
It's the output you'd expect to see on a console - but it's not the return value you normally get from this API.

I'm going to close this because this is a problem in Node.js rather than tsx.
tsx defers source map support to Node.js when it's available.
Reproduction
Create file index.js:
console.log(new Error().stack);

//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJtYXBwaW5ncyI6IkFBQUEsUUFBUSxJQUFJLElBQUksTUFBTSxFQUFFLEtBQUsiLCJuYW1lcyI6W10sInNvdXJjZXMiOlsiL1VzZXJzL29zYW1lL0Rvd25sb2Fkcy90c3gtYnVnLW1hc3Rlci9oZWxsb19iL2Vycm9yLXN0YWNrLmpzIl0sInNvdXJjZXNDb250ZW50IjpbImNvbnNvbGUubG9nKG5ldyBFcnJvcigpLnN0YWNrKSJdfQ==

Use node to run the file:
$ node index.js
Error
    at Object.<anonymous> (/index.js:1:13)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47

Use node to run the file with flag --enable-source-maps:
$ node --enable-source-maps index.js
/error-stack.js:1
console.log(new Error().stack)
            ^

Error
    at Object.<anonymous> (/error-stack.js:1:13)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47

Thanks for spending the time to write a lengthly report (twice). But next time, you don't need to provide the majority of what you provided. Please just say "new Error().stack is inconsistent" in "Bug description" and proceed to demonstrate how. That would be easier for others to read, understand, and support you.
In this issue, sections "My use-case" and "Framing the problem" are unnecessary. Specifically, you don't need to explain how you're parsing the stack.
In your minimal reproduction, there's a lot that can be reduced. For instance, you can simply install from directory instead of adding an npm pack step. Or not include a dependency at all. You can also remove TypeScript to minimize the debugging surface.
Since you previously said you didn't know how to create a minimal reproduction for this, here's a sufficient reproduction:
Given a file error-stack.js:
console.log(new Error().stack)

Running in node and tsx yields different values:
$ node ./error-stack.js
Error
    at Object.<anonymous> (/error-stack.js:1:13)
    at Module._compile (node:internal/modules/cjs/loader:1120:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
    at Module.load (node:internal/modules/cjs/loader:998:32)
    at Module._load (node:internal/modules/cjs/loader:839:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47

$ tsx ./error-stack.js
/error-stack.js:1
console.log(new Error().stack)
            ^

Error
    at <anonymous> (/error-stack.js:1:13)
    at Object.<anonymous> (/error-stack.js:1:30)
    at Module._compile (node:internal/modules/cjs/loader:1120:14)
    at Object.v (/Users/osame/Library/pnpm/global/5/.pnpm/@esbuild-kit+cjs-loader@2.4.0/node_modules/@esbuild-kit/cjs-loader/dist/index.js:1:901)
    at Module.load (node:internal/modules/cjs/loader:998:32)
    at Module._load (node:internal/modules/cjs/loader:839:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:170:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:541:24)

Thank you for looking into this - and thanks for the advice!
I do have a tendency to over explain things - my experience elsewhere has been that of issues getting closed for not having enough "meat" on them, not clearly explaining why the issue was opened.
I had no idea node was doing this, as I've never used --enable-source-maps and didn't realize that's all tsx was doing to enable it. I assumed there was a custom error handler or some magic to make stack-traces work with compilation and everything - nice to know that this is really just leveraging a built-in node feature, I had no idea.
Thanks again! (can I donate to you or to the org behind this project somewhere?)

For anyone else digging around and finding this issue, in my case the solution was that with ts-node I was using import "source-map-support/register";, which fixes this very issue with ts-node but causes it with tsx.
I simply removed the import "source-map-support/register"; line and stack traces worked as expected again.
Hopefully this helps someone else. 😄


Each character page should have an i on it for further information

Each page within the character section of the application form needs an i for further information (see below):

When they press the i a pop up with Guidance appears and a link to the relevant section of the Good Character Guidance - we will need to update these links as we receive them.

@mbrookeswebdev anchors as follows:

[ ] One next to the declaration page bold bit where it talks about continuing duty to disclose: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#continuing-duty-to-disclose
[ ] the criminal offences: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#criminal-offences
[ ] motoring offences: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#motoring-offences
[ ] fixed penalty notices including motoring: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#fixed-penalty-notices-including-motoring
[ ] financial matters: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#financial-matters
[ ] Q8 and 9 under financial matters both go here: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#bankruptcy-or-iva
[ ] Q10 and 11 under financial matters go here: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#late-tax-or-VAT-returns
[ ] Q12 under financial matters goes here: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#hmrc-fines
[ ] Professional conduct goes here: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#professional-conduct
[ ] Further info to be disclosed goes here: https://judicialappointments.gov.uk/guidance-on-the-application-process-2/good-character/good-character-guidance/#further-information-to-be-disclosed


Inline runnable examples with RunKit

I'd like to propose using RunKit embeds for the examples in immutable's documentation. The way I've implemented it, the existing examples remain as is, but also have a "run it" button on the bottom right. When clicked, a RunKit embed is swapped in and the example becomes runnable and editable:

As you can see from the above gif, we've also taken the time to add native support for Immutable classes into RunKit, so that all the objects show up correctly (you can try this now here).
Additionally, I made some custom assert.equals/etc so they show up nicely too:

Some technical details:

Its designed in such a way that if RunKit is down, the site behaves like before (so no absolute dependency).
I've modified the markdown parser so that if you add "<!-- runkit:activate -->" before a code snippet, it will be turned into a runnable snippet, and the others are left alone.
I've left some as not runnable, since they rely on the new unpublished 4.0.0 changes. Once 4.0.0 goes live, these could be made runnable too (or alternatively I could modify the examples to use the current API, but I decided to not make any content changes at all, just usability).
Some examples were not technically runnable on their own, as they do not contain the proper imports. RunKit has a solution for this called the preamble (where you can load code before the users code). I've kept these examples the same by using this feature and placing the imports in a not visible first cell. However, I am happy to simply add the imports to the examples themselves too.

The basic goal we're trying to accomplish is to make code immediately usable in docs, to shorten the time it takes to get familiar with a library. Lodash has been using RunKit on their documentation for about a year now, and Express recently incorporated RunKit into their Getting Started example as well. https://expressjs.com/en/starter/hello-world.html . Would love to see the same here, and I am happy to make any changes as necessary.

This is super cool, thanks @tolmasky!


fix: 1. add default few shot sample instead of query from aos; 2. rem…

as per title

deprecate due to better alternative been raise


About MPI-INF-3DHP's training log

Hi author,
Could you please release the Stage I & Stage II's training log which train on MPI-INF-3DHP dataset??
Thank you so much!!

Sorry, I don't have access to the server where the 3DHP results are located at the moment, so I can't provide the log.


docs/2.3.0/Phaser.Rectangle.html#bottom

Docs

bottomLeft is Missing
bottomRight h4 is 'bottom'

Rectangles don't have a bottomLeft property, which is why it isn't in the docs. Have corrected the bottomRight one though, thanks.


Reset cursor position after app update

Objective

CursorLeft events reset the cursor position immediately
This is an issue if there are other events in the same frame as the position is cleared before those events are read by user code
Fixes #3752

Solution

Reset the position after the app update.This fix the case I'm interested in: https://w3c.github.io/pointerevents/#the-pointerup-event

pointerup events, which winit uses to trigger MouseInput events for mouse button up, are immediately followed by a pointerout event on browser that don't support the "hover"
this means that on those browsers, mouse button up in Bevy don't have the cursor position available as it has been reseted at the start of the frame
most UI frameworks (at least, bevy_ui and bevy_egui) react on mouse button up events
so UI won't work on mobile in wasm

Typically "resource state" is generated by processing all events since this update started in the order they arrive. The problem is that this "projection of event state" is lossy (ex: you cant find an intermediate position of the cursor, only the last position of the cursor). Resource state is provided as a way for users to query the "current state of a thing as of this frame" as a shorthand for regenerating the current state by processing events one by one. Up until now, if the intermediate state was required by the app, the solution was to consume events directly. Resource state == "easy to access and current as of this frame if you were to process all events in the order the arrived". Events == "harder to access current state, but gives you full access to the changes in the order they occur".
This change breaks a number of the assumptions above:

That the resource state is the current state. There is now one frame of lag when processing "pointerout" events.
That the resource state is the product of processing all events in order. Due to the lag, the resource state is out of sync with the event feed.

If there is no other solution to this problem, I'm open to considering this. But I'd like to solve (1) and (2) if we can.

This appears to be resolvable by just handling the "no cursor position" case properly in the interaction handler. I think I have a working solution. Just testing edge cases now.

This appears to be resolvable by just handling the "no cursor position" case properly in the interaction handler. I think I have a working solution. Just testing edge cases now.

I think handling it in the interaction handler could work if you don't care where the mouse is when you have the mouse_up event.

I think thats already the case right? Isn't that desirable behavior?

For drag and drop or selection, if you don't use the cursor position on button up, it means you have to keep an internat state of where the cursor was last seen.

Hmm that might be something we want to provide then (we do already track this, so we could have a "last cursor position" on windows). Introducing information lag in the interest of specific scenarios feels wrong to me.

I'll create a new PR that handles the "no cursor position" correctly in the interaction handler. It will also fix another bug on wasm that leaves the button pressed when a click press results in a scroll (present both in this PR and in my interaction fix).


bottom scroll bar removed

close issue -> #670
https://github.com/codervivek5/VigyBag/assets/114687502/403e18d8-8652-4dac-8873-20899bbd3aaf

@codervivek5 have a look!!! bro


Streaming data test for DPI model and FPGA

Substantial further work on the DPI model to exercise the device much more thoroughly, fixing a number of issues in its original implementation, and extending it with a view to supporting control transfers properly and exercising abnormal conditions such as bus errors, disconnects etc.
Randomized data streams in both directions, using randomized packet sizes, exercising all endpoints concurrently and randomized retrying. DPI model collect some specific responses and timing is more variable, though still friable.
A host-side Linux application provides the higher level streaming functionality and checking allowing the streaming test to run on FPGA.
Coding style migrating incrementally towards standard.
All of the above work, made possible by the inclusion of diags functionality (still very much required) means we now have two t-l tests 'usbdev_test' (a basic smoke test) and 'usbdev_stream_test' which is much more demanding. Both pass in Verilator sim. OTTF software specifies test configuration to DPI model, so a single chip build can run both tests (more to be added).
Please provide comments/feedback on structure/style/readability etc; nothing is expected wrt USB knowledge or reproducing test passes etc. Draft.
Thanks -A

Hi @alees24 ,
thanks for the PR. I did not yet dive into the details. What I think should be done:

Factor out [gpiodpi] commit into seperate PR. It's uncontroversal and will be merged without questioning.
Rebase on current master and resolve conflicts. There seem to be many. In addition, there is also a rebase commit (Rebase TopUSB work to local master the first one). It's not clear to me what it does and whether it's really needed. Can you please clarify?

The rebase commit was something that another person did in trying to resurrect my repo after I moved it to a different laptop, and is I'm afraid responsible for the messy commit history, and the presence of gpiodpi and documentation-related changes in my current branch. (Those changes have already been merged actually)
I ran out of enthusiasm on Friday, but the next task is to rebase the intended changes onto master and drop that unwanted commit! Apologies for any confusion.

Superseded by #17235


go-guru.el: go-guru-set-scope depends on subr-x, but does not 'require' it

Whenever I try to evaluate M-x go-guru-set-scope, I get the following error:
go-guru-set-scope: Symbol’s function definition is void: string-join

M-x version reports:
GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.24), modified by Debian

From what I can tell, string-join comes from the subr-x package, and go-guru-set-scope succeeds if I explicitly evaluate (require 'subr-x) first.
Per the advice in subr-x¹, I believe that go-guru.el should include the line
(eval-when-compile (require 'subr-x))

¹https://github.com/emacs-mirror/emacs/blob/9f58ed156974f6345a85da419c57c4235f549f2a/lisp/emacs-lisp/subr-x.el#L33-L34

(CC @jvshahid)

I wonder why I didn't run into this issue, probably the order in which I load features in my init file. @bcmills do you want me to submit a PR ?

@bcmills do you want me to submit a PR ?

Would be nice. 🙂
(I have a local workaround, but it seems like a good idea to fix this for other users, and since I install via MELPA I don't have a good setup for testing fixes.)

created #259 to address this issue

Wrote this in the pull request as well, but in order to improve backwards compatibility, we could just remove string-join and instead using mapconcat 'identity. string-join is only available in Emacs >25.3

I'll reply on the PR just to consolidate everything related to this specific PR in one place.


Update working-with-the-docker-registry.md

Why:
Closes:

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@Tejindrakhatri Thanks for opening a PR! ✨
Please fill out the pull request template in it's entirety in the top comment in this pull request, then we'll get this up for review! 💛


[RFC] Make possible for server to listen unix socket as well

Currently, the only way to run RR is to listen regular ports 80, 443 for accepting requests. I would like to have an option to listen unix socket as well. This is useful for cases when RR is set up for running behind an edge nginx.
If community accepts such an initiative, I would be able to prepare a PR.

@luza Hey :) I want to clarify a little bit your request. At the moment you can listen unix sockets via FastCGI option in config. You can replace TCP in the sample with unix://rr.sock. Is that what you need?
 fcgi:
   # FastCGI connection DSN. Supported TCP and Unix sockets.
   address: unix://rr.sock

Yes, FastCGI is an option. Already this ticket created, I realised that there is no reason why fcgi socket can't fit my needs.

@luza Great. Thanks


[openal-soft] Add ALSA dependency on Linux

What does your PR fix?
openal-soft on Linux requires ALSA and doesn't work without it. I'm not sure what the "host" field is and I couldn't find it in the documentation so I just set it to true just like for the other dependencies.

Which triplets are supported/not supported? Have you updated the CI baseline?
All, no

Does your PR follow the maintainer guide?
yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
yes

I'm not sure what the "host" field is and I couldn't find it in the documentation

https://github.com/microsoft/vcpkg/blob/master/docs/users/host-dependencies.md
You probably should remove it.


SCTP_SEND_FAILED_EVENT with error = 0

Hi Guys,
In Janus Webrtc server I get SCTP_SEND_FAILED_EVENT like this:  Sent message with PPID = 53, SID = 1, flags: 0x0005 due to error = 0x00000000
I could not find any description for error code 0
Appreciated for any comment.

According to RFC 6458 the description of the field is:
   ssfe_error:  This value represents the reason why the send failed,
      and if set, will be an SCTP protocol error code as defined in
      Section 3.3.10 of [RFC4960].

So my guess is that the association is not terminated due to the reception of an ABORT chunk which includes an error cause. Maybe just due to timeout?

Thanks for your reply, which timer I should change to confirm this?


Fixed headings in getting-started.md

Fixed incorrect heading levels

@angusrtaylor,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Added Go snippet for SQS Process message

Issue #, if available:
Description of changes:
Added Go snippet for SQS Process message

Thanks.
Can you please update the snippet-data.json file within this snippet folder please? Add this file and lang to the array inside there.


[WIP] Translation into Korean

Just started translating the words into Korean!

@1JO Any further progress?

There has been a change in the way Translation is done.
If you are still willing to do this please refere to the wiki.


Update google/go-github to v55

Codecov Report

Merging #727 (ef23497) into main (0448de7) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #727      +/-   ##
==========================================
+ Coverage   93.90%   93.94%   +0.03%
==========================================
  Files          85       85
  Lines        8193     8191       -2
==========================================
+ Hits         7694     7695       +1
+ Misses        380      377       -3
  Partials      119      119

Files Changed
Coverage Δ

internal/reporter/github.go
76.92% <100.00%> (+1.13%)
:arrow_up:


Progress bar during training

It would be nice to have some sort of progress bar or better feedback during training. At the moment you get a "Starting training" message then next message is after 100 iterations and in between there's no indicator of whether it's working or not.

You can set the log_interval to something lower than 100 as an additional
argument. We should have an output after the first iteration thought to
show the user that training is really working.
On Dec 2, 2017 19:16, "maxbartolo"<EMAIL_ADDRESS>wrote:
It would be nice to have some sort of progress bar or better feedback
during training. At the moment you get a "Starting training" message then
next message is after 100 iterations and in between there's no indicator of
whether it's working or not.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/uclmr/jack/issues/345, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABU6G08Aow242sU1Nm3c5ftQf0bwD6Ycks5s8ZP_gaJpZM4QzZ34
.


^Get-Free* Free Cash App Money Generator in-June-2024-2025

In conclusion, while there are several legitimate avenues to potentially earn free Cash App money, it's essential to approach them with diligence and discernment. By leveraging referral programs, cash back offers, participating in surveys and promotions, and staying informed about Cash App events, you can increase your chances of acquiring free money through the app. Always prioritize safety and be wary of offers that seem too good to be true. With careful consideration and proactive engagement, you can make the most of the opportunities available to earn free Cash App money.
👉✅🔴► CLICK HERE TO GET FREE NOW 🌍~
👉✅🔴► CLICK HERE TO GET FREE NOW 🌍~
Cash Back Offers: Cash App occasionally partners with merchants to offer cash back rewards for making purchases using your linked Cash App debit card. These cash back offers may vary in terms of the percentage of cash back and the eligible merchants. By taking advantage of these promotions, you can earn free money on purchases you would make anyway.
Participate in Surveys and Offers: Some third-party websites and apps offer rewards, including Cash App money, in exchange for participating in surveys, completing offers, or watching advertisements.


About demo test

When I run this code， I meet this problem， I dont konw why，hope your answer。thank you。

demoRetrieval
警告: 名称不存在或不是目录: E:\SLAM相关\回环检测\Code\matconvnet\matlab\mex
In path (line 109)
In addpath (line 96)
In vl_setupnn (line 13)
In run (line 91)
In setup (line 3)
In demoRetrieval (line 11)
警告: MatConvNet is not compiled. Consider running vl_compilenn.
In vl_setupnn (line 24)
In run (line 91)
In setup (line 3)
In demoRetrieval (line 11)
serialAllFeats: Start
serialAllFeats: Done
serialAllFeats: Start
serialAllFeats: Done
错误使用 fread
文件标识符无效。使用 fopen 生成有效的文件标识符。
出错 demoRetrieval (line 79)
dbFeat= fread( fopen(dbFeatFn, 'rb'), inf, 'float32=>single');

Your log says:
"MatConvNet is not compiled. Consider running vl_compilenn"
So it sounds like you haven't compiled MatConvNet. Please follow MatConvNet installation instructions: https://www.vlfeat.org/matconvnet/install/
After that, please remove the files created by your previous run as they are likely empty due to the errors, and the code doesn't redo files if they already exist.


feat: GO Feature Flag dotnet provider

Description
This PR adds a new provider for GO Feature Flag.

Thanks, as always, @thomaspoignant/
@kinyoklion @benjiro please don't feel obligated to review this, but I've added you if you're interested. I'll be taking a look at it myself as well.

I don't know why GitHub has removed @benjiro and @kinyoklion from this one when I have re-request the approval from @toddbaert 😞

I think https://github.com/open-feature/dotnet-sdk-contrib/pull/24#discussion_r1036435370 is my only concern. Unless you know for sure that there's no need to call .Dispose() on the Enumerator, I think we should, or we might have memory leaks or a lot of GC.

If you could add just one more thing before merge: a small readme!

@toddbaert I have added the README, I guess we are good to go.


WFLY-12908 MicroProfile ConfigProviderResolver static reference should be set eagerly

https://issues.redhat.com/browse/WFLY-12908
And other miscellaneous optimizations, including:

Removing redundant no-op service implementation classes
Optimize Config building DUP, removing iteration over all services in ServiceRegistry.

@pferraro thanks!


Feature localize dynamic prefrences

Hello !
After working on dynamic-preferences in the passed several weeks , i needed the package to fully integrate my multi language project.
So i've decided to add the feature to the project ,I've followed the contributing guidelines and i've supported both Arabic and French translations.
This simplifies the addition of any other language later. ( Only needs to add translations , no coding needed )
what do you think about it ?
Waiting for your feedbacks !
Greetings
ElManaa

Hi @ElManaa and thank you for the contribution. Sorry I took a full week to review!
I'm a bit uncomfortble with commiting the MO file into the repo, but we can still find a solution for that issue later.
I'll be releasing a new version of the package today :)


Add MLIL_ADDRESS_OF_SSA and MLIL_ADDRESS_OF_FIELD_SSA operations

The MediumLevelILOperation.MLIL_ADDRESS_OF operation has a Variable operand, but in SSA form, this omits information about the version of the Variable in question. Take the following:

In order to identify where the value of the address esp#4 is being set is instruction 116, one must do something like the following:
stack_var = il.src.src # il is esp#4 = &var_4
ssa_version = il.get_ssa_var_version(stack_var)
ssa_var = SSAVariable(stack_var, ssa_version)
definition = mlil.get_ssa_var_definition(ssa_var)

With an MLIL_ADDRESS_OF_SSA operation, it would be as simple as:
stack_var = il.src.src #il is esp#4 = &var_4#3
definition = mlil.get_ssa_var_definition(ssa_var)

Similarly, an MLIL_ADDRESS_OF_FIELD_SSA operation would be useful.

Taking the address of a variable gives you the address of the variable's location in memory. This does not have any actual association to the version of the variable. The only meaningful version of the variable is where the pointer is being dereferenced or stored to, which may be multiple times and is likely different from the version where the address was originally taken. In the case of your example the pointer is never referenced directly, (the real issue is not recognizing that the top of the stack isn't actually a return) so it would be up to you to determine which context the deference should occur in (here, the return, but in general there is no defined context).
This is intentional design and will not be changed.


aeson 0.9 compatability

ekg compiles with aeson <IP_ADDRESS> (latest), but I haven't run it
aeson change log is here: http://hackage.haskell.org/package/aeson-<IP_ADDRESS>/changelog

See #43.

#43 is now merged, is anything blocking a hackage release?

Released.


Upgrade prod DARIA MongoDB to 3.6

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do?

MLab sent us an email about part of their transition, and how it includes upgrading a bunch of mongodb instances to 3.6. The DCAF DARIA prod DB is one of them. This is a ticket for @colinxfleming to do that.
There's a self-service option we should use outside of usage hours.

What feature or behavior is this required for?

mlab transition

How could we solve this issue? (Not knowing is okay!)

self-service upgrade

Anything else?

nah

this happened automatically!


Wheel scrolling does not work well with Firefox

Hello,
I'm been using waynergy for a couple of months on the latest KDE Plasma 6 and everything works fine except for wheel scrolling with Firefox.
When I open a new browser page I can scroll towards the bottom but if I scroll back it will stop before reaching the top of the page. Other scrolling elements inside the page behave worse, i.e. they don't scroll at all or just for a short path.
Scrolling worked fine with the synergy client on X11 and since I use wayland desktop local touchpad scrolling works fine too. Other non-kde apps like Thunderbird and Chromium have no problems too with waynergy, so it seems a problem only with Firefox.
I tried tweaking some configuration options on Firefox with no result, I wonder if this is a common problem or not and I can provide debugging information if instructed to.
Thanks!

I did run into this in initial testing of Plasma 6, and I suspect it's because the virtual pointer doesn't send discrete events while an actual mouse does, but trying to reproduce it again has been fruitless. Which version of Firefox are you using?

I usually have the most recent Firefox release, 125.0.1 now. When I first installed waynergy I think I was using 123.0.
P.S. the O.S. is openmamba Linux and I am the maintainer.

Problem seems resolved! I'm not sure about what fixed it as there have been many updates including Firefox 24.0.2 and Qt 6.7, but my guess is that the fix could be in 5bd33075416dbb0bf22ffb7a0629faff685468de which I integrated as a patch in waynergy just a few days ago. Is this possible?

I have no idea how this is even possible -- I've been digging through gtk3 stuff trying to figure out where this might be happening over the past few days to no avail -- but yeah, that seems to fix it somehow even though it's completely and totally unrelated. I should probably go ahead and make a release at this point, seeing as how that is useful functionality regardless of whether it fixes a weird firefox input bug.

Actually scratch that, it's even worse now, for some reason, on my end.

Well, after downgrading to waynergy as released in 0.0.16 I rebooted and the problem was back, updading again to the patched release Firefox scrolls perfectly. You may see the changes in the last package release here.


Build failure: java-language-server-0.2.38

Steps To Reproduce
Steps to reproduce the behavior:

build java-language-server-0.2.38

Build log
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/v0cp9q40ajzi3v0j374mljxrj02f0g3s-source
source root is source
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "buildPhase" }
building
[INFO] Scanning for projects...
[INFO]
[INFO] ---------------------< org.javacs:javac-services >----------------------
[INFO] Building javac-services 0.1-SNAPSHOT
[INFO]   from pom.xml
[INFO] --------------------------------[ jar ]---------------------------------
[WARNING] The POM for org.apache.maven.plugins:maven-resources-plugin:jar:3.3.1 is missing, no dependency information available
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.076 s
[INFO] Finished at: 2023-07-30T17:24:14Z
[INFO] ------------------------------------------------------------------------
[ERROR] Plugin org.apache.maven.plugins:maven-resources-plugin:3.3.1 or one of its dependencies could not be resolved: The following artifacts could not be resolved: org.apache.maven.plugins:maven-resources-plugin:jar:3.3.1 (absent): Cannot access central (https://repo.maven.apache.org/maven2) in offline mode and the artifact org.apache.maven.plugins:maven-resources-plugin:jar:3.3.1 has not been downloaded from it before. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

Additional context
Occurs after 2a9d660ff0f7ffde9d73be328ee6e6f10ef66b28, works normally in 2de8efefb6ce7f5e4e75bdf57376a96555986841
Notify maintainers

@hqurve
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.38, NixOS, 23.11 (Tapir), 23.11.20230728.2a9d660`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.15.1`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/store/3j9garb3574mxikwbi6zn594j8mjd19s-source`

Updated nixpkgs today and the issue went away, closing


Implement the repr method

It's quite practical to print(args). Right now the class Arguments does not support it.
Do you plan on using to_string for that?
By the way, I am not sure to_string is a good function name. to_table seems more appropriate.

This is a good point. I think the reason I did not add __repr__ or __str__ was to encourage the use of to_string(), which allows explicitly setting max width. But I guess it'd be beneficial to let __repr__ print the table with a reasonable max width.
Regarding the method name, I actually think to_string is more informative than to_table; I would imagine to_table returning some kind of table data structure, such as a pandas DataFrame or sorts.

__repr__ is implemented as of v0.3.0. It calls .to_string() with max_width set to the terminal's width (or 80 if not a terminal). Closing the issue.

__repr__ is implemented as of v0.3.0. It calls .to_string() with max_width set to the terminal's width (or 80 if not a terminal). Closing the issue.

Thanks!

Thanks!


docs: fix typos and broken anchor link

Combine #432, #431, #428 PRs

@JayKan Please rebase with dev


Feature request: Update Permissions

create a command to update or change permissions on existing datarooms.

fixed in fixed in #14 (use dccmd rooms --help to see commands)

add user / group to room (templates: edit, read, admin)
create rooms without inheritance by providing admin user
create top-level rooms
full details in README.md


version capability issue in UWP App

I have installed:
WindowsAzure.MobileServices  version 1.3.2
WindowsAzure.MobileServices.SQLiteStore  version 1.0.4
But exception is thrown on line:
await App.MobileService.SyncContext.PushAsync();
When I adding in Azure Mobile App setting MS_SkipVersionCheck - everything works.
Everything except incremental pull.
Here is topic on MSDN forum

@programmersommer I have provided additional information on the forum. This is a problem with the package versions you're currently using.

Thank you very much! Now it's clear! )


[VS Code] Could not load file or assembly 'System.Net.NetworkInformation, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Error:
Could not load file or assembly 'System.Net.NetworkInformation, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.
Steps to Reproduce:

I upgraded my VSCode version to 1.20.1 (1.20.1) and installed the VS Live Share Extension.
When I click on the 'Share' button, I get this error.

Version Data

extensionName
VSLS

extensionVersion
0.2.163

protocolVersion
2.1

applicationName
VSCode

applicationVersion
1.20.1

platformName
MacOS

platformVersion
17.3.0

@samirbehara could you please check if the dll is present in the extension directory i.e ".vscode-insiders\extensions\ms-vsliveshare.vsliveshare-0.2.163\dotnet_modules\System.Net.NetworkInformation.dll"

@samirbehara @srivatsn  I believe this is a dupe of #112 is it not?  Can we close and merge?

@srivatsn - I verified that the dll is present in the extension directory.

@Chuxel - I am good. Just wanted to report the issue and have it addressed.

@samirbehara Sounds good.  Moved history.


Typing Error in Docu map.addMarker()

Typing Error in Section Adding multiple markers
Folowing Code-Sample has a typing error:

    // Set a camera position that includes all markers.
    var bounds = [];
    data.forEach(function(POI) {
      bounds.push(POI.position);
    });

  bounds.push(POI.position);

must be

  bounds.push(POI.getPosition());

Maybe the variable "POI" could be called "marker". Thats more accurate.

You are misunderstand. You can not add marker instance.
You can add marker options(json).

Oh sorry, i used the markers variable in your example to fill the bounds array, instead of the data variable. Sorry my bad.


Add [Phishing] #malicious GCEPDA…QEJ3MR

Address: GCEPDAZF6QW64FSHGFWTHRWHLGTQ2C6WHQZH2KVO2QACCZSMX5QEJ3MR
Tags: malicious
Title: Phishing
Requested by @sysmanalex

Wallet contain Stolen funds !

This issue has been closed and anyone with follow up information should refer to the discussion on issue https://github.com/stellar-expert/public-directory/issues/202


dashboards: Enable exemplars for histogram queries in Hubble L7 workloads dashboard

With https://github.com/cilium/cilium/pull/21599 it's possible to
extract traceIDs into exemplars from HTTP flows, but to visualize them
in the Hubble L7 HTTP workloads dashboard, we need to explicitly enable
exemplars on the panels we wish to have them displayed on.
This commit enables exemplars on the HTTP request duration by
source/destination panels.
I opted to not enable it on the top-level request duration dashboard because it's smaller and isn't broken up by source/destination and ends up with potentially a lot of exemplars, making the graph hard to see.
dashboards: Enable exemplars for histogram queries in Hubble L7 workloads dashboard

@squeed no need for a full CI run on this PR, please label it as ready-to-merge if you approve it


⚠ Quirk Club Argentina (API endpoint) has degraded performance

In 1c824aa, Quirk Club Argentina (API endpoint) (https://us-central1-quirkclub-dev.cloudfunctions.net/api/check/api) experienced degraded performance:

HTTP code: 200
Response time: 5816 ms

Resolved: Quirk Club Argentina (API endpoint) performance has improved in 189c72c.


Fixing Read More on notes in prescription

Proposed Changes

Fixes #8643
Removed ReadMore from notes in prescription

@ohcnetwork/care-fe-code-reviewers

Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[ ] Ensure that UI text is kept in I18n files.
[ ] Prep screenshot or demo video for changelog entry, and attach it to issue.
[ ] Request for Peer Reviews
[ ] Completion of QA

Refer: #8643 (comment)
@rithviknishad
I just made changes to the PR as requested.

LGTM


Does firewalld_direct_passthrough add rules in iptables?

I tried below code to create iptables rule. Puppet succeeded but iptables rule was neither created in iptables nor in firewalld chain. What's wrong with it?
firewalld_direct_passthrough {'loopback traffic for INPUT chain':
ensure => 'present',
args   => '-A INPUT -i lo -j ACCEPT',
}
Puppet-run output:
Notice: /Stage[main]/Specs_base::Hardening_linux::Cis_3_6_firewall_configuration/Firewalld_direct_passthrough[loopback traffic for INPUT chain]/ensure: created

Why not just make a zone for lo
firewalld_zone { 'some_name_for_zone':
ensure           => present,
target           => 'ACCEPT',
interfaces       => 'lo',
purge_rich_rules => true,
purge_services   => true,
purge_ports      => true,
}


python: Various comprehension-related simplifications

Many of these changes were suggested by the flake8-comprehensions plugin, and/or by the desire to simplify away unnecessary constructions that Black will inflate.

Oh, right, Xenial…do we get to desupport the Python 3.5 upgrade message yet?

Yeah I fixed this to avoid it; it was just some f-strings in provision.py.

Merged, thanks @andersk!
I suppose the Xenial stuff is only important for production; so it's possible that if we rearranged our test for that a bit to work more like the our "production install" tests (i.e. using a shared release tarball built in a Bionic development environment), we could avoid provision being affected by it.


Various minor fixes for upgrade_admin_server.sh

thanks for the update, just needs to be backported (a github label like needs backport would be nice)
+1

+1


Temperature sensor from Aqara TVOC air quality monitor (VOCKQJK11LM) is not transferred from Zigbee2MQTT 1.35.0 to HomeKit!

Description of the issue
The problem
Temperature sensor from Aqara TVOC air quality monitor (VOCKQJK11LM) is not transferred from Zigbee2MQTT 1.35.0 to HomeKit!
Errors in Logs:
1.
Logger: homeassistant.components.sensor.recorder
Source: components/sensor/recorder.py:232
Integration: Сенсор (documentation, issues)
First occurred: 14:00:04 (1 occurrences)
Last logged: 14:00:04
The unit of sensor.0x54ef4410007be710_temperature (ºC) cannot be converted to the unit of previously compiled statistics (°C). Generation of long term statistics will be suppressed unless the unit changes back to °C or a compatible unit. Go to https://my.home-assistant.io/redirect/developer_statistics to fix this

Logger: homeassistant.components.sensor
Source: components/sensor/init.py:719
Integration: Сенсор (documentation, issues)
First occurred: 14:00:24 (1 occurrences)
Last logged: 14:00:24
Entity sensor.0x54ef4410007be710_temperature (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'ºC' which is not a valid unit for the device class ('temperature') it is using; expected one of ['°C', '°F', 'K']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A"integration%3A+mqtt"

Logger: homeassistant.helpers.event
Source: helpers/event.py:296
First occurred: 14:00:24 (2 occurrences)
Last logged: 14:07:33
Error while dispatching event for sensor.0x54ef4410007be710_temperature to <Job track state_changed event ['sensor.0x54ef4410007be710_temperature'] HassJobType.Callback <bound method HomeAccessory.async_update_event_state_callback of <accessory display_name='Temperature' services=['AccessoryInformation', 'BatteryService', 'TemperatureSensor']>>>
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/event.py", line 296, in _async_dispatch_entity_id_event
hass.async_run_hass_job(job, event)
File "/usr/src/homeassistant/homeassistant/core.py", line 715, in async_run_hass_job
hassjob.target(*args)
File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 501, in async_update_event_state_callback
self.async_update_state_callback(new_state)
File "/usr/src/homeassistant/homeassistant/components/homekit/accessories.py", line 525, in async_update_state_callback
self.async_update_state(new_state)
File "/usr/src/homeassistant/homeassistant/components/homekit/type_sensors.py", line 135, in async_update_state
temperature = temperature_to_homekit(temperature, unit)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/homekit/util.py", line 404, in temperature_to_homekit
TemperatureConverter.convert(temperature, unit, UnitOfTemperature.CELSIUS), 1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/unit_conversion.py", line 73, in convert
return cls.converter_factory(from_unit, to_unit)(value)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/unit_conversion.py", line 375, in converter_factory
return cls._converter_factory(from_unit, to_unit)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/util/unit_conversion.py", line 430, in _converter_factory
raise HomeAssistantError(
homeassistant.exceptions.HomeAssistantError: ºC is not a recognized temperature unit.
It seems to me that somewhere in Zigbee2Mqqt there is an error in the configuration of the Aqara TVOC air quality monitor device (VOCKQJK11LM).
The degree sign "º" is not correct before the letter "C".
Comparison of ºC and °C!
https://github.com/home-assistant/core/issues/107063
Addon version
1.35.0
Platform
Core 2024.1.0 Supervisor 2023.12.0 Debian 12
Logs of the issue (if applicable)
No response

Already fixed in the dev branch.
Changes will be available in the dev branch in a few hours from now.