[bug] MultiDrag in Shadow DOM, Ctrl key doesn't work

All items get deselected on 'drop'
The issue I think comes from the fact that the keydown listeners event targets cannot be detected as being inside the sortable element.
Particularly this line:
if (evt && closest(evt.target, this.options.draggable, this.sortable.el, false)) return; // Only deselect if left click

evt.target will always equal the document if the sortable element is in a shadow dom, so it will never return on this line.

change evt.target to evt.composedPath()[0] will work fine


fix: added '_redirect' file

What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description
This PR resolves the "Page not found problem" while accessing any route with a direct link.
Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@shamimbinnur checking in on this to see if you can swap this to the toml
[[redirects]]
  from = "/*"
  to = "/index.html "
  status = 200

@shamimbinnur checking in on this to see if you can swap this to the toml
[[redirects]]
  from = "/*"
  to = "/index.html "
  status = 200

@bdougie added this in toml file


[Question] about clearly params

I've followed your command to run training model
python ./deepy.py train.py -d configs 125M.yml local_setup.yml

However, I want to pass clearly params with command. I've tried:
$ python deepy.py --user_script train.py --conf_file configs/125M.yml configs/local_setup.yml

I get error:
/gpt-neox$ python deepy.py --user_script train.py --conf_file configs/125M.yml configs/local_setup.yml
usage: deepy.py [-h] [--conf_dir CONF_DIR] [--wandb_group WANDB_GROUP] [--wandb_team WANDB_TEAM] [--eval_tasks EVAL_TASKS [EVAL_TASKS ...]] [--iteration ITERATION] [--eval_results_prefix EVAL_RESULTS_PREFIX]
                [-H HOSTFILE] [-i SAMPLE_INPUT_FILE] [-o SAMPLE_OUTPUT_FILE] [--autotuning {tune,run}]
                user_script conf_file [conf_file ...]
deepy.py: error: unrecognized arguments: --user_script --conf_file

I'm very happy if you can give me clearly command.
Thank you very much!

What are “clearly params”?

What are “clearly params”?

Hi @StellaAthena,
The fact, I want to finetune your model, but with my data, I get error --> So I want to debug. If  I want to debug with VSCode, I must give debug clearly arguments for run deep.py file.
For example:
"args": ["--user_script","train.py "]

Ref link stackoverflow

But I can not find detail about this. I run deep.py --help --> It show helping arguments --> I add arguments --> error above I describe.

Based on the stackoverflow post you link, can you just do
"args": ["train.py", "--conf_dir", "configs", "125M.yml", "local_setup.yml"]

to pass the args through the VSCode debugger in the format we expect?

Based on the stackoverflow post you link, can you just do
"args": ["train.py", "--conf_dir", "configs", "125M.yml", "local_setup.yml"]

to pass the args through the VSCode debugger in the format we expect?

Thank you very much, It works


Create without column 'created_at' error

SQLITE_ERROR: table metrics has no column named created_at'

Read this http://dev.adonisjs.com/docs/3.0/lucid#toc-timestamps

Without field never work with a model?

I would suggest to read the documentation clearly and also explain what exactly you are trying to do.

Closing as there is not enough context on the issue. I would recommend checking the docs and creating a issue with enough context and some code samples.


Accommodate data center info metadata for types other than "Amazon"

Fargo allows one to specify and retrieve Amazon-specific data center metadata, but does not accommodate any such metadata for other types of data centers. The Eureka XML schema for instance registration is loose here; it mentions that the Amazon-specific schema for the dataCenterInfo element's metadata element applies only when the name element is "Amazon".

metadata is only required if name is Amazon

That says that it's only required; what it really should say is that anything is tolerated, at the discretion of the data center-specific Java type that parses this metadata in the Eureka server. What actually happens is that the Eureka server parses the metadata element into a Map<String, String> and allows types implementing com.netflix.appinfo.DataCenterInfo to interpret that mapping as they see fit. It just so happens that the Eureka authors were only concerned with one concrete kind of data center. My company has implemented several more data center types in our Eureka fork.
I propose adding a field to fargo.DataCenterInfo—called "AlternateMetadata" of type map[string]string—that allows callers to send and receive this metadata for data center types other than "Amazon". Doing so is necessary for clients to decide on an instance ID that the server will accept. Without this concession, the server always uses the submitted host name. (See #39 for related discussion.)
I will submit a PR that takes care of the marshaling, but first I thought that we might like to discuss the need for and merits of this approach here first.

I will submit a PR that takes care of the marshaling

To that end, see #44.


Cannot connect to Sonar's DB using oracle thin client - doesn't pass u/p

org.apache.commons.dbcp.SQLNestedException: Cannot create PoolableConnectionFactory (ORA-01005: null password given; logon denied

Sorry, now it works (it just didn't the first 5 times I tried it)


fix(opts command) run server on windows 10,  cmd "opts utf8 on" doesn…

…'t  work
When run on windows10, cmd " opts utf8 on" "site help" parse error. because in extension cmd is "UTF8" is UPPER.
[15:39:15 DBG] USER tester
[15:39:15 DBG] 331 User tester logged in, needs password
[15:39:15 INF] Connection closed
[15:39:15 DBG] PASS **************** (password omitted)
[15:39:15 DBG] The root directory for tester is /root\tester
[15:39:15 DBG] 230 Password ok, FTP server ready
[15:39:15 DBG] opts utf8 on
[15:39:51 DBG] 500 Syntax error, command unrecognized.
OptsCommandHandler.Process
public override async Task<IFtpResponse?> Process(FtpCommand command, CancellationToken cancellationToken)
{
var argument = FtpCommand.Parse(command.Argument);
if (!Extensions.TryGetValue(argument.Name, out var extension))  <=======  need to UPPER
{
return new FtpResponse(500, T("Syntax error, command unrecognized."));
}
        return await extension.Process(argument, cancellationToken).ConfigureAwait(false);
    }

I believe that Extensions should use OrdinalIgnoreCase instead, but I'll look into it.


Revert "Fix Issue 9489 - writeln of struct with disabled copy ctor"

Reverts dlang/phobos#8055

@Geod24 @thewilsonator mind if I also commit a unittest for 21920?

Of course not :)

Done!

Doesn't this also fix 21920?

@RazvanN7 added "fix" to the commit message.

Shouldn't this target stable?

No, the offending commit is not in stable.

No, the offending commit is not in stable.

Wow, it's like you read my mind. I did think of suggesting to target stable, but then realized that the offending commit got merged last week. 10 seconds later I see "No, the offending commit is not in stable"

The issue says REG master not REG stable. ;-)

Of course, sorry for the noise :)

Who broke the test-suite?
generated/linux/release/64/benchmark.o:benchmark/runbench.d:function _D8runbench8runTestsFSQu6ConfigZv:
error: undefined reference to '_D3std4path12absolutePathFNaNfAyaLQeZQh'
--
generated/linux/release/64/benchmark.o:benchmark/runbench.d:function _D8runbench8runTestsFSQu6ConfigZv:
error: undefined reference to  '_D3std4path12absolutePathFNaNfAyaLQeZQh'


Carrier flagship Q spell 'Bombing Run' costs mana but the ship doesn't have mana

Fixed, spell no longer costs Mana


Automatic Importing with inotify

🎉 Feature Request! 🎉
More of a personal requirement, but I could see it useful for others too:
I'm running VHA in a docker container, and it would be awesome if it used inotify to watch all the video folders, and automatically imported new videos after an IN_CLOSE_WRITE event! 💡
This would prevent the need for me to rescan the entire directory of videos when adding a single video, and also prevent the need to manually trigger it.
This would be under a feature toggle of course! 👍
I'll look into this! 💯

Thanks Cal!
Seems like a simple "watch folder" button would do the trick on the UI front.
Main question to think about is if it should be a per-hub setting or a app-wide 🤔
I'm unsure how to answer this question -- perhaps you have an intuition about which is better for users 🤷♂

Also it seems like inotify is a Linux-specific thing.
There's surely a way to do it on Windows and Mac too (other apps have features like that) -- I hope it doesn't require re-scanning the whole directory (imagine a hub pointing at a full hard drive) 🤔
Currently initial part of the scan locks up the UI with a green progress bar ...
The feature you describe sounds like it's related for your long-ago discussion about a Daemon mode ...
Perhaps if all a background process does is create screenshots with correct hash file names, the app re-scan would be super quick (only requiring the meta-data extraction) 🤔
All thoughts welcome 👍

This is available on other systems, node.js even has a built in function for this:
https://nodejs.org/docs/latest/api/fs.html#fs_fs_watch_filename_options_listener
But I don't think this will be suitable for my purposes, but I can test it now - I need to know when a file is closed for writing, to avoid importing a copied file before it's finished copying! 💡
This is related to #161 - As I have it in docker, this might be a simpler solution for now, and handy for many people! 😄
Getting CLOSE_WRITE will be my priority for now, but so I'll start with Linux, and port it to the other systems after each with their respective file-watching-ways. 💯

Some thoughts:
As expected, fs.watch() doesn't tell you anything about the event, just that something happened to the file. Also, adding inotify as a dependency will through an error on other platforms. 😢
Two options:

Implement each platform independently, using they're respective native way.

Use fs.watch() combined with something else. For things like rsync (my usecase), it would still work as rsync writes to a temp file, and then renames it to the correct name when finished. Using system copy functions doesn't however (how I assume a lot of people would do it). For this, we could either wait X seconds of no updates for a file and assume it's completed, or use something like opened (https://github.com/ronomon/opened) to see if the file is still open by a process (this could mess up with video players, etc.)

Thoughts? 💭

More developments:
Currently looking at https://www.npmjs.com/package/chokidar and it looks pretty sweet! 🎉
Multi-platform, and has some nifty features that could even help with #369 💡
Along with allowing file change events, it also stats the files to work out better events, which can be returned for your own use (scanning the hdd), and it also can output all files as it initially scans the hard drive - oh, and it's also async! 😄
We could rethink how the importing works, and scan and import files async, and then react and import to file changes too - what do you think? 💭

My thought would be:

Create new hub.

Kick off chokidar, which scans the video folder, outputting files async, along with adding file watchers.

As files come in, begin importing them in the background and update the final array (seems like the app is quite happy with updating the final array on the fly).

Once scan is complete, new files get treated just the same way, import and update the array.

Any files already imported are just skipped.

On a second open, if a toggle is selected, it will do 2-5 again, skipping any known files and importing any new ones in the meantime!
This would have a much better UX experience in that the app wouldn't block on initial or subsequent imports! 🎉

It even has awaitWriteFinish! 🎉 🎉

I have a plan of how this can work, and using what I've learned from coding image-viewer! 😄 I've started working on it, and I'll post a review as soon as I have something working! 📝

Current update:

Importing new videos on open working, along with new videos appearing while the app is running.

Manual thumbnail generation working.

Moved quite a few more methods to be async with Promises (much improving the responsiveness of the app).

My current plan is, if this feature is enabled, new videos will be imported and thumbs generated automatically in the background. Removed files will be automatically removed too.
I think I will also move the current system over too, but in such a way that it will only scan when requested, and won't continue looking for updates after a full scan. This should allow for simpler code, better app responsiveness as it will use the new async code, and also, the app won't need to be locked anymore while scanning! 🎉
Thoughts @whyboris? 💭

Automatic thumbnail extraction working!

Parallel fs requests! (Checking 8 files at a time)

Resume scanning/extraction on reopen!

Using new scanning method for new hubs working!

🚀

Exciting! I think this is your code so far:
https://github.com/whyboris/Video-Hub-App/compare/master...cal2195:file-watch
I'm unsure if running video extraction in parallel is a good idea. I suspect most people are still using mechanical hard drives and random access is slow (making the needle jump between 8 files isn't great I think), and the processor might not be able to handle 8 videos in parallel (thus having to switch tasks, incurring further overhead of task switching). I am pretty sure sequential extraction isn't going to benefit from going parallel (though it would be great if I am wrong).
What do you think is the bottleneck in extracting screenshots? I'm guessing decoding a 4K video makes for a hard-enough job for the HD and the CPU (GPU?) at the same time. I don't have a guess which is slower. But I'm unsure 🤷♂
I ran the app extraction with my Task Manager showing -- the RAM jumped up to ~700MB ... I'm worried if we do things in parallel the RAM might run out and the OS will start dumping things to HD for temporary memory, compounding the trouble 🤔
I don't have much experience with any of this -- so all this is from theoretical understanding of things and may be wrong.
I just realized you may be talking about fs requests not for extracting but only for initial info ... so that may be different, though I'm unsure 😅
All else sounds like exciting improvements! Thank you 🙇

You're correct at the end there - I'm only talking about metadata requests. 😄 I'm running multiple mechanical drives here, and most of the CPU time is taken with iowait, so multiple requests could make sense.
Luckily, it's a single parameter! 🎉  So we can test out which gives the most videos-per-second, and even make it user configurable!
Thumbnail extraction is still sequential, but could also be parallel in the same manner - just one param change! 👍
We could have a simple output when testing to see the exact videos/time extracted, or just go with what feels snappiest! 😄
Working on fixing up bugs now, and getting it all together! One of the best features - it's 100% backwards compatible with .vha2 files currently! 🎉

@cal2195 thank you so much for your #383 🙇 I believe this issue has been solved 🎉
Please let me know if that's not the case 😅


Send mail error

error: Job run MailMessageJob failed: mail from address must be same as authorization user
The configuration is as follows:
Email: 'smtps://xxxx%40qq.com:pwd@smtp.exmail.qq.com:465'

The same user name and password login third software can send mail

Sounds like you also need to change the SmtpFrom to match your user: https://github.com/exceptionless/Exceptionless/blob/master/src/Exceptionless.Core/Configuration/EmailOptions.cs#L53 Please let us know if you have any questions.


No cmdlet to enumerate roles set to an application

On the Azure Portal in AAD, there is an option in preview to set roles to a specific application within AAD, however there are no cmdlets within AzureAD PowerShell to enumerate this info.
https://i.imgur.com/oyV7Oky.png

Hi @hausec
Thank you for your issue submission.  I have created a work item to track this issue and will be sending it to engineering.  At this point, I am going to go ahead and close this issue.  I will post an update as soon as I have any additional information.
Thank you!
Bill


Until and while may cause an error in the unpiped stream.

Consider this more a use case than a problem (as it is outside of scramjet).
Let's consider code:
StringStream.from(request(someUrl))
    .lines()
    .parse(JSON.parse)
    .until(x => x.date < Date.now())

What we do is unpipe the response, but that is not closed by request so how do we handle this?
Mention: openaq-fetch#547

The current solution has been deployed to OpenAQ adapters.
  const requestObject = request.get(stationUrl);
  return DataStream	  return DataStream
    .from(() => request.get(stationUrl).pipe(JSONStream('*')))	    .pipeline(
      requestObject,
      JSONStream('*')
    )
    .catch(e => {
      requestObject.abort();
      e.stream.end();
      throw e;
    })

Should it and can it be any cleaner - the abort operation is specific to request module...


__ToString Error

After installing Claims and declare them I get the following error when doing a request:
{
"message": "Method CorBosman\Passport\AccessToken::__toString() must not throw an exception, caught ErrorException: Replicating claims as headers is deprecated and will removed from v4.0. Please manually set the header if you need it replicated.",
"exception": "Symfony\Component\ErrorHandler\Error\FatalError",
"file": "D:\webs\VOW\experimento\backend\vendor\league\oauth2-server\src\ResponseTypes\BearerTokenResponse.php",
"line": 0,
"trace": []
}

There appears to be some breaking issue with laravel/oauth2 and lcobucci/jwt.  Could you try forcing version 3.3.0 of lcobucci/jwt and see if that fixes that problem?

You mean even see this problem without my package btw, I see similar reports on Passport itself.

I see there is a new passport version that fixes the issue with lcobucci/jwt, i will update my package to use this new version. Might take me a day or so to fully understand the changes.

Ok, so the issue is that you probably installed passport version 10.1.0 or higher, which has new code that fixes problems that arose from a lcobucci/jwt change. So you can probably for now install 10.0.x of passport, or wait until I have updated a new version of my package that works with the new passport. Probably tomorrow.

Hi, I released a version 2.0.0, if you use Passport 10.1.x or higher you should try that and see if it works.

Sorry. Was busy some other projects. I'll install and let you know. THANKS!

Worked like a charm... All is up and running


add tests for RFB parser - v2

Previous PR: #185
Changes to previous PR:

Add tests for new keyword rfb.secresult.
Adjust expected JSON format.

Merged. Thanks!


Purpose of the new 2.0 branches?

Hello @altairwei and @wangwenx190 could you please tell me where I can find information on the different 2.0 branches that appeared in the past month? Is it a rewrite of the library? Is it Qt5 compatible?
Thanks in advance!

We consider that the 1.x version of the borderless window on Linux and MacOS is a rudimentary implementation (arguably not yet implemented on MacOS) and relies on two APIs from Qt 5.15. So we intend to re-implement borderless windows on Linux and MacOS using the system native APIs and remove the dependency on those two Qt 5.15 APIs.

Does it mean there's currently no reason to use 2.0 on Windows?
Thank you.

Is it a rewrite of the library?

For Linux and macOS, yes, the library is almost re-written. For Windows, no, no critical areas are touched, just minor refactoring to fit the new API design. For the current 1.x implementation, the Linux and macOS code are using QWindow's API which only available since Qt 5.15, and Qt's implementation on macOS is not completed due to the lacking of QWindow::startSystemResize(), the 2.0 code will use native code to do the move and resize stuff and thus the minimum required Qt version can be lowered from 5.15 to 5.6 and for macOS the missing support of window resizing will also be available. For Windows, the currrent 1.x implementation is stable enough, so we are not planning to make huge change to it.

Is it Qt5 compatible?

Of course. This library will always support Qt 5 & Qt 6.

the different 2.0 branches that appeared in the past month

You should consider @altairwei 's 2.0 branch is the next generation of this library. After some private discussions with @altairwei , I was convinced by him so I let him design the new API. The 2.0 branch created by me was then stopped developing and will be removed soon.

Does it mean there's currently no reason to use 2.0 on Windows?

For now the 2.0 branch is still work-in-progress and it's not stable enough. The code is not finished yet and it needs more testing. When we think the 2.0 code is finished and stablizied we'll merge it into the main branch and delete the old 1.x branch. But it will not happen soon. And for Windows, the code actually doesn't change much, it will be refactored to fit the new architecture.


Regions - Not able to reach  sidekick targets from LB with network policy set to "allow within linked services".

Rancher versions: Build from https://github.com/alena1108/cattle - "region" branch
network policy manager - leodotcloud/network-policy-manager:regions
Steps to reproduce the problem:
Network policy set to "allow within linked services" and "deny" set for all other rules.
Create a service - s1 with sidekick - sk1 having labels foo=bar
Create a LB service with "selector rule" set to "foo=bar" so that sidekicks get added as targets to LB.
LB is not functional , since sidekick containers are not able to reach from lb container.

@sangeethah @leodotcloud LB shouldn't accept sidekicks as targets. Although it is possible to achieve via labels/selectors, this is not the use case users would exercise.

I have updated the Regions wiki with notes.

Regions wiki documents this limitation.


Merge ttnn with tt_eager

Goal
Streamline further development of our OP library.
Background
Operations are split between tt_eager and ttnn. Many ops in ttnn call their tt_eager implementation. Some ops like unary and binary duplicate lots of code leading to 2 different pathways in C++ / Python. This not only confuses new contributors, but increases time required to make changes. For example, as we add support for queue_id and output_tensor - we have to add them to ops in both libs.
We want to merge the two, moving code from tt_eager to ttnn, consolidating OPs in one place.
Guiding principles

Keep everything related to a single op at a single place
Code organization reflects ownership
User documentation and code organization should be aligned

Milestones

[x] Phase 1 - Smoke out blockers and Align - June 12
[x] Phase 2 - Pave the way - June 12 - June 19
[ ] Phase 3 - Scale migration of ops - June 19 - July 17 (in progress now)
[ ] Phase 4 - Remove tt_lib - July
[ ] Phase 5 - Remove tt_eager - mid Aug

Example instead of 1000 words
See how files are consolidated in ttnn, instead of being split between tt_eager and ttnn. This is the core of the change this effort drives.
From 😫
tt_eager
└── tt_dnn
    └── op_library
        ├── ...
        └── eltwise_binary
            ├── kernels
            │   ├── compute
            │   │   └── eltwise_binary.cpp
            │   └── dataflow
            │       └── reader_binary_interleaved_start_id.cpp
            ├── multi_core
            │   └── eltwise_binary_op_multi_core.cpp
            ├── eltwise_binary_op.cpp
            └── eltwise_binary_op.hpp
ttnn
└── cpp
    ├── pybind11
    │   └── operations
    │       ├── ...
    │       └── binary.hpp
    └── ttnn
        ├── op_library
        │   └── ...
        │   └── binary
        │       ├── binary_op.hpp
        │       └── binary_op.cpp
        └── operations
            ├── ...
            └── binary.hpp

to 😎
ttnn
└── cpp
    └── ttnn
        └── operations
            └── ...
            └── eltwise
                └── binary
                    ├── device
                    │   ├── kernels
                    │   │   ├── compute
                    │   │   │   └── eltwise_binary.cpp
                    │   │   └── dataflow
                    │   │       └── reader_binary_interleaved_start_id.cpp
                    │   ├── binary_op.cpp
                    │   ├── binary_op.hpp
                    │   └── binary_program_factory.hpp
                    ├── binary.hpp
                    └── binary_pybind.hpp

All files related to an Operation are in its own folder. Binary op gets its own folder and owner.

binary.hpp - Op interface and registrations
binary_pybind.hpp - bindings
binary_program_factory.hpp - kernel setup
binary_op.hpp/.cpp - operation itself with validation/program selection/etc

Host and Device "programs" are split. Host program can become a "gold" for comparison in tests.
Scope (tbd)

[ ] #9609
[x] #9377
[ ] #9490
[ ] #9492
[ ] #9493
[ ] #9486
[ ] #9489
[ ] #9487
[ ] #9488
[ ] #9527
[ ] Move Binary Composite ops to ttnn
[ ] #9628
[ ] #9911
[ ] #9491
[ ] #9733
[ ] #9785
[ ] #9874
[ ] #9871
[ ] Move Moreh ops to ttnn
[ ] Merge tt_dnn into ttnn
[ ] Merge tt_lib
[ ] Merge tt_eager

might want to prioritize migration of these:

[ ] Move bcast to ttnn with output_tensor and queue_id
[ ] Move permute to ttnn with output_tensor and queue_id
[x] Move recip to ttnn with output_tensor and queue_id
[ ] Move unpad to ttnn with output_tensor and queue_id

ttnn/ttnn/api.rst

Key points

Keep everything related to a single op local

Talk about the desired structure is in progress

ttnn

operations

binary

binary

device_operation.hpp
interface.hpp (struct with execute on main/worker thread, register_operation)

polyvan

polyvan_op
interface.hpp

data_movement

pad
repeat_interleave

ttnn/ttnn/api.rst

Blocked by #8731

Considerations
During the discussion about the structure we considered:
1. A) Group bindings vs B) Group everything related to a given operation

During changes to operation interface it is convenient when its binding is nearby
Changes to interface are frequent at this point
We want owner to maintain op end to end and do not plan to have a separate owner just for bindings

2. A) Related operations split into own files vs B) Related operations in the same file

Split makes it easier to locate / navigate a specific operation
Split highlights dependencies
Split leads to more files and deeper structures :(
There are plenty of examples where split does not make sense and we need to adequately accommodate those

Question in terms of pipeline setup.
We've currently got tests invoked in run_tt_eager.py and I'm assuming we'll keep the test invocations in there but update the test file paths (as they are migrated) and finish the migration process by simply renaming run_tt_eager.py

As I am porting my first op, I realize that I take issue with the <op>_program_factory.hpp naming convention. We don't write a factory here. A factory has a very specific meaning, which is an object that creates other objects. Here we create a file that defines programs themselves. So it should be renamed to <op>_programs.hpp to reflect what is actually inside.


Implement the future type

https://github.com/bytecodealliance/wit-bindgen/pull/269 adds support for parsing the future type. There are many todo!s left for the implementation in the canonical ABI and bindings implementations.

https://github.com/bytecodealliance/wit-bindgen/issues/270 is an issue tracking the remainder of the implementation for futures.

One thing I want to note here is that future, stream, and other async things are not present in the component model spec at this time. To that end I don't believe that this issue is implementable today because it's not clear what it would mean to actually implement the future type given that there's no target to implement. I think that work needs to be done to design how future and stream types would work first before actually implementing them in wit-bindgen, although a local fork could of course be used to prototype various design decisions.

I'm going to close tis for similar reasons to https://github.com/bytecodealliance/wit-bindgen/issues/233 where work needs to happen upstream first rather than in this repository.


Request for IC2 Classic support by Speiger

We want modtweaker support ^^

So no or yes ? :C
Confused xD

Currently there are other plans for future Modtweaker support.
Some examples are:

Big Reactors
Growthcraft
Updating current support
and so on. The IC2 Classic support is kind of miscellaneous so I suggest you ask the mod dev to add support natively :)

No that is what we want to do, but he need some help, can you talk with Speiger ?

github username?

Speiger ^ ^

got a repo for IC2 classic?

https://github.com/TinyModularThings/IC2Classic Here ^ ^


Added mod alerted notice to auto-infractions

Closes #2247
Summary

Added notice that moderators have been alerted to all automated infractions.

Implementation
infraction/_scheduler.py
if reason:
-   end_msg = f" (reason: {textwrap.shorten(reason, width=1500, placeholder='...')})"
+   end_msg = (
+       f" (reason: {textwrap.shorten(reason, width=1500, placeholder='...')})"
+       " Moderators have been alerted for review"
+   )

Demo

Current latest style as of c9d5aac:


add new project generation capability

Signed-off-by: stevelr<EMAIL_ADDRESS>

I know about the integration_drain test failing - still working on it. In the meantime, I'll mark the PR as draft.

This PR adds three new top-level wash commands
wash new [actor|interface|provider - create a new project from a template
wash lint - run lint checks on a smithy model
wash validate - run validation checks on a smithy model
over time, we'll probably add more rules for both lint and validation.
There's one more command needed to be on-par with the weld binary - a way to trigger code/documentation generation for any codegen.toml file.  I'll do that as a separate PR.

PR ready for review @brooksmtownsend @autodidaddict

Thanks for the review! I addressed  your comments in the latest commits. There's a note addressing the question about 'favorites' above. I'll write a separate documentation file (in a separate PR)  to explain all the project-generation options.


chore(ci): upgrade github actions test matrix

Also includes the addition of workflow_dispatch to facilitate manual github builds.

@Naenyn it looks like there are some compile errors?

Closing this one in favor of https://github.com/uPortal-Project/portlet-utils/pull/66


Skip loading of head revision on write calls

These APIs do not use consistency blocks, so there is no need to load the head revision outside of their transactions

Rebased and updated


Azure Speech Services Tutorials update for MRTK v2.1.0

Docs Build status updates of commit a805e01:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mrlearning-speechSDK-ch4.md
:warning:Warning
View
Details

mixed-reality-docs/images/Lesson1Chapter2Step2b.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson1Chapter2Step3.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step2.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step3.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step4.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_Chapter3_step1im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step3im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step5im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_Chapter1_step1im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_Chapter3_step8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter1_notebim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter1_step4ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter3_step4-7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter3_step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter4_step3-5-noteim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_Chapter1_step2im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_noteim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step10im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step13im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step5im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step6im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step8.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter2_step7-8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter2_step8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11imd.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step12imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step12imc.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step13imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step3im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step3ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9imd.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step2im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step3aim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step3bim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step6im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/mrlearning-asa-ch1-3-step1.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step11.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step12.jpg
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.

mixed-reality-docs/mrlearning-speechSDK-ch4.md

Line 56: [Warning] Invalid file link: 'images/mrlearning-speech-ch4-1-step6.png'.

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

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

File
Status
Preview URL
Details

mixed-reality-docs/images/Lesson1Chapter2Step2b.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson1Chapter2Step3.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step2.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step3.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step4.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_Chapter3_step1im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step3im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step5im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_Chapter1_step1im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_Chapter3_step8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter1_notebim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter1_step4ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter3_step4-7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter3_step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter4_step3-5-noteim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_Chapter1_step2im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_noteim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step10im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step13im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step5im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step6im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step8.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter2_step7-8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter2_step8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11imd.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step12imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step12imc.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step13imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step3im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step3ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9imd.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step2im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step3aim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step3bim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step6im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/mrlearning-asa-ch1-3-step1.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step11.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step12.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step6.jpg
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 3ee0d57:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/images/Lesson1Chapter2Step2b.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson1Chapter2Step3.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step2.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step3.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson2_Chapter4_Step4.JPG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_Chapter3_step1im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step3im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson3_chapter3_step5im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_Chapter1_step1im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_Chapter3_step8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter1_notebim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter1_step4ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter3_step4-7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter3_step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson4_chapter4_step3-5-noteim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_Chapter1_step2im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_noteim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step10im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step13im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step5im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step6im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step8.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter1_step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter2_step7-8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/Lesson5_chapter2_step8im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step11imd.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step12imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step12imc.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step13imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step3im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step3ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step4im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step7im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9ima.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9imb.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter1step9imd.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step2im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step3aim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step3bim.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/module4chapter4step6im.PNG
:white_check_mark:Succeeded

mixed-reality-docs/images/mrlearning-asa-ch1-3-step1.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step11.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step12.jpg
:white_check_mark:Succeeded
View

mixed-reality-docs/images/mrlearning-asa-ch1-3-step6.jpg
:white_check_mark:Succeeded
View

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


Proposing readme updates

Hey @bennyhodl - trying to get this running locally and have started to document the issues I'm running into and steps to resolve them.
An alternative option is to commit your /testconfig/ files to master and this PR could be closed out. Can you share your oracledb.dockerfile?

Thanks for catching that I didn't have docs for the oracle. I use the oracle from rust-dlc https://github.com/p2pderivatives/rust-dlc/tree/master/sample#quick-run
I will spend the day writing documentation on running locally. Wish I had it prepared already, but glad I have people trying it out now! 😁

Is this file not sufficient for running locally? https://github.com/bennyhodl/dlcdevkit/blob/master/regtest/oracle/oracledb.dockerfile

What I ended up doing was:

Copying the contents of /regtest/ into /testconfig/
Modifying https://github.com/bennyhodl/dlcdevkit/blob/master/regtest/oracle/oracledb.dockerfile#L4-L5 to:

COPY ./certs/db/db.crt /certs/
COPY ./certs/db/db.key /certs/

Modifying https://github.com/bennyhodl/dlcdevkit/blob/master/docker-compose.yaml#L113-L114 to:

      context: ./testconfig/oracle
      dockerfile: oracledb.dockerfile

I've now got 4 of the 5 containers running but ernest-bitcoin is exiting within 1-2 seconds of initialization with the following error:
2024-09-11 14:55:26 Error: Error reading configuration file: specified config file "/config/bitcoin.conf" could not be opened.
Progress, though! Thanks for leading this project. I've been excited about DLCs for years and am excited to hack on some projects now that you're helping make development more accessible.

I updated the documentation and made the development environment easier to start up.
https://github.com/bennyhodl/dlcdevkit/commit/dda8cdc9fc1204a208b96128e82a95a7cbfff312
https://github.com/bennyhodl/dlcdevkit/blob/master/README.md
https://github.com/bennyhodl/dlcdevkit/blob/master/ddk-node/README.md
Let me know if this helps!

Nice - this solved it. thanks!
I'm going to create a 2 line PR to fix the copy path in the oracledb.dockerfile and close this one


Review

Please review, @MilicaKov

#Description of repository
Python code is designed to minimize the electricity cost associated with charging an electric vehicle (EV) battery over 24 hours. The function takes as input the prices of electricity throughout the day, the arrival time of the EV, the state of charge (SOC) of the EV battery upon arrival, and the hours needed to fully charge the battery (H). It utilizes the PuLP library for linear programming to optimize the charging schedule, aiming to minimize the total cost while ensuring that the battery is fully charged by the specified time.
The code begins by defining the problem as a linear programming minimization task. Decision variables are created to represent whether the EV is charging during each time slot. The objective function is formulated to minimize the total electricity cost based on the charging schedule and electricity prices. Constraints are imposed to ensure that the battery is fully charged by the required time and that the charging operation occurs only when needed, taking into account the current SOC.
Once the optimization problem is defined, it is solved using the PuLP solver. The optimal charging schedule and total cost are then extracted from the solution. Finally, the code generates a visual representation of the electricity prices and the optimal charging schedule using Matplotlib, with the prices plotted on one y-axis and the charging schedule on another, providing a clear visualization of the optimized charging strategy.
Tests

[x] License exists
[x] Create a fork and start a pull-request
[x] Pytests passed as expected
[x] Ruff linter passed as expected

Submission of second homework assignment, @danielhuppmann


{@inheritdoc} not working with interfaces

In issue #389 the user @rrehbeindoi reported:
This issue appears to have come back. The sample class B ends up with a literal "{@inheritdoc}" rather then interface I's documentation.

Apparently a regression error has crept in which must be fixed

I'm having this issue just now. I'm trying to implement the CacheItemInterface interface from PSR-6. If I use {@inheritdoc} it just prints the string literal under the method...


feat: improved CODEOWNERS flow

So as things are these groups are only to make sure relevant people get a notification and review request assigned automatically, to help everyone see what is relevant for them. Importantly, we still require 2 reviews of anyone with reviewer (write) role. Being in a given team is more of a chore  while being reviewer at all is a privilege (power to approve).
Please don't be shy to ask to be added and removed from any group, fill PRs to modify the CODEOWNERS , and if anything is not ideal etc we can tweak and iterate.

validated again

Feel free to add me to config / DKG related stuff as well.

Should we make another group for these?


Support for AWS Provider Version 3

The only issue I ran into was https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade#resource-aws_cloudwatch_log_group, if you address that it will work with version 3.

Noticed that I was on an older version of the module. When I upgraded the issue went away.


Can not start the project!

Janry:magic-time wangzhili$ yo babel-boilerplate magic-time
(node:59963) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:59963) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.

     _-----_     ╭──────────────────────────╮
    |       |    │   Welcome to the Babel   │
    |--(o)--|    │    Library Boilerplate   │
   `---------´   │        generator!        │
    ( _´U`_ )    ╰──────────────────────────╯
    /___A___\   /
     |  ~  |
   __'.___.'__
 ´   `  |° ´ Y `

[?] What is the Github username/organization for this project? (janrywang)

events.js:160
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read property 'then' of undefined
    at Base.prompt (/Users/wangzhili/.node/lib/node_modules/generator-babel-boilerplate/node_modules/yeoman-generator/lib/base.js:240:44)
    at module.exports.generators.Base.extend.prompting (/Users/wangzhili/.node/lib/node_modules/generator-babel-boilerplate/app/index.js:82:17)
    at Object.<anonymous> (/Users/wangzhili/.node/lib/node_modules/generator-babel-boilerplate/node_modules/yeoman-generator/lib/base.js:439:23)
    at /Users/wangzhili/.node/lib/node_modules/generator-babel-boilerplate/node_modules/yeoman-generator/node_modules/run-async/index.js:26:25
    at /Users/wangzhili/.node/lib/node_modules/generator-babel-boilerplate/node_modules/yeoman-generator/node_modules/run-async/index.js:25:19
    at /Users/wangzhili/.node/lib/node_modules/generator-babel-boilerplate/node_modules/yeoman-generator/lib/base.js:440:9
    at runCallback (timers.js:570:20)
    at tryOnImmediate (timers.js:550:5)
    at processImmediate [as _immediateCallback] (timers.js:529:5)

Hey there, @janryWang . Thanks for the issue! And sorry that it's erroring for you 😓
It looks like the issue might be with this line, which is unexpected. That's just the regular old generator API.
Would you be able to help me debug the problem with you by posting your installed versions of yo & this boilerplate?
Thanks! :v:

This is my node&npm version [node v6.3.1 ,npm v3.10.3)]
yo&boilerplate version[yo v1.2.1 ,Babel-boilerplate v9.0.1]

Thanks! Also, what's your OS?

My OS is X EI Capitan,and I console.log in
node_modules/yeoman-generator/lib/base.js:237
like this

Base.prototype.prompt = function (questions) {
  questions = promptSuggestion.prefillQuestions(this._globalConfig, questions);
  console.log(this.env.adapter.prompt)
  return this.env.adapter.prompt(questions).then(function (answers) {
    if (!this.options['skip-cache']) {
      promptSuggestion.storeAnswers(this._globalConfig, questions, answers);
    }

    return answers;
  }.bind(this));

};

//////////

console.log(this.env.adapter.prompt)

result ==>function _prompt() {
  inquirer.prompt.apply(inquirer, arguments);
}

and if I console.log(this.env.adapter), it will show me

TerminalAdapter {}

and TerminalAdapter in this module

yeoman-environment/lib/adapter.js

@janryWang I'm unable to reproduce this 😦

How to clean my npm cache?

The docs should help with that: https://docs.npmjs.com/cli/cache

@janryWang did you ever get this working? Would you have time to pair sometime to go over it?

Going to close as inactive, but please comment here @janryWang if you want to try to figure it out.


ssl.so issue on aur package

> paru -Sy pastry
....
> pastry --help
pastry: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory

> uname -a
Linux abe 6.0.9-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 16 Nov 2022 17:01:17 +0000 x86_64 GNU/Linux

thank you for your great project!

Seems like it requires openssl 1.1, and I'm assuming you have a much newer version since you're on arch.


fix: use canvas measureText to calculate width in measureText

A bug got introduced in https://github.com/excalidraw/excalidraw/pull/5996 when adding text to arrows
Before

Now

Pending tasks for next PR

[x] A newline gets added when adding a letter to end in https://excalidraw-m66divtzf-excalidraw.vercel.app/#json=vfqSNglnZmD3jCVpe7pPY,N0ObgwJCj3oX5_bEj-Hsrw

[x]  Editor autogrows with below steps

open https://excalidraw-hzs43vab7-excalidraw.vercel.app/#json=V8IuuHiLiBN8Tz78LfHFV,O5phO7_M7NSG3kFPpGDZgA

edit

select all

delete

undo

[ ] Specs

@dwelle the editor growing issue with undo is also fixed by https://github.com/excalidraw/excalidraw/pull/6162


feat(datasets): make datasets arguments keywords only

Description
This is intended to fix #247.
Development notes
I added the keyword only marker * to the __init__ methods of all datasets and ran the respective tests. If any tests made use of positional arguments, I also updated them.
Checklist

[x] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[x] Added tests to cover my changes

Thanks a lot for your pull request @felixws! 🎉 We will review it soon.
I understand this is a breaking change for kedro-datasets and should go to 2.0?

Thanks a lot for your pull request @felixws! 🎉 We will review it soon.
I understand this is a breaking change for kedro-datasets and should go to 2.0? cc @noklam

Hi:) This would be breaking for anyone using positional arguments I believe.
I see some tests failed, I will have a look at those!

Some of the test failures are unrelated @felixws we're observing some weird things with tensorflow on Windows, feel free to ignore those for now.

Yes, this should be for 2.0.0

Before this is merge, we should check if there are any new datasets created. For example, https://github.com/kedro-org/kedro-plugins/pull/360/files, a new dataset is coming.

This is ready to be rebased 👍🏽

I rebased and added a commit to make the new LazyPolarsDataset keyword only.

Before this is merge, we should check if there are any new datasets created. For example, https://github.com/kedro-org/kedro-plugins/pull/360/files, a new dataset is coming.

This is a good point! We might need to double check all datasets have these changes before we release 2.0.0 I'll add it as a task to #421


Support deployment under subdirectory

Currently casdoor can only deployed on main host like http://test.com, but some times we need to deploy it under sub subdirectory such as http://test.com/login, but casdoor's frontpage url is hardcoded using/static/xxx.

@Abingcbc


Change the hook for multithread.

Now multithread will always
have a dummy profile function, so we can enable/disable the
profiling anytime we want.
The downside is, as we will only remove the profile function
when viztracer is deallocated, it's possible that the timing of
garbage collection affects the behavior of viztracer. This won't
be a problem if there is only one tracer per process. However,
for tests it's not the case.
This fix part of #72 when a spawned thread can't find thread
specific info without triggering profile function

Codecov Report

Merging #73 (e37ed3d) into master (058d749) will decrease coverage by 1.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #73      +/-   ##
==========================================
- Coverage   99.77%   98.42%   -1.36%
==========================================
  Files          18       18
  Lines        1809     1781      -28
==========================================
- Hits         1805     1753      -52
- Misses          4       28      +24

Impacted Files
Coverage Δ

src/viztracer/viztracer.py
95.61% <0.00%> (-4.39%)
:arrow_down:

src/viztracer/report_builder.py
96.33% <0.00%> (-3.67%)
:arrow_down:

src/viztracer/simulator.py
96.77% <0.00%> (-3.23%)
:arrow_down:

src/viztracer/flamegraph.py
97.59% <0.00%> (-2.41%)
:arrow_down:

src/viztracer/code_monkey.py
97.95% <0.00%> (-2.05%)
:arrow_down:

src/viztracer/main.py
98.84% <0.00%> (-1.16%)
:arrow_down:

src/viztracer/prog_snapshot.py
99.44% <0.00%> (-0.56%)
:arrow_down:

src/viztracer/tracer.py
100.00% <0.00%> (ø)

src/viztracer/decorator.py
100.00% <0.00%> (ø)

src/viztracer/event_base.py
100.00% <0.00%> (ø)

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 058d749...e37ed3d. Read the comment docs.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.77%. Comparing base (058d749) to head (e37ed3d).
Report is 256 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #73   +/-   ##
=======================================
  Coverage   99.77%   99.77%
=======================================
  Files          18       18
  Lines        1809     1809
=======================================
  Hits         1805     1805
  Misses          4        4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feat: add showsScrollIndex prop to VirtualizedList

Summary
Add new prop to ScrollView that allows to hide the fast scrolling indicator for tvOS. Reference: https://developer.apple.com/documentation/uikit/uiscrollviewindexdisplaymode?language=objc
Before (default behaviour):
https://github.com/react-native-tvos/react-native-tvos/assets/52801365/319898ed-b874-4822-a8bb-b4165e085130
After:
https://github.com/react-native-tvos/react-native-tvos/assets/52801365/51e5fc82-e209-41ff-9d97-b2a4f027ad56
Changelog

[tvOS] [Added] - new prop for controlling scrollIndex behaviour
Test Plan
Add showsScrollIndex prop to flat list and check if the fast scrolling indicator shows up.

Hey @douglowder
I've added implementation for Fabric.
As I understood from what @NickGerleman wrote here: https://github.com/react-native-tvos/react-native-tvos/pull/553#issuecomment-1698335588
I can move the types from VirtualizedList to ScrollView as "VirtualizedList already accepts and passes any Scrollview prop"
I've also set the default for this prop to be true so only if the user passes false explicitly it will be hidden.

This looks fine now -- I'll merge and then test in RNTester, maybe add to one of the examples there.


No background when using IITC

Has anybody seen this strange thing before:https://www.dropbox.com/s/jelsecxbpzoin6e/812320494_16294_15039771292486162114.jpg?dl=0
I have no clue why this could be like that...

What is your OS and phantomJS version? Have you modified the script?

Linux soojendi 3.13.0-46-generic #75-Ubuntu SMP Tue Feb 10 15:24:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
PhantomJS version 1.9.0
I specially made fresh checkout from git to test this, so the script is not modified.

@soend please try a higher version of PhantomJS, at least 1.9.3. Either delete your system PhantomJS or edit the ingress-ice script:
change

if [ "$OSTYPE" = "darwin"* ]; then
    PHANTOMJS="./phantomjs-osx"
else
    if (command -v phantomjs >/dev/null)
    then
        PHANTOMJS='phantomjs'
    else
        PHANTOMJS="./phantomjs"
    fi
fi

into
PHANTOMJS="./phantomjs"

Or just update the script, I've changed ingress-ice script so that system Phantom is never used

Afther updating the script i get this:
./ingress-ice: 490: ./ingress-ice: ./phantomjs: not found

Oh, sorry, i need to add a 64-bit version of PhantomJS
Please, wait 5 minutes

Please, update again now. Sorry for such inconvenience :(

Thanks, now it works.

:)


humanize should include a bit more data

"in seconds" should probably say "in x seconds"

There's a pull request just for this #232


Try to delegate maven-shade-plugin types

[ ] CHANGELOG's "Unreleased" section has been updated, if applicable.

https://issues.apache.org/jira/browse/MSHADE-481

Closed due to blocking.


Publish to Sonatype 0.0.6-SNAPSHOT

we need to publish latest version to sonatype and update examples accordingly.
(They are already presents on different branches)

sbt-swagger-codegen-0.0.6-SNAPSHOT and sbt-swagger-codegen-lib_2.10-0.0.6-SNAPSHOT are now published


faster algorithm for inner join

Code used for benchmarking: https://gist.github.com/peterktung/63c3b6d87fe22cb85621
Results:
Before:
Rehearsal --------------------------------------------------------
full_inner:          413.590000   0.850000 414.440000 (415.140870)
sparse_inner:        386.930000   0.380000 387.310000 (387.571845)
--------------------------------------------- total: 801.750000sec

                           user     system      total        real
full_inner:          388.470000   0.370000 388.840000 (389.073046)
sparse_inner:        400.040000   0.460000 400.500000 (400.807328)

After:
Rehearsal --------------------------------------------------------
full_inner:           85.980000   0.130000  86.110000 ( 86.224135)
sparse_inner:         83.670000   0.070000  83.740000 ( 83.777885)
--------------------------------------------- total: 169.850000sec

                           user     system      total        real
full_inner:           87.270000   0.100000  87.370000 ( 87.423039)
sparse_inner:         85.260000   0.110000  85.370000 ( 85.442580)

Agreed. You have any algorithms in mind?

daru needs to work with both MRI and JRuby. Since the bloomfilters-rb gem depends on MRI, lets keep the previous implementation in case the interpreter being used by the user is JRuby.
Could you please change the code such that the bloomfilters code is only used in case the bloomfilters-rb gem is installed? Also, don't add it as a runtime dependency. Add it as a development so that it's tested with rspec.
You can do something like Daru.has_gsl?, see this code for reference.
Also please don't change version numbers in Pull Requests. That should be a separate PR/commit.

Updated based on your feedback.

I just found a bug when it's a one/many to many join, I will fix and add a test case to it.

Looks good thanks! I'll add a note in the README later.


Fix poc examples selector & menu

I think selector is fixed by https://github.com/dankamongmen/libnotcurses-sys/pull/18?


Update and improve README

Towards https://github.com/giantswarm/giantswarm/issues/7584

I like the godoc badge. We should have it in all go projects.

Same here. I noticed Pawel added it in https://github.com/giantswarm/template/pull/3. I'm planning on working through the libs to improve the readmes. So I can do this then.


Create a demo case with simple topology with ACA and OVS

Please implement a demo case with the following simple topology using ACA and OVS images:

Requirements:

Please use multiple physical nodes as master, worker1 and worker2.
Please use ACA image as vhost
Please use OVS image (from distrinet) as TOR/Switches
Please get the throughput (iperf3) between two ACAs in the same node and also in the different nodes.

There is still a little problem with the mirror image of aca over there. At present, I have studied OVS and aca.

Go through the basic operation of ovs and wait for aca's container microservice deployment


update to 2.0.0-snapshot, java8, guava 21, frameworks 2-14

For these, I want to stay close to what android is using, since a large part of our userbase does android integration.

Well, it's not all of our users, so it's hard to say which one we should chose. I chose 21.0 right now to match appengine-plugins-core.

For maven/gradle which don't use OSGI, this is an issue. Since the classpath loader is not isolated per plugin, Dependencies must be as compatible as possible across all applied plugins.


Basic files for building the project

In its current state, this project is difficult for people to build with Coq. In this pull request, I introduce basic standard build scripts and metadata.
This means that most Coq users, if they have MathComp and Coquelicot installed, can simply run this command to build the project:
make

If someone wants to install the project and and depend on it in their code, it suffices to then run:
make install

Having an easy build is not only good for people who download the code using GitHub. It is also useful when packaging releases of the project in Coq's opam repository.

Hello palmskog,
Thank you very much for giving me the pull request!
Actually, I'm new to GitHub and not so familiar with setting up the appropriate environment.
I think I successfully merged your PR, but please let me know if I did wrong.
Again, I really appreciate your help!

@Yosuke-Ito-345 yes, everything went well with this pull request, thanks!
Are you interested in advertising this project to a wider audience? I can help out with creating a so-called opam package for the project and submit it to our central Coq repository. Then, interested parties would only need to run the following command to build and install your code:
opam install coq-actuary

The only thing you would need to do here is to create a new GitHub release, since the packaging requires build scripts to be present. My suggestion is that you call the release version 2.1, i.e., the tag would be named v2.1.

@palmskog thank you for suggesting the submission to opam package. I would be very happy if my package is in the Coq repository!
I added the tag v2.1 and made the public release. Did it go well?
I struggled to just add the tag... I did:
git clone https://github.com/Yosuke-Ito-345/Actuary
git tag -a v2.1 -m 'version 2.1'
git push origin v2.1
I hope I didn't make a mistake.

Thanks, this works fine. Now I just need one final detail before I submit the package (which I will invite you to approve): what license do you want to use for your code?
For people who are interested in seeing code reused maximally, we usually recommend the open source MIT license, otherwise we recommend the open source Mozilla Public License 2.0. See more on license choice here: https://github.com/coq-community/manifesto/#best-practices
There is no strict requirement even for an open source license, but we recommend it in general.

Thank you for explaining the license. Your advice is really helpful! (The other day I read some articles about this topic, but I couldn't understand.)
I hope this package will be used by many people, so I choose MIT license. :)


How to use lineArray returned in linesDetectedBlock GPUImageHoughLineDetection

I would like to use the lines detected through the HoughLineDetection operation. However, I can't seem to figure how the array is structured. I need the normalized m and c of y=mx+c but lineDetected is an array? The below code returns bunch of numbers in the range of -1 to 1 but I have no clue how to convert them to m and c pair arrays like [0.2, 0.3]
      for i in 0...Int(linesDetected){
          print(lineArray?[i])
      }

Would be great to hear back from you.

The array you get in that callback contains normalized slopes and Y-intercepts in pairs. ([slope, intercept, slope, intercept, etc.]). The linesDetected parameter tells you how large that array is, in pairs.


I want to extract the ActivityNet Caption 2D features

dear wang:
I want to extract the ActivityNet Caption 2D features, do you have the raw video? Or can I use TSN or TSP instead of 2D features？Looking forward to your reply，thank you！

Hi, in my experiments, TSP features (Fintuned R(2+1)D features) are better than TSN or 2D features.
And, ActivityNet organizer provided a google form to request the raw videos.
https://docs.google.com/forms/d/e/1FAIpQLSeKaFq9ZfcmZ7W0B0PbEhfbTHY41GeEgwsa7WobJgGUhn4DTQ/viewform

Hi, in my experiments, TSP features (Fintuned R(2+1)D features) are better than TSN or 2D features.
And, ActivityNet organizer provided a google form to request the raw videos. https://docs.google.com/forms/d/e/1FAIpQLSeKaFq9ZfcmZ7W0B0PbEhfbTHY41GeEgwsa7WobJgGUhn4DTQ/viewform

thank you very much


6.0: [MoveOnlyAddressChecker] Don't complete reborrows or their adjacent phis.

Explanation: Fix a compiler crash caused by completing certain lifetimes during move checking.
Move-only checking relies on the completeness of lifetimes of interest.  Way back in https://github.com/apple/swift/pull/68381 , a change was made to run lifetime completion in functions continaing move-only values; only values obviously derived from the value being checked had their lifetimes completed.  Much more recently, in 874971c40d2b20c9c52b2b906516c96798023dd9, an analogous change was made to complete lifetimes in functions containing move-only addresses; in the recent patch, though, rather than trying to find all the values that could be derived from the address being checked, all lifetimes in the function were completed.  This doesn't quite work, though, because lifetime completion doesn't know how to deal with reborrows--it's intended to be run in a SIL prior to reborrows existing.
Here, the lifetimes that are completed in functions with move-only addresses are trimmed back to exclude values whose lifetimes depend on reborrows.
Scope: Affects noncopyable code.
Issue: rdar://127312637
Original PR: https://github.com/apple/swift/pull/73358
Risk: Low.  Decreases the cases in which a SIL transformation is run.
Testing: Added regression test.
Reviewer: Andrew Trick ( @atrick )

@swift-ci please test

@swift-ci please test


ERROR in requirements.txt

Getting the following error while executing requirements.txt
ERROR: Could not find a version that satisfies the requirement timm==0.4.8 (from -r requirements.txt (line 3)) (from versions: 0.1.1, 0.1.2, 0.1.4, 0.1.6, 0.1.8, 0.1.10, 0.1.12, 0.1.14, 0.1.16, 0.1.18, 0.1.20, 0.1.22, 0.1.24, 0.1.26, 0.1.28, 0.1.30, 0.2.1, 0.3.0, 0.3.1, 0.3.2, 0.3.3, 0.3.4, 0.4.5, 0.4.9)
ERROR: No matching distribution found for timm==0.4.8 (from -r requirements.txt (line 3))

I think we have to change the version from 0.4.8 to 0.4.9

True. There is no v0.4.8 on PyPI: https://pypi.org/project/timm/#history

Thanks for spotting this problem, updated the version to 0.4.9 here (https://github.com/facebookresearch/xcit/commit/17dfb6e44c1de6062fc7770110f283f1c20fcf2f)


c8y-configuration-plugin crashes when repeatedly sending config snapshot message

Describe the bug
I was doing Configuration Management on Child Devices tutorial. When doing the final step of "Step 1: Bootstrap the child device" section, which is sending the config snapshot message, I received an error. When I retried sending the same message, it caused c8y-configuration-plugin to crash.
To Reproduce
The steps I made were just following the tutorial:

Create a child configuration file at /opt/childdevice/c8y-configuration-plugin.toml, with the following content:files = [ { path = '/opt/childdevice/config1', type = 'config1'} ]

And /opt/childdevice/config1:This is child device config

Send config file to thin-edge via HTTP: curl -X PUT --data-binary @/opt/childdevice/c8y-configuration-plugin.toml http://<IP_ADDRESS>:8000/tedge/file-transfer/child1/c8y-configuration-plugin
Send config snapshot MQTT message. Upon receiving any errors i just retried sending the message util the service was down. The message was sent 3 times in total. Here is the combined output of MQTT messages and c8y-configuration-plugin log i received when sending each message:# Entered commands marked as ">"
# mosquitto sub "#" messages marked as "MQTT<"
# c8y-configuration-plugin log messages marked as "LOG<"

> mosquitto_pub -h <IP_ADDRESS> -t "tedge/child1/commands/res/config_snapshot" -m '{"path": "", "type":"c8y-configuration-plugin"}'

MQTT< {"path": "", "type":"c8y-configuration-plugin"}
MQTT< Is a directory (os error 21)
MQTT< Is a directory (os error 21)
MQTT< 119,c8y-configuration-plugin,config1
MQTT< 119,c8y-configuration-plugin,config1
MQTT< 119,c8y-configuration-plugin,config1
MQTT< 50,100,Error on device creation
MQTT< 50,100,Error on device creation
MQTT< 50,100,Error on device creation

LOG< 2023-06-15T08:00:58.376258829Z  INFO MQTT: send Message { topic: Topic { name: "tedge/child1/commands/res/config_snapshot" }, payload: "{"path": "", "type":"c8y-configuration-plugin"}", qos: AtMostOnce, retain: false }
LOG< 2023-06-15T08:00:58.37628343Z  INFO C8Y-Config-Manager: recv Some(MqttMessage(Message { topic: Topic { name: "tedge/child1/commands/res/config_snapshot" }, payload: "{"path": "", "type":"c8y-configuration-plugin"}", qos: AtMostOnce, retain: false }))
LOG< 2023-06-15T08:00:58.37630052Z  INFO c8y_config_manager::upload: Config snapshot response received for type: c8y-configuration-plugin from child: child1
LOG< 2023-06-15T08:00:58.376445161Z  INFO Inotify: send Modified("/etc/tedge/c8y/child1")
LOG< 2023-06-15T08:00:58.376468951Z  INFO Inotify: send Modified("/etc/tedge/c8y/child1")
LOG< 2023-06-15T08:00:58.376641642Z  INFO Inotify: send FileCreated("/etc/tedge/c8y/child1/c8y-configuration-plugin.toml")
LOG< 2023-06-15T08:00:58.376702413Z  INFO c8y_config_manager::plugin_config: Reading the config file from /etc/tedge/c8y/child1/c8y-configuration-plugin.toml
LOG< 2023-06-15T08:00:58.376720003Z  INFO Inotify: send Modified("/etc/tedge/c8y/child1/c8y-configuration-plugin.toml")
LOG< 2023-06-15T08:00:58.376789873Z  INFO ConfigManager MQTT publisher: send Message { topic: Topic { name: "c8y/s/us/child1" }, payload: "119,c8y-configuration-plugin,config1", qos: AtLeastOnce, retain: false }
LOG< 2023-06-15T08:00:58.376811533Z  INFO C8Y-Config-Manager: recv Some(FsWatchEvent(Modified("/etc/tedge/c8y/child1")))
LOG< 2023-06-15T08:00:58.376823633Z  INFO C8Y-Config-Manager: recv Some(FsWatchEvent(Modified("/etc/tedge/c8y/child1")))
LOG< 2023-06-15T08:00:58.376833193Z  INFO C8Y-Config-Manager: recv Some(FsWatchEvent(FileCreated("/etc/tedge/c8y/child1/c8y-configuration-plugin.toml")))
LOG< 2023-06-15T08:00:58.376846004Z  INFO c8y_config_manager::plugin_config: Reading the config file from /etc/tedge/c8y/child1/c8y-configuration-plugin.toml
LOG< 2023-06-15T08:00:58.376885484Z  INFO ConfigManager MQTT publisher: send Message { topic: Topic { name: "c8y/s/us/child1" }, payload: "119,c8y-configuration-plugin,config1", qos: AtLeastOnce, retain: false }
LOG< 2023-06-15T08:00:58.376897094Z  INFO C8Y-Config-Manager: recv Some(FsWatchEvent(Modified("/etc/tedge/c8y/child1/c8y-configuration-plugin.toml")))
LOG< 2023-06-15T08:00:58.376908594Z  INFO c8y_config_manager::plugin_config: Reading the config file from /etc/tedge/c8y/child1/c8y-configuration-plugin.toml
LOG< 2023-06-15T08:00:58.376946704Z  INFO ConfigManager MQTT publisher: send Message { topic: Topic { name: "c8y/s/us/child1" }, payload: "119,c8y-configuration-plugin,config1", qos: AtLeastOnce, retain: false }
LOG< 2023-06-15T08:00:58.376967344Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us/child1" }, payload: "119,c8y-configuration-plugin,config1", qos: AtLeastOnce, retain: false }))
LOG< 2023-06-15T08:00:58.376985505Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us/child1" }, payload: "119,c8y-configuration-plugin,config1", qos: AtLeastOnce, retain: false }))
LOG< 2023-06-15T08:00:58.377002105Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us/child1" }, payload: "119,c8y-configuration-plugin,config1", qos: AtLeastOnce, retain: false }))

> mosquitto_pub -h <IP_ADDRESS> -t "tedge/child1/commands/res/config_snapshot" -m '{"path": "", "type":"c8y-configuration-plugin"}'

MQTT< {"path": "", "type":"c8y-configuration-plugin"}
MQTT< Is a directory (os error 21)
MQTT< Is a directory (os error 21)

LOG< 2023-06-15T08:02:36.13780359Z  INFO MQTT: send Message { topic: Topic { name: "tedge/child1/commands/res/config_snapshot" }, payload: "{"path": "", "type":"c8y-configuration-plugin"}", qos: AtMostOnce, retain: false }
LOG< 2023-06-15T08:02:36.13784111Z  INFO C8Y-Config-Manager: recv Some(MqttMessage(Message { topic: Topic { name: "tedge/child1/commands/res/config_snapshot" }, payload: "{"path": "", "type":"c8y-configuration-plugin"}", qos: AtMostOnce, retain: false }))
LOG< 2023-06-15T08:02:36.137870851Z  INFO c8y_config_manager::upload: Config snapshot response received for type: c8y-configuration-plugin from child: child1
LOG< 2023-06-15T08:02:36.138087812Z  INFO Inotify: send Modified("/etc/tedge/c8y/child1")
LOG< 2023-06-15T08:02:36.138110572Z  INFO Inotify: send Modified("/etc/tedge/c8y/child1")
LOG< 2023-06-15T08:02:36.138245453Z ERROR Runtime: Actor ConfigManager-6 has finished unsuccessfully: ActorError(FromFile(PathNotAccessible { path: "/var/tedge/file-transfer/child1/c8y-configuration-plugin" }))

> mosquitto_pub -h <IP_ADDRESS> -t "tedge/child1/commands/res/config_snapshot" -m '{"path": "", "type":"c8y-configuration-plugin"}'

MQTT< {"path": "", "type":"c8y-configuration-plugin"}
MQTT< {"pid":27141,"status":"down"}
MQTT< 102,devcontainer_c8y-configuration-plugin,"service",c8y-configuration-plugin,"down"

LOG< 2023-06-15T08:04:06.029828665Z  INFO MQTT: send Message { topic: Topic { name: "tedge/child1/commands/res/config_snapshot" }, payload: "{"path": "", "type":"c8y-configuration-plugin"}", qos: AtMostOnce, retain: false }
LOG< 2023-06-15T08:04:06.029864915Z ERROR Runtime: Actor MQTT-1 has finished unsuccessfully: ChannelError(SendError(SendError { kind: Disconnected }))
LOG< 2023-06-15T08:04:06.029904615Z  INFO mqtt_channel::connection: MQTT connection closed

Expected behavior
The service should not crash.
Environment (please complete the following information):

thin-edge.io version 0.11

Additional context
Looking at the log, I'd say there are two things that contributed to this bug:

file upload at /var/tedge/file-transfer/child1/c8y-configuration-plugin is consumed when operation did not complete successfully. Instead we could delete the file upload only after we've confirmed the operation is successful.
file upload at /var/tedge/file-transfer/child1/c8y-configuration-plugin being unaccessible makes the actor crash. This is the more important issue. Instead actor should just return error response/log the error and keep running.

file upload at /var/tedge/file-transfer/child1/c8y-configuration-plugin is consumed when operation did not complete successfully. Instead we could delete the file upload only after we've confirmed the operation is successful.

Not deleting the file on failure would lead to a lot of stale files staying on the disk, never getting cleaned-up. This is probably fine for the bootstrap message for c8y-configuration-plugin type.  But not as a general principle for all config_snapshot requests.

file upload at /var/tedge/file-transfer/child1/c8y-configuration-plugin being unaccessible makes the actor crash. This is the more important issue. Instead actor should just return error response/log the error and keep running.

Yeah, that's the main issue.

@gligorisaev the original tutorial i was using was removed because of the documentation refactor, but hopefully it won't be necessary. I expanded some of the steps with some explanations and what output is expected. Please let me know if any crucial information is missing.

@Bravo555 @gligorisaev the original tutorial has not be removed but moved around. Its new location is here.

QA has thoroughly checked the feature and here are the results:

[x] Test for ticket exists in the test suite.
[x] QA has tested the feature and it meets the required specifications.


feat: Make Extension.name public

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[ ] Documentation change/addition
[ ] Tests change

Description

Breaking if someone was daft enoug to be using a private attribute when public aliases exist.
This PR makes Extension.__name public under Extension.name at the request of @Astrea49

As far as i can tell this breaks nothing
Changes

Remove Extension.name property
Rename Extension.__name -> Extension.name

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

/ok-to-test


Changes for Unity debug extension

Some changes required for Unity debug extension: https://github.com/Unity-Technologies/vscode-unity-debug

@lukaszunity Thanks a lot for your pull request! And I see already more great commits... But To enable us to quickly review and accept your pull requests, may I ask you to always create one pull request per issue (please see https://github.com/Microsoft/vscode/wiki/How-to-Contribute).
My problem with your pull request is, that the first two commits open mono-debug for subclassing. The first commit is not a problem, but I'm a bit reluctant with the second (ignore variables). I looked into your vscode-unity-debug and got the impression, that your changes for unity support are small. What do you think about the idea of folding the Unity support directly into mono-debug?

@weinand Alright, I will create a PR pr issue.
Regarding subclassing; I was trying to reuse as much functionality from mono-debug as possible. But I think the best way forward for the unity-debug extension is just to duplicate the code in MonoDebugSession.cs into UnityDebugSession.cs and have all the necessary Unity changes live in our repo.
I don't think it makes sense to combine mono-debug and unity-debug. A lot more Unity specific code will be included in future and we want to be able to control the release schedule for the unity-debug extension.


[613] General Analytics

closes #613
Description of Work
Adding the remaining analytics calls including two new super properties for hover time & cursor sensitivity.

Hey @Ly-Kyli, @jsmorgan42, @SashankPatel,
@rowildcard, @rhsalas3, and I have some questions below.

Preset Category/Phrase Selection

We don't have implementation of selecting a preset category, there is one in the Mixpanel Tracking Plan sheet. Do we want to implement it?
Selection method is not appearing for our events in the Mixpanel. Is it still something we intend to include?

Keyboard from main page

We track when favorite is selected, do we want to track when it is deselected?

Usage events

When application is closed, we don't have this implementation and also nothing specified in the Mixpanel Tracking Plan sheet. Do we still want an event for this?
We have implementation of App Backgrounded, but it is not specified in the sheet. Should we include it in the sheet?

Preset categories are ordered as General, Basic Needs, Personal Care, Conversation, Environment, 123, My Sayings, Recents, Listen. When iPhone is on the portrait mode, we have one category as selected in the main screen. If we switch to Listen by clicking right arrow, all categories between General and Listen are tracked as Category Selected in Mixpanel, which is too much useless data. As @jsmorgan42, @kyliefk, @rhsalas3, @rowildcard, and I discussed, we need an implementation to add a Category property to the Phrase Selected event. In this case, we will track the phrases with category information for more meaningful reports.

Thanks for the updates! Test verified!
Devices:

iPad Pro - Test Device - iOS 15.3.1
iPhone 11 - Simulator - iOS 15.4

Version:

1.4.1-1


Problem processing Movies; PlexServer.search() got an unexpected keyword argument 'libtype'

error
what i miss hear?

python3 grab-all-IDs.py
Starting grab-all-IDs
connecting to http://<IP_ADDRESS>:32400...
/home/abayoumy/tools/Media-Scripts/Plex/grab-all-IDs.py:82: RemovedIn20Warning: Deprecated API features detected! These feature(s) are not compatible with SQLAlchemy 2.0. To prevent incompatible upgrades prior to updating applications, ensure requirements files are pinned to "sqlalchemy<2.0". Set environment variable SQLALCHEMY_WARN_20=1 to show all deprecation warnings.  Set environment variable SQLALCHEMY_SILENCE_UBER_WARNING=1 to silence this message. (Background on SQLAlchemy 2.0 at: https://sqlalche.me/e/b8d9)
ids = db.Table('keys', metadata, autoload=True, autoload_with=engine)
getting 288 movies from [Movies]...
Problem processing Movies; PlexServer.search() got an unexpected keyword argument 'libtype'
getting 76 shows from [TV Shows]...
Problem processing TV Shows; PlexServer.search() got an unexpected keyword argument 'libtype'
NEW: 0; UPDATED: 0

There was some refactoring done which wasn't accounted for in this script.
The sqlalchemy warning may still appear, but that's just a warning.  I have added env vars to attempt to disable those warnings.
10563b6


Error with styled-components  native-base v3

Hi,
Im trying to use latest version of native base with latest version of react-native but im getting the error showing the the screenshots. Apparently somewhere in native-base components something missing. I tried to install components on my side but i get other styled-components dependency errors. Any suggestion?! I didn't see anywhere that i've to install styled-components as dependency of native-base though?!
"dependencies": {
    "native-base": "^3.0.0-next.36",
    "react": "17.0.1",
    "react-native": "0.64.0"
  },

Solved! I had to install all peerDependencies
"peerDependencies": {
    "@expo/vector-icons": "^12.0.2",
    "@react-native-picker/picker": "^1.9.11",
    "react": "16.11.0",
    "react-dom": "*",
    "react-native": "0.62.2",
    "react-native-safe-area-context": "^3.1.9",
    "react-native-svg": "^12.1.0",
    "styled-components": "^5.2.1",
    "styled-system": "^5.1.5"
  },

from https://github.com/GeekyAnts/NativeBase/blob/v3.0.0-next.36/package.json

it's not work :(((

@sanketsahu
NativeBase v3 is compatible with 0.63 and above. :))))

Try wrapping your component in a SafeAreaProvider tag
import { SafeAreaProvider } from 'react-native-safe-area-context';
export default App = () => {
return (

);
}


Error: Dispatcher stream error, tuner may have crashed. When using PolicyBasedRL to do nas and set concurrency>1

Hello guys, i am using PolicyBasedRL strategy to do multi trial NAS experiments, when I set concurrency=2, the tuner crased, and concurrency=1 works just fine. Here is the error message:
[2022-09-08 02:09:28] ERROR: 1
Traceback (most recent call last):
  File "/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni/runtime/msg_dispatcher_base.py", line 97, in command_queue_worker
    self.process_command(command, data)
  File "/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni/runtime/msg_dispatcher_base.py", line 143, in process_command
    command_handlers[command](data)
  File "/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni/nas/execution/common/integration.py", line 223, in handle_report_metric_data
    self.invoke_callback('intermediate_metric', data['parameter_id'], self._process_value(data['value']))
  File "/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni/nas/execution/common/integration.py", line 119, in invoke_callback
    self.process_queued_callbacks()
  File "/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni/nas/execution/common/integration.py", line 104, in process_queued_callbacks
    self.intermediate_metric_callback(*call_args)  # pylint: disable=not-callable
  File "/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni/nas/execution/pytorch/graph.py", line 130, in _intermediate_metric_callback
    model = self._running_models[trial_id]
KeyError: 1
[2022-09-08 02:09:29] Dispatcher exiting...
[2022-09-08 02:09:30] Dispatcher terminiated
Error: Dispatcher stream error, tuner may have crashed.
    at EventEmitter.<anonymous> (/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni_node/core/nnimanager.js:647:32)
    at EventEmitter.emit (node:events:526:28)
    at WebSocketChannelImpl.handleError (/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:107:22)
    at WebSocket.<anonymous> (/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni_node/core/tuner_command_channel/websocket_channel.js:41:37)
    at WebSocket.emit (node:events:538:35)
    at WebSocket.emitClose (/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:246:10)
    at Socket.socketOnClose (/home/liangkai/miniconda3/envs/camp/lib/python3.8/site-packages/nni_node/node_modules/express-ws/node_modules/ws/lib/websocket.js:1127:15)
    at Socket.emit (node:events:526:28)
    at TCP.<anonymous> (node:net:687:12)

Environment:

NNI version:2.9/2.8
Training service (local):
Client OS:
Server OS (for remote mode only):
Python version: 3.8
PyTorch/TensorFlow version: pytorch 1.21.1
Is conda/virtualenv/venv used?: conda
Is running in Docker?: no

Configuration:

Experiment config (remember to remove secrets!):
Search space:

Log message:

nnimanager.log: nnimanager.log

dispatcher.log: dispatcher.log

nnictl stdout and stderr:

I think a possible problem might be that your trial sends intermediate results too fast, before the trial is even registered in the python end. Would you try to reduce the intermediate result frequency, or try to wait for a couple of seconds before sending the first intermediate result?

time.sleep(5) before report intermediate result doesn't help. When using Random strategy concurrency=2 works just fine, so i think there is something wrong with the PolicyBasedRL strategy

I suspect there might be some kind of racing conditions in the RL implementation.
If you have access to NNI code (which might be found in your site-packages), try to move submit_models into the thread lock and see whether that helps.

Great！Problem solved, thank you!
annother problem is this model describtion with PolicyBasedRL strategy, its a little hard to read ^_^

BTW. is there any method to load a well trained strategy? Like ENAS NASNet doing, when finish searching, man can load the controller and sample 100 archs and evaluate them.

If what you want is a one-shot strategy like ENAS here, you should use strategy.ENAS. PolicyBasedRL is a multi-trial strategy and no weights are shared at all.

IIUC, what you want here is a checkpoint of the strategy, which you can reload and test what it has learned. Otherwise, you would only need to lengthen the search and take the last 100 trials as the final samples.
Checkpoint is a nice feature, which we have been actively working on. In v2.9, we just supported checkpointing for RandomOneShot strategy. We will support more strategies in future.

Thank you for your advice and your hard work👍

发件人: Yuge Zhang @.>
发送时间: Saturday, September 10, 2022 10:23:05 AM
收件人: microsoft/nni @.>
抄送: Kai Liang @.>; Manual @.>
主题: Re: [microsoft/nni] Error: Dispatcher stream error, tuner may have crashed. When using PolicyBasedRL to do nas and set concurrency>1 (Issue #5117)
IIUC, what you want here is a checkpoint of the strategy, which you can reload and test what it has learned. Otherwise, you would only need to lengthen the search and take the last 100 trials as the final samples.
Checkpoint is a nice feature, which we have been actively working on. In v2.9, we just supported checkpointing for RandomOneShot strategy. We will support more strategies in future.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/nni/issues/5117#issuecomment-1242597565, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACIWZHWILXBT22JJGFMCLALV5PWITANCNFSM6AAAAAAQHIZQWY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


[gh-pages] Initialize bootstrap tooltip

What is this PR for?
Currently can't see a tooltip msg when I hover mouse on  which exists next to "Scalding", "Geode" and "Beam"  in https://zeppelin.apache.org/supported_interpreters.html. It needs to be initialized first as bootstrap instruction says.
What type of PR is it?
Bug Fix
What is the Jira issue?
N/A
How should this be tested?
Run the website(gh-pages) locally as described in here
Screenshots (if appropriate)

Before

After

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Tested and works as described.

@1ambda Thanks for testing it out!
Merge into gh-pages if there are no more comments on this.


Initial code for graph metrics.

Coverage increased (+0.9%) to 87.266% when pulling 32501d88d2701866946a924590bae49a2986c963 on graph_metrics into 0c8828f25cbd04156e73d3e14c452362099d3bb8 on master.

Coverage increased (+0.9%) to 87.266% when pulling 32501d88d2701866946a924590bae49a2986c963 on graph_metrics into 0c8828f25cbd04156e73d3e14c452362099d3bb8 on master.

Coverage increased (+0.9%) to 87.266% when pulling 28553d746e3d387e5915aafd5db24fa74ff0d77c on graph_metrics into 0c8828f25cbd04156e73d3e14c452362099d3bb8 on master.

Coverage increased (+0.9%) to 87.266% when pulling e3bf59824266fc4610a91fc1c780572e8176dd27 on graph_metrics into 0c8828f25cbd04156e73d3e14c452362099d3bb8 on master.


Swipe To Dismiss prevent some items to swipe.

Hi,
is it possible to prevent some items to swipe ?

I want to know, too

@anzaidemirzoi Found it.
See DismissableManager. Usage DynamicListView.setDismissableManager

it works thank you :)