implement colorationSpan in MEI 4.0

It would be useful to add a colorationSpan element which would function similarly to the new ligatureSpan element:
https://github.com/music-encoding/music-encoding/commit/3d000618562167b4a82d5956311d535896e7fab6
ligatureSpan elements are used to indicate where ligature was used in the non-CMN original notation.  Likewise colorationSpan would indicate where a coloration was used in the non-CMN original notation (or whatever you are calling coloration in the neumes/mensuration part of MEI).  For example if the name is color, then of course it would be called colorSpan.  If there is no name for it in MEI, then colorationSpan is probably better as otherwise people will be confused about the meaning of the word "color".
I put an example in either the music-encoding or verovio issues for coloration markers, but can't find it at the moment.  But here is a sample:

The solid square bracket above the notes is a ligatureSpan and the dashed square bracket above the second note is a proposed colorationSpan.
Ligatures always have to have two or more notes in them.  Coloration can be applied to one or more notes.

Either way will work for me.

<bracketSpan> added and <ligatureSpan> removed by 39d5e46

@axgeertinger wrote:

So, <ligature> is no longer supported in MEI 4.0.0; instead, <bracketSpan func='ligature'> is introduced.

No, I don't think so, but @pe-ro can clarify:  <ligature> is for encoding music that contains a visual ligature (as in the originally notated music).  The <bracketSpan func='ligature'> is used to encompass a series of individual (modern) notes that were originally in a ligature, but now are notated as separate notes, and the original intent is indicated by a bracket in the notation.
In other words <ligature> is specific to the mensural module of MEI and would be used to encode notes that are visually stuck together (which in turn defines their individual durations), and <bracketSpan func='ligature'> would be used to encode the same music in the cmn module as modern separate notes.

Ah, now I see it! Yes, indeed ´`is still available in the mensural module. My apologies for missing that.


[SPARK-41506][CONNECT][TESTS][FOLLOW-UP] Import BinaryType in pyspark.sql.tests.connect.test_connect_column

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/39047 which import BinaryType that's removed in https://github.com/apache/spark/pull/39050. This was a logical conflict.
Why are the changes needed?
To recover the build.
Does this PR introduce any user-facing change?
No, test-only.
How was this patch tested?
Manually verified by running ./dev/lint-python.

I am going to merge this to fix up the build.

Merged to master.

thank you @HyukjinKwon for this fix


Monarch errors when not in Glitch.com

When do these errors happen?

I can't seem to figure out why this is happening or replicate it myself.
If you happen to get more information, feel free to open this issue (or create a new one).
For now I'll close it.


use arbitrary finType for Address instead of nat

Fix for #3. Having an arbitrary finType for Address gives a lot of flexibility for instantiation (e.g., to use nat one just uses I_n for some fixed n).
On the other hand, extraction of finType has the somewhat annoying property that the enum list is computed whenever a module is loaded (not even necessarily used) at runtime. When using concrete types with many members (e.g., all valid IP addresses) this leads to serious problems and must be addressed with extraction directives.

@palmskog How about you just start committing these?


Destroying a flux plug on the server desyncs clients.

Destroying a flux plug/point seems to desync the client. The client still seems to think that there is something there, and depending on what block you put down afterwards you can crash the client.
Reloading the chunk by going to another dim or far enough away fixes it (but only temporarily obviously)
This only seems to happen in SMP though. I haven't seen this happen (yet) in my singleplayer world.
crashlog : http://pastebin.com/v0mEXuf5
Versions:

Minecraft : 1.10.2
Forge : <IP_ADDRESS>5
Sonar Core : 1.10.2-3.2.1
Flux Networks : 1.10.2-1.1.1

Can confirm this is happening in my SSP world as well.
crashlog: http://pastebin.com/xgx2YPSA
Modpack: SkyFactory 3
Version:

Minecraft : 1.10.2
Forge : <IP_ADDRESS>5
Sonar Core : 1.10.2-3.2.1
Flux Networks : 1.10.2-1.1.1

Confirmed this is happening to me as well in SMP
Crashlog: http://pastebin.com/wpPhda5H
Modpack: SkyFactory 3 3.0.5
Version:

Minecraft: 1.10.2
Forge: <IP_ADDRESS>5
Sonar Core: 1.10.2-3.2.1
Flux Networks: 1.1.1

Fixed in dev


build: bump Stylus SDK to v0.7.0-beta.1 and alloy to v0.8.13

Resolves #424
PR Checklist

[ ] Tests
[ ] Documentation
[ ] Changelog

Blocked by https://github.com/OpenZeppelin/koba/pull/14

Unexpected change in Storage due to this commit in SDK -> https://github.com/OffchainLabs/stylus-sdk-rs/commit/bc05111e2878132b5d67ef257ce803d2fd5adb68

@qalisander sth went wrong with your changes, see last E2E tests errors.

I see. But those errors are related to vesting_wallet::block_timestamp function and alloy.
External call works


liquibase.precondition.core.ViewExistsPrecondition@737bfc7f : String index out of range: -1 at [...]

Environment
Liquibase Version: 3.6.2
Liquibase Integration & Version: maven
Liquibase Extension(s) & Version:
Database Vendor & Version: MySQL 5.7 Community
Operating System Type & Version: Windows Server 2012
Description
This is similar to CORE-3360 as I didn't find a resolution for that, and that project is closed.
db_changelogs/changelog.xml : liquibase.precondition.core.ViewExistsPrecondition@737bfc7f : String index out of range: -1 at [...]
After analysing the affected systems, we figured out that this relates to MySQLs automatic generation of the SECURITY DEFINER in all createView changeSets. In case the user trying to access the view is not covered by that specific definer, the above issue occurs. This can happen for example, if the database user was changed since a specific view required for the changeSet was created. In our case, the recreation of the views with a matching SECURITY DEFINER solved the issue.
/Comment by Christian Schwarz on CORE-3360/

Hi @martoncsukas.  Thanks for taking the time to write this up.  It does look similar to CORE-3360.  We will add this to our queue of issues to fix.

I've tried to reproduced this issue on below environment without success:
Liquibase Version: 4.15.0

Liquibase Integration & Version: Maven (and CLI)

Liquibase Extension(s) & Version:

Database Vendor & Version: MySQL 5.7.39

Operating System Type & Version: Mac OS 12.1

Deployed successfully below changesets through CLI and Maven and and changelog has beeen generated successfully:
<changeSet author="mallod" id="1">
    <createTable tableName="segments">
        <column name="name" type="varchar(255)">
            <constraints nullable="false" primaryKey="true" primaryKeyName="CONSTRAINT_1"/>
        </column>
    </createTable>
</changeSet>
<changeSet author="mallod" id="2">
    <insert tableName="segments">
        <column name="name" value="Daniel"/>
    </insert>
    <insert tableName="segments">
        <column name="name" value="Jhon"/>
    </insert>
    <insert tableName="segments">
        <column name="name" value="Test Daniel"/>
    </insert>
</changeSet>
<changeSet id="3" author="mallod">
    <createView replaceIfExists="true" viewName="TEST_DANIEL_VIEW">
        SELECT seg.name  FROM segments as seg
    </createView>
</changeSet>
<changeSet id="4" author="mallod">
    <comment>New Column Added</comment>
    <addColumn tableName="segments">
        <column name="country" type="varchar(2)"/>
    </addColumn>
</changeSet>
<changeSet id="5" author="mallod">
    <createView replaceIfExists="true" viewName="TEST_DANIEL_VIEW">
        SELECT seg.name, seg.country  FROM segments as seg
    </createView>
</changeSet>

Could you please try again with a 4.15.0 or at least 4.2.0 (or newer) version? If you can still reproduce this issue we would appreciate if you can share the steps to reproduce, as well as some log (if possible).
Thanks.


Capture use cases for PASS Admin Interface

We should use this ticket to capture the initial set of features for the PASS Admin Interface.

MVP to present to users for feedback


locale pt_br

Hi!
the django-material doesn't have a Brazilian portuguese translation, but we added a few words.
Would you like the .po file?

yeap! that would be great.

Hi guys! @ramonrdm did you managed to provide the .po file? 😃
We would really love it ❤


⚠ Bofrost.si has degraded performance

In 4221532, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 4399 ms

Resolved: Bofrost.si performance has improved in 7a26c34 after 20 minutes.


Documentation to enable running with a headless minecraft server

I intend to write this documentation, will send a PR, just putting it here for tracking

Cool. Did you manage to run the mc_port mode with a headless MC server? There is a new discussion: https://github.com/MineDojo/Voyager/issues/88

I intend to write this documentation, will send a PR, just putting it here for tracking

Hi, it is great to know that is possible to use the minecraft server to run the game. I have launched the game and put the mod files into the mods directory. However, I could not find a method to set the gamemode to peaceful and allow cheats on. Do you know how to set the configurations in the Python code and the Linux commands?


the purpose of using T

Hello author, what is the purpose of using T as a priori information? Isn't the value of T corresponding to the whole map the same number?

The T map is used for the objective control parameter map.
During the training time, the value of T corresponds to the whole map with a same value. (T = 1 x t).
However, at inference time, the T map can be fed into the network with locally different values.
For more information, you can refer to the our FxSR paper and repository.


Documentation needs more about the project goals on index page

A Roadmap would be nice, with planned features. What components to expect etc. A little bit more long-term view.

+1
Having been using materialize as test platform for use in business i have to admit there are some key things here preventing materialize growth:

delivery roadmap so that people can plan relevant upgrades

invite community to develop more and contribute more, with original creators to act as reviewers and guides

completion of plugin options, there are more and more plugins being integrated but with only partial features

have animate.css capabilities (or at least incorporate it)

Otherwise great framework

@Dogfalo @acburst
Please solve this!


SST console autodeploy broken after one build timeout, build timeout on wrong domain config

Hey
I guess this can be considered feature request and two bugs.
Bug 1
When adding domain to the api gateway which cannot be configured correctly, build hangs until it times out (2 hrs)
Steps to replicate

have NS record on subdomain to different provider on than aws - for example vercel requires this. eg. dev.companyname.com => to vercel DNS server
ask sst to add domain on that subdomain to api gateway so eg. api.dev.companyname.com
deploy via autodeploy
Expected behaviour
Some error is thrown and build cancelled as this invalid behaviour
Actual behaviour
After creating a record to validate certificate sst console hangs (assume waits for cert to be confirmed, but that will never happen dns points elsewhere) till it times out

Bug 2
When the build was hanging in the above case, I've cancelled build directly in AWS, which now results in all subsequent builds to fail due to concurrent update - |  Locked      A concurrent update was detected on the app. Run sst unlock to remove the lock and try again.

Feature request
Add a way to cancel autodeploy build from console ui. Retrying/starting new builds would also be great. This would just replicate Seed's behaviour

Yeah cancel and retry is on the roadmap.
The domain issue I'm guessing is more SST related. Can you open an issue in the SST repo with that?


Fix bottom navigation links

Make the bottom navigation links actually link to the proper places.
Also, the wrong mouse pointer is being displayed. It currently is the text cursor (cursor: text), but it should be a pointer (cursor: pointer).

I think I can handle it. 😆


Update cicd.yml

Is this update still relevant?
I noticed I don't get notifications from you, it would be great if you give me a heads-up on my chat.
regards

Ok sir.
On Fri, 17 May 2024, 10:07 Sunny Ajiroghene, @.***>
wrote:

Is this update still relevant?
I noticed I don't get notifications from you, it would be great if you
give me a heads-up on my chat.
regards
—
Reply to this email directly, view it on GitHub
https://github.com/Gomerce/GomerceBE/pull/80#issuecomment-2117094622,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7HBWFPW3Z5LWU2F2LJZ4TZCXCGRAVCNFSM6AAAAAA6ZYTVJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJXGA4TINRSGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


[plugins] Cache github plugin

Summary
Excessive github requests are slow and can also lead to API rate limiting. This caches content for 24 hours.
Ideally we store resolved plugin data in the lock file and cache indefinitely (until user does update) but that's a bit more work so this is a stopgap.
Users can use devbox update to clear cache.
cc: @Lagoja
How was it tested?
Added print statements to track http requests and observed them going away after content is cached.

Does this also allow updating to newer versions of Github plugins by running devbox update?

Does this also allow updating to newer versions of Github plugins by running devbox update

Not currently, but the plan is to build that mechanism into this command as well. In order to do that we need to

Fetch current resolved version of plugin and save to lock file
Change update to re-resolve plugin

One caveat is that plugin semantics are a bit weird in case of upgrades. Specifically when it comes to creating files.
For non built-in plugins the semantics are the following:

virtenv files are always recreated.
devbox.d files are created if they are missing. This means some deleted files may be recreated. (I think this can be improved)

For built-ins:

virtenv files are always recreated.
devbox.d files are only created the first time the package that triggered the plugin is added to lockfile and then never again.

I think a future upgrade path that merges how both of these behave could be:

Save all version info in plugin. Instead of using a number/semver version, we could use a git hash (for builtins as well). This would allow folks to stay on an older version of a plugin which would allow us to do backward incompatible changes.
virtenv files are always recreated.
devbox.d files (if any) should show a prompt asking (add-if-missing, replace, ignore) or something like it.


[Feature] Remove items from library according to Trakt's list status

Expected Behavior
It's more like a feature request.
It would be nice if the library is mirroring the current status of ones Trakt's list. So when you remove items from your lists they get removed in the library as well. Maybe make that feature selectable in options.
Current Behavior
Only items that are added to lists are synchronized to library - not deleting items.
Possible Solution
Steps to Reproduce (for bugs)
Not a bug
Context
Your Environment
Don't know if a log is needed.
Copied from Quasar's issue.

@elgatito doesn't elementum has it for a long time now? i mean the sync from trakt collection/lists to library, and it even removes things.

@herrwusel @antonsoroko Not for long time, it was added in recent versions.
If you add something into Trakt list - it is added to Kodi, if removed from Trakt list - removed from Kodi.

@elgatito i see. i recently briefly tried this feature and it worked. so i guess this issue can be finally closed.


REQUEST: New Reviewer for

Change Membership to Commiter\Reviewer\Approver in the title in your case.

GitHub Username
whalecold
Requirements

[x] I have reviewed the community membership guidelines (https://github.com/cloudwego/community/blob/main/COMMUNITY_MEMBERSHIP.md)
[x] I have joined to the Discord and Feishu Group Chat (for Chinese)
[x] I am contributing (any of the following apply: issues, discussions, PRs, reviews) to 1 or more CloudWeGo repositories for more than 1 month

List of contributions to CloudWeGo

PRs reviewed / authored

xds

https://github.com/kitex-contrib/xds/pull/21
https://github.com/kitex-contrib/xds/pull/22
https://github.com/kitex-contrib/xds/pull/23
https://github.com/kitex-contrib/xds/pull/24
https://github.com/kitex-contrib/xds/pull/25
https://github.com/kitex-contrib/xds/pull/29
https://github.com/kitex-contrib/xds/pull/30
https://github.com/kitex-contrib/xds/pull/31
https://github.com/kitex-contrib/xds/pull/33
https://github.com/kitex-contrib/xds/pull/34

codec-dubbo

https://github.com/kitex-contrib/codec-dubbo/pull/92

codec-dubbo-tests

https://github.com/kitex-contrib/codec-dubbo-tests/pull/12

registry-nacos

https://github.com/kitex-contrib/registry-nacos/pull/32
https://github.com/kitex-contrib/registry-nacos/pull/26
https://github.com/kitex-contrib/registry-nacos/pull/25

config-nacos

https://github.com/kitex-contrib/config-nacos/pull/1
https://github.com/kitex-contrib/config-nacos/pull/2
https://github.com/kitex-contrib/config-nacos/pull/3
https://github.com/kitex-contrib/config-nacos/pull/4
https://github.com/kitex-contrib/config-nacos/pull/6
https://github.com/kitex-contrib/config-nacos/pull/8
https://github.com/kitex-contrib/config-nacos/pull/10
https://github.com/kitex-contrib/config-nacos/pull/11
https://github.com/kitex-contrib/config-nacos/pull/12
https://github.com/kitex-contrib/config-nacos/pull/15
https://github.com/kitex-contrib/config-nacos/pull/16
https://github.com/kitex-contrib/config-nacos/pull/17
https://github.com/kitex-contrib/config-nacos/pull/18
https://github.com/kitex-contrib/config-nacos/pull/19
https://github.com/kitex-contrib/config-nacos/pull/21

logger

https://github.com/hertz-contrib/logger/pull/22

kitex

https://github.com/cloudwego/kitex/pull/1035
https://github.com/cloudwego/kitex/pull/1038
https://github.com/cloudwego/kitex/pull/1048
https://github.com/cloudwego/kitex/pull/1058
https://github.com/cloudwego/kitex/pull/1083
https://github.com/cloudwego/kitex/pull/1363

protoc-gen-validator

https://github.com/cloudwego/protoc-gen-validator/pull/10

doc

https://github.com/cloudwego/cloudwego.github.io/pull/1126
https://github.com/cloudwego/cloudwego.github.io/pull/944
https://github.com/cloudwego/cloudwego.github.io/pull/896
https://github.com/cloudwego/cloudwego.github.io/pull/576

kitex-examples

https://github.com/cloudwego/kitex-examples/pull/131

Issues responded to

https://github.com/cloudwego/kitex/issues/1042

1 strong support

+1 thanks @whalecold for your great contribution to cloudwego!

+1

+1 thanks @whalecold for your great contribution to cloudwego!

+1 Look up to you~

Support! Thanks for your great contribution to cloudwego!

Hi @whalecold , your request has been reviewed by the CloudWeGo Kitex maintainer team and passed with majority approval.
You have been promoted as a CloudWeGo Kitex Reviewer. Your certificate is here.
Please check Responsibilities and privileges for more details.
Congratulations !


Updated Metrics Code

The issue was the file name for the images.  You had them with a lowercase "m" but in the img folder, they are "M".  The image file name must match exactly what is in the folder.  I have corrected and published this.  Please be sure you do a pull in each repository to update your local versions before you continue any more editing.


[BugFix] fix #6626: support add json column in unique/primary table

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Support alter table add json column in unique/primary table.

@Mergifyio backport branch-2.2

[FE PR Coverage check]
:heart_eyes: pass : 0 / 0 (0%)


Removing double forward slash before CDATA

I've also posted this here as I wasn't sure if it was a CSV or uglifier problem.
I have an issue when running uglifer JS compression over pages which contain the CSV embedded script.
The compressor seems to be removing the forward slashes before CDATA;
# Before
<script>//<![CDATA[ ...

# After
<script><![CDATA[ ...

This is causing:
Uncaught SyntaxError: Unexpected token <

Versions:
Uglifier: 3.0.0 (Have tried 2.7.2 also)
client_side_validations (4.2.3)
client_side_validations-simple_form (3.2.3)
A possible workaround could be to disable compressing inline JS, is this available?

As a workaround I'm now not compressing inline JS.


some method of figuring out if something is rendered in a slot

I see that you have onChange, but it doesn't get called on the initial render. Is passing context up the tree from the components that render the fills the only method I can use to figure out if a slot has something in it?

Hi @cbranch101
Slot is always empty on first render, therefore you can use onChange to detect if something is really appeared in it (and fallback is hidden).
Please, provide an example code when method doesn't get called on first render.
(this is recent feature, you may need to update nano-slots to v1.3.0 first)

Works great! Awesome, yep, I just need to stay more up to date.  Thanks so much for taking the time to respond.


DRAFT: Very rough in-progress work on Kotlin support in the Gazelle plugin

Do not merge this! It's for discussion. This has soo many caveats right now. It is ugly, is messy, is incomplete, has debug statements everywhere, has commented out code, etc.
I'm putting this up anyway so that people can take an early look at the overall approach, and give any general comments or guidance.
The overall approach:

Add a new Gazelle directive jvm_kotlin_enabled, which defaults to false, to optionally enable Kotlin processing. Use this flag to optionally look for Kotlin files in addition to Java files within packages. If a Kotlin file is present in a package, then we use the kt_jvm_library rule instead of java_library rule. Most remaining Go logic is unchanged.
Add a KtParser to the JavaParser gRPC server. This uses the Kotlin compiler's parser to process Kotlin files, and extract the same data that is extracted by the Java-oriented ClasspathParser.

This file currently handles detecting a main function, imported types and packages, and class declarations. It has partial coverage for exported types, and has a bunch of commented out code where I'm trying to figure out the best way to tackle detecting fully-qualified types and packages throughout the file. I also haven't yet added support for any annotation handling.

Questions for reviewers

Overall, WDYT? If people think this is worth adding, I'll make a series of smaller, cleaner PRs to actually get this done.
The plugin, its directives, packages, and classes often use the name java. By adding Kotlin, I'm somewhat implicitly changing the interpretation of this to something more like jvm. Any thoughts yay or nay on name changes? That's not an all or nothing thing. For example, maybe we rename the Gazelle Language to jvm, but keep the existing directive names to avoid breaking users. Or, we add new jvm directives, but continue to support the old java ones as well. Lots of other possibilities too.

FAQ
Why do this here when there is another Kotlin plugin?
A few reasons:

If you're using Kotlin + Java, and exclusively using Kotlin with the JVM, then I'm not sure that it actually makes sense to treat Kotlin as a separate language from Gazelle's perspective. That makes sense for two languages like protobuf and Java, which have a strictly one-way dependency graph. However, in my experience, Java and Kotlin code frequently depend on each other, sometimes from separate packages, and sometimes within the same package. If dependencies are only between packages, then I can see separate Gazelle plugins potentially working with Gazelle's cross-resolve feature, though this seems more intended for entirely separate resolution methods, not inter-dependent language plugins. Additionally, I don't see a good way to handle intra-package Java & Kotlin dependencies. If the Java plugin knows nothing about Kotlin, it will try to produce a java_library rule for the Java files, which will lack some Kotlin-specific information. A Kotlin plugin would then need to replace this rule with a Kotlin one, and extend it to handle the extra information from the Kotlin files. This seems a bit hacky and error prone. Conversely, adding Kotlin support directly to the Java plugin is turning out to be relatively painless (minus me trying to learn how to use the Kotlin parser).
There is an open support request for it.

Why add the KtParser to the same gRPC request handler, instead of a separate one for Kotlin?
I'd be happy to change this if others feel strongly, but we're ultimately trying to produce the exact same format of output data for Java and Kotlin, and merge them into a single set of data per package. We could either make two separate gRPC calls from Go land and then merge the data there, or make a single call and merge the data in Java land. That seemed like less boilerplate (defining new RPC requests) and less overhead (fewer network calls, even if they're to localhost).
Why add the KtParser to the same Java parsing server, instead of a separate server entirely?
See above, but also this would be even more resource overhead. No need to kick off multiple JVM processes if we can do it all in one.

I should note: I also haven't yet added support for tests


[Document]: Make the release note clearer

Clear and concise description of the problem
I think the current release information is messy, it does not play a role in letting users know what updates and fixes we have in the latest version，Current release note address：https://github.com/module-federation/universe/releases
Suggested solution
I was wondering if we could just include the repository's major pkg release records in the release, such as enhance, while the other pkg guides the user directly into the changelog of the specific pkg
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

@ScriptedAlchemy @brunocabral88 To do this, I want to turn off the behavior of balancing releases other than enhance to github releases. Other balance guides users to view the change log for any questions regarding this operation


Wrong key/secret doesn't exit; empty instances list would generate empty cfg and reload and ruin the env.

Good script. Thanks a lot first. We are planning to use it in production.
But I met the issues mentioned in the title. I'm not sure if this is by design, or a bug.

For example, you have a test environment, and a production one. After you test it, you run it on prod, but somehow you forget to update the key/secret, and boto.exception.EC2ResponseError is thrown, but since the program continues, a new conf with empty instance list would be generated and reloaded, and the environment won't work anymore.
Or if the instance list from a group is empty, it would still generate a new conf with empty instance list.

My five cents:

Maybe we can add a new option, like IS_PRODUCTION, which if is true, don't generate empty conf and definitely don't reload the empty conf.
Or add some checks in generate_haproxy_config to test if instances is empty or not. If empty, give some warnings and don't reload.
Multiple ways to improve this. But again, I'm not sure if this is a bug or by design. Maybe you want to generate a conf no matter there is instance or not.

If I were you, I would exit directly in case of EC2ResponseError, and in case of empty instances list, give warning and don't reload.
What do you think? If you agree but don't have time I can contribute a PR for this.

Hey thanks for your ideas! You're correct in that I don't really maintain this project anymore other than to support and merge PRs. Definitely feel free to fork and maintain something that works best for you in production. I'd be more than happy to review (and hopefully merge) any upstream contributions you're willing to provide! The most important thing is to not break backwards compatibility. I think a number of people do use this in production already and it would be bad for them to do a git pull and unwittingly get a version that causes an outage for them.
Thanks again for your interest!

I'll close this issue now and create a PR for you to review. Thanks!


Fix querydsl-docs dependencies

Fixes #1183

Yes, now that I see it, we indeed miss these artifacts now.


Ask for confirmation before deleting url

odo url delete should display what url will be deleted and ask user for confirmation similar to what we are doing when deleting component .

closed in #479


model explainibility

hi,
after training the model, how to explain the predictions, any example code for implementation of LIME or any other library to explain predictions for image classifier(pytorch)

Model explainability is in development. Will be released very soon


Validator Proxy /metagraph route

/metagraph route for validator proxy

Looks good!

Looks good.

Thanks - will merge once Eli confirms it works for him


Monitor NSM connection in TAPA to get latest local IPs

Description
The conduit handler in the TAPA is now monitoring the NSM connection to get the local IPs up to date. The local IPs can be updated by the proxy in case of a restart.
grpcKeepaliveTime has been increased to avoid grpc err: ENHANCE_YOUR_CALM:too_many_pings
Issue link
https://github.com/Nordix/Meridio/issues/383
https://github.com/Nordix/Meridio/issues/159
Checklist

Purpose

[x] Bug fix
[ ] New functionality
[ ] Documentation
[ ] Refactoring
[ ] CI

Test

[ ] Unit test
[x] E2E Test
[x] Tested manually

Introduce a breaking change

[ ] Yes (description required)
[x] No

Introduce changes in the Operator

[ ] Yes (description required)
[x] No

Tested and seemed okay.


Serialize the user avatar URL inline to the user JSON

This will save the frontend having to make another API call to get it for each user.
https://zooniverse.slack.com/archives/dev-frontend/p1487771756375998

closed by #2216


Component seems not emit events

I can't get any events from this component, I tried @input, @change and others, but no one returns me anything. How can I get the selected option in moment it's selected to call a method for it?

As mentioned here, the component doesn't emit any events at the moment.
Could you please elaborate on what you are trying to do?
If you are trying to retrieve the selected option value (option.value), you should pass a ref() inside the v-model.
Using v-model, you will receive the value property of your option.
Instead, if you want to get the entire option object, this could be done with a computed (assuming each option.value is unique, which should be):
import { computed, ref } from "vue";

const userOptions = [
  { label: "Alice", value: 1, username: "alice15" },
  { label: "Bob", value: 2, username: "bob01" },
  { label: "Charlie", value: 3, username: "charlie20" },
];

const selectedValue = ref<number>();
const activeOption = computed(() => userOptions.find((option) => option.value === selectedValue.value));

As mentioned here, the component doesn't emit any events at the moment.
Could you please elaborate on what you are trying to do?
If you are trying to retrieve the selected option value (option.value), you should pass a ref() inside the v-model.
Using v-model, you will receive the value property of your option.
Instead, if you want to get the entire option object, this could be done with a computed (assuming each option.value is unique, which should be):
import { computed, ref } from "vue";

const userOptions = [
  { label: "Alice", value: 1, username: "alice15" },
  { label: "Bob", value: 2, username: "bob01" },
  { label: "Charlie", value: 3, username: "charlie20" },
];

const selectedValue = ref<number>();
const activeOption = computed(() => userOptions.find((option) => option.value === selectedValue.value));

Thanks, it's work for me, but I have to avoid the pattern used in the project.

Hey @Iscrimou, I've opened a PR to introduce 2 new events (@option-selected, @option-deselected).
These events can cover edge-cases where relying on the v-model isn't sufficient.


sonic-pi: 4.0.3 -> 4.1.0

Description of changes
Bump Sonic Pi version to v4.1.0 and make the whitespace cleanups mentioned in https://github.com/NixOS/nixpkgs/pull/180732#discussion_r933852961
The new version seems to work fine in my brief testing
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 189012 run on x86_64-linux 1

1 package built:

sonic-pi


Digitalbitbox

Hi.
On Electron cash wallet setup when i choose to restore from my digitalbitbox hardware wallet, Electro cash wallet is not detecting it.

I'm sorry but Electron Cash does not support hardware wallets yet.

Ok.
Just btw https://digitalbitbox.com/faq it says that it does.


Improve Defaults of Server (API) Configuration

Problem statement
When developing a service using go-swagger, a server can be automatically generated. On top of that a server cli application can be created, but one can be manually created as well. Before one can call server.Serve() the api needs to be properly configured AND the server has to have the handler set. Currently that process is in my opinion quite error prone.
Steps to reproduce
Generate a server based on any valid OpenAPI spec and then create a server cli app more or less as follows:
package main

// imports...

func main() {
	swaggerSpec, err := loads.Analyzed(restapi.SwaggerJSON, "")
	if err != nil {
		log.Fatalln(err)
	}

	api := foo.NewFooAPI(swaggerSpec)

	server := restapi.NewServer(api)
	defer server.Shutdown()

	// calling any route will make the server app panic (and recover)
	// the reason being that server.ConfigureAPI() isn't called
	// instead the user choose to set the handler herself,
	// but forgot to set the producers and consumers among other things.

	server.SetHandler(api.Serve(nil))
	if err := server.Serve(); err != nil {
		log.Fatalln(err)
	}
}

When you use the generated server cli instead you'll have it calling server.ConfigureAPI(), making it not panic and instead return you the expected NotImplemented errors, when calling any route.
Proposed solution
While this work greats, it's not a good solution I think. The generated configureAPI function is pretty useless, which makes sense I suppose, knowing that it seems to be a file that is meant to be edited and thus being made useful.
Personally however I think we should rely on better defaults and I think I have a solution that doesn't break any code for people using older versions.

Make the API constructor have reasonable defaults.

For this we have to change a constructor such as this:
func NewFooAPI(spec *loads.Document) *FooAPI {
	return &FooAPI{
		handlers:        make(map[string]map[string]http.Handler),
		formats:         strfmt.Default,
		defaultConsumes: "application/json",
		defaultProduces: "application/json",
		ServerShutdown:  func() {},
		spec:            spec,
	}
}

to:
func NewFooAPI(spec *loads.Document) * FooAPI {
	return & FooAPI{
		handlers:        make(map[string]map[string]http.Handler),
		formats:         strfmt.Default,
		defaultConsumes: "application/json",
		defaultProduces: "application/json",
		ServerShutdown:  func() {},
		// basically giving the `ServerError`, `producers`
		// and `consumers` a decent default
		ServeError:      errors.ServerError,
		JSONConsumer:    runtime.JSONConsumer(),
		JSONProducer:    runtime.JSONProducer(),
		TxtProducer:     runtime.TextProducer(),
		spec:            spec,
	}
}

Doing this makes it so that the API as it is just works. On top of that we could also make all the handlers by default NotImplementedHandlers, such that the simple example given above just works, without any weird unexpected panics.
Another idea would be that the configureAPI function wouldn't just stupidly override all handlers, and instead first check if the handlers are still nil. And only override a handler if it is indeed still nil.
Lastly, one could even forget to set the handler (e.g. via server.SetHandler(api.Serve(nil))) and not get a panic or fatal error at start up to warn about this. Instead no routes will be available and everything will return a 404. These errors might tip of the user, but perhaps explicitly shouting to the user about this problem at start-up of the cmd app might be more helpful and beginner-friendly?

@casualjim you have any opinions/feedback on this issue?

yes can be a good idea to add to the codegenerator


feat: convert current layouts to pane-based layouts

I created a management command convertndslayoutstopanes that... converts NDS-style paradigm layouts (i.e., the ones we're using right now) and converts them to the pane-based syntax (see: #167).
Although I think of the management command as throwaway code, I want to keep and build on the new classes introduced in panes.py. Please scrutinize!
Addresses #582... however converted layouts will need to be manually validated.

Codecov Report

Merging #762 (6450730) into master (3821793) will decrease coverage by 2.04%.
The diff coverage is 42.22%.

@@            Coverage Diff             @@
##           master     #762      +/-   ##
==========================================
- Coverage   82.28%   80.24%   -2.05%
==========================================
  Files          92       94       +2
  Lines        3269     3447     +178
  Branches      483      510      +27
==========================================
+ Hits         2690     2766      +76
- Misses        487      587     +100
- Partials       92       94       +2

Impacted Files
Coverage Δ

CreeDictionary/CreeDictionary/paradigm/filler.py
89.66% <0.00%> (-0.75%)
:arrow_down:

...ictionary/management/commands/convertndstopanes.py
26.31% <26.31%> (ø)

CreeDictionary/CreeDictionary/paradigm/panes.py
62.96% <62.96%> (ø)

...ranslate/management/commands/translatewordforms.py
73.17% <0.00%> (ø)

Continue to review full report at Codecov.

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

@aarppe FYI, here are the logs about the English label to FST-style label process:
No English label for ('Def',)
No English label for ('Der/Com',)
No English label for ('Der/X',)
No English label for ('Err/Orth',)
No English label for ('Foc',)
No English label for ('NA-?',)
No English label for ('NDA-x',)
No English label for ('NDI-?',)
No English label for ('NDI-x',)
No English label for ('NI-?',)
No English label for ('PV',)
No English label for ('Rel',)
Ambiguous label: s/he/they (further) → him/her/them
   => maps to [('5Sg/Pl', '3PlO'), ('5Sg/Pl', '4Sg/PlO')]
Ambiguous label: when/if something happens
   => maps to [('Cond',), ('Fut', 'Cond')]
Ambiguous label: later
   => maps to [('Del',), ('PV/masta',)]
Ambiguous label: like: awa, ôma
   => maps to [('Dem',), ('Prox',)]
Ambiguous label: like: pê-
   => maps to [('IPV',), ('Ipv',)]
Ambiguous label: almost
   => maps to [('PV/ami',), ('PV/kekaci',)]
Ambiguous label: half
   => maps to [('PV/apihta',), ('PV/apihtawi',)]
Ambiguous label: small
   => maps to [('PV/apisisi',), ('PV/piwi',)]
Ambiguous label: would, ought to; likely to
   => maps to [('PV/kah',), ('PV/tah',)]
Ambiguous label: grammatical preverb; future; defines a conjunct clause
   => maps to [('PV/kika',), ('PV/kiyi',)]
Ambiguous label: able; good at, competent, practised, experienced, skillful at, expert at, known as one who does s.t. habitually; well
   => maps to [('PV/nahta',), ('PV/nihta',)]
Ambiguous label: pain
   => maps to [('PV/tewi',), ('PV/teyi',)]
Ambiguous label: your and our
   => maps to [('Px12Pl',), ('Px21Pl',)]
Ambiguous label: like: nipâw
   => maps to [('VAI-1',), ('VAI-v',)]

I don't really think the ambiguous labels for preverbs really matters but things like "s/he/they (further) → him/her/them" do matter!

@eddieantonio Yes, the obviatives cases were the ones that matter the most wrt the new panes and the relabeling scheme. Also, we will have to think what sorts of labels we present for the pronouns, in particular to resolve the ambiguity and have distinct plain nêhiyawêwin labels for the various FST-style labels (Dem vs. Prox), but I'll probably sleep on it, having now first fixed the verb labels, hopefully in full.

All the other cases above do not need relabeling in my judgement - their fall-back categories or tentative FST feature tags that were eventually not used, or then various preverbs that happen to have the same English translation. So we could close this issue.


Don't update renovate PRs via mergify

Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

Because renovate doesn't like anyone messing with its PRs. ;) See for example https://github.com/nmshd/backbone/pull/985#issuecomment-2545041688
I assume it does the update own its own.


[Feature request]: Two new options

What do you need?
--export, -e          export as file extension (.txt, .md, .py, .ps1, etc.)
--export_setup, -xp   choose a default file extension for the export, -e option
I propose this improvement for our output to append data (i.e. text/code) into new/existing files.
The shortcuts, -e and -xp, are arbitrary and serve as examples; however, the features could improve code development and document creation.
It might be overkill because https://github.com/danielmiessler/fabric?tab=readme-ov-file#save

Hi, you could just use "> output.md" to redirect the output to a file.


Music is not playing

I think there is an error in the player.js line number 228 please solve this problem.

It is showing error 403 when I click on the play button or any of the buttons in the player in the footer-components


MRG: Fix pytest test discovery for MNE-Python devel versions

This should fix things for the test adapter in VS Code.
cc @cbrnr

@larsoner Im currently afk, feel free to commit your proposed change and merge if you want


Build custom docker image

I would like to build a "standard" docker image for IdentityServer4.LdapExtension.
This would ease the entry barrier to participate in development. Potential develop doesn't have to configure there own docker image.
any thoughts?

Yes, it's not something too difficult to do. But you might have to have a samba/ldap/similar on the same image which would not be "standard" for docker image which you should have only 1 process running. That being said, it's feasible.
For example, if you have a docker compose, you could have Redis+LDAP+IS4 running and then you could tests.
(I will come back eventually to work on my projects, i've been quite busy in the last months)


Fix TUS upload with POST and payload

The JS lib is not sending a zero offset during upload, it is likely
optional. This fix makes it default to 0 when no Upload-Offset header is
set.
Also fixed returned header to be set on the correct response object, the
main one.
@butonic

Fixes https://github.com/cs3org/reva/issues/710
Tested using https://github.com/owncloud/phoenix/pull/3436


GitHub Actions

This PR calls GitHub's free CI service whenever a push or a pull request is made. It additionally makes build artifacts available to download and take for a spin without ever having to set up a development environment on one's local machine.
Does it look appropriate?

Actually, is it possible to run this on tags and to upload the bundle to the release artifacts?
I've only ever used that functionality with electron-builder so I'm not sure how it works for regular node modules. 😅

is it possible to run this on tags and to upload the bundle to the release artifacts

Preliminarily, it looks like that's not as trivial as one would like it to be: there are some 3rd-party scripts to do so, but it's not well-integrated…
Aha, I seem to have found this: https://github.com/softprops/action-gh-release

A common case for GitHub releases is to upload your binary after its been validated and packaged. Use the with.files input to declare a newline-delimited list of glob expressions matching the files you wish to upload to GitHub releases. If you'd like you can just list the files by name directly.

I haven't committed support for it just yet, but it looks like it'd be as simple as on: release
So, in any case, it should only formally attach artifacts to Release-tagged commits; but do you want me to have it build stuff for pushes and PRs anyway, for general CI purposes?

It looks like it will require some sort of token, once accepted:

The following are required as step.env keys:
… GITHUB_TOKEN

Hmm, actually, upon further inspection:

That Action can create releases, and attach files to those it is creating.

Actions, generally, can take action based off the creation of a Release (on: release), though it's not clear whether they can attach files to existing (or user-created) Releases.

It looks like, to leverage that Action to attach files to Releases automatically, you would also have to entrust it with the creation of Releases, which would probably entail having a separate release branch that you push to (which may be a nontrivial change to your workflow.)
I will have to do a bit more research into the options for automatically attaching build artifacts to Releases. (Though, as currently drafted, this PR would enable "simply" downloading the Artifact associated with a commit and attaching it to its associated Release manually.)

@JamesTheAwesomeDude I can supply the GH token for this, sure.

but do you want me to have it build stuff for pushes and PRs anyway, for general CI purposes?

Your call on what you think would be useful for folks. 😁

It looks like, to leverage that Action to attach files to Releases automatically, you would also have to entrust it with the creation of Releases,

Can it detect new tags to create releases? That's what electron-builder does in Agregore
Also, if you're not interested in messing around with the release stuff I'm okay with leaving it as a TODO and doing the PR based build artifact thing in the meantime. There's no pressure either way of course. 😁


ci: 🎡 update docker manifest images for ownership

Closed to fix in branch under this remote. While working on this Tim helped me discover he was able to issue commits directly to the branch on my repository even when he has no access rights to that repo. The presumption is that GitHub has made that use case possible because I've issued a pull request against the upstream. However, I believe this to be unexpected behavior. Nevertheless, we learned and I've pushed up a different branch on this remote and submitted a new PR for this work.

Closed to fix in branch under this remote. While working on this Tim helped me discover he was able to issue commits directly to the branch on my repository even when he has no access rights to that repo. The presumption is that GitHub has made that use case possible because I've issued a pull request against the upstream. However, I believe this to be unexpected behavior. Nevertheless, I've pushed up a different branch on this remote and submitted a new PR.

There is an option "allow edits from maintainers", where if disabled will prevent maintainers to edit the PR and the fork branch if it is not of this repo.

There is an option "allow edits from maintainers", where if disabled will prevent maintainers to edit the PR and the fork branch if it is not of this repo.

I thought that meant to the text, not the code! 🤣 So now I know. Thanks @rht.


article tag

Email
can you have something else so its valid html?

#21 proposed fix

Can you explain what problem it is you're trying to fix? Thanks!

Article tag has to have a h1 or something to be valid

Ah! I don't know why I used article -- I think I was still getting started with styled-components. I've merged your fix and pushed out 4.2.1. Thank you!


i wonder how long does it take for the web server to be fully maintained?

i wonder how long does it take for the web server to be fully maintained?

Hi,
Thanks for your interest. We will be back very soon, today or tomorrow at the lastest. New sequences are being added. Thanks for your patience.
Best regards,
Alejandra

Thank you for your reply

Thank you for your reply

Hi! The webserver is available again now.
Bests,
Alejandra

I wonder why I am unable to access this website

Hi,
You should clear cookies and data site to visualize the website.
Bests,
Alejandra


Update the events, used with scripting, to use lower-case names and avoid using DOM events internally in the viewer + misc scripting-related tweaks

Please refer to the individual commit messages for additional information.
Also, ignoring white-space changes when viewing the larger patches should be helpful.

/botio unittest

/botio integrationtest

/botio integrationtest

/botio test

/botio integrationtest

The failure in integration test is because the open action is executed after trying to get the focused element.
I'm figuring out a way to fix it.

/botio integrationtest

@Snuffleupagus I think this patch fix the issue: https://github.com/mozilla/pdf.js/pull/12755

/botio integrationtest

/botio integrationtest

/botio integrationtest

/botio integrationtest

/botio test

/botio-linux preview

Thank you for improving the overall consistency here!


wire up the checkbox - "allow others to see my profile" on the profile

this checkbox should tie into a boolean field "Public" in Firestore

I made a PR for this, still verifying that it works correctly (will document verification progress in the PR) https://github.com/codeforboston/advocacy-maps/pull/344


Add support for query params in S3 key names

AWS supports ? in key names however the way we were previously encoding
the URL to be signed caused these query params to be dropped.
For more info on what S3 supports in keys see:
http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html#object-keys

@bruce @benwilson512 Are you guys open to this?


add support for retries

in some scenarios, the connection to openwhisk may be unreliable. for example, certain versions of nodejs on linux yield routine ETIMEDOUT or ESOCKETTIMEOUT or ECONNRESET (especially the last one); all of these errors are transient, and can be addressed via retry.
i propose that we can support retries with only a few lines of code change, e.g. by wrapping the rp call in client.request with a promise-retry. PR pending

Implementing retry logic for connection errors is not normally the responsibility of the client library. This is not standard behaviour for client libraries. Responsibility for failure recovery errors should be handled by the client application.

possibly, but every single user of this npm will face the issue, when talking on linux to ibm cloud.


'-e' invalid args in requirements.txt file

Can`t use 'pip install -r requirements.txt'
the reason is that,
in line 170, 171, there are wrong argument '-e'.
Please to delete them !
Thank you again :))

I think the author gave requirements.txt just for reference.  :)

Okay, Thanks your comment :)

I just simply kip all the packages that have installation error. You can try my python script, it works for me!
import sys
import subprocess
with open('requirements.txt') as f:
packages = f.readlines()
for package in packages:
package = package.strip()
if package:
try:
print(f"Installing {package}...")
subprocess.check_call([sys.executable, '-m', 'pip', 'install', package])
except subprocess.CalledProcessError:
print(f"Skipping {package} due to an installation error.")


libsForQt5.phonon: 4.9.1 -> 4.10.0

Semi-automatic update generated by https://github.com/ryantm/nix-update tools.
This update was made based on information from https://repology.org/metapackage/phonon-qt5/versions.
These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 4.10.0 with grep in /nix/store/lm29qmazpjjlsd9hcirkmnkivray2b9p-phonon-qt5-4.10.0
found 4.10.0 in filename of file in /nix/store/lm29qmazpjjlsd9hcirkmnkivray2b9p-phonon-qt5-4.10.0
directory tree listing: https://gist.github.com/fd63e321fc3545dfb6376981138d6246

cc @ttuegel for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: libsForQt5.phonon
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: libsForQt5.phonon
Partial log (click to expand)
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/6viabd9x8wl35v3lwq5f0k2jpdjp5b7p-phonon-qt5-4.10.0/lib
patching script interpreter paths in /nix/store/6viabd9x8wl35v3lwq5f0k2jpdjp5b7p-phonon-qt5-4.10.0
checking for references to /build in /nix/store/6viabd9x8wl35v3lwq5f0k2jpdjp5b7p-phonon-qt5-4.10.0...
shrinking RPATHs of ELF executables and libraries in /nix/store/64174899j99a86cq4m81c90b9grfcrkf-phonon-qt5-4.10.0-dev
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/64174899j99a86cq4m81c90b9grfcrkf-phonon-qt5-4.10.0-dev/lib
patching script interpreter paths in /nix/store/64174899j99a86cq4m81c90b9grfcrkf-phonon-qt5-4.10.0-dev
checking for references to /build in /nix/store/64174899j99a86cq4m81c90b9grfcrkf-phonon-qt5-4.10.0-dev...
postPatchMkspecs

Failure on aarch64-linux (full log)
Attempted: libsForQt5.phonon
Partial log (click to expand)
cannot build derivation '/nix/store/2r92rl114mpx2cwcpjphvx3d4vv36y6b-at-spi2-atk-2.26.1.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/dh3x5ya059a03fjyc1qijwgp5bsi1c4a-graphviz-2.40.1.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/99rw5b979vj79mfpvnvi6arv5w8f35k3-gtk+3-3.22.29.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/1fw6apsy8z38s3ryvyb15lb8rjg4adhg-vala-0.40.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/2kzdj7svhi1mpzvi8l7ak9yzplpk9jd6-dconf-0.28.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/2zj2jz8fxbv9f06b80galjzd2i2r49hi-qtbase-5.10.1.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/xx4d287dmqafjwzyl138g21s93spch1w-hook.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/3h2fnxiv1x78cdp9bqbiyra602s5w0xp-qttools-5.10.1.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/gzfd7pmyh70wx7s1b6cx45q97ydcya4k-phonon-qt5-4.10.0.drv': 3 dependencies couldn't be built
error: build of '/nix/store/gzfd7pmyh70wx7s1b6cx45q97ydcya4k-phonon-qt5-4.10.0.drv' failed

I want to check for backend updates before we merge this.

superseded by #41095


Build Window (and ChildWindow) of Ui

I've, about twice, started trying to make a PR for #454 before realizing how many things there was, before panicing and ctrl+zing the changes...
Thus I've stuck to just the main one, imgui::Window as it's commonly used, and most likely the first thing a new user will interact with (e.g it's in the README example)
I think this is a good change, it's less typing, and more importantly makes thing more consistent so all methods can (eventually) be found via auto-complete like ui.something (e.g I missed imgui::ColorButton when writing the example of #519 because I couldn't find it on the Ui doc page :roll_eyes: )
This is obvious a fairly big breaking change, but.. now seems to be the time for such things! The actual changes should all be pretty simple search-and-replace things s/Window::new(/ui.window(/ and s/.build(ui, /.build(/
I also did same change for ChildWindow, but also made it it's ID handling consistent with Window, as ChildWindow was about the only thing still using the explicit imgui::Id type (now only Ui::push_id is.. and I'm tempted to make that take an ~ImStr~ str also)

Oh I did try and make this backwards compatible, but I couldn't see a nice way of doing this
Problem being:

Old code did: imgui::Window::new("Example").begin(ui) (or build)
New code ui.window("Example") returns imgui::Window,  so .begin() (or build) must take ui arg

Only solutions to that I can think of are either:

Different named methods like ui.window("Example").begin2() (but couldn't think of a non-terrible name)
ui.window returns a different type (but that would mean duplicating all the methods on imgui::Window)

This is a good PR and I like this change. However, I think we should hold off till 0.8.0 is released. It does break code, and just going through a large work project and adapting it to the main branch took me about 2 hours. the vast majority of that was fixing im_str calls, but still, I think limiting that at least somewhat for now would be appreciated.
I'd like 0.9.0 to be virtually entirely changes like this (and I'd also like us to experiment a bit, maybe using begin_window and begin_window_with(name, big_data_blob_instead_of_params)).
What do you think? If you think I'm being overly cautious here, that'd be understandable

Yep makes sense! 0.8 already looks like it has enough excitement for one release :partying_face:

rebase and let's do it?

Done :runner: (well merged instead of rebased as there was a bunch of conflicts which were easier to deal with that way)
The new table bindings use the Id type which is now otherwise entirely unused. I've not used the table API at all, so I couldn't work out what the user_id does or how it would be used, so I've currently just shoved the definition of Id inside tables.rs and left it as is.. but feel like it could probably be handled differently?

Yeah user_id basically let's you use a second, presumably cheap integer, user id for each column of your table. That shows up later in Sorting Operations. Possibly if the table is made completely dynamically, it could be your only way of identifying each column.
The Id struct is used in push_id. Why'd that get changed in this PR? I think it's not well implemented (I think as a general rule, doing Into<MyOwnType> in any crate is a bad idea), but I think the functionality is useful.
I use its functionality myself, for example, in various iterators where I'm generating label names dynamically. For example:
let my_values = ["hello", "hello", "goodbye"];

for (i, v) in my_values.iter().enumerate() {
    // just doing this here will bork, since we'll have two labels of "hello"
    // ui.button(v);

   // this fella works, but allocates a whole new string per button. wasteful
   // ui.button(format!("{}##{}", v, i));

   let t = ui.push_id(i);
   ui.button(v); // this guy works now, because we've incremented the ID stack, and imgui actually cares about the ENTIRE stack state, not just the current id
   drop(t);
}

so I'd not want to accept changing push_id to not accept integers, which are very useful

Ahhh I see! I couldn't see any uses of push_id in the repo and I missed the Into<Id> for integer as a way of actually using Id as a non-string (and I'd only used push_id in cases where I could do ui.push_id(an_existing_str), but makes perfect sense to accept an integer also)
I think I'll reopen the PR from a new branch with the ui.window changes reapplied (and maybe include some better docs for push_id instead of deleting it :sweat_smile: )

Created #537


How to set mintstick.py to tiling

I was trying to set the minstick to tiling rather than floating.
By default it wants to be floating.
I would think this would work. 6th variable to 0 means tiling - right?
static const Rule rules[] = {     /* xprop(1):      *	WM_CLASS(STRING) = instance, class      *	WM_NAME(STRING) = title      */     /* class      instance    title       tags mask     iscentered   isfloating   monitor */     { "Gimp",     NULL,       NULL,       0,            0,           0,           -1 },     { "Firefox",  NULL,       NULL,       1 << 8,       0,           0,           -1 },     { "eww",      NULL,       NULL,       0,            0,           1,           -1 },     { "mintstick",      NULL,       NULL,       0,            0,           1,           -1 }, };
Xprop shows Mintstick.py and mintstick.py in the class. I have tried that and mintstick and Mintstick.
It will not tile whatever I put in there.
Any ideas?
Extra image because the layout is rubbish on github

Changing floating from 1 to 0 does not change the behavior.

tiling is the default behaviour, just remove this line

without that line it will float

without that line it will float

hmm what is ministick actually? :thinking:

mintstick - burns isos on a usb stick
never has failed in the last 5 years
source - https://github.com/linuxmint/mintstick
installed from AUR
https://aur.archlinux.org/packages/mintstick-git

Use dd to burn isos and you won't have to worry about any of this :smile:.

Switching to tiling using the provided keybinding also doesn't seem to work. Maybe have a look at Mintstick's source and change what forces this behaviour. But it probably won't look good on tiling tbh.

I have been on Leftwm since February 2022.
I know it is not fair to compare twms as they are not the same. Period.
This is how it looks on Leftwm - mintstick is tiled automatically.

And here are the references in the configuration.

And that is why I asked if I can kill an app with the right mouse click - in polybar I can do that

@arcolinuxz does minstick app have any wmclass?

result of xprop
_MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0
_NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_NORMAL
_NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 73400329, 73400330
_NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x4600008
WM_CLIENT_LEADER(WINDOW): window id # 0x4600001
_NET_WM_PID(CARDINAL) = 455966
WM_LOCALE_NAME(STRING) = "en_US.UTF-8"
WM_CLIENT_MACHINE(STRING) = "isobuilder"
WM_NORMAL_HINTS(WM_SIZE_HINTS):
program specified location: 0, 0
program specified minimum size: 348 by 225
program specified maximum size: 348 by 225
program specified base size: 0 by 0
window gravity: NorthWest
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST
WM_CLASS(STRING) = "mintstick.py", "Mintstick.py"
WM_ICON_NAME(STRING) = "USB Image Writer"
_NET_WM_ICON_NAME(UTF8_STRING) = "USB Image Writer"
WM_NAME(STRING) = "USB Image Writer"
_NET_WM_NAME(UTF8_STRING) = "USB Image Writer"
[erik@isobuilder ~]$

@arcolinuxz try xprop | grep WM_CLASS
and show the output

You get the line above that is in bold...

oh oops, i missed it

The answer lies in the xprop output.
program specified minimum size: 348 by 225
program specified maximum size: 348 by 225

In dwm if a program's minimum size is the same as the program's maximum size then that means that the window has a fixed size which in turn means that the window should not be resized.
dwm respects those size requirements which is why the window always opens as floating. You won't get around this without tinkering.
For reference we have that the manage function calls updatesizehints which towards the end sets the isfixed flag for the client:
c->isfixed = (c->maxw && c->maxh && c->maxw == c->minw && c->maxh == c->minh);

Then later in manage we have:
    if (!c->isfloating)
        c->isfloating = c->oldstate = trans != None || c->isfixed;

If you wanted to remove this feature then you'd probably want to remove the line from updatesizehints which sets the isfixed flag in the first place. You may of course end up with odd behaviour in other programs that expects to have a fixed size.

I have lived it with it since February 2023
I think I can live with it till the day I die
Mintstick will stay floating and that is just fine with me
you can close this


Typo in the ReadMe

Hello, I am interested in your works and try to reproduce your project but I found some typo in ReadMe.
https://github.com/ccr-cheng/InfGCN-pytorch/blame/dfe402bd2798c7482a75e3e89686c0987be427db/README.md#L71
https://github.com/ccr-cheng/InfGCN-pytorch/blame/dfe402bd2798c7482a75e3e89686c0987be427db/README.md#L79
In the training and evaluation command code, I think main.py is missing
Change
python configs/qm9.yml --savename test

to
python main.py configs/qm9.yml --savename test

may help.
Thank you.

Thank you very much for pointing this out! I have fixed this typo in the readme.
Chaoran


Add codebase RESt API

Codebase is tied to a Space. Each codebase represents some
form of repository.
Provide edit/create API via Che-Starter targeting the tenant services.
Che-Starter interaction is undertested. Needs semi-stable api to produce a api recording.

Codecov Report

Merging #1021 into master will decrease coverage by 1.48%.
The diff coverage is 31.35%.

@@            Coverage Diff             @@
##           master    #1021      +/-   ##
==========================================
- Coverage   64.76%   63.27%   -1.49%
==========================================
  Files          96       98       +2
  Lines        7963     8367     +404
==========================================
+ Hits         5157     5294     +137
- Misses       2292     2541     +249
- Partials      514      532      +18

Impacted Files
Coverage Δ

log/log.go
53.78% <0%> (-0.83%)
:arrow_down:

main.go
0% <0%> (ø)
:arrow_up:

migration/migration.go
50.62% <100%> (+0.12%)
:arrow_up:

controller/space.go
72.63% <100%> (+0.89%)
:arrow_up:

controller/codebase.go
16.73% <16.73%> (ø)

codebase/codebase.go
63.2% <49.35%> (-22.22%)
:arrow_down:

controller/space_codebases.go
72.54% <72.54%> (ø)

remoteworkitem/scheduler.go
60.97% <0%> (+7.31%)
:arrow_up:

... and 1 more

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 55adf0c...ab683be. Read the comment docs.


Missing "Installation" chapter in the doc

This is nothing, really, but it is annoying when you don't see immediately how to install the package.
See an example here: https://github.com/dburles/meteor-collection-helpers

+1


RSDK-3052, RSDK-3053, RSDK-3417, RSDK-3884 Create Intel RealSense C++ Module

This is a modularization of the C++ server originally from github.com/viamrobotics/camera-servers
You can use the README to install the module
Manual tests show that it has the same speed/FPS as the remote server,
i.e. at 640 x 480 resolution, it performs
23 FPS for depth using image/vnd.viam.dep
60 FPS for color using image/jpeg
It also has the option to allow the setting of the endian-ness of the raw depth data in its config.
It also automatically reconnects if the intel realsense device gets disconnected and reconnected.
The get_images method has also been implemented.
Two other features for future PRs are:

~the addition of the get_images method to return both color and depth at the same time.~
the get_pointclouds method to allow returning a PCD.

Overall, this looks good. I think it would be much easier to review though if it could be redone in a way that made the PR a delta above the old grpc server, because then it would be much much easier to know where to spend time reviewing, and where to just accept that the old logic was "good enough" for a v1. I think it might not be that hard to do.

Well, I sort of got tunnel vision on the C++ part and forgot to take a closer look at the supporting context. Let me take a quick look through that now

@bhaney - I left a bunch of comments, but I'd classify almost all of them as optional improvements to take or leave as you see fit. I would however like to see frameLoop and on_device_reconnect restored to their original sequencing in the file so that I can see what really changed there. I think you can resolve any circularity by just writing prototypes for the functions at issue at the beginning of the unnamed namespace. If you can do that I think I can take a quick final look and then approve this, and you can act or not on my suggestions.


Confusing model versions

Hello,
Thank you for developing this package. I had a question concerning the different versions of the EC-GEM E. coli model, as I would like to use the E. coli model for some analyses.
In the model folder, there are two files: 'eciML1515.json' and 'iML1515_irr_enz_constraint_adj.json'. Based on the suppl data from your paper I can deduce that eciML1515.json is the final model version (since it has a growth rate 0.68 h-1).
However, it is confusing that scripts 03 and 04 respectively create and use the iML1515_irr_enz_constraint_adj model, while script 05 uses the eciML1515. Why are the analyses in script 04 performed with the iML1515_irr_enz_constraint_adj model? Could it perhaps be made more explicit which model file is final (and the correct one to use) in the Readme?

I apologize for the confusion. If you're using it for biological simulations, please use 'eciML1515.json'. This model represents the final E. coli model from our published paper (http://dx.doi.org/10.3390/biom12010065), incorporating manual corrections based on experimental results. 'iML1515_irr_enz_constraint_adj.json' is an enzymatic constrained model, built automatically using notebooks 02 and 03 with ECMpy2.0. Notebook 4 involves a general analysis process for enzyme-constrained models, so both 'eciML1515.json' and 'iML1515_irr_enz_constraint_adj.json' can be used. Notebook 05 applies this enzyme-constrained model to real metabolic engineering modifications, hence utilizing the manually corrected model rather than the automatically generated one.

That's clear, thank you!


Editing the Initialized status of a MemoryBlock bytemaped

hi.
let says i have this memory block named '.intercall' in the memory Map:

for somme reason i  used a script to change the bytes ie:
MemoryBlock block ...
block.putBytes(block.getStart(), aByteArray);

Question how do i change is Initialized checkbox ? The User interface didn't allow to tick checkbox.
and the api dont have a method.
this is issue seems to be only related to Byte Mapped type of block
because i later use a script :
if(block.isInitialized()) {
//do stuff
}

Also is there a filter text filed to search for a specific block by name . in the case where there is over 40 blocks of memory ?

You can use Memory.convertToInitialized(MemoryBlock, byte) but I'm not exactly sure you would want to do this for a byte mapped block. When you utilized MemoryBlock.putBytes did you do so on the .intercall block or the block containing what .intercall is mapped to? I would expect some sort of exception from attempting to write data into a byte mapped block and a MemoryAccessException is supposed to be thrown by MemoryBlock.putBytes if the block is uninitialized.

i dont remember witch block i overiten. Either source or the bytemapped one...
solved by replacing (block.isInitialized()) with (block.isInitialized()|| block.isMapped())


Unexpected crash: dts-gen -m aws-amplify-react-native: "SyntaxError: Cannot use import statement outside a module"

> dts-gen -m aws-amplify-react-native
Unexpected crash! Please log a bug with the commandline you specified.
C:\...\node_modules\aws-amplify-react-native\dist\index.js:14
import { default as AmplifyCore, I18n } from 'aws-amplify';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at wrapSafe (internal/modules/cjs/loader.js:1067:16)
    at Module._compile (internal/modules/cjs/loader.js:1115:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Module.require (internal/modules/cjs/loader.js:1040:19)
    at require (internal/modules/cjs/helpers.js:72:18)
    at Object.<anonymous> (C:\Users\...\AppData\Roaming\npm\node_modules\dts-gen\bin\lib\run.js:58:67)
    at Module._compile (internal/modules/cjs/loader.js:1151:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1171:10)

The problem is require doesn't support ES6 modules.
https://github.com/microsoft/dts-gen/blob/bff184105c86a8f7f9e2f4f9a424775cdd4f7c4c/lib/run.ts#L77
The solution in https://github.com/microsoft/dts-gen/issues/42#issuecomment-414038955 uses @babel/register:

The require hook will bind itself to node's require and automatically compile files on the fly.

Run npm install @babel/core @babel/register --save-dev
Add to the top of lib/run.js

require("@babel/register")({
  ignore: [],
  presets: ["INSERT YOUR PRESET HERE"]
});

I used module:metro-react-native-babel-preset as my preset.

Run npm run build
Run npm link
Run dts-gen -m aws-amplify-react-native

However, it kept on wanting me to install more and more packages, aws-amplify-react-native -> aws-amplify -> react-native.
Finally, it crashed with an Invariant Violation: __fbBatchedBridgeConfig is not set, cannot invoke native modules    at invariant error.
This seems to be too complex a use-case for dts-gen so I'm going to close this issue.


angleRange in HDrawablePool does not exist

When opening demo HCircleLayout_007 I get the following error: The function "angleRange(float, float) does not exist . I checked in the javadoc reference and indeed there are not any functions with that name.
Using latest version of HYPE and processing 3.3.6

https://github.com/hype/HYPE_Processing/tree/lib_staging/examples/HCircleLayout
only has 6 examples ?

True, however in the distribution .zip https://github.com/hype/HYPE_Processing/blob/lib_staging/distribution/HYPE.zip inside the folder examples there is a _007 file.


In Windows, error when using sane's local ember-cli

When running sane new <projectname>, if the globally installed version of ember-cli is different from that in sane, a choice is given to the user of which one to use.  Unfortunately, on Windows it is impossible to use the locally installed version because there is no ember.cmd file that Windows can run.  NPM adds that file upon global installation.

+1 I'm having this issue on Windows as well. This cause the "tooling is installing packages via npm" to continue indefinitely after the "sails.cmd cannot be found. Error code 1." and it manages to generate a folder structure so long that you can't physically delete it on windows (didn't think that was possible) without doing some rm -rf magic with some linux based tools.
Luckily I use a lot of linux based stuff on my machine so it wasn't a problem, but I sure hope this gets fixed soon.

I forgot to mention this happens whether you use the local version or sane version so it may be another issue.

Do you have sails.js installed globally? I think you must, just checking to be sure.  It seems to be something to do with Sails or ember-generate which is failing. I'll try to reproduce the error tomorrow.  Are you running the official SANE 0.0.24 release? (as opposed to cloning and linking)

@brandensilva, I am not able to reproduce the problem you describe here.  Can you give some more information about what versions of SANE, Sails, and Node you're using?

I'll do a bit more testing on my end and get back to you. I tested sane
0.24 on another machine and had it working so its likely something isolated
on my main machine.
On Sat, Apr 4, 2015, 7:36 AM Ian VanSchooten<EMAIL_ADDRESS>wrote:

@brandensilva https://github.com/brandensilva, I am not able to
reproduce the problem you describe here. Can you give some more information
about what versions of SANE, Sails, and Node you're using?
—
Reply to this email directly or view it on GitHub
https://github.com/artificialio/sane/issues/128#issuecomment-89578935.

OK I'm going to close this for now then.  If you do some more research and find that this is in fact a SANE bug, please reopen it.

Actually, the original problem is still valid.  It should be fixed when we implement a more robust way of resolving the ember binary.


automatically download virtualbox oracle extpack if allowUnfree = true

Issue description
If would be nice for the Virtualbox package to automatically download and install the Oracle Extension pack if nixpkgs.config.allowUnfree is set to true.
That is to say, with the following settings in /etc/nixos/configuration.nix, the Oracle Virtualbox Extension pack should be downloaded and installed automatically:
virtualisation.virtualbox.host.enable = true;
nixpkgs.config.virtualbox.enableExtensionPack = true;
nixpkgs.config.allowUnfree = true;

Currently, with the above options set, nixos-rebuild build produces the following message and fails to build the virtualbox package:
In order to use the extension pack, you need to comply with the VirtualBox Personal Use
and Evaluation License (PUEL) available at:

https://www.virtualbox.org/wiki/VirtualBox_PUEL

Once you have read and if you agree with the license, please use the
following command and re-run the installation:

nix-prefetch-url http://download.virtualbox.org/virtualbox/5.1.26/Oracle_VM_VirtualBox_Extension_Pack-5.1.26-117224.vbox-extpack

It looks like the maintainers of the virtualbox package are @flokli and @sanders. (I'm not sure if it is appropriate to ping maintainers like this, or if it will happen automatically.)
Technical details

system: "x86_64-linux"
host os: Linux 4.9.78, NixOS, 17.09.2875.c2b668ee726 (Hummingbird)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.16
channels(root): "nixos-17.09.2875.c2b668ee726"
channels(illabout): ""
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Often the license does not permit us to automatically download such files. In this case, the license at

https://www.virtualbox.org/wiki/VirtualBox_PUEL

states

PLEASE READ THE FOLLOWING ORACLE VM VIRTUALBOX EXTENSION PACK PERSONAL USE AND EVALUATION LICENSE CAREFULLY BEFORE DOWNLOADING OR USING THE ORACLE SOFTWARE. THESE TERMS AND CONDITIONS CONSTITUTE A LEGAL AGREEMENT BETWEEN YOU AND ORACLE.

If we provide the means to automatically download the file, then at no point the user is presented with the fact that they should agree to the license first. Therefore, we should not automate this.
IANAL, but one solution that might be possible is a configuration flag for accepting the license which has a description that includes this line.

It looks like the maintainers of the virtualbox package are @flokli and @sanders. (I'm not sure if it is appropriate to ping maintainers like this, or if it will happen automatically.)

That's fine.

@FRidh I'm definitely not a lawyer either. I don't know what the wording of PLEASE READ THE FOLLOWING means legally.
However, I'm used to Arch Linux, where there is an easy-to-use package called virtualbox-ext-oracle that will automatically download and install the Oracle Extension Pack.*
It seems unfortunate that a great distro like NixOS would require a manual step like it currently does.

IANAL, but one solution that might be possible is a configuration flag for accepting the license which has a description that includes this line.

This would work for me. :+1:
Although in the case of the virtualbox package, it seems like it should be enough for the user to specify the nixpkgs.config.virtualbox.enableExtensionPack flag.  The description for the enableExtensionPack flag should have a link to the Oracle PUEL.

However, this is a user-provided package, not officially supported by Arch Linux.

This was already discussed previously in #672.
Personally, I'm more in favor of  the Gentoo way of solving this, require the user to explicitly ack the PUEL (via ACCEPT_LICENSE configuration in this case), and then just allowing it to build. As we don't build unfree packages on Hydra, this would still mean each user will download their own copy, and we don't redistributethe binaries.

@flokli

I'm more in favor of the Gentoo way of solving this, require the user to explicitly ack the PUEL (via ACCEPT_LICENSE configuration in this case), and then just allowing it to build.

This would definitely work for me.
Although, it does seem somewhat silly that the nixpkgs.config.virtualbox.enableExtensionPack flag wouldn't imply acceptance of the PUEL.  I can't think of a time when I would want nixpkgs.config.virtualbox.enableExtensionPack to be true but I don't want to accept the PUEL.

As we don't build unfree packages on Hydra, this would still mean each user will download their own copy, and we don't redistribute the binaries.

This also works for me.
However, would it be possible to do something similar to Arch Linux, where the extension pack is a completely separate package?  There could be a virtualbox-with-extension-pack package that takes the normal virtualbox package as input, and runs the command to install the extension pack.  This would produce a virtualbox-with-extension-pack package very similar to the virtualbox package, just with the extension pack installed.
However, I don't know if this is possible with nix.

So first steps would be a extpack derivation, probably while introducing a virtualbox-puel license with free = false attribute.
Afterwards, this can be used as an input for the virtualbox derivation, so unattended installation would be possible if nixpkgs.config.allowUnfree is set explicitly (but each user would still download by himself, as we don't build unfree on hydra).
Regarding avoiding to compile virtualbox again when enabling extpack:
The current method installs the extpack somewhere inside  $out of virtualbox, which of course would be read-only if the virtualbox package was already built.
I'm not sure if its possible to specify a searchpath to virtualbox, to discover extpacks at runtime.
In case thats possible, we could load the extpack similar to what is done for flash inside the firefox wrapper

Wouldn't it be also a good idea to specify a writable path as alternative for the $out folder, so you can just install Virtualbox and install the Ext Pack when needed?

Well, this all depends on how virtualbox discovers the path to the extpack - didn't dig into the sources yet ;-)

@flokli It's set here I think: https://github.com/NixOS/nixpkgs/blob/b3af2cd9627d717820c96259a878f24687066cf1/pkgs/applications/virtualization/virtualbox/default.nix#L127

Actually, VBoxExtPackHelperApp install simply extracts the oracle extpack to $out/(share/|libexec/)virtualbox/ExtensionPacks: Oracle_VM_VirtualBox_Extension_Pack (depending on whether hardening is enabled or not):
https://github.com/NixOS/nixpkgs/blob/master/pkgs/applications/virtualization/virtualbox/default.nix#L180
However, there seems to be Oracle_VBoxDTrace_Extension_Pack in there, too (and we want to keep that extpack intact - so we can't just point it to another location.
In general, that extension path seems to be a concatenation of RTPathAppPrivateArch and VBOX_EXTPACK_INSTALL_DIR ("ExtensionPacks") - so only one hardcoded path baked into the binary and no logic to look in multiple directories, requiring that extpack to be an input of virtualbox and then triggering rebuilds of virtualbox with unfree extpacks being enabled.
I'm not sure what's the best way to fix that properly - a patch allowing to pass the extpack path as environment variable, and adding a wrapper package in front of virtualbox might help.
In case extpacks would change, we'd then only need to rebuild the wrapper, not whole virtualbox.
Most likely we then also want to move extpacks and tools like VBoxExtPackHelperApp into separate outputs, to clean that up a bit.
@xeji, what are your thoughts on that?

Maybe we can create a separate virtualbox-with-extension-package that contains everything from virtualbox, plus the extension pack. All files except the extension pack can be either copied or symlinked form the original virtualbox package (which is built by hydra) so the build would be trivial and fast.

"I'm not sure what's the best way to fix that properly - a patch allowing to pass the extpack path as environment variable, and adding a wrapper package in front of virtualbox might help.
In case extpacks would change, we'd then only need to rebuild the wrapper, not whole virtualbox."
That sounds like a great idea, because this would allow one to manually download the extpack file from Oracle's page and install it, right?

Maybe we can create a separate virtualbox-with-extension-package that contains everything from virtualbox, plus the extension pack. All files except the extension pack can be either copied or symlinked form the original virtualbox package (which is built by hydra) so the build would be trivial and fast.

@xeji Tried that out - unfortunately, the path where to look is hardcoded
inside the binaries, so no luck.

I'm not sure what's the best way to fix that properly - a patch allowing to pass the extpack path as environment variable, and adding a wrapper package in front of virtualbox might help.
In case extpacks would change, we'd then only need to rebuild the wrapper, not whole virtualbox."
That sounds like a great idea, because this would allow one to manually download the extpack file from Oracle's page and install it, right?

If I'm not mistaken, the logic to look for extpacks is in
src/VBox/Main/src-all/ExtPackManagerImpl.cpp@ExtPackManager::initExtPackManager,
loads the (hard-coded) base dir into szBaseDir, appends
VBOX_EXTPACK_INSTALL_DIR, initializes some data structure, then goes hunting
for extensions to load.
We could either watch out for a env variable being present, and use that one
when set, or probably start looking for multiple locations in $PATH style
(which would be nicer and maybe more upstream-compatible, even though we could
very easily assemble a single directory containing all extpacks using Nix).
In addition, src/VBox/Main/src-helper-apps/VBoxExtPackHelperApp.cpp would need
to be patched too, as it also verifies the extpacks to install are inside the
(hard-coded) base dir before doing anything. There's a comment to be strict "for
now", so maybe upstream intended to change behaviour anyhow at some point.
Thoughts? Somebody who wants to write a patch? :-D

To make navigating through the source simpler, I updated my git-svn mirror of virtualbox: https://github.com/flokli/virtualbox

I sent a PR implementing the first step of @flokli's plan from above:
https://github.com/NixOS/nixpkgs/pull/44896
This adds the Virtualbox PUEL as a license, and adds Virtualbox Oracle Extension Pack as a separate derivation.  As long as the end-user sets allowUnfree = true, they should be able to install the Oracle Extension Pack without any manual steps.  However, this will still require the end-user to compile VirtualBox from scratch.
Hopefully this can get merged in time for 18.09.  And then at some point in the next couple months someone will send a PR to VirtualBox (or just create a small patch for nixpkgs) that allows the Extension Pack to be installed without having to completely rebuild the VirtualBox derivation (as described above in detail by @flokli).

Just as a heads-up: it's highly unlikely I'll spend time on this - see https://github.com/NixOS/nixpkgs/pull/74503.

This PR was originally about updating the virtualbox derivation so the extpack could be downloaded automatically.
This was implemented in #44896.
flokli was also talking about modifying the virtualbox derivation so that it doesn't have to be rebuilt when you enable the extpack.  This hasn't been implemented yet.

yeah, I'd consider this issue to be solved.
The idea from https://github.com/NixOS/nixpkgs/issues/34796#issuecomment-406372825 didn't really work, as Virtualbox has suid wrappers and we (rightly) don't dlopen random .so files from weird places (what extpacks are), so people using the unfree extpack would need to recompile virtualbox.


Add audio (and maybe also video) support to the Genkit UI

Is your feature request related to a problem? Please describe.
Multimodal LLMs are coming and most of them will support for sure support audio input/output (see GPT-4o). Video input/output is probably coming next.
Describe the solution you'd like
Right now the UI has support for both image input and output. I think it would be trivial to also add support for audio and video, since native HTML components can be leveraged without the need of custom components.
Describe alternatives you've considered
For a model I'm working on, I'm converting the audio input in base64 and providing it as string. Then, I'm getting the output base64 string and converting it back to a file to listen to the result. This approach, but it's very time consuming.
Additional context
This is the approach I'm currently using. As you can imagine, this is not ideal.

For images instead, there is native support for both input and output.

Audio and video for the model runner are both supported for media input in Genkit 0.9.7!


App settings not working in preview mode

Describe the bug
As of today, we cannot open the app settings in preview mode.  We click the three-dot menu and "Preview app settings", which opens https://dashboard.stripe.com/test/apps/settings-preview in a new tab, but we get the following error:

To Reproduce
Try opening the app settings in preview mode.
Expected behavior
App settings should be opened.
Desktop (please complete the following information):

OS: Macos
Browser: Chrome (latest)

We tried with the following versions of the Stripe CLI and apps plugin:

1.8.10 / v1.1.8
1.8.11 / v1.1.9

Thanks @dariodjuric, we're looking into this issue now.

This issue should now be resolved.


move whether to hide ball and boxes on game over to page.js and have ball and boxes receive prop for their visibility value

this shouldn't actually happen, since the visibility of each ball should be set in situations other than the game ending


REST service to add a new regex

AS AN Architect
I WANT TO have a REST service to add a new Rasa regex example
SO THAT there wouldn't be any duplicate services for it
Acceptance Criteria

[x] Use POST endpoint /rasa/regexes/add to add a new Rasa regex example
[ ] Create a separate regex/[name]_nlu.yml for every regex, where [name] represents the name of the nlu

Examples
Sample input of /data/regex/asukoht_nlu.yml
version: "3.0"
nlu:
- regex: asukoht
  examples: |
    - abja[- ]paluoja
    - antsla
    - elva
    - haapsalu

Sample input of /data/regex/aastaaeg_nlu.yml
version: "3.0"
nlu:
- regex: aastaaeg
  examples: |
    - kevad
    - suvi
    - sügis
    - talv

BUG - unable to add new rasa regex examples

Works as intended. Able to add new regexes.


Hook up ml event to OTLP

Overview
Use otlp protocol class and protos or json fallback to create ml_event payload and create events in otlp.

Codecov Report

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

@@                  Coverage Diff                   @@
##             develop-scikitlearn     #822   +/-   ##
======================================================
  Coverage                       ?   32.09%
======================================================
  Files                          ?      201
  Lines                          ?    19973
  Branches                       ?     3386
======================================================
  Hits                           ?     6411
  Misses                         ?    12840
  Partials                       ?      722

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

🚀


Choose username save button doesn't work

Enter button works, save button does not

Fixed by b34428e


[latlon muxer] fix gtest

Description
sometimes CI fail by pub/sub and is depend on machine power
1: [ RUN      ] FakeNodeFixture.longitudinal_emergency
Error: OR] [1637094206.261132890] [longitudinal_controller]: [Emergency stop] vel: 0.000, acc: -0.100
1: [       OK ] FakeNodeFixture.longitudinal_emergency (232 ms)
1: [ RUN      ] FakeNodeFixture.longitudinal_set_param_smoke_test
1: [       OK ] FakeNodeFixture.longitudinal_set_param_smoke_test (138 ms)
1: [----------] 17 tests from FakeNodeFixture (6915 ms total)
1:
1: [----------] Global test environment tear-down
1: [==========] 17 tests from 1 test suite ran. (6916 ms total)
1: [  PASSED  ] 16 tests.
1: [  FAILED  ] 1 test, listed below:
1: [  FAILED  ] FakeNodeFixture.stopped
1:
1:  1 FAILED TEST
1:   YOU HAVE 1 DISABLED TEST
1:

fix gtest for latlon muxer
Review Procedure
colcon test pass
Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[ ] Read pull request guidelines
[ ] Code follows coding guidelines
[ ] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the guidelines.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@TakaHoribe @kenji-miyake @KeisukeShima ca you take a look at ?


perf(app): Upgrade Electron to v3 and remove Node in renderer

…erer
overview
This PR is a performance/security update to:

Upgrade Electron to 3.0.0 for various performance and security updates since 1.8.x
Disable Node integration in the renderer process for security

changelog

Upgrade Electron to v3.0.0

Node 10.2.0
Chromium 66.0.3359.181

Disable Node integration in the renderer process

Our renderer process still needs access to Node stuff (the electron module) in the app's shell client (how the app talks to app-shell) at app/src/shell/index.js
Electron allows a preload script to run and attach stuff to window before the UI is loaded for exactly the purpose of handing a safe subset of Node to the renderer
This is how we now access any necessary Node stuff in the renderer process

Moves logs to the proper place

review requests
Important to note: There are breaking changes since our last Electron version upgrade, so after you run this build of the app on Electron 3, you may find that older versions of the app now crash. If you need to go back to an ealier version of the app, you may need to wipe out the app's configuration directory at:

%APPDATA%\Opentrons on Windows
~/.config/Opentrons on Linux
~/Library/Application Support/Opentrons on macOS

Grab a build from #builds and make sure everything works! We'll need tests on:

[ ] Mac
[ ] Linux
[ ] Windows

Sanity checked so far on:

macOS 10.13 (High Sierra)
Windows 7

Still to test:

Linux (any of 'em)
Autoupdate to newer version
Autoupdate to older version (here there be dragons)

OSX
[x] connect to usb and wifi
[x] test a couple http endpoints like lights and home
[x] upload and simulate protocol
[x]

Apologies for the force push again. merge conflicts with yarn.lock because of a recent yarn upgrade

App self-update tested and working on Windows 7


I broke my laptop

I so love this app and tried it on my laptop, I did it too many times and my laptop is broken now, how can I fix it?

sorry for ur loss :cry:
https://github.com/veggiedefender/open-and-shut/blob/6479cfe088b85a7b026ed17cde63859823980273/LICENSE#L17-L18

I am sorry for your loss...  :(
But I cannot stop laughing. ROFL...


Feature/messagepack serializer

This PR adds the package to support MessagePack serialization. Referent to #229.

@walter-psjr
I did read a little bit about the library you are using. The only (or main) extension point of that library are the different resolvers, right?
So, I think that should be a configuration point for this implementation, too. You are currently basically hardcoding it to use ContractlessStandardResolverAllowPrivate.
You can pass objects to serializers in CacheManager, custom configuration or anything, see JsonSerializer for example.
The configuration extensions could take an optional resolver instance which defaults to what you have right now...
What do you think?

Before I review the PR, could you please squash your commits so that the changes do not show up twice in the changed files?
Thanks! ;)

Hi @MichaCo, I'm sorry for the delay in answering. I did the commits squash. I left this configuration of the contracts static because I had problems with running the tests and internal classes. I'll take another look, I saw that other people had problems with tests but said that this was solved in the library in December. Thanks for the feedback, I'll try to see this as soon as possible.


fFeatures/test anjo

List any issues that this PR fixes: fixes # , etc...

Fixes LoserAgent property functions to call agent functions instead of unit functions.

This pull request proposes the following changes:

Adds spawnPoolRavager_agent.py skeleton to implement an all-in 12 spawn pool ravager strategy.

wait i accidentally changed the pull request template


Removal of torchaudio.legacy

The legacy load/save are wrappers around the regular load/save functions. We want to remove them for this release.
def load(filepath, out=None, normalization=None, num_frames=0, offset=0):
  return torchaudio.load(filepath, out, normalization, False, num_frames, offset)

def save(filepath, src, sample_rate, precision=32):
  torchaudio.save(filepath, src, sample_rate, precision, False)

If this goes into the release, then we need to update the notes.