Misspell on authentication on master

Error
Failed to call service configurator/configure. cannot import name 'AuthenicationResult' from 'sonyapilib.device' (/config/deps/lib/python3.7/site-packages/sonyapilib/device.py)
when trying to authenticate. If I edit the file media_player and replace Authenication with Authentication it works.
Other than that, I get these error whenever I press a button:
Failed to call service media_player/media_next_track. Failed to read command list from device.
Home Cinema is  BDVE4100. I guess maybe not compatible?
Sorry about replying in general, but I'm not a dev!

Hi, thanks for testing!
The spelling error is inherited from the upstream library, where it has been fixed before; causing a mismatch.
As I did not re-authenticate my device since, this code wasn't referenced again in my setup so far.
I fixed it, if you check out the code again, you have the correct spelling.
As far as support for the BDV-E4100 is concerned: it should be supported. The code of the library that is being used by this component has been refactored recently and eliminates a few bugs: I will get around to releasing an updated version of this component when I get back from my holiday in a week.
Could you try to retrieve http://<IP_ADDRESS>:52323/dmr.xml (insert the IP of your device) and post it here?

Of course! There you go:

1
0

urn:schemas-upnp-org:device:MediaRenderer:1
BLU-RAY HOME THEATRE SYSTEM
Sony Corporation
http://www.sony.net/
BLU-RAY HOME THEATRE SYSTEM
BDV-2013
uuid:00000000-0000-1010-8000-fcf1521f11ba
DMR-1.50
playcontainer-1-0

image/jpeg
120
120
24
/bdv_ej_device_icon_large.jpg

image/png
120
120
24
/bdv_ej_device_icon_large.png

image/jpeg
48
48
24
/bdv_ej_device_icon_small.jpg

image/png
48
48
24
/bdv_ej_device_icon_small.png

urn:schemas-upnp-org:service:RenderingControl:1
urn:upnp-org:serviceId:RenderingControl
/RenderingControlBdvSCPD.xml
/upnp/control/RenderingControl
/upnp/event/RenderingControl

urn:schemas-upnp-org:service:ConnectionManager:1
urn:upnp-org:serviceId:ConnectionManager
/ConnectionManagerSCPD.xml
/upnp/control/ConnectionManager
/upnp/event/ConnectionManager

urn:schemas-upnp-org:service:AVTransport:1
urn:upnp-org:serviceId:AVTransport
/AVTransportSCPD.xml
/upnp/control/AVTransport
/upnp/event/AVTransport

urn:schemas-sony-com:service:Party:1
urn:schemas-sony-com:serviceId:Party
/PartySCPD.xml
/upnp/control/Party
/upnp/event/Party

1.1

        1

MS_DigitalMediaDeviceClass_DMR_V001MediaDevices
VEN_0106&DEV_0400&REV_01
Multimedia.DMR

Case closed as the other problem does not match the topic


GH-35176: [C++] Add support for disabling threading for emscripten (from sub-branch)

As previously discussed in #35176 this is a patch that adds an option ARROW_ENABLE_THREADING. When it is turned off, arrow threadpool and serial executors don't spawn threads, and instead run tasks in the main thread when futures are waited for.
Updated version of #35471 because the CI stuff requires me to submit the PR from a branch not called main.
It doesn't mess with threading in projects included as dependencies, e.g. multithreaded malloc implementations because if you're building for a non threaded environment, you can't use those anyway.
Basically where this is at is that it runs the test suite okay, and I think should work well enough to be a backend for pandas on emscripten/pyodide, so subject to reviews etc. it is worth merging (and would be jolly convenient for me if it was).
What this means is:

It is possible to use arrow in non-threaded emscripten/webassembly environments (with some build patches specific to emscripten which I'll put in once this is in)
Most of arrow just works, albeit slower in parts.

Things that don't work and probably won't:

Server stuff that relies on threads. Not a massive problem I think because environments with threading restrictions are currently typically also restricted from making servers anyway (i.e. they are web browsers)
Anything that relies on actually doing two things at once (for obvious reasons)

Things that don't work yet and could be fixed in future:

use of asynchronous file/network APIs in emscripten which would mean I/O could work efficiently in one thread.
asofjoin - right now the implementation relies on std::thread - it needs refactoring to work with threadpool like everything else in arrow, but I'm not sure I am expert enough in the codebase to do it well.

Closes: #35176

@kou Could you try and run the github actions bot on here. If it works then I'll copy all the description across and remove the previous PR
thanks,
Joe

@github-actions crossbow submit test-ubuntu-22.04-cpp-no-threading

Right - that's fixed, I think ready for review

@kou - I did a couple of things on this - firstly I fixed most of those comments you had (and added comments where I think things might not need fixing). Secondly, I ran a build in arm64 on oracle cloud, and the test that failed in CI works just fine on there, so maybe that is just a fluke.

Sorry. I can't review this immediately because I don't have enough time for now. It seems that I need to run tests with -DARROW_ENABLE_THREADING=OFF  on GDB , write some codes and so on to consider what approach is reasonable. I hope that I can do it in the next month.
(@westonpace or @pitrou may be able to review this.)

Thank you for working on this.  This will be a great feature.  I haven't fully understood everything but I think I am getting the picture.  Could you just give a general description of how you might have multiple serial executors?  Is this from multiple user threads?  Or is this becuase the CPU executor and the I/O executor need to be two distinct executors for some reason?

So there's two ways to end up with multiple executors - firstly there's lots of code that assumes that while an executor is running a cpu based task, it can fire and wait for i/o calls. In order to support this kind of waiting in CPU processing code, we still have to keep track of things in multiple executors.
There's also I think some stuff in other things which use multiple executors to run things in parallel whilst keeping each set of executions neatly serialised. And I think things that use nested executors. I found it easier to keep the multiple executors in existence logically, even if in reality there is only ever one thing happening at any time. I did try putting everything in a single executor and a lot of tests failed, so I figured it made more sense to keep the logical structure.
The only other difference is that instead of waiting on a condition when a serial executor is held up by I/o or whatever, it instead loops through all other executors to see if they have any tasks that need running.
Because of that, the concept of a current executor, i.e. the innermost executor being called is used instead of the thread id to detect if a particular executor is running the currently executing task.
The other potential advantage of keeping the logical structure of things like this is that in future, there is potential for support for asynchronous i/o even in systems without threading - e.g. in webassembly there is an extension (currently experimental only, but standards track ) which enables creating and waiting on JavaScript futures. With that, whilst you still often don't have threads, you can do i/o in parallel with computation. That could integrate with this code with minimal modifications I think.

@github-actions crossbow submit test-ubuntu-22.04-cpp-no-threading

@westonpace sorry, I went off sick for a few days, and only just caught up with this. I've think I've fixed all the broken things / missing comments now.
I left those tests in, just because I felt they were useful as examples of what does and doesn't work in single threaded mode, Feel free to remove if you think that's a bad idea.

@westonpace Fixed merge conflicts with recent changes (just to bloom filter testing) and merged up to date. hopefully we're ready to merge now.

@kou any concerns?

The description at the top of the PR is up to date now (and has a brief changelog of what changed from initial PR)

Could you replace the initial description directly instead of adding a new "Updated since initial PR:" section?
The latest decision is the most important thing for us.
If we want to see the history, we can use GitHub's history view UI. (See the "edited" pull down in the top of the description area.)

The description at the top of the PR is up to date now (and has a brief changelog of what changed from initial PR)

Could you replace the initial description directly instead of adding a new "Updated since initial PR:" section? The latest decision is the most important thing for us. If we want to see the history, we can use GitHub's history view UI. (See the "edited" pull down in the top of the description area.)

Okay, it's up to date.

@kou think we're good to merge now?


Add code coverage checks and badges

Copied over from #97
Code coverage report is printed and README badge are updated automatically upon running npm run test:node.
Also, I'm adding the same .vscode/launch.json config used in dwn-sdk-js, makes it pretty easy to run tests in VSCode.

@diehuxx in chatting with @mistermoe and @csuwildcat we'd like to include code coverage but to put in the CONTRIBUTOR.md file rather than at the top of the README.
Code coverage seems a bit too in the weeds to put at the top of the main README... but great to check it on every PR
...by highlighting in CONTRIBUTING we make it clear there's an expectation of tests and every PR will have an updated state reviewers can easily glance at
Something like this:

I'm not sure if istanbul-badges-readme can do this but worth investing and perhaps seeing if we can find something that can.


⚠ Bofrost.fr has degraded performance

In 22120bf, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1185 ms

Resolved: Bofrost.fr performance has improved in eda9bc4.


Commands not executed on Windows

I had hoped fixing the globals issue would solve this, but sadly it doesn't.
On Windows, commands are not executed. They are printed into a terminal, but they don't do anything.
Also, when trying to execute, it will do so just once. I can close the terminal afterwards and call up the same task again, but now not even the terminal gets opened anymore until I restart nvim.
There is no output that I can see at all (apart from terminal the first time)
https://github.com/Dax89/automaton.nvim/assets/17877050/f095d3a2-7a7d-435a-9715-a871565f68bf
I tested this in Windows Terminal on both Powershell and Git-Bash. In WSL, it works, but also only once. On my Arch Linux system, I didn't notice any such problems.

Can I see the tasks.json?
So the command is executed only once? In runner.lua there is a "jobs map" which prevents to execute the same command if it's still running, maybe (for some reason) it's not cleared when the task is completed.

I have tried it in both a C++ and a Rust project
Rust:
{
    version: "1.0.0",

    tasks: [
        {
            name: "build",
            type: "shell",
            default: "true",
            command: "cargo build",
            quickfix: true,
            compiler: "cargo",
        }
    ]
}

C++
{
    version: "1.0.0",

    tasks: [
        {
            name: "test",
            cwd: "${workspace_folder}",
            type: "shell"
            command: "cmake -S . -B build"
        }
    ]
}

I'll look at the runner when I find the time

I'm setting up a VM with windows 10 so I can check if I find something this weekend.

I put some time into debugging this. The issue seems that vim.fn.jobstart never seems to finish (or perhaps even start?). Right now, I don't know how to debug this further.
I use git-bash on Windows as my nvim shell, but I also tried Powershell. Same (lack of) effect.
I don't think the terminal itself is the problem though. I use toggleterm as well and I can execute commands in it.

I have finally installed a VM with Windows 10 and did a simple neovim configuration (lazy + automation).
It looks fine both in launch and tasks configuration.
I have tested these configs:
// launch.json
{
    version: "1.0.0",

    configurations: [
        {
            name: "test launch",
            cwd: "${workspace_folder}",
            type: "shell",
            program: "nvim",
            args: ["-h"],
            default: true
        }
    ]
}

// tasks.json
{
    version: "1.0.0",

    tasks: [
        {
            name: "test task",
            cwd: "${workspace_folder}",
            type: "shell",
            command: "clangd --version",
            default: true
        }
    ]
}

There is a missing ',' after the closing brace of the automaton dependencies.
Both :Automaton tasks default and :Automaton launch default try to open /usr/bin/bash (which of course doesn't exist on Windows). That being said, they didn't become unresponsive the same way they did in my original problem.
I added the following to the init.lua to target git-bash instead:
-- ...
vim.g.mapleader = " "
vim.g.maplocalleader = "\\"

-- share the clipboard with the system
vim.opt.clipboard = 'unnamedplus'
vim.cmd [[let &shell = '"C:/Program Files/Git/bin/bash.exe"']]
vim.cmd [[let &shellcmdflag = '-s']]

require("lazy").setup({

-- ...

And this already introduced the problem. Which shell did you default to on your VM?
You can get the git-bash through the default git installer, it will ask you about installing it at some point.
Also, I am on Windows 11.

There is a missing ',' after the closing brace of the automaton dependencies.

Ooops, I'm writing the code manually by reading the VM :D

Which shell did you default to on your VM?

It's a vanilla windows 10 so I assume that is the good old cmd.exe
I have made some tests and I come across your bug: basically the job stays pending because the command just opens the shell and waits for inputs.
I have changed your shell options as:
vim.cmd [[let &shell='"C:\Program Files\Git\bin\bash.exe"'']]
vim.cmd [[set shellcmdflag='-c']]
vim.cmd [[set shellxquote=]]
vim.cmd [[set shellxescape=]]

And it looks like it works

I looks like changing the shellcmdflag from -s to -c is important. I did this originally because others suggested it for git-bash specifically, but at first glance the terminal itself still works. Therefore I think this is fixed and hope I don't run into follow up problems. Thank you for having a look

If there are any problems (even related to this one) feel free to open other issues!


Lock Button and Off / On Grid Function

Referencing #28
I did the following:

Added a 'Lock / Unlock the Room' Button to the UI.
Added 'Click' Event Listener that calls offGrid() (Future TODO: Can we unlock the room?)
Replaced onGrid function to create a peer object in the same schema as when passed to original   Gun Constructor

The lock button is first unlocked, when clicked will switch to locked. (You can keep clicking and unlocking, locking, but currently there is no  'unlock' functionality)

@Dletta my apologies we had to rollback some breaking changes. Could you refactor?

No problem, I’ll pull back, resolve conflicts and reissue PR?


Esp32 in looping

Hello, I would like to know which name of the board in the Arduino IDE should I select?
After I put the read.me link, my IDE has a huge list of esp32 boards, I selected wt32-eth01 but my esp is looping... I use Arduino IDE 2.0.3

Select ESP32 DEV MODULE

I selected the ESP32 DEV MODULE, but I keep having looping problem, below what is coming out in the serial monitor repeatedly:
rst:0x8 (TG1WDT_SYS_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13836
load:0x40080400,len:3608
entry 0x400805f0
ets Jul 29 2019 12:21:46

It's possible that the code is causing the reset. You try to compile another simple example for testing.

i fixed a problem in the code, but now i have another error:
rst:0x1 (POWERON_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1344
load:0x40078000,len:13836
load:0x40080400,len:3608
entry 0x400805f0
E (51) lan87xx: lan87xx_init(499): wrong chip ID
E (52) esp_eth: esp_eth_driver_install(215): init phy failed


Add a simple benchmark to check retrofit performance.

For #1185 - it's good to have some benchmarks to establish a baseline. This first one doesn't intend to be representative of all use cases, but has minimal business logic to try to stress the integration itself as much as possible. Indeed seeing about a 10% improvement in performance using upstream okhttp, similar to the report.
Edit: Was stupidly creating new client every benchmark iteration, ignore emails.
Benchmark                                            Mode  Cnt     Score     Error  Units
c.l.a.r.downstream.DownstreamSimpleBenchmark.empty  thrpt   20  3406.076 ▒ 105.094  ops/s
c.l.a.r.upstream.UpstreamSimpleBenchmark.empty      thrpt   20  3785.867 ▒ 130.965  ops/s

By the way, to not feel too down, here are the results with 20 JMH threads - as expected our throughput is way better.
Benchmark                                            Mode  Cnt      Score     Error  Units
c.l.a.r.downstream.DownstreamSimpleBenchmark.empty  thrpt   20  12852.210 ▒ 261.126  ops/s
c.l.a.r.upstream.UpstreamSimpleBenchmark.empty      thrpt   20   7064.704 ▒ 112.538  ops/s

JFYI trying on Windows Subsystem for Linux, had the same behavior of connections never being reused. Will be able to check real Linux on Monday

Oops. Could you fix the conflicts, @anuraaga?

Yup, merged

Thank you!


Syncing with the implementation of official repo

The official repo made some changes that are different from the paper.
For example, the paper claims that v2-s uses 272 channels in the last stage, but they changed to 256 in their code, and the author claimed that the code will be the source of truth. Is this repo planning on syncing with the official code?
Thanks

Yes, it is 256
https://github.com/d-li14/efficientnetv2.pytorch/blob/775326e6c16bfc863e9b8400eca7d723dbfeb06e/effnetv2.py#L179
the c column indicates the output of efficientnetv2-s backbone (before the last layer conv-avgpool-linear) is 256.
Or you can put the code in your program and see the output tensor size.


Re-enables gradle build cache

Description
Uses https://github.com/marketplace/actions/gradle-cache to replace gradle-build-action.
Issues Resolved

Resolves #3185

Testing
Passing CI
Check List
~- [ ] New functionality includes testing~
~- [ ] New functionality has been documented~

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

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

Thanks for looking into this, could you explain why you think this will work better/different than removing the flag on the exiting gradle-build-action?

What are the tradeoffs of cache enabled or disabled?
I was having difficulty when the cache was enabled bc there were unpredictable builds. Any time caches needed to be removed, there was no bulk way of doing it. The caches could only be removed 1-by-1 and there are caches for each GHA check which in this repo is a lot since the tests are split into parallel test groups. IMO I haven't seen degradation of the GHA runtimes after the cache was disabled so I'd be in favor of having it remain disabled unless there are good reasons to re-enable it.

Thanks for looking into this, could you explain why you think this will work better/different than removing the flag on the exiting gradle-build-action?

Based on the description on the marketplace, the cache action uses a "small" index and a proxy server which redirects requests to @actions/cache API and the cache receives only the relevant updates. The increased granularity enables GitHub to evict entries better (it removes unused entries automatically).
Another advantage: gradle-cache-action creates a layered cache, and it uses a small "index" cache to identify the required layers. If only a small fraction of files changes, then the action reuses the existing caches, and it adds a layer on top of it. That enables to save cache space (GitHub has a default limit of 5 GiB), and it reduces upload time as only the cache receives only the updated files.

What are the tradeoffs of cache enabled or disabled?

Enabled gradle build cache leads to: Faster builds . Reduced network usage. Cache can be shared between CI agents when remote cache is enabled.

@DarshitChanpura I think I am missing something, what about gradle-build-action that was incorrect that is fixed with gradle-cache-action?
To Craig's concern, any caching system would be faster, but it wasn't accurate; how do we know this will be more accurate?

AFAIU, gradle-cache-action is faster and saves memory by creating a layered cache, and it uses a small "index" cache to identify the required layers. If only a small fraction of files changes, then the action reuses the existing caches, and it adds a layer on top of it.
Here is how it is better than gradle-build-action in their own words:
🚀 Gradle remote build cache backend (pulls only the needed entries from GitHub cache)
🎉 Support multiple remote caches via [gradle-multi-cache](https://github.com/burrunan/gradle-multi-cache) (e.g. GitHub Actions + S3)
👋 Simplified configuration (action name + gradle command is enough for most case)
👾 Less space usage (GitHub imposes overall 5GiB limit by default, so cache space matters)
🔗 Link to Build Scan in build results
💡 Gradle build failure markers added to the diff view (e.g. compileJava or compileKotlin markers right in the commit diff)

I understand Craig's concern, however without trying this solution we wouldn't know for sure whether cache would work for our CI. If it doesn't fit our CI, we can always revert this PR and permanently disable the cache. Wdyt?

what about gradle-build-action that was incorrect that is fixed with gradle-cache-action?

Without data to justify this change I don't think we should move forward.

Would you suggest some steps in gathering the data to verify whether there was an improvement?

I would first recommending asking yourself what you would expect reviewers of this PR to weight in choosing to accept it or not, its very rare that changes are accepted without some form of validation, no?
If you are trying to find an approach I might suggest, starting by running a number of builds with different conditions in your fork, then you can use those results from the GitHub action to make claims with justify of it being faster, or uses less resources.
As Craig mentioned accuracy I would suggest seeing if you can test how the cache invalidation happens, and force different conditions.
These experiments might be with the full build or a streamlined part that is easier to measure/control.  Please let us know the path you are taking and the results you generate so we can weight our options.

I would first recommending asking yourself what you would expect reviewers of this PR to weight in choosing to accept it or not, its very rare that changes are accepted without some form of validation, no?
If you are trying to find an approach I might suggest, starting by running a number of builds with different conditions in your fork, then you can use those results from the GitHub action to make claims with justify of it being faster, or uses less resources.
As Craig mentioned accuracy I would suggest seeing if you can test how the cache invalidation happens, and force different conditions.
These experiments might be with the full build or a streamlined part that is easier to measure/control. Please let us know the path you are taking and the results you generate so we can weight our options.

makes sense... I will update this thread with my results once I have them.

Lets close this out since there hasn't been progress in 2 weeks - please reopen if you pick this back up


Rate limite?

I am sorry, I am new to this. Please, is there a rate limit in using these calls?
Where can I find this answer?
Thanks a lot for your help!

Not sure what you're asking about. When it comes to price polling etc, the only restriction is your node bandwidth. Transaction-related calls are performed subsequently, although you can modify code to fire txns in parallel.


HTC One: Circles around "About" kittens are square

Stock android browser, HTC One
(this also shows other error. I tapped the top kitten, text popup aligned with bottom one)

Fixed by #66


WIP: Pipeline testing

As discussed in previous PR I've moved the Jenkins notes here instead. I've drafted Pipeline testing page where I've included all Jenkins notes. Relevant installation files are in includes/jenkins.
I haven't written anything about Travis CI since I'm not sure what should be the content.

We still need to write some docs about Travis CI. Another cool thing could be maybe to write a small tutorial on how to setup a Jenkins Pipeline project and include the Jenkinsfile template?


assets not work

as Doc , i config it like this:
assets: {
          // Root folder of assets
          folder: "./public",

          // Options to `server-static` module
          options: {}
        },

Then i write a index.html in ./public/index.html, But i try those URL, all can't get the index.html
/index.html
/api/index.html
/api/public/index.html
/api/public/api/public/index.html
/api/api/public/index.html

Please show the full settings.

To fix this issue, i create my own static middleware:
let staticMiddleware = function (req, res, next) {
  if (_.startsWith(req.url, '/api/static')) {
    //must change the url prefix to map to static folder root
    let oldUrl = req.url
    req.url = _.replace(req.url, '/api/static/', '/');
    console.log(`staticMiddleware change req.url: [${oldUrl}] -> [${req.url}]`)
    serve(req, res, finalhandler(req, res))
  }
  else {
    next()
  }
}

To enable Dir access, need modify the error hander:
onError(req, res, err) {
          if (!_.startsWith(req.url, '/api/static') && _.endsWith(req.url, '/')) {
            res.writeHead(302, {
              'Location': '/api/static' + req.url
            })
            res.end();
            return
          }
          res.setHeader("Content-Type", "text/plain");
          res.writeHead(err.code || 500);
          res.end('Error: ' + err.message);
        }

 mixins: [ApiService],
 settings: {
   path: "/api",
   assets: {
          // Root folder of assets
          folder: path.join(__dirname, "./public"),

          // Options to `server-static` module
          options: {}
        },

It should work with this settings. Similar code in examples and it works.

and i found that // Global-level middlewares in settings is not really GLOBAL. It only handle request from /api

@icebob

It should work with this settings. Similar code in examples and it works.
which url should i use to access index.html in assets folder ?
/index.html
/api/index.html
/api/assets/index.html

if you have a root path: "/api", in this case /api/index.html. If no root path, just /index.html`.

OK, it works. But root path is /api, the access path need to be /index.html.

Hmm it's weird. Maybe it doesn't consider the path setting.

But i think it is great. asserts path should not start with /api. Please do not change it :)

I think the assets not use compression , because the root level middleware is not GLOBAL so far, which only handle /api

Global middlewares are added to routes only, not for global static serving. In this case you'd better make a path: "/" route where you can add compression & serve static middlewares instead of global assets.

so the global assets can't use compression ?

why not make the Global middlewares apply to GLOBAL ? (I mean on /)
It not make any sense, because the routes already have its own // Route-level middlewares.
So far, if setting the root path is /api,  then all i can hook is on this path, all other /xxx can't handle. Its not extendable.

So far, I found the only interface I can hook to GLOBAL is onError ......

So the right way to use this library is :
root path: /
route1: /api
route2: /assets
If it is right, then the global assets setting does not make any sence.

No the route can be / too.
root path: /
route1: /api
route2: / (must be the latest)

Can I make an example settings?

yes, please.

not work ......
here is code:
ApiGatewayService ->
class ApiGatewayService extends Service {
  constructor(broker) {
    super(broker);
    this.parseServiceSchema({
      name: "apiGateway",
      mixins: [ApiGateway],

      settings: {
        path: "/",

        port: 10300,

        use: [
          compression(),
          // Security
          // helmet(),
        ],

        routes: [
          /**
           * API route
           */
          {
            path: "/api",
            mappingPolicy: "all",
            // Use bodyparser modules
            bodyParsers: {
              json: { limit: "2MB" },
              urlencoded: { extended: true, limit: "2MB" }
            },
          },

          /**
           * Static route
           */
          {
            path: "/",

            use: [
              // Serve static
              ApiGateway.serveStatic("./public"),
            ],
          }
        ]
      }
    });
  }
  async serviceCreated() {
    this.logger.info(`${this.name} Service created.`);
  }
  async serviceStarted() {
    this.logger.info(`${this.name} Service started.`);
  }
  async serviceStopped() {
    this.logger.info(`${this.name} Service stopped.`);
  }
}
module.exports = ApiGatewayService;

main.js
//new moleculer broker
let broker = new ServiceBroker({
  namespace: config.namespace,
  nodeID: config.nodeID,
  requestTimeout: config.natsTimeout,
  logger: console,
  logLevel: config.logLevel,
  logFormatter: logFormatter,
  transporter: {
    type: "NATS",
    options: {
      url: config.natsHost,
      // user: "admin",
      // pass: "123"
    }
  },
  statistics: true,
});

//load service
broker.loadService(path.join(__dirname, `./services/${config.service}`, '/index.js'))

//start
broker.start().then(() => {
  console.warn(`=====[${config.nodeID}]=====>>>>> started`)
})

open /index.html return
{
  "name": "MoleculerError",
  "message": "Not found",
  "code": 404
}

a strange thing is Service created never print. But my other services printed, does ApiGateway not support by loadService?

Which versions?

a strange thing is Service created never print. But my other services printed, does ApiGateway not support by loadService?
You should set functions in parseSchema

            created: this.serviceCreated,
            started: this.serviceStarted,
            stopped: this.serviceStopped,

Now the /api works weird:
      name: "apiGateway",
      mixins: [ApiGateway],
      settings: {
        path: "/",
        port: 10300,
        use: [
          compression(),
        ],

        routes: [
          {
            path: "/api",
            bodyParsers: {
              json: { limit: "2MB" },
            },
          },

call curl -H "Content-Type:application/json" -X POST -d '{"name": "roy"}' http://<IP_ADDRESS>:1030/api/demo/welcome return:
{
  "name": "MoleculerError",
  "message": "Not found",
  "code": 404
}

But call curl -H "Content-Type:application/json" -X POST -d '{"name": "roy"}' http://<IP_ADDRESS>:1030//api/demo/welcome it works, return:
"Welcome, roy :)"

you see, the // works ...

Which versions are you using?

version:
"name": "moleculer-web",
  "version": "0.6.4",

Try it:
      name: "apiGateway",
      mixins: [ApiGateway],
      settings: {
        path: "",

I just installed it yesterday

OK, set path: "", make both /api and static assets work

Great, I will fix this path: "/" issue in the next version

Thanks for your help 👍


How can I set default protocol as https instead of Http using feign client with eureka?

Hello @pragatech, for load-balanced requests, we get the scheme for the outgoing request from the retrieved service instance of the application you would like to send a request to; so while registering that application in Eureka, you would need to set it up to use https. Please see the docs.


fix: stabilize transitions on top nav

https://github.com/user-attachments/assets/529525f4-9d12-4ddb-b504-3446cd1f4201
The palette updates required two key changes: implementing the ability to disable transitions on dropdowns, and synchronizing the visibility prop changes with pointer events. Without this synchronization, focus isolation would incorrectly activate during transition-out states.
For the nav implementation, we maintain an entry counter for the row, limiting transitions to the first entry only, with the counter resetting on nav exit.

Dedicated to @damassi

Woops. Pushed to wrong branch. Will reopen.


Oracle Database Migration to Azure

Below statement is not clear as to what for is this alternative. I am a Core oracle DBA move into Azure. Please provide clarity to this statement.
Alternatives
If your database is over 2 TB, you can use Oracle Data Guard with Oracle Recovery Manager (RMAN), or use Data Pump to replicate changes after an initial bulk data transfer, which provides a minimal downtime migration.

Thanks for reporting - this issue is under review. This is a Microsoft Internal DevOps Bug ID # 471584

@Asha-Hiremath  the alternative listed here is a suggestion for databases over 2TB, the initial recommendaiton above is suggest for databases under 2TB, does that address your question?
https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/reference-architecture-for-oracle-database-migration-to-azure

Thanks for clarifying, Jason!
On Thu, Aug 19, 2021 at 8:38 AM Jason Roberts @.***>
wrote:

@Asha-Hiremath https://github.com/Asha-Hiremath the alternative listed
here is a suggestion for databases over 2TB, the initial recommendaiton
above is suggest for databases under 2TB, does that address your question?
https://docs.microsoft.com/en-us/azure/architecture/solution-ideas/articles/reference-architecture-for-oracle-database-migration-to-azure
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/architecture-center/issues/3015#issuecomment-901474807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3VEFYPII2JKN5E2PN3DYLT5QZADANCNFSM5B7JTYWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


android  弹出之后,一直转圈圈??

android  弹出之后,一直转圈圈??  iOS是好的
bug

0.4.5

加载中,点击预览还是爆红

这是一个bug.希望尽快修复.  现阶段只能降级处理   photo:  ^0.3.4+1    这个版本是好的

environment ?
use flutter doctor -v

I think you should use the PhotoPicker.pickAsset to use the api.
Of course I also fixed this usage.

Update version to 0.4.5+1.

您好.我测试了.还是一样啊 0.45.1  测试机:HIsense L13<IP_ADDRESS>.00

Look like same of #67 .
If this doesn't work out in the end, can you give me a reproducible Example? It can be a repository or a zip archive.
And indicate flutter version.

flutter version:

version: 1.0.0+1
environment:
sdk: ">=2.1.0 <3.0.0"
photo:  0.4.5 + 1
code:
GestureDetector(                     child: Text('从相册选择'),                     onTap: () async {                       var assetPathList = await PhotoManager.getImageAsset();                       _pickAsset(PickType.onlyImage, pathList: assetPathList);                     },                   ),
`
void _pickAsset(PickType type, {List pathList}) async {
Navigator.of(context).pop();
List<AssetEntity> imgList = await PhotoPicker.pickAsset(
  // BuildContext required
  context: context,

  /// The following are optional parameters.
  themeColor: Colors.black,
  // the title color and bottom color

  textColor: Colors.white,
  // text color
  padding: 1.0,
  // item padding
  dividerColor: Colors.grey,
  // divider color
  disableColor: Colors.grey.shade300,
  // the check box disable color
  itemRadio: 0.88,
  // the content item radio
  maxSelected: 9 - _imgControList.length,
  // max picker image count
  // provider: I18nProvider.english,
  provider: I18nProvider.chinese,
  // i18n provider ,default is chinese. , you can custom I18nProvider or use ENProvider()
  rowCount: 3,
  // item row count

  thumbSize: 150,
  // preview thumb size , default is 64
  sortDelegate: SortDelegate.common,
  // default is common ,or you make custom delegate to sort your gallery
  checkBoxBuilderDelegate: DefaultCheckBoxBuilderDelegate(
    activeColor: Colors.white,
    unselectedColor: Colors.white,

//        checkColor: Colors.green,
),
// default is DefaultCheckBoxBuilderDelegate ,or you make custom delegate to create checkbox
  // if you want to build custom loading widget,extends LoadingDelegate, [see example/lib/main.dart]

  badgeDelegate: const DurationBadgeDelegate(),
  // badgeDelegate to show badge widget

  pickType: type,

  photoPathList: pathList,
);

if (imgList == null) {
  currentSelected = "not select item";
} else {
  List<String> r = []; // img 真实路径数组

  for (var e in imgList) {
    setState(() {
      _showLoadingTag = true;
    });
    var file = await e.file;
    _uploadImg(EditableActivityItem(thumbnail: file.absolute.path));
  }
}

setState(() {});

}
`

Not just code. The problem come from your gradle config and environment.
I need runnable project to reproduce and try to fix it.

这个么?

I need a project, I can't reproduce you problem, so you need commit a whole example to help me locate problem.
A gist can't reproduce your problem.

the same problem happens in example project. please check, thanks!

I need a project, I can't reproduce you problem, so you need commit a whole example to help me locate problem.
A gist can't reproduce your problem.

please run ios example project on your device and go to select photo(s) page,  then press home button, then go back to example app again, you will find there is no photo showing anymore, just a loading item .

I need a project, I can't reproduce you problem, so you need commit a whole example to help me locate problem.
A gist can't reproduce your problem.

please run ios example project on your device and go to select photo(s) page, then press home button, then go back to example app again, you will find there is no photo showing anymore, just a loading item .

The reporter's problem is not the same. It seems that the problem is glide on android. And your problem is from ios, although it may look the same,but its should not be the same problem.

I need a project, I can't reproduce you problem, so you need commit a whole example to help me locate problem.
A gist can't reproduce your problem.

please run ios example project on your device and go to select photo(s) page, then press home button, then go back to example app again, you will find there is no photo showing anymore, just a loading item .

The reporter's problem is not the same. It seems that the problem is glide on android. And your problem is from ios, although it may look the same,but its should not be the same problem.

thanks for reply, this project is amazing and i hope problems from both android and ios will be fixed as soon as possible, thank you very much for your kindness ! 😁

@wys619
In fact, my own iPhone / Android is currently normal.

@wys619
In fact, my own iPhone / Android is currently normal.

problem happens on my devices: iPhone8 plus running iOS13.3 and an android 8.0 device


Workaround for OutOfMemoryError : resize image. #1.

The best correction would however to change all images to real optimized JPEG.

Ok I will launch an image optimizer on all the speaker images...

Thanks for the workaround

Ok, I will check after image optimization.


Change contract_address range to match backend.

This change is

the backend put more restriction than the cairo code in lots of places:
e.g.
https://github.com/starkware-industries/starkware/blob/a290ebf2ab90b523d9f36179a1323c08244cbfd9/src/starkware/starknet/definitions/constants.py#L17

crates/cairo-lang-sierra/src/extensions/modules/starknet/interoperability.rs line 17 at r1 (raw file):
Previously, liorgold2 wrote…
The comment says storage, but the type name is ContractAddress.

Ori already fixed that.

crates/cairo-lang-sierra-to-casm/src/invocations/starknet/interoperability.rs line 74 at r1 (raw file):
Previously, liorgold2 wrote…
Can this be negative?

Yes.
I fixed it in a different PR.

Decided to keep the range [0, 2**251)


not support null safety in dart language

please make the model support null safety..
just add the required keyword
and make the constructor constant with the const keyword.

model creation is not null safe  when all optional setting is active, given a json like:
   "commoditiesSummary": {
        "totElements": 2,
        "createdAt": "2022-09-08T09: 58: 32.743000000Z",
        "updatedAt": "2022-09-08T09: 58: 32.743000000Z"
    },

it produce a model like
class CommoditiesSummary {
  CommoditiesSummary({
    this.totElements,
    this.createdAt,
    this.updatedAt,
  });

  int totElements;
  String createdAt;
  String updatedAt;

instead  of the null safe version (with question point)
class CommoditiesSummary {
  CommoditiesSummary({
    this.totElements,
    this.createdAt,
    this.updatedAt,
  });

  int? totElements;
  String? createdAt;
  String? updatedAt;

Duplicate of #1673 and #1755


Changing the Default Rule Set to DRS2.1 in Firewall Policy

Preconditions

[X] No need to upgrade Python SDK or the Python SDK is ready.

Related command
No new command, just changing a field in CLI
Resource Provider
Network (NRP)
Description of Feature or Work Requested
Changing the Default Rule Set to DRS2.1 from CRS3.0 in PSApplicationGatewayFirewallPolicyManagedRuleSet, there are 2 places needs change, example in below
example in Powershell: https://github.com/Azure/azure-powershell/pull/23760
Minimum API Version Required
2022-11-01
Swagger PR link / SDK link
no swagger needed
Request Example
NA
Target Date
2024-02-01
PM Contact
luke.nowak
Engineer Contact
lishawn
Additional context
No response

Thank you for opening this issue, we will look into it.

@Shawnli222 at least you should share which command and which parameter in Azure CLI will be affected

@necusjz updated the info, pls let me know it is good enough


Move logo_text and logo_text_small values to settings

These are currently blocks in a partial. Overriding them is something very likely to be done in a project, but creating the files and folders necessary to simply change these values is somewhat cumbersome.

Done. Instructions are also added to the documentation.


Disabled modules shouldn't call pkg-config if they are set to be non-builtin

Godot version: Git https://github.com/godotengine/godot/commit/72d87cfbce137b8012e86f678c27f0f19a9771cf
OS/device including version: Fedora 30
Issue description: Someone reported on IRC that non-builtin dependency checking is done even if the module that requires them is disabled. This causes a build failure if the dependency in question isn't installed on the system.
For instance, builtin_libtheora=no will always call pkg-config, even if module_theora_enabled=no is also passed to the SCons command line:
https://github.com/godotengine/godot/blob/72d87cfbce137b8012e86f678c27f0f19a9771cf/platform/x11/detect.py#L241-L247
Steps to reproduce: Build Godot with scons platform=x11 builtin_libtheora=no module_theora_enabled=no.

builtin_*=no should only be used if you want to link against the system provided version. If you don't want to use theora, the module_theora_enabled=no flag should be used.
This could be made more robust but would require substantial changes, and a proper dependency checking system à la configure.

@akien-mga What about replacing if not env['builtin_libtheora']: with if env['module_theora_enabled'] and not env['builtin_libtheora']: (and doing the same for other modules with non-builtin dependency options)?

It's likely still valid yes.


Convert the "slow" Kafka tests to the new IT framework

Converts the following ITs from the old KAFKA_INDEX_SLOW  group to the new framework:
- ITKafkaIndexingServiceNonTransactionalSerializedTest

ITKafkaIndexingServiceTransactionalSerializedTest
ITNilColumnTest

The new category is TransactionalKafkaIndexSlow.
Release note
No user-visible changes.

This PR has:

[X] been self-reviewed.
[X] a release note entry in the PR description.
[X] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[X] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[X] added integration tests.
[X] been tested in a test Druid cluster.

@cryptoe, correct, there is no GHA integration yet. Trying to get a clean build without running the test. Then I (or a GHA expert) can sort out how to run this one in place of the always-failing old one.

This PR build is green except for CodeQL warnings issued on existing code copied into the new IT branch.
As noted, the new IT is not yet integrated with GHA. The next steps are:

Add this IT to the GHA steps for the new ITs
Remove the corresponding old IT from the GHA steps for the old ITs.


OAuth Providers

Description
github, google, etc
Proposed solution
No response
Alternatives considered
No response
Do you want to create a pull request?
No

@theryansmee 🧙♀

Ah sorry I missed this. Yeah I'll have a look 😊 I'll have to do a little Googling as I don't know many haha


Update spin_sidebar.hbs

Signed-off-by: tpmccallum<EMAIL_ADDRESS>
writing
structuring
building -running

This makes more sense now, whereas before the "structuring" menu item came along, it felt like saying "building" meant constructing (vs compiling).
The build command does build, so I guess "Building Applications" is technically correct.
Closes https://github.com/fermyon/developer/issues/435

See https://github.com/fermyon/developer/issues/435 for more conversation around deciding on a new term to replace the original one.


Update getTaskById.ts camelCase 84 2

Please merge this PR to your first PR

Hello @MrRefactoring
I originally tried sending the whole PR via git but was unable: I forked the repository, cloned it, made the changes in branch and pushed to create the pull request.
This is why I sent the requests via Github separately. I cannot merge them, I get that Only those with write access to this repository can merge pull requests.
Please let me know if I am missing a step?

You can just checkout in your patch-1 branch and push changes there


highlight remains after exiting

So the highlight remains active even "after" I exit visual mode.

+1 I am seeing the same behavior

I'm not sure, but I think this solved for me:
set selection=inclusive

Reopen if this is still an issue.


auth-idp-oidc auth LB get updated on every cycle (10 min)

Hi guys,
There is an issue with one of the ingresses, the one that uses auth oidc annotations is getting updated on every cycle run. any idea?

Hi,
Yeah, that's right but it I would think that it does not make sense to change it manually in AWS as long as the resource is managed by alb, so we shouldn't care in such scenario. The scenario to consider would be when the secret changed on the kubernetes side, in that case it needs to be updated in aws also.


I'm using addStream method and passing ByteArrayInputStream as a argument but I want to append the data into single File. Currently it is overriding the old data which came from the inputStream.

   ByteArrayInputStream byteArrayInputStream = new ByteArrayInputStream(data.getBytes(StandardCharsets.UTF_8));         ZipParameters zipParameters = new ZipParameters();         zipParameters.setCompressionLevel(CompressionLevel.ULTRA);         zipParameters.setFileNameInZip(file.getName());         new ZipFile(file + ".zip").addStream(byteArrayInputStream, zipParameters);

This happens most likely because the filename that you set is the same each time. In this case zip4j replaces the content instead of adding new content. Can you make sure that the fileName being passed in this line zipParameters.setFileNameInZip(file.getName()) is unique and does not already exist in the zip file?

That won't be possible with zip4j. You have to first extract your file, then append your content to that file, and then add its content back to the zip file


container runtime is not running via kubeadm

root@clusterworker-HP-EliteDesk-800-G6-Desktop-Mini-PC:~# kubeadm init --pod-network-cidr=<IP_ADDRESS>/16
I0201 13:51:00.203988    5012 version.go:256] remote version is much newer: v1.26.1; falling back to: stable-1.25
[init] Using Kubernetes version: v1.25.6
[preflight] Running pre-flight checks
	[WARNING Swap]: swap is enabled; production deployments should disable swap unless testing the NodeSwap feature gate of the kubelet
error execution phase preflight: [preflight] Some fatal errors occurred:
	[ERROR CRI]: container runtime is not running: output: time="2023-02-01T13:51:00-08:00" level=fatal msg="validate service connection: CRI v1 runtime API is not implemented for endpoint \"unix:///var/run/containerd/containerd.sock\": rpc error: code = Unimplemented desc = unknown service runtime.v1.RuntimeService"
, error: exit status 1
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher

apparently original packages from ubuntu is not working as expected. I believe that we need to use containerd.io and docker.ce.
see https://r2schools.com/how-to-install-docker-on-ubuntu/

addressed by https://github.com/fujitatomoya/ros_k8s/commit/4f9ad27f0e4d6a534bd0f7232c7c2cf3e767ab23


Improve tx db

Description

Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@d6b173b). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 0978dd9 differs from pull request most recent head 5ea0bea. Consider uploading reports for the commit 5ea0bea to get more accurate results

@@            Coverage Diff            @@
##             master     #140   +/-   ##
=========================================
  Coverage          ?   62.91%
=========================================
  Files             ?       34
  Lines             ?     1494
  Branches          ?        0
=========================================
  Hits              ?      940
  Misses            ?      521
  Partials          ?       33

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 d6b173b...5ea0bea. Read the comment docs.


auto upgrade

Is there some way to upgrade automatically?

I hope not - upgrades should be handled by your package manager


Recursion not working properly

This yields -1:
fn fib(n) {
  if (n <= 1) {
    return n;
  } else {
    return fib(n - 2) + fib(n - 1);
  }
}

print fib(2);

Fixed by 0b9aa68 --- it was a problem with the environment nesting.


Unity Unit Test In Play Model

The sample playmode test case is so simple， can you provide a more complicated example ， using gameobject and entity in your unit test case

@ZhouJiaZhi thank you for your request.
I fully agree it's not such a complicated example, but I also found it's quite a bit of a learning curve and a bit of work to get started with unity tests. Any improvements would be very much appreciated and anyone is free to contribute any improvements.

Closing this for low demand. PRs are always welcome of course. Proper play tests seem to be uncommon. Awaiting perhaps some contributions for bigger game developers.
Closing for now.


indices_.reshape(indices_.shape[0], 1024, -1, indices_.shape[2]) error in run_nerf_deform.py

Nice work! Thanks your sharing code. When I rendering.sh one video, there is a problem in this line:
  try:
      indices_ = indices_.reshape(indices_.shape[0], 1024, -1, indices_.shape[2])
  except:
      pdb.set_trace()

I printed the shape of the tensor indices_:
indices_ shape: torch.Size([4, 28544, 2])

28544 cannot be divided by 1024. So what is the reason? And any suggestions?

while running  " sh run.sh 1"  , I  meet  the same error。 what is wrong?
File "NeRFs/run_nerf_deform.py", line 290, in gather_indices
indices_ = indices_.reshape(indices_.shape[0], args.N_rand, -1, indices_.shape[2])
RuntimeError: shape '[4, 850, -1, 2]' is invalid for input of size 131072

Is your input image size 512*512？

yes， I use the  1.mp4   when running  sh process_data.sh .
and the  .jpg files   in dataset/1/0/xxx_imgs  are 512512  pixel 。

You can try to debug. I'll check the relevant code when I'm free.

Is your input image size 512*512？

yes

@aishoot Hi, may I ask have you solved the problem yet ?

@aishoot   Hi, have you solved the problem yet ?

You can try to debug. I'll check the relevant code when I'm free.

I have encountered the same problem and would like to ask if you know how to solve it.


Add microseconds to logs

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?  In order to motivate your point, it may be valuable to explain why this change is useful or what problem is being solved.
Additional Notes
This is the section to put technical guidance/constraints, call out potential regressions, cite sources, and in general offer some exposition on the how of the PR.  This section doesn't need to be incredibly detailed, but it makes life easier for reviewers!
How to test the change?
Describe here in detail how the change can be validated.  This is a great section to call out specific tests you've added or improved, or to acknowledge code sections which are particularly difficult to test.

Current dependencies on/for this PR:

main

PR #141

PR #142

PR #143

PR #144   👈

This comment was auto-generated by Graphite.

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: Fh1RcgohLIXtvXiDWMuk

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: RRcBgCgNPigo0atqHNO7

Graphite Merge Job
Current status: ⏳ Queued to merge
This pull request is currently queued to be merged as part of a stack.
This comment was auto-generated by Graphite.

Job Reference: jw2xvMi2FrdTsr9Ch01v


Support plain arrays

When having plain arrays defined on a PO, the string properties assertion would throw an error:
Error: string values are not supported in page object definitions Key: "0"`

Thanks for the fix! I'm sorry you face issues like that. I'm going to merge and publish it by Friday.

just published it under v2.2.3.


demo ui to work on a gw path

Currently if you put it on a gw path you get 404 for all the resource downloads. But it should work to use e.g. npm run build -- --base-href “/activiti-cloud-demo-ui/". So we could make that a variable and use it in the Dockerfile https://github.com/ryandawsonuk/activiti-cloud-demo-ui/blob/develop/Dockerfile#L7
then we'd be able to pass in an env var at the chart level to tell the ui which path it is meant to be on
and default it to "/". This would mean we'd only need ingresses for the gateway and keycloak

@almerico addressing this - see https://github.com/ryandawsonuk/activiti-cloud-demo-ui/pull/1

We've stopped maintaining the demo UI


fix: :bug: make force_torque_sensor_broadcaster wait for realtime_publisher

The referenced issue shows that some of the tests in test_force_torque_sensor_broadcaster are flaky. This is because the realtime_publisher thread doesn't have time to start before the test tries to publish a message. Any subscription test will fail as the message will not get published if the publishing thread hasn't started.
This is one example solution, but since it modifies the life-cycle behavior of force_torque_sensor_broadcaster, I'm not exactly aware of all of the consequences. I imagine that most nodes will wait for the broadcaster to move to the inactive state anyways so this shouldn't have a negative effect but I am open to feedback.
refs: #263

Thank you for finding this! I have a few questions about possible solutions.

Would it make a difference if we modify the tests and add sleep there instead in the broadcaster's code?
Can we also expect issues in the real world with this? Or do we simply lose few messages at the beginning, if controller is activated directly after configuring?

Thank you for finding this! I have a few questions about possible solutions.

Would it make a difference if we modify the tests and add sleep there instead in the broadcaster's code?
Can we also expect issues in the real world with this? Or do we simply lose few messages at the beginning, if controller is activated directly after configuring?

We could just add a sleep to the test and that should work. I personally prefer synchronizing tests so there is no way they can fail but I couldn't find a way to do that from the test directly as the publisher is a protected member. If you think a sleep would be better, I'd be be happy to switch it. If there are only two threads in the test then it would seem very unlikely to fail as cpu time should go to the publisher thread.
You are correct. The real world affect is that messages would get dropped near the beginning of initialization.

We could just add a sleep to the test and that should work. I personally prefer synchronizing tests so there is no way they can fail but I couldn't find a way to do that from the test directly as the publisher is a protected member.

if you need to access protected members from tests, then you can use friending concept. (Check changed in #154 – or more specifically these lines to see how this is used.)

If you think a sleep would be better, I'd be be happy to switch it. If there are only two threads in the test then it would seem very unlikely to fail as cpu time should go to the publisher thread.

Direct sync, as you proposed, is a much better approach.

I wouldn't classify this as behaviour modification, it simply ensures better initialization in on_configure, it does not affect update() directly other than leaving us w an immediately usable publisher :D
perhaps a throttled warning in the lock-loop would be useful to detect cases of deadlocks?

I would still prefer direct sync in the tests for this. Just to make them more (100%?) stable.

I propose the following resolution of this issue:

Add here proposed approach to all controller that are using RealtimePublisher (for each instance of real-time publisher) + add ROS_WARN_THROTTLE_SKIP_FIRST writing out that we are waiting for lock to get available.
https://github.com/ros-controls/ros2_controllers/blob/d70e4caa9677a2b8c5dec1dc6545cce68aa945b8/force_torque_sensor_broadcaster/src/force_torque_sensor_broadcaster.cpp#L113-L117
Investigate adding fix for this into RealtimePublisher itself, e.g., in the constructor if possible
Remove this temp fix from all controllers and make sure they are working properly with stable tests.

One more question before proceeding as suggested: Do we then actually acquire lock in the line 127 to set default values? @jaron-l can you please check this if you didn't yet?

One more question before proceeding as suggested: Do we then actually acquire lock in the line 127 to set default values? @jaron-l can you please check this if you didn't yet?

I'm not sure I know what you mean for setting default values but yes, the lock is acquired there and used for setting the message frame id.
I briefly investigated moving the wait to the real time publisher constructor and that seems like the best route; however, I hit a problem that I'm still investigating. I'll report back tomorrow.

Okay, I think I understand better what is going on. Hopefully this makes sense.
The root of the problem is that force_torque_sensor_broadcaster::update makes no guarantees that a message will get published, nor does it provide feedback when a message was successfully published. Having the wait right after the RealtimePublisher seems to make it far more likely; however, I think even my current fix doesn't eliminate the problem. To show this, I originally tested running the current version of the code 10,000 times without test failure, but when moving the waits to different locations, I found that the success rate sometimes drops, and indeed, even the original location of the wait produces failures very occasionally. It's hard to estimate the rate because it's low and very dependent on the hardware the test is run on. It likely has a higher failure rate on GitHub Actions VMs due to their internal load balancing, hence the frustration in tests failure in CI but not when people run it locally.
So if the publisher thread is running, why are messages getting dropped? It's because the the publisher periodically obtains a lock. If the publisher thread holds the lock, or turn_ is not set to REALTIME as this PR originally was trying to fix, then force_torque_sensor_broadcaster will not publish the message (code where the two if statements are evaluated to show this). So while the wait fixes one of those if statement checks, it doesn't guarantee that the message will get published.
Proposed solutions:

We could change test_force_torque_sensor_broadcaster.cpp::subscribe_and_get_message to loop between force_torque_sensor_broadcaster::update and test_force_torque_sensor_broadcaster::wait_for until they pass with a max loop count. That way the test doesn't proceed until the message is published and received successfully.
We could implement some sort of feedback into force_torque_sensor_broadcaster to respond if a message was published. This would likely change the return type of force_torque_sensor_broadcaster::update which would be a breaking change.
Any other idea someone else has.

As a side note, we could still implement the wait in the RealtimePublisher constructor. This did help the tests to pass far more likely (at least an order of magnitude on my hardware but it's probably relative) and doesn't conflict with any other solution.

Few more possibilities:

using concurrent queues on RealtimePublisher
check what realtime-group is doing: https://github.com/ros-realtime/reference-system

My most recent commits show how solution 1 would work. I tested it and I couldn't get it to fail.

@jaron-l sorry, I introduced wait_set again.

@jaron-l sorry, I introduced wait_set again.

I went ahead and removed them. Should be good to go now.


Timezone bug in memory dump reporting

Timezone is captured in local timezone.
Convert to UTC with offset value.
App can convert to local time from UTC and calculate the correct duration.
Also return the time as is to show the time of the dump local to the server if it's different.

Fix included in 2.22.6 🚀


Release

GraphQL
Delete projects endpoint

Codecov Report
Base: 68.60% // Head: 67.63% // Decreases project coverage by -0.97% :warning:

Coverage data is based on head (e33b30d) compared to base (46cb018).
Patch coverage: 26.40% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #334      +/-   ##
==========================================
- Coverage   68.60%   67.63%   -0.98%
==========================================
  Files          71       71
  Lines        5453     5561     +108
==========================================
+ Hits         3741     3761      +20
- Misses       1712     1800      +88

Impacted Files
Coverage Δ

api/routes/analysis.py
43.97% <ø> (ø)

db/python/tables/analysis.py
34.24% <4.76%> (-3.13%)
:arrow_down:

db/python/tables/sample.py
27.35% <15.38%> (-1.94%)
:arrow_down:

db/python/layers/sample.py
47.36% <23.52%> (-3.92%)
:arrow_down:

db/python/layers/analysis.py
63.63% <25.00%> (-2.08%)
:arrow_down:

db/python/tables/project.py
29.29% <27.77%> (-1.15%)
:arrow_down:

db/python/tables/participant.py
56.07% <28.57%> (-1.93%)
:arrow_down:

db/python/layers/participant.py
66.35% <42.85%> (-0.74%)
:arrow_down:

api/routes/project.py
47.36% <50.00%> (-2.64%)
:arrow_down:

models/models/project.py
81.25% <50.00%> (ø)

... and 3 more

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

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


Apple Store Connect Build Error

Description
abseil-cpp-binary and grpc-binary causes my failure in my building process.
I am opening my Xcode with open --env FIREBASE_SOURCE_FIRESTORE booksp.xcodeproj . I have tried manually deleting Package.resolved, Clean Build Folder, and Reset Package Caches & Resolve Package versions & Update to the latest package versions.  Though in the error log output, it says which is not allowed when automatic dependency resolution is disabled but I cannot edit and save new version number to Package.resolved so it seems automatic dependency resolution is currently on.
Forgive me to tag @paulb777, it is urgent for me. I have tried and errored dozens times of building, and I have to submit this app by today. If you and other members here have any idea to fix this issue, please let me know.
Sincerely,
Takuzen
Reproducing the issue
On building from Xcode Cloud
Firebase SDK Version
10.21.0
Xcode Version
15.2
Installation Method
Swift Package Manager
Firebase Product(s)
Database, Firestore
Targeted Platforms
visionOS
Relevant Log Output
Could not resolve package dependencies: an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'abseil-cpp-binary' (https://github.com/google/abseil-cpp-binary.git) fatalError

Error
an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'grpc-binary' (https://github.com/google/grpc-binary.git)fatalError

If using Swift Package Manager, the project's Package.resolved
{
  "pins" : [
    {
      "identity" : "abseil-cpp-swiftpm",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/abseil-cpp-SwiftPM.git",
      "state" : {
        "revision" : "06e7506b74bfc47c70f3353e2927ea3e2275230c",
        "version" : "0.20220623.1"
      }
    },
    {
      "identity" : "app-check",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/app-check.git",
      "state" : {
        "revision" : "3e464dad87dad2d29bb29a97836789bf0f8f67d2",
        "version" : "10.18.1"
      }
    },
    {
      "identity" : "boringssl-swiftpm",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/boringssl-SwiftPM.git",
      "state" : {
        "revision" : "dd3eda2b05a3f459fc3073695ad1b28659066eab",
        "version" : "0.9.1"
      }
    },
    {
      "identity" : "firebase-ios-sdk",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/firebase-ios-sdk",
      "state" : {
        "revision" : "f91c8167141d0279726c6f6d9d4a47c026785cbc",
        "version" : "10.21.0"
      }
    },
    {
      "identity" : "googleappmeasurement",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleAppMeasurement.git",
      "state" : {
        "revision" : "cb8617fab75d181270a1d8f763f26b15c73e2e1e",
        "version" : "10.21.0"
      }
    },
    {
      "identity" : "googledatatransport",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleDataTransport.git",
      "state" : {
        "revision" : "a732a4b47f59e4f725a2ea10f0c77e93a7131117",
        "version" : "9.3.0"
      }
    },
    {
      "identity" : "googleutilities",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleUtilities.git",
      "state" : {
        "revision" : "bc27fad73504f3d4af235de451f02ee22586ebd3",
        "version" : "7.12.1"
      }
    },
    {
      "identity" : "grpc-ios",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/grpc/grpc-ios.git",
      "state" : {
        "revision" : "da8a2405e9fdf3dfb127cefc5af56c29be8df2f2",
        "version" : "1.49.2"
      }
    },
    {
      "identity" : "gtm-session-fetcher",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/gtm-session-fetcher.git",
      "state" : {
        "revision" : "76135c9f4e1ac85459d5fec61b6f76ac47ab3a4c",
        "version" : "3.3.1"
      }
    },
    {
      "identity" : "interop-ios-for-google-sdks",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/interop-ios-for-google-sdks.git",
      "state" : {
        "revision" : "2d12673670417654f08f5f90fdd62926dc3a2648",
        "version" : "100.0.0"
      }
    },
    {
      "identity" : "leveldb",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/leveldb.git",
      "state" : {
        "revision" : "9d108e9112aa1d65ce508facf804674546116d9c",
        "version" : "1.22.3"
      }
    },
    {
      "identity" : "nanopb",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/nanopb.git",
      "state" : {
        "revision" : "819d0a2173aff699fb8c364b6fb906f7cdb1a692",
        "version" : "2.30909.0"
      }
    },
    {
      "identity" : "promises",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/promises.git",
      "state" : {
        "revision" : "e70e889c0196c76d22759eb50d6a0270ca9f1d9e",
        "version" : "2.3.1"
      }
    },
    {
      "identity" : "swift-protobuf",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/apple/swift-protobuf.git",
      "state" : {
        "revision" : "65e8f29b2d63c4e38e736b25c27b83e012159be8",
        "version" : "1.25.2"
      }
    },
    {
      "identity" : "swiftyjson",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/SwiftyJSON/SwiftyJSON",
      "state" : {
        "revision" : "b3dcd7dbd0d488e1a7077cb33b00f2083e382f07",
        "version" : "5.0.1"
      }
    }
  ],
  "version" : 2
}

If using CocoaPods, the project's Podfile.lock
No response

Build Log from Xcode Cloud(App Store Connect)
Resolve package dependencies

1m 24.2s
Run command: 'xcodebuild -resolvePackageDependencies -project /Volumes/workspace/repository/booksp.xcodeproj -scheme booksp -derivedDataPath /Volumes/workspace/DerivedData -hideShellScriptEnvironment'

Command line invocation:

    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -project /Volumes/workspace/repository/booksp.xcodeproj -scheme booksp -derivedDataPath /Volumes/workspace/DerivedData -hideShellScriptEnvironment

User defaults from command line:

    HideShellScriptEnvironment = YES

    IDEDerivedDataPathOverride = /Volumes/workspace/DerivedData

    IDEPackageSupportUseBuiltinSCM = YES

Resolve Package Graph

Fetching from https://github.com/grpc/grpc-ios.git

Fetching from https://github.com/google/GoogleUtilities.git

Fetching from https://github.com/google/GoogleDataTransport.git

...

Checking out 3.3.1 of package ‘gtm-session-fetcher’

Creating working copy of package ‘SwiftyJSON’

Checking out 5.0.1 of package ‘SwiftyJSON’

an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'abseil-cpp-binary' (https://github.com/google/abseil-cpp-binary.git)fatalError

Resolved source packages:

  RealityKitContent: (null)

2024-02-20 21:06:29.996 xcodebuild[3207:13197] Writing error result bundle to /var/folders/pc/xhyhfmrd1mq975kcng4w278r0000gn/T/ResultBundle_2024-20-02_21-06-0029.xcresult

xcodebuild: error: Could not resolve package dependencies:

  an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'abseil-cpp-binary' (https://github.com/google/abseil-cpp-binary.git)

  fatalError

Error
Command exited with non-zero exit-code: 74

Error
an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'abseil-cpp-binary' (https://github.com/google/abseil-cpp-binary.git)fatalError

Error
Make sure that Package.resolved is up to date on the 'main' branch, and that this branch has been pushed to your remote repository.

...

Check project configuration

11.9s
Error
Failed to catalog app correctly

Error
Plan schemes for project: '/Volumes/workspace/repository/booksp.xcodeproj'

11.8s
Run command: 'xcodebuild -describeSchemes -json -project /Volumes/workspace/repository/booksp.xcodeproj'

2024-02-20 21:06:44.258 xcodebuild[4127:16706] Writing error result bundle to /var/folders/pc/xhyhfmrd1mq975kcng4w278r0000gn/T/ResultBundle_2024-20-02_21-06-0044.xcresult

xcodebuild: error: Could not resolve package dependencies:

  an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'abseil-cpp-binary' (https://github.com/google/abseil-cpp-binary.git)

  fatalError

Error
Command exited with non-zero exit-code: 74

I tried rm -rf ~/.swiftpm/cache and following steps. However errors did not get resolved.
Reset Package Caches in Xcode: Go to File > Swift Packages > Reset Package Caches in Xcode to ensure that all package caches are cleared within Xcode as well.

Update Packages: Optionally, you can go to File > Swift Packages > Update to Latest Package Versions to make sure you have the latest versions of your dependencies.

Clean Build Folder: Go to Product > Clean Build Folder to clean any old build artifacts that might still be lingering.

It looks like the problem is related to /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved. Does removing it help?
Another clue is the message about adding abseil-cpp-binary which should not be added when building in source mode.

There might be a lingering reference in your Xcode project to it? A recursive grep might find it somewhere

@paulb777
~ ❯ grep -R "abseil-cpp-binary" booksp
~ ❯ grep -R "grpc-binary" booksp
~ ❯

You mean this, right? Any other place possible?
*booksp is my app name.
@ncooke3 If you know any.

It is so weird.
I have tried deleting booksp-* from DerivedData.
Moreover, there is no such file and folder workspace under /Volumes.
~ ❯ ls -a /Volumes                                                            ~
.		..		Macintosh HD

But the build keeps failing.
an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'grpc-binary' (https://github.com/google/grpc-binary.git)fatalError

Configuration Issues
Error
Could not resolve package dependencies: an out-of-date resolved file was detected at /Volumes/workspace/repository/booksp.xcodeproj/project.xcworkspace/xcshareddata/swiftpm/Package.resolved, which is not allowed when automatic dependency resolution is disabled; please make sure to update the file to reflect the changes in dependencies. Running resolver because the following dependencies were added: 'abseil-cpp-binary' (https://github.com/google/abseil-cpp-binary.git) fatalError

Hmm...

Possibly related to this issue, since both are on Xcode Cloud: https://github.com/apple/swift-package-manager/issues/6914
Can you try the workaround script in the linked issue to see if it resolves your build error?

Thank you. I have bypassed this issue by directly archive and distribute from Xcode, instead of going through Xcode Cloud.
I am not if https://github.com/apple/swift-package-manager/issues/6914 would fix it or not. On the next time I need to leverage Xcode Cloud, I would give it a try and update here.


Update Dinos “maiasaura”

Automatically generated by Netlify CMS

👷 Deploy Preview for quizzical-galileo-bf682e processing.

Name
Link

🔨 Latest commit
2ddb30e98ee3d9b6dc43e019fe57284597073464

🔍 Latest deploy log
https://app.netlify.com/sites/quizzical-galileo-bf682e/deploys/64f1d8f429d2430008f846d1


Coverage decreased (-15.7%) to 52.003% when pulling 19b132ad8d9356b49c43ad8966904170f5461f68 on feature/getEntryCollectionOrganization into 2b1de2786b4006799b39ff1b4db68e8e1ae67268 on develop.

Sample response:

[
  {
    "collection": {
      "dbCreateDate":<PHONE_NUMBER>994,
      "dbUpdateDate":<PHONE_NUMBER>004,
      "description": "asdf",
      "entries": null,
      "id": 1,
      "name": "asdf"
    },
    "organization": {
      "dbCreateDate":<PHONE_NUMBER>797,
      "dbUpdateDate":<PHONE_NUMBER>797,
      "description": null,
      "email": null,
      "id": 1,
      "link": null,
      "location": null,
      "name": "Potato",
      "status": "APPROVED",
      "topic": "asdf",
      "users": null
    }
  }
]


Add Crossplane Labs (Nested Compositions, GitOps, OPA/Gatekeeper)

What would you like to be added?
Enhance the Crossplane lab with additional sections

Nested Compositions (Using the composition from previous section)
Deploy a Claim using GitOps using the Nested Composition
Add a section on Policy Engines show how to work with Crossplane resources using OPA and Gatekeeper

Why is this needed?
Customer asked for a GitOps and Crossplane workshop that included how to work with nested composition, deploy with argocd, and how to enforce policies on crossplane resources

Going to close this for now as stale


[NEW ALGORITHM] Recursive Inorder Traversal

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
Recursive Inorder Traversal
About:
Inorder Traversal is a fundamental tree traversal technique used to visit all nodes of a binary tree in a specific order. In Inorder Traversal, the nodes are visited in the following sequence:
Left Subtree
Root Node
Right Subtree
Inorder traversal is particularly useful in scenarios where you need to process nodes in a sorted order, such as in binary search tree operations, expression tree evaluations, and generating sorted outputs of tree data.
Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[X] Contributor in GSSoC-ext
[X] Want to work on it

please assign this to me!


Bug: App not creating, Generator hangs without logs

The current generator is not working here with FOSSASIA Zip https://opev-webgen-dev.herokuapp.com/

@aayusharora Works fine for me. Is your sample updated ?


Work in progress: JUnit 5 migration

This is not done yet, it's currently intended as a proof of concept for migrating tests to JUnit 5

Hi @DamnedElric
What is the status?

Hi @garydgregory ,
I'll quote what I said on the mailing list, but the TL;DR; is that I'm awaiting feedback, and that I'll try to make some more progress.

Following Rob's suggestion, I migrated FTPSClientTest from @Parameterized to @Nested
The result so far can be found here: https://github.com/apache/commons-net/pull/227/commits/b14ee39cca486bda106758a48d31c91ad52d0d83
Basically the test methods were moved from FTPSClientTest.java [1] to AbstractFtpsTest.java [2]. The two @Parameterized values are then injected using @Nested.
The behaviour in maven is exactly the same as before. The behaviour in Eclipse bugs me a little, instead of asking both nested tests by default, it asks which one should be executed. But that seems to be the case with @Nested tests in general.
[1] https://github.com/apache/commons-net/blob/b14ee39cca486bda106758a48d31c91ad52d0d83/src/test/java/org/apache/commons/net/ftp/FTPSClientTest.java
[2] https://github.com/apache/commons-net/blob/b14ee39cca486bda106758a48d31c91ad52d0d83/src/test/java/org/apache/commons/net/ftp/AbstractFtpsTest.java
Any feedback is welcome. I personally feel like this test case is a bit too complex to be easily grokked, and perhaps it can be improved a bit more after the JUnit migration.

Yeah, I don't use the Nested feature. Eclipse behavior is important to me, I want that to work as well as it can...


add text shadow for user

sm

or md

this is fr medium larrge

this is for small shadow

for example without shadow looks like

or


add ssl switch

Codecov Report

Merging #250 into dev will decrease coverage by 0.10%.
The diff coverage is 0.00%.


RequestQueue.addRequest is an error inside the PlaywrightCrawler/handlePageFunction

Describe the bug
RequestQueue.addRequest is an error inside the PlaywrightCrawler/handlePageFunction.
Processing https://xxxxx ...
INFO  PlaywrightCrawler: All the requests from request list and/or request queue have been processed, the crawler will shut down.
node:internal/process/promises:246
  triggerUncaughtException(err, true /* fromPromise */);
  ^

route.continue: Target page, context or browser has been closed
    at RouteHandler.interceptRequestHandler [as handler] (/app/node_modules/apify/build/playwright_utils.js:59:38)
    at RouteHandler.handle (/app/node_modules/playwright/lib/client/network.js:620:10)
    at Page._onRoute (/app/node_modules/playwright/lib/client/page.js:221:22)
    at Proxy.<anonymous> (/app/node_modules/playwright/lib/client/page.js:179:16)
    at Proxy.emit (node:events:394:28)
    at Proxy.emit (node:domain:475:12)
    at Connection.dispatch (/app/node_modules/playwright/lib/client/connection.js:199:21)
    at Immediate._onImmediate (/app/node_modules/playwright/lib/inprocess.js:45:83)
    at processImmediate (node:internal/timers:464:21) {
  name: 'Error'
}

To Reproduce
handlePageFunction: async ({ request, page }) => {
    logger.info(`Processing ${request.url} ...`);
    const body = await page.content();
    // parse
    await requestQueue.addRequest(makeRequest(parse.url), { forefront: true });
    //await Apify.utils.sleep(1500); // Fix code
},

Expected behavior
It seems that crawler is terminating without waiting for handlePageFunction to finish.
If you add the following code to the end of handlePageFunction, the error will no longer occur.
await Apify.utils.sleep(1500);
System information:

OS: [e.g. Linux Ubuntu]
Node.js version [e.g. 16.9.1]
Apify SDK version [e.g. 2.0.7]

Additional context
This problem occurs even with a small number of requests. (1request and 1addRequest.)
Is there a problem with using RequestQueue.addRequest()?
In 0.x versions, there was a problem adding a large number of URLs to RequestQueue.
(Managing request queues:  File / Sqlite)
https://github.com/apify/apify-js/issues/505
I'd like to process a large number(50000) of requests dynamically,
Should I avoid RequestQueue in the current 2.0 version as well?

this is not coming from requestQueue.addRequest, it's coming from the gotoExtended function that is not try/catch'ing the interception code inside a synchronous code, but calling an async method without attaching a catch while also not awaiting it
https://github.com/apify/apify-js/blob/71150be4706187ef213b1379c1728f152d459ce8/src/playwright_utils.js#L59-L73

I'm relieved to hear that requestQueue.addRequest is not the cause.
I expect playwright.gotoExtended function to be scalable so that we can implement the following features by ourselves.
page.route(own interceptRequestHandler), blockRequests、blockResources
Thank you always.

Please retest this with<EMAIL_ADDRESS>

I am glad to inform you that the problem is now solved.
Thank you!


Can't resolve @babel/assertThisInitialized

Do you want to request a feature or report a bug?
Bug
What's the current behavior?
RBC can't resolve @babel/assertThisInitialized. No idea why this is happening, although I think it's due to a conflict with one of my other dependancies.
A similar issue (#971) appears to have a similar problem and doesn't offer a solution. Other people have experienced this with other libraries (Material UI and redux) and solved it with npm install --save-exact<EMAIL_ADDRESS>deleting & reinstalling node modules, as well as changing the version of the affected library. I've tried these methods and none have worked.
Any idea how to fix this, or any other info I could provide to help debug?
Your help is very much appreciated.
The exact error message:
./node_modules/react-big-calendar/dist/react-big-calendar.esm.js
Module not found: Can't resolve '@babel/runtime/helpers/esm/assertThisInitialized' in '/EnsoConnect/Enso_React/material/node_modules/react-big-calendar/dist'
My package.json
{
"name": "material",
"private": true,
"version": "4.0.0",
"main": "",
"homepage": "",
"scripts": {
"start": "react-app-rewired start",
"build": "react-app-rewired build",
"test": "react-app-rewired test --env=jsdom",
"eject": "react-scripts eject",
"prettier": "prettier --write ./src///**/*"
},
"dependencies": {
"@babel/runtime": "7.0.0-beta.55",
"@material-ui/core": "^1.5.0",
"@material-ui/icons": "^2.0.2",
"@material-ui/lab": "^1.0.0-alpha.10",
"aws-amplify": "^1.1.29",
"axios": "^0.18.0",
"classnames": "^2.2.6",
"core-js": "^2.5.7",
"date-fns": "^2.0.0-alpha.31",
"downshift": "^2.1.1",
"echarts": "^4.1.0",
"echarts-for-react": "^2.0.14",
"element-resize-event": "^2.0.9",
"font-awesome": "~4.7.0",
"history": "^4.6.1",
"jquery": "^3.3.1",
"jquery-slimscroll": "~1.3.8",
"material-ui-pickers": "1.0.0-rc.11",
"moment": "^2.24.0",
"prop-types": "^15.6.2",
"rc-queue-anim": "^1.6.5",
"react": "^16.8.6",
"react-big-calendar": "^0.21.0",
"react-chat-elements": "^10.5.0",
"react-dom": "^16.8.6",
"react-hot-loader": "^4.3.4",
"react-loadable": "^5.5.0",
"react-redux": "^5.0.7",
"react-render-html": "^0.6.0",
"react-router": "^4.3.1",
"react-routaer-dom": "^4.3.1",
"react-router-redux": "5.0.0-alpha.6",
"react-scripts": "2.0.0-next.3e165448",
"react-spinners-kit": "^1.9.0",
"react-timer-mixin": "^0.13.4",
"react-verification-code-input": "^1.2.0",
"redux-immutable-state-invariant": "^2.1.0",
"redux-thunk": "^2.3.0",
"socket.io": "^2.2.0",
"styled-components": "^4.2.1"
},
"browserslist": {
"development": [
"last 2 chrome versions",
"last 2 firefox versions",
"last 2 edge versions"
],
"production": [
">0.25%",
"not op_mini all",
"ie 11"
]
},
"devDependencies": {
"bootstrap": "^4.1.3",
"node-sass": "^4.9.3",
"prettier": "^1.14.2",
"react-app-rewire-provide-plugin": "^1.0.0",
"react-app-rewired": "^1.5.2",
"redux": "^4.0.1",
}
}

You have quite old setup. From what I remember react-scripts somehow enforced specific babel runtime version. I think upgrade should fix the problem. If it still will not work You will have to upgrade material-ui and babel runtime too.
Also which package manager do you use?


iOS 9 Black Screen Issue

While Appearing Status bar the screen gets black on iOS 9

Hello, please try this change, it helps in my case:
nihilenz@565488e

:+1:
Thanks it worked!

thanks

This helped but didn't completely fix my issue. Now the status bar will be shown correctly on iOS 6, 7, and 8, but on iOS 9 it is only shown on the iPad - it doesn't show on the iPod.

Thanks it helped me!!

:+1: cool! how did you managed to know that using -init: instead of -initWithFrame: will fix the black screen problem??

When we display message on status bar using MTStatusbaroverlay class then message doesn't display properly in portrait & landscape mode on iOS 9 devices. Its working fine on iOS 8 or lower devices.

Any update regarding above issue?


Conversion should recover spare allocated source blocks to a new file

On at least one volume I've encountered, there are blocks set as allocated in the VBM that are not actually allocated to any extent in the catalog or the extents overflow tree. impluse already has a check that reports any blocks that are marked as allocated but don't visited by file copies.
There's a possibility that there is important data in those blocks—perhaps a file that was deleted from the catalog without freeing the blocks, or was incorrectly not added to the catalog or overwritten in the catalog. (The volume in question did have other problems in its catalog; meanwhile, I don't have any specific reason to suspect the VBM of being wrong.)
It might make sense to make a new file in the converted volume—with a 32-character-or-longer name, so it's clearly not from the HFS volume—that adopts the orphaned blocks in its data fork, to enable recovery attempts.

Note that recovered data might be a data fork or a resource fork. The copied blocks should be assigned to both forks; if the data is a resource map, then it will at least be viewable in ResEdit and possibly be usable if the file's correct type can be guessed.
(Of course, it might also be a data fork and a resource fork, but we can't help that since we can't tell where anything was supposed to begin or end among the recovered blocks.)

I have a working implementation of this, but it's too sensitive and not specific enough: It also creates the recovery file on volumes that have no orphaned blocks, because the creation of the recovery file has to happen before the catalog is finalized (and its space allocated), but no real files have been copied (and their blocks visited) yet, so the orphan check at that time thinks almost everything is orphaned.
The existing “how many blocks haven't been visited yet?” check (which was originally a debugging method) won't work at that point in the process; I'll need to implement a new, separate traversal of the source catalog's leaf row, marking off blocks in a separate copy of the VBM.

One possible refinement of this might be to create a recovery file for every contiguous extent of orphaned blocks. I'm not sure this is worth it; contiguousness or lack thereof isn't a strong signal of belonging in separate files.

I think the most solid argument in favor of it is that separate extents can be reassembled in any order, but once we fuse them together, they're that much harder to pull apart.
That's already a problem for orphaned data from different files/forks in consecutive orphaned blocks. We don't need to make that worse.


Feature Request: Transaction configuration on a per migration basis

I'm submitting a...

[ ] Bug report
[x] Feature request
[ ] Question

Current behavior
There is no way to turn off transactions for individual migrations.
Expected behavior
Certain migrations need to be run outside of a transaction.  For example, in PostgreSQL, ALTER TYPE type_name ADD new_value cannot be run in a transaction.  The rest of the migrations, however should be run in a transaction.  There is currently no way to configure individual migrations to not use a transaction block.  It would be extremely helpful to allow this to be part of the configuration for a single migration.

Here's the hack I use, as a work around:
await db.endMigration();
await db.runSql(sqlScript);

Agreed, it would be better to have proper support for this.

this would be easy to add, if someone feels to push out a pr, it would be a target to be included in the setup routine of a migration.

Here's the hack I use, as a work around:
await db.endMigration();
await db.runSql(sqlScript);

Agreed, it would be better to have proper support for this.

Thank you so much! This is exactly what I've been looking.

Is anyone working on this yet? I’d like to pick this up

Hey is anyone working on this ? i would like to work on this


Unable to open PDF files in VS code

VS Code Version: 1.56.1
OS Version: Win10 x64bit

Steps to Reproduce:

Does this issue occur when all extensions are disabled?: Yes/No

To view PDF files you have to install the PDF extension https://marketplace.visualstudio.com/items?itemName=tomoki1207.pdf


The default version of the add-on is retrieved even if an explicit version is specified

Description
The EKS module uses aws_eks_addon_version data source to retrieve default/latest version of all add-ons, even the ones where the versions are explicitly specified through the addon_version map entry.
This has become an issue with the EFS CSI add-on recently, because the default version for it does not seem to exist:
$ aws eks describe-addon-versions --kubernetes-version 1.27 --addon-name aws-efs-csi-driver --query addons[0].addonVersions[*].compatibilities[0].defaultVersion
[
    false,
    false,
    false,
    false,
    false
]

As a result, even if I pass a version to the module explicitly, I have an following error on terraform plan.
Versions

Module version 19.20.0:

Terraform version:

Terraform v1.5.7
on linux_amd64

Provider version(s):

+ provider registry.terraform.io/hashicorp/aws v5.29.0

Reproduction Code [Required]
module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "19.20.0"

  create = true

  cluster_name    = "test"
  cluster_version = "1.27"

  cluster_addons = {
    aws-efs-csi-driver = {
      addon_version            = "v1.7.1-eksbuild.1"
      most_recent              = false
    }
  }
}

Steps to reproduce the behavior:
terraform plan

Expected behavior
Data source is not instantiated for any add-ons with an explicit version.
No error on the plan.
Actual behavior
Error on the plan.
Terminal Output Screenshot(s)
Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: reading EKS Add-On version info (aws-efs-csi-driver, 1.27): empty result
│
│   with module.eks.data.aws_eks_addon_version.this["aws-efs-csi-driver"],
│   on .terraform/modules/eks/main.tf line 439, in data "aws_eks_addon_version" "this":
│  439: data "aws_eks_addon_version" "this" {
│
╵

Additional context
N/A

FYI I have a patch that fixes this problem and I am working on a PR.

this was a hiccup in the AWS API, we  no longer need any changes here - but thank you!


New team - devnull

Add new team gentx - devnull

Can you please close this PR and recreate a new one? We have added a CI test to validate the gentx and it works on new PRs only.

Yes of course


go/parser: fails when a valid function declaration follows an broken one

Repro case:
package main

type e struct {
	error
}

func (*e) random() {}

func main() {
	var diags []error
	for _, err := range diags {
		handled := handle(err)
                handled.
	}
}

func handle(err error) *e {
	return &e{err}
}

The selector with no "Sel" field breaks parsing in the main function, causing the code below it to fail parsing. The handle function never gets registered as a function declaration. Moving the handle function above the main function causes this code to type-check as expected. This poses a problem for editor-integrated tools that need to work on broken code.

/cc @ianthehat


Check last official Falcon version && Separately implementation 😏

Following issue #1
Falcon is a promising algorithm for post-quantum cryptography, has become a finalist in the NIST competition and is approved for inclusion in the standardization. 😎
Your implementation is a perfect example of what it should look like. 👍

Can you check the official latest version of Falcon? If so, how long can we expect you to release an updated version of your implementation? ✨

Since you have implemented WASM or JS, could you also implement them separately so that you can simply connect the .js file and use it? 📑

With best regards.

Regarding question 1:
It is in my future plans to upgrade this project to the latest version of Falcon as well as improve its API. But no from my side ETA. It is probably not much work, but nevertheless I have to find the time to do it.
With that been said, all the code is here and any person with a bit of linux experience and understanding could update the code and compile it from source.
Regarding question 2:
The best approach is to always load the JavaScript version and before using it, check if the wasm is also available. Thus, to support your needs, it is better to add an option just to skip this step and just use the JavaScript version.