Laravel 5: New session created each time a request is made

I have implemented JWT middleware, and i think almost the same JS as in your Satellizer Angular demo into an Ionic app.
But everytime i make a request a new session is created, when it should use the aleady created one that belongs to the Bearer...
Any ideas on why this might happen?
PS: i know wihout code is much more difficult.

I have the feeling that it has something to do with using cross domain.
I mean, for example chrome generates an OPTIONS before every GET request... I get the filling that this has something to do with the multiple session's creation.
Something that doesn't happen after building the app and testing it from the device.

@fcaivano the current JWT will create a new token every time you authenticate and refresh. JWT dev address fixes this issue by replacing the existing session.


Update limits-and-config.md

Removed Medium low1, low2 references as they are not being used

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

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


fix github actions deprecation warnings + preflight checks

update action dependencies to avoid deprecation warnings
add more error checking and preflight checks around SDK webservice assumptions

reference points:

actions/cache: https://github.com/actions/cache/issues/953
actions/checkout: https://github.com/actions/checkout/issues/959
seanmiddleditch/gha-setup-vsdevenv: https://github.com/seanmiddleditch/gha-setup-vsdevenv/pull/15

Could we merge this? @humbletim

Guess a year between reminders is ok @humbletim

Can you merge this @humbletim ?

Hi.. I am (somewhat) back again and in any event planning to get this PR merged this week. Apologies for the delay. Also if anyone is interested in adopting lead responsibility for the project or helping to co-maintain please let me know.

Hi.. I am (somewhat) back again and in any event planning to get this PR merged this week. Apologies for the delay. Also if anyone is interested in adopting lead responsibility for the project or helping to co-maintain please let me know.

Don't worry. I could help you out 😃

Hi.. I am (somewhat) back again and in any event planning to get this PR merged this week. Apologies for the delay. Also if anyone is interested in adopting lead responsibility for the project or helping to co-maintain please let me know.

Thank you! This is awesome!

Hi everyone!
There seems to be a recent issue building SPIRV-Tools on macOS. While unrelated to this PR, I typically run a final "CI build" on different platforms before releasing. Unfortunately, Mac builds are failing for all but the the latest SDK version, apparent due to sprintf-related warnings being promoted into errors by compile flags somewhere. Which for older releases should not have changed... but could have for example on LunarG webservices config.json side of the equation.
To understand the scope of the problem, I'd appreciate it if anyone using the SDK on Mac could share:

Which SDK version are you targeting?
Have you encountered any recent build failures related to sprintf?

I'm planning to merge this PR to "main" later tonight after one final non-mac-legacy CI test, but am thinking to hold off on stamping an official release tag until I have a clearer picture of the Mac issue. Once I gather more information, I plan to file an issue report and potentially involve relevant teams for a resolution.
Thanks for your input!


Update Raft to 0.4.0

What have you changed? (mandatory)
Updates Raft to 0.4.0.
Closes #3836, #3632.
What are the type of the changes? (mandatory)
Improvement
How has this PR been tested? (mandatory)
CI
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No
Refer to a related PR or issue link (optional)
Closes #3836, #3632.
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)

@overvenus Can we merge this? My another PR which needs to update kvproto seems to be blocked by this PR.


windows no such file or directory #72

The commit for issue #72 does not work.  my local change...replace getRalativePath (sic)
I changed path to fsPath and forced normalization of the path because the workspace folder path is normalilzed already.
Would somebody please try on *nix?
function getRalativePath(fullPath:string): string {
const root = vscode.workspace.workspaceFolders ? vscode.workspace.workspaceFolders[0].uri.fsPath : "" ;
//
// normalize fullPath before we try to look for common base(win32 needs this).
//
const nFullPath: vscode.Uri = vscode.Uri.file( fullPath ) ;
const relativePath =  path.resolve(nFullPath.fsPath).replace(root + path.sep, '');
return relativePath;

}

simpler change having the same effect, just resolve root as well:
const relativePath =  path.resolve(fullPath).replace( path.resolve(root) + path.sep, '');


jscs.info offline

Hey,
your documentation site jscs.info is offline. The domain is for sale.

@dasdany just a reminder: this project has merged with eslint

@bboydflo oh, thanks for reminder 👍

jscs merged with eslint


packagerConfig icon property that will work with both windows and osx

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description
Currently I have to change the packagerConfig.icon property manually depending on what platform I am building for.  osx requires a icns file and windows requires a .ico file.  It would
be nice if there were a solution to build against both platforms without having to manually alter the config file.
Proposed Solution
A config solution that will allow building either a mac or windows app without having to manually change the packagerConfig.icon property

Per the Packager icon documentation:

If the file extension is omitted, it is auto-completed to the correct extension based on the platform


m: Use EVFILT_USER instead of a self-pipe on kqueue where supported

Certain BSD platforms (macOS and FreeBSD) support an EVFILT_USER event on kqueue, which lets the user send arbitrary events to the queue to be dequeued. This PR adds a system that uses EVFILT_USER when available to notify the Poller instead of a self-pipe.
Draft because I need to test this on FreeBSD and NetBSD.

Verified that this works on FreeBSD and NetBSD, although tests fail on NetBSD because it does not support high precision mode.


fix(deps): update terraform terraform-ibm-modules/cos/ibm to v8.11.15

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cos/ibm (source)
module
patch
8.11.14 -> 8.11.15

Release Notes

terraform-ibm-modules/terraform-ibm-cos (terraform-ibm-modules/cos/ibm)
v8.11.15
Compare Source
Bug Fixes

deps: update terraform-module (#734) (4699c26)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.6.7 :tada:
The release is available on:

GitHub release
v1.6.7

Your semantic-release bot :package::rocket:


Can I send an input from web browser to Hololens2?

Hi,
I use Hololens2.
By using MixedReality-WebRTC, can I send any input(actually, I want to display a ball where user click with a mouse)??
If can, please tell me how to do so.

You can send anything that you can put in a browser's Media Track.
I'm not sure if there's a way to render web content directly into a video, but some browsers allow you to request Screen Capture (instead of a webcam) as the video source. Not the best, but might work for you.


add input

I wonder what will happen if there is added a input for 'hunger' ie. the longer after last apple, the hungrier the snake gets

huh
On Sat, Nov 12, 2022 at 9:14 AM Kenneth Due @.***>
wrote:

I wonder what will happen if there is added a input for 'hunger' ie. the
longer after last apple, the hungrier the snake gets
—
Reply to this email directly, view it on GitHub
https://github.com/greerviau/SnakeAI/issues/18, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWR5VPBSGPCM4MLOWZQ36Y3WH6X3TANCNFSM6AAAAAAR6LSTGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Bumped gemspec

Allow Capybara in any v3 version
Enforce addressable 2.5+ because ... that's 2 years old, and I'm not sure on the code being consumed in SP for it.
Bump minimum rubocop (Now it's fixed)

Just dotting the t's @ineverov

@luke-hill interested to see the capybara constraint loosened
but as a head-up,
it's a good idea to set a max for rubocop,
as they always add in new default cops,
eg. these tests are failing because they added a new cop Layout/EmptyLineAfterGuardClause
Currently in my main project I specify ~> 0.59.0 then there won't be any surprise failures when I bundle update

Yeh cheers for that. I think I'm going to revert it back to what it was. Because I've raised an issue on their tracker regarding the _memoized method.
For now having it at 0.58 is still reasonably good.

Yeah, I saw that one and thought it was funny.
Memoized variable @_load_validations does not match method name _load_validations. Use @_load_validations instead.

Thanks.


feat(guardrail): support calculating sample size by metric category

To help us get this pull request reviewed and merged quickly, please be sure to include the following items:

[ ] Tests (if applicable)
[ ] Documentation (if applicable)
[ ] A full explanation here in the PR description of the work done and statistical methods used

PR Type
What kind of change does this PR introduce?

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

Backward Compatibility
Is this change backward compatible with the most recently released version? Does it introduce changes which might change the user experience in any way? Does it alter the API in any way?

[ ] Yes (backward compatible)
[ ] No (breaking changes)

We don't want to let the calculator do adjustment by category


can't build using browserify

Hi,
I am using the "master" branch, because the "reactify" browserify-transform is specified in package.json.
But it looks like last commit (https://github.com/instructure-react/react-menu/commit/3a012ab81ceb687c6a734e03ee07a89d40071b2b) prevents from building using browserify: required files in lib/index.js can't be found (probably because of the .js to .jsx renaming).
@trungpham could you please have a look at this?
Thanks,

reverted the jsx extension stuff in https://github.com/instructure-react/react-menu/commit/07b01f531aa6e21d3feae38aa593daa147b28eb2 . browserify builds should be working

@knomedia thank you very much, it works correctly indeed!


Remove pointer events polyfill from examples

Maybe fixes #14703
I think it's now been long enough to wait for browsers without pointer events support to disappear.

I presume you did not intend to add the Circle example via this PR?

Thanks, @mike-000. This was indeed unintentional.


Row height not working

row.height does not affect anything.
Nothing changed in my code, but i can not set the row height.
let workbook = new Excel.Workbook()
let sheet = workbook.addWorksheet('Leckages')

sheet.columns = [
  {width: 40},
  {width: 30},
  {width: 10},
  {width: 25},
  {width: 10},
  {width: 10},
  {width: 10},
  {width: 10},
];

sheet.addRow(['a', 'b', 'c', 'd', 'e', 'f', 'g', 'h'])
sheet.addRow(['a', 'b', 'c', 'd', 'e', 'f', 'g', 'h'])
sheet.addRow(['a', 'b', 'c', 'd', 'e', 'f', 'g', 'h'])
sheet.getRow(1).height = 300

const savePath = app.getPath('documents');
const defaultDirectory = 'Test'
const absolutePathForReportStorage = path.resolve(path.join(savePath, defaultDirectory));
if (!fs.existsSync(absolutePathForReportStorage)) {
  fs.mkdir(absolutePathForReportStorage);
}
const currentTimestamp = Date.now()
const absolutePathForGeneratedXLS = path.join(absolutePathForReportStorage, `report-${currentTimestamp}.xlsx`)

workbook.xlsx.writeFile(absolutePathForGeneratedXLS).then(() => {

  shell.openItem(absolutePathForGeneratedXLS)
  resolve(true)
})

Any ideas?

I found something out:
When i pass styles for the row via row.styles = {...} then I can see them in row-xform.js when i debug the file. But the height attribute is always undefined at this place.

Still having issues with this.  Any update?


Feat: Multiple Selected Options and Context Integration

Related Issue
Fixes Issue : #969
Description
This pull request implements the multi-select functionality for filters and displays the selected filters in the URL. The changes include the following:
Added support for multi-selecting filter options.
Updated the URL query parameters to reflect the selected filters.
Added the FilterProvider component to incorporate the new functionality.
Added appropriate comments to explain the changes.
Screenshots

this branch has a conflicts error. Please resolve it

hey, @Rohan3011 ig you mistakenly removed a few codes. we added a new feature.
https://github.com/priyankarpal/ProjectsHut/assets/88102392/02a818d1-b5d5-4c0e-aa7d-1869ace3d317

this branch has a conflicts error. Please resolve it 😢


pretrained model

Hello, Could you please share the pretrained model and show how to test using a single image?
Thanks a lot for your reply!

Hello, Could you please share the pretrained model and show how to test using a single image?
Thanks a lot for your reply!

@SherlockHolmes221
I want to try to use a custom picture for testing but without success, have you solved this problem? Thanks for help

sorry, not solve


Fix windows compilation

Checklist

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

Some symbol were missing in the Windows shared library.
Apply patch including commits from:

https://gitlab.com/tango-controls/cppTango/-/merge_requests/924
https://gitlab.com/tango-controls/cppTango/-/merge_requests/944

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Changed pronouns for correctness and inclusivity (more than 2 genders)

This is a followup to #5730
'He or she' doesn't cover all genders.

I'm not sure if I should create another pull request on the main repo, or whether to proceed by this "pull request to the #5730". Can someone instruct me on the right protocol?


Make transferring body a compulsory argument when fetching series

This fixes an authorisation issue, where it was possible to fetch series for all departments by passing a null body parameter.
The only reason that body was an optional parameter was to support future admin functionality, but that does not exist yet so it's more secure to make the parameter compulsory are revisit this once we have requirements for the admin functions.
Also remove the admin token handling the same endpoint for the same reason.
Set as draft for now. The frontend needs to be updated to use https://github.com/nationalarchives/tdr-generated-graphql/pull/11 before this can be safely merged.

Rebased to fix the merge conflicts.
This can now be merged because the frontend is on the latest version of the GraphQL library.


Dropdown Fix

travis says:
WARNING - more than one element found for locator By.cssSelector(".inputcellmenu") - the first result will be used
Failures:

beaker landing page has a file menu with 4 items
Message:
Expected 0 to equal 4.

This is better now :+1:


problems combining generated manifests via .flux.yaml with raw manifests in repo

Describe the bug
I have a raw yaml workload in a repo, and it's running in the cluster started by flux. When I add a .flux.yaml file, and edit the raw yaml workload and commit that, flux correctly starts the templated manifest, but removes the previous raw manifest.
I have made a minimal repo https://github.com/alexhumphreys/flux-yaml-test to demonstrate. The commit https://github.com/alexhumphreys/flux-yaml-test/commit/1caaa6a5f19dba2328094e14d7962d4b46f54b4e adds a raw yaml workload that is a deployment named nginx-workload. The commit https://github.com/alexhumphreys/flux-yaml-test/commit/dd6d69f93b2e0819faf075164f6c96e926da5777 adds a .flux.yaml file which generates a deployment named nginx-template.
Flux is pretty new to me so there's a good chance I'm doing something pretty basic wrong, but any help would be appreciated.
To Reproduce
Steps to reproduce the behaviour:

go to https://github.com/alexhumphreys/flux-yaml-test/tree/1caaa6a5f19dba2328094e14d7962d4b46f54b4e
deploy that to your environment
go to https://github.com/alexhumphreys/flux-yaml-test/commit/dd6d69f93b2e0819faf075164f6c96e926da5777 (child commit of the previous 1caaa6a)
deploy that to your environment
observer that templated nginx appears, and the raw nginx workload is removed.

Expected behavior
I expected both nginx-template and nginx-workload to both remain after that dd6d69f is applied. The docs here have the line "Flux supports both generated manifests and raw manifests tracked in the same repository", so I would assume what I'm attempting should be possible.
Logs
{"caller":"main.go:224","ts":"2019-07-08T10:16:55.797222605Z","version":"1.13.1"}
{"caller":"main.go:316","msg":"using in cluster config to connect to the cluster","ts":"2019-07-08T10:16:55.797290029Z"}
{"caller":"main.go:395","component":"cluster","identity":"/var/fluxd/keygen/identity","ts":"2019-07-08T10:16:55.867183097Z"}
{"caller":"main.go:396","component":"cluster","identity.pub":"-----REDACTED-----","ts":"2019-07-08T10:16:55.86722387Z"}
{"caller":"main.go:401","host":"https://<IP_ADDRESS>:443","ts":"2019-07-08T10:16:55.867246425Z","version":"kubernetes-v1.13.5"}
{"caller":"main.go:413","kubectl":"/usr/local/bin/kubectl","ts":"2019-07-08T10:16:55.867286975Z"}
{"caller":"main.go:425","ping":true,"ts":"2019-07-08T10:16:55.867842005Z"}
{"caller":"main.go:558","email":"support@weave.works","notes-ref":"flux","set-author":false,"signing-key":"","sync-tag":"flux-sync","ts":"2019-07-08T10:16:55.86938521Z","url":"git@github.com:alexhumphreys/flux-yaml-test","user":"Weave Flux","verify-signatures":false}
{"caller":"main.go:619","ts":"2019-07-08T10:16:55.869450979Z","upstream":"no upstream URL given"}
{"caller":"loop.go:85","component":"sync-loop","err":"git repo not ready: git repo has not been cloned yet","ts":"2019-07-08T10:16:55.870853199Z"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:16:55.870920859Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:16:55.870945348Z"}
{"addr":":3030","caller":"main.go:640","ts":"2019-07-08T10:16:55.871516005Z"}
{"caller":"checkpoint.go:24","component":"checkpoint","latest":"1.13.1","msg":"up to date","ts":"2019-07-08T10:16:56.35147338Z"}
{"caller":"warming.go:198","component":"warmer","image":"memcached","info":"refreshing image","of_which_missing":72,"of_which_refresh":0,"tag_count":72,"to_update":72,"ts":"2019-07-08T10:16:57.073837225Z"}
{"attempted":72,"caller":"warming.go:206","component":"warmer","successful":72,"ts":"2019-07-08T10:16:58.110585929Z","updated":"memcached"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:16:58.110728576Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:16:58.11076126Z"}
{"caller":"warming.go:198","component":"warmer","image":"vault","info":"refreshing image","of_which_missing":51,"of_which_refresh":0,"tag_count":51,"to_update":51,"ts":"2019-07-08T10:16:58.830092877Z"}
{"attempted":51,"caller":"warming.go:206","component":"warmer","successful":51,"ts":"2019-07-08T10:16:59.582517498Z","updated":"vault"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:16:59.583779236Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:16:59.583856351Z"}
{"caller":"warming.go:198","component":"warmer","image":"gcr.io/google_containers/defaultbackend","info":"refreshing image","of_which_missing":5,"of_which_refresh":0,"tag_count":5,"to_update":5,"ts":"2019-07-08T10:17:00.281339039Z"}
{"attempted":5,"caller":"warming.go:206","component":"warmer","successful":5,"ts":"2019-07-08T10:17:01.163260052Z","updated":"gcr.io/google_containers/defaultbackend"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:17:01.163450888Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:17:01.163478411Z"}
{"caller":"warming.go:198","component":"warmer","image":"quay.io/kubernetes-ingress-controller/nginx-ingress-controller","info":"refreshing image","of_which_missing":53,"of_which_refresh":0,"tag_count":53,"to_update":53,"ts":"2019-07-08T10:17:04.69912131Z"}
{"attempted":53,"caller":"warming.go:206","component":"warmer","successful":53,"ts":"2019-07-08T10:17:05.334066946Z","updated":"quay.io/kubernetes-ingress-controller/nginx-ingress-controller"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:17:05.334316522Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:17:05.33435533Z"}
{"caller":"warming.go:198","component":"warmer","image":"gcr.io/kubernetes-helm/tiller","info":"refreshing image","of_which_missing":73,"of_which_refresh":0,"tag_count":73,"to_update":73,"ts":"2019-07-08T10:17:05.948637609Z"}
{"attempted":73,"caller":"warming.go:206","component":"warmer","successful":73,"ts":"2019-07-08T10:17:07.048638704Z","updated":"gcr.io/kubernetes-helm/tiller"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:17:07.048892127Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:17:07.048927305Z"}
{"caller":"warming.go:198","component":"warmer","image":"docker.io/weaveworks/weave-kube","info":"refreshing image","of_which_missing":378,"of_which_refresh":0,"tag_count":378,"to_update":378,"ts":"2019-07-08T10:17:07.801657753Z"}
{"attempted":378,"caller":"warming.go:206","component":"warmer","successful":378,"ts":"2019-07-08T10:17:10.542703951Z","updated":"docker.io/weaveworks/weave-kube"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:17:10.542946799Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:17:10.542981822Z"}
{"caller":"warming.go:198","component":"warmer","image":"docker.io/weaveworks/weave-npc","info":"refreshing image","of_which_missing":360,"of_which_refresh":0,"tag_count":360,"to_update":360,"ts":"2019-07-08T10:17:11.241032248Z"}
{"attempted":360,"caller":"warming.go:206","component":"warmer","successful":360,"ts":"2019-07-08T10:17:13.892936094Z","updated":"docker.io/weaveworks/weave-npc"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:17:13.893182405Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:17:13.89322312Z"}
{"caller":"warming.go:198","component":"warmer","image":"docker.io/weaveworks/flux","info":"refreshing image","of_which_missing":33,"of_which_refresh":0,"tag_count":33,"to_update":33,"ts":"2019-07-08T10:17:14.529466743Z"}
{"attempted":33,"caller":"warming.go:206","component":"warmer","successful":33,"ts":"2019-07-08T10:17:15.226749091Z","updated":"docker.io/weaveworks/flux"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:17:15.226985318Z"}
{"caller":"images.go:28","component":"sync-loop","msg":"no automated workloads","ts":"2019-07-08T10:17:15.227018979Z"}
{"caller":"loop.go:85","component":"sync-loop","err":"git repo not ready: git clone --mirror: fatal: Could not read from remote repository., full output:\n Cloning into bare repository<EMAIL_ADDRESS>Permission denied (publickey).\r\nfatal: Could not read from remote repository.\n\nPlease make sure you have the correct access rights\nand the repository exists.\n","ts":"2019-07-08T10:18:55.871120895Z"}
{"HEAD":"1caaa6a5f19dba2328094e14d7962d4b46f54b4e","branch":"master","caller":"loop.go:111","component":"sync-loop","event":"refreshed","ts":"2019-07-08T10:19:08.795991056Z","url":"git@github.com:alexhumphreys/flux-yaml-test"}
{"args":"","caller":"sync.go:480","cmd":"apply","count":1,"method":"Sync","ts":"2019-07-08T10:19:10.785076202Z"}
{"caller":"sync.go:546","cmd":"kubectl apply -f -","err":null,"method":"Sync","output":"deployment.apps/nginx-workload created","took":"330.090451ms","ts":"2019-07-08T10:19:11.115310698Z"}
{"caller":"loop.go:206","component":"sync-loop","new":"1caaa6a5f19dba2328094e14d7962d4b46f54b4e","old":"fb32e8ba67166977830f6ed501db64382b91ac9e","tag":"flux-sync","ts":"2019-07-08T10:19:17.868297451Z"}
{"HEAD":"1caaa6a5f19dba2328094e14d7962d4b46f54b4e","branch":"master","caller":"loop.go:111","component":"sync-loop","event":"refreshed","ts":"2019-07-08T10:19:18.984485343Z","url":"git@github.com:alexhumphreys/flux-yaml-test"}
{"caller":"warming.go:198","component":"warmer","image":"nginx","info":"refreshing image","of_which_missing":245,"of_which_refresh":0,"tag_count":245,"to_update":245,"ts":"2019-07-08T10:19:56.703110498Z"}
{"attempted":245,"caller":"warming.go:206","component":"warmer","successful":245,"ts":"2019-07-08T10:20:00.313421213Z","updated":"nginx"}
{"caller":"images.go:18","component":"sync-loop","msg":"polling images","ts":"2019-07-08T10:20:00.313684555Z"}
{"caller":"images.go:112","component":"sync-loop","container":"nginx-workload","current":"nginx:1.16.0","info":"added update to automation run","new":"nginx:1-alpine-perl","pattern":"glob:*","reason":"latest 1-alpine-perl (2019-07-01 21:26:42.594359557 +0000 UTC) \u003e current 1.16.0 (2019-06-11 00:04:48.728051038 +0000 UTC)","repo":"nginx","ts":"2019-07-08T10:20:00.351570357Z","workload":"default:deployment/nginx-workload"}
{"caller":"loop.go:119","component":"sync-loop","jobID":"9adf1535-c680-ab5f-6ea0-f1a4c81b8843","state":"in-progress","ts":"2019-07-08T10:20:00.35168049Z"}
{"caller":"releaser.go:59","component":"sync-loop","jobID":"9adf1535-c680-ab5f-6ea0-f1a4c81b8843","ts":"2019-07-08T10:20:00.377868829Z","type":"release","updates":1}
{"caller":"loop.go:129","component":"sync-loop","err":{"type":"user","help":"Problem committing and pushing to git repository.\n\nThere was a problem with committing changes and pushing to the git\nrepository.\n\nIf this has worked before, it most likely means a fast-forward push\nwas not possible. It is safe to try again.\n\nIf it has not worked before, this probably means that the repository\nexists but the SSH (deploy) key provided doesn't have write\npermission.\n\nIn GitHub, please check via the repository settings that the deploy\nkey is \"Read/write\". You can cross-check the fingerprint with that\ngiven by\n\n    fluxctl identity\n\nIf the key is present but read-only, you will need to delete it and\ncreate a new deploy key. To create a new one, use\n\n    fluxctl identity --regenerate\n\nThe public key this outputs can then be given to GitHub; make sure you\ncheck the box to allow write access.\n\n","error":"git push git@github.com:alexhumphreys/flux-yaml-test [master refs/notes/flux]: failed to push some refs to 'git@github.com:alexhumphreys/flux-yaml-test', full output:\n To github.com:alexhumphreys/flux-yaml-test\n   649425b..2438569  refs/notes/flux -\u003e refs/notes/flux\n ! [rejected]        master -\u003e master (fetch first)\nerror: failed to push some refs to 'git@github.com:alexhumphreys/flux-yaml-test'\nhint: Updates were rejected because the remote contains work that you do\nhint: not have locally. This is usually caused by another repository pushing\nhint: to the same ref. You may want to first integrate the remote changes\nhint: (e.g., 'git pull ...') before pushing again.\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\n"},"jobID":"9adf1535-c680-ab5f-6ea0-f1a4c81b8843","state":"done","success":"false","ts":"2019-07-08T10:20:04.229398468Z"}
{"HEAD":"dd6d69f93b2e0819faf075164f6c96e926da5777","branch":"master","caller":"loop.go:111","component":"sync-loop","event":"refreshed","ts":"2019-07-08T10:20:07.97022118Z","url":"git@github.com:alexhumphreys/flux-yaml-test"}
{"args":"","caller":"sync.go:480","cmd":"apply","count":1,"method":"Sync","ts":"2019-07-08T10:20:09.941963206Z"}
{"caller":"sync.go:546","cmd":"kubectl apply -f -","err":null,"method":"Sync","output":"deployment.apps/nginx-template created","took":"151.313709ms","ts":"2019-07-08T10:20:10.093344664Z"}
{"caller":"sync.go:149","dry-run":false,"info":"cluster resource not in resources to be synced; deleting","resource":"default:deployment/nginx-workload","ts":"2019-07-08T10:20:13.881471326Z"}
{"args":"","caller":"sync.go:480","cmd":"delete","count":1,"method":"Sync","ts":"2019-07-08T10:20:13.88153072Z"}
{"caller":"sync.go:546","cmd":"kubectl delete -f -","err":null,"method":"Sync","output":"deployment.apps \"nginx-workload\" deleted","took":"71.114982ms","ts":"2019-07-08T10:20:13.952686315Z"}
{"caller":"daemon.go:652","component":"daemon","event":"Sync: dd6d69f, default:deployment/nginx-template","logupstream":"false","ts":"2019-07-08T10:20:13.955543471Z"}
{"caller":"loop.go:206","component":"sync-loop","new":"dd6d69f93b2e0819faf075164f6c96e926da5777","old":"1caaa6a5f19dba2328094e14d7962d4b46f54b4e","tag":"flux-sync","ts":"2019-07-08T10:20:17.05171854Z"}
{"HEAD":"dd6d69f93b2e0819faf075164f6c96e926da5777","branch":"master","caller":"loop.go:111","component":"sync-loop","event":"refreshed","ts":"2019-07-08T10:20:18.169072078Z","url":"git@github.com:alexhumphreys/flux-yaml-test"}
{"HEAD":"dd6d69f93b2e0819faf075164f6c96e926da5777","branch":"master","caller":"loop.go:111","component":"sync-loop","event":"refreshed","ts":"2019-07-08T10:22:09.169909711Z","url":"git@github.com:alexhumphreys/flux-yaml-test"}
{"args":"","caller":"sync.go:480","cmd":"apply","count":1,"method":"Sync","ts":"2019-07-08T10:22:20.138582227Z"}
{"caller":"sync.go:546","cmd":"kubectl apply -f -","err":null,"method":"Sync","output":"deployment.apps/nginx-template unchanged","took":"147.36829ms","ts":"2019-07-08T10:22:20.286009484Z"}

There is an error in that pile:
{"caller":"loop.go:129","component":"sync-loop","err":{"type":"user","help":"Problem committing and pushing to git repository.\n\nThere was a problem with committing changes and pushing to the git\nrepository.\n\nIf this has worked before, it most likely means a fast-forward push\nwas not possible. It is safe to try again.\n\nIf it has not worked before, this probably means that the repository\nexists but the SSH (deploy) key provided doesn't have write\npermission.\n\nIn GitHub, please check via the repository settings that the deploy\nkey is \"Read/write\". You can cross-check the fingerprint with that\ngiven by\n\n    fluxctl identity\n\nIf the key is present but read-only, you will need to delete it and\ncreate a new deploy key. To create a new one, use\n\n    fluxctl identity --regenerate\n\nThe public key this outputs can then be given to GitHub; make sure you\ncheck the box to allow write access.\n\n","error":"git push git@github.com:alexhumphreys/flux-yaml-test [master refs/notes/flux]: failed to push some refs to 'git@github.com:alexhumphreys/flux-yaml-test', full output:\n To github.com:alexhumphreys/flux-yaml-test\n   649425b..2438569  refs/notes/flux -\u003e refs/notes/flux\n ! [rejected]        master -\u003e master (fetch first)\nerror: failed to push some refs to 'git@github.com:alexhumphreys/flux-yaml-test'\nhint: Updates were rejected because the remote contains work that you do\nhint: not have locally. This is usually caused by another repository pushing\nhint: to the same ref. You may want to first integrate the remote changes\nhint: (e.g., 'git pull ...') before pushing again.\nhint: See the 'Note about fast-forwards' in 'git push --help' for details.\n"},"jobID":"9adf1535-c680-ab5f-6ea0-f1a4c81b8843","state":"done","success":"false","ts":"2019-07-08T10:20:04.229398468Z"}

I did the double check it recommended, and the fluxctl identity fingerprint matches the deploy key on github, and has read/write access.
Additional context

flux version docker.io/weaveworks/flux:1.13.1
Helm Operator version: not using helm operator
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Git provider: github
dockerhub, nginx official image.
that template command I'm using is pretty goofy, just cating a text file, but it was the simplest i could think of to make a failing case. But I did run into a similar issue using the more complicated .flux.yaml here https://github.com/alexhumphreys/flux-test-drive/blob/master/.flux.yaml

Thank you for the great bug report!
From looking at your example repo, I think the problem is that fluxd defaults to examining one path (./) in the repo, and the .flux.yaml there is taken as defining the whole of the configuration -- fluxd will assume the only thing it needs to do is run what's in it.
To mix raw config and generated config, you'll need to provide two paths, one with the .flux.yaml and one containing the raw YAMLs. So you might have
-+ templates
 +-- .flux.yaml
 `-- nginx.txt
-+ workloads
 +-- nginx.yaml

then supply --git-path=templates,workloads as an argument to fluxd.
It sounds like the docs were not very clear on this point, so I'll have a look and see if they can be improved.

Thanks for your fast reply! Just tested out moving the .flux.yaml and the --git-path flag and it did the trick, thanks!
Just testing there so I understand the director structure, it seems when you pass --git-path=templates,workloads the following raw yaml workload files will/won't be found and deployed by flux:
project-root
│   not-found-raw.yaml
│
└───template
│   │   .flux.yaml
│   │   nginx.txt
│   └───subfolder1
│       │   not-found-raw.yaml
│
└───workloads
│   │   found-raw.yaml
│   └───subfolder2
│       │   found-raw.yaml

Yes that's correct. The algorithm is basically this:

for each --git-path

if .flux.yaml exists then follow what it says there and ignore any other files
if no .flux.yaml then look for YAML files here and below (except for directories that look like Helm charts)

Ah, good to know, thanks! I'll close this issue so.
Also, thanks for your work on flux, it's got some great ideas, hopefully we can add it to our stack and simplify a bunch of stuff :+1:


feat: formalizing point-visiting strategies

adds

useq.TraversalOrder - to dictate how random points are traversed
addes a nearest neighbor and  2-opt algorithm, (for slightly better path choosing)
allows you to specify the starting index
adds plotting to all points plans:

import useq

pp = useq.RandomPoints(
    num_points=100,
    max_height=6000,
    max_width=6000,
    order=useq.TraversalOrder.TWO_OPT,
    random_seed=1,
    shape="rectangle",
    start_at=10,
    fov_height=300,
    fov_width=300,
    allow_overlap=False,
)
pp.plot()

two-opt:

nearest neighbor:

this is going to temporarily break one of the new point plan selectors in pymmcore-widgets, because requires a max_width > 0


[Bug] Flaky test: chained_bft::chained_bft_smr_test::reconfiguration_test

🐛 Bug
This test seems to be flaky. It failed on CI when I submitted my PR (#1978), but a subsequent bors-libra run was successful. Here's the log:
https://circleci.com/gh/libra/libra/22164#tests/containers/2
test chained_bft::chained_bft_smr_test::secondary_proposers ... ok
test chained_bft::chained_bft_smr_test::aggregate_timeout_votes ... ok
test chained_bft::chained_bft_smr_test::chain_with_nil_blocks ... ok
test chained_bft::chained_bft_smr_test::reconfiguration_test ... test chained_bft::chained_bft_smr_test::reconfiguration_test has been running for over 60 seconds

Too long with no output (exceeded 10m0s): context deadline exceeded

To reproduce
Not sure if this can be easily reproduced.
Expected Behavior
Test should pass.

This happened again recently - https://circleci.com/gh/libra/libra/24207#tests/containers/2


Add "random tiles" checkbox

When selecting multiple tiles from a tileset, it would be nice to be able to "randomize" which tile gets placed when using any of the tile-placing tools.

This feature already exists! You can randomize tiles by holding Ctrl as you draw. 🙂 In the docs: https://ogmo-editor-3.github.io/docs/#/manual/tile-layers.md

Oh! Cool. Totally missed that! Maybe this can be made more clear in the UI somewhere? Just my 2 cents. 👍


How to interpret the ID?

safety version: 1.10.3
Python version: 3.7.13
Operating System:

Description
Maybe I'm really stupid, but I cannot make sense of the "ID" that the safety check command delivers. I looked on the safety webpage, here on github, nothing really how to make sense of it? Outputting a link would be nice ;-) What I do now, is just google the package name with the word "cve" ...not ideal. Any pointers greatly appreciated!
+==============================================================================+
| REPORT                                                                       |
| checked 81 packages, using free DB (updated once a month)                    |
+============================+===========+==========================+==========+
| package                    | installed | affected                 | ID       |
+============================+===========+==========================+==========+
| djangorestframework        | 3.9.4     | <3.12.0                  | 38841    |
| numpy                      | 1.19.5    | <1.21.0rc1               | 43453    |
| numpy                      | 1.19.5    | <1.22.0                  | 44717    |
| numpy                      | 1.19.5    | <1.22.0                  | 44716    |
| numpy                      | 1.19.5    | <1.22.2                  | 44715    |
+==============================================================================+

What I Did
safety check

Hi benzkji,
Please try safety check --full-report
Tristan

Thank you! This helps alot.
Just curios, is the ID an internal https://pyup.io/ id?


Page not fully loaded after call to visit when using phantomjs 2.0.0

Hi!
Great work on poltergeist!  It is of great benefit to our development and testing, every day :smile:
We tried an upgrade to phantomjs 2.0.0 the other day, and ran into some trouble.  The most important one is a difference in timing.  It seems a call to visit waits until the page is fully loaded when using phantomjs 1.9.8, but returns before images are loaded when using phantomjs 2.0.0.
The effect is that screen shots taken after a call to visit include images when using 1.9.8, but can be without images when using 2.0.0.
Another effect is that a test will finish before all images are loaded in pages loaded by the test, leaving requests running on the server while DatabaseCleaner cleans and fixtures are being loaded.  This results in database errors and failing tests.
Is there a way to ensure pages are fully loaded before continuing after a call to visit when using phantomjs 2.0.0?

Anybody able to reproduce this?

This error is consistent for us with phantomjs 2.0.0.  Anybody else able to reproduce it?

visit waits for phantomjs to fire its onLoadFinished event (unless it was only a hash change to the url)-- That event is described here - http://phantomjs.org/api/webpage/handler/on-load-finished.html  -  you may be better off checking at phantomjs what exactly "finished loading" means, or producing a test case for the behavior you believe is wrong, rather than repeatedly asking if anyone else can reproduce it.

Hi @twalpole !
Thanks for the response.  It usually pays off checking if it is a known problem before putting in lots of work for a test case.  Also getting a second reproduction helps deciding if it is a local problem on my system.
I felt waiting two months before asking again when there has been no response at all was not nagging.  My mistake.
I'll check with phantomjs and see if I can produce an automated test case for it.
My current test case is based on manual inspection of any screenshot taken directly after visit has returned.

One guess here would be you're using a polyfill for responsive images that is running in phantom 2 but not in 1.9.x because it's WebKit engine is so old. That would leave asynchronous image requests that onLoad would fire before completion.  If that is what's happening you may be out of luck and just have to put a delay before taking screenshots (or disable the polyfill when testing)

@twalpole Thank you so much for the tip.  I will look into it and report back.

Solved it!  It was actually not visit that was the subject but click_link.  My test called click_link on a JavaScript enabled link (via TurboLinks) that did an ajax call that resulted in a DOM manipulation that triggered new images to be loaded, and these images are slow to load.
I now use this method to ensure images are loaded before I take a screen shot:
  IMAGE_WAIT_SCRIPT = <<EOF
function pending_image() {
  var images = document.images;
  for (var i = 0; i < images.length; i++) {
    if (!images[i].complete) {
        return images[i].src;
    }
  }
  return false;
}()
EOF

  def assert_images_loaded
    start = Time.now
    loop do
      pending_image = evaluate_script IMAGE_WAIT_SCRIPT
      break unless pending_image
      assert (Time.now - start) > Capybara.default_max_wait_time
      sleep 0.1
    end
  end

Thanks again @twalpole for you guidance.


IGNITE-12261 Issue with adding nested index dynamically

This will ensure we are using fullName instead of lastAttribute in nested attribute
Ex: Address.street
With out this fix, field name will be street
with this fix, field name will be Address.street. It will help when we query from other node

https://github.com/apache/ignite/pull/7016
Created another PR with all the changes at one place. Hence closing this

https://github.com/apache/ignite/pull/7016
Created another PR with all the changes at one place. Hence closing this


"Sângeru" , "Butuci", "Mireșu Mare", "Mireșu Mic", "Piatra Mică" and "Tisa" villages are listed in the drop-down menu

The villages are listed in the drop-down menu alongside its corresponding county and commune, according to the law
Preconditions : the website (https://peviitor-ro.github.io/ui.orase/) is up and runing. After every step delete the text you typed from the search bar.

Step 1
Type "Sângeru" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Sângeru, PRAHOVA (Sângeru)".

Step 2
Type "Butuci" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Butuci, PRAHOVA (Sângeru)".

Step 3
Type "Mireșu Mare" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Mireșu Mare, PRAHOVA (Sângeru)".

Step 4
Type "Mireșu Mic" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Mireșu Mic, PRAHOVA (Sângeru)".

*Step 5
Type "Piatra Mică" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sat Piatra Mică, PRAHOVA (Sângeru)".


Improve subBatchPerPartition

Re-seek the entire remaining sub-batches after an abort, not just the current sub-batch.

Closing as invalid - this is not necessary since the remaining sub-batches are unrelated to the failed sub batch and should be processed without re-polling.


Correct loading of models with shared tensors when using accelerator.load_state()

What does this PR do?
I would run into problems with PyTorch's load_state_dict complaining about missing keys. These keys belonged to shared tensors. These shared keys are intentionally omitted by the safetensors library. To load a model correctly, one has to use safetensor's load_model function instead of the default load_state_dict function (described here). This was previously not done when using the load_state function of the Accelerator.
Fixes # (issue)
I think this issue might be relevant as they also report problems when loading with accelerator.load_state.
https://github.com/huggingface/accelerate/issues/2155
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

Core parts of the library: @muellerzr @BenjaminBossan @SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Yes, I'll have a look into it.

You can verify that the shared weights are implemented correctly by checking the output. safetensors warns you about that fact.

Just did. This is the expected error message I get when reverting my changes.

Just did. This is the expected error message I get when reverting my changes.

I was only expecting linear2.weight and linear2.bias to be missing. Maybe this is due to
self.weight = self.linear1.weight
self.bias = self.linear1.bias

Just did. This is the expected error message I get when reverting my changes.

I was only expecting linear2.weight and linear2.bias to be missing. Maybe this is due to
self.weight = self.linear1.weight
self.bias = self.linear1.bias

After removing the unnecessary bits, it correctly only throws an error for the weights and bias of the 2nd linear layer.

Nice ! Could you just fix the quality issue (make style) and we are good to merge !


Validate the combination of CloudCompute and BuildConfig

What does this PR do?
Fixes https://github.com/Lightning-AI/lightning/issues/14278
Goes alongside #14125, or closes it depending on what we prefer.
I'll take over #14125 if needed.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
I made sure I had fun coding 🙃
cc @borda

Apologies, I completely forgot that this was still open!


Update to v9

Any updates?

Any updates?

Working on it. In the meantime the current version still works without issues.

an experimental version using the v9 gateway version is now available in the v13 branch (which is based on the master branch of discord.js).


il2cpp.perform not being called

I am using memu emulator.
The Code:
console.log("Frida loaded succesfully !");
      Connected to ASUS I005DA (id=<IP_ADDRESS>:21503)
Spawning com.zads.android...
Frida loaded succesfully !
Spawned com.zads.android. Resuming main thread!
[ASUS I005DA::com.zads.android ]->

Follow #355

@vfsfitvnm For some reason perform is not called, specifically on the first start when il2cpp has not been called and intercept is not working.  I patched it temporarily by waiting for il2cpp, you can take a look at this case.
Device: xiaomi mi a2
Android verision: 8.1
Rom link: https://mifirm.net/model/jasmine.ttt#global
V<IP_ADDRESS>.ODIMIFE
https://github.com/vfsfitvnm/frida-il2cpp-bridge/blob/e97fb50ecd8e3e44e5fade24d816809e15325842/src/utils/native-wait.ts#L65

@thinhbuzz  Are you using frida-gadget or a emulated environment?

@vfsfitvnm no, i got that error on xiaomi mi a2 device (rooted), start by command:
frida -Uf package.name.com -l _.js --runtime=v8

Unfortunately I cannot debug it. It looks like a rom/device/vendor specific issue, my take is the library is being loaded by a export I am not aware of. If you are able to pinpoint and solve the issue, please let me know

Here's how I fixed it link
It seems to happen on Android 8.1 and lower I can replicate it on my device but I haven't looked on how it could be fixed.

@Flechaa Thanks. Perhaps I could implement a busy-waiting version of native-wait.ts.
However, if it's Android specific, I can definitely try to reproduce on the official android emulator; it's just hard to find a x86 Unity game

Indeed it really looks like Android specific, I have tried on a Huawei device running Android 7, @thinhbuzz has the same problem on a Xiaomi device and one of my friends tried it on a Samsung S7 (Android 8) and the same problem also occurs.


Using tilde does not resolve path in data-src

Hello,
I'm using .NET Core SDK 1.0.0-preview2-003131, NETCoreApp 1.0.1,  Microsoft.AspNetCore.Razor.Tools 1.0.0-preview2-final.
I have the following markup in my view:
<img src="~/style/images/logo.png" alt="" data-src="~/style/images/logo.png"  />
Data-src is not being resolved by the Razor engine, only src. Is this by design or an issue in this version?
Thanks,
Daniel

/cc @NTaylorMullen
I believe the answer is that we leave everything in a data- attribute alone. If you want a workaround, use data-src="@Url.Content("~/...")"

I believe the answer is that we leave everything in a data- attribute alone

Yup, 100% correct.

Closing since this has been answered


An Example App.

Hi,
Is there an sample/tutorial app that can be used to see this pattern in action?
I have used RIBs in the past, but with only UIKit, moving to swift-ui the whole navigation paradigm has changed.

Hi, thank you for taking a look at my template :D
I'll put aside some time to add a sample project for this soon that includes an example of how to handle sub-routes as well.
Just an example of its practicality, I've built this app using this architecture: https://apps.apple.com/us/app/pixquare-pixel-art/id1659428179
From my experience, RIB really shines over other architecture when the screen's composition is complex and broken down into multiple children RIBs.
I'll update here again once the sample is ready


PlatformDispatcher.accessibilityFeatures complete with properties for 'Button Shapes' and 'On/Off Labels'

Hi,
I use the PlatformDispatcher to query some accessibility features at app startup. I noticed that there is currently no possibility to query the iOS specific settings 'Button Shapes' and 'On/Off Labels'. Could the AccessibilityFeatures of the PlatformDispatcher be extended by these two options?
Thank you very much and best regards

@chunhtai any thoughts about this?

Yes this is possible since iOS does provide the API to query this data, we can hook them to the AccessibilityFeatures
https://developer.apple.com/documentation/uikit/3618943-uiaccessibilitybuttonshapesenabl?language=objc
https://developer.apple.com/documentation/uikit/3131973-uiaccessibilityisonoffswitchlabe?language=objc


Lock Unspent Wallet Feature

The lock unspent feature does not save when you close out of the zcoin wallet.

Duplicate of #332
This is a limitation from Bitcoin Core


False negative in 942230

Describe the bug
This is the regularity of 942230:
(?i:[\s()]case\s+when.*?then|\)\s*?like\s*?\(|select.*?having\s*?[^\s]+\s*?[^\w\s]|if\s?\([\d\w]\s*?[=<>~])

It can be split into four independent rules:
1: (?i:[\s()]case\s+when.*?then)
2: (?i:\)\s*?like\s*?\()
3: (?i:select.*?having\s*?[^\s]+\s*?[^\w\s])
4: (?i:if\s?\([\d\w]\s*?[=<>~])

My question is that there may be a risk of missing the attack on the fourth rule.
Below are two payloads of the same type:
1: if(1=2, -1, 2) union select table_name from information_schema.tables limit 1
2: IF(7423=7424) SELECT 7423 ELSE DROP FUNCTION xcjl--

You can check the test in https://regex101.com/r/h9Vz4I/2, the regular rule only hits the first payload, but not the second payload.
So my suggestion for modification is：
(?i:if\s?\([\w]+\s*?[=<>~])

Remove \d, because \w already contains it.
The modification effect can be viewed https://regex101.com/r/k0G4Ux/1/

Steps to reproduce

Expected behaviour

Actual behaviour

Additional context

Your Environment
CRS version v3.4/dev

CRS version (e.g., v3.2.0):
Paranoia level setting:
ModSecurity version (e.g., 2.9.3):
Web Server and version (e.g., apache 2.4.41):
Operating System and version:

I am just peering through this issue, but in MySQL, the syntax for the CASE operator is different. The example would be correct as:
mysql> select case when 1=1 then 1 else 2 end;
+---------------------------------+
| case when 1=1 then 1 else 2 end |
+---------------------------------+
|                               1 |
+---------------------------------+

However, I don't know how other SQL dialects allow CASE.

@NiceYouKnow are you still interested in this? Could you respond to @lifeforms' question?

I am just peering through this issue, but in MySQL, the syntax for the CASE operator is different. The example would be correct as:
mysql> select case when 1=1 then 1 else 2 end;
+---------------------------------+
| case when 1=1 then 1 else 2 end |
+---------------------------------+
|                               1 |
+---------------------------------+

However, I don't know how other SQL dialects allow this. What servers accept your notation?

Your example is correct, no problem. But my question is about (?i:if\s?\([\d\w]\s*?[=<>~]).

Nice catch @NiceYouKnow. The exact query syntax isn't relevant. The issue is that by the rule could be circumvented by using a number > 9 in the comparison.
I've moved the four statements into a new regex data file.
I also adjusted the fourth rule to fix the false negative (test included) and removed the unnecessary character class still left in the original suggestion ([\w]).

Closing this in favor of #2348. Thank you for reporting @NiceYouKnow and for providing a PR @theseion.


Updated broken C# link

The link for "Data Structures and Algorithms with Object-Oriented Design Patterns" under C# was broken. I updated it so it goes to the correct pdf file.

It looks like the author, Bruno Preiss, passed away over a year ago, which is why the domain disappeared. Linking to the wayback machine is probably the best way to go.

Wayback machine working link (for C# version) is https://web.archive.org/web/20161220072449/http://www.brpreiss.com/books/opus6/, so prefixing it with https://web.archive.org/web/20161220072449/ would work for the other versions (Java, etc.).

Thanks @tedyoung Wayback machine links are appropriate here.

Thank you @tedyoung @JamieDawson @rautamiekka
PRs for the other brpeiss books appreciated- need to verify that they are in Wayback machine.


Gradle Build error: versionCode not found. Define flutter.versionCode in the local.properties file.

I've deleted the android and build folders and run flutter create . and I'm still getting this error.
FAILURE: Build failed with an exception.

* Where:
Build file 'mydir/android/app/build.gradle' line: 16

* What went wrong:
A problem occurred evaluating project ':app'.
versionCode not found. Define flutter.versionCode in the local.properties file.

And then after adding a versionCode, I get the following error:
* What went wrong:
A problem occurred evaluating project ':app'.
> versionName not found. Define flutter.versionName in the local.properties file.

Flutter Doctor:
[✓] Flutter (Channel beta, v0.5.6-pre.105, on Mac OS X 10.14 18A314k, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK 28.0.0-rc1)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[✓] IntelliJ IDEA Ultimate Edition (version 2018.1.5)
[✓] VS Code (version 1.24.1)
[✓] Connected devices (2 available)

android/app/build.gradle
def localProperties = new Properties()
def localPropertiesFile = rootProject.file('local.properties')
if (localPropertiesFile.exists()) {
    localPropertiesFile.withReader('UTF-8') { reader ->
        localProperties.load(reader)
    }
}

def flutterRoot = localProperties.getProperty('flutter.sdk')
if (flutterRoot == null) {
    throw new GradleException("Flutter SDK not found. Define location with flutter.sdk in the local.properties file.")
}

def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    throw new GradleException("versionCode not found. Define flutter.versionCode in the local.properties file.")
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
   /throw new GradleException("versionName not found. Define flutter.versionName in the local.properties file.")
}

apply plugin: 'com.android.application'
apply from: "$flutterRoot/packages/flutter_tools/gradle/flutter.gradle"

android {
    compileSdkVersion 27

    lintOptions {
        disable 'InvalidPackage'
    }

    defaultConfig {
        // TODO: Specify your own unique Application ID (https://developer.android.com/studio/build/application-id.html).
        applicationId "com.thinkdigitalrepair.livekhflutter"
        minSdkVersion 16
        targetSdkVersion 27
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            // TODO: Add your own signing config for the release build.
            // Signing with the debug keys for now, so `flutter run --release` works.
            signingConfig signingConfigs.debug
        }
    }
}

flutter {
    source '../..'
}

dependencies {
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'
}

Please add the output of flutter doctor
and of android/app/build.gradle

You want the content of build.gradle? Coming up
On Sun, Jul 1, 2018, 11:06 PM Günter Zöchbauer<EMAIL_ADDRESS>wrote:

Please add the output of flutter doctor
and of android/app/build.gradle
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/18983#issuecomment-401681145,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV-HfSY0iWdNn6VfuOg7GGFu0g9Cv_hHks5uCbhXgaJpZM4U-ksc
.

Looks like the problem is in android/local.properties
Try adding the line flutter.versionCode=1

The thing is, this file was built by flutter. If I commit my code, it will
have to be rebuilt again causing the same error, right? I did try a 1 there
and then I got the second error
On Mon, Jul 2, 2018, 8:39 AM Günter Zöchbauer<EMAIL_ADDRESS>wrote:

Looks like the problem is in android/local.properties
Try adding the line flutter.versionCode=1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/18983#issuecomment-401846408,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV-HfWYzUA0UjTG7U_sRoTH6BOSCTFLIks5uCj7DgaJpZM4U-ksc
.

I see.
Is this all in the project created with flutter create . or is this in an existing project where you copied files from the newly created project?
The long-time project I'm working with these files look a bit different then a newly created project.
The old project doesn't contain flutter.versionCode and flutterVersionName and also the reference in build.gradle looks different.
If this is in an existing project, you probably need to add all settings it complains about.

It was created with flutter create .. The file you see was fresh, since I
deleted the entire build and android folder and re-ran create to make sure
it wasn't a fluke
On Mon, Jul 2, 2018, 8:53 AM Günter Zöchbauer<EMAIL_ADDRESS>wrote:

I see.
Is this all in the project created with flutter create . or is this in an
existing project where you copied files from the newly created project?
The long-time project I'm working with these files look a bit different
then a newly created project.
The old project doesn't contain flutter.versionCode and flutterVersionName
and also the reference in build.gradle looks different.
If this is in an existing project, you probably need to add all settings
it complains about.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/18983#issuecomment-401850582,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AV-HfdnX7T_wCKewkoakniE_yarpvETNks5uCkIQgaJpZM4U-ksc
.

I faced this I today with a project that I created on my other machine which may have an older Android Studio installed. A newly on this machine created project builds without problems

Currently Flutter does not update files from existing projects when templates for flutter create change. This needs to be done manually. Just create a new project with flutter create . and compare the config files and adjust them to match the files in the new project with the changes manually added to the old project.

That is the strange thing. After adding
flutter.versionCode=1
flutter.versionName=1.0

To the failing project it builds on the new machine. Although it ran without problems on the old machine. Which I don't understand because the gradle file tests for this values on my old machine too.

Perhaps flutter clean or deleting android/.gradle results to the same result as moving to a clean machine. Perhaps there are other files that are retained.
The android/.gitignore is a list of files and directories that are not supposed to be checked in because they are re-generated.

it seems like a strange combination. The problematic file was created on channel master and has gradle 4.4 and builds on my desktop without problems. The Laptop here I set to beta. Perhaps that cause the problem. Although I still wondering how it could build on my desktop without the properties set. I created it new this morning.

Just had this error, I fixed it by adding:
flutter.versionName=1.0.0
flutter.versionCode=1
flutter.buildMode=debug

to the local.properties file. Hope this helps someone!

The problem here is what I think is a bug in the flutter create templates. In the build.gradle files they create, they have these stanzas:
def flutterVersionCode = localProperties.getProperty('flutter.versionCode')
if (flutterVersionCode == null) {
    throw new GradleException("versionCode not found. Define flutter.versionCode in the local.properties file.")
}

def flutterVersionName = localProperties.getProperty('flutter.versionName')
if (flutterVersionName == null) {
    throw new GradleException("versionName not found. Define flutter.versionName in the local.properties file.")
}

The thing is, the local.properties file contains local paths, and so it shouldn't be checked in (it's in the .gitignore file for this reason), so we're kind of putting developers in an untenable situation: you have to edit local.properties, but you can't check it in.
The workaround for this is to change the lines in your build.gradle from something like this:
android {
    compileSdkVersion 27

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 27
        versionCode flutterVersionCode.toInteger()
        versionName flutterVersionName
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
}

to this:
android {
    compileSdkVersion 27

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 27
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"
    }
}

and remove the flutterVersionCode and flutterVersionName stanzas.
The fix to the bug will probably something like defaulting to a value if the version information isn't in the local.properties.

So, this is fixed now on the master branch.  In order to take advantage of it, you'll need to run flutter create . in your project directory, and it should fix things up. It will eventually make its way to the dev and beta branches.  In the meantime, the workaround above will fix things for you.

flutter create with a " ." ?
Have the same issue.

flutter build apk --build-number=2

Just had this error, I fixed it by adding:
flutter.versionName=1.0.0
flutter.versionCode=1
flutter.buildMode=debug

to the local.properties file. Hope this helps someone!

Where did you put these lines to ?

Just had this error, I fixed it by adding:
flutter.versionName=1.0.0
flutter.versionCode=1
flutter.buildMode=debug

to the local.properties file. Hope this helps someone!

Where did you put these lines to ?

when I change the local.properties file and run it, it goes back to the previous setting. Why is that?

Just had this error, I fixed it by adding:
flutter.versionName=1.0.0
flutter.versionCode=1
flutter.buildMode=debug

to the local.properties file. Hope this helps someone!

Where did you put these lines to ?

when I change the local.properties file and run it, it goes back to the previous setting. Why is that?

@jay11234  It happens because it reads the version from pubspec.yaml
# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# In Android, build-name is used as versionName while build-number used as versionCode.
# Read more about Android versioning at https://developer.android.com/studio/publish/versioning
# In iOS, build-name is used as CFBundleShortVersionString while build-number used as CFBundleVersion.
# Read more about iOS versioning at
# https://developer.apple.com/library/archive/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html
version: 1.0.1+3

version code is automatically parsed from pubspec.yaml
version number is number part at the left side of + plus sign and the rest is versionCode
version: 1.0.0+2
version number 1.0.0
version code 2

I'm getting this on my GitHub Action (https://github.com/mylisabox/lisa_flutter/commit/52788f4367d55db5693e8dbe2c57ccf59d6c03a5/checks?check_suite_id=263017737)
@gspencergoog if I apply your patch it will mean that my version will be put to 1.0 build 1.
Which is not what I want too, in fact it's worse as it will not fail at all but will not have the right version number. Shouldn't this local.properties be created automatically if it doesn't exist by flutter build ?

Here is my workaround for github actions
Github Actions workflow file
      - uses: subosito/flutter-action@v1
        with:
          channel: 'stable'

      - name: flutter pub get
        run: flutter pub get

      - name: set gradle wrapper
        run: gradle wrapper
        working-directory: ./android/

      - name: flutter build version number error workaround
        run: |
          cat ../pubspec.yaml | grep version: | cut -d' ' -f2 | cut -d'+' -f1 > FLUTTER_VERSION_NAME
          cat ../pubspec.yaml | grep version: | cut -d' ' -f2 | cut -d'+' -f2 > FLUTTER_VERSION_CODE
          echo -e "\nflutter.versionName=$(cat FLUTTER_VERSION_NAME)" >> local.properties
          echo "flutter.versionCode=$(cat FLUTTER_VERSION_CODE)" >> local.properties
          echo "flutter.buildMode=release" >> local.properties
        working-directory: ./android

      - name: check build number
        run: cat local.properties
        working-directory: ./android

These parameters are fetched from pubspec.yaml, so it's not a good idea to remove them from build.gradle or modify local.properties!
You have 2 options:
1- Change version inside pubspec.yaml to 1.0.1+5 (after + is versionCode (now versionCode is 5))
2- If you use kinda semver versioning (1.0.1 = 10001) then you can use this in your app build.gradle:
int generateVersionCode(String versionName){
    def parts = versionName.split("\\.").collect{it.toInteger()}
    return parts[0] * 10000 + parts[1] * 100 + parts[2]
}
...
 defaultConfig {
        applicationId "app.package.name"
        minSdkVersion 16
        targetSdkVersion 29
        versionCode generateVersionCode(flutterVersionName)
        versionName flutterVersionName
        multiDexEnabled true
    }


Add CI/CD

Having CI/CD would allow for automated linting and testing in the pipeline which would make it easier to contribute to the project, ensuring proper Quality, reducing number of bugs and so on.
GitHub Actions would do the job just fine.

Agree! We're currently working on making the codebase more established and writing automated testing

@thomashacker I've seen that currently the tests fail, I probably don't know the codebase well enough to fix them, but I can definitely add the CI/CD

That'd be helpful, thanks! 🚀

We'll work on proper testing in future versions! Thanks a lot for the good work


fix: gateway has all underscore_separated endpoints

Rename CONNECT_FED_ENDPOINT to CONNECT_FED_OLD_ENDPOINT and LEAVE_FED_ENDPOINT to LEAVE_FED_OLD_ENDPOINT (both for handler and client usage). Then add CONNECT_FED_ENDPOINT and LEAVE_FED_ENDPOINT which use underscores instead of dashes in their endpoint values. Set the gateway server to serve both the new (underscored) and old (dashed) endpoints using the same handlers. This way, once backwards compatibility is dropped in the future, we can switch the client to use the new endpoints.
Change CONNECT_FED_ENDPOINT and LEAVE_FED_ENDPOINT to use underscores instead of dashes, to match the rest of the endpoints

I don't think we care about backwards compatibility between gateway-cli, gatewayd, and gateway-cln-extension. All three of these binaries should be run by the same operator, if one of them is off they should realize this and upgrade.
https://github.com/fedimint/fedimint/pull/5871 is making the last bit of changes to devimint that should use the same version for all of these binaries across the backwards compatibility tests and the upgrade tests.
I'd say just fix the endpoints, don't keep the old ones around.

I would like to wait to merge until the upgrade tests are working again, just to be sure we don't introduce additional regressions

I don't think we care about backwards compatibility between gateway-cli, gatewayd, and gateway-cln-extension. All three of these binaries should be run by the same operator, if one of them is off they should realize this and upgrade.

While we don't commit to stability yet, we should still consider cost/benefit. @Kodylow whyt do you think? Is it wort the changes to the Gateway UI?

Think this should be good to go unless @Kodylow has any objections

Send it

Something is weird here, how can such an easy change seemingly amplify flakiness?

Something is weird here, how can such an easy change seemingly amplify flakiness?

fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:05 2024-08-20T13:16:49.131172Z  INFO tests: Testing inter federation payment from LDK -> CLN
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:05 2024-08-20T13:16:49.951041Z  INFO fm::task: signal received, starting graceful shutdown
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06 2024-08-20T13:16:50.967509Z  INFO devimint::cli: Received shutdown signal before finishing main process, exiting early
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06 2024-08-20T13:16:50.969748Z  WARN fm::devimint: failed to terminate lightningd plugins: command: lightning-cli --network regtest --lightning-dir=/build/lnv2_module-3dkw/devimint-15741-419/cln plugin stop gateway-cln-extension
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06 Caused by:
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06     exit status: 2
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06     stdout:
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06     stderr:
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06     lightning-cli: Connecting to 'lightning-rpc': Connection refused
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06
fedimint-test-all-wasm32-unknown-unknown-ci> 00:04:06
fedimint-test-all-wasm32-unknown-unknown-ci> ## FAIL: lnv2_module

From the logs, it appears as though CLN is crashing during the inter-federation test of lnv2, since it fails to kill the extension. I doubt its related to this PR but its hard to tell why. I'm having trouble reproducing the problem locally.
@tvolk131 to help debug, we could add this change temporarily to your PR to get the logs from your CI runs
https://github.com/bradleystachurski/fedimint/commit/56f2abd1a4fa85e34079c9740045b61907ed2050
No guarantee it repros after that change though :/

I believe it was electrum flakiness this time, retrying...


⚠ SkyfallMC Minecraft Server has degraded performance

In 9cb6528, SkyfallMC Minecraft Server (play.skyfallmc.ga) experienced degraded performance:

HTTP code: 200
Response time: 1140 ms

Resolved: SkyfallMC Minecraft Server performance has improved in b327e04.


Epinio UI test - CI is failing on Service

I think we can improve code to avoid this issue:
https://github.com/epinio/epinio-end-to-end-tests/runs/5135051649?check_suite_focus=true
From a first quick eye, it looks like the cy.click is triggered too early.
  1) Services testing
       Create an application with a service, unbind the service and delete all:
     CypressError: Timed out retrying after 10050ms: `cy.click()` failed because this element is detached from the DOM.

`<a href="/dashboard/ext/epinio/c/local/services/create" class="btn role-primary">Create</a>`

Cypress requires elements be attached in the DOM to interact with them.

The previous command that ran was:

  > `cy.contains()`

This DOM element likely became detached somewhere between the previous and current command.

Common situations why this happens:
  - Your JS framework re-rendered asynchronously
  - Your app code reacted to an event firing and removed the element

You typically need to re-query for the element or add 'guards' which delay Cypress from running new commands.

I added a quick-and-dirty workaround for this here.
It works but it's not an elegant one, let's try to use another solution when we will re-factorize the code for the standalone UI.


Add functions for histogram standard deviation

Proposal
I would refer to old feature request https://github.com/prometheus/prometheus/issues/3998
Calculating stddev for histogram would be useful for me, because I use smokeping exporter https://github.com/SuperQ/smokeping_prober, which makes huge amount of probes and returns values aggregated by histogram data type.
My goal is to make sub second interval probing and I don't want to put such load on prometheus server directly. I consider two solutions, the first is calculate stddev by exporter and produce one more gauge metric per target, the second is to use existing histogram and calculate later on prometheus. The second one would be probably less precise, however it would provide this feature for general usage.
I think anyone who use histograms agree with some degree of precision loss. Anyone can controll it by defining bucket sizes wisely. Finally if I wanted absolute precision I wouldn't use metrics monitoring but log monitoring

Per #3998 this is possible in a statistically sane and useful way.

Based on https://github.com/prometheus/prometheus/issues/7030#issuecomment-602235105, we have decided in the bug scrub to close this.


Add uplink field topics support

The MQTT broker now published topics for specific fields:
https://github.com/TheThingsNetwork/ttn/tree/refactor/mqtt#uplink-fields
In the node's settings the user should be able to override the default messages topic alias (which is +/devices/+/up.

I'd say add the ability to enter an optional field name which is appended to the topic internally

I thought of that but then you will not be able to subscribe to a specific device. I already thought of an idea for https://github.com/TheThingsNetwork/node-app-lib/issues/9 which I'll implement next week

How so? You can subscribe to +/devices/+/up/{field}, replacing {field} by the entered field name. If no field name is entered, just subscribe to +/devices/+/up

Both examples are for all devices, not a specific one, which would require the second + to be a device ID

Circling back after convo on Slack, for Node-RED the node should have an optional Device ID field as well as an optional Field (Path).
If you'd want to listen to a couple of Device ID / Field combos you should use multiple TTN nodes or simply use the MQTT node and go crazy.

Can be done once https://github.com/TheThingsNetwork/node-app-lib/pull/18 is merged

Closed by #16


[QUERY] How to set Application Insights Metrics Namespace in AzureMonitorOpenTelemetryExporter

Library name and version
Azure.Monitor.OpenTelemetry.Exporter" Version="1.0.0-beta.14
Query/Question
I'm working on getting open telemetry working (so very close). One question I hope someone can quickly help me with. When using System.Diagnostic.Meter, how do I set the namespace for the metrics in Azure Monitor / Application Insights? Or is that a field that is only kept for backwards compatibility and always set to azure.applicationinsights? Thanks!
Environment
.NET SDK:
Version:   7.0.306
Commit:    f500069cb7
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.22621
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\7.0.306\
Host:
Version:      7.0.9
Architecture: x64
Commit:       8e9a17b221
.NET SDKs installed:
6.0.413 [C:\Program Files\dotnet\sdk]
7.0.306 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.20 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 6.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 7.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86   [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download

Hey all, any update on this one? Thanks!

Hi @joebeernink.   Sorry that the support team failed to pick this up.  I shifted this over to the Monitor team directly.

Thanks!

It is currently hardcoded and not available for customization.

@cijothomas is there an open github issue somewhere for adding this capability? If not, can we turn this request into an issue please? Having all OT metrics forced into the same namespace for large projects is going to make it really difficult to manage large systems.

@mattmccleary Could you help where would user put this feature request? This is not .NET specific ask, so a more general place for feature request?

We do have https://feedback.azure.com/d365community/forum/3887dc70-2025-ec11-b6e6-000d3a4f09d0. However, I want to bring this up in our next available PM/Engr sync as I think it should be higher pri to resolve this.

Hey @mattmccleary, any word on this? Thanks!

Yes, the metrics team is working on a namespace concept in Azure Monitor Workspace, but it's still 6-18 months out (and we need customer feedback to understand how customers would want to use it). Can I understand your scenario better?

Having all OT metrics forced into the same namespace for large projects is going to make it really difficult to manage large systems.

How so? Are you trying to send all metrics to a single App Insights Resource? How would you like to use namespace? Is the issue of service being too big to understand also an issue in, for instance, the App Map?

I second this. Right now we have many custom metrics and we were able to group them into namespaces per service since .net core 3.1:

But with .net 8 with the promoted OpenTelemetry api (UseAzureMonitor + IMeterFactory + CreateCounter()) all meters are pushed to default namespace, i.e. "azure.applicationinsights".

I'm consolidating all issues regarding overriding specific fields in the Application Insights schema into another issue to help with tracking. https://github.com/Azure/azure-sdk-for-net/issues/46021


Implement cross axis size in DatePickerOptions

Thanks for making this great package.

Maybe I am missing something, but there doesn't seem to be a way to prevent line break other than making font size smaller.

I think it would be best if we could provide our own date view builder

Thank you for writing your opinion!
Your suggestion will be taken into consideration.
Thank you.

we couldn't provide a builder, but we updated 3.5.0 by improving usability.
Thank you again for writing your comments :)


Storage: Unifies LVM and Ceph filesystem mount option logic

Fixes LVM driver that wasn't reading volume's block.mount_options when mounting.
Addresses an issue discovered in https://discuss.linuxcontainers.org/t/volume-block-mount-options-not-working/8049

Testsuite passed

@tomponline aren't we losing the user_subvol_rm_allowed part of the logic with this branch?

@stgraber ah yes indeed, I'd intended to add that into the Volume's new function but got distracted with the veth device cleanup bug in the other PR. Will add back in now.

@stgraber fixed.

Testsuite passed


Fix error related to timewizard formatting.

Effect:
numbers on sidebar were missing because an error was occuring.
services cards appeared blank if they were rendered after a service that had switched health statuses.
The error was due to scoping of this when calling another function in the class. this was not in the scope when the function was called from the html page, so it couldn't find the function also in the class.
Fix:
Removed the function by pulling in simple logic into the same method.
There is probably a better way to do this if you are a level 8+ javascript wizard.
The error that occured was
ServicesSidebarComponent.html:74 ERROR TypeError: this.formatHealthStatusForTimewizard is not a function
at ServicesSidebarComponent.timewizardMessage (service-groups.facade.ts:92)
:nut_and_bolt: Description: What code changed, and why?

:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
This error occurred after a service switched health statuses. I was able to do this by manually publishing a service and editing the health status.
example:
    applications_publish_supervisor_message --name "pos-terminal" --group "default" \       --origin custom --version "2.3.4" --release "20190115181111" --health "1" \       --sup-id "3802df84-14e4-42f7-8e15-07865a49b033" \       --application "pos" --environment "production-us-east" --site "ny-123"
and then
applications_publish_supervisor_message --name "pos-terminal" --group "default" \       --origin custom --version "2.3.4" --release "20190115181111" --health "0" \       --sup-id "3802df84-14e4-42f7-8e15-07865a49b033" \       --application "pos" --environment "production-us-east" --site "ny-123"
:white_check_mark: Checklist

[ ] Tests added/updated?
[ ] Docs added/updated?

:camera: Screenshots, if applicable

Easier to read as well 🎉


Windows Support

As already in the title mentioned, are you planning on supporting Windows too? The only thing that should differ, is the extraction of the git credentials as mentioned here: #12, right?

Yes, we want this to work on all platforms.
I am not sure about the difference though. If thats the only difference then yes, it should solve the issue.

The git creds can be configured via the config file now. As mentioned if this is the only change required then it should work on windows. Can you please check?

Unfortunately Windows has a different name for the HOME environment variable. It's equivalent to %userprofile% or %homepath%.  If you manually add the HOME environment variable, everything works fine.

Try configuring it via the ggconf file. Look at ggconf.example.yaml

I tried compiling on Windows and I get an error, I'm a rust newbie so no idea if this is a project thing or just a "my machine" thing:
gg on  master is 📦 v0.3.2 via 🐍 v3.7.6 (.venv) via 🦀 v1.42.0 took 10s
❯ cargo install --path .
  Installing git-governance v0.3.2 (C:\Work\GitHub\gg)
    Updating crates.io index
error: failed to compile `git-governance v0.3.2 (C:\Work\GitHub\gg)`, intermediate artifacts can be found at `C:\Work\GitHub\gg\target`

Caused by:
  failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (exit code: 0xc0000374, STATUS_HEAP_CORRUPTION)
--- stdout
___.exe
lib___.rlib
___.dll
___.dll
___.lib
___.dll
C:\Users\Matt\scoop\apps\rust-msvc\1.42.0
debug_assertions
proc_macro
target_arch="x86_64"
target_endian="little"
target_env="msvc"
target_family="windows"
target_feature="fxsr"
target_feature="sse"
target_feature="sse2"
target_os="windows"
target_pointer_width="64"
target_vendor="pc"
windows

Otherwise I'd be happy to try and get the configuration test verified.

Looks there has to be more work to be done for windows. I unfortunately dont have a windows machine setup to try now.
Can you try re-installing rust via rustup(if you did not do it via rustup in the first place) and check?

Hm, I now installed via rustup (I am using rustup-msvc from scoop). It has worked perfectly right now! I'm using it for the gg status command.

Cool. Closing this issue then.


gamnit: miscellaneous services and a few fixes

This PR groups features required by my recent unpublished tech demos built on gamnit.
Here are more details on the less intuitive commits:

The change to current_fps lets a program use it right from the beginning and gives a value which is somewhat realistic (vs returning 0).
The placeholder_model can be useful when quickly writing the prototype of a game to get something visible in the 3D space.
The doc of subtexture clarifies an ambiguity as to whether the method expected pixel offsets or proportional values out of 1.0.
The tool texture_atlas_parser can be useful to other games.
draw_mode is very useful to create optimized Mesh, using gl_TRIANGLE_STRIP and gl_TRIANGLE_FAN.
The old API of triangulate was counter-intuitive. The result was put in a parameter and the list of points was cleared in the process. This PR offers a simple method and the recursive implementation as an optimized alternative. ping @BlackMinou
tinks_vr is not playable but it shows how to convert a gamnit game to a basic VR version.

Reroll to fix tests and apply @privat comment.

+1


docs: update overview text

Update overview to mention lists

It lacks the fact that it can now do music aswell for me...
What do you think about this?
omegabrr transforms tv shows, movies and music of your arrs or predefined lists into autobrr filters.
This is especially useful for automating your filters for monitored or popular media or even for racing purposes.