CVE USN-4309-1: Vim vulnerabilities - bump cflinuxfs3 to 0.172.0

Describe the bug
https://www.cloudfoundry.org/blog/usn-4309-1/ details a vulnerability in VIM. We already appear to have the CF bump to 12.39 but we need to get cflinuxfs3 to 0.172.0 to clear the Ubuntu vulnerabilities.
I can't tell if the SLE stack we use has the same VIM version since Ubuntu listed these versions as the upgraded platform:

Ubuntu 19.10: vim 2:8.1.0875-5ubuntu2.1
Ubuntu 18.04 LTS: vim 2:8.0.1453-1ubuntu1.3
Ubuntu 16.04 LTS: vim 2:7.4.1689-3ubuntu1.4
Ubuntu 14.04 ESM: vim 2:7.4.052-1ubuntu3.1+esm1
Ubuntu 12.04 ESM: vim 2:7.3.429-2ubuntu2.3

We need to check the vim version in our sle15 filesystem to see if it has a similar vulnerability.

Handled by #949


Support Objective-C (.objcproj) and Objective-C++ (.objcxxproj)

This is contingent on Objective-C(++) cross-compilation actually working.


Issues found

[ ] WGHO is missing a license specifier
[ ] there's unused imports like import {AaveGovernanceV2} from '@aave/AaveGovernanceV2.sol';, which don't change the code but will make verificated code on etherscan messy.
[ ] the remappings are quite weird, aave-address-book & solidity-utils are bgd, why remapping one to @aave one to @bgd. It's minor, but as this is non upgradable and the metadata will be on etherscan i think better to do:

aave-address-book/=lib/aave-address-book/src/
solidity-utils/=lib/solidity-utils/src/

[ ] better to consistently use named imports (so no import './interfaces/IGHO.sol'; etc)
[ ] not sure but you might want to add aci as author
[ ] https://github.com/AaveChan/WGHO/blob/master/src/WGHO.sol#L59 would put a check for address(0)
[ ] might make sense to consistently use ECDSA from oz

Tests

https://github.com/AaveChan/WGHO/blob/master/test/WGHO.t.sol#L21 would get this from gho contract
https://github.com/AaveChan/WGHO/blob/master/test/WGHO.t.sol#L30 would take this from address book
example on test for signature using ERC712 https://github.com/bgd-labs/aave-governance-v3/blob/7afbf3134ba778da0418b3ce2e80668e17dd5a75/tests/voting/votingMachineWithProofs.t.sol#L1216

On it!

ERC20 getting imported twise here and here
errors should be moved to the interface
PermitParams should not be a part of METADEPOSIT_TYPEHASH and METAWITHDRAWAL_TYPEHASH
If Permit will be overtaken by malicious actor and executed in advance tx will fail. This issue was known time ago, use try -> catch around instead
does not look reasonable to do checks of allowance and balance here, because it will fail anyway on safeTransfer
should be used _hashTypedDataV4 here instead
example is here
here should be amount > balanceOf - totalSupply
on deadline and owner check use the same errors as here OZ uses
here and here use internal _useNonce function same as OZ doing it here
nonces should not be overloaded, because of the previous point


Hide hidden files by default

I shouldn't have to install a package to hide hidden files...
I had to look this up to disable such a basic setting.
http://blog.lukebennett.com/2015/09/21/show-hidden-files-in-atom-sidebar/

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:


Remove LastPass from the "Password Vaults" section

They can't seem to avoid massive security vulnerabilities being discovered far later than they should, and part of that problem is because they're not open-source.
To be honest, BitWarden and KeePass probably cover every user need, but at the very least LastPass is too shoddy to be on the list.

Do you recommend migrating from lastpass to bitwarden? I love lastpass because of its multi platform functionality

@jmada bitwarden is olso cross platform and supports synchronisation between multiple devices. But I prefer using the Google's own password manager because I don't store anything else other than website passwords.

@jmada I used a LastPass user for 3 years and almost 2 years ago I switched to BitWarden because of its nature (open source & free). I've got many mac, ios, android devices and I can tell you that I've never got a problems.
99% stressfree move (the 1% is for the day you have to move your pwd).

Thanks! I'm using Bitwarden know and I deleted my lastpass account xD

I can agree with using Bitwarden, it's beenn my go-to password manager for 2 years.


remove the primary and secondary keystore for jwt

as they only used by the light-oauth2 and oauth-kafka

 remove the primary and secondary keystore for jwt light-rest-4j master

 remove the primary and secondary keystore for jwt light-rest-4j master


Cherry-pick documentation from 2.x to master

Cherry pick documentation changes from https://github.com/elastic/elasticsearch-net/commit/6fe620546b1386409e396d4cc931ec1996e9eeae to go into master

This has been done as part of https://github.com/elastic/elasticsearch-net/pull/1992


Spike: deploy and test Franklin

So that we can confidently productionise a STAC API and indexing tool we want to install and import LINZ data to Franklin.
Tasks

[ ] Deploy and configure the tool in a LINZ AWS account (devs nonprod Geostore account (1,2 or 3))
[ ] Import LINZ's current production metadata (excepting the root catalog) in the Geostore production bucket.
[ ] Brief results against the assesment criteria below should be captured in confluence.

See confluence page for research done so far.
Assessment criteria:

cost is acceptable (storage, compute, requests)
can ingest our data automatically from an S3 bucket with accptable operational or development overhead
the API functionality works well and does what we expect
can index LINZ STAC metadata extensions and make available for search
easily deployed, maintained and configured
performs well with LINZ's full dataset (search speed etc)
list any missing functionality or components

Franklin isn't a good fit for Geostore. The documentation is very light (almost non-existence). The instructions are outdated (they don't work). It also looks like the project has been abandoned??? Last human commit was a while back...

Closing this as done. Thanks @Jimlinz


fix(sequence): broken in 2.5. Fixes #2248

Checklist:

[ ] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[X] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[X] I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
[X] Optional. I've added My organization is added to the README.
[X] I've signed the CLA and required builds are green.

Fixes #2248

This is currently targeted for v2.7 (end of March) do you NEED it sooner?

Thank you for this fix and adding the test. From my end (the reporter) waiting until 2.6 is no problem.


The file in the staging area is lost due to an error

NodeJS: v16.14.2
package.json
{
  "name": "uni-preset-vue",
  "version": "0.0.0",
  "scripts": {
    "dev": "uni --open",
    "dev:app": "uni -p app",
    "dev:custom": "uni -p",
    "dev:h5": "uni",
    "dev:h5:ssr": "uni --ssr",
    "dev:mp-alipay": "uni -p mp-alipay",
    "dev:mp-baidu": "uni -p mp-baidu",
    "dev:mp-kuaishou": "uni -p mp-kuaishou",
    "dev:mp-lark": "uni -p mp-lark",
    "dev:mp-qq": "uni -p mp-qq",
    "dev:mp-toutiao": "uni -p mp-toutiao",
    "dev:mp-weixin": "uni -p mp-weixin",
    "dev:quickapp-webview": "uni -p quickapp-webview",
    "dev:quickapp-webview-huawei": "uni -p quickapp-webview-huawei",
    "dev:quickapp-webview-union": "uni -p quickapp-webview-union",
    "build:app": "uni build -p app",
    "build:custom": "uni build -p",
    "build:h5": "uni build",
    "build:h5:ssr": "uni build --ssr",
    "build:mp-alipay": "uni build -p mp-alipay",
    "build:mp-baidu": "uni build -p mp-baidu",
    "build:mp-kuaishou": "uni build -p mp-kuaishou",
    "build:mp-lark": "uni build -p mp-lark",
    "build:mp-qq": "uni build -p mp-qq",
    "build:mp-toutiao": "uni build -p mp-toutiao",
    "build:mp-weixin": "uni build -p mp-weixin",
    "build:quickapp-webview": "uni build -p quickapp-webview",
    "build:quickapp-webview-huawei": "uni build -p quickapp-webview-huawei",
    "build:quickapp-webview-union": "uni build -p quickapp-webview-union",
    "prepare": "husky install"
  },
  "dependencies": {
    "@dcloudio/uni-app": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-app-plus": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-components": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-h5": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-alipay": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-baidu": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-kuaishou": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-lark": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-qq": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-toutiao": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-mp-weixin": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-quickapp-webview": "^3.0.0-alpha-3040320220325006",
    "luch-request": "^3.0.7",
    "pinia": "^2.0.13",
    "vue": "^3.2.31",
    "vue-request": "^1.2.4"
  },
  "devDependencies": {
    "@dcloudio/types": "^2.5.19",
    "@dcloudio/uni-automator": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/uni-cli-shared": "^3.0.0-alpha-3040320220325006",
    "@dcloudio/vite-plugin-uni": "^3.0.0-alpha-3040320220325006",
    "@typescript-eslint/eslint-plugin": "^5.17.0",
    "@typescript-eslint/parser": "^5.17.0",
    "eslint": "^7.32.0",
    "eslint-config-prettier": "^8.5.0",
    "eslint-config-standard": "^16.0.3",
    "eslint-plugin-import": "^2.25.4",
    "eslint-plugin-node": "^11.1.0",
    "eslint-plugin-promise": "^5.2.0",
    "eslint-plugin-vue": "^8.5.0",
    "husky": "^7.0.4",
    "postcss": "^8.4.12",
    "postcss-html": "^1.3.0",
    "postcss-scss": "^4.0.3",
    "prettier": "^2.6.1",
    "sass": "^1.49.10",
    "stylelint": "^14.6.1",
    "stylelint-config-prettier-scss": "^0.0.1",
    "stylelint-config-recess-order": "^3.0.0",
    "stylelint-config-recommended-vue": "^1.4.0",
    "stylelint-config-standard-scss": "^3.0.0",
    "stylelint-csstree-validator": "^2.0.0",
    "stylelint-declaration-block-no-ignored-properties": "^2.5.0",
    "stylelint-group-selectors": "^1.0.8",
    "typescript": "^4.6.3",
    "unplugin-auto-import": "^0.6.9",
    "unplugin-vue-components": "^0.18.5",
    "vite": "^2.9.1",
    "vue-demi": "^0.12.5"
  },
  "lint-staged": {
    "*.{js,ts,vue}": "eslint --fix",
    "*.{css,scss,sass,vue}": "stylelint --fix",
    "*.{js,ts,md,vue}": "prettier --write"
  }
}

ERROR:
node:internal/errors:464 ErrorCaptureStackTrace(err); ^
Error: kill ENOSYS at kill (node:internal/process/per_thread:220:13) at Arra
I'm sorry I can't provide a complete log for the time being
I can only provide some information based on the search records
Because it doesn't happen 100%
When I tried the second time, I succeeded
I only remember that I restored sass version 1.49.11 - > 1.49.10
I used pnpm and I'm not sure if it's relevant
Because the error message contains node_ modules
If I find it next time, I will provide a complete log

I have the same exact issue.
[2022-04-06T20:48:11.949Z] [STARTED] Preparing lint-staged...
[SUCCESS] Preparing lint-staged...
[STARTED] Running tasks for staged files...
[STARTED] .lintstagedrc.json — 1 file
[STARTED] .{js,jsx} — 0 file
[STARTED] src/**/.{ts,tsx} — 1 file
[STARTED] stories//*.{ts,tsx} — 0 file
[STARTED] * — 1 file
[SKIPPED] *.{js,jsx} — no files
[SKIPPED] stories//*.{ts,tsx} — no files
[STARTED] tsc-files
[STARTED] npm run-script prettier:format
[FAILED] tsc-files [FAILED]
[FAILED] tsc-files [FAILED]
[SUCCESS] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[SKIPPED] Skipped because of errors from tasks.
[STARTED] Reverting to original state because of errors...
node:internal/errors:464
ErrorCaptureStackTrace(err);
^
Error: kill ENOSYS
at kill (node:internal/process/per_thread:220:13)
at Array.forEach ()
at Timeout.loop [as _onTimeout] (file:///C:/vs/GIT/PowerFramework360/node_modules/lint-staged/lib/resolveTaskFn.js:62:11) {
errno: -4054,
code: 'ENOSYS',
syscall: 'kill'
}
husky - pre-commit hook exited with code 1 (error)

I almost lost a couple of hours work because of a similar error.
Upgraded to version 12.3.7 this morning and when I was going to commit changes it errored and my changes were gone.
The first time I was able to use the stash backup to restore my changes but the second time the git process crashed and i was unable to pop the stash.
Luckily I had made a copy of my changes outside the repository.
node 16.14.0
lint-staged 12.3.7
[STARTED] Preparing lint-staged...
[SUCCESS] Preparing lint-staged...
[STARTED] Running tasks for staged files...
[STARTED] package.json — 20 files
[STARTED] *.(js|svelte) — 17 files
[STARTED] *.(scss|css|svelte) — 9 files
[STARTED] *.(svelte) — 9 files
[STARTED] eslint
[STARTED] stylelint
[STARTED] prettier --check
[FAILED] prettier --check [FAILED]
[FAILED] prettier --check [FAILED]
[SUCCESS] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[SKIPPED] Skipped because of errors from tasks.
[STARTED] Reverting to original state because of errors...
[FAILED] eslint [FAILED]
[FAILED] eslint [FAILED]
node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error: kill ESRCH
    at kill (node:internal/process/per_thread:220:13)
    at Array.forEach (<anonymous>)
    at Timeout.loop (file:///C:/dev/skalbar-2/node_modules/lint-staged/lib/resolveTaskFn.js:62:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  errno: -4040,
  code: 'ESRCH',
  syscall: 'kill'
}
husky - pre-commit hook exited with code 1 (error)

I reverted back to 12.3.4 as @rexkenley suggested and now it works as expected.

This PR that was introduced in 12.3.6 seems a likely cause: #1117.
I think it may kill the revert process losing the files.
As stated above, try git stash list and git stash pop for backed up files.

Chiming in to say that we've run into this issue and it seems specific to Windows. 12.3.7 works fine on my setup (OSX), but our other dev experienced errors when trying to restore the stash on Windows. Reverting to 12.3.4 worked.
Relevant logs with --debug
[STARTED] prettier --check
[FAILED] prettier --check [FAILED]
[FAILED] prettier --check [FAILED]
[SUCCESS] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[SKIPPED] Skipped because of errors from tasks.
[STARTED] Reverting to original state because of errors...
  lint-staged:GitWorkflow Restoring original state... +381ms
  lint-staged:execGit Running git command [ 'reset', '--hard', 'HEAD' ] +452ms
  lint-staged:execGit Running git command [ 'stash', 'list' ] +102ms
  lint-staged:execGit Running git command [ 'stash', 'apply', '--quiet', '--index', 'refs/stash@{0}' ] +105ms
node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^
Error: kill ENOSYS
    at kill (node:internal/process/per_thread:215:13)
    at Array.forEach (<anonymous>)
    at Timeout.loop [as _onTimeout] (file:///C:/XXXXXXXX/AppData/Local/npm-cache/_npx/8facc973fbdb1091/node_modules/lint-staged/lib/resolveTaskFn.js:62:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  errno: -4054,
  code: 'ENOSYS',
  syscall: 'kill'
}

Can confirm this is happening on Windows...
[STARTED] Preparing lint-staged...
[SUCCESS] Preparing lint-staged...
[STARTED] Running tasks for staged files...
[STARTED] packages/components/package.json — 1 file
[STARTED] **/*.{js,ts,tsx} — 1 file
[STARTED] **/*.{ts,tsx} — 1 file
[STARTED] eslint --fix
[STARTED] tsc-files
[FAILED] tsc-files [FAILED]
[FAILED] tsc-files [FAILED]
[SUCCESS] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[SKIPPED] Skipped because of errors from tasks.
[STARTED] Reverting to original state because of errors...
node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error: kill ENOSYS
    at kill (node:internal/process/per_thread:220:13)
    at Array.forEach (<anonymous>)
    at Timeout.loop [as _onTimeout] (file:///C:/work/[...]/node_modules/lint-staged/lib/resolveTaskFn.js:62:11)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  errno: -4054,
  code: 'ENOSYS',
  syscall: 'kill'
}
husky - pre-commit hook exited with code 1 (error)

update version to 12.4.0

Had this happen to me on 12.4.1

i get 465
`node:internal/errors:465
ErrorCaptureStackTrace(err);
^
Error: kill ESRCH
at process.kill (node:internal/process/per_thread:220:13)
at Timeout.loop (file:///D:/workspace_cli/vite-vue3-admin/node_modules/.pnpm/lint-staged@12.5.0/node_modules/lint-staged/lib/resolveTaskFn.js:67:17)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
errno: -4040,
code: 'ESRCH',
syscall: 'kill'
}
husky - pre-commit hook exited with code 1 (error)
`

Have you updated to v13.0.1?

prevent possible race condition when killing tasks on failure (bc92aff)

$ lint-staged
node:internal/process/esm_loader:94
internalBinding('errors').triggerUncaughtException(
^
Error [ERR_MODULE_NOT_FOUND]: Cannot find package<EMAIL_ADDRESS>imported from<EMAIL_ADDRESS>Did you mean to import<EMAIL_ADDRESS>at new NodeError (node:internal/errors:371:5)
at legacyMainResolve (node:internal/modules/esm/resolve:336:9)
at packageResolve (node:internal/modules/esm/resolve:917:14)
at moduleResolve (node:internal/modules/esm/resolve:976:18)
at defaultResolve (node:internal/modules/esm/resolve:1078:11)
at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
at ModuleWrap. (node:internal/modules/esm/module_job:79:40)
at link (node:internal/modules/esm/module_job:78:36) {
code: 'ERR_MODULE_NOT_FOUND'
}
error Command failed with exit code 1.

is it resolved ?

I believe the original issue is resolved, yet. I'll close this ticket for now.


Typos in commands

You have typos in commands. Whereas, it won't work if you have whitespace between - and EwsAllowList. This whitespace has to be removed.
Wrong Command Example:
Set-OrganizationConfig - EwsAllowList @{Add="MicrosoftOWSPersonalBookings"}
Correct Command Example:
Set-OrganizationConfig -EwsAllowList @{Add="MicrosoftOWSPersonalBookings"}

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

ID: 7bad8864-5f08-90ae-a6d1-a23e58fc1843
Version Independent ID: 7bad8864-5f08-90ae-a6d1-a23e58fc1843
Content: Bookings in Outlook
Content Source: microsoft-365/bookings/bookings-in-outlook.md
Service: bookings
GitHub Login: @kwekuako
Microsoft Alias: kwekua

@RAJU2529 Thank you very much for the contribution and updating the documentation with PR. @ahamin01 Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


[ENH] Pulse schedules should be easier to work with

What is the expected enhancement?
It should be possible to create a pulse schedule by passing only the number of qubits in the schedule and possibly other memory and register information, e.g.

schedule = Schedule(n_qubits=5, memory_slots=5, n_registers=5)

Then it should be possible to append pulses to this object using, for example:

schedule.qubit[0].drive.append(gaussian, shift=150)

This is also closer in spirit to the QuantumCircuit class.  This removes the need for getting a device specification before constructing the schedule; A step that is required for the pulse simulator.

I agree that helper methods/interface should be added for schedule construction. I should point out that we initially started very close to the builder interface that you describe, but as we concerned the problem at hand that we had to solve, we evolved to the current data structure.
I would not hold the QuantumCircuit to be the reference implementation as this is changing in v0.9, likely to have many of the attributes of the pulse Schedule implementation. They should meet somewhere in the middle. The key component of Schedules that I wish to keep intact is their immutability, this allows rapid reuse and construction of composite schedules.
The crux of your suggestion essentially involves merging the DeviceSpecification and Schedule classes. I think what you are describing is effectively a builder interface on top of the pulse schedules data structure. This is something I could support if it could be done while maintaining the desired existing features.
schedule = Schedule(n_qubits=5, memory_slots=5, n_registers=5)

This could be done by renaming the current schedule to Schedule -> CompositeSchedule, and then have Schedule have both a DeviceSpecification and a Schedule. I do worry that at this stage it becomes hard to maintain immutability
schedule.qubit[0].drive.append(gaussian, shift=150)

This issue I see (and we ran into this when we tried this approach)

Now every channel needs to know which schedule it is owned by, Channels are not reusable and each Channel has a Schedule and each Schedule has the Channel which introduces a circular dependency between the two.
The other issue is that some commands take multiple channels such as the acquire command

for proper comparison how this should be done with the current API.
spec = DeviceSpecification((n_qubits=5, memory_slots=5, n_registers=5) # should be allowed to do this but currently not
schedule = Schedule()
schedule = schedule.append(gaussian(spec.q[0].drive).shift(150))

Note that at each step it is clear that a function is being called and a result returned.
This could be easily modified to also be like
spec = DeviceSpecification((n_qubits=5, memory_slots=5, n_registers=5) # should be allowed to do this but currently not
schedule = Schedule()
schedule = schedule.append(gaussian, spec.q[0].drive, shift=150)

which would do the same as the former behind the scenes (and which most closely aligns with the QuantumCircuit).

I am fine with this:

spec = DeviceSpecification((n_qubits=5, memory_slots=5, n_registers=5)
schedule = Schedule()
schedule = schedule.append(gaussian(spec.q[0].drive).shift(150))

Tracking the device specification enhancement in #2479.

Closed by #2621.


Remove need to modify build.gradle in node_modules

Yep, we're working alongside OneSignal team on this, we'll update this issue when it's resolved.
I think we need @jkasten2 in here to take care of this.

+1

@avishayil You might be able to simplify the process by not requiring the modification of node_modules/react-native-onesignal/android/build.gradle. I am guessing you have already tried leaving the file as is without modification however could you try just setting these to a blank string?
manifestPlaceholders = [manifestApplicationId: "",
                        onesignal_app_id: "",
                        onesignal_google_project_number: ""]

I believe this may work as android/app/build.gradle should override this. I don't have a lot of experience with react-native but I do with gradle so let me know if you need me to dig into this more.

Yeah, I'm on a vacation right now so can't take a look, can you try doing this with the sample project?

OK, it seems to solve the issue. Thanks @jkasten2 !


Redesign Bars for Small Width

Problem:

Solution mockup:

text could be for example "Iraq: 580,327"

I'm thinking to use the same technique as here

https://bl.ocks.org/mbostock/8d2112a115ad95f4a6848001389182fb
For highlighting the text (instead of the light shadow we have in the Somalia viz).


[ES DateTimeV2] anoche is resolved incorrectly

Describe the bug
When "anoche" ("last night") is followed by "a las," as in "Llevé a mis niños a dormir anoche a las 8 en punto," the resulting timex is identical to the timex for "esta noche a las 8" ("tonight at 8").
To Reproduce
Steps to reproduce the behavior:

Create an es-es or es-mx app and include datetimeV2
Test "Llevé a mis niños a dormir anoche a las 8 en punto"
The timex will point to the current day instead of the previous day.

Expected behavior
The timex for anoche should have yesterday's date.
Platform (please complete the following information):

Platform:
Environment: in browser
Version of package: ?

We can't replicate this issue.
The repo contains a SimpleConsole project that can be used to test if a specific issue still exists. One just need to change the target language to the desired one and feed it text.
If possible, please run the tool as it speeds up bug triage. Thanks.


Add support for groups.

Adding support for timeline groups was a matter of four simple changes.

Working great. Pull 'er in!

Hey, any update on this?

Thanks for this @alvaroabascar and sorry for the delay. We'll look at getting this merged with #4


Make the variable DynamicCaption protected in page 11310 "General Ledger Entries Apply"

Hello,
We will need to have the variable DynamicCaption protected in page 11310 "General Ledger Entries Apply".
We have a function in the page extension for page 11310 "General Ledger Entries Apply" and there we change the DynamicCaption variable. We would need to have this variable protected, so we could access it through the page extension and then, this value is used when executing the code CurrPage.Caption := DynamicCaption; from OnOpenPage trigger.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Docker-compose-ipfscluster

Hi,
I did a change on docker-compose-ipfscluster, because the elasticsearch it wasn't working for me.
docker-compose-ipfscluster.txt
Basically, I change this:
elasticsearch:
image:  docker.elastic.co/elasticsearch/elasticsearch:6.3.1
container_name: elasticsearch
environment:
- cluster.name=docker-cluster
- bootstrap.memory_lock=true
- "ES_JAVA_OPTS=-Xms512m -Xmx512m"
ulimits:
memlock:
soft: -1
hard: -1
nofile:
soft: 65536
hard: 65536
Could you confirm?
Tks

Hey,
Thanks for you feedback. You are absolutely right !
I haven't noticed this error before because my machine (host) has already a "ulimit -n" pretty high and if not set, the value in the container is inherited from the host.
Could you submit a Pull Request with your change, and i will do some testing then.
Thanks!


Tutorial problem

Inverter() is not able to properly instantiate a pystan model when running in a virtual environment. Setting up C++ compiler, pystan, and bayes-drt in the exact same way but not in a virtual environment results in no errors. This implies the error is based on how the file path is automatically generated for accessing the 'stan_model_files' folder when calling Inverter in a virtual environment.
Error when running in a virtual environment:
"Fit the data"
# by default, the Inverter class is configured for the DRT
inv_hmc = Inverter()
inv_map = Inverter()

# Perform HMC fit
start = time.time()
inv_hmc.bayes_fit(freq,Z)
elapsed = time.time() - start
print('HMC fit time {:.2f}'.format(elapsed))

# Perform MAP fit
start = time.time()
inv_map.map_fit(freq,Z)
elapsed = time.time() - start
print('MAP fit time {:.2f}'.format(elapsed))

WARNING:pystan:No module named 'stanfit4anon_model_5e41d7ccbb68c66e26beba2b6307db0c_8841332859592360126'
WARNING:pystan:Something went wrong while unpickling the StanModel. Consider recompiling.

AttributeError                            Traceback (most recent call last)
 in
6 # Perform HMC fit
7 start = time.time()
----> 8 inv_hmc.bayes_fit(freq,Z)
9 elapsed = time.time() - start
10 print('HMC fit time {:.2f}'.format(elapsed))
~\AppData\Local\Continuum\anaconda3\envs\impedance-analysis\lib\site-packages\bayes_drt\inversion.py in bayes_fit(self, frequencies, Z, part, scale_Z, init_from_ridge, nonneg_drt, outliers, sigma_min, warmup, sample, chains, random_seed, inductance_scale, fitY, Yscale, SA, SASY)
802
803                 # sample from posterior
--> 804 		self._sample_result = model.sampling(dat,warmup=warmup,iter=warmup+sample,chains=chains,seed=random_seed,init=init,
805 								  control={'adapt_delta':0.9,'adapt_t0':10})
806
~\AppData\Local\Continuum\anaconda3\envs\impedance-analysis\lib\site-packages\pystan\model.py in sampling(self, data, pars, chains, iter, warmup, thin, seed, init, sample_file, diagnostic_file, verbose, algorithm, control, n_jobs, **kwargs)
756                 raise ValueError("Warmup samples must be greater than 0 when adaptation is enabled (adapt_engaged=True)")
757         seed = pystan.misc._check_seed(seed)
--> 758         fit = self.fit_class(data, seed)
759
760         m_pars = fit._get_param_names()
AttributeError: 'StanModel' object has no attribute 'fit_class'

I haven't been able to reproduce this, but it seems like some other packages that use pystan may have similar issues (e.g. https://github.com/facebook/prophet/issues/599). Can you see if you still have this issue with the new installation procedure?
If the issue persists, I can think of two potential workarounds:

Have the user navigate to the stan_model_files directory and delete all the .pkl files (bayes_drt will detect that they're missing and recompile them).
Install bayes_drt with only the model code files and exclude the pre-compiled models. Pro: takes the burden off the user to fix the problem. Con: the first time that bayes_drt is imported, all stan models will have to be compiled, which will take a while (~10-20 minutes).

I think this is probably related to https://github.com/jdhuang-csm/bayes-drt/issues/4. Option 2 from above seems like the best fix (force Stan models to be compiled during first import).

I'm pretty sure that the fix for https://github.com/jdhuang-csm/bayes-drt/issues/4 will also fix this, as the Stan models will now always be compiled after installation, rather than relying on precompiled models being copied into the virtual environment.


Create a tool to reverse engine a template or a scheme

This issue is directly related to base16-builder. I would love to get a tool to create a template from a theme. Basically, it will replace colors with nunjucks string.
A maths metaphor would be: scheme + template = theme thank to base16-builder and with this tool we could do: theme  - scheme = template or theme - template = scheme.

Would this belong in another repository?

Yes I think. What do you think?

Could be use for #60


Attempt at having a parallel tests test project

not yet working, opening an issue at aruba (https://github.com/cucumber/aruba/issues/699) to figure out how to
do this :thinking_face:
The issue being that my thought of having a separate Gemfile doesn't work as it appears that the bundle commands are executed in the scope of the top level simplecov project.
for parallel_tests I might add a development dependency, but in the future I'd also like to test against different Rails versions or something so while feasible that might not be ideal.
#781

It works :tada:
It might fail though... because - surprise! - the merging of parallel tests might fail/is timing dependent. It's hard to reproduce. Sometimes it happens 4 times in a row. Sometimes it doesn't happen at all in 10 runs. Classic flaky (but in this case I blame our implementation so it's a "good" flaky).
Probably should then skip it for the time being and attempt to fix it in another PR... which kinda defeats the purpose but probably better than having to rerun all other PRs n times because of a known flaky.

Collected some failures here for future reference. In all of them it seems that the correct report is generated but is then overridden by a subsequent incorrect one that doesn't take everything into account.
Which I believe is a great find to have semi reproducible in a test :tada:

4 processes for 4 specs, ~ 1 specs per process
..

Finished in 0.00217 seconds (files took 0.09603 seconds to load)
2 examples, 0 failures

.

Finished in 0.00292 seconds (files took 0.09621 seconds to load)
1 example, 0 failures

...

Finished in 0.00245 seconds (files took 0.0952 seconds to load)
2 examples, 0 failures

Finished in 0.00224 seconds (files took 0.09621 seconds to load)
1 example, 0 failures

Coverage report generated for (2/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 23 / 33 LOC (69.7%) covered.
Coverage report generated for (1/8), (2/8), (3/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 37 / 43 LOC (86.05%) covered.
Coverage report generated for (1/8), (2/8), (3/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 42 / 47 LOC (89.36%) covered.
Coverage report generated for (1/8), (2/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 32 / 39 LOC (82.05%) covered.

6 examples, 0 failures

Took 0 seconds

(::) failed steps (::)

expected: 9
     got: 7

(compared using ==)
 (RSpec::Expectations::ExpectationNotMetError)
./features/step_definitions/html_steps.rb:14:in `block (3 levels) in <top (required)>'
./features/step_definitions/web_steps.rb:5:in `block in with_scope'
./features/step_definitions/web_steps.rb:5:in `with_scope'
./features/step_definitions/html_steps.rb:12:in `block (2 levels) in <top (required)>'
./features/step_definitions/html_steps.rb:11:in `each'
./features/step_definitions/html_steps.rb:11:in `/^I should see the groups:$/'
./features/step_definitions/parallel_tests_steps.rb:4:in `"I should see the results for the parallel tests project"'
features/parallel_tests.feature:12:in `Then I should see the results for the parallel tests project'

Failing Scenarios:
cucumber features/parallel_tests.feature:9 # Scenario: Running it through parallel_tests produces the same results as a normal rspec run

4 processes for 4 specs, ~ 1 specs per process
....

Finished in 0.00174 seconds (files took 0.0938 seconds to load)
1 example, 0 failures

.

Finished in 0.00186 seconds (files took 0.09369 seconds to load)
2 examples, 0 failures

Finished in 0.0018 seconds (files took 0.0936 seconds to load)
2 examples, 0 failures

.

Finished in 0.00237 seconds (files took 0.09319 seconds to load)
1 example, 0 failures

Coverage report generated for (1/8), (2/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 37 / 43 LOC (86.05%) covered.
Coverage report generated for (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 19 / 31 LOC (61.29%) covered.
Coverage report generated for (1/8), (2/8), (3/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 42 / 47 LOC (89.36%) covered.
Coverage report generated for (1/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 28 / 37 LOC (75.68%) covered.

6 examples, 0 failures

Took 0 seconds
[DEPRECATED] use `bundle info rspec-core` instead of `bundle show rspec-core`
[DEPRECATED] use `bundle info rspec-core` instead of `bundle show rspec-core`
[DEPRECATED] use `bundle info rspec-core` instead of `bundle show rspec-core`
[DEPRECATED] use `bundle info rspec-core` instead of `bundle show rspec-core`
.F

(::) failed steps (::)

expected: 9
     got: 7

(compared using ==)
 (RSpec::Expectations::ExpectationNotMetError)
./features/step_definitions/html_steps.rb:14:in `block (3 levels) in <top (required)>'
./features/step_definitions/web_steps.rb:5:in `block in with_scope'
./features/step_definitions/web_steps.rb:5:in `with_scope'
./features/step_definitions/html_steps.rb:12:in `block (2 levels) in <top (required)>'
./features/step_definitions/html_steps.rb:11:in `each'
./features/step_definitions/html_steps.rb:11:in `/^I should see the groups:$/'
./features/step_definitions/parallel_tests_steps.rb:4:in `"I should see the results for the parallel tests project"'
features/parallel_tests.feature:19:in `Then I should see the results for the parallel tests project'

Failing Scenarios:
cucumber features/parallel_tests.feature:16 #

4 processes for 4 specs, ~ 1 specs per process
.

Finished in 0.00221 seconds (files took 0.09079 seconds to load)
1 example, 0 failures

..

Finished in 0.00172 seconds (files took 0.09245 seconds to load)
2 examples, 0 failures

..

Finished in 0.00195 seconds (files took 0.09657 seconds to load)
2 examples, 0 failures

.

Finished in 0.00179 seconds (files took 0.0979 seconds to load)
1 example, 0 failures

Coverage report generated for (3/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 19 / 31 LOC (61.29%) covered.
Coverage report generated for (1/8), (3/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 28 / 37 LOC (75.68%) covered.
Coverage report generated for (1/8), (2/8), (3/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 42 / 47 LOC (89.36%) covered.
Coverage report generated for (1/8), (2/8), (3/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 37 / 43 LOC (86.05%) covered.

6 examples, 0 failures

Took 0 seconds

(::) failed steps (::)

expected: 9
     got: 8

(compared using ==)
 (RSpec::Expectations::ExpectationNotMetError)
./features/step_definitions/html_steps.rb:14:in `block (3 levels) in <top (required)>'
./features/step_definitions/web_steps.rb:5:in `block in with_scope'
./features/step_definitions/web_steps.rb:5:in `with_scope'
./features/step_definitions/html_steps.rb:12:in `block (2 levels) in <top (required)>'
./features/step_definitions/html_steps.rb:11:in `each'
./features/step_definitions/html_steps.rb:11:in `/^I should see the groups:$/'
features/parallel_tests.feature:12:in `Then I should see the groups:'

Failing Scenarios:
cucumber features/parallel_tests.feature:9 # Scenario:

4 processes for 4 specs, ~ 1 specs per process
..

Finished in 0.00186 seconds (files took 0.09117 seconds to load)
2 examples, 0 failures

..

Finished in 0.00198 seconds (files took 0.09406 seconds to load)
2 examples, 0 failures

.

Finished in 0.00271 seconds (files took 0.09533 seconds to load)
1 example, 0 failures

.

Finished in 0.00258 seconds (files took 0.09796 seconds to load)
1 example, 0 failures

Coverage report generated for (2/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 23 / 33 LOC (69.7%) covered.
Coverage report generated for (1/8), (2/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 32 / 39 LOC (82.05%) covered.
Coverage report generated for (1/8), (2/8), (3/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 42 / 47 LOC (89.36%) covered.
Coverage report generated for (1/8), (2/8), (4/8) to /home/tobi/github/simplecov/tmp/aruba/project/coverage. 37 / 43 LOC (86.05%) covered.

6 examples, 0 failures

Took 0 seconds

(::) failed steps (::)

expected: 9
     got: 8

(compared using ==)
 (RSpec::Expectations::ExpectationNotMetError)
./features/step_definitions/html_steps.rb:14:in `block (3 levels) in <top (required)>'
./features/step_definitions/web_steps.rb:5:in `block in with_scope'
./features/step_definitions/web_steps.rb:5:in `with_scope'
./features/step_definitions/html_steps.rb:12:in `block (2 levels) in <top (required)>'
./features/step_definitions/html_steps.rb:11:in `each'
./features/step_definitions/html_steps.rb:11:in `/^I should see the groups:$/'
features/parallel_tests.feature:12:in `Then I should see the groups:'

Failing Scenarios:
cucumber features/parallel_tests.feature:9 # Scenario:


Not working materialbox with original photo and preview?

Proposed changes

Screenshots (if appropriate) or codepen:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

At me at pushing it the indicator of infinite loading under a picture is displayed, and in full screen with the original does not pass.

You should try fleshing out the text of your pull request. I don't really know what you are trying to achieve. try explaining it and also give a demo of what it looks like?

Earned with a lower version of jquery 2.1.4. And also there is no refinement when the image jumps after changing the source.

Jumping is because of reflows and recalcs when there are no fixed widths and heights.

There are currently some conflicts which should be resolved in your branch. Can you check them?

Now I'm doing the addition of a preloader.
What conflicts did you notice?

This is some kind of joke?
PS. I made the preloader.

#Not sure what you mean. There are actual conflicts with two files.

You can only see the notice at the bottom in desktop view.

Also afaik we moved the development to the v1-dev branch (instead of master).

I just do not really understand how github works. Excuse me. Do you want to create a pull for v1 dev?

No problem, was not aware of this.
At the top right there is an edit button to edit the PR. You can switch the target branch to v1-dev there.
I am currently not on a computer so it is a bit complicated here. Also I just have simple contributor rights.
I'll try to provide you some more info later when I am on my computer and see what I can do here to bring your PR forward. I'll probably provide a PR to update your PR (basically rebase on current head of v1-dev + resolve conflicts).

Well, how is it supposed to consider such a solution for version 1?


WRO-11352: CustomSkin generator: Fix custom skin components colors.

Enact-DCO-1.0-Signed-off-by: Alexandru Morariu<EMAIL_ADDRESS>Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Changed the variables that overwrite the skin ones to cover the correct css attributes.
Resolution
Additional Considerations
Links
WRO-11352
Comments

Placeholder in Skin Name input still changes when we change component text color.


[DOCFIX] Update README.md with SIGs

@apc999 Do you want other people to review this PR? or we can merge it?

alluxio-bot, merge this please


Add formatter to line-length documentation

Summary
This PR updates the line-length option documentation to mention its usage in the formatter.
I used this as an opportunity to clarify how the line-length is measured (using unicode width rather than characters) and removed the (characters) unit from the line-too-long and doc-line-too-long lints.
Closes #7574
Closes #7573
Note: I decided not to rename the options to -width, at least for now. Mainly because performing the renaming causes other inconsistencies:

The rule line-too-long would need to be renamed to line-too-wide. Same for doc-line-too-long
The ignore-overlong-task-comments option would need to be renamed to ignore-overwide-task-comments.

While I like width more, it seemed out of scope to rush these changes before the formatter release (and change it as part of a patch release).
Test Plan
I generated and reviewed the build documentation.

Current dependencies on/for this PR:

main

PR #8150   👈

This comment was auto-generated by Graphite.


APM cmd

Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[ ] Did you check the debugging guide?
[ ] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
When try use "Apm" on the cmd appear the next line:
"INFO: Could not find any file for given patterns.", "The system can not find the specified archive.", and i dont know if for this warning or error i cant use some package like beautify in C#, where throw me "error permision".
*note: i re-install windows, and only install atom.
*note: my native language is spanish, but i deleted the "option to select this language", because my laptop keyboard is USA, so i use USA-international, if i delete the latinamerican keyboard language option the apm throw "The system can not find the specified archive.", so i include the latinamerican language and the warning disappear so now the only warning left is "INFO: Could not find any file for given patterns."
Steps to Reproduce

CMD
Input "Apm"
throw error

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
apm  1.12.9
npm  3.10.5
node 4.4.5
python
git
visual studio

This is just an informational message that should have no affect on using atom or apm.
The message has been removed in Atom 1.13 which is currently in beta.

ok, thank you.


issues selecting between endpoints

Hi,
I've been using your sample login application (databasedotcom-oauth2-sinatra-jqm) and the code in this gem to try and set up a log in page for users to select which endpoint they should log in through.  I have set up my endpoints like so:
use Databasedotcom::OAuth2::WebServerFlow,
  :debugging            => true,
  :token_encryption_key => Base64.strict_decode64(settings.force['encrypt_key']),
  :display              => "touch", # will force salesforce login to be optimized for touch
  :endpoints            => {"login.salesforce.com" => {
                              :key    => settings.force['client_id'],
                              :secret => settings.force['client_secret']},
                            "myco.secure.force.com" => {
                              :key    => settings.force['client_id'],
                              :secret => settings.force['client_secret']}}

And my login page has two links:
- Click [here](/auth/salesforce?state=%2F&terms=on&endpoint=login.salesforce.com) to login through salesforce.

- Click [here](/auth/salesforce) to login through customer portal.

However I can never get the gem to take the login.salesforce.com.  It will always try to use myco.secure.force.com (or whichever is last in the endpoints list).
I have tried all permutations of the /auth/salesforce link.  In reading the gem, I would think that the following should work:
/auth/salesforce?endpoint=login.salesforce.com

but no cigar.  I've even tried using the exact link from the sinatra sample you've provided and it ignores the endpoint there.  Is there a setting I am supposed to change to allow the endpoints to be selected?
Thank you,
~mattie ruth

i have de same issue when i try to set the endpoint throw  params !
Do you have any update about this issues ?
Thanks


Possible support for Azure Active Directory?

Now it only supports bind and search (pending pull request).
The most significant missing feature is SASL authentication, which is also true for lualdap.

Azure Active Directory Domain Services (Azure AD DS) provides managed domain services such as domain join, group policy, LDAP, Kerberos/NTLM authentication that is fully compatible with Windows Server Active Directory.

https://learn.microsoft.com/en-us/azure/active-directory-domain-services/tutorial-create-instance
So, if ADDS is configured to use Kerberos (GSSAPI), then we cannot even pass the authentication phase.

I wish this could be developed soon @kingluo. So windows domain joined devices can work with resty ldap

@rayhanwatkins Have you tried setting up AD (Kerberos enabled) and managed to bind it via somehow client? If so, could you share some installation and configuration information? Or, have you tried Azure AD (Kerberos enabled)?


Make lsp-python-ms work with the new "lsp.el"

Change-Id: I78918c06aa6af1588c346db9024180ec03a06404

@astenman Thanks, this looks great!  To confirm - this supersedes the previous PR you submitted and closed, right?

This seems to have been manually merged in and can probably be closed now.

@seanfarley thanks for noticing, closing now


new script: move_tags_to_custom_fields

review pls

I haven't tested it yet but the code itself looks great - simple and effective :+1:


Implemented resubscribe on reconnect logic

Fixes #419

Refactored MqttManager: client is now created by MqttManager instead of MqttClientConnectionFn (necessary because callback is invoked before MqttClientConnectionFn returned the MqttClient, and subscribing moved to the onConnect callback.
Changes to MqttSourceTask: no more implicit MqttSourceSettings: now explicitly passed to MqttManager instead of MqttClientConnectionFn
Changes to MqttManagerTest: Added try-finally block so MqttManager is closed even when tests fail. Added test that verifies that manager resubscribes after reconnect.

This change is

@NiekPeeters thanks!


⚠ ClamAV has degraded performance

In 5b1039d, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: ClamAV performance has improved in 375e2fa.


Multiple build issues

Hi
I am trying to follow this tutorial but there have been multiple issues:

The Firebase/AdMob pod results in two conflicting installations for both Firebase and GoogleUtilities
(you get Firebase 3.6.0 as well as latest Firebase, and you get GoogleUtilities 1.3.2 and 7.13.0)
This results in license errors during pod installation ("eg Unable to read the license file LICENSE for the spec Firebase (9.6.0)") and build errors when building (eg says it can't find the GoogleUtilities import)
Some Googling suggested I swap the Firebase/AdMob pod for the Google-Mobile-Ads-SDK pod, but this resulted in various build errors because this code is using GIDSignInDelegate, which is now deprecated. I tried following the migration guide (https://developers.google.com/identity/sign-in/ios/quick-migration-guide) but I didn't understand this code well enough to be able to do this. I did manage to finally get the code to build by simply commenting out some code and changing some other bits, but once the project was finally running, I got an error "The Google Mobile Ads SDK was initialized without an application ID. Google AdMob publishers, follow instructions at https://googlemobileadssdk.page.link/admob-ios-update-plist to set a valid application ID. Google Ad Manager publishers, follow instructions at https://googlemobileadssdk.page.link/ad-manager-ios-update-plist."	0x000000010e307c40" and at this point I gave up as I really only want to follow a simple Firebase tutorial rather than address all these issues, and I know nothing about Google Ad Manager or AdMob.

Hi
I managed to get an application ID and get the code running, but now the tutorial says I need to add the line "GIDSignIn.sharedInstance().delegate = self" to the didFinishLaunchingWithOptions application function in AppDelegate.swift. This is the line of code I had to comment out before, because GIDSignIn has changed and the shared instance no longer has a delegate property. I checked the migration guide for google Signin, but it didn't help me work out how to fix this.
migration guide: https://developers.google.com/identity/sign-in/ios/quick-migration-guide

I have created a PR of the changes I needed to make to get the app to build and run: https://github.com/firebase/codelab-friendlychat-ios/pull/242
See notes in the PR though - I believe there is still work needed to get the GIDSignIn stuff working.
Also anyone using this code will need to add their own app id into info.plist (currently line 63).


Change recycleview to cardview

Currently, the list of contests we are fetching in recyclerView change them to cardView

@Chromicle I'll work on this issue.


birthday added on .txt file

add birthday, it is correct!

Would you kindly give your true birthday


Update the Twitter logo to X

To Reproduce -
Go to the Be a part of community of the website.
In the current version of the website the logo of Twitter is not updated.

Please assign me this issue.

This repository does not contain the source code for the website, closing this as invalid. Duplicate of #2499, #2530.


[BUG]: DatabaseErrorException: ERROR: operator does not exist: uuid = text; Hint: No operator matches the given name and argument types. You might need to add explicit type casts.; Position: 54; SQLState: 42883

What version of drizzle-orm are you using?
0.31.2
What version of drizzle-kit are you using?
0.22.8
Describe the Bug
When I use driver: "aws-data-api" with an RDS database I can't update or delete in the studio without this error: [BUG]: DatabaseErrorException: ERROR: operator does not exist: uuid = text; Hint: No operator matches the given name and argument types. You might need to add explicit type casts.; Position: 54; SQLState: 42883
Following this https://ion.sst.dev/docs/start/aws/drizzle/.
Cross-posting this to drizzle-orm from https://github.com/drizzle-team/drizzle-kit-mirror/issues/421
Expected behavior
I would expect to be able to update and delete from the studio like when using other databases.
Environment & setup
I have only tested development with sst shell drizzle-kit studio.

It seems this also happens when using enums in my case:
Error: ERROR: operator does not exist: agent_task = text; Hint: No operator matches the given name and argument types. You might need to add explicit type casts.; Position: 1879; SQLState: 42883

any way to solve this? the same is happening to me. It started happening when i change my serial primary key to uuid type:
export const SHIPMENTS = EDI_SCHEMA.table(   "shipments",   {     id: uuid("id").primaryKey().defaultRandom(),     bookingNumber: text("bookingNumber").notNull(),     billOfLading: text("billOfLading").unique(),     company: text("company").notNull(),     pol: text("pol").notNull(),     pod: text("pod").notNull(),     finalPod: text("finalPod"),     carrier: text("carrier").notNull(),     createdAt: timestamp("createdAt"),     updatedAt: timestamp("updatedAt"),   },   (t) => ({     bl_company: unique("bl_company")       .on(t.billOfLading, t.company)       .nullsNotDistinct(),   }) );

Any news on this ? I'm getting the same issue, which makes the studio unusable 🥲
Thanks!


Initial addition of kubevirt chart

Pushing to branch to test in cluster. Will undraft when tested
Created using:
docker pull registry.opensuse.org/home/atgracey/kubevirt/containerfile/chart:latest
docker create --name tmp registry.opensuse.org/home/atgracey/kubevirt/containerfile/chart:latest

docker cp dummy:/usr/share/kube-virt/manifests/release/kubevirt-operator.yaml charts/kubevirt/templates/
docker cp dummy:/usr/share/kube-virt/manifests/release/kubevirt-cr.yaml charts/kubevirt/templates/
docker cp dummy:/usr/share/cdi/manifests/release/cdi-operator.yaml charts/kubevirt/templates/
docker cp dummy:/usr/share/cdi/manifests/release/cdi-cr.yaml charts/kubevirt/templates/

docker rm tmp

Where the container is built here: https://build.opensuse.org/package/view_file/home:atgracey:kubevirt/helmchart/Dockerfile?expand=1
Then I templatised the image tags to allow for side loading dev builds and allowed for enabling/disabling components.

This works for k8s 1.24 but not 1.25. For >=1.25 I'll need to bump versions, will ask what the timeline is for that internally

Closing in favour of https://github.com/suse-edge/charts/pull/13.


Fix reposense attribution

Some methods were incorrectly attributed to me, @@author should fix this.

LGTM

Codecov Report

Merging #229 (8df3512) into master (39fa534) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #229   +/-   ##
=========================================
  Coverage     70.51%   70.51%
  Complexity      595      595
=========================================
  Files            85       85
  Lines          1923     1923
  Branches        259      259
=========================================
  Hits           1356     1356
  Misses          448      448
  Partials        119      119

Impacted Files
Coverage Δ

.../java/seedu/intern/logic/commands/ViewCommand.java
22.22% <ø> (ø)

...ain/java/seedu/intern/logic/parser/ParserUtil.java
79.28% <ø> (ø)

...ain/java/seedu/intern/ui/ApplicantDetailPanel.java
0.00% <ø> (ø)

src/main/java/seedu/intern/ui/MainWindow.java
0.00% <ø> (ø)

Continue to review full report at Codecov.

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

lgtm


train update

changelog
-remove swirlies between cars so feels better to traverse
-move cmo office to surgery car and make medical entrance use double doored double doors
-reduced amount of overexposed lighting
-lawyers can now enter brig
-teg room big now and has a burn chamber
-remove lots of insuls around map
-qol fixes for many pipes doors and firelocks
-skub

keep the SWIRLIES you have no soul

the swirlies make it too hard to move around on lots of people got stuck in playtest. harlot

id rather playtest the map more for more data collection

the swirlies make it too hard to move around on lots of people got stuck in playtest. harlot

i told him lol

bruh
😭


implement bbolt snapshot instead of file snapshot

Summary
currently, we use file snapshot(https://github.com/casbin/hraft-dispatcher/blob/main/store/store.go#L107) provided by hasicorp/raft, disk file will be fragmented when there are too many snapshot files, use bbolt snapshot instead of file snapshot should be efficiently.
bbolt: https://github.com/etcd-io/bbolt

Hi, I'm an applicant for GSOC Casbin Mesh project and I'd like to take this issue.


afterChange collection hook and drafts

Link to reproduction
private repo
Describe the Bug
The previousDoc value always returns either the last published version of the document or the last saved draft. This makes it difficult to react on field changes between published versions. For instance we want to add redirects whenever a slug changes but comparing previousDoc.slug to doc.slug will be wrong whenever a draft version was created in between.
The problem is there is no workaround available because in afterChange the last published version is already overwritten if the user publishes the changes.
A solution would be to add a originalDoc property which is equal to the last published version or last available draft if the document was not published before. This would make state handling much easier.
The documentation should be extended to include all necessary details.
To Reproduce

create collection using draft
add afterChange hook
monitor previousDoc value

Payload Version
2.3.1
Adapters and Plugins
db-mongodb, bundler-webpack, live-preview

Have the same problem in a revalidate hook for Next.js. In afterChange it's impossible to distinguish the following state changes:

published (last saved) to draft
draft (last saved) to published

Therefore every afterChange call leads to a revalidation i.e. much too often while editing because of the intermediate draft calls.

A partial workaround is to switch to the beforeChange hook and read the last saved document through the local API:
//Note: only works here, afterChange hook runs too late!
if (originalDoc._status === 'draft') {
    //get last published
    originalDoc = await payload.findByID({
        //@ts-ignore
        collection: collection.slug,
        id: originalDoc.id, //Note: data contains no id
        depth: 0,
        draft: false,
        locale: lang,
        //Note: needed or falls back to default language!
        //Note: returns undefined value on first save
        fallbackLocale: lang
    });

    //Note: right now always getting a document but could be a draft
    if (!originalDoc || originalDoc._status === 'draft') {
        if (DEBUG) {
            console.log('-> could not find last published document');
        }

        return;
    }

    if (DEBUG) {
        console.log('-> read last published document');

        //debug
        //console.dir(originalDoc);
    }
}

However, this has some drawbacks and won't work for revalidation hooks. Here the document has to be saved first.
findById() has some strange behaviors:

Draft query is set to false but still getting a draft document if no document was published yet.
We use a default locale and a fallback in the Payload settings. To know a translation exists, we have to set fallbackLocale to the locale value. In this case we get undefined values being returned or values being pre-processed by other hooks. I would prefer having an API which does not return invalid documents in case a translation does not exist yet.

@cbratschi I am trying to follow along with your issue here. I believe you could accomplish this by writing to the req's context in a beforeChange hook and reading from it in the afterChange hook:
// beforeChange hook

let transitionState: 'fromPublishToDraft' | 'fromDraftToPublish' | null = null
if (originalDoc._status === 'draft' && data?._status === 'published') {
  transitionState = 'fromDraftToPublish'
} else if (originalDoc._status === 'published' && data?._status === 'draft') {
  transitionState = 'fromPublishToDraft'
}

req.context = {
  ...req.context,
  transitionState: transitionState || undefined,
}

And then in your afterChange hook you could read from the req.context and determine if the document is transitioning from publish to draft or draft to publish or neither.
Does that sound like it would assist you with what you are looking to accomplish?

@JarrodMFlesch the situation is more complicated than that but the context could be used to pass data available at beforeChange to afterChange.
The follow transitions happen:

edit a (original) document
modify content
document is saved as draft

beforeChange: originalDoc is the original document (correct naming)

save document

beforeChange: originalDoc point to the last draft (points to the last saved document, not the original one)

We use the code listed above to read the real original document in beforeChange (see https://github.com/payloadcms/payload/issues/4405#issuecomment-1845584738).
A workaround would be:

beforeChange

read original document from database
pass original document to context

afterChange

get original document from context (use for business logic)


Migrate from Laravel Mix to Vite

This pull request includes changes for migrating from Laravel Mix to Vite outlined in Migration Guide and automated by the Vite Converter.
Before merging, you need to:

Checkout the shift-109094 branch
Run composer update
Run npm install
Review all comments for additional changes
Thoroughly test your application (no tests?, no CI?)

Please send your feedback to<EMAIL_ADDRESS>or share the good vibes on Twitter.

:x: Shift did not remove some of the previous npm scripts running mix commands as they appeared to be customized. You should review the scripts configured in your package.json file and update any custom commands to use vite.

:warning: Shift detected you are using Vue. As such, Vite recommends importing your CSS from your JavaScript entry point. This will improve your development experience by avoiding flashes of unstyled content during hot reloading.
Shift removed your CSS entry point from your Vite configuration. However, you will need to import this CSS in your JavaScript entry point.

:information_source: Previously, Laravel configured several npm scripts for building assets. For Vite, Laravel configures a dev script for generating and watching your assets (for development) and build script for generating your assets (for production).
Shift automated this change by replacing commands using these scripts with their new Vite script. However, you may still be referencing these scripts in your code or in deployment scripts.

:information_source: Laravel renamed the environment variables used by Mix to use a VITE_ prefix, instead of MIX_. While Shift automated this change throughout your code, you should check for any additional references which may not be included in your Git repository.

:warning: Shift found files which appeared to contain JSX but had a .js file extension. Vite requires these files to have a .jsx file extension.
While Shift automated this change, you may have additional files which contain JSX or may need to update any imports explicitly referencing the old .js file extension.

:warning: Vite generates frontend assets to the public/build folder. This folder is not tracked by Git within a default Laravel project. As such, Shift added this folder to your .gitignore file.
If you wish to track the generated frontend assets within your project, such as for ease of deployment, you may undo this commit by running git revert d26f2bec.

:warning: Shift detected you may be using the tilde (~) prefix to import CSS or JavaScript. You may try to add an alias for the ~ to your Vite configuration. Alternatively, you may update these imports to use an absolute reference or @ alias.

:information_source: The new @vite Blade directive outputs <script> tags with the type="module" attribute. This attribute implicitly defers the script. This is a difference from Laravel Mix which may change the execution order of the JavaScript on your page.
If you experience JavaScript errors relating to undefined references, you may need to reorder your scripts or add the defer attribute to any inline <script> blocks on your page.

:alembic: This Shift is still being refined. Please report any issues or suggestions to<EMAIL_ADDRESS>Your feedback is what helps improve the experience for everyone.


General principles page

Tracking Info
Resolves #5
Changes
Created General Principles and Emergency Care pages, created bullet point component that is used in a lot of other pages with the same format at General Principles (such as Emergency Care), used nested list view for multiple subpoints
Testing
Checked the page on iOS device and Android virtual device, both of which were different screen sizes too, worked fine in all cases.
Confirmation of Change

Looks awesome guys! Great job, especially with those bullet point components. Aside from what Anthony and Lillian mentioned, it appears to run well for me. Approving this PR, great job guys!


Reduced set of plugins causes missing PACKAGE_UNRELOCATABLE_TEXT_FILES

I've read Brief overview section and do understand basic concepts. [Yes]
I've read F.A.Q. section and haven't found an answer to my question. [Yes]
I've read Code of Conduct, I promise to be polite and will do my best at being constructive. [Yes]

I'm using PARAM_EXTRA_FLAGS on gst_plugins_{base,good,ugly,bad} in my local config.cmake for Hunter 0.23.154 to limit the set of gstreamer plugins to be included in my project. (Incidentally: how to add multiple options using PARAM_EXTRA_FLAGS? Neither setting multiple instances nor using double quotes, ie. "--with-x --without-y" works for me).
I can see that the autotools configuration happens as it should and building is fine. However, when Hunter starts to save the build to cache it wants to patch the plugin's .la files as listed in the project's hunter.cmake under PACKAGE_UNRELOCATABLE_TEXT_FILES. The first file that's missing causes a FATAL ERROR: File not exists:
-- [hunter *** DEBUG *** 2019-04-18T21:34:23] Saving to cache: gst_plugins_base
[hunter ** FATAL ERROR **] File not exists:
[hunter ** FATAL ERROR **]   /home/emile/.hunter/_Base/d720f37/5930f74/e6c0184/Build/gst_plugins_base/Install/lib/gstreamer-1.0/libgstadder.la
[hunter ** FATAL ERROR **] (check HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES)
[hunter ** FATAL ERROR **] [Directory:/home/emile/.hunter/_Base/Download/Hunter/0.23.154/d720f37/Unpacked/cmake/projects/gst_plugins_base]
(This also happens for me for gst_plugins_bad without having set PARAM_EXTRA_FLAGS, if I don't have hunter_add_package(BZip2) anywhere, since that prevents the bz2 plugin from being built).
The question I'd like to raise is whether the patching for HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES should not better silently skip files that have not been created during the build. If they were necessary, the issue will show up later, just as before the unrelocatable text file patching was implemented.

how to add multiple options

Both spaces and ; should work fine:
CMAKE_ARGS A=a b c d

CMAKE_ARGS A=a;b;c;d

Neither setting multiple instances

It's equivalent to -DA=a -DA=b -DA=c so they are overwriting each other.

using double quotes

I'm not sure how autotools (GStreamer use non-CMake build scheme) interpreter this, but probably it ends up as a single argument with space or even argument with quotes inside.
If you do A="a b" it's passed as \"a\ b\" to a command line, see the example:

https://cgold.readthedocs.io/en/latest/tutorials/variables/regular.html#quotes

This also happens for me for gst_plugins_bad without having set PARAM_EXTRA_FLAGS, if I don't have hunter_add_package(BZip2) anywhere, since that prevents the bz2 plugin from being built

The default configuration should work fine:

https://travis-ci.org/ingenue/hunter/builds/412409441

Probably that's the error.

The question I'd like to raise is whether the patching for HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES should not better silently skip files that have not been created during the build

As far as I can see it's not silently skipped, you have an error while creating cache archive.

If they were necessary, the issue will show up later, just as before the unrelocatable text file patching was implemented.

You want an issue to be raised later? It's not clear for me what behavior you want to have.

Indeed, the issue isn't multiple CMAKE_ARGS but multiple PARAM_EXTRA_FLAGS (formerly EXTRA_FLAGS) for the autotools scheme. As you described in cgold under case c, PARAM_EXTRA_FLAGS="--option-1 --option-2" gets interpreted as an unquoted argument and the quotes end up in funny places. However, PARAM_EXTRA_FLAGS=--option-1 --option-2 will cause --option-2 to be interpreted as a CMAKE_ARGS argument and not be part of PARAM_EXTRA_FLAGS.

The default configuration should work fine: https://travis-ci.org/ingenue/hunter/builds/412409441

That shows only gstreamer-1.0 itself, not gst_plugins_*, right?

As far as I can see it's not silently skipped, you have an error while creating cache archive.

Right, and what I am wondering is if that is the right thing to do (sorry for expressing that a little unclearly).
Right now, using HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES requires that all listed files are present after building and fails if anyone of them is missing, even if for completely valid reasons (a reduced set of plugins, normal customization using CMAKE_ARGS). Having Hunter construct the list of files based on second guessing the package's build process and flags does not seem right and the project's default.cmake is not part of the configuration if you don't fork Hunter. It seems better to let the patching process take all files listed and just silently ignore missing files.

You want an issue to be raised later? It's not clear for me what behavior you want to have.

If the build fails or any essential file is missing, that will cause an error later, somehow or other, and that's fine by me. I meant to say it's not important for the patching process for HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES to check if all build artefacts are present for archiving.
The behaviour I'd like to see is that HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES ignores missing files, quite simply.

That shows only gstreamer-1.0 itself, not gst_plugins_*, right?

It seems so. Qt camera example should use all of them:

https://github.com/ruslo/hunter/blob/v0.23.158/examples/qt-camera/config.cmake#L47
https://github.com/ruslo/hunter/blob/v0.23.158/cmake/projects/Qt/schemes/url_sha1_qt.cmake.in#L203-L209

Build log:

https://travis-ci.org/ingenue/hunter/jobs/504140950

It seems better to let the patching process take all files listed and just silently ignore missing files

The behaviour I'd like to see is that HUNTER_PACKAGE_UNRELOCATABLE_TEXT_FILES ignores missing files, quite simply.

I don't think it's a good idea, at least to do it by default. Maybe an optional feature UNRELOCATABLE_TEXT_FILES_OPTIONAL or allow a user to customize it similar to CMAKE_ARGS mechanism.

I'm preparing a patch, please see https://github.com/ruslo/hunter/pull/1864

https://github.com/ruslo/hunter/blob/v0.23.214/README.rst


Cannot 'make' when installing on linux.

I'm a newbie to this kind of stuff, and when running make build/libv86.js, I get the following result;
root@hn:/var/www/hn.fyi/test/emu/v86# make build/libv86.js
wget -P closure-compiler https://dl.google.com/closure-compiler/compiler-20190709.zip
--2020-05-24 13:45:58--  https://dl.google.com/closure-compiler/compiler-20190709.zip
Resolving dl.google.com (dl.google.com)... 2a00:1450:4007:805::200e, <IP_ADDRESS>
Connecting to dl.google.com (dl.google.com)|2a00:1450:4007:805::200e|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7342217 (7.0M) [application/zip]
Saving to: ‘closure-compiler/compiler-20190709.zip.2’
compiler-20190709.zip.2                 100%[=============================================================================>]   7.00M  --.-KB/s    in 0.1s
2020-05-24 13:45:58 (47.5 MB/s) - ‘closure-compiler/compiler-20190709.zip.2’ saved [7342217/7342217]
unzip -d closure-compiler closure-compiler/compiler-20190709.zip *.jar
Archive:  closure-compiler/compiler-20190709.zip
replace closure-compiler/closure-compiler-v20190709.jar? [y]es, [n]o, [A]ll, [N]one, [r]ename: A
inflating: closure-compiler/closure-compiler-v20190709.jar
mv closure-compiler/*.jar closure-compiler/compiler.jar
mv: target 'closure-compiler/compiler.jar' is not a directory
Makefile:158: recipe for target 'closure-compiler/compiler.jar' failed
make: *** [closure-compiler/compiler.jar] Error 1
And it fails.

Try rm -r closure-compiler and then run make again.


Multiple definitions

You have variables definitions in .h file. And when you try to make this project, you already have errors.
make server gcc -c -o main.o main.c gcc -c -o httpd.o httpd.c gcc -o server main.o httpd.o /usr/bin/ld: httpd.o:(.bss+0x0): multiple definition of method'; main.o:(.bss+0x0): first defined here
/usr/bin/ld: httpd.o:(.bss+0x8): multiple definition of uri'; main.o:(.bss+0x8): first defined here /usr/bin/ld: httpd.o:(.bss+0x10): multiple definition of qs'; main.o:(.bss+0x10): first defined here
/usr/bin/ld: httpd.o:(.bss+0x18): multiple definition of prot'; main.o:(.bss+0x18): first defined here /usr/bin/ld: httpd.o:(.bss+0x20): multiple definition of payload'; main.o:(.bss+0x20): first defined here
/usr/bin/ld: httpd.o:(.bss+0x28): multiple definition of payload_size'; main.o:(.bss+0x28): first defined here collect2: error: ld returned 1 exit status make: *** [Makefile:8: server] Error 1

I just received the same error message.
Any news on that?
@zloyvolkey  What did you do to be able to use the library anyway?

@mocle Cuz author don't try to test his own code - I don't use this library. I write my own raw tcp client-server library/

@mocle I was able to compile with the following modifications. using extern declaration in main.c and moving the declaration from httpd.h into httpd.c
main.c
#include "httpd.h"
#include <stdio.h>

// Client request
extern char     *method,    // "GET" or "POST"
        	*uri,       // "/index.html" things before '?'
        	*qs,        // "a=1&b=2"     things after  '?'
        	*prot;      // "HTTP/1.1"

extern char    *payload;     // for POST
extern int      payload_size;

int main(int c, char** v)
{
	serve_forever("12913");
	return 0;
}

void route()
{
	ROUTE_START()

	ROUTE_GET("/")
	{
		printf("HTTP/1.1 200 OK\r\n\r\n");
		printf("Hello! You are using %s", request_header("User-Agent"));
	}

	ROUTE_POST("/")
	{
		printf("HTTP/1.1 200 OK\r\n\r\n");
		printf("Wow, seems that you POSTed %d bytes. \r\n", payload_size);
		printf("Fetch the data using `payload` variable.");
	}

	ROUTE_END()
}

httpd.h
#ifndef _HTTPD_H_
#define _HTTPD_H_
#include <string.h>

//Server control functions

void serve_forever(const char *PORT);
char *request_header(const char* name);

// user shall implement this function

void route();

// some interesting macro for `route()`
#define ROUTE_START()       if (0) {
#define ROUTE(METHOD,URI)   } else if (strcmp(URI,uri)==0&&strcmp(METHOD,method)==0) {
#define ROUTE_GET(URI)      ROUTE("GET", URI)
#define ROUTE_POST(URI)     ROUTE("POST", URI)
#define ROUTE_END()         } else printf(\
                                "HTTP/1.1 500 Not Handled\r\n\r\n" \
                                "The server has no handler to the request.\r\n" \
                            );

#endif

httpd.c
#define CONNMAX 1000

// Client request
char    *method,    // "GET" or "POST"
        *uri,       // "/index.html" things before '?'
        *qs,        // "a=1&b=2"     things after  '?'
        *prot;      // "HTTP/1.1"

char    *payload;     // for POST
int      payload_size;

static int listenfd, clients[CONNMAX];
/* inserted between the above lines */

@mocle Cuz author don't try to test his own code - I don't use this library. I write my own raw tcp client-server library/

don't be so mean. and if you wrote your own, it would've been nice if you had it on your git

@mocle Cuz author don't try to test his own code - I don't use this library.


Add class or wrapping div to iframe?

Would it be possible to add a config setting that would allow for class names on the iFrame, or, better yet, a wrapping div with a custom className?

@kentcdodds I love that idea. This gives greater flexibility on adding custom HTML for each provider/transformer.
It would also be great if that function could also get the provider information from https://github.com/remark-embedder/transformer-oembed also. Something to the effect of:
function handleHTML(html, {url, config}) {
  if (!isUrlIWantToChange(url, config)) return html

  if (config.provider.provider_name === 'YouTube') {
    return `<div class="youtube aspect-w-16 aspect-h-9">${html}</div>`
  }

  return `<div class="general-wrapper">${html}</div>`
}

I can try working on it but my skills aren't the greatest. It might be better for something more experienced than myself to handle this.

If you get stuck, just push what you have in a PR (use git commit with the --no-verify if you need to) and I can help you out. Rather than having the provider added to the config, maybe there can be an additional option provided. I haven't thought much about it, but go ahead and try to make it work the way you think you'd like it and we can work through the API.

@kentcdodds just submitted PR. Feel free to review 👍🏻

Closed with #26


Can't force reconnect while within transaction and connection lost

Laravel Version: 5.3.*

Description:
It seems that the framework don't provide any way to reconnect to database while within a transaction and connection is lost.
Steps To Reproduce:
It is hard to reproduce. Not having the option of handling such a situation is bad. It may happen if someone is working with daemon queue workers and for some reason a transaction is not closed within a job and is leaked out. It may also happen for queries that are expected to take long.
    public function reconnect($force = false)
    {
        ...
    }
    ...
    public function setPdo($pdo, $force = false)
    {
        if ($this->transactions >= 1 && ! $force) {
            throw new RuntimeException("Can't swap PDO instance while within transaction.");
        }

        $this->transactions = 0;

        $this->pdo = $pdo;

        return $this;
    }

what do you suggest? how do you think we should handle this?

I was working on a PR to add a $force = true param to DB::reconnect().

There is another PR already open to fix this I believe? https://github.com/laravel/framework/pull/15511

#15511 sounds to be different. My PR lets the client code do this:
try {
DB::beginTransaction();
...
//possibly nested transactions are here without any extra try-catch
...
DB::commit();
} catch (Exception $e) {
   try {
   while(DB::transactionLevel() > 0) DB::rollBack();
   } catch (Exception $e) {
       //This looks only possible after the pull request: to handle lost connection or any other reason that makes rollbacks impossible.
       // Without this PR the application must be aborted, a terrible situation for daemon workers as an example.
       DB::reconnect(true);
       throw $e;
   }
}

@halaei was this taken care of by any of your PRs?

Does github have a problem with replies via email? I answered 2ice via email but both are failed I think?
Sorry for possible duplicate replies:
@themsaid Yes check this please: https://github.com/laravel/framework/pull/15931
It is simple and hopefully working. This issue is now closed for 5.3. I may not try for a proper change for 5.1 though.

Yes check this please: https://github.com/laravel/framework/pull/15931
It is simple and hopefully working. This issue is now closed for 5.3. I may
not try for a proper change for 5.1 though.


Move <configuration> in jmeter-analysis-maven-plugin out of <execution>

Otherwise running jmeter-analysis:analyze by itself produces an error. See this issue for more details.

I can do a PR if you prefer.


Mostly Panel updates and style changes

Hello 😀

Forgot to update test scripts ... I'll open new PR when ready.

@AscendFB Sounds good. If you need any help with testing or have questions about our CI system please let me know.

Well, I've been struggling with that as you can see. I still try to figure out the currently shown errors (at #1391) from CI because all tests in my local terminal ran fine without errors. Is there anything different being checked in CircleCI? Is there a way to trigger these tests again or is a new PR needed when fixes are committed?

@AscendFB I will have time to up the coverage for you on Monday if you would like (we're happy to get your contributions and understand that testing can be tedious).
To answer your question though, here's how I usually do it:
First, I can check coverage by running:
sudo docker-compose run web rake coverage:run

which will generate output like this:
This build:
Statements: 0.2791%
Branches:   0.2306%
Functions:  0.2959%
Lines:      0.2871%
Aggregate:  0.2708%

Using data from 4 recent coverage builds.

Coverage history (newest to oldest):
staging: 97.046%
staging: 96.982%
staging: 96.982%
staging: 96.979%

=====================================
COVERAGE RESULTS
This build:     0.27083794%
staging  build: 97.04648248% 968ee6c0
=====================================
Difference:     -96.77564454%
Pass?           no

This is useful, but does not tell you why coverage does not pass. To know which files are missing coverage, you can run:
sudo docker-compose run web npm run test-slow

As the name implies, this test run will be much slower than npm run test. The reason it is slower is because the test suite will run a "coverage report". The coverage report will look like this:

The report above is an HTML file located at coverage_fe/index.html. It is dynamically generated after each run of test-slow. You can open it in any web browser via the file:/// protocol.
You can click around and look for files that you have either authored or modified. In order for CI to pass, you must cause test coverage to increase for all files created and modified. Open the files that were modified and look for red text, which indicates that the line is untested code. Our test coverage is very high and most of the untested lines are legacy code that existed before the test suite was created:

In the example above, line 76 lacks test coverage. Please be sure when you do add assertions to the test suite, they are "realistic" and cover common use cases, plus edge cases. A unit test that simply executes a function without doing proper assertions is problematic because it makes test coverage look higher than it really is without actually being able to detect problems later.
I hope that helps answer your question! As mentioned, I'd be happy to write the unit tests for you as an example if you are unfamiliar with Jest, Enzyme or unit testing. Please let me know.

To add to that, the full list of checks can be viewed here.
The failing command checks that the code test coverage doesn't decrease more than a set threshold. Since the coverage decreased in the current PR because code that is no longer necessary was removed, in my opinion the PR #1391 is ready to merge as is.
As for your second question, CircleCI will automatically run again when changes are committed while a PR is open, so no new PR is needed.
Thanks again for the PR!

Thank you both for taking the time to make the testing procedure clear for me. That detailed writeup really helps me a lot and I really appreciate that! Hopefully your efforts will pay off with my contributions in the future 👍
In the past I've only ran npm run test which didn't show any errors, now that I'm aware that coverage is also important I will rather run the test-slow. I just tried run web rake coverage:run and  npm run test-slow and it was working as expected.
In my recent changes I had no struggles with unit tests as they were pretty standard. But I'll be cautious if something comes up that I'm not yet familiar with and tell you to check what I've done. Its a whole new environment for me that I need to get familiar with so I start with pretty easy tasks.
I still got a few questions:

Do I need to worry if one or more commits in the PR are marked with a red cross?

In this test it looks like something went wrong on CI side. Is it necessary to react in some way to repeat the test cycle like a retrigger?

What can I do when CI failed because of a decreasing coverage (like #1391)? Write a comment in the PR to let you know what is missing?

@AscendFB

Do I need to worry if one or more commits in the PR are marked with a red cross?

This means that when you pushed that commit up, it did not pass CI. As long as the most recent commit passes CI, it's OK.

repeat the test cycle like a retrigger?

This is a known bug that we have unfortunately not had time to investigate. It is a bug in the CI configuration and not a bug in your code. I do not know if non-admins have permission to restart failed builds, but there is a "rebuild" button.

Again, I don't know if you need admin rights to see the "rebuild" button, but you would get to the screen by clicking on the "details" view of Circle CI:

What can I do when CI failed because of a decreasing coverage (like #1391)? Write a comment in the PR to let you know what is missing?

If the use case is too difficult to test I will get a notification about it via Github. I am happy to write the tests if need be. I realize some use cases are not easy to test. In this case, I am back in the office after the weekend and can take a look today.

Again, I don't know if you need admin rights to see the "rebuild" button, but you would get to the screen by clicking on the "details" view of Circle CI:

Yes, write permissions are needed, just FYI. But since that bug doesn't seem to occur often, this should not be a problem.


Unable to load the "svg2img" library. SVGs are not supported

I'm getting this warning every time I run a bubblewrap build (or any other bubblewrap command really).
What can I do to resolve this?
> bubblewrap build
Unable to load the "svg2img" library. SVGs are not supported
,-----.        ,--.  ,--.  ,--.
|  |) /_,--.,--|  |-.|  |-.|  |,---.,--.   ,--,--.--.,--,--.,---.
|  .-.  |  ||  | .-. | .-. |  | .-. |  |.'.|  |  .--' ,-.  | .-. |
|  '--' '  ''  | `-' | `-' |  \   --|   .'.   |  |  \ '-'  | '-' '
`------' `----' `---' `---'`--'`----'--'   '--`--'   `--`--|  |-'
                                                           `--'
Using passwords set in the BUBBLEWRAP_KEYSTORE_PASSWORD and BUBBLEWRAP_KEY_PASSWORD environmental variables.

Building the Android App...

I've already run:
npm i -g svg2img
npm i svg2img (in the folder where I run bubblewrap)
But I'm still getting the same issue.
In the catch block at: https://github.com/GoogleChromeLabs/bubblewrap/blob/830dbe695c1e690c81c0a6b29dbdd75693586f47/packages/core/src/lib/wrappers/svg2img.ts
It would probably help if the actual exception was printed too (or logged somewhere).
Thank you!

OS: Windows 11
Version: 1.17.2

This is due to the canvg dependency on native libraries. If those are not available, canvg fails to install when npm install @bubblewrap/cli runs.  Since many users don't need SVGs, Bubblewrap uses it a an optional dependency and tries to use it at runtime.
I just learned about @resvg/resvg-wasm, which is based on pure Rust implementation called resvg, which can be compiled to WASM and would remove any native dependencies. It's probably worth trying to replace canvg with @resvg/resvg-wasm.
@tropicadri FYI

A new version using resvg was published.


iOS7 Crash

NSDateComponentsFormatter cause crash on "XCDYoutubeVideo.m"
Symbol not found: OBJC_CLASS$_NSDateComponentsFormatter

Version 2.5.4 of XCDYouTubeKit officially dropped support for iOS 7 and requires iOS 8.


redis-cli <IP_ADDRESS>:6379> HSCAN to ioredis function

I'm trying to get the date from my HashMap, if the key of my HashMap matches the pattern *_i*.
<IP_ADDRESS>:6379> HSCAN MY_HM_EVT 0 MATCH *_i* COUNT 9999999

what is the wrapper in the ioredis client,
that I can use to achieve the above code written in redis-cli

function scan (count) {
  return redis.hscan('MY_HM_EVT', count || 0, 'MATCH', '*_i*', 'COUNT', 9999999).then((nextCount, results) => {
    console.log(results)
    return scan(nextCount)
  })
}

thanks but i used hscanStream
can you look at it and tell me if it's better and optimized or should i use hscan only ?
var name = "MY_HM_EVT";

var obj = {
  match: '*',
  cursor: 0,
  count: 10
};

if(pattern)
  obj.match = pattern
if(batchSize)
  obj.count = batchSize

var stream = redis.hscanStream(name, obj);
var keys = {};
stream.on('data', function (resultKeys) {
  // `resultKeys` is an array of strings representing key names
  for (var i = 0; i < resultKeys.length; i++) {
    if(i % 2){
      // Logic as output is
      // 1) "806_i" => Key (present in 'i-1')
      // 2) "1520508780,2273" => value (present in 'i')
      keys[resultKeys[i-1]] = resultKeys[i];
    }
  }
});
stream.on('end', function () {
  cb(null,keys);
});

i was looking for the reposnse as same standard as how the client gives for rpop and other pop function
redis.rpop(name, function(err, result) {
  if (err) {
    lmessages("err", err, "result", result);
  }
  cb(err, result);
});


MINOR: Improve security documentation for Kafka Streams

Migrate content from https://github.com/confluentinc/docs/pull/4655.
Also restore content from https://github.com/apache/kafka/pull/4532, which seems to have been lost along the way. cc @mjsax

Thanks for the PR @JimGalasyn! Merged to trunk.


Unable to import from relative packages

When I run the demo_pipeline.py as is, I get an error from each of the scripts that call functions from another script. For example, eval_wall_thickness.py gives the error "ModuleNotFoundError: No module named 'common'" for
`from common.cardiac_utils import *'
How should I fix this error?

The module common can be imported, if you add the git repository to the environment variable PYTHON_PATH, such as
export PYTHONPATH=YOUR_GIT_REPOSITORY_PATH:"${PYTHONPATH}"


Added -DefaultSensitivityLabelForLibrary to Set-PnPList

Type

[ ] Bug Fix
[X] New Feature
[ ] Sample

Related Issues?
N/A
What is in this Pull Request ?
Added -DefaultSensitivityLabelForLibrary to Set-PnPList which allows setting the default sensitivity label for a library

Hello @KoenZomers
I am trying to use the above command but it says
Set-PnPList : A parameter cannot be found that matches parameter name 'DefaultSensitivityLabelForLibrary'.
I have update the module to the latest. Could you please tell me what I am doing wrong.
Thanks

@NaveenRajdev Update to the latest nightly release using Update-Module PnP.PowerShell -AllowPrerelease

I ran the updated command and it still gives me the error. Could you please let me know what the next step I can follow is to accommodate the same?
Naveen Rajdev
E
<EMAIL_ADDRESS>M
+61 470 254 804
P
1300 835 723
velrada.comhttps://velrada.com/
From: Koen Zomers @.>
Sent: Wednesday, 1 March 2023 4:01 PM
To: pnp/powershell @.>
Cc: Naveen Rajdev @.>; Mention @.>
Subject: Re: [pnp/powershell] Added -DefaultSensitivityLabelForLibrary to Set-PnPList (PR #2825)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@NaveenRajdevhttps://github.com/NaveenRajdev Update to the latest nightly release using Update-Module PnP.PowerShell -AllowPrerelease
—
Reply to this email directly, view it on GitHubhttps://github.com/pnp/powershell/pull/2825#issuecomment-1449514656, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A6GF5HYIN2Y6AFZS7JKIT2TWZ36Z5ANCNFSM6AAAAAAU5NJNGQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Naveen,
I make it work with the build 2.0.35.
It work. If you call the fonction with the name you will need to be Conformity Administrator to get the GUID automaticly.
If you call it with the GUID directly, it will work with lower priviledge.
Thanks


Cannot create new node because of DevEUI size check

Hi,
After installing new version (looks like this bug appeared about 7-10 days ago) I can't create a new node.
If I put a size of 8 byte in DevEUI it shows message 'exactly 16 bytes are expected', when I put 16 bytes in it it says 'exactly 8 bytes are expected'.

Also I suggest to exclude this check:
if ns.DevAddr.NwkID() != a.ctx.NetID.NwkID() {
return grpc.Errorf(codes.InvalidArgument, "DevAddr must contain NwkID %s", hex.EncodeToString([]byte{a.ctx.NetID.NwkID()}))
}
from file /internal/api/node_session.go because it is a usual situation when you buy a node with fixed DevAddr written on it and this check doesn't allow to add this node.

The error you're seeing is related to the AppKey field, not the DevEUI. Please note that the web-interface is really basic (at some point, there will be a better one, but I wanted to provide a gui on top of the API at least).
Regarding your second point, I'm not sure if it is common that a node has a fixed DevAddr. The check is there since the NwkID prefix will be used for roaming. I've heard this is now under discussion and might be specified further in the upcoming LoRaWAN spec.
(one option I'm considering is to make the NetID optional, so that the full 32 bit address space can be used, when NetID and NwkID is not important)

Yes, you right, there's no problem in node creation here. Regarding DevAddr, at least in Loriot server they allow any DevAddr. And to me it seems that it is very convenient if you print on a sticker an addr of node and put it on sensor so that you may see which is sending data on gateway or server without connecting to it.

Wouldn't the DevEUI make more sense (this EUI is as well being used as identifier to the application)? Please note that after an OTAA, the device will get a new random DevAddr.

Agree, it is not a simple question. In my case we use only ABP as it is more secure and DevAddr is the only thing you see from gateway to understand who is the sender. Anyway it is not a bug and you may leave it or remove as you wish. For me it is easier if it is removed.

Making the NetID (and thus the NwkID prefix in the DevAddr) optional might be the best solution I think :-) I'll look into it. Mind if we close this issue and track the DevAddr issue in #56?

Agree =)


Update dataverse plugin

In load_cache() the extraction of external metadata sources is removed, extracts now only the metadata from the dataverse not its external sources.
The handle.net resources ( a unique case ) is also adjusted with the change and does not extract the external source anymore.
Simple update to the parse() function to adjust with document load.
Added the extraction function to an external .txt for future reference if needed.

@jal347 @gtsueng I have an jupyter notebook if we need to go over some of the ways the documents look, plus I have lists of unique keys for the various data sources (harvard vs. the external data). But I didn't add any new keys, so it should still be schema.org compliant as before?


failed to convert llama_2 7B model in .gguf to .bin format

I have tried to convert  llama 2 model from .gguf to .bin
~/llm_inferences/llama.cpp/models/meta$ ls
llama-2-7b.Q4_K_M.gguf

python3 export.py llama2_7b.bin --meta-llama /home/####/llm_inferences/llama.cpp/models
Traceback (most recent call last):
  File "/home/aadithya.bhat/llm_inferences/llama2.c/export.py", line 559, in <module>
    model = load_meta_model(args.meta_llama)
  File "/home/aadithya.bhat/llm_inferences/llama2.c/export.py", line 373, in load_meta_model
    with open(params_path) as f:
FileNotFoundError: [Errno 2] No such file or directory: '/home/aadithya.bhat/llm_inferences/llama.cpp/models/params.json'

I have downloaded this model from https://huggingface.co/TheBloke/Llama-2-7B-GGUF, the model with name ending with Q4_K.gguf

llama2.c supports conversion of original llama2 checkpoints, not quantised ones in gguf format.

Yes noted. I did not follow the instructions carefully.


delete obsolete module kbclick.js

Fixes internal issue CFPB/knowledgebase#178
This JS is obsolete, a security risk, and all references have been removed from the knowledgebase project. This change deletes the JS module from the website altogether. We were planning to release the update to the knowledgebase repo separately on Monday - this change can go live anytime after that, and is not a dependency otherwise.
Removals

kbclick.js

Review

@rosskarchner

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

💥  that 💾  debt
👍

:+1:

FYI, the change in knowledgebase that is a dependency for this change is now planned for release to production tomorrow morning (~10am)


Derive Serialize for JournalEvent

Small addition, I find myself needing to serialize an JournalEvent, but it's not implemented.

Thank you as always!

Releases 0.6.1 which includes these changes 🎉


🐞 Fix: vertical style issue.

Fix #85  .

I've done everything, I think it's a good time to merge in order to avoid rebasing.

We will review as soon as possible and if everything is ok then we will merge it.

Thank you for the fix @hadizakialqattan! If you are interested in contributing unimport, feel free to just state I want to work on this issue and send your PR. We're glad to see people contributing.


Add Xcode 7.1 GM to DVTPlugInCompatibilityUUIDs

@dppeak cheers :beers:

There should be a script that automates all of this Xcode UUIDs update stuff :]

@onmyway133 that would be great!

@zenangst forget to mention that it is https://github.com/onmyway133/Minion :stuck_out_tongue_winking_eye:

@onmyway133 awesome! I'll check it out! :grin: