username database connection

The SQL scripts now add a users table with two test users.
/createuser allows you to add new users to DB and security can be turned on (but is off right now)
/logger now hits the database to query for the user's input instead of reading it from JSON or whatever I was doing before
Cleaned up some stuff here and there.

Reviewed some of this yesterday, getting 500s after creating the user relation model and also populating it with some entries. might be doing something wrong but need to debug before merging this in.
@paulojblack are there some specific things besides

Updating the schema
adding a user
navigating to /login

that im missing?

@wbprice or @ttavenner if you could check out this PR sometime in the future and give a LGTM. Probably issues I'm having are with my local user tables not configured correctly and giving me 500.

As far as I can tell it's a little messy but it works, I'll try and be explicit about what I added below and then we can try and sort it out later.
What was added:

Username schema with one sample admin entry and one user entry. See database file (sampledata) or look in psql to find the info.

/login page - Logging in with the manually uploaded entries works. Note that the login info requests email and password, not username and password.

/logout - obvious

/createuser - As far as I can tell this properly inserts a new entry to the db. Make SURE that in the scope box you write "admin". Nothing else is formatted though so write whatever.

And this is probs extraneous and can be removed but I wanted to play with the front end so I added a button at the bottom right of the landing page that doesn't link anywhere rn. Idk how best to link to stuff inside the site so I left it vacant, I didn't want to make it an href since that seems clumsy compared to however it's been set up with react.

So yeah I'm not sure what is causing the error. I got hung up for a moment because I kept trying to enter the USERNAME rather than the EMAIL of the entries I had created while trying to login. So I can't say if the problem is from a confusing setup or if there really is a bug somewhere.


[Django Upgrade] Fix from_db_value & to_python in EncryptedJSONField

super.from_db_value must be called first since it is expected to only work on the raw value retrieved from DB
moved super.from_db_value call to from_db_value and let to_python call from_db_value instead of the other way around

Merged in https://github.com/CenterForOpenScience/osf.io/commit/dd377cc72a66e239e9d86978991120a76ab7903d


still not running

the exception.txt file:
Exception:
#=qG_Cl0xPUIXAr7Gxbj9xr1UFh0GNaWUpitkXmSs4mohU=: GlyphSheet: No clean breaks found between glyph rows.
  at #=qLVNq3PVNh2PfpPGTi0HeUw==.#=q8zlhvQt5aBUR6IR0eIS_nQ== () <0x41bcf88 + 0x00273> in <filename unknown>:0
  at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) <0x41bc128 + 0x0008f> in <filename unknown>:0

Thread: , State: Running, Alive: True, Background: False
  at #=qYCigg8hLK$7E5EiWde8WJg==+#=q5XL4rRNSsLDu1uYr6ozmWiKNS$meZV1AZZikvTEP_PM=.#=q$1lj7LzPsgPU14Z3i$WhB_E5yBeowzHfDVfYPvvpwEs= (System.Threading.Thread #=qFgBOpMisigH6TDO25lRJcA==) [0x00000] in <filename unknown>:0
  at #=qYCigg8hLK$7E5EiWde8WJg==.#=qguQNvTEYvLaTIJaJx0lmEA== (System.Exception #=qLFoUTKR8Y3OaLg7ljBcblQ==, System.String #=qGLoTrVPSA4Cyj5m1oV8llg==, System.Object[] #=qrV2jy6hl8b_C29KqMesjDw==) [0x00000] in <filename unknown>:0
  at #=qYCigg8hLK$7E5EiWde8WJg==.#=qr$ULSWLnd_6uZTLZW$F9dg== (System.Exception #=qg$NDjlvFfuJddthg8tkGuQ==) [0x00000] in <filename unknown>:0
  at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=q$ySgeZBME1e8LHvYdFbfLg== (System.Exception #=qDxDKLI_uaGBoMRLus6Yhsg==) [0x00000] in <filename unknown>:0
  at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) [0x00000] in <filename unknown>:0
  at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in <filename unknown>:0
  at System.AppDomain.ExecuteAssembly (System.AppDomain , System.Reflection.Assembly , System.String[] ) [0x00000] in <filename unknown>:0
  at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly a, System.String[] args) [0x00000] in <filename unknown>:0
  at System.AppDomain.ExecuteAssembly (System.String assemblyFile, System.Security.Policy.Evidence assemblySecurity, System.String[] args) [0x00000] in <filename unknown>:0
  at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in <filename unknown>:0

Thread: .locals, State: WaitSleepJoin, Alive: True, Background: False

macOS 10.11.5, fresh installed spacechem

Same problem here. This also happens when I try to execute SpaceChem.bin.osx
$ ./SpaceChem.bin.osx
WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v4.0.30319
Setting breakpad minidump AppID = 92800
Steam_SetMinidumpSteamID:  Caching Steam ID:<PHONE_NUMBER>0873899 [API loaded no]
The game experienced an error. A report has been saved:
"/Users/eugene/.local/share/Zachtronics Industries/SpaceChem/crashes/005.zicrash"
KQ: Error reading KQ:Bad file descriptor

Same issue here.  Just got SpaceChem on steam, here is the exception file.
`Exception:
#=qG_Cl0xPUIXAr7Gxbj9xr1UFh0GNaWUpitkXmSs4mohU=: GlyphSheet: No clean breaks found between glyph rows.
at #=qLVNq3PVNh2PfpPGTi0HeUw==.#=q8zlhvQt5aBUR6IR0eIS_nQ== () <0x40daf88 + 0x00273> in :0
at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) <0x40da128 + 0x0008f> in :0
Thread: , State: Running, Alive: True, Background: False
at #=qYCigg8hLK$7E5EiWde8WJg==+#=q5XL4rRNSsLDu1uYr6ozmWiKNS$meZV1AZZikvTEP_PM=.#=q$1lj7LzPsgPU14Z3i$WhB_E5yBeowzHfDVfYPvvpwEs= (System.Threading.Thread #=qFgBOpMisigH6TDO25lRJcA==) [0x00000] in :0
at #=qYCigg8hLK$7E5EiWde8WJg==.#=qguQNvTEYvLaTIJaJx0lmEA== (System.Exception #=qLFoUTKR8Y3OaLg7ljBcblQ==, System.String #=qGLoTrVPSA4Cyj5m1oV8llg==, System.Object[] #=qrV2jy6hl8b_C29KqMesjDw==) [0x00000] in :0
at #=qYCigg8hLK$7E5EiWde8WJg==.#=qr$ULSWLnd_6uZTLZW$F9dg== (System.Exception #=qg$NDjlvFfuJddthg8tkGuQ==) [0x00000] in :0
at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=q$ySgeZBME1e8LHvYdFbfLg== (System.Exception #=qDxDKLI_uaGBoMRLus6Yhsg==) [0x00000] in :0
at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) [0x00000] in :0
at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in :0
at System.AppDomain.ExecuteAssembly (System.AppDomain , System.Reflection.Assembly , System.String[] ) [0x00000] in :0
at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly a, System.String[] args) [0x00000] in :0
at System.AppDomain.ExecuteAssembly (System.String assemblyFile, System.Security.Policy.Evidence assemblySecurity, System.String[] args) [0x00000] in :0
at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in :0
Thread: .locals, State: Running, Alive: True, Background: False`

WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v4.0.30319
Setting breakpad minidump AppID = 92800
Steam_SetMinidumpSteamID:  Caching Steam ID:<PHONE_NUMBER>9385322 [API loaded no]
2016-06-30 23:14:22.603 SpaceChem.bin.osx[10336:993555] 23:14:22.602 WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
The game experienced an error. A report has been saved:
"/Users/omerenbar/.local/share/Zachtronics Industries/SpaceChem/crashes/004.zicrash"
KQ: Error reading KQ:Bad file descriptor

Not working here either.
spacechem-terminal.txt
004.zip

Whoops... sorry for missing this bug!
Those exceptions (@LeoDT, @danielmunoz, @jalbright) mentioning 'GlyphSheet: No clean breaks found between glyph rows' is what the SDL downgrade is meant to fix. In the newest magical .app bundle, I'm shipping old SDL to replace the ones built in to SpaceChem's .app file.
@omere2: Please upload the mentioned 004.zicrash file from the error message, or manually rename it to have a .zip extension and paste the exception.txt file contents here please.

...Wow. Seems the Macbook I prepared this on actually still had my old SDL hacks around, and I managed to pack the wrong version of SDL into the .app bundle. Impressive!
(SDL_image needs to be downgraded to 1.2.10. I'll prepare a new .app tonight.)

Manual fix: Download https://www.libsdl.org/projects/SDL_image/release/SDL_image-1.2.10.dmg , open it, replace the SDL_image.framework inside ~/Library/Application\ Support/Steam/steamapps/common/spacechem/SpaceChem.app/Contents/Frameworks/ with the one from the .dmg.

@leafi seems that I have the exact same error 'GlyphSheet: No clean breaks found between glyph rows'
I will wait for your update.

@leafi  I tried your manual fix with the same results.
007.zip
Exception:
#=qG_Cl0xPUIXAr7Gxbj9xr1UFh0GNaWUpitkXmSs4mohU=: GlyphSheet: No clean breaks found between glyph rows.
at #=qLVNq3PVNh2PfpPGTi0HeUw==.#=q8zlhvQt5aBUR6IR0eIS_nQ== () <0x41728b0 + 0x00273> in :0
at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) <0x4171a50 + 0x0008f> in :0
Thread: , State: Running, Alive: True, Background: False
at #=qYCigg8hLK$7E5EiWde8WJg==+#=q5XL4rRNSsLDu1uYr6ozmWiKNS$meZV1AZZikvTEP_PM=.#=q$1lj7LzPsgPU14Z3i$WhB_E5yBeowzHfDVfYPvvpwEs= (System.Threading.Thread #=qFgBOpMisigH6TDO25lRJcA==) [0x00000] in :0
at #=qYCigg8hLK$7E5EiWde8WJg==.#=qguQNvTEYvLaTIJaJx0lmEA== (System.Exception #=qLFoUTKR8Y3OaLg7ljBcblQ==, System.String #=qGLoTrVPSA4Cyj5m1oV8llg==, System.Object[] #=qrV2jy6hl8b_C29KqMesjDw==) [0x00000] in :0
at #=qYCigg8hLK$7E5EiWde8WJg==.#=qr$ULSWLnd_6uZTLZW$F9dg== (System.Exception #=qg$NDjlvFfuJddthg8tkGuQ==) [0x00000] in :0
at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=q$ySgeZBME1e8LHvYdFbfLg== (System.Exception #=qDxDKLI_uaGBoMRLus6Yhsg==) [0x00000] in :0
at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) [0x00000] in :0
at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in :0
at System.AppDomain.ExecuteAssembly (System.AppDomain , System.Reflection.Assembly , System.String[] ) [0x00000] in :0
at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly a, System.String[] args) [0x00000] in :0
at System.AppDomain.ExecuteAssembly (System.String assemblyFile, System.Security.Policy.Evidence assemblySecurity, System.String[] args) [0x00000] in :0
at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in :0
Thread: .locals, State: Running, Alive: True, Background: False

@leafi Tried the manual fix, got a different exception.
Exception:
System.DllNotFoundException: ../Frameworks/SDL_image.framework/SDL_image
  at #=qLVNq3PVNh2PfpPGTi0HeUw==.#=q8zlhvQt5aBUR6IR0eIS_nQ== () <0x41b7f88 + 0x00273> in <filename unknown>:0
  at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) <0x41b7128 + 0x0008f> in <filename unknown>:0

Thread: , State: Running, Alive: True, Background: False
  at #=qYCigg8hLK$7E5EiWde8WJg==+#=q5XL4rRNSsLDu1uYr6ozmWiKNS$meZV1AZZikvTEP_PM=.#=q$1lj7LzPsgPU14Z3i$WhB_E5yBeowzHfDVfYPvvpwEs= (System.Threading.Thread #=qFgBOpMisigH6TDO25lRJcA==) [0x00000] in <filename unknown>:0
  at #=qYCigg8hLK$7E5EiWde8WJg==.#=qguQNvTEYvLaTIJaJx0lmEA== (System.Exception #=qLFoUTKR8Y3OaLg7ljBcblQ==, System.String #=qGLoTrVPSA4Cyj5m1oV8llg==, System.Object[] #=qrV2jy6hl8b_C29KqMesjDw==) [0x00000] in <filename unknown>:0
  at #=qYCigg8hLK$7E5EiWde8WJg==.#=qr$ULSWLnd_6uZTLZW$F9dg== (System.Exception #=qg$NDjlvFfuJddthg8tkGuQ==) [0x00000] in <filename unknown>:0
  at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=q$ySgeZBME1e8LHvYdFbfLg== (System.Exception #=qDxDKLI_uaGBoMRLus6Yhsg==) [0x00000] in <filename unknown>:0
  at #=q2MHgewmxt9cdxLxBGG$zCsSY1nU1MtXK7J7sI8ZiWkY=.#=qtJinfaPEqp6B13oJP0fYuQ== (#=qLVNq3PVNh2PfpPGTi0HeUw== #=q914uQhbuf6NAKv2o58RDJQ==) [0x00000] in <filename unknown>:0
  at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in <filename unknown>:0
  at System.AppDomain.ExecuteAssembly (System.AppDomain , System.Reflection.Assembly , System.String[] ) [0x00000] in <filename unknown>:0
  at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly a, System.String[] args) [0x00000] in <filename unknown>:0
  at System.AppDomain.ExecuteAssembly (System.String assemblyFile, System.Security.Policy.Evidence assemblySecurity, System.String[] args) [0x00000] in <filename unknown>:0
  at #=qrEwbiPMszIEB9Azc_qhPwVFBd_U1GAjarN4Be6khTX0=.#=q6SCD5KBoFBNiZtK8BfDrdQ== (System.String[] #=q7uUkEPDZNgVk4qYJrF82EQ==) [0x00000] in <filename unknown>:0

Thread: .locals, State: Running, Alive: True, Background: False

$ ./SpaceChem.bin.osx
WARNING: The runtime version supported by this application is unavailable.
Using default runtime: v4.0.30319
Setting breakpad minidump AppID = 92800
Steam_SetMinidumpSteamID:  Caching Steam ID:<PHONE_NUMBER>0873899 [API loaded no]
2016-07-04 21:31:56.212 SpaceChem.bin.osx[37650:1571440] 21:31:56.212 WARNING:  140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
The game experienced an error. A report has been saved:
"/Users/eugene/.local/share/Zachtronics Industries/SpaceChem/crashes/000.zicrash"
KQ: Error reading KQ:Bad file descriptor

000.zicrash.zip
Thanks!

@eugene-lim ahh, yes, needs a symlink too...
cd (blah blah blah)/SpaceChem.app/Contents/Frameworks/SDL_image.framework
ln -s Versions/A/SDL_image SDL_image

Reckon it's the MonoKickstart build I'm shipping; it seems to be less good with paths as compared to full-fat desktop Mono.

@leafi - my mistake. I followed the instructions wrong.
It works now. thanks.

@leafi Got it to work too after updating the symlink. I think I messed it up while moving stuff around. Thanks!

@leafi Confirmed! Replacing the SDL_image.framework worked great. For me, my symlinks were already in place. This was after running your Fix It script yesterday, on OS X 10.11.5.
Thanks for keeping this great game alive!

@leafi Working here as well.  Thanks so much!

Fix worked for me too. Saved the day!

Worked. Thank you so much.

Hi all - I've finally found time to integrate the fix into the .app and made a new release. If you can find time to give it a quick run & ensure it works I'll be eternally grateful. <3


[Question] iOS Performance Benchmark

❓ General Questions

Hi, I have read the tutorials for having chats in Colab, including a benchmark:

I wonder what are the procedures for benchmarking the performance on iOS Devices instead of on Colab. Thank you so much for your help!

In this case, we show up the stats on the app.


Feature request: Add option to stop search of a key

VERSION
Version 1.5.5
ISSUE DESCRIPTION
When using *, searches can take a while. I sometimes figure in the middle of it that I know the exact search term. I would like to stop the current search (and any Scans happening in the background).

this is quite a necessary function that allow users to stop scanning by themself, I will consider it


I've compiled it, so why do prompt  to install these packages in my project?

These dependencies were not found:

node-gyp in ./~/sqlite3/~/node-pre-gyp/lib/util/compile.js
npm in ./~/sqlite3/~/node-pre-gyp/lib/util/compile.js

To install them, you can run: npm install --save node-gyp npm

What command did you execute? You have given me no information at all.
Thanks.


Interop built dependencies & broken build by unwize define config

Describe the bug
I managed to use Vite on my big vue-cli-3 project. However, few libs imports were raising errors, such as @mapbox/mapbox-gl-draw which was version 1.2.0.
ReferenceError: require is not defined

due to this line in the source:  if (typeof module !== 'undefined' && require.main === module), which seems to be a weird way to deal with.
I have done a lot of debug to understand what is going on. I think this is related to this issue.
https://github.com/vitejs/vite/issues/1724#issuecomment-767619642
It seems that in my case, @mapbox/mapbox-gl-draw is not detected to needs interop (needsInterop returns false) (while in a very minimal repro I installed 1.2.2 and needsInterop returns true).
Hence, updgrading to version 1.2.2 solved my problem. However I have to mention that during my tests I did this:
// vite.config.js
import { defineConfig } from 'vite'

export default defineConfig({
  define: {
    require: {},
  },
});

which completely breaks the interop imports.
Reproduction
To see how this vite.config.js breaks imports, see this minimal repro project:
break-require-default.zip
After yarn & yarn vite, you can see the error opening localhost:3000:
// Uncaught TypeError: define_require_default is not a function
// at dep:axios:1

and if you look into generated file node_modules/.vite/axios.js: it breaks define_require_default:
// <define:require>
var define_require_default = {};

// dep:axios
var axios_default = define_require_default("./node_modules/axios/index.js");
export {
  axios_default as default
};
//# sourceMappingURL=axios.js.map

I suggest to add a security on Vite to check if vite.config.js has this breaking define of just ignore it.
System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
  System:
    OS: macOS Mojave 10.14.6
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
    Memory: 193.29 MB / 16.00 GB
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 12.20.1 - ~/.nvm/versions/node/v12.20.1/bin/node
    Yarn: 1.17.3 - ~/.yarn/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v12.20.1/bin/npm
  Browsers:
    Chrome: 89.0.4389.114
    Firefox: 86.0.1
    Firefox Developer Edition: 71.0
    Firefox Nightly: 76.0a1
    Safari: 14.0.3
    Safari Technology Preview: 13.2
  npmPackages:
    vite: ^2.1.5 => 2.1.5

Used package manager:
yarn

Before submitting the issue, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the docs.
[x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[x] Provide a description in this issue that describes the bug.
[x] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

require: {} is a fairly dangerous config to do as it may cause side-effects outside of prebundling. The docs recommend to only use constants for define. Re ReferenceError: require is not defined I think a better solution is to contact the package author to fix the way they publish the library, if (typeof module !== 'undefined' && require.main === module) syntax is off as you've showed. I'm not sure if this is already addressed today, but I'll close this for now as it's an issue with the @mapbox/mapbox-gl-draw publishing


Weird codegen

suicidal.rs exposes weird behavior of the codegen:
For the negative branch the following code is being produced:
    (set_local $0
     (call $_ext_memcpy
      (i32.const 1)
      (get_local $5)
      (get_local $2)
     )
    )

I began to suspect externalization of memcpy et al but it turned out that this also happens with std versions prior externalization.
I'm not sure why this codegen behavior exposed, but I tend to think that it is more probable that we have another instance of an UB here, not a codegen bug in Emscripten.

It turned out that, in such cases memcpy always called with length 0. It is legal to call memcpy with zero length as long as dst and src pointers are non-null.


Provide wheel packages for Linux on PyPI

Is there are reason wheel packages for Linux to be missing from PyPI ?
If there isn't a technical reason I am advocating for Linux wheel packages to be uploaded to PyPI (preferably upload one for the latest release as well).
In my particular case we're building a Docker image which needs python3-saml (provides wheel) which in turn depends on xmlsec which pip3 tries to compile from source.  The environment inside the docker image is very limited and we don't have access to all of the required -devel libraries in order to builds from source (vendor provides xmlsec1.rpm but not xmlsec1-devel.rpm).
Let me know how you feel about providing those packages on PyPI?

Hi @atodorov, yes, the support of PEP 513 wheels was requested already; I have explained my reasoning here. You can also roll out your own manylinux2010 wheels using the instructions from here.


Make "assertVisible" find part of a text

In my React Native application the test should open an article and check it's content being visible afterwards. I can't make it work yet, since it seems to only succeed when the string of assertVisible is the complete content of a screen element. I am not able to provide the whole article text in the yaml file. Also pasting the whole article in the test yaml makes it unreadable and
the content can contain text styling, line breaks and more.
My understanding of something being visible is fullfilled, if it is visible as part of a bigger text:

assertVisible: "World"
This should be true if an element containing "Hello World!" is visible.

Would be great to make this the standard behaviour. If necessary you can possibly add an option to use the current behaviour.
Best regards.

Is this one for the maestro repo? I don't see a documentation specific problem here.


Exploding on d1 creates infinite loop

Describe the bug
If you try and explode on a d1 it will create an infinite loop because it will always explode.
To Reproduce
Roll any of the following notations:

d1!
d1!!
d1!p
d1!!p

Expected behaviour
I'm thinking that the best option is to disallow exploding on a d1.
For context, Roll20 seem to throw an error:

You must roll a d2 or higher to roll exploding dice.

This is fixed in the master branch and will go out in the next major release (v4.0.0).


ENG-5802 retrofit library integration

add retrofit
remove old HttpUrlConnector
add retrofit callback and associated items
integrate retrofit implementation into NIDServiceTracker
fix integration tests (they seem to be more reliable now)
ensure libs on android and reactive native flavors build

Notes:
debug and production flavor will send events to "https://receiver.neuroid.cloud/c/"
NIDJobServiceManager configures the server URL when setting up the Retrofit instance from endpoint in getApiService()
This is a big one so feel free to ping me and I can walk you through it. Thank you!

Put on hold until 3.1.x is ready for release. Do not close.


Skip uppercase regex tests before 2.4.0

This feature was backported in #4219 and will only be present in version 2.4 and newer. The test must be skipped for mixed cluster cases with nodes older than 2.4.
Signed-off-by: Andrew Ross<EMAIL_ADDRESS>Issues Resolved
#4831
Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@nknize I think we need this version guard after the backport in #4219. Can you take a look?

The test "org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/190_index_prefix_search/search with uppercase regex}" failed again in gradle-check 5204 and I'm not sure why. That test fails reliably without the fix in this PR locally for me, but when I apply this change I cannot reproduce the error. Not sure what is going on here...

The test "org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/190_index_prefix_search/search with uppercase regex}" failed again in gradle-check 5204 and I'm not sure why. That test fails reliably without the fix in this PR locally for me, but when I apply this change I cannot reproduce the error. Not sure what is going on here...

I see the skip is not applied in the failure cases. The the test is executed against v2.3.1 cluster.
REPRODUCE WITH: ./gradlew ':qa:mixed-cluster:v2.3.1#mixedClusterTest' --tests "org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT.test {p0=search/190_index_prefix_search/search with uppercase regex}" -Dtests.seed=DA47345E5530945F -Dtests.security.manager=true -Dtests.jvm.argline="-XX:TieredStopAtLevel=1 -XX:ReservedCodeCacheSize=64m" -Dtests.locale=cs -Dtests.timezone=America/St_Thomas -Druntime.java=17
NOTE: leaving temporary files on disk at: /var/jenkins/workspace/gradle-check/search/qa/mixed-cluster/build/testrun/v2.3.1#mixedClusterTest/temp/org.opensearch.backwards.MixedClusterClientYamlTestSuiteIT_DA47345E5530945F-003

The successful run of gradle check shows that the test {p0=search/190_index_prefix_search/search with uppercase regex} was skipped as expected. I don't know why the tests were run in the failure case above. @heemin32 any idea why it ran those tests on check 5204?

Test run 5213 shows:
Git clone: https://github.com/andrross/OpenSearch.git with ref: 852cd348675ab4f43e2492f5f6170d3c471a14df

which is the commit of this PR and seems to be correct. However, test run 5204 shows:
Git clone: https://github.com/opensearch-project/OpenSearch.git with ref: c2e6a03b741c817431a039144c98c595d04cb99b

which is an unrelated commit? Seems like some wires were crossed here. I'm going to merge this change because I think it should unblock things and open another issue about the gradle check workflow.

The successful run of gradle check shows that the test {p0=search/190_index_prefix_search/search with uppercase regex} was skipped as expected. I don't know why the tests were run in the failure case above. @heemin32 any idea why it ran those tests on check 5204?

Github bug it seems. https://build.ci.opensearch.org/job/gradle-check/5204/ is for [PR #4832](https://github.com/opensearch-project/OpenSearch/pull/4832): backport 2x exclude jettison version brought in with hadoopminicluster actually.


New OMIM data and existing Mondo record: ACTB-ASSOCIATED SYNDROMIC THROMBOCYTOPENIA

OMIM has a new record and includes an alt name that matches the primary record name in Mondo. My question is whether these two are the same, and does Mondo plan to map the new OMIM record to the existing Mondo ID? OR are they distinct concepts (the ClinGen record is broader? ) and the MIM record will get a new Mondo ID that is a child of the existing term?
OMIM 620475 (uses 'ACTB-ASSOCIATED SYNDROMIC THROMBOCYTOPENIA' as an alternate name)
Mondo:0100433
It looks like ClinGen hasn't yet evaluted/curated the new MIM number either: https://search.clinicalgenome.org/kb/conditions/MONDO:0100433
MedGen's got a naming conflict here, so we'll follow the preferred names from Mondo and OMIM for now and keep separate until I hear otherwise.

@miajsullivan - is this term the same as the new OMIM term? Can we add the OMIM ID as an xref?
Thanks!
related to https://github.com/monarch-initiative/mondo/issues/4019

Excellent, thanks so much @miajsullivan, I appreciate the quick reply!
@kanems, I'll add the OMIM ID as an xref.


Repo sync for protected CLA branch

The pull request is created from master637661990761835429 to master to fix git push error for protected CLA branch

@shsagir : Thanks for your contribution! The author(s) have been notified to review your proposed change.


⚠ Bofrost.lu has degraded performance

In 3737e15, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 936 ms

Resolved: Bofrost.lu performance has improved in 51c180a.


this.$refs.croppa.chooseFile() is not opening file explorer

After calling this.$refs.croppa.chooseFile() nothing happens. Clicking on preview windows opens explorer window.
Enviroment:

Ubuntu: 16.04
Chrome: 65
Vue: 2.5.8

==== UPDATES =====
It's happening only if this.$refs.croppa.chooseFile() is called in same function call when the flag to display croppa is set to true.
    test() {
      this.editPicture = true; // v-if="editPicture" is set on croppa element
      this.$nextTick().then(() => {
        setTimeout(() => { // Timeout is set just for testing same behaviour with or without it
           // NOTHING HAPPENS AT THIS POINT (BUG)
           this.$refs.croppa.chooseFile();
        }, 150);
        // Auto open file explorer
      });
    },

Yes, that's normal because if v-if="false" the component is not rendered. You can use v-show="false" to hide it while still render the DOM.

Yes but I'm calling chooseFile inside of nextTick and for the test after timeout at which point the component should be rendered. So I don't see reason why it shouldn't work for example from above? I'm using v-show as a workaround but I would prefer v-if as for my uscase component will not be needed in most of the cases.

https://codepen.io/zhanziyang/pen/JLRgLG?editors=1010
See this demo. It works fine here.

@zhanziyang indeed it is! Thanks for the demo I will do some more investigation tomorrow to see what is going on in context of my application and demo code. I will close the issue for now.


As an Administrator: Have the ability to  define when allocations should be automatically created

The ability to enable default allocations allows you to specify which opportunities to exclude based on Opportunity Record Type and Type, but it would be useful to also include stage criteria.
Ideally it would be great to set criteria based on the Opportunity Status: Open, Closed, Closed Won.

@lyndsayneer Interesting idea - can you describe the use case where you would want to exclude by Opportunity Stage?

:+1:

@judisohn We have a client who would prefer to only have an allocation created when the opportunity is considered won in the pipeline. In the initial prospecting and cultivation stages it seems pre-mature to add an allocation for this client because these are budget codes within their instance.

Interesting idea! For your clients' peace of mind, the GAU rollups only happen for closed/won opportunities.

**lurch: add

@njjc Yes we mentioned this to them as well, but they still have reservations with user adoption as this is a new implementation and still getting used to reporting filters!

Tracking W-008559

NPSP now has an integration with the Accounting Subledger product which achieves part of what is requested. Additionally, generating Allocations based on a default GAU, or Campaign Specific GAU Allocation is possible currently -
NPSP Allocation Configuration
https://powerofus.force.com/s/article/NPSP-Configure-Donation-Allocations
Accounting Subledger
https://powerofus.force.com/s/article/ASL-How-Accounting-Subledger-Runs-the-Numbers
https://www.salesforce.org/accounting-subledger/


Update on Payment card number

Hello,
An update on Payment card number was released the 2022-02-19T19:22:52Z. Check for any new Issuer identification number edit. Link to the diff. Here is the summary:
Remove leading zero from dates

← Previous revision
Revision as of 19:22, 19 February 2022

Line 165:
Line 165:

|-

|-

|[[Troy (card scheme)|Troy]]

|[[Troy (card scheme)|Troy]]

|65 (Discover co-branded<ref></ref>), 9792<ref></ref>

|65 (Discover co-branded<ref></ref>), 9792<ref></ref>

|style="color:green" |Yes

|style="color:green" |Yes

|16

|16

If this Wikipedia's edit does not affect us, just ask for this issue to be close.
In case of trouble, ask for @aloisdg

Changed wording, does not concern us


Improved documentation of c_dim

Changing c_dim breaks imread() since scipy.misc.imread generally returns images with 3 channels. It also requires reshaping batch_images during training. This bit of documentation improves clarity and solves issues like #26.
What do you think? If you would like, I could explicitly add support for grayscale images, which is the most common reason as to why c_dim would be modified.

Thanks. I think this might solve the problem like #26 but support for grayscale images should be also great!


[docs] mention MS4W option for Windows install

add short tip to installation.rst in the Windows section, that MS4W is available containing mod_wsgi, pycsw, etc.

Thanks @jmckenna !


Multiple triangulation

When I tried to put a triangulation in many different places into for loop to proceed it two or more times the Unity crashes does anyone have an idea what to do with that?

Can you share the code? I could imagine the processing locking up Unity if it's too intensive and looping too quickly.


tests are not run

Setting -DMFEM_ENABLE_TESTING=ON causes this message:
otal Test time (real) =   0.04 sec

The following tests FAILED:
	  1 - unit_tests (Not Run)
	  2 - sedov_tests_cpu (Not Run)
	  3 - sedov_tests_debug (Not Run)
	  4 - tmop_pa_tests_cpu (Not Run)
	  5 - tmop_pa_tests_debug (Not Run)
	  6 - debug_device_tests (Not Run)
	  7 - ex0_ser (Not Run)
	  8 - ex1_ser (Not Run)
	  9 - ex2_ser (Not Run)
	 10 - ex3_ser (Not Run)
	 11 - ex4_ser (Not Run)
	 12 - ex5_ser (Not Run)
	 13 - ex6_ser (Not Run)
[...]

Test executables weren't built.

Hi @yurivict,
Can you provide the full list of commands you are executing?
Is this something that worked before and now is not working with mfem-4.3?
Tzanio

cmake -DMFEM_USE_MPI:BOOL=false -DCMAKE_C_COMPILER:STRING="cc"  -DCMAKE_CXX_COMPILER:STRING="c++"  -DCMAKE_C_FLAGS:STRING="-O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -fno-strict-aliasing "  -DCMAKE_C_FLAGS_DEBUG:STRING="-O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -fno-strict-aliasing "  -DCMAKE_C_FLAGS_RELEASE:STRING="-O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -fno-strict-aliasing "  -DCMAKE_CXX_FLAGS:STRING="-O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -fno-strict-aliasing -fno-omit-frame-pointer  "  -DCMAKE_CXX_FLAGS_DEBUG:STRING="-O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -fno-strict-aliasing -fno-omit-frame-pointer  "  -DCMAKE_CXX_FLAGS_RELEASE:STRING="-O2 -pipe -fno-omit-frame-pointer -fstack-protector-strong -fno-strict-aliasing -fno-omit-frame-pointer  "  -DCMAKE_EXE_LINKER_FLAGS:STRING=" -fstack-protector-strong "  -DCMAKE_MODULE_LINKER_FLAGS:STRING=" -fstack-protector-strong "  -DCMAKE_SHARED_LINKER_FLAGS:STRING=" -fstack-protector-strong "  -DCMAKE_INSTALL_PREFIX:PATH="/usr/local"  -DCMAKE_BUILD_TYPE:STRING="Release"  -DTHREADS_HAVE_PTHREAD_ARG:BOOL=YES  -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=YES  -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON -DBUILD_SHARED_LIBS:BOOL=ON -GNinja

make

make test

I never tried to run tests before.

Hello @yurivict.
Looking at this, it seems you may not be building in a dedicated build directory.
For the record, MFEM has two build systems: Makefile (I will refer to as "original") and CMake. CMake is an out-of-source build system generator, that will generate a build-system in Makefile or another language like Ninja. Here, you chose Ninja, which is a good choice with CMake (and hopefully works with MFEM). But you are not building out-of-source.
The clue was that you are missing ".." at the end of the first command. You are apparently configuring MFEM with CMake in-source (directly in the mfem root directory), and then running make and make test. The last 2 command will call the the original Makefile build system instead of the generated Ninja.
Here are your options:

Use the original Makefile

cd <mfem-root-dir>
make config [...options...]
make all -j 8   # Build everything
make test       # Run the tests

Use CMake + Makefile (option 1: explicit makefile)

cd <mfem-root-dir>
mkdir build
cd build
cmake [...options...] ..   # Note the ".."
make -j 8                  # Build MFEM
make tests -j 8            # Build unit-tests
make examples -j 8         # Build examples
make miniapps -j 8         # Build miniapps
make test                  # Run the tests

Use CMake + Makefile (option 2: generic build, cmake wrappers)

cd <mfem-root-dir>
mkdir build
cd build
cmake [...options...] ..                  # Note the ".."
cmake --build . -j 8                      # Build MFEM
cmake --build . --target tests -j 8       # Build unit-tests
cmake --build . --target examples -j 8    # Build examples
cmake --build . --target miniapps -j 8    # Build miniapps
ctest --output-on-failure -T test         # Run the tests

Use with CMake + Ninja (this is not what we are used to do, but it works)

cd <mfem-root-dir>
mkdir build
cd build
cmake [...options...] -GNinja ..          # Note the ".."
cmake --build . -j 8                      # Build MFEM
cmake --build . --target tests -j 8       # Build unit-tests
cmake --build . --target examples -j 8    # Build examples
cmake --build . --target miniapps -j 8    # Build miniapps
ctest --output-on-failure -T test         # Run the tests

No, it uses out-of-soutce build. Sorry, I missed .. in my previous message.

Still, you are generating a Ninja build system, and then running make commands.
Please try following one of the suggestion above, and let us know if the issue remains.
Thank you.

Note: running the test with CMake is described here: https://github.com/mfem/mfem/blob/c528f79c9fc2f92612660ccf0f98cd1fe95879dc/INSTALL#L825-L837

Hello @yurivict, did this help?

@yurivict @tzanio @v-dobrev since I was able to reproduce the problem by building with -GNinja and then using Makefile commands, I believe this is solved and more clear now. (I also wrote a how-to article about this).
I believe we can close this.

Link to Adrien's article: https://github.com/mfem/web/blob/5621afc9e4c3a449393aa282211bf85262ecb180/src/howto/build-systems.md

I will close this now, but please feel free to reopen if you still have questions.


WIP: LCD T&H with date/time display

Need to figure out on which DP to put the time. And likely update on any message. They get out of sync by a minute within the hour.

@JohanBendz
I'd like to ask for help.
2024-01-03T21:57:22.348Z [log] [ManagerDrivers] [Driver:lcd_th_sensor] [Device:8862b603-79ea-41f3-8ca0-40f140cf33ee] measure_humidity | relativeHumidity - measuredValue (humidity): 67
  zigbee-clusters:cluster ep: 1, cl: tuya (61184) unknown command received: ZCLStandardHeader {
  frameControl: Bitmap [ clusterSpecific, directionToClient ],
  trxSequenceNumber: 81,
  cmdId: 36,
  data: <Buffer 0c 00>
} { dstEndpoint: 1 } +231ms
  zigbee-clusters:endpoint ep: 1, cl: tuya (61184), error while handling frame unknown_command_received {
  meta: { dstEndpoint: 1 },
  frame: ZCLStandardHeader {
    frameControl: Bitmap [ clusterSpecific, directionToClient ],
    trxSequenceNumber: 81,
    cmdId: 36,
    data: <Buffer 0c 00>
  }
}

Correct me if i'm wrong but i believe the above request is send by the sensor to request for date/time in some format likely epoch or something. But for the life of me i can't find how to answer with code and or if im actually looking at the request for time update.

Hi there @jepke, not sure I get the issue here.. your PR is quite a mess with two drivers and images and icons etc that do not match.. is this an earyl trial to get something working? Perhaps better to start an issue and ask for me to have a look at your code?

Yea i need to fix that up, based all my PR's off SDK3 branch but something is funky with that app.json file that gets regenerated by homey app install or something i dont know. Might be something else i do locally.  It started happening after #581. For now this is that last device i have my hands on that doesnt work. Once the majority is in SDK3 i need to rebase everything i have locally.
TS0601
_TZE200_locansqn

this is the device i have which can display date and time but there's no code to actually send date/time or respond to its request to get date/time. So when the device is booted it just shows/starts at 00:00 00/00
i've googled and found they got it fixed in a few projects but reading up on that code i still dont know the DPID and if its even in the tuya specific cluster.
I found something that suggested 0x24 is the request command for date/time which equals 36 in decimal which makes me believe the debug output from my last message is the device its request for date/time value.

@jepke The app.json is nothing you should make changes in. it is a generated file.
https://apps.developer.homey.app/the-basics/app

I found something that suggested 0x24 is the request command for date/time which equals 36 in decimal which makes me believe the debug output from my last message is the device its request for date/time value.

Yes, Cmd ID 36 (0x24) is the Set Time command. I guess it's just to simple to use Zigbee Cluster 10.. they HAVE to come up with their own way using commands 😂

@jepke The app.json is nothing you should make changes in. it is a generated file. https://apps.developer.homey.app/the-basics/app

Yea been just reading up in the SDK docs about it. Either homey app run or homey app install or both generates it and since its not in the .gitignore it gets pushed into a commit. I'm still learning on the job.
Gotta cleanup my local branches as it got a mess real quick lately. Ill pay more attention to what happens when to that file. And fetch origin before pushing to github.
@JohanBendz
My lcd thingy says it has cluster 10 in the zigbee interview not sure if it works tho. But any pointers or other drivers i can take a peek to see how that works.
Ill also redo this PR once i have cleaned up locally and rebase of the the updated SDK3 branch.

  zigbee-clusters:endpoint ep: 1, cl: time (10), error while handling frame binding_unavailable {
  meta: { dstEndpoint: 1 },
  frame: ZCLStandardHeader {
    frameControl: Bitmap [  ],
    trxSequenceNumber: 143,
    cmdId: 0,
    data: <Buffer 07 00>
  }

Guess tuya did something with CL10 (time) havent noticed these before.

Hi @jepke, how is work going on this driver? :)

Hi @jepke, how is work going on this driver? :)

was still strugling with the date/time update thing and then got caught up in other things. Hopefully some more time for fun things after this week.

@JohanBendz
i ended up hooking these lcd t&h sensors up to my zigbee2mqtt. This PR fully works with the temp hum and battery i just never got the damn time to update on those so the display would display correct date/time.
Ill leave it up to you what to do with this PR. Hopefully someday i get enough knowledge about zigbee and tuya to finaly fix it.

Have you tried adding _TZE200_locansqn to the temphumidisensor4 driver? It already supports the pretty much identical, though with a color LCD, _TZE200_vvmbj46n


Make travis only run product tests on python 2.7

Since we want to exclude most of the tests from being run on 2.6, it seemed clearer to explicitly write out what we did want to run.

I'm not sure if I read build output right, but I couldn't find trace of 2.6 tests being executed https://travis-ci.org/prestodb/presto-admin/jobs/160172002

Alright cleaned up the commits.  Should be ready for review again.

LGTM! :)

merged!


Select Box Item not rendering Properly

Hi,
I used Select Carbon Component and try below url:
https://codesandbox.io/s/2vk4n6jw7y
Issue I found that was not rendering as expected.
Thanks

If you remove the className="bx--select-input" to the Select element, and the wrapping div it renders correctly. These classes will be provided by the component itself.
To use the light version, just pass the light prop down to Select. Hope this helps!


koroshell

Is there any method for getting the updated binaries/level 3 noise reduction into koroshell?

Level 3 noise reduction is in? Or what do you mean?
   --noise_level <1|2|3>
     noise reduction level

Right. Except the koroshell UI seems to be hard coded to only accept "low" and "high" - as well as lacks options for forcing opencv, meaning if I swap the binary directly I can only run it in a VM (crashes otherwise, as the binary does if I run it with default settings) and only with level 1 and 2 noise reduction. Since koroshell was listed on the project page I was thinking there might have been some compatibility between the two. Koroshell by itself is great, but it does seem to do something wonky with RGB whereas your version here, and thank you for it, works just fine.

@Lurkios is the koroshell UI in this repo? Like does my fork build it?

@DeadSix27 To be honest I'd have had no idea. I made this github account today and it's my first time using the site.

@Lurkios I have no idea what "koroshell UI".

@DeadSix27 I read that as dripping sarcasm. If that wasn't the case then my apologies.
In the ReadMe.md file shown on the "main page" (terminology?) of this fork there's a link to waifu2x_win_koroshell. It's a gui/front-end for the original version of the converter (I think) by nagadomi (https://github.com/nagadomi/waifu2x) that lets you drag&drop a file or multiple to process - not necessary but very convenient. All it really looks to be doing is passing arguments on to the binary for nagadomi's version. Dropping your binary in over the existing one, along with the models, actually does work - but because your version introduces several new options over nagadomi's those are missing from the gui (including an option I believe most nvidia users are probably going to need to get this version to work). I was thinking there was a chance that, since koroshell was mentioned right under the link to your binary as a "waifu2x converter GUI" - there might be some method of getting those additional options to work with it. It sounds like that isn't the case.
Working on my own UI for it now. No idea what I'm doing, I expect the results will be interesting.

@Lurkios ah ye I never use a GUI i just have a python script for that. So I didn't even know that GUI existed.
The koroshell UI doesn't support level 3 yes, it's also not part of this source codes so I can not change that in anyway.
There is https://github.com/DeadSix27/waifu2x-converter-cpp/tree/master/w32-apps
But I never touched that, I'm waiting on OpenCV to implement support for unicode image file names until then its unlikely Ill make a UI or something, feel free to do one yourself tho.

@Lurkios SnowShell will be help for you! https://github.com/YukihoAA/waifu2x_snowshell/releases/tag/v1.1


Looping over input image bands

arosics version: 1.7.8
Python version: 3.10.5
Operating System: Linux Mint 21 Cinnamon

Description
In the paper introducing this package, it states: "If co-registration targets a multi-band data cube, the algorithm can be either applied band-by-band in a loop, or the co-registration results of a single band can be applied to the remaining bands."
I would like to loop over the bands of my input image, but I do not see a built in option to do so. It appears to me that the default of the correct_shifts method is to apply a single correction to all of the bands, although I am not completely sure this is what's happening when I follow the example here. Can you confirm or explain what is happening, if that's not correct?
How would you recommend to loop through the bands of an image? Is there a method for this that I am missing?
If not, the most obvious, but messy, solution I see is to create a loop to initiate a COREG object, calculate the shifts, apply the shifts, and save the output file for each band separately. However, this means I would get several output files in which I would only need one of the bands, so I would have to combine the correct bands from the correct files into one image after the initial processing. With one image I don't think that's really a big deal, but with many images, it's definitely not ideal. I think it would also be possible to not save the output file to disk each time, but to copy the shifted GeoArray into a variable in the environment. However, this still has the issue of creating a bunch of GeoArrays in which there is only one band of interest (and I'm not sure yet how to neatly compile the correct bands).
Neither of these options seem great to me, so I'm hoping you have a recommended method that allows the correction to be applied only to the band of interest.

Hi @HRodenhizer,

It appears to me that the default of the correct_shifts method is to apply a single correction to all of the bands, although I am not completely sure this is what's happening when I follow the example here.

Correct, by default, AROSICS assumes that there are no remarkable shifts between multiple bands of the same image. Thus, the misregistration is detected in a single band and then corrected in all bands based on the detected tie points.

How would you recommend to loop through the bands of an image? Is there a method for this that I am missing?

Currently, there is no method to apply a co-registration on each band individually. However, it is not a big deal to achieve that by wrapping a bit of code around the actual call of AROSICS. You can use GeoArray to get single bands from a multispectral image (or alternatively pass GDAL VRT files). Then just compute the co-registered result for each band and finally combine the bands into a multispectral image. Maybe this helps:
from geoarray import GeoArray
from arosics import COREG

pr = '/path/to/ref.tif'
pt = '/path/to/tgt.tif'

ref_b3 = GeoArray(pr).get_subset(zslice=slice(2,3))  # get the third band of the reference image
tgt_b3 = GeoArray(pt).get_subset(zslice=slice(2,3))  # get the third band of the target image

# pass the single bands to AROSICS and make sure the output is always resampled to the same pixel grid
# (you may also use COREG_LOCAL here)
CR_b3 = COREG(ref_b3, tgt_b3, target_xyGrid=[[0, 30], [0, 30]])
CR_b3.calculate_spatial_shifts()
output = CR.correct_shifts()
b3_coreg = output['GeoArray_shifted']  # GeoArray instance

You may call this in a loop for all bands and then either save the co-registered bands to disk and then stack them using GDAL or use numpy + geoarray for this:
import numpy as np

# make sure all of them cover the same area
b1_geoarray_sub = b1_coreg.get_mapPos((xmin, ymin, xmax, ymax))  # pass map bounds here
b2_geoarray_sub = b2_coreg.get_mapPos((xmin, ymin, xmax, ymax))  # pass map bounds here

# stack the bands and save the output image to disk
stacked_array = np.dstack((b1_geoarray_sub, b2_geoarray_sub))
stack = GeoArray(stacked_array, geotransform=b1_coreg.geotransform, projection=b1_coreg.projection)
stack.save('/path/to/stacked_output.tif', fmt='GTiff')

Thanks! Somehow I missed that you could pass a GeoArray instead of a filepath to COREG when reading the help page, which was the main issue I was running into.


feat: Add cartItems to EmbedParams

https://gr4vy.atlassian.net/browse/TA-3820

Closing and re-opening to try and get a stalled test to restart.


Add check if crc daemon is running and bind to default endpoints

If user set the network mode as vsock then crc daemon needs to
be running as a backgroud process or in different terminal. This
is something user might forget and direct start the crc after setup.
This patch address it for windows and linux since those platform
have some preflight check for vsock side.
$ crc setup
[...]
INFO Checking if vsock is correctly configured
INFO Setting up vsock support
'crc daemon' is not running, run it manually on different terminal/tab

fixes: #1923

This patch address it for windows and linux since those platform
have some preflight check for vsock side.

Is there an issue to implement on Darwin/macOS?

Yes it should work on darwin with the socket you use.

@praveenkumar would you be able to modify this PR for macOS? As suggested this should be an easy test... else, a follow issue is possible.

@guillaumerose @gbraad I changed the logic a bit so can be work on all the platform and also exit as soon as user try to use vsock mode.

/needs-rebase

/need-rebase


Fixed invalid File.link behaviour

File.link wrongly called LibC.symlink.
This commit closes #4115

Thanks @KCreate!


Fixes #211 and #212 where anchor link and markdown indentation didn't work as intended

Fixes #211 #212

Codecov Report

Merging #215 (99b90bf) into master (a027937) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master     #215   +/-   ##
=========================================
  Coverage     93.37%   93.37%
  Complexity      176      176
=========================================
  Files             7        7
  Lines           543      543
=========================================
  Hits            507      507
  Misses           36       36

Impacted Files
Coverage Δ

src/LaravelRequestDocs.php
99.13% <100.00%> (ø)

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


How to access Ansible variables in the Python code

Issue Type

Question

Molecule and Ansible details
ansible --version = ansible <IP_ADDRESS>
molecule --version = molecule, version 2.4.0

Molecule installation method: pip
Ansible installation method: pip

Question
How to access ansible variables inside of Python test code?
I have a role that writes a string into a file and I wanted to check if the file has the string.
e.g.:
import os
import testinfra.utils.ansible_runner

testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(os.environ['MOLECULE_INVENTORY_FILE']).get_hosts('all')

def test_passwd_file(host):
    passwd_file = host.file('/etc/passwd')
    my_string = 'my_username_value'  # How to import ansible my_username var?
    assert passwd_file.contains(my_string)

The code works, but instead of hardcoding the string (my_username on the example), I wanted to import my role's default file and use the variables in the test.
Something like:
import os
import testinfra.utils.ansible_runner

testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
    os.environ['MOLECULE_INVENTORY_FILE']).get_hosts('all')

def test_passwd_file(host):
    passwd_file = host.file('/etc/passwd')
    my_string = Ansible("include_var","./defaults/main.yml")["my_username"]
    assert passwd_file.contains(my_string)

Just figured out how:
import os
import testinfra.utils.ansible_runner

testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
    os.environ['MOLECULE_INVENTORY_FILE']).get_hosts('all')

def test_passwd_file(host, Ansible):
    ansible_vars = Ansible("include_vars", os.path.join("../../../defaults/main.yml"))["ansible_facts"]
    passwd_file = host.file('/etc/passwd')
    my_string = ansible_vars["my_username"]
    assert passwd_file.contains(my_string)

Hope this issue helps others in need.

The Ansible fixture feature is deprecated.
Here is a better way to access the variables using the host fixture and include_vars Ansible module:
import os
import testinfra.utils.ansible_runner

testinfra_hosts = testinfra.utils.ansible_runner.AnsibleRunner(
    os.environ['MOLECULE_INVENTORY_FILE']).get_hosts('all')

def test_passwd_file(host, Ansible):
    ansible_vars = host.ansible("include_vars", "file=../../../defaults/main.yml")["ansible_facts"]
    passwd_file = host.file('/etc/passwd')
    my_string = ansible_vars["my_username"]
    assert passwd_file.contains(my_string)

This isn't a Molecule issue, this is really a testinfra issue.  However, I personally don't recommend this approach.  If one inadvertently changes a variable, the tests will continue to pass.
As an example, if the listen port were a variable and it was changed, the tests may consume the listen port variable and continue to function, even though this change could have drastic side effects when deployed.
Again, this is more of a testinfra question than a Molecule question.  Closing, since we have had this issue asked quite a few times.  See closed issues.


Comments doesn't load on production environment

The comments work perfectly on dev environment but not in prod.
I have seen some similar issues but I have already tried with: "assetic: dump" and "assets: install"  and still no luck, any ideas what's going on ?
Heroku logs show me that /js/35a8e64.js is not found (404 error).

#assetic configuration
assetic:
    debug:          "%kernel.debug%"
    use_controller: false
    bundles:        ["FOSCommentBundle"]
    #java: /usr/bin/java
    filters:
        cssrewrite: ~
        lessphp:
            file: %kernel.root_dir%/../vendor/oyejorge/less.php/lessc.inc.php
            apply_to: "\.less$"
        #closure:
        #    jar: "%kernel.root_dir%/Resources/java/compiler.jar"
        #yui_css:
        #    jar: "%kernel.root_dir%/Resources/java/yuicompressor-2.4.7.jar"

Solved it by searching the 35a8e64.js in the development environment, copy-pasted it to a new js and uploaded it manually to heroku. Assetic:dump should have done this.


"ȘOMCUTA MARE", "Buciumi", "Ciolt", "Hovrila" and "Vălenii Șomcutei" are listed in the drop-down menu

Description:
"ȘOMCUTA MARE", "Buciumi", "Ciolt", "Hovrila" and "Vălenii Șomcutei" are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "ȘOMCUTA MARE" in the search bar.

Expected results
The location is listed in the drop-down menu as "Oraș ȘOMCUTA MARE, MARAMUREȘ" and "Oraș ȘOMCUTA MARE, MARAMUREȘ (ȘOMCUTA MARE)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Type "Buciumi" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Buciumi, MARAMUREȘ (ȘOMCUTA MARE)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Type "Ciolt" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Ciolt, MARAMUREȘ (ȘOMCUTA MARE)".

Step 6
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 7
Type "Hovrila" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Hovrila, MARAMUREȘ (ȘOMCUTA MARE)".

Step 8
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 9
Type "Vălenii Șomcutei" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Vălenii Șomcutei, MARAMUREȘ (ȘOMCUTA MARE)".


Black rectangles in Minish Cap without BIOS

Certain sprites are just displayed as black rectangles or otherwise distorted.
It happens during the opening cutscene with Vaati, but it's also apparent every time you shrink during the shrinking cutscene. Doesn't happen on Windows.
I'll try and get a screenshot comparison soon.
Edit: it just occured to me that this is a common issue I've seen several years back without BIOS in other emulators, and I was having trouble loading the BIOS, so this is probably more an issue with SkyEmu's provided BIOS alternative.
Tested on: 104c287
Left is Android without BIOS, right is Windows with BIOS:

I also did a quick test with Windows with BIOS, and it had similar issues.

Yep, definitely a COG BIOS issue. I filed an issue on that github referencing this so that we don't lose track of it.

This could be closed once https://github.com/skylersaleh/SkyEmu/blob/dev/src/gba_bios.h is regenerated from the latest version of the COG BIOS


Use a Confinement Queue to Protect IncrementalCompilationState

This class is serendipitously used only from the main queue for the
Driver's usual use cases. But we have no reason to expect clients of
libSwiftDriver to manipulate this class in the same manner. Provide a serial
confinement queue and protect the mutable members of
IncrementalCompilationState with it.
In the future, we ought to drop the queue and use actors.
rdar://75744005

@swift-ci test

It would be good to consider at some point using a Lock wrapper over pthread_mutex_t, since in general it can be more efficient than locking via dispatch queue.

@swift-ci test

⛵


Unable to connect to queue? using the UI. Constantly attaching...

See the following GIF. The server constantly tried to connect, and "attach" to server.
I am running on WSL2, but it should not make a difference. I can see the UI is connecting to localhost:9181 and I see the network requests are returning OK and resolving.

Hi @viperfx, thanks for reporting. What version of Quirrel are you running on?

Hi @viperfx, thanks for reporting. What version of Quirrel are you running on?

I am running 1.0.1

I am running 1.0.1

Thanks! Can reproduce locally, and will publish a fixed version ASAP.

Thanks! Can reproduce locally, and will publish a fixed version ASAP.

This has been caused by Fastify 3.10.0. I've pinned now it to 3.9.2 and published Quirrel v1.0.2 which contains that. That should fix it. Feel free to re-open if it doesn't :D

This has been caused by Fastify 3.10.0. I've pinned now it to 3.9.2 and published Quirrel v1.0.2 which contains that. That should fix it. Feel free to re-open if it doesn't :D

@Skn0tt I've just installed Quirrel latest version and I have the same problem. However, I have a 500 on the WS handshake.

@Skn0tt I've just installed Quirrel latest version and I have the same problem. However, I have a 500 on the WS handshake.

I think that's a different issue, created one here: https://github.com/quirrel-dev/quirrel/issues/65

I think that's a different issue, created one here: https://github.com/quirrel-dev/quirrel/issues/65


Fixes #1573 - Report number of apps/groups in metrics

Added the number of add/groups to the metrics exposed by Marathon.
Note: With this change, Marathon will load all the groups from ZK each
time the /metrics endpoint is hit. If this becomes a performance
issue, we can cache the metrics and move the refreshing logic to an
actor. I decided to try to avoid premature optimizations.

LGTM


(Nova-v3): Allow custom keyName

Allow custom keyName on Nova v3.0

Thanks for the PR! :) Released in version 2.4.3.


Contact sidebar too small

When clicking on "New contact", the sidebar coming from the left is too small.

This is also present in 1.5.

can't confirm this ... also after the today whatsapp update!
just checked ... what osx / safari version you are using?

This has been fixed. We just need a new release.

ok ... great ! :-)


en: fix wrong section number (#147)

What is changed, added or deleted? (Required)
manually cherry-pick #147

Which DM version(s) do your changes apply to? (Required)

[x] master (the latest development version, including v2.0 changes for now)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

/merge

lgtm

/merge

unlabel translation/doing

/unlabel translation/doing

/label translation/no-need


loading pane

Loading needed to screen to switch between pages. how can I do that? Thank you.

Nprogress.js does not work

I ran your friends :)

This pr #30 also fix this bug


[Feature Request] Create a reset method for Gdx.input.getX and Y

this is the despription of the method Gdx.input.getX()
/** @return The x coordinate of the last touch on touch screen devices and the current mouse position on desktop for the first 	 *         pointer in screen coordinates. The screen origin is the top left corner. */
we should place a method for reset all the pointers to (0,0)

What would be the benefit of resetting these to 0?

Best thing I can think of is if you move your mouse outside of the window on desktop you might want the mouse to return to origin, and same with touch if you're not touching the phone you might want it to be at origin.  I can't think of any personal use cases for such a feature, but someone else probably can.

Yeah, my guess is that providing incorrect coordinates (0,0 is valid but incorrect) will cause more issues than there are valid use-cases.
Closing this, @LogicWrite  please read this again: https://github.com/libgdx/libgdx/blob/master/.github/CONTRIBUTING.md#feature-requests.
Will reopen if the required information is provided.


sublime Stylus semicolon problem

who i can fix this?

before

//SECTION
section {
overflow hidden
position relative
}

after

//SECTION
section {
overflow hidden position relative
}

its old themes: https://github.com/victorporof/Sublime-HTMLPrettify/issues/373
I do not understand why he sent me here.
my code -is stylus  example and at the output it is css

@mrG0bliN
What is stylus?

http://stylus-lang.com/

like a SASS preprocessor

Ah, okay, so it is not CSS but another templating/variant.  That would explain when it doesn't work as you would like.

dead issues
close

Twenty twenty years in the yard, leave the dead man ⚰


Cannot link to GitHub repos owned by an organization of which I am a member

If I try to link to a GH repo that is owned by an organization of which I am a member (admin, but not the owner/creator), the linking fails. This seems to happen whether the organization-owned target repository is private or public.

Link works for me but I can't manage to publish anything. It may be a limitation in the GitHub API.

Fair enough, thanks for checking.
Are you sure it's not a dupe of #60?

It's not, I'm afraid. I've tried with the fix and it still doesn't work.

Ah well. Thanks for looking anyway!


Central Switch cannot be activated

I enabled the Central Switch with the goal to periodically force all thermostats back to Auto mode. Tis as worked for a period of time, but now the button acts as if it is stateless (i.e. I can activate the button but it is directly turned off again). It also doesn't reset te thermostats to auto mode.
Related question: My central config setting for Tado is to revert to auto when te next scheduled event happens. However is seems that a manual change in Homekit sets it to Active until cancelled by user, this should not happen.

Im currently working on v5. Should be fixed now

Hey, i opened a new issue with instructions to test the beta version!
https://github.com/SeydX/homebridge-tado-platform/issues/16

should be fixed in v5


Native Modules don't work with 0.18 (and maybe 0.17 too)

My feeling is that way to build native modules as described in the wiki don't work with elm 0.17+? Is that true?

Yes, that's true.

So what's the new way? I've been reverse engineering generated Elm for now lol


Extremely log hashtag repeatedly failing to insert

The stator is trying to insert a hashtag that is over 100 characters long, and I'm seeing postgres repeatedly fail to insert it.
This is happening in 7d1558a. I resolved it by deleting the post which was in a new state.
Attempting transition on activities.postattachment#10004 from state new
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 929, in get_or_create
    return self.get(**kwargs), False
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 650, in get
    raise self.model.DoesNotExist(
activities.models.hashtag.Hashtag.DoesNotExist: Hashtag matching query does not exist.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
psycopg2.errors.StringDataRightTruncation: value too long for type character varying(100)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/asgiref/sync.py", line 486, in thread_handler
    raise exc_info[1]
  File "/takahe/stator/models.py", line 234, in atransition_attempt
    next_state = await current_state.handler(self)  # type: ignore
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/takahe/activities/models/post.py", line 84, in handle_new
    await post.ensure_hashtags()
  File "/takahe/activities/models/post.py", line 563, in ensure_hashtags
    tag, _ = await Hashtag.objects.aget_or_create(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 945, in aget_or_create
    return await sync_to_async(self.get_or_create)(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/asgiref/sync.py", line 448, in __call__
    ret = await asyncio.wait_for(future, timeout=None)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/tasks.py", line 442, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/asgiref/current_thread_executor.py", line 22, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/asgiref/sync.py", line 490, in thread_handler
    return func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 936, in get_or_create
    return self.create(**params), True
           ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 671, in create
    obj.save(force_insert=True, using=self.db)
  File "/takahe/activities/models/hashtag.py", line 129, in save
    return super().save(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 812, in save
    self.save_base(
  File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 863, in save_base
    updated = self._save_table(
              ^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 1006, in _save_table
    results = self._do_insert(
              ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/base.py", line 1047, in _do_insert
    return manager._insert(
           ^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/manager.py", line 85, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/query.py", line 1791, in _insert
    return query.get_compiler(using=using).execute_sql(returning_fields)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/models/sql/compiler.py", line 1660, in execute_sql
    cursor.execute(sql, params)
  File "/usr/local/lib/python3.11/site-packages/sentry_sdk/integrations/django/__init__.py", line 563, in execute
    return real_execute(self, sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 67, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 80, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 84, in _execute
    with self.db.wrap_database_errors:
  File "/usr/local/lib/python3.11/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/usr/local/lib/python3.11/site-packages/django/db/backends/utils.py", line 89, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
django.db.utils.DataError: value too long for type character varying(100)

2023-04-21 06:24:14.367 UTC [26098] ERROR:  value too long for type character varying(100)
2023-04-21 06:24:14.367 UTC [26098] STATEMENT:  INSERT INTO "activities_hashtag" ("state_ready", "state_changed", "state_attempted", "state_locked_until", "hashtag", "name_override", "public", "state", "stats", "stats_updated", "aliases", "created", "updated") VALUES (true, '2023-04-21T06:24:14.366553+00:00'::timestamptz, NULL, NULL, '<very long hashtag>', NULL, NULL, 'outdated', NULL, NULL, NULL, '2023-04-21T06:24:14.366632+00:00'::timestamptz, '2023-04-21T06:24:14.366647+00:00'::timestamptz)

Ah yes, that's going to fail every few minutes because it's too big for the column. We need to just chop the length down if it gets to 100 I think, that's one long hashtag.

This issue is spamming my 0.8.0 install and I'm wondering, will a 0.9.0 or even a 0.8.1 release be forthcoming to fix this and similar operational bugs? I was expecting one in May based on the blog posts etc in April..

A 0.9 release should come soon once I stop being rather unwell. Apologies for how long it's taken.

sorry to hear you're unwell! In the meantime, I upgraded my server to git main, and got rid of that error (but acquired new ones I'm now trying to understand).


Summer cleaning

Now that this dependency is gone, CI should be easier to get going. Also upgrades to .net 6.


az interactive mode - deploy application: Unable to parse parameter: {

using 'Administrator: Command Prompt -az interactive' Azure CLI 2.0 installed: the "Deploy the application" steps fails with "Unable to parse parameter: {"

Command works fine when not in interactive mode.  You can exit interactive mode with [Ctrl + D]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e026dd3b-caa2-73bd-ce82-65660d5e2128
Version Independent ID: a925fed6-52b4-c67d-2088-306a128984cb
Content: Quickstart - Deploy Hello World to Azure Service Fabric Mesh
Content Source: articles/service-fabric-mesh/service-fabric-mesh-quickstart-deploy-container.md
Service: service-fabric-mesh
GitHub Login: @rwike77
Microsoft Alias: ryanwi

honestly.. would be easier to diagnose the issue if you weren't seemingly suppressing stack trace with the mesh extension.

in the screenshot above... the appearance of the stack trace was from an attempt to not define parameters

@brcaswell Thanks for the feedback! We are currently investigating and will update you shortly.

@brcaswell thanks for the feedback on this. As you mentioned the commands do not work when in interactive mode. In most cases this is not a mode enabled by default in CMD so I am not sure it would be worth mentioning.
I will close this but if we see more feedback on this we can always consider adding a note to the docs.
CC @rwike77 for awareness.


Add certificate chain flag for signing

This allows users to pass their own certificate chain to include in the
OCI signature. The chain is checked for validity using the provided
certificate.
Also refactored the check for matching public keys using a method from
sigstore/sigstore, comparing the certificate's key with the provided
key. Also added this check when extracting the PKCS11 certificate.
Certificate chains must be PEM-encoded. I changed the text of the
certificate flag to also specify a preference for PEM encoding, but
didn't remove the code that handles DER encoding for backwards
compatibility.
Signed-off-by: Hayden Blauzvern<EMAIL_ADDRESS>
Summary

Ticket Link

Ref #1554
Release Note

Added cert-chain flag for including certificate chain in OCI signature on signing

cc @bburky @dlorenc

Codecov Report

Merging #1656 (c86b2c6) into main (bdef009) will increase coverage by 0.23%.
The diff coverage is 25.67%.

@@            Coverage Diff             @@
##             main    #1656      +/-   ##
==========================================
+ Coverage   28.08%   28.32%   +0.23%
==========================================
  Files         139      139
  Lines        8025     8072      +47
==========================================
+ Hits         2254     2286      +32
- Misses       5523     5527       +4
- Partials      248      259      +11

Impacted Files
Coverage Δ

cmd/cosign/cli/attest.go
0.00% <0.00%> (ø)

cmd/cosign/cli/options/attest.go
0.00% <0.00%> (ø)

cmd/cosign/cli/options/sign.go
0.00% <0.00%> (ø)

cmd/cosign/cli/policy_init.go
1.43% <0.00%> (ø)

cmd/cosign/cli/sign.go
0.00% <0.00%> (ø)

cmd/cosign/cli/sign/sign_blob.go
0.00% <0.00%> (ø)

cmd/cosign/cli/sign/sign.go
11.04% <38.77%> (+9.41%)
:arrow_up:

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 bdef009...c86b2c6. Read the comment docs.

@dlorenc Are you familiar with ./hack/update-codegen.sh? I ran it, but it had a few errors, and ended up generating a bunch of code files in vendors/ rather than updating the licenses.

Figured out the issue, looks like some part of the script needs a license binary to be installed via go install instead of go get.

I tested with a couple configurations:
# The following works great and adds the chain annotation:
cosign sign --key "awskms:///..." --cert cert.pem  --cert-chain chain.pem "localhost:5000/$image"
# The following does _not_ work. The certificate is automatically extracted from the smartcard, but the provided chain is not added as an annotation:
cosign sign --key "pkcs11:..."  --cert-chain chain.pem "localhost:5000/$image"

In general, I've noticed the (optional) --cert flag doesn't seem to work for --key "pkcs11:..." and I think this is the same issue. The cert provided from the token is used unconditionally, the cert on the command line is not used. It should probably be an error to pass --cert, or it should be used instead of the one on the token.
Perhaps the cosign sign --key "pkcs11:..."  --cert-chain chain.pem behavior is related? It seems that the provided cert chain is ignored.

Thanks for testing this out. Currently, with a pkcs11 key, it attempts to fetch a certificate from the token and then returns early. You're correct, it's currently ignoring the cert and cert chain flags. I just need to change it to not exit early.


Encode partial URL. Fixes #1536

url.toString is not encoded properly, so to not lose the "+" in the url one has to properly encode it before decoding other chars like " " are correctly encoded
According to https://docs.oracle.com/javase/7/docs/api/java/net/URLDecoder.html this behaviour is correct "+" is Encoded as " " which is not the file someone whants
This Fixes #1536

We'll put this one on the 'boy, who finds this stuff?' list. 👏 colour me impressed!


¡hi!

This pages doesn't works at all.
I would like to download react.js to handle better my webs.
Thankyou!!
https://es.react.dev/learn/add-react-to-a-website

This is the original page
It isn't translated.
https://react.dev/learn/start-a-new-react-project
Have a nice day-night, LRC


Added my name

Please check it out and merge it.

Please make a separate branch for this change 🙏
Check the readme for instructions

okay. I will


default lp_suffix value revert

rebased to master (ci fails because of no package.json
Strategy.getHarvestable only executes when the Strategy contract has it


Website crash when Bulk delete records from Content Manager in Strapi Admin

Bug report
Required System information

Node.js version: 20.11.1
NPM version: 10.2.4
Strapi version: 4.20.1
Database: MySql
Operating system: Windows
Is your project Javascript or Typescript: Javascript

Describe the bug
When i select any item from listing, and click on delete button. the Strapi Admin site is crash with below error.

if remove this plugin from Strapi, the bulk delete is working without any error.
Steps to reproduce the behavior

Go to Content Manager
Click on check box for Select item
Click on Delete button which is display after filter button
Strapi admin crash after that action with above error.

Expected behavior
Delete the item without error.

@ChristopheCVB  I am getting same error while bulk deleting any items


Emit error event.

Summary
In case of error in asynchronous operation it can't emitted, but in docs there is "Mojo::Pg inherits all events from Mojo::EventEmitter".
Sample use case of error emitting is global logging of all errors in one place, we not need to do this in every callback.
References
No.

Since there is no use case and tests, i'm afraid this pull request has to be rejected.


Use multiple outputs to make package name with underscore

~To align with the name on pypi.org~

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[n/a] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[n/a] Ensured the license file is being packaged.

I confused myself between the package name and library names... 🤦♂


Question

Hi,
Will you be updating to 0.8.1?
Thanks

You can choose any OC version, including the latest version, in the following way, which is very simple
https://github.com/ic005k/OCAuxiliaryTools/issues/223

To make it simple, it means that OCAT is not tied to any OC version, and you can simply select your preferred OC version through OCAT.

Thanks for your reply.
I can only see 0.7.8 in the dropdown menu.

https://github.com/ic005k/OCAuxiliaryTools/issues/223#issuecomment-1099234975

Latest Version = 0.8.1 ... 0.8.2 ... 0.8.3 ... 0.9.0 or 2.0.0 ......

I used the latest version option, it still only updates to 0.7.8, not 0.8.1. Not sure what I'm doing wrong.