Marshadium Z And Darkinium Z

Marshadow can't learn soul stealing seven star with or without Marshadium Z and darkria can't learn black hole eclipse with or without Darkinium Z so can you fix it

"You can use one Z-Move per battle. To do so, teach a Pokémon a move and give it a Z-Crystal of the same type (e.g. Fire Blast and Firium Z).The Z-Move will either be physical or special, depending on the base move. To check how powerful a Z-Move will be, or what the effects of a Z-Status Move are, type /dt name and it will appear at the bottom. Some Z-Moves, like Sinister Arrow Raid, are exclusive to certain Pokémon and base moves; /dt name will list their conditions."
" Z-Crystal: Marshadium Z |  User: Marshadow |  Required Move: Spectral Thief"
Please never open an issue here again for things you can just ask the Help room.


Dockerization

@vwdubb, I'd like to merge this in but it's still in draft mode. Did you want me to go ahead or are you still working on it?

@dbeaudoinfortin I do want to make further changes but this can be merged now.


Better libary / custom boards handling

Changes have been made so that LUFA could be enabled/disabled by selecting a board type after running the new "install.py" python script.
While this enhances the workflow, there is still room for improvement as the Arduino IDE has a "board manager" which is meant for new boards installation (as used by Adafruit and other third party boards manufacturers), which would allow the end user to install the new boards without having to install python or even use the commandine at all.
I've got a PoC working on this branch : https://github.com/CrazyRedMachine/Arduino-Lufa/tree/library
Workflow from a fresh arduino IDE install
Install LUFA library

go on https://github.com/CrazyRedMachine/Arduino-Lufa/tree/library , download ZIP
in arduino IDE, go to Sketch -> include library -> Add ZIP library..., select the zip file downloaded in step 1.

Library is now installed
Install custom boards

in arduino IDE, add a new URL to File -> Preferences -> Additional Boards Manager URLs  : https://github.com/CrazyRedMachine/Arduino-Lufa/raw/library/custom_boards/package_arduino-lufa_index.json

Restart Arduino IDE
in arduino IDE, go to Tools > Board > Boards Manager, wait for the list to load then type LUFA in the search box

Click install

Boards are now in the board list
From PoC to prod

(WIP) bump the library to 1.5 format by adding a library.properties file
create a "release" from github menu so that LUFA can appear directly in the arduino library manager rather than having to use the "add ZIP library"
change package_arduino-lufa_index.json contents to reflect the Palatis repo rather than my fork
update README to reflect the new install procedure

also a nice to have feature would be a generate.py script to automatically generate a new custom boards zip with new version number and the relevant data to be appended to the index.json... but i'm not sure yet if that's a good idea because it might break stuff and sometimes making changes to that might require further human intervention anyways...

and here is a quick write down of what was required to change from the inital repo :

the LUFA subfolder has to be populated with the files rather than being declared as a submodule (this is important so that the github "download zip" feature contains every required file, and so that arduino library manager can also retrieve the correct versions zip from the tags)
a package_<libname>_index.json file has to be created and hosted somewhere so that it can be added to the custom board manager URLs list
a custom boards zip folder has to be created and hosted somewhere so that the index.json can reference it (the contents are the same as generated by the install.py script, but with avr renamed to the lib name in the root of the zip)
(e.g. everything we have in <arduino install path>/hardware/arduino-lufa/avr/cores/* will be found in the zipfile in arduino-LUFA-1.8.3/cores/* )

Note I removed some subfolders from the avr/ path as I think they weren't technically needed (the different bootloaders etc can still be flashed without being in LUFA mode as a board type...)

Awesome, and a great write-up, too! I think the PoC is great, but maybe we can actually simplify it. Some ideas:

Could we move LUFA from being a library to being distributed with the board manager? I think it could be inside avr/cores/arduino, which is included by default. You could then #include <LUFA.h>, no need to add the library. This would make sense, as LUFA is basically replacing part of the Arduino core in this usecase.
The package_lufa_index.json could just be hosted at the root of the project, so it would be https://github.com/Palatis/Arduino-Lufa/raw/package_arduino-lufa_index.json, which seems quite ok as a URL.
The script seems like a nice idea. Ideally, we could maybe even do this automatically with GitHub actions? But you're right, it is not required. I'd rather just have a RELEASE.md file that explains what to do when releasing for now. This project is very low-traffic currently, so doing releases manually seems fine to me. However, I don't want to stop you taking a crack at it. If you can figure out how to make that work, it would certainly make our lives easier in the long run and could be a nice learning experience.

Ooh I actually love this, and indeed it makes sense since we cannot include LUFA without using the board, and we cannot use the boards without including LUFA... and it also avoids having to do the "make lufa available through lib manager" process (and also this way we don't have to waste space by including LUFA library which includes the boards zip, and then download the boards zip again from the url to install them...), I will quickly try it before going to bed!
haha I actually did it this way on a previous commit and then moved the file when I bumped the library format in order to keep everything board manager at the same place, so yea let's revert this
oh, I'm not familiar with github actions at all but might be worth to have a look (I'm just worried the script only helps in cases where doing it manually isn't much work anyways... )

made a new PoC on "board-only" branch and http://github.com/CrazyRedMachine/Arduino-Lufa/raw/board-only/package_arduino-lufa_index.json as url (beware you might have cache issues as I didn't change the version number, you should go to the board manager and uninstall the boards, then remove the url from preferences, restart the IDE, add the url, restart, then try to add... if it gives you "CRC error" just restart the IDE and then it should work)
I didn't put the LUFA folder in avr/cores/arduino but rather in avr/libraries/ , and #include <LUFA.h> works as intended :)
moreover, the dualserial example sketch does appear in File > Examples > Arduino-LUFA under the board section, which is awesome too! Thanks to your suggestion the workflow is now very clean :D
Ok so I think the new course of action should be :

keep everything the zip should contain as is on the repo (we don't include a custom_boards folder and we don't host the zipfile inside the repo.
(basically the repo structure looks similar to the current Palatis branch, but with a new library.properties as well to bump to the 1.5 format)
create a git release to have a versioned .zip, that will work as a custom boards zip file (we exclude the index.json from the zip generation if possible).
edit the index.json to reflect the new size and hash of the release zipfile, and point to the release zipfile url

Holy cow this is awesome! I just tried it on a fresh install, it's super easy and works perfectly!
This is some incredible work, should make LUFA way more accessible for those who need it. Hats off! To me this seems like the perfect occasion to bump the version to 1.0 as well.
I'm not sure how to integrate this properly now, because we can't really put all of this into a PR, right?
@Palatis, do you think you could add @CrazyRedMachine and me as collaborators to this repository so that we can approve PRs and create releases for this?

glad it's working :D I've updated the readme in the new-workflow branch
we can make a PR with all the changes, but indeed in order to be able to use it we then need to create a "release" from the github menu once the PR is merged, which only Palatis can do at the moment.
I will still prepare the branch as much as possible and open a PR, with instructions on what to do once it is merged :)

nice work, would be interesting to somehow get this into platform io

@fluffymadness thanks, never used platformio myself but I guess it must support custom boards somehow, so there should be a way too... you can hit me up on my forked repo if you need help with it
welcome about descriptor switching (if you check the PCFX branch you can even see how to switch during runtime), haven't touched rp2040 yet but that's awesome you made an xinput firmware for it too, will surely be useful when I get my hands on that board :D

@fluffymadness seems reasonable straightforward to get it into platform.io
I just took the existing framework-arduino-avr platform package, applied the Arduino-Lufa changes manually, and then pushed that to git. This is at https://github.com/sanjay900/framework-arduino-avr.git. This is however using the latest master version of LUFA as i was originally using that for an old project that I am porting across to platform.io.
Putting the following into the env section of my platformio.ini file was enough to be able to use LUFA from within platform.io
platform_packages =
    framework-arduino-avr @ https://github.com/sanjay900/framework-arduino-avr.git

@fluffymadness seems reasonably straightforward to get it into platform.io I just took the existing framework-arduino-avr platform package, applied the Arduino-Lufa changes manually, and then pushed that to git. This is at sanjay900/framework-arduino-avr.git. This is however using the latest master version of LUFA as i was originally using that for an old project that I am porting across to platform.io.
Putting the following into the env section of my platformio.ini file was enough to be able to use LUFA from within platform.io
platform_packages =
    framework-arduino-avr @ https://github.com/sanjay900/framework-arduino-avr.git

Im curious as I'm also trying to get LUFA working in platformio, whats a complete config for you look like? Thanks!

@fluffymadness seems reasonably straightforward to get it into platform.io I just took the existing framework-arduino-avr platform package, applied the Arduino-Lufa changes manually, and then pushed that to git. This is at sanjay900/framework-arduino-avr.git. This is however using the latest master version of LUFA as i was originally using that for an old project that I am porting across to platform.io.
Putting the following into the env section of my platformio.ini file was enough to be able to use LUFA from within platform.io
platform_packages =
    framework-arduino-avr @ https://github.com/sanjay900/framework-arduino-avr.git

Im curious as I'm also trying to get LUFA working in platformio, whats a complete config for you look like? Thanks!
My current project that i am using this on is open source, https://github.com/sanjay900/Ardwiino/
Hopefully enough is in there to answer your questions.

@fluffymadness seems reasonably straightforward to get it into platform.io I just took the existing framework-arduino-avr platform package, applied the Arduino-Lufa changes manually, and then pushed that to git. This is at sanjay900/framework-arduino-avr.git. This is however using the latest master version of LUFA as i was originally using that for an old project that I am porting across to platform.io.
Putting the following into the env section of my platformio.ini file was enough to be able to use LUFA from within platform.io
platform_packages =
    framework-arduino-avr @ https://github.com/sanjay900/framework-arduino-avr.git

Im curious as I'm also trying to get LUFA working in platformio, whats a complete config for you look like? Thanks!
My current project that i am using this on is open source, sanjay900/Ardwiino
Hopefully enough is in there to answer your questions.

Awesome thanks so much I'll try and see what i can extract from this haha, looks like a lot! I was thinking more just a pre-run script and a lib deps with specific branch :3 I'm starting to think the LUFA lib is a bit more involved.

If its easier i can put you together a minimal example probably?
That project is only massive because its a single project for a bunch of different microcontrollers at once haha

If its easier i can put you together a minimal example probably? That project is only massive because its a single project for a bunch of different microcontrollers at once haha
On the platform.io side, it really is as simple as putting the following in your ini file
platform = atmelavr
board = micro
framework = arduino
platform_packages =
	framework-arduino-avr @ https://github.com/sanjay900/framework-arduino-avr.git

And then you can just use LUFA as you would

Yeah haha i noticed! Im so impressed by the size!
Im sure a minimal project example would be very appreciated for lots of beginners like me, just those four lines looks really good though! But, I'm not sure how they include LUFA in the platformio way, should i still be using git submodules or is there a way for PIO to handle it via lib-deps?

https://github.com/sanjay900/LufaPlatformioExample
Heres a minimal example, LUFA is included as part of the arduino core itself, so you don't need to add it to lib deps.

@KenwoodFox sanjay900/LufaPlatformioExample Heres a minimal example, LUFA is included as part of the arduino core itself, so you don't need to add it to lib deps, or use any submodules, its all included within that framework-arduino-avr project thats being linked in. Its just a copy of the VirtualSerial example from the LUFA repo

This is really very concise and helpful, thank you very much! Ill be sure to share your example project around!

@KenwoodFox were you able to get it all working? Let me know if you need anything else

Hi,
Thanks for the sample code for PlatformIO, I managed tu upload it on my pro micro and it shows as LUFA CDC Demo.
Now it seems I can no longer upload new code to the board (get an avrdude error: programmer is not responding).
Is it due to having installed the LUFA driver or could it be something else ?
Thanks,

yes, you need to use the reset button to upload new code, as lufa doesn't contain the code to trigger a reset by opening the serial interface with specific baudrate

I suppose it probably would have been a good idea to include that in the sample, but I put that sample together pretty quickly and never really thought to include listening to the baudrate changes for jumping to bootloader

since #23 has been merged, no need to keep this open anymore :) thanks!

Awesome thanks! hopefully we see this working in pio too,

My pio examples should still be working


[Flow] __typename not marked a read-only

Describe the bug

To Reproduce
Steps to reproduce the behavior:
https://codesandbox.io/s/wizardly-moser-nsrl1?file=/types.js

My GraphQL schema:

Any schema

My GraphQL operations:

No operations.

My codegen.yml config file:

schema: schema.graphql
documents: document.graphql
generates:
  types.js:
    plugins:
      - flow
      - flow-operations
    config:
      useFlowReadOnlyTypes: true

Expected behavior
__typename should be read-only

Any chance this could be triaged?

Hi @FezVrasta and thank you for the report
Sorry but I'm not adding a lot here but just labeling it according to our new Contribution Guide and issue flow.
It seems already got into stage 1 thanks to your reproduction! Thank you for that!
Now in order to advance to stage 2 we'll need a failing test, would be great if someone could help progress the issues through the stages.
Thank you and sorry that this comment is not a complete solution (yet).


Is there a way to compose two images so the transparent background of one takes over the black background of the other?

Question about an existing feature
What are you trying to achieve?
I have image A. image A is an image with some transparent parts. Image A has a low resolution, so I send it over an AI Image Resolution API, and I get back a better version of that image but in jpeg format, which we call image B. Because image B is in jpeg format, the transparent parts are now black.
My question is: is there a way to convert those black parts back to transparent, distinguishing between the parts that are black because they used to be transparent and the parts that should actually be black in the image?
My idea was to compare the original image A with the new image B, assuming they are of the same size, and then make it so the transparent parts of Image A take over image B. Is there a way to do this with Sharp?
When you searched for similar issues, what did you find that might be related?
I tried to simply convert the jpeg to png with sharp by saying .png() but the black remains and it is not converted back to transparent. Not sure what I should do
Please provide a minimal, standalone code sample, without other dependencies, that demonstrates this question

Please provide sample image(s) that help explain this question
image A (png with transparent borders)
https://ratdao.mypinata.cloud/ipfs/QmVv7jcg4q1LdPgmM8pwQ3ia9VtYdzLexeCFujeakmF4md
image B (jpeg with black borders)
https://api.deepai.org/job-view-file/ffddfdc3-92af-4e0d-bbc4-1ee44118e542/outputs/output.jpg

The sample image B responds with 404.
Did you try all of the blend modes detailed at https://sharp.pixelplumbing.com/api-composite ? Perhaps try out or dest-out.

hi. Sorry, I'll resend the image B, I saved it this time!
https://i.ibb.co/2d9Gp9J/output.jpg

@Br3ikros Were you able to make any progress with this?

Hi! Sorry for the late reply! Yes i managed to! I don't have the code in
fron of me exactly but it was basically using blend functionality to create
a map to then compose again with the original image.
On Tue, 3 May 2022, 21:27 Lovell Fuller, @.***> wrote:

@Br3ikros https://github.com/Br3ikros Were you able to make any
progress with this?
—
Reply to this email directly, view it on GitHub
https://github.com/lovell/sharp/issues/3142#issuecomment-1116564849, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGKDSXPGP5B7EUDZLOXNL2TVIGDZRANCNFSM5RBVVLUA
.
You are receiving this because you were mentioned.Message ID:
@.***>


[Request] Add pokeball icon somewhere in fancy display

Pokeball information may be useful for people (such as myself) when breeding-in a specific ball during a breeding chain. Probably doesn't need to be displayed on every template.. but maybe the fancy one?
Right now I need to check the ball in-game as there doesn't seem to be any indication of it in KeySAVe.
It seems like the {{ball}} tag in custom formatting provides some sort of value corresponding to the ball, but it would be nice to have this converted to text and/or a sprite.
Not that important, depends on how much demand there is for this.

This is a planned feature in the pretty formatter. It has been for quite some time, but there were always other more important features :P For the time being you can use the {{ballName}} helper. Which thinking about it... may not support Gen 7 balls yet, welp.


[Chip] Does not focus on when navigating with arrows on with Safari 16.3 (186<IP_ADDRESS>.6)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example: Mui-focused
Steps:

Select the "Multiple values" example
Add a few movies to the list

Current behavior 😯
The chips don't change colours when you navigate using arrows like it does in Chromium
Expected behavior 🤔
The chips should switch to the colours defined in https://github.com/mui/material-ui/pull/35502/files#diff-8f415fe330d102624dbf0dbb137ff10972d0d336ecc89df39355d291f7cc2b02R183 which works on Chromium
Context 🔦
No response
Your environment 🌎
Packages.json:
    "@mui/lab": "5.0.0-alpha.121",
    "@mui/material": "5.11.11",
    "@mui/styled-engine": "5.11.11",

 System:
    OS: macOS 13.2.1
  Binaries:
    Node: 19.7.0 - /private/var/folders/jy/hc1n_qhd0sb1tbbm5z945v500000gn/T/xfs-c1d0b0ec/node
    Yarn: 4.0.0-rc.39 - /private/var/folders/jy/hc1n_qhd0sb1tbbm5z945v500000gn/T/xfs-c1d0b0ec/yarn
  Browsers:
    Chrome: Chromium: 110.0.5481.177 (Official Build) (arm64)]
    Safari: 16.3

@seivan Can you provide a screen recording?
It should work because I don't see a potential possible error. The background changes occur by .Mui-focusVisible. I'm curious to see why it does not work.


[url_launcher] build error on latest flutter

Running "flutter pub get" in Doris...                               1.3s
You are building a fat APK that includes binaries for android-arm, android-arm64.
If you are deploying the app to the Play Store, it's recommended to use app bundles or
split the APK to reduce the APK size.
    To generate an app bundle, run:
        flutter build appbundle --target-platform android-arm,android-arm64
        Learn more on: https://developer.android.com/guide/app-bundle
    To split the APKs per ABI, run:
        flutter build apk --target-platform android-arm,android-arm64 --split-per-abi
        Learn more on:
        https://developer.android.com/studio/build/configure-apk-splits#configure-abi-sp
        lit
Initializing gradle...                                              4.7s
Resolving dependencies...                                           7.7s
Running Gradle task 'assembleRelease'...

FAILURE: Build failed with an exception.                                                                                * What went wrong:                                                                      Execution failed for task ':url_launcher:verifyReleaseResources'.                       > java.util.concurrent.ExecutionException: java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: AAPT2 error: check logs for details
                                                                                * Try:                                                                                Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
                                                                                * Get more help at https://help.gradle.org                                                                                BUILD FAILED in 3m 11s                                                                  Running Gradle task 'assembleRelease'...                                                Running Gradle task 'assembleRelease'... Done                     192.2s (!)
****************************************************************************************
***
The Gradle failure may have been because of AndroidX incompatibilities in this Flutter
app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.
****************************************************************************************
***
Gradle task assembleRelease failed with exit code 1

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel beta, v1.7.8+hotfix.4, on Mac OS X 10.14.6 18G71a, locale en-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
[✓] iOS tools - develop for iOS devices
[!] Android Studio (not installed)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

Only when flutter build apk

The issue you're having might be because of not using AndroidX
The Gradle failure may have been because of AndroidX incompatibilities in this Flutter
app.
See https://goo.gl/CP92wY for more information on the problem and how to fix it.

@phanirithvij  I want to mention that is, this error only got when I try build android apk with release mode which is flutter build apk. If using flutter build it works OK. And also I don't think there any lib I use not using AndroidX since many lib I am using need AndroidX support. And I am using url_launcher newest version.
also this happened just when I upgrade flutter yesterday with version I posted above.
I suspicious it's a bug... or something missed out with that lib

I'm facing this problem too.

@BB-fat @jinfagang Is this still an issue with flutter 1.12? If not we may close this.

Upgrade url_launcher version works for me
In pubspec.yaml, change the version of the url_launcher like as follows:
url_launcher: ^5.4.1

and run flutter build apk again.

Hi @jinfagang
Please upgrade to latest version as this comment above suggests
if you're still experiencing this problem with latest stable, please create a new issue and provide the information required in the template.
Thank you


Add scanSilentBlock to wallet

Add a scanSilentBlock(silentBlock: SilentBlock) that uses the silent block to scan for incoming payments.

taking this


Send operator policy event if status is reset

ConfigurationPolicies were already handling this, and the predicate used there was modified for OperatorPolicy so that it is watching for the same events.
The new test for this behavior was added to the existing CRD status reporting test, because it benefits from being run after the full operator has been installed, and adding a separate test that does that would be an inefficient use of test time.

Created and linked https://issues.redhat.com/browse/ACM-15049, thanks for the reminder @dhaiducek

/unhold


fix: rendering problem in query preview sliding panel

EMP-2492

Pull request template

When opening Empathize without query, and then closing it by clicking somewhere in the brand recommendations area, the carousel behind the Empathize stays hidden until you roll over it.
Google Chrome has a problem rendering components with mask style applied. We think that is a new bug from Chrome, so we have decided to develop a temporary solution and wait for them to fix it soon.
Next steps:

Apply this fix to all the setups with a fill width empathize.

Motivation and context

[ ] Dependencies. If any, specify:
[X] Open issue. If applicable, link: EMP-2492

Type of change

[X] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that causes existing functionality to not work as expected)
[ ] Change requires a documentation update

What is the destination branch of this PR?

[X] Main
[ ] Other. Specify:

How has this been tested?

Go to the archetype:

Open empathize
Click somewhere in the brand recommendations area

The carousel that was behind the empathize should look ok.
Checklist:

[ ] My code follows the style guidelines of this project.
[X] I have performed a self-review on my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.

Check PR 352 preview 👀   https://x.test.empathy.co/preview/352/index.html


Switch Konnect sync backoff to warning

Is there an existing issue for this?

[X] I have searched the existing issues

Does this enhancement require public documentation?

[X] I have added an Acceptance Criteria item for adding and/or adjusting public documentation (if applicable)

Problem Statement
The Skipped pushing configuration to Konnect log message is currently set to error, which is flooding customer log pipelines.
Proposed Solution
Switch Skipped pushing configuration to Konnect to be a warning
Additional information
Is this considered a breaking change? Perhaps if people are alerting on it, but there is also a Failed pushing configuration to Konnect error which will remain an error
Acceptance Criteria

[ ] As a user, the Skipped pushing configuration to Konnect does not trigger my error alerts

I think this is not considered as a "Breaking change" -- a backoff does not mean an error happened in Konnect sync, but we cannot retry due to the backoff strategy. If users care about actual error happened, they will get the error in the "Failed pushing configuration to Konnect"  logs.


field_genre in islandora_defaults points to an undefined "genre" taxonomy

As far as I can tell, when field_genre was added to Islandora defaults, it referenced a genre taxonomy. But the taxonomy itself isn't defined in that module. So when we install the module now, we get the field but no taxonomy with it.

Uninstalling controlled_access_terms_defaults won't purge the configs. (It is designed to be enabled once and then disabled, leaving the configs behind, like search_api_solr_defaults.) The best way to manage missing configs is to export your configs (drush cex -y), copy the missing configs into config/sync, and then re-importing them (drush cim -y).

Same issue @mdlincoln is reporting was in the sandbox @dannylamb set up for MIG use.
I didn't realize the genre taxonomy was set up outside islandora_defaults, so I set up that taxonomy in islandora_defaults in the config changes that came out of the MIG sprint.
Danny has those config changes, but they haven't been merged anywhere. But just noting that there is now a duplicate genre taxonomy defined in my changes. There were a couple other entity reference fields that were supposed to be pulling from a taxonomy that didn't exist in the sandbox, so I defined those taxonomies and pointed the fields at them. Might be worth checking if those aren't also defined in controlled_access_terms

I just spun up the islandora-playbook using the ubuntu/focal64 base box and the genre vocabulary is present... so something is happening with the installer if the genre vocabulary is missing in your build.

My build was the sandbox Danny spun up for MIG. 🤷🏻

@dannylamb, what did you use to spin up the MIG box? The islandora/8 base box or isle_dc?
@mdlincoln, did you use the islandora-playbook or isle_dc for your site? If isle_dc, which make option did you use?

@seth-shaw-unlv I work with @mdlincoln
We are using isle-dc. We used the make local option after creating the codebase from the make-local-from-demo branch.
I had tried using the islandora-sandbox as the codebase and then using make local but ran in to some issues with the install -- I can speak to that more in a different issue if appropriate

I'm not very familiar with isle_dc and I'm in a training most of today and the next two days, so I'm probably not the best person to move forward with this. I put out a call on the isle channel of the Islandora Slack, so hopefully someone will be able to give it a look.


[GSSOC 23: New Project]: Custom Music Player Software

Custom Music Player (GSSOC '23)
Custom music player application using HTML, CSS, JavaScript
Features:

Set Unlimited music at playlist
Listen any music from playlist
Make fast forward or back at any time while listening
Randomly shuffle playlist
Make pause and resume music at any time

assigned to @sujanrupu
Complete this within 10 days and
Include a screenshot or deploy link to assess your project and thereafter include your project to the main code following the contributing.md guidelines.


Update supported Go language versions to include 1.20.0

Signed-off-by: avifenesh<EMAIL_ADDRESS>
Checklist
https://github.com/valkey-io/valkey-glide/issues/2739
Before submitting the PR make sure the following are checked:

[x] This Pull Request is related to one issue.
[x] Commit message has a detailed description of what changed and why.
[x] Tests are added or updated.
[ ] CHANGELOG.md and documentation files are updated.
[x] Destination branch is correct - main or release
[x] Commits will be squashed upon merging.

Please update readme too

Please update readme too

It doesn't mention anywhere. I don't we announced support for something somewhere.


Switch to e2e attachments spec v1

v1 uses 64 bits of the IV rather than all 128. It turns out
commoncrypto does this anyway and has no option to change it,
so iOS has always done this, so this is basically adding the
v: "v1" to the attachment info.
Add unit test testing the IV wraparound behaviour (this is what
tests how many bits of the IV we're using)
Fix base64 padder
Check type of things we get out of the attachment dict to avoid
crashes due to unknown selectors.

The thinking on not checking the version was that we're anticipating this to be backwards compatible if we were to change it again, so we should try to decode it anyway rather than fail hard (web uses the version field to switch the IV wraparound size, but iOS only supports 64 bit wraparound so we can't check and use 128 if the v field is absent). If we need to make a non-backwards compatible version, we'll put the files under a different json key in the content.


Adding Reseller component and REST APIs

Added Reseller component and REST APIS
Signed-off-by: Templeton, Randall<EMAIL_ADDRESS>

Will there be a separate PR to enable docker deployment for reseller?

Will there be a separate PR to enable docker deployment for reseller?

Yes, we can take care of that in a separate PR.


feat: implement the min_tokens sampling parameter

Adds the min_tokens sampling parameter to ensure a minimum number of generated tokens. Also provides a LogitsProcessor that could optionally be used to prevent generation of stop tokens.
The implementation here is meant to align with https://github.com/IBM/text-generation-inference (IBM's fork of HF TGI). In particular, we want to ignore stop sequences until min_tokens have been generated  (i.e. the stop sequence can be generated but generation will not terminate before min_tokens), and we want to be able to penalize the EOS token during sampling.
Related PR that stalled: https://github.com/vllm-project/vllm/pull/1945
Usage
Setting min_new_tokens on its own will prevent the generation from terminating due to EOS, stop token ids, and stop sequences, but those tokens may still be generated. The included Logits Processor can be used to penalize EOS and stop tokens to prevent generation of EOS/stop tokens until min_tokens have been generated:
llm = LLM(model="facebook/opt-125m")
tokenizer = llm.get_tokenizer()

min_new_tokens = 10
# NB: assumes the same stop token, which may not be the case with LoRA adapters
eos_token_id = llm.get_tokenizer().tokenizer.eos_token_id
stop_token_ids = [tokenizer.encode("\n")[1], tokenizer.encode("\n\n")[1]]
min_tokens_processor = MinTokensProcessor(min_new_tokens, stop_token_ids + [eos_token_id])

sampling_params = SamplingParams(
    temperature=0.0,
    stop_token_ids=stop_token_ids,
    logits_processors=[min_tokens_processor],
)

@simon-mo I am unable to add you as a reviewer but tagging you RE: https://github.com/vllm-project/vllm/pull/1945#issuecomment-1969629230.
I made the change to use a Logits Processor to penalize the tokens, but the changes are more than just the logits processor in order to skip the stop sequences check if min_tokens have not yet been generated. Let me know if you had something else in mind for the Processor.

@tjohnson31415 IMHO since an explicit parameter is being introduced for this, it would be best for the eos token suppression to be tied to that without having to additionally pass a LogitsProcessor. There is already an ignore_eos parameter which is similar but I think is practically only useful for performance testing; I think min_tokens wouldn't have much utility unless used in conjunction with the MinTokensProcessor anyhow.
An additional advantage is that it would then be possible to have a vectorized implementation (not necessarily in this first PR).
One question in this case is whether other provided stop tokens (if any) should be suppressed in addition to eos, I'd lean towards yes but would be good to get input from others on that too.

Thank you for the contribution, and thank Nick for the review.
My original intention is that min_tokens can be implemented using a built-in logits processor so the interface is cleaner. But current approach is fine as well.
There are some readability issue with _apply_min_tokens_penalty, please redo the list comprehension to make future devs easier to understand. And please add this to OpenAI compatible server as well (see protocols.py in the entrypoints/openai` directory).

@simon-mo this should be ready now!


make sure nikos users are gated with linux_bpf

What does this PR do?
This PR gates some files that are depending on nikos with the build tag linux_bpf. All users of exported functions are already gated with the same build tag so it's not causing any issue.
The main goal is to make sure nikos doesn't end up in the core agent (a win of ~2MiB).
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Container with ARM images not running

Hello, just wanted to document.
Currently, the arm builds from branches ubuntu20.04-arm and ubuntu22.04-arm do not run.
How to Reproduce
When creating the container, it errors out with the logs:
Docker logs
cat: twistd.pid: No such file or directory
no twistd.pid found
/entrypoint.sh: line 16: /usr/local/openvpn_as/scripts/openvpnas: No such file or directory

I found a similar issue on issue #108 in LinuxServer.io's archived repository for docker-openvpn-as
Would love help if anyone has an idea of why this is. Will troubleshoot and try to figure it out!

By using docker exec to open a bash shell into the container, I was able to get ovpn-as running by manually adding the repositories and the key. Then install using apt
I might have screwed something up with the Dockerfiles, getting somewhere!

fixed in PR (Developer branch #2)


exclude endpoints

Codecov Report

Merging #184 (7454a67) into main (6914303) will decrease coverage by 0.03%.
The diff coverage is 25.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
- Coverage   74.32%   74.29%   -0.03%
==========================================
  Files         131      131
  Lines        7466     7470       +4
==========================================
+ Hits         5549     5550       +1
- Misses       1610     1612       +2
- Partials      307      308       +1

Flag
Coverage Δ

unittests
74.29% <25.00%> (-0.03%)
:arrow_down:

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

Impacted Files
Coverage Δ

diff/endpoints_diff.go
83.17% <0.00%> (-2.40%)
:arrow_down:

diff/config.go
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Runtime error with 2 GPU with 0.8.0/0.9.0dev (RuntimeError: Can't enable access between nodes 0 and 1)

In a A10 with 2GPU:
➜ xx@A10 ~ nvidia-smi topo -m

	GPU0	GPU1	CPU Affinity	NUMA Affinity	GPU NUMA ID
GPU0	 X 	PHB	0-63		N/A		N/A
GPU1	PHB	 X 	0-63		N/A		N/A

>>> from cuda import cudart
>>> error, result = cudart.cudaDeviceCanAccessPeer(0, 1)
>>> print(error)
cudaError_t.cudaSuccess
>>> print(result)
0

With 0.7.1, we can infer with 2 gpu, but with 0.8.0/0.9.0.dev2024022000  we get a runtime error:
    output_token_ids = self.model.generate(**model_input, logits_processor=logits_processor, stopping_criteria=stoping_criterion)
                       │    │     │          │                             │                                   └ [<function TrtGenerationInstance._build_stoping_criterion_list.<locals>.wrap_stop_fn at 0x7f9446a6b5b0>]
                       │    │     │          │                             └ [<function TrtGenerationInstance._build_logits_processor_list.<locals>.wrap_logits_fn at 0x7f9446a276d0>]
                       │    │     │          └ {'batch_input_ids': [tensor([174422, 120957, 108755, 120161,    758, 152333,    100,   2791, 160713,
                       │    │     │                    107620,  33718, ...
                       │    │     └ <function ModelRunner.generate at 0x7f94f376eb90>
                       │    └ <tensorrt_llm.runtime.model_runner.ModelRunner object at 0x7f9446b919f0>
                       └ <trt_gen.trt_gen.TrtGenerationInstance object at 0x7f9446a3af50>
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/runtime/model_runner.py", line 613, in generate
    self.session.setup(
    │    │       └ <function GenerationSession.setup at 0x7f94f375b1c0>
    │    └ <tensorrt_llm.runtime.generation.GenerationSession object at 0x7f9446b92b00>
    └ <tensorrt_llm.runtime.model_runner.ModelRunner object at 0x7f9446b919f0>
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/runtime/generation.py", line 1305, in setup
    set_peer_access(self.mapping)
    │               │    └ <tensorrt_llm.mapping.Mapping object at 0x7f94f581bc40>
    │               └ <tensorrt_llm.runtime.generation.GenerationSession object at 0x7f9446b92b00>
    └ <function set_peer_access at 0x7f94f4388af0>
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/_ipc_utils.py", line 50, in set_peer_access
    raise RuntimeError(

RuntimeError: Can't enable access between nodes 0 and 1

In V100 with 8GPU, we can successfully infer at GPU0/1 with 0.8.0/0.9.0.dev2024022000, but failed at GPU3/4
	GPU0	GPU1	GPU2	GPU3	GPU4	GPU5	GPU6	GPU7	CPU Affinity	NUMA Affinity	GPU NUMA ID
GPU0	 X 	NV1	NV1	NV2	PHB	PHB	NV2	PHB	0-95	0		N/A
GPU1	NV1	 X 	NV2	NV1	PHB	PHB	PHB	NV2	0-95	0		N/A
GPU2	NV1	NV2	 X 	NV2	NV1	PHB	PHB	PHB	0-95	0		N/A
GPU3	NV2	NV1	NV2	 X 	PHB	NV1	PHB	PHB	0-95	0		N/A
GPU4	PHB	PHB	NV1	PHB	 X 	NV2	NV1	NV2	0-95	0		N/A
GPU5	PHB	PHB	PHB	NV1	NV2	 X 	NV2	NV1	0-95	0		N/A
GPU6	NV2	PHB	PHB	PHB	NV1	NV2	 X 	NV1	0-95	0		N/A
GPU7	PHB	NV2	PHB	PHB	NV2	NV1	NV1	 X 	0-95	0		N/A

In container, we have:
root@iZbp1e88tejvu7psufh2vqZ:/app/tensorrt_llm# python
Python 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from cuda import cudart
>>> error, result = cudart.cudaDeviceCanAccessPeer(0, 1)
>>> print(error)
cudaError_t.cudaSuccess
>>> print(result)
1

>>> error, result = cudart.cudaDeviceCanAccessPeer(3,4)
>>> print(error)
cudaError_t.cudaSuccess
>>> print(result)
0

Here is the questions:

Is it an expected result that we can not infer at GPU3/4 in V100?
Why we can infer successfully with 0.7.1 (at 2GPU), but failed with 0.8.0 ? How can we fix this?

Inference at single GPU works well for A10/V100, with all the versions.

A10:   Driver Version: 535.104.12   CUDA Version: 12.3
V100: Driver Version: 535.161.07   CUDA Version: 12.3

@bnuzhanyu thanks for the reporting.
please set --use_custom_all_reduce disable when building the engines. Ideally, it should fallback to nccl implementations if peer access is not supported, and we will fix that later.

also cc @kaiyux

@bnuzhanyu thanks for the reporting. please set --use_custom_all_reduce disable when building the engines. Ideally, it should fallback to nccl implementations if peer access is not supported, and we will fix that later.

it works!!

Hi @bnuzhanyu , thanks for the support. Since disabling custom_all_reduce is a WAR, and we expect custom_all_reduce to work under all cases, I'm re-opening this issue so that we can track and investigate it.


Cheat<T> is UB

Why UB should be avoided? Run this code and you'll know:
fn main() {
    let xs = &mut [0, 1, 2];
    let xs = &[0, 1, 2];

    let x0 = &xs[0];
    let x0 = unsafe { &mut *(x0 as *const _ as *mut _) };

    let x1 = &xs[1];
    let x1 = unsafe { &mut *(x1 as *const _ as *mut _) };

    *x0 = 10;
    *x1 = 20;

    println!("{:?}", xs);
}

$ cargo run
   Compiling ub-test v0.1.0 (/Users/tbm/dev/rs/ub-test)
    Finished dev [unoptimized + debuginfo] target(s) in 0.43s
     Running `target/debug/ub-test`
fish: Job 1, 'cargo $argv' terminated by signal SIGBUS (Misaligned address error)

UnsafeCell can be the help:
fn main() {
    use std::cell::UnsafeCell;

    let xs = &[UnsafeCell::new(0), UnsafeCell::new(1), UnsafeCell::new(2)];
    println!("{:?}", xs);

    let x0 = xs[0].get();
    let x1 = xs[1].get();
    let x0 = unsafe { &mut *(x0 as *mut _) };
    let x1 = unsafe { &mut *(x1 as *mut _) };

    *x0 = 10;
    *x1 = 20;

    println!(
        "{:?}",
        xs.iter().map(|x| unsafe { *x.get() }).collect::<Vec<_>>()
    );
}

$ cargo +nightly miri run
    Finished dev [unoptimized + debuginfo] target(s) in 0.00s
     Running `/Users/tbm/.rustup/toolchains/nightly-x86_64-apple-darwin/bin/cargo-miri target/miri/x86_64-apple-darwin/debug/ub-test`
[UnsafeCell { .. }, UnsafeCell { .. }, UnsafeCell { .. }]
[10, 20, 2]

Note also that miri doesn't argue about &mut T → *mut T → &mut T if the alias doesn't overlap with others:
fn main() {
    let xs = &mut [0, 1, 2];
    println!("{:?}", xs);

    let x0 = &mut xs[0] as *mut _;
    let x1 = &mut xs[1];
    let x0 = unsafe { &mut *x0 };

    *x0 = 10;
    *x1 = 20;

    println!("{:?}", xs);
}

$ cargo +nightly miri run
    Finished dev [unoptimized + debuginfo] target(s) in 0.01s
     Running `/Users/tbm/.rustup/toolchains/nightly-x86_64-apple-darwin/bin/cargo-miri target/miri/x86_64-apple-darwin/debug/ub-test`
[0, 1, 2]
[10, 20, 2]

An alternative to Cheat<T> would be:

Take the target value with mem::swap
Wrap that value in Rc<RefCell<T>> or UnsafeCell<T> if you know it won't break the aliasing rule at runtime
If the valus is of a container type, make use of &mut T → *mut T → &mut T
Give the target value back to the original place

Cheat<T> is now only be used in snow2d::ui for giving tree structure to Pool nodes. I'm implementing tree-oriented version of Pool, so Cheat will be removed before long.


Require other assets as dependency

e.g.
I add a custom js script which requires moment.js. So I create a second assets of type 'url' which is for the cdns of moment.js which I load on the same page as my custom script.
Assets does not care about the order of adding the scripts, so it depends on which assets you created first. So if moment.js is added after my custom script, its utitility can not be used, as my script does not know about moment.

As I am only adding dependencies that are shipped with Pagekit, I won't fix that - as far as I know, Pagekit does not allow to specify the order of all added scripts and styles.
If you think I'm wrong, feel free to reopen.

But it would be possible to add a dependency to another Assets of your extension, added earlier?
Your using the slug of the Asset as name/identifier at adding it to the asset manager. You could simply add a textfield, where you can add comma seperated slugs, which you want to require as dependency.
On view.content you just explode this string and add the array as dependency argument at adding the asset.
Users could use pagekit preregistered assets and their custom assets added via the asset extension. If the idendifier is not know, it will just ignore it.


Don't skip JS/TS diagnostic updates on equals

Even though the diagnostics on the ext host side may be equal, the displayed diagnostic may be at a different spot as we shift around markers on edit. We need to make sure the UI is also updated in these cases by setting the diagnostics again
Fixes #169443

I think this also fixed an issue I just hit when pasting in text where the line before an error changes length.
https://user-images.githubusercontent.com/972891/225538037-2b3fc67c-5f95-42e1-8d32-7db3c2f09c40.mp4


Add Accordion

Add Accordion for shlok commentaries

@ajaynegi45 Ready to work on it. Please assign if it’s up for grabs. Thanks!

Assignee: @sameer1612
Hi @sameer1612 ,
I'm pleased to inform you that I have assigned this issue to you. Your willingness to contribute to our project is greatly appreciated.
Please feel free to start working on the task, and if you have any questions or need assistance during the process, don't hesitate to reach out. We're looking forward to seeing your contributions to the implementation of the accordion feature for Shlok commentaries.

@ajaynegi45  I believe you were referring to these cards with blue headers (clicking on which does nothing as of now). Is the ideal behaviour that,  clicking on the card header will hide the content and clicking again will show it?
Please clarify the expectation so that I can start implementing. Thanks!

@ajaynegi45 I believe you were referring to these cards with blue headers (clicking on which does nothing as of now). Is the ideal behaviour that, clicking on the card header will hide the content and clicking again will show it?
Please clarify the expectation so that I can start implementing. Thanks!

Assignee: @sameer1612
Hi @sameer1612 ,
You are absolutely correct in your understanding. The ideal behavior for the accordions is as follows:

Clicking on the blue header of the accordion should expand and display the commentaries.
Clicking on the same blue header again should collapse and hide the commentaries.
Add open and close icon for that

Additionally, please make sure that the accordions are responsive, meaning they should work well on various screen sizes and devices.
At the starting of accordaion and after the chapter and shlok number , include an appropriate title that describes the content. For example, you can use "Commentaries" as the title for accordion.
Thank you for clarifying, and we appreciate your efforts in implementing this feature. If you have any further questions or need additional information, please feel free to ask.

@ajaynegi45   please review and merge the pull request for this issue:  https://github.com/ajaynegi45/Library/pull/15

Also, you don't need to write all that css, you installed react bootstrap but did not import the css file for it. We can clean up almost 80% of the css in this project and use ones provided by react bootstrap. If you want me to help with that, do raise a issue and tag me.

I've assigned the issue to you https://github.com/ajaynegi45/Library/issues/24#issue-1929605149


Issue in adding API Documentation

Following dialog box pops up which is not required for documents with URL as source. If we click on ADD CONTENT button, it redirects to a blank page.
Similar behavior observed when adding documentation with file source.

OPEN button in Documents listing page is not working (in Publisher).

When creating/editing docs with unsupported file format (tried importing a JSON file), 415 response can be observed from browser console, but UI does not shows it, nothing happens when clicking on save button.

When click on the Open button, it should redirected to the provided URL. Currently the button click does nothing.

When creating/editing docs with unsupported file format (tried importing a JSON file), 415 response can be observed from browser console, but UI does not shows it, nothing happens when clicking on save button.

Unsupported files cannot be uploaded anymore.


this.data not properly retaining typescript types when used in methods

Version
3.2.33
Reproduction link
www.typescriptlang.org/play
Steps to reproduce
Using Vue 3 and typescript, define a component:
export default defineComponent({
    name: 'Test',

    data() {
        return {
            test: new Child(),
        };
    },

    methods: {
        testMethod: function () {
            this.test = new Child();
            let test2 = new Child();
        }
    },
});

class Child {
    b = 0;
}

In the method, the parser thinks that test2 is of type Child. But it thinks that this.test is of type {b: number} (i.e. it has lost the connection to Child).
In this example, it's not a huge deal, because it could easily be recast. But if Child is instead defined as:
class Parent {
private a = 1;
}
class Child extends Parent {
b = 0;
}
then this.test still has the same type {b: number} (it loses the private member) and can no longer be cast to Parent. This causes endless typecasting to any to work around.
Another symptom it isn't picking up the right type is that something like this.test.a = 3 generates property does not exist (ts2339) while test2.a = 3; generates property is private and only accessible with parent (ts2341) (which is the correct error).
What is expected?
this.test should have type Child
What is actually happening?
this.test has type {b: number}

this is essentially caused by Ref-Unwrapping happening in reactive objects. As a side effect, classes are essentially reduced to their interface.
As you said, when using simple classes, it's not a big deal in most situations. when using more complex ones with private fields, internal state, side effects and so forth, I would argue that it's better to keep the instance raw anyway, and (at least in composition API, which has better Typescript inference), this would then work as you expect:
Playground
import { defineComponent, ref, shallowRef } from 'vue'

class Parent {
private a = 1
}
class Child extends Parent {
    b = 0;
};

export default defineComponent({
    name: 'Test',

    setup() {
        const child = shallowRef(new Child())

        const functionInSetup = () => {
            const _child = child.value
            _child.a = 0

        }
        return {
            child
        }
    },
    methods: {
        testMethod: function () {
            // interestingly enough, also works in Options API methods when
            // defined in setup with shallowRef
            let child = this.child
            child.a = 0
        }
    },
});

For Options API, for now, you would have to cast the value, unfortunately. Because even when doing the same thing in data that works in setup, it doesn't infer correctly:
data () {
  return {
     // still won't be recognized as instance of `Child` in options API methods.
     child: shallowRef(new Child())
  }
}

MAybe some TS guru wants to take a stab at this, but I'm not too optimistic.

This is super helpful, @LinusBorg.  Thank you.  I've had an outstanding question on stack overflow for a couple of months, if you want to post the same answer there for some credit. :)


can you please tell me how to use with vue.js with capacitor.js

i am using vue js i want to use this plugin with cpacitor.js can you please give me instruction that how to add this plugin in vue project

It's a Cordova plugin so you can use it with capacitor.js.
Please follow:
https://capacitorjs.com/docs/v2/cordova/using-cordova-plugins


See error message when swift.path is set

Describe the bug
On windows (UPDATE: also seen on macOS) even when swift.path setting is set and the swift exe exists in that directory, see this error message

Seems to only happen when swift is not in PATH
To Reproduce
Steps to reproduce the behavior:

Correctly select your toolchain
Make sure swift is not in PATH
Reload window

Expected behavior
If have a valid toolchain selected, shouldn't matter if cannot detect in PATH
Environment

OS: Windows 11
Swift version (output of swift --version): 6.0-SNAPSHOT and 5.10
Visual Studio Code version:
vscode-swift version:

Did some testing around this on Windows and I am able to reproduce if I remove the path to the swift runtimes directory. The swift toolchain installer actually adds three separate directories to PATH:

<user-dir>\AppData\Local\Programs\Swift\Runtimes\6.0.0\usr\bin
<user-dir>\AppData\Local\Programs\Swift\Toolchains\6.0.0+Asserts\usr\bin
<user-dir>\AppData\Local\Programs\Swift\Tools\6.0.0

If that first path to the Runtimes directory is malformed or deleted, then swift.exe will fail to launch and cause the extension to be unable to resolve the toolchain version. Unfortunately, this means that selecting a toolchain folder will never work on Windows. I suspect that this will require changes to the toolchain itself to get working.

Opened https://github.com/apple/swift-installer-scripts/issues/303 to see if there is anything that can be done with toolchain


registering glue nodes

this also adds a glue title in the tests to make sure that it will pass as expected
closes https://github.com/executablebooks/MyST-NB/issues/170

Yep once you fix the test, this looks good

tests are happy!


tests: run tests against zksync-era weekly

Component
Forge
Describe the feature you would like
We'd like to run our CI tests against zksync-era instead of only era-test-node, but not for every PR, only after a given interval.
This will allow us to detect changes that cause errors on testnet/mainnet but not on era-test-node
Additional context
No response

Maybe we can add onto this testing with zk stack


chore: Check lambda init result once, rather than every time.

What
Rather than checking the result of initialisation on every invocation of the lambda, check it once and register a specialized "failure handler" or "success handler".
Why
It moves the check out of the invocation loop, for what I'm sure is a completely un-measurable performance boost. Mostly this was something that I was wondering about when reviewing #9 and I wanted to see what it would look like. I think it looks OK, although YMMV.

I'm line ball down the middle on this vs the incumbent. On the one hand, I think this is more explicit and perhaps a bit easier to grok, on the other hand it results in a bit of duplicated boilerplate.
I'm going to ponder it for a bit longer and see whether a compelling argument for either option crystallises. I think I'm maybe 51/49 in favour at the moment :-)

FWIW, I will not be even the slightest bit upset of you close this out without merging, it was neat to try :-)

@timleslie what do you think about this, keep or close?

Having now had the time to really have a think about this, I think I fall just on the side of not merging it, sorry @rfk! I think the kicker for me is having two separate lambda_runtime::run instantiations made it feel more complex that what it is. I think it's more natural to have everything happen inside a single runtime function.
As I said before, pretty line ball, could've gone either way, but I've decided to make a final call on this to clear it off the board, rather than having it live in limbo for eternity :-)


Bug: Upgrade failing with Invalid format specifier on nodegroup updates

Expected Behaviour
eksupgrade would complete the pre-flight checks and complete the upgrade. Currently running the eksupgrade from sitepackages to avoid my local issue#48

Cluster is upgraded to version 1.22 from 1.21
Addons are updated
Image type is identified and then it fails with the message below in Current behavior

Current Behaviour
The upgrade path fails on
INFO:eksupgrade.starter:The Image Type Detected = Amazon Linux 2
ERROR:eksupgrade.starter:Exception encountered in main method - Error: Invalid format specifier

Code snippet
eksupgrade eksup-cluster 1.22 us-east-1

Possible Solution
No response
Steps to Reproduce

Created a cluster using eksctl eksctl create cluster -f cluster.yaml. Config yaml below

apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: eksup-cluster
  region: us-east-1
  version: "1.21"
nodeGroups:
  - name: ng-1
    instanceType: t2.micro
    desiredCapacity: 2
addons:
- name: vpc-cni
- name: coredns
- name: kube-proxy

Installed eksupgrade using pip install eksupgrade
Ran the eksupgrade command to upgrade the version to 1.22 eksupgrade eksup-cluster 1.22 us-east-1

Amazon EKS upgrade version
0.4.0
Python runtime version
3.9
Packaging format used
PyPi
Debugging logs
DEBUG:botocore.hooks:Event needs-retry.ec2.DescribeImages: calling handler <botocore.retryhandler.RetryHandler object at 0x1051279d0>
DEBUG:botocore.retryhandler:No retry needed.
INFO:eksupgrade.starter:The Image Type Detected = Amazon Linux 2
DEBUG:botocore.hooks:Event choose-service-name: calling handler <function handle_service_name_alias at 0x102aee4c0>
DEBUG:botocore.loaders:Loading JSON file: /Users/***/.pyenv/versions/3.9.10/lib/python3.9/site-packages/botocore/data/ssm/2014-11-06/service-2.json.gz
DEBUG:botocore.loaders:Loading JSON file: /Users/***/.pyenv/versions/3.9.10/lib/python3.9/site-packages/botocore/data/ssm/2014-11-06/endpoint-rule-set-1.json.gz
DEBUG:botocore.hooks:Event creating-client-class.ssm: calling handler <function add_generate_presigned_url at 0x102a47550>
DEBUG:botocore.endpoint:Setting ssm timeout as (60, 60)
DEBUG:botocore.client:Registering retry handlers for service: ssm
DEBUG:botocore.hooks:Event choose-service-name: calling handler <function handle_service_name_alias at 0x102aee4c0>
DEBUG:botocore.hooks:Event creating-client-class.ec2: calling handler <function add_generate_presigned_url at 0x102a47550>
DEBUG:botocore.endpoint:Setting ec2 timeout as (60, 60)
DEBUG:botocore.client:Registering retry handlers for service: ec2
ERROR:eksupgrade.starter:Exception encountered in main method - Error: Invalid format specifier

The format issue is on names = [f"/aws/service/eks/optimized-ami/{cluster_version: str}/amazon-linux-2/recommended/image_id"]


Refactor remaining function services to class

ConfigService
Subscription

https://github.com/elastic/apm-agent-js-base/issues/104


fix(docs): wrong  location in System.ClientModel

This is reported by docs team.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.

Thanks for putting this out, @archerzz.   I'd like to make one tweak to the doc string that was there, but otherwise looks good!


Python Cleanup

Added linting rules for flake8, formatting with black
Added a GitHub Action to enforce lint/format rules
Consolidated all existing DRC conversion functions into drc_babel.py
Consolidated fake_diode_replace and place_diode into diode.py
Consolidated and/or rewrote most def manipulation functions into defutil.py and other files under odbpy/.
Consolidated and/or rewrote most lef manipulation functions into lefutil.py
Added cat command to tcl: stop the whole [open x r] [read x] thing it's irritating
Made override_env able to override the PDK
Made PDK overridable via environment variables
~ Moved all files using odb to a new folder, odbpy/
~ Move replicate/update configs to config folder
~ Various Tcl Formatting Consistency Changes
~ Changed invocation in many files: check --help for more

Removed many unused files, all consolidated files

[ci ets]
Resolves #775

I'm gonna work longer on this. I might wanna add tests for all of this before merging it.

A cursory review would be fine.

Looks great to me @donn

Gets rid of the only use of perl
Consolidates all the DRC conversion into a single file, together with examples of what each conversion does
Moves the inline magic TCL script creation into separate files (something that always annoyed me)


8bitdo Retro Receiver locks up the system.

https://www.8bitdo.com/retro-receiver-genesis-mega-drive/
Test the Sizif 512K with a Retro Reciever for SEGA MegaDrive crashes and locks up the system. I need to turn the machine on and off to get it back.

Is 3.3V power line stable?

I think this RF dongle maybe drawing too much power. I would buy one for tests probably.

where in the world are you located? I can order 1 and have it shipped to you.
It can literally work with any BT controller.
https://download.8bitdo.com/Manual/Receiver/md/MD_RR_ENG_Manual.pdf

This isn't required.
After googling a bit, I found complaints about the compatibility of 8bitdo controllers with zx-uno:
https://www.zxuno.com/forum/viewtopic.php?t=3972
This may be caused by the same reason - zx uno like sizif provides only 3.3V power for gamepad.

I tried powering it through USB, it didn’t crash the system when you plug it in and crashes intermittently.
It will be nice if it works, i will order the 2.4Ghz ver to try out. Thanks

Anyway, I would love to send 1 to you if you want to work on it, at least to thank you for the hard work and wonderful design.

I bought 8BitDo M30 gamepad with Megadrive Bluetooth receiver and it's works just flawlessly with Sizif-512 (rev.D). So I assume there is some issue with your hardware.

PCB rev.E released with +5 power for gamepad. This should eliminate any theoretical incompatibilities.


Improve test coverage

Presently test coverage is awful — hovering around 50%. I've pushed a report generated using Istanbul to gh-pages, it's visible here. This goes hand-in-hand with #149.

See this comment on #149 for where help is needed.

This is kind of a dupe of #149, so closing.


Development/rust bridge

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 6 files pending identification.

Protex Server Path: /home/blackduck/github/ThunderNanoServices/587/rdkcentral/ThunderNanoServices

Commit: 244524867fd79bc6a08630ffba52c5755246edb9

Report detail: gist

Hi Pierre: Please use Metrological headers.  Is there any reason they aren't on the two js files? - Thanks, Martin

Hi Martin, its due to the fact that they where contributed by someone from Comcast. They are example files. Let me check with Comcast if I should copyright them with Metrological or with Comcast. or Would Comcast be a problem ?

@mhughesacn now looked at the git report, it is the wrong disclaimer in our code ;-) No problem, I will correct it.

@mhughesacn is it a problem that the example code does not have a license header ?

Hi @pwielders RDK policy is that all code files have headers.  It isn't a blocker though and if you have a justification, please tell me.
Also, for most components, using Comcast header on Comcast-created files is fine.  But if they are changed, use a Metro header on top (and maybe truncate the Comcast header to a two liner "Copyright Year Comcast.../Licensed under the Apache License").


Persist the logs

We need to find a way to also persist the server log /home/steam/.klei/DoNotStarveTogether/log.txt and the chat log /home/steam/.klei/DoNotStarveTogether/chat_log.txt.

We need to persist the whole /home/steam/.klei/DoNotStarveTogether/ directory anyway, because DST writes all kinds of other data into it.
-rw-r--r-- 1 1000 1000   15 Jan  5 16:37 boot_modindex
-rw-r--r-- 1 1000 1000    0 Jan  5 17:05 chat_log.txt
drwxr-xr-x 2 1000 1000 4096 Jan  5 16:03 client_temp/
-rw-r--r-- 1 1000 1000 8016 Jan  5 17:05 log.txt
drwxr-xr-x 2 1000 1000 4096 Jan  5 16:03 mod_config_data/
-rw-r--r-- 1 1000 1000  307 Jan  5 16:37 modindex
-rw-r--r-- 1 1000 1000  511 Jan  5 16:03 profile
drwxr-xr-x 2 root root 4096 Jan  5 17:05 save/
-rw-r--r-- 1 1000 1000  424 Jan  5 16:03 saveindex
drwxr-xr-x 2 1000 1000 4096 Jan  5 16:03 server_temp/
drwxr-xr-x 3 1000 1000 4096 Jan  5 16:03 session/
-rw-r--r-- 1 root root  848 Jan  5 17:05 settings.ini

Need to think about how this influences the settings.ini file which is written initially from the entrypoint script if it's not existing. Probably we won't have any problems, I guess.

The problem here is that log.txt is cleand any time the server is restarted. Is that desirable? Can we create a better log with all the historic?

And the log doesn't have neither any time reference. You don't know then the things happened.

The log.txt comes from DST itself, it's how the game logs it's output. If we went more information, we probably need to use/develop a mod. But that's not the scope of this project.

-rw-r--r-- 1 1000 1000   15 Jan  5 16:37 boot_modindex
-rw-r--r-- 1 1000 1000    0 Jan  5 17:05 chat_log.txt
drwxr-xr-x 2 1000 1000 4096 Jan  5 16:03 client_temp/
-rw-r--r-- 1 1000 1000 8016 Jan  5 17:05 log.txt
drwxr-xr-x 2 1000 1000 4096 Jan  5 16:03 mod_config_data/
-rw-r--r-- 1 1000 1000  307 Jan  5 16:37 modindex
-rw-r--r-- 1 1000 1000  511 Jan  5 16:03 profile
drwxr-xr-x 2 root root 4096 Jan  5 17:05 save/
-rw-r--r-- 1 1000 1000  424 Jan  5 16:03 saveindex
drwxr-xr-x 2 1000 1000 4096 Jan  5 16:03 server_temp/
drwxr-xr-x 3 1000 1000 4096 Jan  5 16:03 session/
-rw-r--r-- 1 root root  848 Jan  5 17:05 settings.ini

I think that this output you posted comes for a wrong configurations. You can check that the unknown files are files that are usually stored at save.
So we have:

save is a dir that store files generated by the game. Probably some of them are not necessary for a backup, but it's not a big deal right now.
log.txt and chat_log.txt. They are generated by the game too, but we don't need to backup them. We have other issue for these files, so they are not important for 0.3.0 Milestone.
settings.ini, worldgenoverride.lua and modoverrides.lua (and I probably forget some others). We know how to generate this files. But we need that the user tell us how they want them. Persist this files allow us to just ask one time for that info.

I think that our problem here is how we are going to allow the user to configure their servers: settings, mods, mod settings, world...

docker run --volume /home/user/config/overworld:/var/lib/dsta/server/DoNotStarveTogether/ \
    --volume overworld:/var/lib/dsta/server/DoNotStarveTogether/save/ [...]

Inside /home/user/config/overworld you have your desired config: the files settings.ini, worldgenoverride.lua and modoverrides.lua.
Because this is not "ready to play" the image must know how to generate three different configurations:

An overworld
An overworld master with shard
A cave slave with shard

docker run --volume /home/user/config/overworld:/var/lib/dsta/server/DoNotStarveTogether/ dstacademy/server generateconfig
docker run --volume /home/user/config/overworld:/var/lib/dsta/server/DoNotStarveTogether/ dstacademy/server generateconfig --shard=12345
docker run --volume /home/user/config/overworld:/var/lib/dsta/server/DoNotStarveTogether/ dstacademy/server generateconfig --cave --shard=12345

And, if the user just start the container the entry point script checks that there is not any configuration so he launches the generateconfig by default and starts a server.
This way we have a ready to use, easy to config server. But it's easy to customize too because you have access to the files and you can edit them as you want. And if we finally make the web page the output will be this three files.
I know that this idea needs to be polish. But what do you think as a starting point? Any UX problem? Any technical problem?

I appreciate the ideas, although we're gettin' off-topic I think.
So, persisting data from containers always involves volumes, at least as an easy, built-in option for Docker. Persisting the logs makes sense after all, if desired. That means, if one does not like to persist the files, no volumes should be configured for the containers.
After thinking about this, it probably makes total sense to change the pre-configured VOLUME to include the parent-directory of the save directory. The path would then be .klei/DoNotStarveTogether/, which includes save.
This will work from now on, because our entrypoint script does not overwrite existing files.
Additionally this enables people to just mount existing files, like settings.ini etc. to configure their server, if they don't want to use ENV variables.
Does that sound solid to you? We just change the default VOLUME path and document some examples.
We can think about how to configure the server via CLI in another ticket.

By the way, we could incorporate #16 into this, so we can fix both in one change. :+1:

It seems solid for me. You've conviced me about the environment variables. Or at least for a while ;-P.
If I continue thinking about my proposal I'll open a new issue.


0 bytes for the file

Trying to upload the file from the uri, using RN 17, Genymotion emulator,
let formData = new FormData();
formData.append('image', {uri: pic.uri, type: 'image/jpg', name: 'seventh.jpg'});
let options = {};
options.body = formData;
options.method= 'post';
fetch("http://posttestserver.com/post.php", options).then((response) => {
debugger;
});
message back: post body has 0 char long
it seems like the file is 0 bytes.

I'm guessing this isn't an issue with my package. Can you log your response from .showImagePicker()? If the URI returned is valid, I can assure you it's not 0 bytes and the issue is with fetch.
I personally had success using the react-native-file-upload package (https://github.com/booxood/react-native-file-upload)
        const obj = {
          uploadUrl: 'https://yourawesomewebsite.com/upload',
          method: 'POST',
          headers: {
            'Authorization': this.props.authToken
          },
          files: [{
            filename: 'file',
            filepath: response.uri,
            filetype: 'image/jpeg'
          }]
        };

        FileUpload.upload(obj, (err, result) => {
          console.log('uploaded avatar to url: ' + result.data);
        });

It shows the picture Image tag with URI.

That look like an android file path, i recommend you to update your version of image-picker.
The uri was the filepath and it's now an uri

I have version 13.1,
I have tried to use several file upload, including react-native-file-upload. I have tried iOS and Android and get this same error:
" InvalidArgumentPOST requires exactly one file upload per request.file09988428B13D691F9BDZ+tRRV9F0HipT7At1ZfMhn4L+yMknD6pr97pqqRcJ3N2vELa01H7NreX6DmSKN0pRNi64+DGQ="

I have tried on the iOS simulator, a real iPod with iOS 8, emulator, and a real Android LG phone with Lollipop.

I don't think that's an issue with this package, that's look like it's an issue with your upload
http://stackoverflow.com/questions/6030371/http-post-with-httpwebrequest
http://stackoverflow.com/questions/21498845/s3-upload-issue
Try to upload using fetch it with the proper header etc..
https://github.com/marcshilling/react-native-image-picker/issues/61#issuecomment-164467359

http://stackoverflow.com/questions/30737226/react-native-upload-image-to-amazons-s3

I have tried fetch, and xhr. And if I upload as a file with the base64 string that works
var base64Policy = data.policy;
//console.log('base64Policy:', base64Policy);
var s3Signature =  data['x-amz-signature'];
let formdata = new FormData();

this.addTextParams(s3Signature, base64Policy, data['x-amz-date']);
this.textParams.forEach((param) => {
    formdata.append(param.name, param.value)
  }
);

var xhr = new XMLHttpRequest();
xhr.open('POST',  'http://makeuroffer.s3.amazonaws.com'); //'http://posttestserver.com/post.php');
xhr.onload = () => {
  console.log('status ' + xhr.status);
  debugger;
};

formdata.append('file', pic.data);// {...'.\test.jpg', name: ('first'+".jpg") });
xhr.send(formdata);

Amazon is happy the signature is correct if just the base64 string.
But if i try to upload the actual file
formdata.append('image', {uri: pic.uri, type: 'image/jpg'});
I get the error. Always no matter what method of uploading or device.

Ahhh I got it ,
formdata.append('file', {uri: pic.uri, type: 'image/jpg'});

This works. The RN documentation is a bit wrong. See https://github.com/facebook/react-native/issues/5308.

You can close but all the bugs in RN github have file upload as 'image' for a picture. I think Amazon wants to see 'file'.


fix(NODE-3541): allow unacknowledged write with hint

Description
This is a replacement to #3409, from the knowledge I got there I could implement this properly instead of just improving the error message!
Now it actually fixes the entire ticket 🎉
What is changing?
The driver now allows unacknowledged writes when a hint is present in the following scenarios:

In update calls when the server is 4.2 or newer
In delete calls when the server is 4.4 or newer

Is there new documentation needed for these changes?
Not as far as I know, because I couldn't find any documentation on this limit in the first place.
What is the motivation for this change?
This allows us to submit a hint to an unacknowledged write. See more background in NODE-3541.
Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[ ] Changes are covered by tests see below
[x] New TODOs have a related JIRA ticket

I also need to update the tests here, but since this is my first contribution here I would love some guidance.
What I think we need to do is to update the test/spec/crud/unified/unacknowledged-*-hint-clientError.yml files and make them only test for the error on specific server versions, but expect success on others. If anyone could point me in the right direction here I would be grateful. Should we also rename the files to remove "clientError" from the name? Actually, the ticket mentions syncing unified CRUD tests, that might be what we should instead?
ping @baileympearson, thank you for reviewing my first PR, and giving me info to continue this!

Hey @LinusU - thanks for this contribution.  There are still some open questions about this ticket and at this time, it's not ready to be implemented.  Our team will need to discuss the ticket in refinement to iron out some of the details.
We don't have the bandwidth to pick this up at the moment but we will put the ticket in our triage queue to revisit it when we get the chance and when we do implement it, we'll make sure you get credit for your contribution as well.
I think we can move forward with https://github.com/mongodb/node-mongodb-native/pull/3409 in the meantime though!

I understand, let me know if there is anything you want me to do here 👍


FormCollections with RichtextArea not working

Hi! Reporting another issue: https://github.com/codematsing/django-formset-debug/commit/cf4e7b4d93febfbab31b315d15881b4b61932746
Execution:
Minor introduction of form field with RichtextArea on Gallery Form Collection for demonstration
Expectation:

Access http://localhost:8001/bootstrap/gallerycollection
Click add activity
Should be able to add a new Image Form
Click Submit
Should submit

Actual Results:

Nothing happens when clicking other buttons

Notes:

I tried to debug using chrome dev-tools and console logs but I couldn't find any error logs to point me to any issues. It's as if buttons just don't respond at all

Well spotted. I was able to reproduce this and fixed it using the monolithic build. I still have to check why it doesn't work in the default build. It seems as if the RichtextArea never fires a connected event. I stay tuned.

This issue has been fixed in version 1.5. @codematsing Please check out branch https://github.com/jrief/django-formset/tree/releases/1.5 and try if it works form you.


Skip acceptance test in forks

When pushing to my forked branch where secrets are not defined, the acceptance tests should be skipped.

I found there are some conversations around but it seems it is not possible to ignore forks yet. Alternatively, you can disable actions in your forked repository or create a:
Settings > Actions > General > Actions permissions > Disable Actions
You can also add a tag in your commits to skip actions
https://docs.github.com/en/actions/managing-workflow-runs/skipping-workflow-runs


ca-r/lib/ca-r/ca-r.rb:173:in `block in convert_covid19cases_test': oops (RuntimeError)

bin/ca-incidence-all out/covid19cases_test.csv out/
/home/dkelley/src/ca-r/lib/ca-r/ca-r.rb:173:in `block in convert_covid19cases_test': oops (RuntimeError)
        from /usr/share/ruby/csv.rb:2557:in `each'
        from /usr/share/ruby/csv.rb:1334:in `block in foreach'
        from /usr/share/ruby/csv.rb:1610:in `open'
        from /usr/share/ruby/csv.rb:1333:in `foreach'
        from /home/dkelley/src/ca-r/lib/ca-r/ca-r.rb:142:in `convert_covid19cases_test'
        from /home/dkelley/src/ca-r/lib/ca-r/ca-r.rb:262:in `convert_case'
        from /home/dkelley/src/ca-r/lib/ca-r/ca-r.rb:378:in `convert'
        from /home/dkelley/src/ca-r/lib/ca-r/ca-r.rb:497:in `gen_all'
        from bin/ca-incidence-all:13:in `'

Case data not being reported

1006>head -1 ./out/covid19cases_test.csv
date,area,area_type,population,deaths,cumulative_deaths,total_tests,cumulative_total_tests,positive_tests,cumulative_positive_tests

Can't calculate estimated R without it...

Looks like positive_tests, cumulative_positive_tests track case data reasonably well. so will use that instead.

Case data reappeared this week!

See #37, #38


HiFi-MAG-Pipeline: KeyError: 'min_contig_size'

Hi,
I'm running into the following issue with the HiFi-MAG-Pipeline v1.6.0.
I just test workflow with the following command:
snakemake -np --snakefile Snakefile-hifimags --configfile configs/Sample-Config.yaml
and got the KeyError message.

I use ATCC MSA-1003 as input data.
Thank you.

Hi @YenlingPeng ,
I'm not able to reproduce this error on my side. Can you please attach or copy/paste the contents of config.yaml here?

Hi @YenlingPeng ,
The config.yaml you are using appears to be outdated (v1.5).
You will need to use the new version of this config file (https://github.com/PacificBiosciences/pb-metagenomics-tools/blob/master/HiFi-MAG-Pipeline/config.yaml), which is included in the HiFi-MAG-Pipeline directory.
The same will be true for all the files - there were changes to items in the scripts/ folder as well.
When using the newest version of the pipelines, please make sure to download all the associated files, and not just the snakemake file.
Please update all files and let me know if any errors persist.

Hi @dportik,
I upgraded to the latest version (v1.6) and re-running pipeline.
But, I get new error message.
`Error in rule ConcoctAnalysis:
jobid: 20
output: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/3-concoct/atcc-msa-1003, /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/3-concoct/atcc-msa-1003/clustering_gt50000.csv
log: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/logs/atcc-msa-1003.ConcoctAnalysis.log (check log file(s) for error message)
conda-env: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/.snakemake/conda/d8dcd29ee246a470a1610d178025c180
shell:
concoct --composition_file /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/3-concoct/atcc-msa-1003.contigs_cut.fasta --coverage_file /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/3-concoct/atcc-msa-1003.coverage_table.tsv -l 50000 -b /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/3-concoct/atcc-msa-1003 -t 24 2> /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/logs/atcc-msa-1003.ConcoctAnalysis.log
(one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)
Removing output files of failed job ConcoctAnalysis since they might be corrupted:
/data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/3-concoct/atcc-msa-1003
[Mon Jan 30 14:40:34 2023]
Error in rule MaxbinDepths:
jobid: 18
output: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/2-bam/atcc-msa-1003.maxbin.depth.txt
log: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/logs/atcc-msa-1003.MaxbinDepths.log (check log file(s) for error message)
conda-env: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/.snakemake/conda/a17fd7858475ec78dc480fa36697a0cb
shell:
python scripts/Make-maxbin-depths.py -i /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/2-bam/atcc-msa-1003.JGI.depth.txt -o /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/2-bam/atcc-msa-1003.maxbin.depth.txt &> /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/logs/atcc-msa-1003.MaxbinDepths.log
(one of the commands exited with non-zero exit code; note that snakemake uses bash strict mode!)
[Mon Jan 30 14:40:36 2023]
Finished job 11.
1 of 20 steps (5%) done
Shutting down, this might take some time.
Exiting because a job execution failed. Look above for error message
Complete log: /data2/PB/Metagenomics/pb-metagenomics-tools-1.6.0/HiFi-MAG-Pipeline/.snakemake/log/2023-01-30T144032.038838.snakemake.log`
In the directory of the v1.6 pipeline, it seems that the file scripts/Make-maxbin-depths.py is not seen.
python: can't open file 'scripts/Make-maxbin-depths.py': [Errno 2] No such file or directory logs/atcc-msa-1003.MaxbinDepths.log (END)
Thanks for your help.

Hi @YenlingPeng ,
Thanks for pointing this out. There were several scripts missing from the updated workflow. I added them, so please go ahead and download the new release to obtain the updated script bin.
Please let me know if you experience any other issues.

Hi @dportik,
I downloaded the new version and ran the process again.
When I try to run concoct I get the error:
`Traceback (most recent call last):
File "/data2/PB/Metagenomics/pb-metagenomics-tools-1.6.1/HiFi-MAG-Pipeline/.snakemake/conda/e5bf84c8149cdac98e6448219decc368/bin/concoct", line 6, in
import vbgmm
ModuleNotFoundError: No module named 'vbgmm'
logs/atcc-msa-1003.ConcoctAnalysis.log(END)`
I think it's something with how python locates it's internal modules.
May I know how to fix it?
Many thanks for your help and your quickness.

Hi @YenlingPeng ,
This was a known issue with Concoct (see here). I tested the solution proposed in that thread and it worked for our systems. The environment recipe that is in the workflow (e.g., the concoct.yml file) contains that solution so I am unsure why this is happening.
I am planning on phasing out Concoct in the next release as I continue to test binning algorithms.

Hi @YenlingPeng ,
The newest version of HiFi-MAG-Pipeline is now available. Binning includes MetaBat2 and SeminBin2. Concoct and MaxBin2 have been retired, so this should end the issue.
I would encourage you to use this new version (v2.0.0), as it implements a "completeness-aware" strategy that outperforms all other versions of this pipeline. You can find more details here.


Fix backwards compatibility between TraceComponentBaseImpl and TraceComponent.

The problem is caused by the fact that the constructor of the TraceComponent was package protected in the previous version (0.5.*) and if try to load via the old API the new implementation IllegalAccessError happens:
java.lang.IllegalAccessError: tried to access method io.opencensus.trace.TraceComponent.()V from class io.opencensus.implcore.trace.TraceComponentImplBase
at io.opencensus.implcore.trace.TraceComponentImplBase.(TraceComponentImplBase.java:49)
at io.opencensus.trace.TraceComponentImpl.(TraceComponentImpl.java:32)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at io.opencensus.internal.Provider.createInstance(Provider.java:67)
at io.opencensus.trace.Tracing.loadTraceComponent(Tracing.java:81)
at io.opencensus.trace.Tracing.(Tracing.java:29)
at io.opencensus.exporter.trace.stackdriver.StackdriverExporter.createAndRegister(StackdriverExporter.java:85)
at com.google.cloud.bigtable.dataflow.WriteToBigtable.initialize(WriteToBigtable.java:74)
at com.google.cloud.bigtable.dataflow.WriteToBigtable.main(WriteToBigtable.java:125)

Codecov Report

Merging #575 into master will decrease coverage by 0.5%.
The diff coverage is 44.11%.

@@             Coverage Diff              @@
##             master     #575      +/-   ##
============================================
- Coverage     89.92%   89.41%   -0.51%
- Complexity      573      581       +8
============================================
  Files           110      110
  Lines          2412     2438      +26
  Branches        216      216
============================================
+ Hits           2169     2180      +11
- Misses          185      200      +15
  Partials         58       58

Impacted Files
Coverage Δ
Complexity Δ

...ncensus/implcore/trace/TraceComponentImplBase.java
94.44% <ø> (ø)
6 <0> (ø)
:arrow_down:

...va/io/opencensus/trace/TraceComponentImplLite.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...n/java/io/opencensus/trace/TraceComponentImpl.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ncensus/impllite/trace/TraceComponentImplLite.java
88.88% <87.5%> (-11.12%)
5 <4> (+4)

...a/io/opencensus/impl/trace/TraceComponentImpl.java
90% <88.88%> (-10%)
5 <4> (+4)

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 8808721...eec1fbe. Read the comment docs.


Remove unsupported system_packages from RTD config

https://blog.readthedocs.com/drop-support-system-packages/
https://github.com/readthedocs/readthedocs.org/pull/10562

Contributor checklist

[ ] Included tests for the changes.
[ ] PR title is short, clear, and ready to be included in the user-facing changelog.

Maintainer checklist

[x] Verified one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
[ ] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

Thanks @theryanwalker!


NO_COLOR tests fail on Fedora 36

This is broken again, though under Tmux 3.3a. I can only assume this is related to Tmux changing its $TERM var to tmux-256color, though I don't immediately know why this would cause breakage.


Home directory is not created with server.user

Using the following states does not result in the home directory being created. The use is created and /home/deploy is written in /etc/passwd, but the directory is not created.
    server.user(
        'deploy',
        group='deploy',
        ensure_home=True,
    )

Using pyinfra-0.1.dev26 (pip installed) on Ubuntu 16.04 x86_64 in a Linux container.

@hoh this was expected behaviour - ensure_home only triggered when home was explicitly set. I've now changed it to default home to /home/{name} in https://github.com/Fizzadar/pyinfra/commit/419df4f9145fc483f4f93d8786dddca94afa8194, so this should now work.

Great, 👍


RogueCloudClientLiberty not building in Ubuntu 16.04 or Windows 10

I have two 16.04 installations with different history, the one which is out of the box could not build the package after getting the prerequisites with apt install netbeans maven. The one which has gone through a lot was able to build and and run the package. Then I moved to my Windows 10 machine, installed latest maven and JDK 10, and the build breaks at the same point. Apparently I can choose two more verbose levels, which I had a look at but did not get enlightened, but posting this just in case something obvious is going on.
[INFO] RogueCloudShared ................................... SUCCESS [ 38.819 s]
[INFO] RogueCloudClient ................................... SUCCESS [  4.318 s]
[INFO] RogueCloudResources ................................ SUCCESS [  4.571 s]
[INFO] RogueCloudClientLiberty ............................ FAILURE [02:59 min]
[INFO] RogueCloudServer ................................... SKIPPED
[INFO] RogueCloudUtilitiesCLI ............................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:51 min
[INFO] Finished at: 2019-05-10T16:55:01+02:00
[INFO] Final Memory: 25M/94M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal net.wasdev.wlp.maven.plugins:liberty-maven-plugin:2.1.1:install-feature (install-feature) on project RogueCloudClientLiberty: CWWKM2002E: Failed to invoke ["C:\java\rogue-cloud\RogueCloudClientLiberty\target\liberty\wlp\bin\installUtility.bat", install, --acceptLicense, --to=usr, defaultServer]. RC= 32 but expected=[0, 22]. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :RogueCloudClientLiberty

PS In my working Ubuntu Iwent down the kube/microclimate path as well, and everything seemed to be going smoothly until importing from github and "Build failed". I did find this mention that earlier versions of microclimate would fail to build Liberty, but I had everything downloaded yesterday so, perhaps, that Liberty build problem is persisting.

Thanks for filing this @reppolice and for the detailed info! Happy to say I was able to reproduce, know what the problem is, and this should now be fixed by PR #31.
Presuming that you and I hit the same issue, the error was due to the JDK version. In Java 9+, a number of previously deprecated APIs were removed (JAXB in this case), and the version of the Liberty Maven plugin (responsible for installing and configuring the Liberty server) I was targeting was still using those APIs. Fortunately this has long been fixed by the Liberty Maven plugin, I just needed to bump up the plugin version I was targeting.

The Rogue Cloud game client repo (https://github.com/microclimate-dev2ops/rogue-cloud-client) has also been updated with the fix.


Gateway API Dep Bump

Bumps deps due to Gateway API v0.2.0. Note that refactoring was required due to controller-runtime v0.8.0.

Closing as I will add these changes to https://github.com/projectcontour/contour-operator/pull/198.


added delete request for group and added slide to delete from view

 Implement POST, PUT, DELETE requests for groups


Introduce an NPM package built around Noosphere Wasm library

As a follow-up to #164 and in the spirit of #131 , we should introduce an NPM package (that is, a JavaScript package built from TypeScript sources) that wraps the Noosphere Wasm library (and associated TypeScript bindings) in a high-level API that is suitable for general consumption by web developers who are comfortable wielding the NPM package ecosystem.
The package should probably load and run the Wasm core in a web worker, while the high-level API may be wielded from the main thread or another worker.

Would this allow web browsers to host clients for Noosphere, or would it be focused on node.js?

@kinostl this is primarily intended for web browsers, actually. Node.js is an interesting use-case, but I can't guarantee that we will support it out of the box right away.


Allow custom build script

This PR allows a user to add a custom build script (as long as it's defined in package.json). Why is this useful? Well, what if you want to deploy to Pages using a specific environment (not necessarily production)? This PR aims to fix that without having to change the behavior of npm run build

Can you please add the option to the docs in the README.


Add I/O timing cons, fix speed-grade, faster JTAG

Add I/O timing constraints for all ports.
Correct FPGA speed-grade to the faster "-2" grade.
Increase openocd JTAG speed using on-board programmer (used when loading programs into SRAM from computer).
Add missing HyperRAM physical IOB constraint.
Tidy pins_sonata.xdc and update deprecated properties.

The biggest change (by volume) is by far the I/O timing constraints. These should improve timing on some synchronous interfaces, such as the User JTAG, and improve reliability.
Further changes/refinements are likely.
Note that internal timing constraints have yet to be tackled.
Also note that build times may increase slightly due the there being more for the tool to consider and optimise timing-wise.

This will probably need reworking to account for pinmux once that is merged

Forgot multicycle constraint for Ethernet MAC SPI

Remove unused clock, add SPI clocks for R-Pi, loosen SPI input constraints a touch to ease implementation

Rebased to include pinmux. Reworked clock creation/renaming to use clock net names instead of PLL pins.

Realised the method of finding the PLL pins was faulty, so changed it. Also rebased

Missing line-wrapping \'s

Relax some margins to avoid internal setup timing failure on clk_sys


XLSX Files, Provider com.bea.xml.stream.EventFactory not found

My simple code:
InputStream myInput;
// initialize asset manager
AssetManager assetManager = getAssets();
//  open excel sheet
InputStream fin = openFileInput("myexcelsheet.xlsx");
// Create a workbook using the File System
XSSFWorkbook myWorkBook = new XSSFWorkbook(fin);
Produces Provider com.bea.xml.stream.EventFactory not found

Please read the main-page/README, especially the section "Necessary System-Properties".

Many thanks...
Il giorno sab 26 ott 2019 alle 21:31 Dominik Stadler <
<EMAIL_ADDRESS>ha scritto:

Please read the main-page/README, especially the section "Necessary
System-Properties".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/centic9/poi-on-android/issues/69?email_source=notifications&email_token=ANTEWNJUNVUVJZSDNDOBZ4LQQSLIVA5CNFSM4JFM4QH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECKPHZI#issuecomment-546632677,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANTEWNM2AI6UUJZ26DWUT3TQQSLIVANCNFSM4JFM4QHQ
.


Add error handling for node and compiler

i am getting this error while running the AEnode
===== Starting Node =====
Creating myaeternity_node1_1 ...
Creating myaeternity_proxy_1 ...
.Creating myaeternity_proxy_1
Creating myaeternity_node1_1
Creating myaeternity_node1_1 ... done
Creating myaeternity_proxy_1 ... done
.........................................................................................===== Node was successfully stopped! =====
Cannot start AE Node!


manifest: bsim: Do not import but replicate in main manifest

manifest: bsim: Do not import but replicate in main manifest

Due to a limitation in the west import feature,
a project cannot both have an import and be part of a group.
Moreover, when a project has an import and is not filtered
out, it is required for that project to be present
for most west commands to work.

As the bsim project is not filtered by default,
it causes trouble for users who never run a
west update but try to use west further.

To work around this issue, let's disable the import
in the bsim project, and instead replicate its content
inside Zephyr's main manifest.

Having a replica of the babblesim manifest content
is likely to cause some confusion in users,
wrt to which version of components they are using.
So whenever west supports both imports and groups, or another
simple and nicer way of working around this, it should be used.

The changes themselves LGTM, but before we merge this we need to decide betweent this approach and https://github.com/zephyrproject-rtos/zephyr/pull/57361.