[core] Remove withStyles from @material-ui/core/styles

BREAKING CHANGE
The withStyles JSS utility is no longer exported from @material-ui/core/styles. You can use @material-ui/styles/withStyles instead. Make sure to add a ThemeProvider at the root of your application, as the defaultTheme is no longer available. If you are using this utility together with @material-ui/core, you should use the ThemeProvider component from @material-ui/core/styles instead.
-import { withStyles } from '@material-ui/core/styles';
+import { withStyles } from '@material-ui/styles';
+import { createTheme, ThemeProvider } from '@material-ui/core/styles';

+const defaultTheme = createTheme();
 const MyComponent = withStyles((props) => {
   const { classes, className, ...other } = props;
   return <div className={clsx(className, classes.root)} {...other} />
 })(({ theme }) => ({ root: { background: theme.palette.primary.main }}));

 function App() {
-  return <MyComponent />;
+  return <ThemeProvider theme={defaultTheme}><MyComponent /></ThemeProvider>;
 }

This was the last dependency on @material-ui/styles, we can remove it now from @material-ui/core.

Looks like failing codemods is the last issue we need to solve - https://app.circleci.com/pipelines/github/mui-org/material-ui/42518/workflows/a47a4fe4-83ea-4651-9aa3-05427294135f/jobs/254836
@oliviertassinari @mbrookes what is the expected thing here?


Add Page Modules concept for integration tests

This is an experiment in using Page Modules (ala Page Objects) for feature tests. What do y'all think?

These look really great! If you're using the most recent version then you can swap a lot of your calls to Browser.find to force the browser to block with Browser.assert_has. assert_has is chainable so you don't have to worry about returning the session explicitly.

OMG I ❤ this @jbranchaud
After updating some deprecation warnings in the tests I realized they were too hard to parse to just get the general sense of what the test does. This would fix that. 👍 from me.

Thank you! 👍


Removing Native-base from a React Native project

Are there any instructions to remove Native Base from a project I tried it on, please?
I tried npm uninstall native-base but the the project.pbx still has tons of references that causing the build to fail.
For example
62D9CE01C81042789D08256D /* Andale Mono.ttf */ = {isa = PBXFileReference; name = "Andale Mono.ttf"; path = "../node_modules/native-base/Fonts/Andale Mono.ttf"; sourceTree = "<group>"; fileEncoding = undefined; lastKnownFileType = unknown; explicitFileType = undefined; includeInIndex = 0; };
		D73C6061F7E64AA392F2A5D4 /* Arial Black.ttf */ = {isa = PBXFileReference; name = "Arial Black.ttf"; path = "../node_modules/native-base/Fonts/Arial Black.ttf"; sourceTree = "<group>"; fileEncoding = undefined; lastKnownFileType = unknown; explicitFileType = undefined; includeInIndex = 0; };

Is there some what to clean this up, pls?

OK, I think I got it worked out ... I ran npm uninstall native-base before react-native unlink native-base. You have to run the unlink first.

Unlink
npx react-native unlink native-base
or
npm react-native unlink native-base
...then uninstall
npm uninstall native-base


[core] Incorrect niavigation to method after adding comment to method

After decompiling and add any comment to any method, navigation breaks between methods (Ctrl+LBM).
Namely, the transition to the method is shifted to several rows higher than the desired method.

@amspeople fixed. Please check.


Ensure no NULL tags are set

Because mpd_song_get_tag from libmpdclient can return NULL, verify the
value of tag is valid. Otherwise, set a default string of "N/A". Also
adds configuration to specify what this default string should be.
Additionally, fix compile-time warning of catch by value.
Closes #273 (I'll file another issue on the segfault at mpd_status_get_state,
unless we want to keep conversation there)
P.S. Thoughts appreciated on the config name "unknown-tag"; for some
reason it just doesn't jive with me, though it's fairly descriptive of what it does.
I'll update the wiki once this gets merged.
EDIT: It appears you guys are using Conventional Commits style (or
something similar). Should I fix my commits to reflect that?

Thanks!


play-swagger no longer available in mvnrepository

I just ran a build for a project which uses this dependency, and it's no longer present in maven repository.
https://repo1.maven.org/maven2/com/iheart/

It's not here at all: https://mvnrepository.com/search?q=sbt-play-swagger&d=com.iheart
And https://dl.bintray.com/sbt/sbt-plugin-releases/com.iheart/sbt-play-swagger/ contains no version for scala_2.13 but only:

scala_2.10/
scala_2.12/


Draft: Add ACL group read interface - By @tchu and @lsitu.

Add interface for group read.
Basing on our discussions, Vivian and I think we only can start with assuming we've got the ACL for a Valkyrie::Resource. It seems like Margret's PR #3 could be a good feed to retrieve the ACL.

this looks like a good start
@lsitu @VivianChu: was there something about this in particular you were looking for feedback about?

@no-reply Yes, thanks.
We also have the following questions that want to clarify:

Should the ACL checker interface be more user friendly to check permission for a Valkyrie resource instead of the AccessControll instant of  Valkyrie resource?
Do we need to differentiate the  checker interface for group permission and personal permission? We currently named the example method has_read_group, however, it doesn't reflect any group context in the implementation at this time. It'll be more general for method has_read_grant if we don't need to take care of the group agent context.
Should we include checker interface for other permissions like discover, edit etc?

CC: @VivianChu

Should the ACL checker interface be more user friendly to check permission for a Valkyrie resource instead of the AccessControll instant of Valkyrie resource?

i think keeping with the pattern we use for writes is appropriate. in principle, a Valkyrie Resource doesn't have one single set of permissions, the relationship is in the other direction: AccessControl and Permission resources each have a Valkyrie Resource they relate to. for this reason, implementing the DSL directly on Resource is more rigid than is likely to work in general. Hyrax::AccessControlList gets to respect Hyrax's assumptions about how resources are handled without imposing those assumptions elsewhere.
did you have an approach in mind that is more user friendly than Hyrax::AccessControlList(resource)?

Should we include checker interface for other permissions like discover, edit etc?
yes, the implementation should be general over any mode symbol.

@no-reply @marrus-sh Thank you both for your review comments. I think that answers all the questions.

did you have an approach in mind that is more user friendly than Hyrax::AccessControlList(resource)?
No. Just thinking about what the writer interface looks like and how it'll affect the checker interface.


RFC: Add options block so that webpack 2.6 won't complain

Also, I had to include autoprefixer in the list of plugins to get it working here.

This change is

@ened can you paste the error you see without this? If you want to upgrade the webpack (and other library versions), then please put all into this PR.

@justin808 - in the end, this might not even be web pack related, but is an artifact (during previous merges). I noticed it worked with the spec/dummy/Procfile.hot right away, which had this fixed.
Typical error messages are:

Module build failed: ModuleBuildError: Module build failed: Error: No PostCSS Config found in ...

@ened What shall we do with this PR?

@ened Please get back to me on this one and let me know if we should re-open this PR.


Add extension to send events to NATS broker

This PR adds support to publish events to NATS broker from Streampipes [1].

Fixes: https://issues.apache.org/jira/browse/STREAMPIPES-354
This PR only provides support for the NATS broker. It would be good to add support for the NATS streaming broker as well, but that specific project will be deprecated, and there is an upgraded streaming broker called "JetStream" is at the tech-preview level. I'll send a PR for that support once it is graduated.
[1] https://nats.io/

@grainier @wipatrick @dominikriemer


feat:(FSADT1-664): adding native support

Description
Adding support to native image builds
Fixes FSADT1-664
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have already been accepted and merged

Further comments

Thanks for the PR!
Any successful deployments (not always required) will be available below.
API available
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Just a few caveats from this change to let both @mishraomp and @DerekRoberts aware of.

Native images got a few issues with reflection, so keep in mind some reflection-based code can backfire. You can generate some files to help the native image find out about your reflection code but it can fail your build depending on what you're using.
Webflux Functional doesn't work properly with native images, keep up with annotation-based endpoints for now (depending on what you're doing, you can do the trick I mentioned above, but I don't recommend it for now)
Oracle certificates were a pain, but it's an easy fix, you can pass the certificate path through a query string and you can use an init container to extract the certificate for you
Swagger works fine but only with annotation-based endpoints. For some reason, it failed while testing the endpoint through swagger, but when testing using postman worked just fine
It takes a lot of time to build, but it is worth it. It's better to set a few parameters in the pom to set some of the buildpacks, labels and version
6 - For now, it's not possible to turn this build part into action as it requires some environment variable settings. Maybe we can try in the future to pass it as environment variables and see how it goes
7 - It looks like it's not using the distress build, but the ubuntu one, we can try to rework this in the future if it becomes a problem

whats the startup time for the actual container (not including the init one) and the CPU and memory stats? @paulushcgcj

whats the startup time for the actual container (not including the init one) and the CPU and memory stats? @paulushcgcj

The startup time is between 0.7 and 1.9 seconds. I think we will not be able to reduce it even more due to database checks that the oracle client does when booting up. Other factors such as flyway can also delay the startup time, but we can expect (even with flyway) less than 2 seconds of startup time.
In terms of resource usage

@paulushcgcj thanks for the stats, the startup time is great,  I think the spring boot team needs to do some work around the memory, 128 is high for a native one.

@paulushcgcj thanks for the stats, the startup time is great, I think the spring boot team needs to do some work around the memory, 128 is high for a native one.

True. It could be due to connection pools and webflux thread pools as well, but for now, it is something to be discussed with them.


docs: point resources to v3 instead of master

update urls to use v3 branch instead of master

Codecov Report

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

@@          Coverage Diff          @@
##             v3    #3899   +/-   ##
=====================================
  Coverage      ?   96.36%
=====================================
  Files         ?       45
  Lines         ?     2281
  Branches      ?      640
=====================================
  Hits          ?     2198
  Misses        ?       80
  Partials      ?        3

Continue to review full report at Codecov.

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


Save data erased after updating games

Games losing save data after updating
I just did the normal method of going to the installed apps section and upon updating Blaston (2 days ago) and In Death: Unchained (today) I opened the games to find that none my other saves were there.
Running :

OS: Windows
Version v0.0.6-alpha

The data backup and restore does not work for all games, so im not sure about blaston, HOWEVER, for "in death" it should update normally without losing data i think it just stores in "com.Solfar.InDeath", unless it has changed to "internal data" recently
ill do a test myself tmrw with that specific title, thx for reporting.

hi srry due to lack of hmd i havent been able to test it yet , but someone else has reported the same thing, and there is also something fishy going on with the versionnumbers as far as in death goes...   so no progress so far,  but not forgotten

Could you please retry using v0.0.10
https://github.com/whitewhidow/quest-sidenoder/releases/tag/v0.0.10
thx and sorry for the slow reply

Please check if fixed in
https://github.com/whitewhidow/quest-sidenoder/releases/tag/v0.0.12

Can confirm that the issue is still there. Updated In Death on v0.0.12 to have all save files be deleted from data folder.

Can confirm that the issue is still there. Updated In Death on v0.0.12 to have all save files be deleted from data folder.

I just tested this myself..
the following files are backed up and restored:
doing adb pull appdata (ignore error)
pull: building file list...
[ 29%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/Settings.sav: 100%
[ 49%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/General.sav: 100%
[100%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/PlayerProgressGD.sav: 100%
/sdcard/Android/data/com.Solfar.InDeath/: 3 files pulled. 0.0 MB/s (6034 bytes in 0.255s)
doing adb uninstall (ignore error)
Success
doing adb push appdata (ignore error)
[ 50%] /PlayerProgressGD.sav: 100%
[ 80%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/Settings.sav: 100%
[100%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/General.sav: 100%
/tmp/sidenoder_restore_backup/com.Solfar.InDeath/files/: 3 files pushed. 1 file skipped. 0.3 MB/s (6034 bytes in 0.017s)
Confirmed afterwards that the files are present
adb shell ls /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames
General.sav
PlayerProgressGD.sav
Settings.sav
and the savegame is also still present for me ..
not sure what could be going wrong for you ....  any chance you still have the game running while trying to update or something?
As it most certainly seems to work fine for 99% of the users, including myself

I just tested this myself..
the following files are backed up and restored:
doing adb pull appdata (ignore error)
pull: building file list...
[ 29%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/Settings.sav: 100%
[ 49%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/General.sav: 100%
[100%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/PlayerProgressGD.sav: 100%
/sdcard/Android/data/com.Solfar.InDeath/: 3 files pulled. 0.0 MB/s (6034 bytes in 0.255s)
doing adb uninstall (ignore error)
Success
doing adb push appdata (ignore error)
[ 50%] /PlayerProgressGD.sav: 100%
[ 80%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/Settings.sav: 100%
[100%] /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames/General.sav: 100%
/tmp/sidenoder_restore_backup/com.Solfar.InDeath/files/: 3 files pushed. 1 file skipped. 0.3 MB/s (6034 bytes in 0.017s)
Confirmed afterwards that the files are present
adb shell ls /sdcard/Android/data/com.Solfar.InDeath/files/cloud/data/SaveGames
General.sav
PlayerProgressGD.sav
Settings.sav
and the savegame is also still present for me ..
not sure what could be going wrong for you ....  any chance you still have the game running while trying to update or something?
As it most certainly seems to work fine for 99% of the users, including myself

Interesting. I will test some more

Interesting. I will test some more

also,  just for info, in case it is usefull somehow,
after updating, there should also be a folder named 'sidenoder_restore_backup' left inside your machines TMP folder (location depends on your os), this folder should also hold a backup of the data that has been backed up and restored.
These are the files that are placed back onto the headset, manually restoring these should also restore your data. (but this is the process that should already have been taken done sidenoder, but worth a shot to test)

also,  just for info, in case it is usefull somehow,
after updating, there should also be a folder named 'sidenoder_restore_backup' left inside your machines TMP folder (location depends on your os), this folder should also hold a backup of the data that has been backed up and restored.
These are the files that are placed back onto the headset, manually restoring these should also restore your data. (but this is the process that should already have been taken done sidenoder, but worth a shot to test)

I did backup manually but I also did find the folder with backups that you spoke of.
Not sure why it is not working for me. I installed an older version dropped in my saves and updated. Same issue, no save files. Game was not running during the update.
Not sure if it only happens for this game or for the others as well for me, this was the only one that needed an update and had save files.

I did backup manually but I also did find the folder with backups that you spoke of.
Not sure why it is not working for me. I installed an older version dropped in my saves and updated. Same issue, no save files. Game was not running during the update.
Not sure if it only happens for this game or for the others as well for me, this was the only one that needed an update and had save files.

any chance you could run the NPM version ?
(this will show actual errors in the concole) (im suspecting a windows-related backslash-issue here)

any chance you could run the NPM version ?
(this will show actual errors in the concole) (im suspecting a windows-related backslash-issue here)

Sure, I can do that. What and where should I be looking for?

Sure, I can do that. What and where should I be looking for?

Instructions for running with npm (instead of the exe) are here :
https://github.com/whitewhidow/quest-sidenoder#manually-run-using-node-on-windows
(if you end up needing manual help with this: https://discord.gg/pVMsAyYhAf)

Instructions for running with npm (instead of the exe) are here :
https://github.com/whitewhidow/quest-sidenoder#manually-run-using-node-on-windows
(if you end up needing manual help with this: https://discord.gg/pVMsAyYhAf)

Running is not the issue, more of where to look for the necessary info.
I found this, if you need something else do let me know where to look for it.
attempting to read package info
package info read success (com.Solfar.InDeath)
checking if installed
exec_stdout
package:com.Solfar.InDeath
doing adb pull appdata (ignore error)
exec_stdout
/sdcard/Android/data/com.Solfar.InDeath/: 4 files pulled, 0 skipped. 0.7 MB/s (19359 bytes in 0.028s)
doing adb uninstall (ignore error)
exec_stdout
Success
doing adb push appdata (ignore error)
exec_stderr
exec_error
exec_stdout
adb: error: cannot stat 'C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/*': No such file or directory
doing adb install
is remote, copying to C:/Users/vitvk/AppData/Local/Temp/In Death - Unchained [<IP_ADDRESS>764052] S2.11.apk
exec_stdout
Performing Streamed Install
Success
exec_error
exec_stderr
'rm' is not recognized as an internal or external command,
operable program or batch file.
DATAFOLDER to copy:com.Solfar.InDeath
doing obb rm
exec_error
exec_stderr
rm: /sdcard/Android/obb/com.Solfar.InDeath: No such file or directory
C:/Users/vitvk/AppData/Local/Temp/com.Solfar.InDeath already exists
obb File: C:/Users/vitvk/AppData/Local/Temp/mnt/In Death - Unchained v29764052+1.2.7 -QU -versionCode-29764052 -packageName-com.Solfar.InDeath -steam-605450/com.Solfar.InDeath/main.29764052.com.Solfar.InDeath.obb
doing obb push
obb is remote, copying to C:/Users/vitvk/AppData/Local/Temp/com.Solfar.InDeath/main.29764052.com.Solfar.InDeath.obb
exec_stderr
doing shell mv
exec_stderr
DONE

Running is not the issue, more of where to look for the necessary info.
I found this, if you need something else do let me know where to look for it.
attempting to read package info
package info read success (com.Solfar.InDeath)
checking if installed
exec_stdout
package:com.Solfar.InDeath
doing adb pull appdata (ignore error)
exec_stdout
/sdcard/Android/data/com.Solfar.InDeath/: 4 files pulled, 0 skipped. 0.7 MB/s (19359 bytes in 0.028s)
doing adb uninstall (ignore error)
exec_stdout
Success
doing adb push appdata (ignore error)
exec_stderr
exec_error
exec_stdout
adb: error: cannot stat 'C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/*': No such file or directory
doing adb install
is remote, copying to C:/Users/vitvk/AppData/Local/Temp/In Death - Unchained [<IP_ADDRESS>764052] S2.11.apk
exec_stdout
Performing Streamed Install
Success
exec_error
exec_stderr
'rm' is not recognized as an internal or external command,
operable program or batch file.
DATAFOLDER to copy:com.Solfar.InDeath
doing obb rm
exec_error
exec_stderr
rm: /sdcard/Android/obb/com.Solfar.InDeath: No such file or directory
C:/Users/vitvk/AppData/Local/Temp/com.Solfar.InDeath already exists
obb File: C:/Users/vitvk/AppData/Local/Temp/mnt/In Death - Unchained v29764052+1.2.7 -QU -versionCode-29764052 -packageName-com.Solfar.InDeath -steam-605450/com.Solfar.InDeath/main.29764052.com.Solfar.InDeath.obb
doing obb push
obb is remote, copying to C:/Users/vitvk/AppData/Local/Temp/com.Solfar.InDeath/main.29764052.com.Solfar.InDeath.obb
exec_stderr
doing shell mv
exec_stderr
DONE

thx,   so this first part seems to succe3ssfully PULL the data from the device:

doing adb pull appdata (ignore error)
exec_stdout
/sdcard/Android/data/com.Solfar.InDeath/: 4 files pulled, 0 skipped. 0.7 MB/s (19359 bytes in 0.028s)

But then the following part seems to fail when trying to pull them back onto the device after the uninstall:

exec_error
exec_stdout
adb: error: cannot stat 'C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/*': No such file or directory

is the directory C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/ not the correct path to where it saved the backup ?
also,   what happens when you manually try to push the backup data using:
adb push C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/* /sdcard/Android/data/com.Solfar.InDeath/
Does this indeed fail the same way (it should, as this is the command used)?
then, please check what happens when quotes are added as so :
adb push "C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/*" "/sdcard/Android/data/com.Solfar.InDeath/"
Do these quotes fix the issue on windows ?
thx in advance.

thx,   so this first part seems to succe3ssfully PULL the data from the device:

doing adb pull appdata (ignore error)
exec_stdout
/sdcard/Android/data/com.Solfar.InDeath/: 4 files pulled, 0 skipped. 0.7 MB/s (19359 bytes in 0.028s)

But then the following part seems to fail when trying to pull them back onto the device after the uninstall:

exec_error
exec_stdout
adb: error: cannot stat 'C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/*': No such file or directory

is the directory C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/ not the correct path to where it saved the backup ?
also,   what happens when you manually try to push the backup data using:
adb push C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/* /sdcard/Android/data/com.Solfar.InDeath/
Does this indeed fail the same way (it should, as this is the command used)?
then, please check what happens when quotes are added as so :
adb push "C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/*" "/sdcard/Android/data/com.Solfar.InDeath/"
Do these quotes fix the issue on windows ?
thx in advance.

If I do something like these it works:
adb push C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/ /sdcard/Android/data/

and is the data actually indeed properly restored after this ?
If so, i will make the change and build a new release
thx again

If I do something like these it works:
adb push C:/Users/vitvk/AppData/Local/Temp/sidenoder_restore_backup/com.Solfar.InDeath/ /sdcard/Android/data/

and is the data actually indeed properly restored after this ?
If so, i will make the change and build a new release
thx again

Looks like it. Booted the game, saves are there.

Looks like it. Booted the game, saves are there.

Looks like it. Booted the game, saves are there.

thx,
Could you please verify that it works in compiled build v0.0.13 (pre-release):
https://github.com/whitewhidow/quest-sidenoder/releases/download/v0.0.13/sidenoder-win-x64-exe.zip
if so, i will promote it to stable so that everyone gets the update prompt.

Looks like it. Booted the game, saves are there.

thx,
Could you please verify that it works in compiled build v0.0.13 (pre-release):
https://github.com/whitewhidow/quest-sidenoder/releases/download/v0.0.13/sidenoder-win-x64-exe.zip
if so, i will promote it to stable so that everyone gets the update prompt.

I updated and my saves were there.
Thank you.

I updated and my saves were there.
Thank you.

thx,  fixed in stable release https://github.com/whitewhidow/quest-sidenoder/releases/tag/v0.0.13
closing ticket

thx,  fixed in stable release https://github.com/whitewhidow/quest-sidenoder/releases/tag/v0.0.13
closing ticket


Add Locale

Add Locales 'de' for Germany

Hi Arengard, I'm interpreting this as a feature request?
Right now, the possible locales come from the fake crate, which don't have a Germany locale.
I don't know German, and wouldn't be the best person to implement this. If you raise an issue to discuss adding German on the fake-rs github I would be more than happy to support de if it were supported in fake-rs. The code wouldn't be particularly complicated to add to fake-rs, the work is more to source a good amount of plausible German data. They would probably be very open to your contributions if you were willing to help with that.


Support resilient values.

Specifically LLDB now calls into Remote Mirrors to determine whether a
resilient value that is stored in a fixed-size buffer is stored inline
or not.
rdar://problem/48018240
(cherry picked from commit afed7caf4365afc36fe319c9e9d5cd3bd8ca5006)

test with https://github.com/apple/swift/pull/23622
@swift-ci test


how to remove mask results on inference_demo.py with mask_RCNN

hello,
I want to remove my mask result when making inference with mask-RCNN, with only bounding box been shown.
is it possible to do this?
Thank you!

remove segmentation results from result
https://github.com/open-mmlab/mmdetection/blob/a1cecf63c713c53941b8dcf8a9d762baf8511f2c/mmdet/models/detectors/base.py#L303

Feel free to reopen the issue if there is any question

this is a similar question @jshilong, how do I return the bounding boxes parameters so I can save them in a txt file for each image?


Functions names in a relatively large shared library are not shown in cpu profile

Originally reported on Google Code with ID 622
What steps will reproduce the problem?
1. Build a dynamic linking library with -g and -fno-pie.
2. Build an executable that is also compiled with -g and -fno-pie, and also linked
with the library with -g.
3. Link to libprofiler. ProfilerStart/ProfilerStop in the executable, then pprof --pdf
<application> <profile> > a.pdf

What is the expected output? What do you see instead?

Expected: All function names are retrieved from the dynamic library and demangled names
are shown in the profile.
Actual: Many function names in the shared library are shown as physical addresses like
"00007f54c09cbbf7"

What version of the product are you using? On what operating system?
Fedora 20, x86_64.
gcc 4.8.2. libunwind 1.1.3.
Tried two versions of gperftools
 1. gperftools/gperftools-devel-2.1.4-fc20.x86_64 (from the repo)
 2. gperftools 2.2, build from source myself.

Please provide any additional information below.

Both the shared library and the executable have debug symbols. Attached nm results
as well as the profile.

When I build the library as a static library and link the executable to it, I can get
the correct function names.

I tried several things, but no avail so far.
I guess it's related to the following issues.
  https://code.google.com/p/gperftools/issues/detail?id=562
  https://code.google.com/p/gperftools/issues/detail?id=586
So, I tried -fno-pie and the newest gperftools (2.2) from source build.
Nope, the problem is still there.

The symptoms described in Issue 586 seem quite similar to what I get.
This problem happens only with shared library.
I didn't have this issue until my shared library became relatively big (8MB).
I had no problems using gperftools/pprof otherwise.

It seems like gperftools fails to retrieve symbols from shared libraries for some reason.
I vaguely remember there is some option to get gperftools into verbose mode and describe
what symbols/why it couldn't load, is there?

The workaround so far is to build the library as a static library when I want to profile,
but not ideal:-(

Reported by hideaki.kimura on 2014-05-15 18:28:26

 * *Attachment: [exec.nm](https://storage.googleapis.com/google-code-attachments/gperftools/issue-622/comment-0/exec.nm)*
 * *Attachment: [lib.nm](https://storage.googleapis.com/google-code-attachments/gperftools/issue-622/comment-0/lib.nm)*
 * *Attachment: [tpcb_experiment.prof](https://storage.googleapis.com/google-code-attachments/gperftools/issue-622/comment-0/tpcb_experiment.prof)*

Closing this as perl pprof implementation is deprecated in favor of golang version at github.com/google/pprof


--disableChecks throws error

If I run protractor as
$> ./node_modules/./bin/protractor protractor-conf.js

It just works fine. But if I do:
$> ./node_modules/./bin/protractor protractor-conf.js --disableChecks
[14:42:47] E/configParser - Error code: 105
[14:42:47] E/configParser - Error message: failed loading configuration file ./tests/protractor.conf.js
[14:42:47] E/configParser - UNKNOWN_OPTION: Unknown option: --disableChecks

I managed to find the piece of code which throws the error: ./node_modules/protractor/build/configParser.js:
/**
 * Public function specialized towards merging in a file's config
 *
 * @public
 * @param {String} filename
 */
addFileConfig(filename) {
    if (!filename) {
        return this;
    }
    let filePath = path.resolve(process.cwd(), filename);
    let fileConfig;
    try {
        fileConfig = require(filePath).config;
    }
    catch (e) {
        throw new exitCodes_1.ConfigError(logger, 'failed loading configuration file ' + filename, e);
    }
    if (!fileConfig) {
        throw new exitCodes_1.ConfigError(logger, 'configuration file ' + filename + ' did not export a config object');
    }
    fileConfig.configDir = path.dirname(filePath);
    this.addConfig_(fileConfig, fileConfig.configDir);
    return this;
}

it is the require(filePath) which fails, but in both cases the filePaths are identical.
Node version: 7.4.0, Protractor version: 5.0.0, macOS Sierra 10.12.2

After some research I noticed it has nothing to do with protractor, but with something I did in the config itself


Block tag changes found at "minecraft:blocks/mineable/pickaxe" not loading because of JSON error

There's an extra comma at the end of the list of tag additions in the file, causing it to error in the log and not load at all.
Alex's Abnormalities 1.2.3
Minecraft 1.18.2

I've also discovered that in that same file, the entries for shingle stairs and walls(for crocodile scutes and spiked scutes) are incorrect and have an extra 's' at the end of the word 'shingle'.
Instead of these,

"alexsabnormalities:crocodile_scute_shingles_stairs",
"alexsabnormalities:crocodile_scute_shingles_wall",
"alexsabnormalities:spiked_scute_shingles_stairs",
"alexsabnormalities:spiked_scute_shingles_wall"

it should be this:

"alexsabnormalities:crocodile_scute_shingle_stairs",
"alexsabnormalities:crocodile_scute_shingle_wall",
"alexsabnormalities:spiked_scute_shingle_stairs",
"alexsabnormalities:spiked_scute_shingle_wall"


[modify][gws] user occupation refinements

Coverage: 82.957% (-0.005%) from 82.963% when pulling 3513ddf17d026768aef7c839ba8869c7a27bcadf on pr-gws-user_occupation into 8fec17445d6613e441f930d3f026440ed942a39e on master.


Publish-BcContainerApp fails when app has a certain size

Describe the issue
When publishing our main app (65mb) to a cloud sandbox into dev scope we get an unexpected (and unspecific) error.
Scripts used to create container and cause the issue
$authContext = New-BcAuthContext `
    -clientID $entraApp.clientID `
    -clientSecret $entraApp.clientSecret `
    -tenantID $tenantId

Publish-BcContainerApp `
    -bcAuthContext $authcontext `
    -environment $environment `
    -appFile "$App"

Full output of scripts
Attempting authentication to https://api.businesscentral.dynamics.com/.default u
sing clientCredentials...
Authenticated as app {guid}
Publishing {our_AppName} to https://api.businesscentral.dynamics
.com/v2.0/{our_environment}/dev/apps?SchemaUpdateMode=forcesync
Exception when calling "GetResult" with 0 argument(s): "Error sending the request.
of the request."
Error sending the request.
The underlying connection was closed: Unknown error

Additional context
We are using service to service auth, which you said wouldn't be possible in a comment under one of your blog posts but the app will still be published and installed despite the error message, it just takes around 10-15 minutes.
We created the app registration as shown in the guide (API.ReadWrite.All, Automation.ReadWrite.All, admin consent granted) and successfully added an entry in the business central entra applications page. Authentication works fine and all of our other apps (way smaller, around 100kb-25mb) don't run into this issue and get published/installed just fine.
Maybe I looked in the wrong places but I couldn't find limitations on the file size except for SOAP services (65,536 kilobytes) which seems to match our app but surely this isn't the problem at hand.
The error stems from the GetResult() method when sending the request to publish the app and I played around with the timeout and other httpHandler properties but that's where my research ended.
As a workaround I created a loop which checks every minute if the app is installed and while this works I would like to know if an app this large is the problem in general or if there really is some kind of problem either in the containerHelper or in Microsoft's handling of the request in the backend.
Do you know of any limitations regarding app file sizes when publishing to cloud environments or could this really be some sort of bug?

Hi there,
I was just wondering if there are any feedback on this issue yet, as I have another partner that is experiencing the same issue as described above. Your feedback in this regard will be greatly appreciated.
Greetings,
Berny During
PTS - BC / MCT Companial

Sorry, didn't see this issue - if possible, I would like to get my hands on an app, which causes this issue - then I can troubleshoot this.
thanks

I tried to make a repro here https://github.com/microsoft/bcsamples-bingmaps.pte/actions/runs/8153202748 - but that doesn't fail.
Please create a repro scenario and provide me with an app and a script which which fails to upload using publish-bccontainerapp.
Thanks

Hi Freddy,
Facing this issue, please let me know where can I send you copy of the extensions to test it from your side.
Thank you
Eclipses

You can email a download link to freddyk at microsoft dot com and I will try to repro this.

On this issue, I did get an app from @eclipses, which failed publishing.
This was a simple out-of-memory exception though - 7Gb was allocated to the container and publishing the app required ~12Gb.
I don't think this is problem from @CriticalMax or @bernyd123 - so if I am to investigate this - I still need something to reproduce this problem.
Without a repro I can spend 100s of hours looking at code without ever finding the reason.

@CriticalMax - on this

We are using service to service auth, which you said wouldn't be possible in a comment under one of your blog posts but the app will still be published and installed despite the error message, it just takes around 10-15 minutes.

When you publish using s2s - you will NOT publish into dev scope - it will publish into global (PTE) scope - just FYI (which you also can see on the URL (api.businessce....)

Hi there Freddy,
Sorry this time it was me to miss the message... I will get the partner to reply to you on here.
Greetings,
Berny


Curriculum update needed on command_line_basics.md

The Odin's file, command_line_basics.md is updated. Please update the Kampus' file, checkout file here command_line_basics.md
Latest commits:

Foundations: unify descriptions replacing WSL with WSL2 to be specific (#27130) (additions: 17, deletions: 15) on Jan 16 2024, 16:02 UTC

Dublicated issue


Include bootstrap-utilities.scss in release

I'm working on a project that only uses Bootstrap utilities and the Bootstrap grid, so I tried importing the bootstrap/scss/bootstrap-utilities file. However, it turned out that this specific file is not included in the latest Bootstrap release, so I'm stuck manually re-implementing its functionality in my project.
Bootstrap's modularization is immensely helpful in building apps with a low CSS footprint and including the utilities file soon would make it even easier for people to use only the Bootstrap code that they need.
I would be happy to make a PR that moves these files to the v4-dev branch if necessary.

Well, this is in master which is unreleased. It'll be in v5.0.0.


[2.0] New content for templating: Create your own templates for dotnet new

Title: Create your own templates for dotnet new
Area: docs/core/tools
Reference: How to create your own templates for dotnet new

Should we call it create custom templates for dotnet new perhaps?
@sayedihashimi do we have data on search terms for the blog post? also, any preferences on whether you'd like to see this topic under Tutorials or under Tools?
Thanks!

I was too folksy there. :smile: ... but I was following @sayedihashimi's lead.
Title updated.

@sayedihashimi ... We'll try a 1st draft for this under core/tools and make it a reference-style doc that links to your blog post (as opposed to making this a tutorial/walk-through). Later, there might be a core/tutorials topic closer to how to go with your blog post. For right now tho, we'll just link to you if that's ok.

This work has been moved to https://github.com/dotnet/docs/pull/2495.


Publish fails if subdir is set to /

/ means root dir, which is valid, but our input validation prevents it.

taking a look


Output the name of the corresponding step, scenario, feature or suite when a failure on a hook is recorded

When using the --progress formatter there may be was a situation where a test failed in an after or before hook. The information printed to the output may not be enough to diagnose the issue because we are just told which hook function failed but not the related step, scenario, feature or suite.
When printing out the failed hooks, we should print:

For beforeStep or afterStep hooks, the name of the step where the failure happened
For beforeScenario or afterScenario hooks, the name of the scenario where the failure happened
For beforeFeature or afterFeature hooks, the name of the feature where the failure happened
For beforeSuite or afterSuite hooks, the name of the suite where the failure happened

Related to https://github.com/Behat/Behat/pull/1392 and https://github.com/Behat/Behat/issues/842

My only thought is for the step-level hooks it would still help to have more context than just the step, since the same step will probably be used in multiple places and the hook failure could well relate to specific scenarios / features.
It might be enough to give just path/to/feature.feature:23 in all cases, similar to how the file & line get rendered for failures at the end of the progress printer?

Ah, yes that might be the best option


Bugfix: reduce memory usage when reporting big DataFrames

Pull Request Test Coverage Report for Build 894340066

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 80.261%

Totals

Change from base Build 894206114:
0.01%

Covered Lines:
2277

Relevant Lines:
2837

💛  - Coveralls


Fix tests that could only run locally

@mauricioszabo What do you think the chances are that this fix will allow us to unrevert this commit?
Since originally I had bumped autocomplete-plus and updated it on Pulsar, only to have it to have all of it's tests failing. So we reverted it, but it looks like if this does fix that issue I could go ahead and bump autocomplete-plus (Or really I'd rather just bundle it so we don't have to worry about bumps)


How is the performance of dinov2-b14?

How is the performance of dinov2-b14? It is difficult for me to train it myself. Would you like to help train a b14 model? Thank you very much.

Hi, I think there is such a model, see here. It's not trained by me though.


Make-up assignment

@djbarnhar this pull request is a merge from Georgetown to District Data Labs, which isn't the correct direction for the pull. Would you please submit a new pull request from your fork to the georgetown-analytics repository?


errorBox is behind the Application

When there is an error-box opening direct behind the main Application, the Program blocks everything.

Probably needs to set Always on Top on the ErrorBox too or remove the Always on top from the frame temporaly


Error flag HAL_ADC_STATE_ERROR_INTERNAL checked but never set

Description
At line https://github.com/STMicroelectronics/stm32f2xx_hal_driver/blob/master/Src/stm32f2xx_hal_adc.c#L370 (just example) flag HAL_ADC_STATE_ERROR_INTERNAL checked
I looked in all the files and realized that it is not setting anywhere
Screenshots

Hi @vilesovds,
Thank you for reporting this issue. It will be forwarded to our development teams. I will let you updated as soon as they provide me with their feedback. Thank you for your patience.
With regards,

Hi @vilesovds,
Our development teams confirmed the issue you pointed out.  As a fix, they propose you to add the else case described above :
  else
  {
    /* Update ADC state machine to error */
    SET_BIT(hadc->State, HAL_ADC_STATE_ERROR_INTERNAL);

    /* Set ADC error code to ADC IP internal error */
    SET_BIT(hadc->ErrorCode, HAL_ADC_ERROR_INTERNAL);
  }

in the following functions :

 HAL_ADC_Start() line 805

HAL_ADC_Start_IT() line 1099

HAL_ADC_Start_DMA() line 1419

HAL_ADCEx_InjectedStart() line 205

HAL_ADCEx_InjectedStart_IT() line 317

 HAL_ADCEx_MultiModeStart_DMA() line 670

This will be fixed and made available in a future firmware package release. Thank you once more for your contribution.
With regards,

ST Internal Reference:  85500

Hi @vilesovds,
I hope you are fine. The issue you reported has been fixed, so please allow me then to close this thread.
Thank you again for having reported.
With regards,


vite.config.js behavior is different than vanilla scaffolding when importing Flickity or jQuery

Describe the bug
Vite in the craft-vite branch of this repo does not behave the same way when importing Flickity (or perhaps other packages as well) as it does in a new scaffolding when creating a new Vite app. I understand that it should be have a little differently because it is set up to work with Craft CMS but I would expect the import statement to behave similarly as it would with a new Vite app.
To reproduce
Steps to reproduce the behaviour:

Clone the vite-craft branch of this repo.

Run the following command in the buildchain directory:
npm i flickity

Then edit /src/js/app.ts by adding these two lines:
import Flickity from "flickity";
console.log(Flickity);

Now the app.ts file should look like this:
 import Flickity from "flickity";
 console.log(Flickity);
 import App from<EMAIL_ADDRESS> import { createApp } from "vue";

 // Import our CSS
 import<EMAIL_ADDRESS>
 // App main
 const main = async () => {
   // Create our vue instance
   const app = createApp(App);
   // Mount the app
   const root = app.mount("#component-container");

   return root;
 };

 // Execute async function
 main().then((root) => {});

Save the file and check the reloaded file contents in the browsers inspector. It should look similar to this:
import Flickity from "/node_modules/flickity/js/index.js";
console.log(Flickity);
import App from "/src/vue/App.vue";
import { createApp } from "/node_modules/vue/dist/vue.runtime.esm-bundler.js";
import "/src/css/app.pcss";
const main = async () => {
  const app = createApp(App);
  const root = app.mount("#component-container");
  return root;
};
main().then((root) => {
});

//# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJ....dfQ==

Notice that in the browsers console you'll get an error like the following:
 Uncaught SyntaxError: import not found: default         app.ts:6

Expected behaviour
I would expect that it would behave like a new Vite scaffolding with the following steps.

Run the following commands:
npm init vite@latest my-vanila-app --template vanilla
cd my-vanilla-app
npm i flickity

Open up the project in your IDE and edit the main.js file by adding these two lines at the top (or really anywhere in it. It all has the same effect):
import Flickity from 'flickity'
console.log(Flickity)

Now the main.js file should look like this:
import Flickity from 'flickity'
console.log(Flickity)
import './style.css'

document.querySelector('#app').innerHTML = `

Hello Vite!

  Documentation
`

Then run npm run dev

Check the output of the main.js file in the network tab of the browsers inspector. It should look similar to this:
import '/style.css'
import __vite__cjsImport1_flickity from "/node_modules/.vite/flickity.js?v=a7f2a681"; const Flickity = __vite__cjsImport1_flickity.__esModule ? __vite__cjsImport1_flickity.default : __vite__cjsImport1_flickity

console.log(Flickity)

document.querySelector('#app').innerHTML = `

Hello Vite!

  Documentation
`

I would expect the output of the import statement to look similar to this but it doesn't even look like it's processing it in the Craft setup:
 import __vite__cjsImport1_flickity from "/node_modules/.vite/flickity.js?v=a7f2a681"; const Flickity = __vite__cjsImport1_flickity.__esModule ? __vite__cjsImport1_flickity.default : __vite__cjsImport1_flickity

but instead it is just like this:
import Flickity from "/node_modules/flickity/js/index.js";

I'm not sure I understand what you're saying here? Vite is Vite... what exactly isn't working?

Good question. I accidentally posted this issue before I was ready to publish it. The part that isn't working is that it's not importing the Flickity script in the craft version but it will in a new Vite scaffolding. If you do a console.log(Flickity) with the Vite scaffolding it will show this:

But with the craft setup it will show this:

I think the critical part is that with the vanilla scaffolding setup it's actually processing the file as seen here:
 import __vite__cjsImport1_flickity from "/node_modules/.vite/flickity.js?v=a7f2a681"; const Flickity = __vite__cjsImport1_flickity.__esModule ? __vite__cjsImport1_flickity.default : __vite__cjsImport1_flickity

This shouldn't have anything to do with the Vite plugin but rather whatever your Vite config is?

Right. I've tried removing as much as I can from the craft project so that it will still work and it doesn't. The vanilla project doesn't even have a vite.config.js file.

I was wondering if it had something to do with it needing to interact with the back end. Perhaps this is more of a vitejs issue/question than a question for your craft setup.

Can't imagine how that could ever be the case, Vite isn't even aware of the backend.
It looks to me like that in one case it's trying to do a CJS import of an old library, and in another case, it's trying to do an ESM import, and thus not finding default

Well I think it is aware of the backend with the Craft setup: https://vitejs.dev/guide/backend-integration.html
build: {
    emptyOutDir: true,
    manifest: true,
    outDir: '../cms/web/dist',
    rollupOptions: {
      input: {
        main: '/src/main.js',
      },
      output: {
        sourcemap: true
      },
    }
  },

That's right about the import. I'm not sure what's causing it not to process it the same way in the Craft project.

So I was wondering if something compiles differently if it has backend integration. Just a long shot. But that might be more of a question for Evan You?

Compare your vite.config.js in the Craft project with the one generated by the Vite scaffolding.

I have. The Vite scaffolding does not create a vite.config.js. And this is the vite.config.js from the Craft project which is the same as https://github.com/nystudio107/craft/blob/craft-vite/buildchain/vite.config.js:
import vue from '@vitejs/plugin-vue'
import legacy from '@vitejs/plugin-legacy'
import ViteRestart from 'vite-plugin-restart';
import { nodeResolve } from '@rollup/plugin-node-resolve';
import critical from 'rollup-plugin-critical';
import path from 'path';

// https://vitejs.dev/config/
export default ({ command }) => ({
  base: command === 'serve' ? '' : '/dist/',
  build: {
    emptyOutDir: true,
    manifest: true,
    outDir: '../cms/web/dist',
    rollupOptions: {
      input: {
        app: '/src/js/app.ts',
      },
      output: {
        sourcemap: true
      },
    }
  },
  plugins: [
    critical({
      criticalUrl: 'https://nystudio107.com',
      criticalBase: '../cms/web/dist/criticalcss/',
      criticalPages: [
        { uri: '/', template: 'index' },
      ],
      criticalConfig: {
      }
    }),
    legacy({
      targets: ['defaults', 'not IE 11']
    }),
    nodeResolve({
      moduleDirectories: [
        path.resolve('./node_modules'),
      ],
    }),
    ViteRestart({
      reload: [
        '../src/templates/**/*',
      ],
    }),
    vue(),
    // Static Asset Fixer, see: https://github.com/vitejs/vite/issues/2394
    {
      name: 'static-asset-fixer',
      enforce: 'post',
      apply: 'serve',
      transform: (code, id) => {
        return {
          code: code.replace(/\/src\/(.*)\.(svg|jp?g|png|webp)/g, 'http://localhost:3000/src/$1.$2'),
          map: null,
        }
      },
    },
  ],
  publicDir: '../src/public',
  resolve: {
    alias: {
      '@': '/src',
    },
  },
  server: {
    host: '<IP_ADDRESS>',
  }
});

I'll maybe post an issue about it over here: https://github.com/vitejs/vite/issues

You have no vite.config.js in the scaffolding at all? I'm not sure I understand? Show me exactly how you're creating this Vite app?

In step 1 of the Expected Behavior of the issue I posted this:
npm init vite@latest my-vanila-app --template vanilla
cd my-vanilla-app
npm i flickity

Also you could try it with npm i jquery and get the same results.

And then try to import jQuery from 'jquery' and console.log(jQuery.
I apologize that I edited my original post so many times. That could be a cause of a lot of the confusion here. I accidentally hit the wrong keystroke and it submitted the post before I was done with it.

Okay, so it's using whatever the default internal config is, then, if that file doesn't exist.

Right.

If you copy the vite.config.js from the Craft scaffolding to your newly created vanilla scaffolding, what happens (will need to update the package.json, etc. too?

Good question. Hadn't tried that yet. I'll give that a try.

I work with @cavellblood, here are my thoughts on the issue.  (Good suggestion to test, BTW.)
It seems that the Vite build does not work with any CommonJS-only NPM package.  Most packages support ES Modules, but there are a few holdouts like jQuery and flickity.
You can tell if a package supports ES modules by looking at the package.json: it should have a field like module,  jsnext:main, or jsnext.  This is mentioned in the Vite documentation.  Originally we had the issue with Flickity, but then we went looking for a more popular CommonJS-only package and landed on jQuery.
I think somehow the default Vite config handles this correctly, but the config in this repository breaks it.  We have tested creating a brand-new project from the craft-vite branch and attempting to import jQuery, but it fails in the same way.
My theory is that somehow the files are not getting processed by @rollup/plugin-commonjs, which Vite uses internally.  But I have no idea why that might be.

I think the default Vite config handles this correctly, but the config in this repository somehow breaks it. We have tested creating a brand-new project from the craft-vite branch and attempting to import jQuery, but it fails in the same way

This sounds right to me!
When I encounter this, I usually look for more modern, ESM packages... there is CommonJS plugin but I think this goes against the "Vite way" to some extent.

My theory is that somehow the files are not getting processed by @rollup/plugin-commonjs, which Vite uses internally. But I have no idea why that might be.

Interesting, I thought you had to explicitly use that plugin. If that's the case, then likely something in the config or in one of the plugins is causing it.
I'd start by disabling the plugins until it works.

I'd be curious to hear the results here, to see if it's some config setting or some plugin that is interfering in the CommonJS loader that would normally be used.

lmk if you folks managed to figure any of this out. I may try myself as well.

Will do. I plan on working on it this afternoon.

Well I was able to get jQuery to work this afternoon but not Flickity. Kind of strange. Some things that I noticed that helped was to remove the leading slash everywhere this string appeared: /src/js/app.js, namely:

config/vite.php
critical-css.twig
Line 17 of vite.config.js

I then updated the app.js contents to this:
import $ from "jquery";

console.log($);

$("#component-container").html("It Works!");

And that worked. But I wasn't able to get Flickity working. I'll get back to this on Monday.

Ok so I have some results. I just cloned down a clean version of the nystudio107/craft to verify what works with minimal changes. I just had to change one character for it to work: remove the leading slash on line 17 of vite.config.js.
export default ({ command }) => ({
  base: command === 'serve' ? '' : '/dist/',
  build: {
    emptyOutDir: true,
    manifest: true,
    outDir: '../cms/web/dist',
    rollupOptions: {
      input: {
        app: 'src/js/app.ts',  // <-- This used to be `/src/js/app.ts`
      },
      output: {
        sourcemap: true
      },
    }
  },
  ...
}

I also had to declare the modules in the shims.d.ts or else it wouldn't work.
declare module "app";
declare module "jquery";
declare module "flickity";

I'm not super familiar with TypeScript so this was probably a beginners mistake.

Wow, that's crazy. Nice find!!

Did you also need to change it here: https://github.com/nystudio107/craft/blob/craft-vite/cms/templates/_boilerplate/_partials/critical-css.twig#L12
{{ craft.vite.script("/src/js/app.ts", false) }}

?

I tried changing it there and it didn't seem to have any effect. I thought that maybe your craft-vite plugin took all that into account.

It worked with the leading slash.

I should note that I did all these tests when make dev was running. I didn't but should've run these tests after doing a make build to verify. I can try that now but I'm guessing it would work.

yep might as well make build and give it a whirl that way too

Also, just curious about the best way to test built files. Here's what I currently do:

Run make dev
Then once all the containers are up and running I run make build in a new window.
When that process is complete I use Docker Desktop to stop the project_vite_1 container so that that vite server is no longer running.
Then I reload the page to get the built assets.

Is that the best way to test built files?

You can do it that way, or you can stop the vite container with:
docker-compose stop vite

but I typically just leave it running and do
make build

as you've suggested

That's one of the selling points of Docker-izing things, you can spin up as many instances as you need/want

Ok.
What's really odd now is that when I clone down cavellblood/craft Vite doesn't seem to be working at all. It says it's running in the terminal but on the front end all I see is this:

Maybe there's something awry with my machine. I'll try cloning down your repo to see if I have the same issue.

It's not loading the app.ts file anymore.

Same thing is happening when I clone your repo down.

I'm not sure what happened. I've cloned your repo down twice and I can't get the front end to load. Everything was working just fine a moment ago. I'll have to try a different computer. Sorry that this verification is taking longer than expected. I've even removed old images from Docker after quitting the project.
Anyway, I'll get back to you when I get it working.

I made you change to the Spoke and Gears P&T demo site that I converted over to Vite, and it's working as expected:
https://github.com/nystudio107/spoke-and-chain/commit/b9a896c18555a85b1cde441b6ac1dc0f1baa2afd
(but it has always worked -- just noting that nothing broke)

Right. Well I just was able to get things working again. I had to adjust the path in config/vite.php and criticalcss.twig to ../src/js/app.ts. I'm adding it to the PR.

Looks like the right way to do this is just change it to this in buildchain/vite.config.js:
      input: {
        app: './src/js/app.ts',
      },

...then you don't need to change anything anywhere else, at least in my testing.

Ok. Good to know. I should've tried that. I'll have to test that later but I think we can close this issue now.

I'm going to do a little more testing but you've been fantastic, thank you for digging into this!

I was able to get Europa Museum ported over to Vite, thanks to this finding!
https://github.com/nystudio107/europa-museum/tree/docker-vite

I see the changes you made here: https://github.com/nystudio107/craft/commit/e213d4f3ce8497c875c07b5480f45cf405f48790


use local activity and fix input type bug

What was changed
Use LocalActivity for SSNTrace activity invocation to demonstration.
Why?
To illustrate how LocalActivities appear in the history. Also, there was a bug in the input type being used to invoke it anyways.

 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.Mike Nichols seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closing to redo from fork


Use 5 seconds for the confirmation polling

Problem
This error happened on production nodes:
 Failure("os [MissedBlockDuringConfirmationError]: Taquito missed a block while waiting for operation confirmation and was not able to find the operation\n    at e._tapNext (/tmp/tezos_js_bridge0f65f0.js:2:231069)\n    at e._next (/tmp/tezos_js_bridge0f65f0.js:2:86684)\n    at e.next (/tmp/tezos_js_bridge0f65f0.js:2:60925)\n    at e.notifyNext (/tmp/tezos_js_bridge0f65f0.js:2:82470)\n    at e._next (/tmp/tezos_js_bridge0f65f0.js:2:80638)\n    at e.next (/tmp/tezos_js_bridge0f65f0.js:2:60925)\n    at e.next (/tmp/tezos_js_bridge0f65f0.js:2:66424)\n    at e.nextInfiniteTimeWindow (/tmp/tezos_js_bridge0f65f0.js:2:73767)\n    at Object.next (/tmp/tezos_js_bridge0f65f0.js:2:88967)\n    at e.__tryOrUnsub (/tmp/tezos_js_bridge0f65f0.js:2:62981)")

Solution
When building Deku for non-dev mode, we will use 5 seconds for the confirmation polling.
Related

https://github.com/ecadlabs/taquito/issues/276#issuecomment-942726844

I changed the streamerPollingIntervalMilliseconds
BTW, they unified these variables on v12.

The update guide.


iPhone: Setting larger font in accessibility settings doesn't change site font

I will look at this and try to diagnose what's wrong - then pass to @kkoryaka

This is a good check to also do in our accessibility + design QA cc @adam-little @kkoryaka @zakiya @aaronhans @xjensen
This is true - setting the larger text size in iPhone accessibility has no bearing on the site.
But there are additional instructions to make this work, and I was able to resize this on iPhone XR.
https://mcmw.abilitynet.org.uk/making-text-larger-safari-ios-13-iphone-ipad-and-ipod-touch
In the URL bar there is a text button that can be touched to change the size. While I have seen the button thousands of times, I didn't notice it & wish I had known because I can't read tiny text on my phone - sometimes even with glasses because to get the glasses to focus, the phone needs to be like 18" away - and if the text is tiny then it's too far away to see it. Yay for this button. Boo for Apple not making sure I know - a tip on the Accessibility settings page would be helpful. cc @britt-allen
@thepegisin probably knows all about this 👁

Adding to next sprint - would be nice to review this issue and think about our QA practices for testing typography on mobile devices.

Per planning discussion, the impetus issue is due to iOS/Safari usability issue. Chach confirmed that the font size does update if you find the right function/setting in iOS Safari. Marking won't do.

Just adding a supporting note.
The settings on an IPhone at Settings  > Accessibility > Display & Text Size affect Safari's app text like the in the address bar and Favorites list. Actual website text is adjusted the way Chach listed above.
Related Apple support links:
https://support.apple.com/guide/iphone/display-text-size-iph3e2e1fb0/ios#:~:text=Go to Settings > Accessibility > Display,using the Font Size slider.
https://support.apple.com/guide/iphone/customize-your-safari-settings-iphb3100d149/ios


cleanup(storage): use unified credentials in examples

Change the examples to use the unified credentials. In the process I
discovered that many examples included storage/oauth2/credentials.h
without using it.
Part of the work for #6612

This change is

google/cloud/storage/examples/storage_auth_samples.cc, line 56 at r1 (raw file):
Previously, dbolduc (Darren Bolduc) wrote…
i don't think this tag is ever referenced

Yes, that is (more or less) intentional.  I will fix in a future PR.


Allow FnMut closures

It would be nice to be able to time functions that use a rng would be nice.

Wow, that was fast, thanks!

No problem.


SNAPSHOT-1.1.0 mistranslation of Exp and removal of Implies operator

I am experiencing a similar issue as the Time(x.x.x...) issue I posted back in June. The Exp operation is being translated as a function reference instead of a Exp expression. This is not an issue with the 1.2.0 SNAPSHOT. Also, has the implies operation been removed from the language? I do not see it in the expression.xsd...

This issue has been corrected in the 1.1 translator, but not verified in a unit test, so I added a unit test.

Also, the implies operator is being added in CQL 1.2, it is not defined for CQL 1.1.


Update bsdd_utils.py

So there's three cases:

Present and valid json
Present and invalid json
Not present

Two remarks:

In the 3rd case the value is set to 0. Shouldn't that also be the case in the 2nd case for consistency in the report database?
I would log an error in the 2nd case (even if we don't really have a way to handle them now, but we probably will in the future).


please update version at least 3.7

v3.6 color picker properties are broken on windows 7.
v3.7 fixes the issue with ColorPicker in Windows 7. Here's the fix.
Go in file Xceed.Wpf.Toolkit/ColorPicker/Generic.xaml,
In the style targeting ""{x:Type local:ColorPicker}"",
Replace the Setter:
<Setter Property="DropDownBackground" Value="{StaticResource PanelBackgroundBrush}" />
by:
<Setter Property="DropDownBackground">
      <Setter.Value>
        <LinearGradientBrush EndPoint="0.5,1"
                              StartPoint="0.5,0">
          <GradientStop Color="#FFFAFBFB"
                        Offset="0" />
          <GradientStop Color="#FFF4F4F4"
                        Offset="1" />
        </LinearGradientBrush>
      </Setter.Value>
    </Setter>

issue is here

could you create a pull request?

Is there no plan to upgrade this with a new version of the Xceed.Wpf.Toolkit?the Xceed.Wpf.Toolkit has update to 4.0+;

no.
xceed changed licence, so there will be no more merges.


No sound but video is working

Bug report
Your Environment

Netflix add-on version: <1.12.4>
Operating system version/name: <LibreElec 9.2>
Device model:  <Raspberry Pi 4>

Used Operating system:

[ ] Android
[ ] iOS
[ ] Linux
[ ] OSX
[x] Raspberry-Pi
[ ] Windows

Describe the bug
Video does playback with no issues but there is no sound. When Playback is stoped there is the error message "AMplayback disabled due to exception u'percentage'
Expected behavior
Video does playback with sound
Actual behavior
No sound and error message
Steps to reproduce the behavior

Play video
No Sound
Error message

Debug log
The debug log can be found here:
https://paste.kodi.tv/orovawufas

the percentage exception error is not related to your problem
i have no idea whats do not works in your system
but it is quite difficult that this depends from the addon..

Thanks a lot for taking your time and having a look into it, the problem was sitting in front of the screen...
It seems at some point I made a wrong setting in the InputStream Adaptive plugin at the item "Media", it was set to "Video" (not quite shure about that) after setting it to "All" sound came back and this issue can be considered closed I guess, Netflix Playback is working flawless again as usual.
So everybody who has the same troubles:

Set InputStream Adaptive plugin to standard settings
Profit!


CASMINST-4857: Add manual step to create BSS Global bootparameters

Description
Add a step to create the base BSS global bootparameters object in BSS. Other CSM Services and tooling expect BSS to have a Global bootparameter object for them to PATCH against.
Tested pm Sutur:
surtur-ncn-m001-pit:~/rsjostrand # kubectl -n services rollout status deployment cray-bss
deployment "cray-bss" successfully rolled out
surtur-ncn-m001-pit:~ # SPIRE_JOB=$(kubectl -n spire get jobs -l app.kubernetes.io/name=spire-update-bss -o name)
surtur-ncn-m001-pit:~ # echo $SPIRE_JOB
job.batch/spire-update-bss-1
surtur-ncn-m001-pit:~ # kubectl -n spire get $SPIRE_JOB -o json | jq 'del(.spec.selector)' \
>    | jq 'del(.spec.template.metadata.labels."controller-uid")' \
>    | kubectl replace --force -f -
job.batch "spire-update-bss-1" deleted
job.batch/spire-update-bss-1 replaced
surtur-ncn-m001-pit:~/rsjostrand # kubectl -n spire wait  $SPIRE_JOB --for=condition=complete --timeout=5m
job.batch/spire-update-bss-1 condition met

The perviously failing tests now pass:
surtur-ncn-m001-pit:~/rsjostrand # grep "Total Test" ncn-healthcheck.log
Total Tests: 33, Total Passed: 33, Total Failed: 0, Total Execution Time: 3.2339 seconds
Total Tests: 33, Total Passed: 33, Total Failed: 0, Total Execution Time: 3.1858 seconds
Total Tests: 33, Total Passed: 33, Total Failed: 0, Total Execution Time: 3.5193 seconds
Total Tests: 71, Total Passed: 71, Total Failed: 0, Total Execution Time: 8.6881 seconds
Total Tests: 71, Total Passed: 71, Total Failed: 0, Total Execution Time: 8.0112 seconds
Total Tests: 75, Total Passed: 75, Total Failed: 0, Total Execution Time: 24.8543 seconds
Total Tests: 75, Total Passed: 75, Total Failed: 0, Total Execution Time: 25.4267 seconds
Total Tests: 75, Total Passed: 75, Total Failed: 0, Total Execution Time: 32.2317 seconds

surtur-ncn-m001-pit:~/rsjostrand # grep "Total Test" ncn-kubernetes-checks.log
Total Tests: 30, Total Passed: 30, Total Failed: 0, Total Execution Time: 0.5580 seconds
Total Tests: 30, Total Passed: 30, Total Failed: 0, Total Execution Time: 0.5583 seconds
Total Tests: 28, Total Passed: 28, Total Failed: 0, Total Execution Time: 0.6354 seconds
Total Tests: 28, Total Passed: 28, Total Failed: 0, Total Execution Time: 0.5946 seconds
Total Tests: 28, Total Passed: 28, Total Failed: 0, Total Execution Time: 0.5570 seconds

Checklist Before Merging

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I don't have a JIRA.

I'll create the main backport

I'll create the main backport

https://github.com/Cray-HPE/docs-csm/pull/1930


entered unreachable code at Portal::wait_once

I'm seeing this error in production somewhat rarely. I haven't been able to repro it yet.
 ERROR device            > 93281.127 panicked at 'internal error: entered unreachable code'
stack backtrace:
   0: core::panicking::panic
        at /root/.rustup/toolchains/nightly-2021-10-16-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/panicking.rs:41
   1: __defmt_default_panic
        at /root/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/50e3db3/defmt/src/lib.rs:367
   2: nrf_softdevice::util::portal::Portal<T>::wait_once::{{closure}}::{{closure}}
   3: nrf_softdevice::util::portal::Portal<T>::call
   4: nrf_softdevice::ble::on_evt
   5: nrf_softdevice::events::run::{{closure}}::{{closure}}
        at /root/.cargo/git/checkouts/nrf-softdevice-c6f1e1abd1ad6893/6a01c4c/nrf-softdevice/src/events.rs:73
   6: <futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
        at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.18/src/future/poll_fn.rs:56
   7: nrf_softdevice::events::run::{{closure}}
        at /root/.cargo/git/checkouts/nrf-softdevice-c6f1e1abd1ad6893/6a01c4c/nrf-softdevice/src/events.rs:54
   8: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
        at /root/.rustup/toolchains/nightly-2021-10-16-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80
   9: nrf_softdevice::softdevice::Softdevice::run::{{closure}}
        at /root/.cargo/git/checkouts/nrf-softdevice-c6f1e1abd1ad6893/6a01c4c/nrf-softdevice/src/softdevice.rs:323
  10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
        at /root/.rustup/toolchains/nightly-2021-10-16-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80
  11: application::ble::softdevice_task::task::{{closure}}
        at /builds/firmware/firmware/ak-application/src/application/ble.rs:131
  12: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
        at /root/.rustup/toolchains/nightly-2021-10-16-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/future/mod.rs:80
  13: embassy::executor::raw::TaskStorage<F>::poll
        at /root/.cargo/git/checkouts/embassy-00cf184034ab5a1f/7561fa1/embassy/src/executor/raw/mod.rs:183
  14: core::cell::Cell<T>::get
        at /root/.rustup/toolchains/nightly-2021-10-16-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/cell.rs:436
  15: embassy::executor::raw::timer_queue::TimerQueue::update
        at /root/.cargo/git/checkouts/embassy-00cf184034ab5a1f/7561fa1/embassy/src/executor/raw/timer_queue.rs:35
  16: embassy::executor::raw::Executor::poll::{{closure}}
        at /root/.cargo/git/checkouts/embassy-00cf184034ab5a1f/7561fa1/embassy/src/executor/raw/mod.rs:329
  17: embassy::executor::raw::run_queue::RunQueue::dequeue_all
        at /root/.cargo/git/checkouts/embassy-00cf184034ab5a1f/7561fa1/embassy/src/executor/raw/run_queue.rs:71
  18: embassy::executor::raw::Executor::poll
        at /root/.cargo/git/checkouts/embassy-00cf184034ab5a1f/7561fa1/embassy/src/executor/raw/mod.rs:308
  19: cortex_m::asm::inline::__wfe
        at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-0.7.3/src/../asm/inline.rs:177
  20: cortex_m::asm::wfe
        at /root/.cargo/registry/src/github.com-1ecc6299db9ec823/cortex-m-0.7.3/src/asm.rs:49
  21: embassy::executor::arch::Executor::run
        at /root/.cargo/git/checkouts/embassy-00cf184034ab5a1f/7561fa1/embassy/src/executor/arch/cortex_m.rs:54
  22: application::sys::__cortex_m_rt_main
  23: application::sys::__cortex_m_rt_main
        at /builds/firmware/firmware/ak-application/src/application/../sys.rs:158
error: the stack appears to be corrupted beyond this point

It's hitting the unreachable! here:
https://github.com/embassy-rs/nrf-softdevice/blob/8a7ae35733156e903a6c9ddc8dc3c0b7dfada59c/nrf-softdevice/src/ble/l2cap.rs#L199
I've changed it to print which event it is, we'll see in a few days...


Check token expiry instead of auth_time

I might be missing something, but checking auth_time always seems to return the first time the user authenticated, which means the token is always expired after 5 mins.

I think IAT is what I really intended, will address in the next release. Thanks for taking the initiative here.


Produce language outputs, as well as combined blacklist.json

This will allow users to be able to fetch the produced JSON lists (e.g. https://raw.githubusercontent.com/sqids/sqids-blacklist/main/output/blacklist.json for the whole list, https://raw.githubusercontent.com/sqids/sqids-blacklist/main/output/en.json for English) and directly generate code from them (I do this in C.)

Sorry, I just now saw this - gotta fix my notifications.
Thanks for the PR. Merged & also sent you an invite so you can push without creating PRs.


Any way to connect over rdp when session started at local pc ?

Situation: I work on pc locally, and not end session when going home. From home I want to connect to pc over rdp, and I can't do it.
I use xrdp + xorgxrdp.

Duplicate of #960.
You should connect to localhost via rdp from the beginning. Local session should be used only to run rdp client.


Implement A Custom Artisan Command

Implement an example of a custom Artisan command within the context of a Vending Machine.
See documentation here.

As an idea, maybe a command to correct stock in a slot (in case someone was lucky and got a double drop!)

As an idea, maybe a command to correct stock in a slot (in case someone was lucky and got a double drop!)

@accu-clw Thanks for the idea! It's been implemented 😄


Document features

Document new features

[ ] https://github.com/jquery-validation/jquery-validation/pull/2061
[ ] https://github.com/jquery-validation/jquery-validation/pull/2063

@staabm docs are only needed for #2063 as it is a new option of the validate() method. As for the new additional methods, we don't need that as not all additional methods are documented (from docs):

Some more methods are provided as add-ons, and are currently included in additional-methods.js in the download package. Not all of them are documented here:
accept – Makes a file upload accept only specified mime-types.
creditcard – Makes the element require a credit card number.
extension – Makes the element require a certain file extension.
phoneUS – Validate for valid US phone number.
require_from_group – Ensures a given number of fields in a group are complete.
You can find the source code for all additional methods in the GitHub repository.


feat(firebase_messaging): Added 'critical' to notification settings.

Enables apps to check whether the user permitted critical alerts (iOS only)
Description
The PR adds a critical to notification_settings.dart. This informs calling apps whether the user permitted the app to trigger critical alerts, which bypass the phone's "mute" and "focus" settings. Apple only.
The according flag criticalAlert was already part of the native ObjectiveC code but was not yet read in Dart. Just added that part.
Related Issues

none

Checklist

[X] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[X] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[X] All existing and new tests are passing.
[X] I updated/added relevant documentation (doc comments with ///).
[X] The analyzer (melos run analyze) does not report any problems on my PR.
[X] I read and followed the [Flutter Style Guide].
[X] I signed the [CLA].
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[X] No, this is not a breaking change.

Hey @komaxx, thanks for the PR! Could you rename to "criticalAlert" to match the iOS property?

Absolutely! Done :)

@russellwheatley If you don't mind, could you take another look?


Could not find a valid gem 'fauxhai' (~> 2.3) in any repository

> [2016-04-18T05:47:59-07:00] ERROR: chef_gem[chefspec] (tc3-chefspec::gem_install line 41) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '2'
> ---- Begin output of C:/opscode/chef/embedded/bin/gem install C:\chef\cache\chefspec-4.4.0.gem -q --no-rdoc --no-ri -v "4.4.0" --local ----
> STDOUT:
> STDERR: ERROR:  Could not find a valid gem 'fauxhai' (~> 2.3) in any repository
> ---- End output of C:/opscode/chef/embedded/bin/gem install C:\chef\cache\chefspec-4.4.0.gem -q --no-rdoc --no-ri -v "4.4.0" --local ----
> Ran C:/opscode/chef/embedded/bin/gem install C:\chef\cache\chefspec-4.4.0.gem -q --no-rdoc --no-ri -v "4.4.0" --local returned 2; ignore_failure is set, continuing
> [2016-04-18T05:47:59-07:00] INFO: Processing log[end tc3-chefspec::gem_install] action write (tc3-chefspec::gem_install line 54)
> [2016-04-18T05:47:59-07:00] INFO: end tc3-chefspec::gem_install
> [2016-04-18T05:47:59-07:00] INFO: Chef Run complete in 16.51561 seconds
> [2016-04-18T05:48:00-07:00] INFO: Running report handlers
> [2016-04-18T05:48:00-07:00] INFO: Report handlers complete

Hi there,
Thank you for opening an issue. This version is released on ruby gems: https://rubygems.org/gems/fauxhai/versions. Please check your caches and Internet connection. This is not a fauxhai issue.
Please refrain from opening the same issue across multiple repositories. It's unprofessional and creates noise in maintainers inbox that could be better spent working to improve the software. Thanks!

Issue resolved by using the older version which was already installed. Thanks @sethvargo for your time... :)


Please make a release for windows.

This Project is manly made for windows at the alpha-release on 17/12/2021. There will be a compiled version of the game somewhere.


PayPal FIDO Ready™ Implementation

PayPal also supports another strong authentication option - the new FIDO Alliance protocol - though admittedly support is limited to the Samsung Galaxy S5, S5 mini, Galaxy Tab S, and Alpha devices (with a fingerprint sensor).
https://www.paypal-pages.com/samsunggalaxys5/us/index.html
https://fidoalliance.org/news/item/the-fido-alliance-announces-first-authentication-deployment-paypal-samsung
This approach actually ends up being easier than SMS/OTP based 2FA solutions, while also providing stronger security (the approach is not phishable like SMS, and there are no symmetric secrets stored on the server, waiting to be stolen). It's multifactor auth because the user must posses the device (which is provisioned with a public/private key pair during registration), and authenticate with their fingerprint (biometric) to the device to unlock access to the private key. Authentication is performed by the user unlocking the private key with their fingerprint, and using the private key to sign a challenge provided by the server.
The same approach is also now used by Alipay in China, and a number of other financial institutions are investigating the approach. If you look at the FIDO Alliance web site, you'll see a number of the heavy hitters involved in the effort (Google, Microsoft, Lenovo, Samsung, Bank of America, Visa, MasterCard, Discover, many more).

Hi! I created a friendly fork of twofactorauth which lists OTP (OATH) and U2F compatible websites only. See: https://github.com/Nitrokey/dongleauth/ and http://www.dongleauth.info
I would be glad to see it merged in twofactorauth eventually.

So... No column then?


After the Docker Compose Down, a lot of data was left behind

After the docker-compose down , a lot of data was left behind.
docker volume ls You can see residual rolls
[root@localhost ~]# docker  volume  ls
DRIVER    VOLUME NAME
local     ed2d8ca078b3089d4e11a6c324d16125c8470d306f28743a5ee035edf3f6e381

How to distinguish?
Try to docker info, and cd to docker root dir, and see the volumes, you'll see the data.

I see. Thank you very much


Add javaagent foundation

Codecov Report

Merging #79 into master will increase coverage by 0.06%.
The diff coverage is 84%.

@@             Coverage Diff              @@
##             master      #79      +/-   ##
============================================
+ Coverage     76.26%   76.33%   +0.06%
- Complexity      737      748      +11
============================================
  Files            79       83       +4
  Lines          2680     2730      +50
  Branches        242      245       +3
============================================
+ Hits           2044     2084      +40
- Misses          503      511       +8
- Partials        133      135       +2

Impacted Files
Coverage Δ
Complexity Δ

...main/java/co/elastic/apm/bci/ElasticApmAdvice.java
100% <100%> (ø)
1 <1> (?)

...lastic/apm/bci/bytebuddy/ErrorLoggingListener.java
50% <50%> (ø)
2 <2> (?)

...stic/apm/bci/bytebuddy/ClassLoaderNameMatcher.java
83.33% <83.33%> (ø)
5 <5> (?)

.../main/java/co/elastic/apm/bci/ElasticApmAgent.java
87.17% <87.17%> (ø)
4 <4> (?)

...a/co/elastic/apm/report/ReportingEventHandler.java
92.59% <0%> (-7.41%)
9% <0%> (-1%)

Continue to review full report at Codecov.

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


[FeatReq] Implement a Plugins system in Aider

Issue
Please implement a plug-in system for Aider.
The PLUGINS should be able to simply provide an INPUT or an OUTPUT.
An AIDER INPUT PLUGIN would be content added to the chat. This would be extremely useful for allowing the AI to receive some custom output or debug data from some library, like HTTP responses, images or socket/connection logs, memory tracing, raw SQL, JSON messages, GUI/TUI screen snapshots, etc. to help the debug process.
For example, I would be happy to write a plugin for letting Aider receive the log output from Textual. All I need to do is to adapt the code from here:  https://github.com/Textualize/textual-dev/blob/main/src/textual_dev/client.py
An AIDER OUTPUT PLUGIN would be a way to execute some code and data in a sandbox to see it running. Something similar to the "Artifacts" generation in the Claude 3.5 chatbot.
This would allow people like me to contribute to the project.
Thanks.
Version and model info
No response

Thanks for trying aider and filing this issue.
The best ways to feed output from other programs into aider are:

Use /run.
Copy & paste the output into the chat.
Put the output into a file somehow, and add it to the chat.

I think /run is probably most useful for your needs. Simply make a cli program that will output the Textual logs. Then you a /run it to add the logs to the aider chat.

I'm going to close this issue for now, but feel free to add a comment here and I will re-open or file a new issue any time.


tagless component assertion too aggressive

I have a couple of tagless pass-through components that forward most of their arguments (including test selectors) to a contained component. I used to silence the deprecation warnings about data-test-* attributes on tagless components, but now that it's a hard assert I have to do this:
  init() {
    // Work around ember-test-selectors' assertion that data-test- attributes
    // aren't set on tag-less components
    let dataTestModalName = this['data-test-modal-name'];
    delete this['data-test-modal-name'];
    this._super(...arguments);
    this['data-test-modal-name'] = dataTestModalName;
  },

😭😭😭😭😭
Could we devise some way to disable this assertion, either on a component-by-component basis, or globally? Options I see:

Add some magic attribute to components to opt out of the tagless assertion, maybe data-test-ignore-tagless: true (so it gets stripped out just like regular test selectors)
Add an option to config/environment.js to globally disable the assertion
Downgrade the assertion back to a warning
Remove the assertion/check entirely

I provide the last two as options because I find the assertion to be of pretty limited value -- all it could possibly be doing is giving you a clue as to why a test is failing, it could not possibly prevent an actual bug. While this may be helpful for beginners, asserting seems like a pretty extreme measure for such an un-severe issue. But if others feel differently, I'll happily concede the point and continue advocating for (1) or (2).

see https://github.com/simplabs/ember-test-selectors/issues/204#issuecomment-444486652 and the following comments

Okay. I'll likely have time in the next day or two to PR the change suggested at the end of that thread. However, now that we're talking about writing code to disable the code that sometimes spuriously tells us that the code we wrote to help test the code isn't going to help us test the code, I'm still wondering if it's worth it. What value do we think this assertion provides that is worth this extra complexity? I don't think it's ever saved me any time/effort, and between figuring out how to silence the deprecation warning so it didn't clutter up my test output, and now this, it's cost me handful of hours, so I'm wondering if we have any evidence that others have the opposite experience.

Resolved by #323


DAPR App health checks

Please provide us with the following information:

This issue is a: (mark with an x)

[ ] bug report -> please search issues before submitting
[ x] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
Dapr Runtime v1.9 has released App health checks feature that allows probing for the health of your application and reacting to status changes.  More info about those feature dapr docs.
App health checks are disabled by default, but can be enabled with either:
The --enable-app-health-check CLI flag; or
The dapr.io/enable-app-health-check: true annotation when running on Kubernetes.

Expected behavior [Ability to configure Dapr App health checks in bicep for Azure Container App ]
Actual behavior [App health checks feature can be enabled by CLI or Kubernetes annotation ]
Additional context
Do we have possibility to configure new feature Dapr App health checks using bicep? If no do we have any plans to release?

@greenie-msft

+1
The absence of this feature makes Container Apps a non-viable alternative to Kubernetes.

i too would really like to see some form of this enabled. it's probably the biggest reason we're currently avoiding dapr. would like to see this added to the roadmap with some kind of ETA so we can make some judgement calls. thanks for the consideration

@mikalst  what is the specific scenario that you are expecting to be enabled from Dapr app health checks?
By default, container app enables platform level pod liveness health check API and Dapr health check is mere complimentary as per my understanding of it.
Details [here](https://docs.dapr.io/operations/resiliency/health-checks/app-health/#app-health-checks-vs-platform-level-health-checks


Add github actions.

Update to current flagscript cicd.
Use GitHub actions for cfn-lint and semantic release.

closes #1

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Search modals sometimed don't show when triggered on GitHub

Describe the bug
On both the development and deployed builds, on Github, I sometimes get the error "Autofocus processing was blocked because a document already has a focused element." (see screenshot below). This seems to cause the extension not to show when triggered.
To Reproduce
The problem is I don't even know how this even happens. It just happens randomly sometimes and I am unsure if this is even happening on websites other than GitHub (or any other computer for that matter).
Expected behavior
The Search modal should always be shown when triggered.
Screenshots

Platform Info (please complete the following information):

OS: Mac
Browser: Chrome

Additional context
Upon further googling and code inspection, it seems that I use autoFocus on the Input element in the Search component. Apparently, autofocus only really works on page load, so there could be some form of interference here. A possible simple solution would be to remove that prop and on mount, use a ref to call the focus() method for the input element.
Another possible reason could be this problem could be  focus-trap. I have been thinking of removing this package and with the introduction of #40, there might not really be a need to use this package anymore.
As said earlier, this could just be an issue with my machine and more testing needs to be done.

Upon further inspection it seems to have something to do with GitHub's own command pallete and the same message is sometimes logged even when the Search Modal is not triggered. Will close this for now but will keep an eye out for this and how it could potentially affect us. It might still be a good idea to use a ref to focus the input on mount instead of using the autoFocus prop (need to confirm)

Confirmed it ✅ . Need to switch to calling .focus instead.

After changing the injection strategy in #69, this issue seems to have subsided. However, we should still replace the autofocus on the input field.


i am confused

i installed this mod but it didn't work, i came here and saw it was a fork of the original so i thought I'd need to disable it, and that broke the mods dependent on the original, i am confused, how does one install this mod properly?

The original and this fork are not interchangeable.
This means if a mod depends on the original you need to use the original. You can't substitute it with this fork.
You could use both at the same time, but the ensuing confusion is out of my hands


Next.js and auto:true - using "next start" million.js runs and then stops server

What version of million are you using?
2.6.0-beta.13
Are you using an SSR adapter? If so, which one?
None
What package manager are you using?
npm
What operating system are you using?
Windows
What browser are you using?
Chrome
Describe the Bug
I have installed million.js and added it to my next.config.js as described in the tutorial.
When i start next.js in developer mode "Next Start" it looks like everything works fine, but after million.js has optimized some components it just exits the terminal.
- wait compiling /src/middleware (client and server)...
- event compiled successfully in 411 ms (53 modules)
- wait compiling /api/redirects (client and server)...

🦁  million  Automatic mode is enabled ✓ (beta)
Schedule a call if you need help: https://million.dev/hotline. To disable help messages, set the "mute" option to true.
There is no guarantee that features in beta will be completely production ready, so here be dragons.

💡 TIP: Use // million-ignore to skip over problematic components.

- event compiled successfully in 2.8s (78 modules)
- wait compiling / (client and server)...
⚡ <ErrorFallback> was optimized. Estimated reconciliation improvement: ~41% faster.
   7 nodes, 3 attributes, 2 texts, 1 components, and 4 expressions. Average depth = 5. (12 - 5) / (12 + 5) = 41%.
⚡ <DynamicComponent> was optimized. Estimated reconciliation improvement: ~38% faster.
   5 nodes, 3 attributes, 3 texts, 1 components, and 4 expressions. Average depth = 4. (11 - 5) / (11 + 5) = 38%.
⚡ <Employee> was optimized. Estimated reconciliation improvement: ~11% faster.
   17 nodes, 18 attributes, 0 texts, 5 components, and 23 expressions. Average depth = 2. (35 - 28) / (35 + 28) = 11%.
⚡ <Preview> was optimized. Estimated reconciliation improvement: ~64% faster.
   4 nodes, 3 attributes, 2 texts, 1 components, and 1 expressions. Average depth = 0. (9 - 2) / (9 + 2) = 64%.

What's the expected result?
I would excpect it to keep running the server, so I could view the page by going to localhost:3000.
Or is this only a build time thing and cant be use together with the server running?
I apologize if this is not a bug but intended behaviour.
Link to Minimal Reproducible Example
n/a
Participation

[ ] I am willing to submit a pull request for this issue.

I am using<EMAIL_ADDRESS>with<EMAIL_ADDRESS>Works fine with this config:
next.config.mjs
import million from 'million/compiler';

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  swcMinify: true,
  output: 'standalone',
}

const millionConfig = {
  auto: { rsc: true },
}

export default million.next(nextConfig, millionConfig);

Yep! I just used it on a project too. I think you should change it to next.config.mjs

Thanks everyone....
Must have been Gremlins in my machine, today it just works, nothing changed :)

Thanks everyone....
Must have been Gremlins in my machine, today it just works, nothing changed :)

Awesome! Glad it works now.


Bug/fix behaviour after a database error

Description
Fixes #132
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Refactor (refactoring code, removing useless files)

Testing steps
go test ./... and ./test.sh

continuous integration fails because this version requires function Send from this pull https://github.com/RedHatInsights/insights-operator-utils/pull/8


Fix bazel integration

//cc @alexeagle

I think this PR should no longer be necessary once https://github.com/bazelbuild/rules_nodejs/pull/1430 lands
It will cause us to lay out the normal node_modules tree in the working directory and patch the symlink primitives in node, when you call architect via a load from index.bzl

@alexeagle That might not necessarily be the case until we change the generated nodejs_test target to have its entry point live from within the normal node_modules directory. As it is the entry point will still be external/npm after that PR lands.


First Step of new Postgres DB Structure

source_session
	id auto increme pk not null
	source_id string not null
	data_version string not null
	store_start_at  date time (UTC) not null
	store_end_at    date time  null
	sample boolean not null
	index(source_id, data_version, sample)

source_session_file_status
	id auto increme pk not null
	source_session_id fk not null index
	filename string not null
	store_start_at  date time null
	store_end_at    date time  null

release
	id auto increme pk not null
	source_session_file_status_id fk not null index
	release_id string null not null
	ocid string null not null
	data_id fk not null
	package_data_id fk not null

record
	id auto increme pk not null
	source_session_file_status_id fk not null index
	ocid string null
	data_id fk not null
	package_data_id fk not null

data
	id auto increment pk not null
	hash_md5 string unique index not null
	data jsonb not null

package_data
	id auto increment pk not null
	hash_md5 string unique index not null
	data jsonb not null

Transaction 1:
	write source_sesions with store_start_at and all source_session_file_statuses rows

For each file:
	in one transacction:
		update source_session_file_statuses as started
		add data
		update source_session_file_statuses as ended

Final transaction:
	update source_sesions to say finised

I started on this on branch '40-db'.
I'm not working on Monday - if someone wanted to pick this up on Monday and have a go feel free? @tian2992 @yolile Just update here.
It basically works in that data appears in the database!  Oh, and I broke the existing tests and haven't fixed them yet. And I definitely haven't written any new tests :-)

PR at https://github.com/open-contracting/ocdsdata/pull/66