Fix [R-package] Prevent remembering parameters

Reverts Microsoft/LightGBM#796 and fixes it correctly.
STILL TODO

[x] Use model save/load trick
[x] Check model save/load trick
[x] Update doc

library(lightgbm)
data(agaricus.train, package = "lightgbm")
train <- agaricus.train
dtrain <- lgb.Dataset(train$data, label = train$label, weight = inverse.rle(list(lengths = c(rep(500, 12), 513), values = 1:13)), init_score = inverse.rle(list(lengths = c(rep(500, 12), 513), values = (1:13) * 2)))
params <- list(objective = "regression", metric = "l2")

# Works with/without
dtrain$construct()

model <- lgb.train(params,
                   dtrain,
                   10,
                   list(train = dtrain),
                   min_data = 1,
                   learning_rate = 1,
                   early_stopping_rounds = 10,
                   reset_data = TRUE)

# Check whether data is copied deeply or not
dtrain$setinfo("weight", inverse.rle(list(lengths = c(rep(500, 12), 513), values = 13:1)))

# Info (weight as example) on data are NOT identical // CORRECT
dtrain$getinfo("weight")

# Not identical training! // CORRECT
model <- lgb.train(params,
                   dtrain,
                   10,
                   list(train = dtrain),
                   min_data = 1,
                   learning_rate = 1,
                   early_stopping_rounds = 10)

@guolinke This should be OK now.


Add epidemic phase figure as a check for how its working

This PR adds an additional figure (that we might want to reformat if we were to really put in the supplement) that I am using to check how the epidemic phase classification is working. As expected, I don't think this is exactly what we want because it is telling us about the trend in infection dynamics currently, which is about 2 weeks on average earlier than what we see in the hospital admissions signal. See fig here.
Not for this PR necessarily, but we should probably have a discussion about changing this algorithm a bit @zsusswein tagging you for awareness/thoughts since you suspected this would be an issue...

Closing this bc its in the #112


Migrate just crashed sqlserver

Hi Prisma Team! Prisma Migrate just crashed.
Command
db pull
Versions

Name
Version

Platform
windows

Node
v14.17.0

Prisma CLI
4.1.1

Engine
8d8414deb360336e4698a65aa45a1fbaf1ce13d8

Error
Error: [libs\datamodel\connectors\dml\src\model.rs:494:29] Hi there! We've been seeing this error in our error reporting backend, but cannot reproduce it in our own tests. The problem is that we have a primary key in the model `AD_OCOPROMOTOR` that uses the column `NROREG` which we for some reason don't have in our internal representation. If you see this, could you please file an issue to https://github.com/prisma/prisma so we can discuss about fixing this. -- Your friendly prisma developers.

Hi @anaelj, thanks for reporting this. What database are you using and which version? Could you introspect this database before successfully with Prisma? Can you share the SQL schema of that database with us? (We can accept them in private at<EMAIL_ADDRESS>NDA if needed as well.)

This error occurs when i run instrospect
prisma : 4.1.1
@prisma/client : 4.1.1
Microsoft SQL Server 2014 - 12.0.4100.1 (X64)
Standard Edition (64-bit) on Windows NT 6.3  (Build 9600: ) (Hypervisor)
Sorry, i don´t have permission to share the schema.

This should be fixed in Prisma 4.2, to be released tomorrow (https://github.com/prisma/prisma-engines/pull/3108)


Revamp calendar view design on native

Right now the design isn't great. I like that it scrolls infinitely in either direction, but the date labels are very easy to miss. Additionally, it should be possible to see a monthly view, so you can scroll to any specific location you want.
Note that right now the calendar view is built around the assumption that the current day is always visible. We'd like to break this assumption in the future, for instance if you use the monthly view to select a date far in the future.

Would also be great if it were possible to filter the entries that appear, similar to what is currently possible on web.


Request: do not store domains in etcd:/deis/domains

Currently, when a domain is added for an app, the relationship between that app and that domain is stored in two places: the database (makes sense) and etcd under the key /deis/domains (might not make quite as much sense).
The deis-router, ultimately needs to be aware of these relationships and I believe it runs confd in the background to update routes based on what's found in etcd under the /deis/domains key.
The problem with this is that anyone who's seeking to externalize durable platform state using the likes of RDS and S3 has no way of externalizing this little bit of configuration. It has, at least once, left me tearing down a cluster that I presumed to be stateless, only to replace it with another brand new cluster, backed by the same externalized datastores only to find that some of my routes are broken.  Deleting and re-adding the domains fixes the situation, but that's less than ideal.
Can the router source this information from the database instead?
#3486 is strikingly similar in nature, but pertains to the builder.  These two issues probably call for one common solution.

The router relies on confd, which in turn relies on certain backends like etcd, consul, redis, etc. We'd need a way to allow confd to read from either a database or some other construct.

Deleting and re-adding the domains fixes the situation, but that's less than ideal.

Note that we explicitly call that out in the documentation: http://docs.deis.io/en/latest/managing_deis/backing_up_data/#finishing-up

@bacongobbler sorry... I missed that part of the documentation.  Thank you.
Question: what about pivoting a little on both this issue and #3486 and instead of not storing any platform state in etcd as initially requested, we made restoring those key/value pairs a bit easier?  I'm thinking that the steps highlighted in the documentation you just linked me to could be performed by a new API endpoint (accessible only to admins) and the CLI could allow admins to perform this final restoration step with ease.
Thoughts?

Maybe the controller could re-add this keys to etcd on boot from the database. This would ensure that on a restore from an existing database all keys are re-populated.

This issue is quite old, but has new relevance because of #4333
I do think controller should re-publish application config, application domains, and user keys at startup.

Superseded by #4355


How to continue an conversation?

Can you show me what I need to save so that Bard can remember the previous conversation without starting a new one after each question?
I'm trying to write it on PHP
I used Chrome Dev Tools to monitor and found SNlM0e and conversation_id unchanged, I tried saving it again but the result is not as expected

I think it is correct to get the conversation data (conversation_id...) somewhere before get_answer

Trying to stick more cookie information into the session and then proceeding may be able to fix it.
Try using a reusable session first, then stick more cookie values to the session. If you find a solution, please contribute.

It was confirmed that the conversation can be continued through a reusable session. Use the following code. Close the issue.
from bardapi import Bard
import os
import requests

token='VwhVqhvFpnOm_sSsLszdru_DWm8otZBt3hPR9fud2BePGTk2jQmGmfcbKb_vyr3IjJFKEA.'
session = requests.Session()
session.headers = {
            "Host": "bard.google.com",
            "X-Same-Domain": "1",
            "User-Agent": "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36",
            "Content-Type": "application/x-www-form-urlencoded;charset=UTF-8",
            "Origin": "https://bard.google.com",
            "Referer": "https://bard.google.com/",
        }
session.cookies.set("__Secure-1PSID", token)

bard = Bard(token=token, timeout=30, session=session)
bard.get_answer("나와 내 동년배들이 좋아하는 뉴진스에 대해서 알려줘")['content']

bard.get_answer("What is my last prompt is?")['content']

@dsdanielpark This re-usable session is the same as in the readme, correct? So one must not use sessions if one wants to reset the conversation?
Worth adding to the readme.

@dsdanielpark This re-usable session is the same as in the readme, correct? So one must not use sessions if one wants to reset the conversation?
Worth adding to the readme.

I added a little explanation, but it doesn't mean much to continue that much conversation in the current bard.
bardapi is just a slightly more simplified version of chatting on the bard official site.
In practice, the very notion of continuing this conversation means that the session will be very limited and short.
Bards don't remember me for very long, which means that I don't update parameters, just that my chat history is kept for a short period of time.
Find out more about how the bard service works with the large language model.

If you keep the session fixed and test it, you can receive the last prompt of the previous conversation as part of the result. Please confirm and let me know.
If that's not the case, it would be best to maintain the conversation history and continue the conversation based on that.


[BUG] Not creating Text Channels

Hello
I was trying to use this bot with my server and when i first invited it and joined a voice chat. It created a linked voice chat in a separate category. Then moved the channel to my current category and change the name to remove text from it. I then deleted the channel by mistake. I tried moving to another voice channel and back. This did not make any new text channel. I tried resetting the nexus bot by kicking and reinviting it. I am currently trying banning it.
Thank you

@AkashCanjels by mistake I wrote in the previous comment that I was able to reproduce the issue.
Just in case you're looking at emails, not comments on GitHub: can you please verify that text category created by Nexus bot exists on your server?
Thanks in advance.

I've added logic to remove category and linked channels info when the bot is kicked from the server.
You can try to add bot again and kick it straight away.
If it still won't work - consider reopening this issue.
Hope it helps.
I’m eager to receive your feedback.


Bug(Button): Incorrect button behavior in next js 14 ssr

Incorrect button behavior in next js 14 ssr

use case

@lu-perfect Should be fixed now. Is it still reproducable in the latest version?


Change level of the file length rule

Decoder.scala needs to shrink a bit but I don't think that needs to happen immediately (especially since a large proportion of the lines are docs).

[Current coverage][cc-pull] is 80.54% (diff: 100%)
[][cc-pull]

No coverage report found for master at c934acf.

Powered by Codecov. Last update [c934acf...bdd28fa][cc-compare]
[cc-base-branch]: https://codecov.io/gh/travisbrown/circe/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/travisbrown/circe/compare/c934acf6bf63db1b3db9ad5d9490d2298af6c938...bdd28fa6040482f543ff45071c44c72f92260dbc?src=pr
[cc-pull]: https://codecov.io/gh/travisbrown/circe/pull/330?src=pr


feat(backdrop): add fullscreen flag to backdrop

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
Currently, the backdrop doesn't take up the entire height available to it.
Fixes: N/A
What is the new behavior?
This flag allows the backdrop to take up the height.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

lgtm


Draw UI to the Edge of the screen

Describe the bug
On Xbox, the app don't fit the screen. Instead we have borders.
Steps to reproduce the bug
Steps to reproduce the behavior:

Download XAML Controls Gallery on Xbox OS (One / Series S/X)
Open the app.

Expected behavior
Fit the screen.
Actual behavior
Have bad borders.
Screenshots

(Sorry, because it's not a game. Xbox don't allow me to capture the screen).
I think it's related to https://docs.microsoft.com/en-us/windows/uwp/xbox-apps/turn-off-overscan
Device form factor:

[ ] Desktop
[ ] Mobile
[x] Xbox
[ ] Surface Hub
[ ] IoT

@Brouilles this behavior is expected. TVs can overdraw and it's important for apps to provide a buffer so that important content doesn't get clipped on some users' hardware. More information here: https://docs.microsoft.com/en-us/windows/uwp/design/devices/designing-for-tv#tv-safe-area

It's weird. Not consistant. No way to enhance this?
I know the Chromuim Edge is now "Fullscreen" whereas the Edge lagacy on Xbox is not.

This behavior has nothing to do with Edge. It's because Xboxes are typically hooked up to televisions not monitors. Monitors have precise pixel rendering and can be adjusted to make sure content never draws outside the monitor's visible area. TVs make no such promises so we strongly recommend building in a safe area, which will be visible on some TVs and not visible on other TVs.


[OAP-CACHE]Disable OAP Cache in runtime

For some query, w/ OAP data source cache(Parquet/ORC) may be slower than wo/. Provide a config so that user could choose use cache or not in runtime.

close since PR got merged.


Update Bootstrap (for admin) to v4.a6

Ruby noob question. :D
A v4.a6 ruby gem only exists for bootstrap and not for bootstrap-sass.
Do you think we can change on for the other or you have done some customization to bootstrap-sass and we need to wait tor the boostrap-sass gem ?

gem "bootstrap", "~> 4.0.0.alpha6" is good


Add NVIDIA tegra support

Thanks for creating this project!
This pull request adds support for NVIDIA tegra, as discussed in the forum and mender hub page.
To test before the pull request is complete you can use
repo init \
        -u https://github.com/Trellis-Logic/meta-mender-community \
        -m meta-mender-tegra/scripts/manifest-tegra.xml \
        -b add-tegra
repo sync

Based on Mirza's recommendations in the forum and the recommendations in the meta-tegra pull request I haven't tried to update partitioning or moving u-boot environment out of a dedicated sector.  Although I'd expect these patches to support any NVIDIA platforms supported by meta-tegra there will be partition layout related work to do which I've summarized in the README.  I only have access to a TX 2 development board today and can't test on other platforms, therefore I'll avoid trying to add untested work with the initial PR.
This was my first time setting up a yocto project with the repo tool and I think it's a cool way to setup a project.  A few observations:

I think the mkdir mender-<vendor/soc name> would really be setting up your yocto based project, so a directory name like yocto-yourprojectname might be more appropriate.
I think the README.md instructions in the root folder are missing a repo sync command after repo init.
Some detail about the workflow in the README might be warranted.  I don't think repo upload works unless you have a gerrit server for instance, so it's likely anyone not using gerrit will want to add git submodules and also add their conf/local.conf and bblayers.conf files to share their project with others on the local team.  Let me know if you have a different workflow in mind.  If this is the workflow you expect people to use often it might be handy to add a script which can create git submodules and adds appropriate .gitignore files.
I added a helper meta-mender-tegra/scripts/deploy.sh script but couldn't figure out how to add this to the root directory of the project on init.  I needed to back out my first attempt in f3f0537791722cf4aaff9b60233c1cfd80b3cf3f because the repo init command was failing with:

fatal: manifest 'meta-mender-tegra/scripts/manifest-tegra.xml' not available
fatal: duplicate path sources/meta-mender-community in /home/dan/yocto-tegra-2/.repo/manifests/meta-mender-tegra/scripts/manifest-tegra.xml

probably because I had duplicated the same project attribute from scripts/mender.xml.  Let me know if you have ideas about how I could accomplish this.

Related to the comment above, I like to put really simple scripts in the base directory of projects so team members, even ones who don't know yocto or bitbake workflow, are comfortable doing simple tasks like building and deploying software.  For this reason I typically add a ./build.sh script with content like this one in the root of a project directory.  This could be shared with all projects and would be useful after the first setup-environment step for future builds.  Just an idea and no worries if you'd rather not.  I'd be interested in any reasons this is not a good idea from your perspective.

I'm happy to incorporate any of the changes above into this or a new PR, and equally happy to just let the project be as-is, just let me know.
Thanks again for creating this project!

I think the README.md instructions in the root folder are missing a repo sync command after repo init.

Yes they are :). Feel free to fix that.

Some detail about the workflow in the README might be warranted.

repo is only intended to be used to fetch the sources, and is a somewhat simple way of doing so instead of keeping separate "git clone" commands. For most people this will be enough.
Development workflow might be a good idea to add later on, but I do not see why you would need git sub-modules for that? I normally just use "repo" to fetch and then you have the individual git repos locally and I can work on them how ever I would like.

I like to put really simple scripts in the base directory of projects so team members, , even ones who don't know yocto or bitbake workflow, are comfortable doing simple tasks like building and deploying software

This might be out of scope for meta-mender-community, as we have the Mender Hub which are a couple of copy/paste commands to get an image built and do not really require any knowledge of Yocto nor Bitbake if it works :P.
One downside with these type of scripts is that we will get more files to maintain and it will be hard to cover all corner cases.

One other comment about potential README changes: you could consider a TODO section linking to building-for-production instructions so people doing their first deployment are aware of the work remaining to get the solution ready for production, also a section linking the partition layout section which discusses the need to move persistent data into the /data partition.

Great ideas. I would rather see this to be part of the template we have on Mender Hub for Yocto project, as we are trying to keep the README here minimal (see my other comment)

I think the README.md instructions in the root folder are missing a repo sync command after repo init.
Yes they are :). Feel free to fix that.

Done

Development workflow might be a good idea to add later on, but I do not see why you would need git sub-modules for that? I normally just use "repo" to fetch and then you have the individual git repos locally and I can work on them how ever I would like.

You wouldn't necessarily need git submodules but I haven't worked on a team yocto based project which did anything else yet.  If you don't have repo or git submodules what mechanism do you use to stay in sync with other team members on builds and ensure you are always building from the same branches of each repository?  This is why I'm wondering if there's some different workflow others use which I haven't considered.

This might be out of scope for meta-mender-community, as we have the Mender Hub which are a couple of copy/paste commands to get an image built and do not really require any knowledge of Yocto nor Bitbake if it works :P.

Agree, the Mender Hub or README instructions and repo steps get you as far as getting the setup and first build done, it's just after this that you need to understand more about yocto and buildroot.

One downside with these type of scripts is that we will get more files to maintain and it will be hard to cover all corner cases.

Agreed.
What do you think is the right way to share the deploy.sh script I mentioned in the comments, which would be specific for tegra?  Leave it in the meta-mender-tegra/scripts directory?  Or is there some way I'm missing to get it copied to the root folder by the setup script?

One other comment about potential README changes: you could consider a TODO section linking to building-for-production instructions so people doing their first deployment are aware of the work remaining to get the solution ready for production, also a section linking the partition layout section which discusses the need to move persistent data into the /data partition.
Great ideas. I would rather see this to be part of the template we have on Mender Hub for Yocto project, as we are trying to keep the README here minimal (see my other comment)

Agreed these probably would be better in the Mender Hub template, especially since they are unlikely to change between branches.
I'm re-testing the build with latest changes, once this is complete I'll fix any other issues, then modify scripts/mender.xml to prepare for the pull request to be resolved.

What do you think is the right way to share the deploy.sh script I mentioned in the comments, which would be specific for tegra? Leave it in the meta-mender-tegra/scripts directory? Or is there some way I'm missing to get it copied to the root folder by the setup script?

I would just leave it in meta-mender-tegra/scripts for now.
Also I took some liberties and edited your Mender Hub post. I noticed that our template is out of date and needs updating. If you can take a look.
The current policy is to put all the useful information in Mender Hub, and avoid linking to README files to setup build etc. Instead I kept you link to the tegra "local.conf.append" for additional details (putting it in Mender Hub seemed liked a duplication as it was pretty good documented in the actual file). This is for anyone wanting to dig deeper.

Could you please put this one, https://github.com/mendersoftware/meta-mender-community/pull/15/commits/a63d50994d48c7b98cbbea7d70680651e4798600 in a separate PR. Trying to keep the PR "scoped" :), and this is unrelated to Tegra support.
Also can you squash your commits?

The tegraflash_custom_pre step apparently must happen before the dataimg file exists in ${DEPLOY_DIR_IMAGE}, and the dataimg file does not exist when the zip step is performed. Let me know if you have any suggestions.

I wounder if the dependency should say:
 "core-image-base.do_image_tegraflash" -> "core-image-base.do_deploy"

The tegraflash_custom_pre step apparently must happen before the dataimg file exists in ${DEPLOY_DIR_IMAGE}, and the dataimg file does not exist when the zip step is performed. Let me know if you have any suggestions.

I think you need to use IMGDEPLOYDIR instead of DEPLOY_DIR_IMAGE

The tegraflash_custom_pre step apparently must happen before the dataimg file exists in ${DEPLOY_DIR_IMAGE}, and the dataimg file does not exist when the zip step is performed. Let me know if you have any suggestions.

Looking at this line, https://github.com/mendersoftware/meta-mender/blob/sumo/meta-mender-core/classes/mender-dataimg.bbclass#L7
The image is installed to ${IMAGE_NAME}.dataimg and not ${IMAGE_BASENAME}-${MACHINE}.dataimg, which is the symlink name. Not quite sure where that one is created (magic :)).

OK @mirzak thanks for your help and suggestions.  I think it's ready to go, please review and let me know if you'd like any additional changes.

Sorry @dwalkes, busy busy :).
This looks good to me and merging.

Just a reminder to update you Mender Hub post


Release 7.80.1

Please make sure all GH checks passed before merging. It can take around 20 minutes.
Briefly review this PR to see if there are no issues or red flags and then merge it.

Testing release script, please ignore


UI / Reduce the number of scroll bars

Reduce the number of sidebar scroll bars

@dethan3 How is it now?

I checked the website and the scrollbar issue has been resolved. It's working great now.
Thank you to whoever fixed it. This issue can now be closed.


add util/retry package

What does this PR do?
Retryer implements a configurable retry mechanism than can be embedded in any class providing attempt logic as a func() error method reference.
See the unit test for an example.
I will rework the dockerutil and kubeutil to use that in coming separated PRs.
Motivation
We'll need retry logic for the docker daemon & kubelet, I decided to move that logic to a common class, that could be used for other retry-and-error use cases. Logic is generic enough to be usable with any process that might fail.

Updated the naming


UI Dashboard - Technical documentation update

Please revise chapter. Divide it to Functionality (description of what is delivered in 1st prototype) and Future work (everything else). Also Technology chapters should be revised and only what we are using in the first prototype should remain here.
This chapter can maybe link to functionality of other technical components. Such as in case of data download & export. Should we rename the component Metadata authoring? Manual update of metadata can be even skipped for the first iteration.

Text in this chapter will be split between other components - Metadata Catalogue, Metadata Authoring,...


The support to Milk-V Duo RISC-V board is missing

Since NuttX supports C906, the low cost Milk-V Duo RISC-V board is a nice addition! ;-)

Seems to be the save chip with just some small modifications:
https://lupyuen.codeberg.page/articles/sg2000.html


Enforce version bounds per-bundle and inter-bundle

Description

Intra-bundle dependencies are fixed to the exact same version.
Inter-bundle dependencies are set to the current version up to the next minor (see treatment on ^>= here)

Motivated by this FAQ I think this would only be a minor bump.
Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[x] The documentation has been properly updated
[x] New tests are added if needed and existing tests are updated
[x] Any changes affecting Consensus packages must have an entry in the appropriate changelog.d directory created using scriv. If in doubt, see the Consensus release process.
[x] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[x] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

bors r+

bors r+

bors r+

bors r+


Exception thrown while trying to create Partner Connection!!!Failed to get next element

[Moving from email thread to an issue]
I'm having a spot of bother getting ApexUnit up and running.
Any insight you can provide would be appreciated because I'd very much like to get this tool up and running for us. We develop three managed packages for diverse customers with complex implementations, and being sure all the test pass with optimal coverage is crucial for us.
I'm able to connect with the curl command
curl -v https://login.salesforce.com/services/oauth2/token -d "grant_type=password" -d "client_id=3MVG98XJQQAccJQcC7AAOFrxPf5wo7oCP1h83CjrbS9dKlmFDx_e7xSB5XaN7vBR9IO2uPQID_9LnisG6HRmg" -d "client_secret=1103520132783667035" -d<EMAIL_ADDRESS>-d "password=$password"
and it returns a token
{"access_token":"00DG00000005KL8!AQwAQJ6uAyNbyTJ3o9PBVZPRZN9uL5L3OUdz7ASSmXW01acvelJS170Kyg9.db7SV.m87hb9wpv8ex1xrFFZxytKy1Yi6rUP","instance_url":"https://na11.salesforce.com","id":"https://login.salesforce.com/id/00DG00000005KL8MAM/005G0000005IPdoIAG","token_type":"Bearer","issued_at":"1456821243980","signature":"N74stPAnX2fj0mHv2kAkwxliPDeftn67HRtw4qH8xt4="}
when I try the Maven command against a fresh checkout of ApexUnit
/opt/apache-maven/bin/mvn compile exec:java -Dexec.mainClass="com.sforce.cd.apexUnit.ApexUnitRunner"  -Dexec.args="-org.login.url https://login.salesforce.com/services/oauth2/token  -org.client.id 3MVG98XJQQAccJQcC7AAOFrxPf5wo7oCP1h83CjrbS9dKlmFDx_e7xSB5XaN7vBR9IO2uPQID_9LnisG6HRmg  -org.client.secret<PHONE_NUMBER>783667035 -org.username<EMAIL_ADDRESS>-org.password $password -regex.for.selecting.source.classes.for.code.coverage.computation Action -regex.for.selecting.test.classes.to.execute ActionTest"
the system presents

[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ApexUnit 2.3.2
[INFO] ------------------------------------------------------------------------
[WARNING] The artifact org.apache.commons:commons-io:jar:1.3.2 has been relocated to commons-io:commons-io:jar:1.3.2
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ApexUnit-core ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 7 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ApexUnit-core ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] >>> exec-maven-plugin:1.2.1:java (default-cli) > validate @ ApexUnit-core >>>
[INFO]
[INFO] <<< exec-maven-plugin:1.2.1:java (default-cli) < validate @ ApexUnit-core <<<
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ ApexUnit-core ---
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.ApexUnitRunner - ####################################   Processing the Apex test classes specified by the user  ####################################
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] ERROR com.sforce.cd.apexUnit.ApexUnitUtils - Exception thrown while trying to create Partner Connection!!!Failed to get next element
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.ApexUnitUtils - Shutting down ApexUnit
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:1365)
at com.sforce.cd.apexUnit.ApexUnitUtils.shutDownWithErrMsg(ApexUnitUtils.java:68)
at com.sforce.cd.apexUnit.ApexUnitUtils.shutDownWithDebugLog(ApexUnitUtils.java:53)
at com.sforce.cd.apexUnit.client.connection.ConnectionHandler.createConnection(ConnectionHandler.java:130)
at com.sforce.cd.apexUnit.client.connection.ConnectionHandler.getConnection(ConnectionHandler.java:200)
at com.sforce.cd.apexUnit.client.testEngine.TestExecutor.testExecutionFlow(TestExecutor.java:50)
at com.sforce.cd.apexUnit.ApexUnitRunner.main(ApexUnitRunner.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:745)

The Action and ActionTest classes exist in the target org. For debugging purposes, I'm not trying a wildcard regex but passing two actual class names.
The org is a Developer Edition branch pilot org with a prefix enabled. I've also tried adding the prefix reference with no joy.
I can start over and try it with a scratch org first but I thought you might have a ready answer for this particular error message.
Maven 3.3.9 is installed at /opt/apache-maven and the java -version is
java version "1.7.0_91"
OpenJDK Runtime Environment (amzn-<IP_ADDRESS>.63.amzn1-x86_64 u91-b00)
OpenJDK 64-Bit Server VM (build 24.91-b01, mixed mode)
-Ted.
---------- Forwarded message ----------
From: Adarsh Ramakrishna<EMAIL_ADDRESS>Date: Tue, Mar 1, 2016 at 5:07 PM
Subject: Re: ApexUnit - Exception thrown while trying to create Partner Connection!!!Failed to get next element
To: Ted Husted NU<EMAIL_ADDRESS>Cc: IT-CD<EMAIL_ADDRESS>Hi Ted,
Welcome to ApexUnit community! Thanks for reaching out to us.
Do you mind logging this issue on github for tracking purpose?
Our suggestion is:
Please try using -org.login.url https://login.salesforce.com/ over to using -org.login.url https://login.salesforce.com/services/oauth2/token in the maven command. Let us know how it goes.
Also,
The curl  command is for verifying Tooling API connection for code coverage computation and has no impact on the partner connection handling which is used to execute the tests. I am glad that you verified it, code coverage computation should work for you with your current setup.
Thanks,
Adarsh

Changing the login url to
-org.login.url https://login.salesforce.com
did help, though I'm up against another error now.

[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.client.utils.ApexClassFetcherUtils - Using regex(es): ActionTest to fetch apex classes
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.client.utils.ApexClassFetcherUtils - Using regex: "ActionTest" to fetch apex classes
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] ERROR com.sforce.cd.apexUnit.ApexUnitUtils - No/Invalid test classes mentioned in manifest file and/or regex pattern for ApexTestPrefix didn't return any test class names from the org

It's a branch pilot org, and so there is a managed package prefix associated with the org.
I tried with and without the prefix. I also tried escaping the "." in the prefix, which presented a different error

[com.sforce.cd.apexUnit.ApexUnitRunner.main()] ERROR com.sforce.cd.apexUnit.ApexUnitUtils - Connection Exception encountered when trying to query : SELECT Id , Name FROM ApexClass WHERE NamespacePrefix =null AND Name like 'NC.ActionTest%'

Have people been using ApexUnit successfully with packaging orgs?
How is the prefix reference handled?
-Ted.

Hi Ted,
I opened an issue about this awhile back and a solution was implemented that should allow you to specify the namespace as part of your regex. If you namespace is NC, then you should be able the regex as NC.ActionTest*. Please see the commentary on this pull request: https://github.com/forcedotcom/ApexUnit/pull/14 for some background.

Hmmm, that's what I'm doing with a fresh checkout.

/opt/apache-maven/bin/mvn compile exec:java -Dexec.mainClass="com.sforce.cd.apexUnit.ApexUnitRunner"  -Dexec.args="-org.login.url  https://login.salesforce.com  -org.client.id 3MVG98XJQQAccJQcC7AAOFrxPf5wo7oCP1h83CjrbS9dKlmFDx_e7xSB5XaN7vBR9IO2uPQID_9LnisG6HRmg  -org.client.secret<PHONE_NUMBER>783667035 -org.username<EMAIL_ADDRESS>-org.password $password -regex.for.selecting.source.classes.for.code.coverage.computation NC.Action -regex.for.selecting.test.classes.to.execute NC.ActionTest"
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building ApexUnit 2.3.2
[INFO] ------------------------------------------------------------------------
[WARNING] The artifact org.apache.commons:commons-io:jar:1.3.2 has been relocated to commons-io:commons-io:jar:1.3.2
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ ApexUnit-core ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
[INFO] Copying 7 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ ApexUnit-core ---
[INFO] Nothing to compile - all classes are up to date
[INFO]
[INFO] >>> exec-maven-plugin:1.2.1:java (default-cli) > validate @ ApexUnit-core >>>
[INFO]
[INFO] <<< exec-maven-plugin:1.2.1:java (default-cli) < validate @ ApexUnit-core <<<
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:java (default-cli) @ ApexUnit-core ---
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.ApexUnitRunner - ####################################   Processing the Apex test classes specified by the user  ####################################
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.client.utils.ApexClassFetcherUtils - Using regex(es): NC.ActionTest to fetch apex classes
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.client.utils.ApexClassFetcherUtils - Using regex: "NC.ActionTest" to fetch apex classes
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] ERROR com.sforce.cd.apexUnit.ApexUnitUtils - No/Invalid test classes mentioned in manifest file and/or regex pattern for ApexTestPrefix didn't return any test class names from the org
[com.sforce.cd.apexUnit.ApexUnitRunner.main()] INFO com.sforce.cd.apexUnit.ApexUnitUtils - Shutting down ApexUnit
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:1365)
at com.sforce.cd.apexUnit.ApexUnitUtils.shutDownWithErrMsg(ApexUnitUtils.java:68)
at com.sforce.cd.apexUnit.client.utils.ApexClassFetcherUtils.constructTestClassesArray(ApexClassFetcherUtils.java:100)
at com.sforce.cd.apexUnit.client.testEngine.TestExecutor.testExecutionFlow(TestExecutor.java:54)
at com.sforce.cd.apexUnit.ApexUnitRunner.main(ApexUnitRunner.java:74)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:745)

And the classes do exist.

Any thoughts? I could try a manifest, if that might help.
Or even some other org to see if I can get this running someplace.

Hmm... that certainly looks like the correct pattern. I would have expected that to work. I can try the pattern with a namespace prefix in one of my packager orgs tommorrow to see if I can get it to work.

Ted, I concur with your findings. This appears to be broken right now. It looks like the code that splits the "regex" on . is absent from ApexClassFetcherUtils.fetchApexClassesBasedOnRegex.
private static String[] fetchApexClassesBasedOnRegex(PartnerConnection connection, String[] classesAsArray,
			String regex, Boolean includeTriggers) {
		if (regex != null && !regex.equals(" ")) {
			LOG.info("Using regex: \"" + regex + "\" to fetch apex classes");
			// construct the query
			String namespace = null;
			String soql = QueryConstructor.generateQueryToFetchApexClassesBasedOnRegex(namespace, regex);
			// fire the query using WSC and fetch the results
			String[] classesAsArrayUsingWSC = constructClassIdArrayUsingWSC(connection, soql);
			// if both manifest file and testClass regex expression is provided
			// as command line option, combine the results

			Set<String> uniqueSetOfClasses = new HashSet<String>();
			ArrayList<String> duplicateList = new ArrayList<String>();
			// eliminate duplicates from the given class Ids
			// (just in case duplicates still exist in the class array passed
			// from the calling method)
			if (classesAsArray != null && classesAsArray.length > 0) {
				for (int i = 0; i < classesAsArray.length; i++) {
					if (!uniqueSetOfClasses.add(classesAsArray[i])) {
						duplicateList.add(classesAsArray[i]);
					}
				}
			}
			// eliminate duplicates from the classes fetched using the prefix
			if (classesAsArrayUsingWSC != null && classesAsArrayUsingWSC.length > 0) {
				for (int i = 0; i < classesAsArrayUsingWSC.length; i++) {
					if (!uniqueSetOfClasses.add(classesAsArrayUsingWSC[i])) {
						duplicateList.add(classesAsArrayUsingWSC[i]);
					}
				}
			}

			//if include triggers, add triggers to duplicate list as Triggers cannot be tested on force.com
			if(includeTriggers){
				String soqlForTrigger = QueryConstructor.generateQueryToFetchApexTriggersBasedOnRegex(namespace, regex);
				String[] triggersAsArrayUsingWSC = constructClassIdArrayUsingWSC(connection, soqlForTrigger);

				if (triggersAsArrayUsingWSC != null && triggersAsArrayUsingWSC.length > 0) {
					for (int i = 0; i < triggersAsArrayUsingWSC.length; i++) {
						if (!uniqueSetOfClasses.add(triggersAsArrayUsingWSC[i])) {
							duplicateList.add(triggersAsArrayUsingWSC[i]);
						}
					}
				}
			}

			// eliminate duplicates from the triggers fetched using the prefix

			String[] uniqueClassesAsArray = uniqueSetOfClasses.toArray(new String[uniqueSetOfClasses.size()]);

			// log the duplicate classes/triggers found by querying the org with
			// the given regex
			if (duplicateList != null && !duplicateList.isEmpty()) {
				String logDuplicates = "Found duplicates from the classes fetched from the regex: " + regex
						+ ". Skipping multiple execution/code coverage computation of these test class/source class(es) :";
				for (int i = 0; i < duplicateList.size(); i++) {
					duplicateApexClassMap.put(duplicateList.get(i), apexClassMap.get(duplicateList.get(i)));
					logDuplicates += " " + apexClassMap.get(duplicateList.get(i)) + ",";
				}
				LOG.info(logDuplicates);
			}

			return uniqueClassesAsArray;
		}
		return classesAsArray;
	}

Notice that in the first few lines of this method, it set the "namespace" variable to null, and then calls QueryConstructor.generateQueryToFetchApexClassesBasedOnRegex, passing it a null value for the namespace. In my case, my "regex" for specifying test classes is "TomPackage.fflib_*Test". Ultimately this regex gets converted into the following SOQL:
SELECT Id , Name FROM ApexClass WHERE NamespacePrefix =null AND Name like 'TomPackage.fflib_%Test'

This is a bug. I'm going to file a new issue against this.

@TedHusted I filed an issue against this namespace issue and submitted a pull request: https://github.com/forcedotcom/ApexUnit/pull/31

@tfuda  Yes, there was a plan to implement the feature to test ApexClasses that belong to a Namespace prefix. However, it was not implemented because of some of the additional discussion that was to happen here. A quick fix was instead implemented to always look for the default namespace. (to unblock @tfuda)
@TedHusted  We certainly have this in our backlog to add this feature (https://github.com/forcedotcom/ApexUnit/issues/23) and created an issue for this.
Thank you for the pull request @tfuda , we will review the PR and test it for both manifest file and regex.

@pmedapuram My pull request only addresses the regex story. I did not look at the manifest file handling.

I switched orgs, and I've gotten back my first ApexUnitReport.html -- sweet!


Peer support subgroup for mentors

We need to create a sub-group to help guide mentors, initiate kick off meetings, and answer any questions the mentors have.
Not all of our mentors have mentorship experience, hence they will need some guidance, resources and a place to ask questions at times where they do not know how to deal with certain situations.
I believe the support group will carry most of its activity on the slack channel as it is our main communication channel for mentorship.

Totally agree with @Bamieh
And we need some kinds of learning paths, which help both mentors and mentees to better understand the direction where they should focus on.

Closing this since it has been resolved long time ago. We have created a private slack channel for the mentors and the mentorship team to support each other.


how to run demo on CPU

I wanted to run demo on CPU so I tried
python demo.py --vid_file demo.mp4 --gpu -1
However, it turned out:
RuntimeError: Attempting to deserialize object on a CUDA device but torch.cuda.is_available() is False. If you are running on a CPU-only machine, please use torch.load with map_location=torch.device('cpu') to map your storages to the CPU.
Then I tried to fix code in demo.py in line 108 and line 127.
But it still couldn't work.

Did you also change the code here?

Did you also change the code here?
It works, thanks!

Did you also change the code here?
It works, thanks!

i did the same thing and i changed the code as follow:
demo.py {
line 108: ckpt = torch.load(pretrained_file,map_location=torch.device('cpu'))
line 127: checkpoint = torch.load(osp.join(BASE_DATA_DIR, 'spin_model_checkpoint.pth.tar'),map_location=torch.device('cpu'))
}
tcmr.py {
line 134: pretrained_dict = torch.load(pretrained,map_location=torch.device('cpu'))['model']
}
but I'm still getting this error:

AssertionError:
Found no NVIDIA driver on your system. Please check that you
have an NVIDIA GPU and installed a driver from
http://www.nvidia.com/Download/index.aspx

@hongsukchoi
thank you for your answer but i still have the same error even after eliminating that line (line 374 in demo.py)
can i run it in google colab ?

No, I haven't prepared google colab codes.
I recommend you follow this instructions to run on CPU. I did the same thing and was able to run TCMR on CPU.
In demo.py
L55 : device = torch.device('cpu')
L108: ckpt = torch.load(pretrained_file,map_location=torch.device('cpu'))
L115: model.regressor.smpl = SMPL(
        SMPL_MODEL_DIR,
        batch_size=64,
        create_transl=False,
        gender=gender
    ) #.cuda()
L127: checkpoint = torch.load(osp.join(BASE_DATA_DIR, 'spin_model_checkpoint.pth.tar'),map_location=torch.device('cpu'))

In tcmr.py
L134: pretrained_dict = torch.load(pretrained, map_location=torch.device('cpu'))['model']


dts/arm/st/f1: stm32f107: add Ethernet MAC

Add Ethernet MAC to STM32F107 dts, similar to SMT32F207 but different clocks and especially no PTP clock.
Note that PHY configuration from Zephyr through DT or Kconfig is not possible, HAL has to be modified manually, in particular stm32f1xx_hal_conf.h when using a LAN8720A/LAN8742 for example, and also note that the default configuration generated by STM32CubeMX for LAN8742 is wrong (see: https://community.st.com/s/question/0D53W000015bQsFSAU/cant-get-f746zg-nucleo-ethernet-to-work-with-the-lwip-example-on-cubeide ).

Note that PHY configuration from Zephyr through DT or Kconfig is not possible, HAL has to be modified manually,

Thanks for the notice. Would you be able to share a branch to share your working configuration as a reference ?

Thanks for the notice. Would you be able to share a branch to share your working configuration as a reference ?

This is what I used: piernov/hal_stm32@9cfd4df . I'm not confident in these changes though, it works for what I needed but I haven't dug into the datasheets and exact roles of the registers/offsets.

Right, missed that one, hope it's ok now.


Defining "level" where it's meant to: in the stream

Fixes bug where "level" was ignored entirely.

Changes Unknown when pulling 5ccfc4ad2bd40fd1bf808d922c1aaaf99fc5b655 on fix/level-issue into ** on master**.


Build & Publish container to docker hub

Won't do!
Due to licensing issues we will not provide pre-built, runnable components for the public to use.


Merge pull request #2 from BluNite/secondBranch

Merge pull request #1 from BluNite/main
blunite

ongoing timer issues added notes to js blunite

blunite

fixed title to Dog Api from App blunite


Focus is not returned after opening icon selector and then using escape to cancel dialog

Both subject and badge exhibit the same issue:

open new subject dialog
click icon selector
press escape

PR #2678

:+1:


improve file dialog icons

OK now that I can see them, I think some of these really need help.
In particular "delete" and "icons view" / "list view" are incomprehensible,
and also quite useful.
delete should be paper with red X.
icons view should be grid of squares (2x2) vs list of lines, more like the mac:

also, all these icons are low resolutio, including the expanding triangle and folders used in the main view below.  consider replacing them all.

use http://fontawesome.io/icons/
since we already have it.
fa-arrow-left
fa-arrow-right
folder (needs a plus)
fa-files
fa-scissors
fa-clipboard
? (eraser seems wrong, seems like it should be x over a file)
fa-files-o
pencil-square
fa-th/fa-th-list
sort-alpha-asc


Colcon runs in global interpreter

The colcon executable installed through apt has a shebang of #!/usr/bin/python3.
This prevents use in different virtual environments, especially since this shebang then puts the global python shebang into scripts built with colcon.
One (or more) of the following would make this easier:

Recommended to install colcon-core locally (instead of globally with apt as per https://colcon.readthedocs.io/en/released/user/installation.html).
Change the shebang on colcon to /usr/bin/env python3.
Colcon should respect the Python interpreter specified with $COLCON_PYTHON_EXECUTABLE when building other python projects.

➜  ros2_ws git:(master) ✗ cat `which colcon`
#!/usr/bin/python3
# EASY-INSTALL-ENTRY-SCRIPT: 'colcon-core==0.3.20','console_scripts','colcon'
__requires__ = 'colcon-core==0.3.20'
import re
...

Recommended to install colcon-core locally (instead of globally with apt as per https://colcon.readthedocs.io/en/released/user/installation.html).

On Debian systems we do recommend to install Debian packages since they are being updated by apt. Using pip instead requires the user to update the packages manually which is not desired.
In the use case with a virtual environment you can install colcon into that venv using pip.

Change the shebang on colcon to /usr/bin/env python3.

The shebang line is generated by the Python setuptools package. I don't think colcon has a way to influence that. If there is something we can do different please let us know how to achieve that.
Again in the use case with a virtual environment if you install colcon into that venv using pip it should used the absolute path to the Python interpreter used in that venv.

Colcon should respect the Python interpreter specified with $COLCON_PYTHON_EXECUTABLE when building other python projects.

That sounds like a good idea. Please consider to create a pull request for this enhancement.

I've had considerable difficulty with figuring this out, but I'm making progress and you will have a pull request (or two).

The shebang line is generated by the Python setuptools package. I don't think colcon has a way to influence that. If there is something we can do different please let us know how to achieve that.

Putting this in setup.cfg causes the shebang to be as desired for both pip install and colcon build:
[build_scripts]
executable=/usr/bin/env python3

Hard lessons from playing around with this:

This setting is not respected when using pip install's -e/--editable option
When testing this, use the pip --no-cache-dir flag.


As a developer I want to understand the data.

Epic: #3

[x] Look through data.
[x] Understand what every column means
[x] Add correlation for better understanding
[x] Decide what is important and what is not

DoD:

[x] A document has been created in which the data has been described
[x] Document has been reviewed

Document has been reviewed


Update about us

Update AboutUs.md to reflect the real team. Also delete irrelevant profile photos

@INCENDE @fanwgwg @rachx Please review this PR. Let me know if you'd like to change the images or text.
@rachx Please provide me with a profile photo.


Can't build in Vite

magick-wasm version
Any
Description
When trying to build with Vite, it gives the following warning, but not always on the same file:
'ws' is imported by ws?commonjs-external, but could not be resolved – treating it as an external dependency
It decides to alias ws to require$$2, which doesn't exist, breaking the build.
I tried installing ws, which stops Vite from complaining. But the build still doesn't work, saying that Buffer does not exist, suggesting it tries to run in a node environment.
From what I can find, the problematic code resides in @imagemagick/magick-wasm/wasm/magick.js.
Steps to Reproduce
Set up a minimal project (use single -- for npm 6 and under):
npm init vite vite-build-test -- --template vanilla
cd vite-build-test
npm i @imagemagick/magick-wasm

Overwrite main.js to contain only the following:
import { initializeImageMagick } from "@imagemagick/magick-wasm";

Then try npm run build
Optionally serve the freshly created build: npm run preview
Images
No response

I have experience with Vite so I don't know what is causing this. Someone else ran into the same issue and they created this: https://github.com/Armster15/imagemagick-wasm-builds. It says they don't know why this breaks but maybe you can find out by how they solved it?

By now I've spent many hours trying to figure this out and I too can't find the underlying problem. It seems that @dlemstra/magick-native needs a build step that Vite (Rollup under the hood) can't provide, also not with polyfills (that is what the linked repository does with Webpack).

I'm trying to get things working with Webpack instead, and looked at @dlemstra/magick-wasm-docs to see your configuration. But just running git clone and npm i doesn't result in a working application, neither with serve nor with build. Webpack doesn't give any errors, but in both cases stuff just doesn't work in the browser. The only pointer so far is a whole lot of complaining from npm while installing about deprecated packages and mismatched versions, and the lock file being from an old version of npm. Do you have some custom configuration for node or npm that makes this work for you?

I've been experimenting with the repo you linked, stripping it down to the bare minimum to get a functional build. It seems a lot of their configuration is for additional things, not just being able to build.
The main thing that seems to make it work is making sure that Webpack knows what to do with a couple of nodejs modules. The linked package resolves some using browser polyfills, and disables resolution for others. I found that disabling only ws, fs, child_process, crypto and path already results in something that Vite plays well with, without specifying resolution for anything else.
Given this knowledge I've tried achieving the same thing with Vite, but no such luck. But if @imagemagick/magick-wasm gets build using Webpack before uploading to NPM, finding that solution should not be necessary. Which is probably preferable, as having to change a lot of configuration for your project just to use a library probably prevents a lot of people from using this. I'd like to hear your thoughts!
If you're interested in what I found to be the minimal build configuration, take a look below:

View code
Create a new npm project and run npm i webpack webpack-cli ts-loader typescript @imagemagick/magick-wasm. Then create the following files:
// webpack.config.js
module.exports = {
  entry: "./main.ts",
  resolve: {
    fallback: {
      ws: false,
      fs: false,
      child_process: false,
      crypto: false,
      path: false,
    },
  },
  module: {
    rules: [{ test: /\.ts$/, loader: "ts-loader" }],
  },
  output: {
    filename: "main.js",
    library: { type: "module" },
  },
  experiments: { outputModule: true },
};

// tsconfig.json
{
  "compilerOptions": {
    "outDir": "dist",
    "declaration": true,
    "module": "esnext",
    "moduleResolution": "node"
  },
  "files": ["./main.ts"]
}

// main.ts
export { ImageMagick, initializeImageMagick } from "@imagemagick/magick-wasm";
export * from "@imagemagick/magick-wasm/alpha-option";
export * from "@imagemagick/magick-wasm/auto-threshold-method";
export * from "@imagemagick/magick-wasm/channels";
export * from "@imagemagick/magick-wasm/color-space";
export * from "@imagemagick/magick-wasm/composite-operator";
export * from "@imagemagick/magick-wasm/distort-method";
export * from "@imagemagick/magick-wasm/drawables/drawable-color";
export * from "@imagemagick/magick-wasm/drawables/drawable-fill-color";
export * from "@imagemagick/magick-wasm/drawables/drawable-fill-opacity";
export * from "@imagemagick/magick-wasm/drawables/drawable-font";
export * from "@imagemagick/magick-wasm/drawables/drawable-font-point-size";
export * from "@imagemagick/magick-wasm/drawables/drawable-text";
export * from "@imagemagick/magick-wasm/error-metric";
export * from "@imagemagick/magick-wasm/evaluate-operator";
export * from "@imagemagick/magick-wasm/filter-type";
export * from "@imagemagick/magick-wasm/gravity";
export * from "@imagemagick/magick-wasm/image-magick";
export * from "@imagemagick/magick-wasm/magick-color";
export * from "@imagemagick/magick-wasm/magick-colors";
export * from "@imagemagick/magick-wasm/magick-error-severity";
export * from "@imagemagick/magick-wasm/magick-error";
export * from "@imagemagick/magick-wasm/magick-format-info";
export * from "@imagemagick/magick-wasm/magick-format";
export * from "@imagemagick/magick-wasm/magick-geometry";
export * from "@imagemagick/magick-wasm/magick-image-collection";
export * from "@imagemagick/magick-wasm/magick";
export * from "@imagemagick/magick-wasm/orientation-type";
export * from "@imagemagick/magick-wasm/paint-method";
export * from "@imagemagick/magick-wasm/percentage";
export * from "@imagemagick/magick-wasm/pixel-channel";
export * from "@imagemagick/magick-wasm/pixel-interpolate-method";
export * from "@imagemagick/magick-wasm/point";
export * from "@imagemagick/magick-wasm/quantum";
export * from "@imagemagick/magick-wasm/virtual-pixel-method";

Then run npx webpack and you should get a dist folder containing main.js and main.d.ts.

Finally got the same thing working in Vite! Under the hood it uses Rollup, so using rollup-plugin-ignore and the following config does the trick:
// vite.config.js
import { builtinModules } from "module";
import { defineConfig } from "vite";
import ignore from "rollup-plugin-ignore";

export default defineConfig({
  build: {
    rollupOptions: {
      plugins: [ignore([...builtinModules, "ws"])],
      // or:
      // plugins: [ignore(["ws", "fs", "child_process", "crypto", "path"])],
    },
  },
});

Thanks for your help, can we close this issue?

We now know a workaround, but should the underlying issue not be resolved first? I can make a PR that adds a build step either based on Vite or on Webpack, if you'd like.

Can we close this now?

I'd wait till next release, when this is no longer necessary!

When do you plan to publish the next release @dlemstra?

The new release has been publish but is broken. The index.ts file does not export everything. I wonder if this file should be generated.

I will update it myself. I was also wondering why you did export { ImageMagick, initializeImageMagick } from './image-magick'; instead of export *?

I based the index.ts it on the one from the wasm-builds library you linked somewhere above, and they did it that way there. But as I pointed out in #55, I exported it both ways and fixed it there to just export *.

The new release has been publish @Peeterush and @Helehelehele. Can you give it another try and check if we can close this issue? And thank you for are your help to make this possible @Peeterush, and also for your other improvements.

My project now builds without any special configuration! Thank you for the great library.


Error on installation - Debian 9

I'm trying to install Koel v3.6.0 on my debian system (Debian 9, stretch)
Following this guide for the most part:
https://gist.github.com/bplower/613a99156d603abac083
Using php7, nodejs 6.x, and yarn 0.23.
I'm stuck on the npm install step.
https://paste.lolisandstuff.moe/voxupovaba.coffeescript

Fixed it, edited the gist with my installation instructions:
https://gist.github.com/Duckbuster/88aac6c6b4991440a95287262cc58398


How would you add tailwinds to this repo?

Any recommendations on how to add tailwinds to this repo?

Okay. Although I'm not a big fan of Tailwind, I understand that many people find it useful. I'll give it a try.

To my friends who have been waiting for this... I apologize for the delay due to personal circumstances. I will be working on this starting this week.

https://github.com/Jonghakseo/chrome-extension-boilerplate-react-vite/pull/138

@all-contributors please add @remusris for ideas


[Deployment] Secure kubelet public api

Secure kubelet public api, add authentication for https port 10250 and close http port 10255.
Please refer to https://github.com/kubernetes/kubernetes/issues/7965, https://github.com/kubernetes/kubernetes/pull/59666 for reasons and https://github.com/docker/for-linux/issues/324, Backdooring through kubelet for hacking examples.

Coverage decreased (-3.3%) to 72.964% when pulling 9493c12635b0c527a9ef020160eddfb2b07a3f11 on xiongyf/secure-kubelet into 90f1691551b00ffd317495d613ff6f9d450391c8 on master.

Coverage decreased (-3.3%) to 72.964% when pulling 9493c12635b0c527a9ef020160eddfb2b07a3f11 on xiongyf/secure-kubelet into 90f1691551b00ffd317495d613ff6f9d450391c8 on master.

Coverage decreased (-3.3%) to 72.964% when pulling 9493c12635b0c527a9ef020160eddfb2b07a3f11 on xiongyf/secure-kubelet into 90f1691551b00ffd317495d613ff6f9d450391c8 on master.

@ydye , this PR breaks the deployment process, could you take a look?

should remove kubelet health metrics from watchdog after this PR is merged.

close this PR and address this issue in other PRs.


Crash when placing text block

https://paste.ee/p/GxFdK
discovered by quat on modfest 1.17 server

I cannot reproduce this with just Glowcase (as of 6fb36249f3dc1c58aeee8d3dcd694a986382e92f) btw, even when connecting to a server, so it's probably something in the modfest pack

A couple rounds of filebisect confirm it's caused by Lithium. The version in the Modfest pack is lithium-fabric-mc1.17.1-0.7.3.

Glowcase reads directly from the heldItem field of EntityShapeContext. However, Lithium makes some of the fields in EntityShapeContext lazy, including heldItem: https://github.com/CaffeineMC/lithium-fabric/blob/1.17.x/dev/src/main/java/me/jellysquid/mods/lithium/mixin/shapes/lazy_shape_context/EntityShapeContextMixin.java


Pytest + Geopandas not in requirements

Trying to run the tests, followed the install instructions in readme, but when I run 'make test' it says
make: pytest: No such file or directory make: *** [test] Error 1
Manually installing (via conda or pip) requirements-dev.txt resolves this.
Recommendation:

Update README to include the workflow for installing dev requirements using conda / mamba
Add a CI step that includes running the provided setup workflow and making sure the tests run

Verified as of merged PR: https://github.com/thinkingmachines/unicef-ai4d-poverty-mapping/pull/198 that the requirements were fixed (it is now streamlined to just follow one file; no more requirements-dev as this isn't prod software anyway).


Add support for arc4random() for TLS rng

MbedTLS has support for getrandom() on linux.
This adds arc4random() which should allow for operation in chroot()
on BSDs

@jasom it has been almost a year, can we make a new release for this change? Thanks!


There is no 'Preview' action on the toolbar of one file share under read-only snapshot context view

Storage Explorer Version: 1.34.0-dev (98)
Build Number: 20240305.3
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Sonoma 14.3(Apple M1 Pro)
Architecture: x64/x64/x64
How Found: Ad-hoc testing
Regression From: Previous release (1.33.0)
Steps to Reproduce

Expand one storage account -> File Shares.
Create a file share -> Upload one file.
Create a snapshot for the file share -> Switch to read-only snapshot context view.
Check whether there is a 'Preview' action on the toolbar.

Expected Experience
There is a 'Preview' action on the toolbar.

Actual Experience
There is no 'Preview' action on the toolbar.

Fixed.

Verified this issue on the main build 20240305.7. Fixed.


when the confirm dialog is up, escape closes both it and also minimizes the sidecar

i think this is a regression from the react switchover

carbon-components-react Modal is not property typed to allow overriding keydown
the underlying carbon-components modal uses keydown to handle Escape; it does do stopPropagation
however, BaseSidecar uses keyup to listen to escapes, meaning that the escape still propagates to us

Fix: use keydown in BaseSidecar!
based on:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

update: using keydown is necessary but not sufficient to fix this bug. this is because BaseSidecar is stacked below the Modal, and so stopPropagation does not work.
however, by listening to the same event class (keydown), at least we can witness the visibility of the confirm. until the types get fixed, this may be the best we can do.


Code organization is too messy！！！！

First of all, thank you for creating webpack.
However the souce code of webpack is so messy!!!
I really can't read the code.😱really hope you can sort it out , or reorganize source code.

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.


Support for Carthage

I changed the project so it is a Framework instead of an App.
I also put it in a Workspace and bumped the version.

Thanks @tsuharesu!
Everything looks good.  and fix my typo too. Can you change project name from .travis.yml and make test working from xctool.
Very excited to get your PR.

look like you need remove library from

Yeah, I didn't saw travis.yml... Will work it out today.

Yey, passing!

Good job @tsuharesu


[BUG] exceljs on Browser emits TypeError: Cannot read property 'split' of undefined

🐛 Bug Report
https://github.com/exceljs/exceljs/commit/33b050eaad7a604abcb025787ad09146a1cdde3b#diff-0ec03eab8a78bd1225de2927c0fd8e85
This commit causes error on browser. Accessing to process variable causes error.
Lib version: X.Y.Z
Steps To Reproduce

const wb = new ExcelJS.Workbook();
const ws = wb.addWorksheet('XYZ');

ws.getCell('A1').value = 7;
expect(ws.getCell('A1').value).to.equal(7);

The expected behaviour:

Possible solution (optional, but very helpful):

I am also running into this issue, any workarounds?


Compilation errors aren't silenced in a .tst.ts file when running typescript, but the test still passes with tstyche

Hi, and thanks for this awesome library!
We noticed that .toRaiseError sometimes doesn't quite work as we expect it to with respect to compilation errors.
We're not sure if there is a bug, or some better documentation is needed 🤔
Reproduction
/// file sample.tst.ts
import { expect, test } from 'tstyche';

function id(arg: number): number {
	return arg;
}

test('Cannot call "id" function with an argument of type string', () => {
	// Full error underneath: "Argument of type `string` is not assignable to parameter of type `number`."
	expect(id('123')).type.toRaiseError('Argument');
	expect(id('123')).type.toRaiseError();
});

And then when we run yarn tsc, the result is
src/__typetests__/sample.tst.ts:9:12 - error TS2345: Argument of type 'string' is not assignable to parameter of type 'number'.

9  expect(id('123')).type.toRaiseError('Argument');
             ~~~~~

src/__typetests__/sample.tst.ts:10:12 - error TS2345: Argument of type 'string' is not assignable to parameter of type 'number'.

10  expect(id('123')).type.toRaiseError();

However, running yarn tstyche gives an expected output:
❯ yarn tstyche
yarn run v1.22.19
$ /Users/..../.bin/tstyche
uses TypeScript 5.2.2 with ./tsconfig.json

pass ./src/__typetests__/sample.tst.ts
  + Cannot call id function with an argument of type string

Targets:    1 passed, 1 total
Test files: 1 passed, 1 total
Tests:      1 passed, 1 total
Assertions: 2 passed, 2 total
Duration:   11.1s

Ran all test files.
✨  Done in 12.66s.

Packages
<EMAIL_ADDRESS><EMAIL_ADDRESS>

Do you get it right, you would expect to see no error in tscs output? Hm.. It does not know anything about tstyche, so it reports the error.
 (;

Thanks for giving for TSTyche! It is a fresh library, can be documentation is missing some clarity. Let’s figure this out.

Do you get it right, you would expect to see no error in tscs output? Hm.. It does not know anything about tstyche, so it reports the error.

You're right. After giving it a second thought, that was a bit of an unfair expectation 😬

Why do you run tsc on a type test? (;

It's valuable for us to get autocomplete and other help from Typescript when writing a test (think of a normal unit test -- would you like it to write it without TSC?). Please note that if this would be another type test (not the one with .toRaiseError), running typescript on it probably wouldn't make any difference.
I see your suggestion to not run TSC on type test files 🙌🏻
I'd like to think of it as a last resort, due to a worse DevEx.
If nothing more comes to mind, though, we'll give it a go. Maybe I'm being too pessimistic about that "bad DevEx"

Wait.. Autocompletions should be there. TypeScript provides these through language service. That is just a technical detail, tsc is the TypeScript compiler.
Are you trying to say that the errors should not be highlighted in IDE, if they are matched by .toRaiseError()? This will be fixed in some 2-3 months. I have a working prototype.

Wait.. Autocompletions should be there. TypeScript provides these through language service. That is just a technical detail, tsc is the TypeScript compiler.

Yeah sorry, I mixed things up a little, but here's what I meant:

I thought it would be best if I can both compile this file with tsc and run it with tstyche. That does not seem to be possible (cause' as you said, TS does not know nothing about tstyche).
Yes, it would be nice if errors are not highlighted in the IDE and language service still works. If there's a working prototype for that, I'm more than happy to wait 🚀

Thanks!
It still feels puzzling for me why you want to pass test files through tsc? Are you trying to type check them? There is no need, because tstyche does that for you. It will pick up all syntactic and semantic errors just like tsc. Try it out (also on different versions of compiler, e.g. tstyche --target 4.8,latest).
And there is more:
import { expect, test } from "tstyche";

test.skip("is skipped?", () => {
  const a: string = 123; // obviously a type error, but it will be skipped

  // ...
});

If a test is skipped, tstyche does not report type errors in that particular test. This is why it is a type test runner.

Yes, the watch mode is planned for version 2. I have a working draft, but it needs more thinking.

To make it easier to track the progress, I open these issues:

https://github.com/tstyche/tstyche/issues/16
https://github.com/tstyche/tstyche/issues/17

Add a couple of sentences will be added to the documentation website as well.

TSTyche 2 shipped today. It has the watch mode. Give it a try! For feedback I opened #222.
Also I opened #224 to track progress on ability matchers. This is the next milestone. Thanks for starting this discussion.
I think it is time to close this issue. Is there is anything you would like to ask, feel free to leave a message here or opening new issue.


Generated JPA query with incorrect argument binding indexes

Observed vs. expected behavior
Given an JPA entity with two boolean fields, one of them annotated with a custom type @Type, when querying by those two fields providing the same boolean value (true, true or false, false) the generated query ends up using ?1 for both arguments (as they are considered a constant).
The generated query is
select user
from User user
where user.active = ?1 and user.admin = ?1  -- note the two arguments as ?1

when the expected would be
select user
from User user
where user.active = ?1 and user.admin = ?2

Steps to reproduce
Here is a sample application to reproduce the problem, with some tests and loggers enabled to show the differences between the generated query and the expected one.
https://github.com/didiez/hibernate-querydsl-type-binding-bug
Environment
Querydsl version: 4.4.0
Querydsl module: querydsl-jpa
Database: tested against oracle 11g and h2 (probably database agnostic)
JDK: 11
Additional details
Might be related to the changes applied to fix #2326 (PR #2354)

I would expect this issue to have appeared even before #2326 (PR #2354), can you confirm whether this is the case or that the regression was in fact introduced in 4.4.0?

@F43nd1r should we look into this issue before 5.x?

I confirm the issue was present before 4.4.0.
I have tested the following versions:

4.4.0
4.3.1
4.2.2
4.1.3
4.0.9
3.7.4 (same behaviour even in 3.x)

@jwgmeligmeyling  looked into it.
Easy fix would be to rip out the optimization for same constants.
Correctly fixing this is very involved.
Maybe a @Type annotated field shouldn't be represented by a BooleanPath at all, would need design for alternatives.
Or Constant could also hold their target type...
I would go ahead with 5.0 first and then someone can look into how to support custom hibernate types.

I'm all for ripping out premature optimizations. So I am fine with using multiple parameters for the same value.
ORMs, JDBC drivers and Query Engine Optimizers are perfectly capable of optimizing on their own.

An unfortunate side effect of delaying the fix is that we will probably need a 6.0 (due to a signature change in the serializer).
The specific signature change already caused quite a bit of fuzz for people using modern  querydsl-sql/querydsl-jpawith olderquerydsl-core` versions (which was easily solved, but generated a bunch of issue reports nonetheless).

In that case SerializerBase #constantToNamedLabel and '#constantToNumberedLabel need to be changed from map to list. That still involves quite a bit of related changes and I won't have time for it today, maybe I could do it this weekend.

Or we simply inverse it: labelToConstant. The label will always be unique. I'll see if I can have a look before the weekend.

I do see now that such a change would break my personal integrations 😢 So there probably will be others. Not that sure about this change anymore...

Closing as duplicate of #1413

@F43nd1r apparently someone already did the work in https://github.com/querydsl/querydsl/pull/2000/files (largely outdated PR though, and conflicts with the fix for https://github.com/querydsl/querydsl/issues/2326 provided in https://github.com/querydsl/querydsl/pull/2354 ,

Working like a charm with the latest and greatest querydsl-5.0.0.
Many thanks @jwgmeligmeyling and @F43nd1r


addressdetails for nominatim is confusingly described

https://geopy.readthedocs.io/en/stable/#nominatim

If you want in Location.raw to include addressdetails such as city_district, etc set it to True

while the most important feature is that it returns address info in a structured form

If you want in Location.raw to include address details such as house_number, city_district, postcode, etc (in a structured form) set it to True

would be IMHO better description, with original I though that it would include irrelevant detail such as city_district in the textual description (display_name), while I needed exactly structured form (I wanted to check whatever response actually matches request)

Good point!
Would you like to submit a PR? The relevant part is here: https://github.com/geopy/geopy/blob/cc3226700632fffce4b934634332e02eefb21f0e/geopy/geocoders/nominatim.py#L178-L179
It would be enough to just update that part of the doc in the PR.


Add accessibility attributes to Autocomplete

Describe the feature in detail (code, mocks, or screenshots encouraged)
I noticed the current autocomplete implementation is missing accessibility features, such as role and aria-selected attributes, unlike ListBox and ListBoxItem which have similar presentation and do provide these attributes. I know v2 is not a priority at the moment, but as this is a relatively simple enhancement maybe it can make it into v2. I'd be happy to try and make the PR myself.
What type of pull request would this be?
Enhancement
Provide relevant links or additional information.
No response

@LoremFooBar we would welcome a PR for this, otherwise we can certainly aim to address this as part of v3. Thanks for the heads up!

No activity on this so I'm going to consolidate it this under the v3 effort:
https://github.com/skeletonlabs/skeleton/issues/2366


Will routable engines support different location type from the host app?

I have a routable engine which I mount in 2 different applications.
In the first application I want the engine to extend host app router's location (in my case it is hash) but in the second one, i want the engine to have location type none while having location type history in the host app.
Will engines support such configuration in future?

Can you explain the use case a bit more?
Currently, the location type is per-router and since Engines share the same router as the host application your Engine's location type will be determined by the consumer. Given the existing setup, having multiple location types would be non-trivial to support.

@trentmwillis we are working on a search tool called OneBar.
The search bar which you see at landing page is our main business application to easier show it at landing website, at application website (available only to subscribed users) and at desktop electron app we decided to wrap it in routable ember engine and simply mount in different host apps.
At landing website we dont want the engine to touch page's history when routes are changing inside the engine while routes changing inside the host landing application should change the history. But at application website we want ember engine to change the history so user will be able to see the same set of searched data after the refresh of the page.
Now we accieved the desired behaviour at landing website with overriding pushState method:
   pushState() {
      let router = appInstance.lookup('router:main');
      if (!get(router, 'currentRouteName').match(/onebar-app/)) {
        this._super(...arguments);
      }
    }

which feels a very hacky.
Do you think that the problem which we solved is not uniq for us and people in the community will also face it?


Page Masthead and horizontal navigation

I would have liked a horizontal navigation page as described in Patternfly but I see that I can't eliminate the bars button.
From what I could see in the code there is no way to do this with the Page component. Or is there a way?
Marco

Maybe not right now. But if you can come up with a PR, I would be happy to merge that.

Yes, you would like to do it, but it would be the first PR ever. I have already made the change to my local copy.
I tried to create the PR but Github asks me to select a branch and I don't know which one is the right one, can you give me a tip?

main would be the correct branch.

Sorry for basic question. After click on "New Pull Request" a page "Comparing changes" appear where the button "Create Pull Request" is disabled. On the top left there are 2 selectors that show "base:main" and "compare:main". If I choose main the button "Create Pull Reqest" disappears and a message tells "There is nothing to compare".
For sure I miss some fundamental point. There are some operation to do before this step?

The typical process would be:

Fork the repo (into your own account)
Create a new (local) branch
Make local changes
git add, git commit, git push
Then create a PR, from your branch to patternfly-yew's main branch


Failed to establish a new connection: [Errno 111] Connection refused

Hi Sourab,
For some reason the program is unable to establish connection.  I tried to change the port, but that didnt work. I can see the document in the bucket (https://investors.mongodb.com/static-files/10f57c7a-a481-4663-bbc5-1cc79e36b147). Curious what am I missing? Yesterday it worked just fine. Thanks for the help.

I was able to get it running, however, I am unable to get any output from the document:

if you are running from Codespace, have you tried make your port public?


id: more housing questions

Some of these feel like they should be behind a show if. Use radio buttons for marriage status.
"Are the people in your household aware of your debt situation" -- feels better to come closer to the solution time.

Is it redundant to ask someone who has a joint tenancy or joint mortgage if they live with anyone else in their home?
I am thinking, for example, someone  may have a joint mortgage with a parent that does not live with them

Separated the family questions into more appropriate groupings


Use onClickOutside wrapper for Edit Dialog, add docs for BuilderHeaderMisc

Fixes #

The Edit Dialog now closes when a user clicks outside the component. All of the other popover variations implement this behavior already. This was done by importing from index.js (an onClickOutside wrapper for popover.js instead of popover.js itself.

Added documentation for the BuilderHeaderMisc component. It was added in https://github.com/salesforce/design-system-react/pull/2287, but the docs were never updated.

Additional description

CONTRIBUTOR checklist (do not remove)
Please complete for every pull request

[x] First-time contributors should sign the Contributor License Agreement.  If you haven't before, wait a few minutes and a bot will comment on this pull request with instructions.
[x] npm run lint:fix has been run and linting passes.
[x] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[x] Review the appropriate Storybook stories. Open http://localhost:9001/.
[x] Review tests are passing in the browser. Open http://localhost:8001/.
[x] Review markup conforms to SLDS by looking at DOM snapshot strings.

REVIEWER checklist (do not remove)

[ ] TravisCI tests pass. This includes linting, Mocha, Jest, Storyshots, and components/component-docs.json tests.
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.

Required only if there are markup / UX changes

[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

I'm seeing 2-3 failures with the browser tests (1 is a flapper, 2 of them ar combobox tests). These are also failing in master, so I assume they're not caused by my changes.


has-detailed-visible prop on table not working as expected

Overview of the problem
Oruga version: [v0.9.0-pre.2]
Vuejs version: [3.4.21]
OS/Browser: Chrome
Description

Table component prop hasDetailedVisible has no effect on the visibility of the detail icon. It's always visible and does not seem to reflect the prop.
Steps to reproduce

Construct a table with detailed element.
<o-table           narrowed           bordered           striped           hoverable           checkable            detailed           :has-detailed-visible="(row) => false"> ...
Expected behavior
Expect to not see any detail row icons on the table.
Actual behavior
detail icons are visible for all rows.

Hey, thanks for checking out the pre-release version!
This prop has been renamed to isDetailedVisible. Try this one :)
Let us know if you find any other bugs.

Thank you so much!

Another related quick question - is there a way to programatically trigger opening a detail row (like how you would in buefy with this.$refs.table.openDetailRow(row); ?
I tried using update:openedDetailed but I could not get it to work.

If you have specified the rowKey prop or given the customCompare function prop, you can specify v-model:detailedRows (openedDetailed has been renamed detailedRows to match checkedRows).
A detailed list of changes will be in the release nodes when the main 0.9 release is made (I would expect early next month).
If you want the updated docs for the 0.9 pre-release, I would suggest cloning the develop branch of the oruga repo, installing the dependencies (npm i) and running the docs for 0.9 locally with npm run dev:watch.


Sender for SOAP

Can version 2 be integrated with the RicorocksDigitalAgency\Soap package using custom senders? If yes, can you please give me an example of such a sender?
Thank you in advance!

Hey, @toughcookie!
While I feel it can be achieved, I don’t have plans to build a SOAP Sender for Saloon just yet. The way SOAP is structured is quite different to a regular REST API, and when I get to build an integration with an XML API I actually use Spatie’s “Array to XML” library which is fantastic at building quick integrations.
You can find the library here
You can use that in combination with Saloon’s HasXMLBody trait: https://docs.saloon.dev/the-basics/request-body-data
I hope that helps for now.
With regards to the SOAP sender, if you have any ideas on how you would build a sender for it I’d be happy to discuss it.

I’m closing this as a future enhancement 🙌

For anyone interested in how to integrate with RicorocksDigitalAgency\Soap, here is my version:
<?php

declare(strict_types=1);

use Exception;
use GuzzleHttp\Promise\PromiseInterface;
use GuzzleHttp\Psr7\Response as GuzzleResponse;
use Psr\Http\Message\ResponseInterface;
use RicorocksDigitalAgency\Soap\Facades\Soap;
use Saloon\Contracts\PendingRequest;
use Saloon\Contracts\Response as ResponseContract;
use Saloon\Contracts\Sender;
use SoapFault;

class SoapSender implements Sender
{
    /**
     * Send a request
     *
     * @param \Saloon\Contracts\PendingRequest $pendingRequest
     * @param bool $asynchronous
     * @return \Saloon\Contracts\Response|\GuzzleHttp\Promise\PromiseInterface
     * @throws \SoapFault
     * @throws \GuzzleHttp\Exception\GuzzleException
     * @throws \Saloon\Exceptions\Request\FatalRequestException
     */
    public function sendRequest(PendingRequest $pendingRequest, bool $asynchronous = false): ResponseContract|PromiseInterface
    {
        unset($asynchronous);
        $exception = null;

        try {

            $response = Soap::to($pendingRequest->getUrl())
                ->trace()
                ->call(
                    $pendingRequest->config()->get('method'), // set in connector/request config
                    $pendingRequest->body()->all(), // use HasJsonBody trait in connector/request and just pass array
                );
            //
        } catch (SoapFault | \Throwable $e) {
            $exception = $e;
        }

        $status = (int) \Str::betweenFirst($response->trace()->responseHeaders, 'HTTP/1.1', 'Content-Type');

        $psrResponse = new GuzzleResponse(
            status: $status,
            body: json_encode($response->return),
        );

        return $this->createResponse($pendingRequest, $psrResponse, $exception);
    }

    /**
     * Create a response.
     *
     * @param \Saloon\Contracts\PendingRequest $pendingSaloonRequest
     * @param \Psr\Http\Message\ResponseInterface $guzzleResponse
     * @param \Exception|null $exception
     * @return \Saloon\Contracts\Response
     */
    protected function createResponse(PendingRequest $pendingSaloonRequest, ResponseInterface $soapResponse, Exception $exception = null): ResponseContract
    {
        /** @var class-string<\Saloon\Contracts\Response> $responseClass */
        $responseClass = $pendingSaloonRequest->getResponseClass();

        return $responseClass::fromPsrResponse($soapResponse, $pendingSaloonRequest, $exception);
    }
}


Update Composer dependencies (2022-12-17-00-11)

Visual regression test passed!
View the visual regression test report


Java heap space error on MaltExtract

I've gotten a java heap space error with MaltExtract. We need a way to easily configure memory usage. Maybe add an -Xmx flag to the MaltExtract rule?

I close it since the issue was fixed in the previous PR


GH-2297: Default config for icon config

Closes #2297

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Remove unnecessary dependencies from our images

To reduce the potential attack surface and thus the number of vulnerabilities in our images, we should try to remove all unnecessary dependencies.
The basic idea is to look for dependencies that are not really needed at runtime and remove them.
Some vague examples:

Unneeded JAR files
System packages (maybe set install_weak_deps=0 option for microdnf?)
Packages that are needed for features that are never enabled in our platform

A good place to start might be to browse through critical vulnerabilities in SecObserve, inspect the components are affected by them and verify if they are really needed. Or to think about general options / techniques to clean up our images.

We already do set the settings to not install week dependencies. This is in the base image

Closing this as this was part of the vulnerability hackathon (my main concerns were adressed in https://github.com/stackabletech/docker-images/pull/665 and https://github.com/stackabletech/operator-templating/pull/361). We'll remove further unnecessary dependencies if we find some during vulnerability analysis, I don't think we need a general issue for this anymore.


Self triage nomination Bjarki Arge Andreasen

Nomination
GitHub User
Provide the following information about the GitHub user:
Full name: Bjarki Arge Andreasen
GitHub name: bjarki-trackunit
Organization: Trackunit A/S
Supporting Documents
Cleanup of modem driver libraries https://github.com/zephyrproject-rtos/zephyr/pull/48530
Issue with solutions to multiple APIs pr device instance https://github.com/zephyrproject-rtos/zephyr/issues/48934
Solution 1 to multiple APIs pr device instance https://github.com/zephyrproject-rtos/zephyr/pull/48817
Solution 2 to multiple APIs pr device instance https://github.com/zephyrproject-rtos/zephyr/pull/48932
Location API proposal https://github.com/zephyrproject-rtos/zephyr/pull/48536
We probably discussed at the arch and dev meetings, I'm the one with the camera on :)

Added as a contributor with triage permssion.


package missing during build

gyp verb command build []
gyp verb build type Release
gyp verb architecture arm
gyp verb node dev dir /home/rpi/.node-gyp/12.18.3
gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack     at getNotFoundError (/web/node_modules/node-gyp/node_modules/which/which.js:13:12)
gyp ERR! stack     at F (/web/node_modules/node-gyp/node_modules/which/which.js:68:19)
gyp ERR! stack     at E (/web/node_modules/node-gyp/node_modules/which/which.js:80:29)
gyp ERR! stack     at /web/node_modules/node-gyp/node_modules/which/which.js:89:16
gyp ERR! stack     at /web/node_modules/isexe/index.js:42:5
gyp ERR! stack     at /web/node_modules/isexe/mode.js:8:5
gyp ERR! stack     at FSReqCallback.oncomplete (fs.js:168:21)
gyp ERR! System Linux 5.4.51-v7l+
gyp ERR! command "/usr/bin/node" "/web/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /web/node_modules/node-sass
gyp ERR! node -v v12.18.3
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/watchpack-chokidar2/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/rpi/.npm/_logs/2020-07-28T17_31_35_685Z-debug.log
Done!

fix : apt install make
package was missing to build module

Could not replicate, does this problem still exist?

fixed by adding build-essential to Dockerfile.


2.0.0-rc13 package installation bugs out

Describe the bug
│  ERROR  Error while requiring module @nuxtjs/seo: Error: Cannot find module<EMAIL_ADDRESS>Reproduction
No response
System / Nuxt Info
No response

Hi, thanks for the issue. Could you try 2.0.0-rc.14

Looks like it's working now. Thank you for the fast update!


<IP_ADDRESS> Unable to start wsl, unable to upgrade wsl, unable to downgrade wsl

Windows Version
Microsoft Windows [版本 10.0.22621.2283]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
0.0.0
Distro Version
Ununtu 20.04
Other Software
No response
Repro Steps
Installing a Docker in a Docker Container(Because compiling without installing Docker Trust will result in an error)
curl https://get.docker.com | sh
cross build --target aarch64-linux-android --release --manifest-path ./userspace/ksud/Cargo.toml
After execution, wsl crashed and even restarting the computer couldn't start wsl
Expected Behavior
升级或者降级wsl
Actual Behavior
wsl --update --pre-release
Prompt for upgrading to <IP_ADDRESS>, but the upgrade was not successful and no error was reported

Download and install the offline installation package successfully
But the wsl version has not changed
Microsoft.WSL_<IP_ADDRESS>_x64_ARM64.msixbundle
Microsoft.WSL_<IP_ADDRESS>_x64_ARM64.msixbundle
The most important thing is that wsl cannot start
Diagnostic Logs
No response

/dupe 10574


Tests could warn, when vm.warp() was used to reduce/decrease the timestamp

Component
Forge
Describe the feature you would like
This Situation, ok I was also stupid.
I am debugging some tests, and don't know, why they fail. In the end, it was because somewhere deep in my test setups I set vm.warp(1 hours);, and in the test I wrote I set vm.warp(1);, and this lead to a underflow error.
Proposed solution:

When tests detect a warp that decreases the blocktime AND when tests fails, a hint is given that the blocktime was reduced.

If this is a bad idea, just close :-)
Additional context
No response

An alternative solution that should be simpler to implement is to have forge revert if you warp/roll to an earlier timestamp/block. I can't think of a valid use case for that, and if there is one we can add a config flag to disable this behavior

Agree, that's better.


Documentation about onboarding new connectors (DistributedIdentity)

This PR adds sequence diagrams and accompanying documentation about the following flows:

onboarding new connectors, issuing verified credentials/claims
verifying those claims

Those flows are only valid in a distributed identity scenario, which uses DIDs and Identity Hubs[
Adapting the registration-service and registration-service-api will be done in a subsequent PR, this serves merely as basis for discussion.

@bscholtes1A please take a look if this scheme fits your needs.


Private Story Likes: Addding method for downloading users who liked your story

Provide us a use case of the feature
In February 2022, Instagram added the "Private Story Likes" feature, enabling users to like each other's stories. These likes are private, but it is possible for the recipient to see a list of usernames who have liked their particular story in the Instagram App. I propose the feature to download the users who have liked a user's own story.
Describe the solution you'd like
I propose a method, ".get_likes()", added to the user story item class (StoryItem). It would work like the post.get_likes() method.
Describe alternatives you've considered
Currently, Instaloader does not have a way to do this that I am aware of.
If the feature request is accepted, would you be willing to submit a pull request?
Yes.

Yes, this feature would be nice to have!


❓ questions

          > > > ❓ codeql.yml

❓ 📘 why do I have to review an earlier version of this documentation when I have already approved the newer version?
❓ 📘 isn't there a way to compile these documentation changes into one PR?

❓ 📘 if I modify the actions rulesets to exclude repositories other than main, minor-x, and minor-2, then will that slow the notifications that subscribers receive? changed the rulesets. testing...

Originally posted by @eeshvardasikcm in https://github.com/eeshvardasikcm-workflow/version-support/issues/27#issuecomment-2144578801

LICENSE change #54


Increase test coverage and overall test quality

This is an issue to track a big effort to improve our test suite. Please, open smaller, more specific issues for this and link them to this one.

Closing as this has been superseded by changes to our overall testing approach and infastructure.


update triangles to conform with style guide

Triangle facts exercise

Two suggestions, but no need to resubmit. Well done.


⚠ Burdi - Selfservice has degraded performance

In ce6fd95, Burdi - Selfservice (https://manage.burdi.com.au) experienced degraded performance:

HTTP code: 200
Response time: 17302 ms

Resolved: Burdi - Selfservice performance has improved in 595896e.


MSVCR120.dll not found

When I installed the prebuilt version for windows, an error message popped up stating that the DLL MSVCR120 was missing on my computer. As I found out, this particular DLL is installed with the Visual C++ Redistributable Packages für Visual Studio 2013. All the newer versions, even the ones included in the installation, do not install this DLL.
So could you please force an installation of the Visual C++ Redistributable Packages für Visual Studio 2013 for your pre built windows installer.

I'm sorry, but I don't have windows: (

Just download the Visual C++ 2013 package, this install the missing MSVC120.Dll (a reboot may be required):
https://support.microsoft.com/en-us/help/4032938/update-for-visual-c-2013-redistributable-package


PROD: utf-8 characters in filenames

see ../runden/WÜ_35.xlsx .... the "Ü" is show as 2byte utf octet
should use $name= utf8_decode(htmlspecialchars_decode($name));

using just Str::slug() to adjust club and league shortnames