Auto-update Node versions used in CI pipelines

Addresses this comment
Context
We pinned the Node versions used in CI to make our builds more deterministic. However, as @gonzaloriestra pointed out, we do it at the cost of not detecting if new versions of Node break the CLI.
What
We can reduce the cost of leaning towards determinism by automating updating the Node versions in CI pipelines. We can use a GitHub action that runs recurrently, updates the pipeline if there are newer Node versions, and opens a PR. The workflow is similar to the one that Dependabot follows when there are new dependency versions.

As an alternative, maybe we can distinguish between main vs PR builds, where PR builds are deterministic to avoid unrelated breakages blocking a PR, but we'll still get alerted on any problems with new Node versions when we merge to main, before deployment happens.

As an alternative, maybe we can distinguish between main vs PR builds, where PR builds are deterministic to avoid unrelated breakages blocking a PR, but we'll still get alerted on any problems with new Node versions when we merge to main, before deployment happens.

I'd keep main and PR consistent. Otherwise we might see failing builds in main that are hard to diagnose.


Bump ASM version to 9.5

ASM 9.5 supports Java 21 bytecodes. There's no API changes in this version.
As ASM affects the generated instrumented bytecode, the decoration format is changed too.

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test RfR

I've triggered the following builds for you. Click here to see all build failures.

ReadyForRelease build

@bot-gradle test and merge

I've triggered a build for you. Click here to see all failures if there's any.


Need to flip glt_x?

Here are a few granules for which the default processing did not work as expected for us. We had to end up using
glt_x  = ds.reflectance.shape[1] - loc.glt_x.data
Here are some examples:
EMIT_L2A_RFL_001_20230530T092122_2315006_042
EMIT_L2A_RFL_001_20230530T092146_2315006_044
Is there any other metadata field that we need to parse and check against to make sure if this flip is needed or not?

Here are other examples. There appears to be a correlation with the pass direction of the sensor?
Granule that needed a flip: EMIT_L2A_RFL_001_20230528T220519_2314815_009
Granule that did not need a flip: EMIT_L2A_RFL_001_20230427T173257_2311711_009

Thanks for bringing this to our attention. I started to look into this and found the same inconsistency with newer granules. I'm guessing the data is now being flipped (or no longer being flipped) with the new software version. We will reach out to the EMIT team.

Testing more - everything that was processed with software version 010613 appears to have this issue. The ones with 010611 do not.  Looking for examples of 010612 but havent found any yet

We are looking into this.  I suspect the issue was either introduced with the flatfield update in 010612 or is unrelated to the software build.  010613 is unlikely to be the culprit.

Would it be possible to provide a timeline (dates) on which software updates were deployed. Alternately, it would be nice to have the software/processor version in the CMR metadata for the granules.

The easiest way to track the release history through time is to look at the emit-sds/emit-main repository (https://github.com/emit-sds/emit-main/releases).   The software build version is also available in the file metadata (not the CMR), which I believe (?) is api queryable. @ebolch, can you confirm that?

Yeah - intent is to make it queryable via CMR. Right now I have been looking at the netcdf metadata to identify the software version. The releases to emit-main are less useful as we don't really know when these were deployed and used in production.

Reference to emit-main was simply to give the timeline (dates) as requested above - I understand that's independent of the desire to access the particular metadata with each granule.
Re: file metadata, I should have been more explicit - certainly the build number is in the netcdf, but it's also available in the ummg (along with quite a bit of other metdata), which may give you what you're after.

We also have a positive ID on the core issue, which did occur in 010612, due to a gdal read failure for long metadata fields.  We are working on a fix.

Until a fix is implemented, you can retrieve the software build version from the additional attributes via cmr using the umm_json cmr endpoint. Something like this in python:
import requests

granulesearch = 'https://cmr.earthdata.nasa.gov/search/granules.umm_json'

cmr_param = {
    "collection_concept_id": 'C2408750690-LPCLOUD', # EMIT L2A Reflectance
    "temporal": '2022-09-03T00:00:00Z,2022-09-03T23:23:59Z',
    "point":'-62.1123,-39.89402'
}

response = requests.post(granulesearch, data=cmr_param)
response.json()['items'][0]['umm']['AdditionalAttributes']

Thank you. Closing this as these products have already been removed.


Address k8s del_svc api change

Fix Kubernetes Container Manager:
CHANGELOG (Kubernetes)
delete_namespaced_service() now takes an required body (delete option) parameter.
Refactor service storage to remove registry wrapper kubernetes/kubernetes#59510

Spec:
https://github.com/kubernetes-client/python/blob/master/kubernetes/docs/CoreV1Api.md#delete_namespaced_service
Error like
  File "/Users/simonmo/Desktop/clipper/clipper/clipper_admin/clipper_admin/kubernetes/kubernetes_container_manager.py", line 393, in stop_all
    namespace='default', name=service_name)
TypeError: delete_namespaced_service() takes exactly 4 arguments (3 given)

will now go away.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1343/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1361/
Test PASSed.


Add // IWYU: export to log_level.h

Add // IWYU: export to log_level.h in order to fix a clang-tidy error which shows up internally.
Signed-off-by: Ryan Hamilton<EMAIL_ADDRESS>

/assign @Augustyniak

/assign @mjbshaw

Is this a false positive in clang-tidy? Is the header actually used?

Is this a false positive in clang-tidy? Is the header actually used?

Ah. So clang-tidy complains in some code we have internally which includes log_level.h and then attempts to use LogLevel which is defined on line 10. I think it's a legit warning. Or alternatively, we could get rid of that "using" and instead just use the enum from source/common/common/base_logger.h directly (and have callers include that file).
WDYT?

Yeah, clang-tidy sees that mobile/library/cc/log_level.h exports the type LogLevel, so if that's all I use then there are no complaints. But the enum constants are not defined in that header, so if I do something like LogLevel::off then clang-tidy will complain that I'm not including #include "source/common/common/base_logger.h".

WDYT?

Fine with me, I was just trying to understand a bit better. Thanks for explaining!


Kitura-net 0.13 fails to build CHttpParser

We're trying to use the 0.13 tag of Kitura-Net in our SDKs, however it fails with below error. Note that 0.12 works without similar issues.

Try going to your Build settings and in the KituraNet target, add {project path}/.build to the Header Search Paths and the Library Search Path.

@dfirsht I've also noticed that Http was renamed to HTTP in 13.x stream, is this a permanent change?

Yes, this is to comply with swift 3 API guidelines.

Ok, this seemed to fix the problem. Thanks.

HI, I'm having this same problem now. I've been using swift package manager so far, is it possible to make the necessary changes that way or would I need to export it to an xcode project? Either way, would you be able to give specific step by step instructions on how to make the change? I would really appreciate it!

We just use swift package generate-xcodeproj to create an XCode project for all of our repositories.
If you are still having difficulties, please include the version of Kitura-net you are using.


build.lib support format amd module

Description
build.lib support format amd module, rollup support, but when i use rollupOption to set output, is invalid
Suggested solution
build.lib add formats: [amd]
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

You can just use umd because umd can be consumed as amd and cjs.
https://github.com/umdjs/umd

You can just use umd because umd can be consumed as amd and cjs. https://github.com/umdjs/umd

@sapphi-red  umd consumed as amd, but there is no mechanism to load dependencies

there is no mechanism to load dependencies

What do you mean by this?

there is no mechanism to load dependencies

What do you mean by this?

amd dependencies use define('someLib', ['moduleA', 'moduleB'], () => { }), if format umd, somelib  consumed as amd but moduleA and moduleB can't load

I think it works. Would you expand it more?
https://stackblitz.com/edit/vitejs-vite-fkydrs?file=vite.config.js&terminal=build


dart.exe crashes when closing IntelliJ on Windows

I am running IntelliJ on Windows with the Dart and Flutter plugin. Very often, when I am closing IntelliJ after I used it for a longer time, I am presented with this dialog indicating that dart.exe has crashed:

Not sure if the Dart Plugin or the Flutter plugin is causing this. It happens fairly frequently, though.

/cc @devoncarew

This issue was moved to flutter/flutter-intellij#711

I'll track over at flutter-intellij (w/ the assumption that the resolution is in the plugin).


makefile osx arguments error

osx-x64-debug: .build/projects/gmake-osx-x64
make -C .build/projects/gmake-osx config=debug
osx-x64-release: .build/projects/gmake-osx-x64
make -C .build/projects/gmake-osx config=release
osx-x64: osx-x64-debug osx-x64-release

Generated path name is gmake-osx-x64

What's the actual problem here?!


fix: Fix the correcrt link to the docs

Summary
We had a 404 with the docs. PR is the fix

Pre merge checklist

[x] Did you check you NRQL syntax? - Does it work?
[x] Did you check your dashboard image quality? -  Do they look good?
[x] Did you check that your alerts actually work?
[x] Did you include an InstallPlan and Documentation reference?
[x] Did you check your descriptive content for voice, tone, spelling and grammar errors?
[x] Did you attach images of your dashboards to the PR so we can see them working?

Screenshots
Attach images of any visual changes, such as a dashboard here.

I made some suggestions to the description and URL format under documentation, please review the contributor guide for details on why I am suggestion this. Thanks for the contribution.

Commiting reviewer changes


Custom Tool descriptions

⚠ Please check that this feature request hasn't been suggested before.

[X] I searched previous Ideas in Discussions didn't find any similar feature requests.
[X] I searched previous Issues didn't find any similar feature requests.

🔖 Feature description
A user should be able to set a custom tool description.
Extend the Prisma schema with a description field.
Adapt the /api/tools endpoint to take a in description in it's payload.
📝 Additional Context
No response
Acknowledgements

[X] My issue title is concise and descriptive.
[X] I have searched the existing issues to make sure this feature has not been requested yet.
[X] I have provided enough information for the maintainers to understand and evaluate this request.

This was fixed by #154


InvalidNetworkInterfaceId.Malformed

Do you already have an issue opened with F5 support?
No
Description
Cloud failover was failing. EIP was not associated to any eni. Error message:
finest: [f5-cloud-failover] Status: "HTTP request failed: 400 \"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\"?>\\n<Response><Errors><Error>InvalidNetworkInterfaceId.Malformed<Message>Invalid id: \\\"to-set\\\" (expecting \\\"eni-...\\\")</Message></Error></Errors><RequestID>ac32605b-8594-4bdf-961d-5e1d4db7ad64</RequestID></Response>\"" Retries left: 50

Cloud Failover Extension Version: 2.1.3
BIG-IP version: <IP_ADDRESS>
Cloud provider: AWS

Severity Level
For bugs, enter the bug severity level. Do not set any labels.
Severity: 2

@lyoben Please open a case with F5 if this is still an issue.


Allow manual entries in File Sharing settings of Docker for Mac OSX

Currently, the only allowed method is selecting from a pop up, however, the pop up will not allow selecting volumes like /var or /etc but add them as /private/var or /private/etc. So if the docker config is set to use /var, as it's volume, it will fail to start.
This is a problem where there is a mix of Linux and Mac machines using docker and docker-compose to setup development environment.

ping @dsheets

This is specific to docker for Mac; can you reopen this in the docker for Mac issue tracker? https://github.com/docker/for-mac/issues
Thanks!

This is a duplicate of docker/for-mac#412 which is on the roadmap for our GUI team. Sorry for the inconvenience and thanks for your patience!


Optimizer creates candidate from out of bounds args

Steps to reproduce
Note: I don't know if this is properly handled (doesn't cause the optimizer to mis-behave) but here is my observation:

Define a bounded instrumentation variable (ex. instru.var.Array(1).asfloat().bounded(0,5))
Create a candidate from out of space args (ex. 10)
Optimizer.tell(candidate, arbitrary value)

Observed Results
the candidate is created normally and the optimizer accepts it.
Expected Results
throwing an exception due to output of bounds args.

Good point, this should be easy to solve, by updating the transforms:
https://github.com/facebookresearch/nevergrad/blob/b8fdfa72ce6674ff10c9d668d252c9257025c742/nevergrad/instrumentation/transforms.py#L107-L173
You're welcome to do it if you want to, otherwise I should have time to do it by wednesday I think


Advanced option for searching on currently display-only fields

Many parameters are currently displayable on the "Details" tab, but can't be searched. These have been eliminated from the search page to improve the user experience. There could be an option to provide them, though.
Examples
• BIAS_STRIP_MEAN
• COMMAND_SEQUENCE_NUMBER
• DARK_STRIP_MEAN
• DETECTOR_TEMPERATURE
• ELECTRONICS_BIAS

We don't have display-only fields anymore so this is no longer relevant.


Added ML basic programs

Done this PR as part of Hacktoberfest2021 so do add hacktoberfest-accepted tag! thanks


Project is not working.

Hey i was trying to use this but not able to run.

@pradeep-chauhan what's your problem?
what version of Swift/Xcode did you try to compile?

getting this cannot be opened because it is missing its project.pbxproj file.
Xcode - 8.3.1

@pradeep-chauhan Pushed missing folder. now good to go.


Fix apiBaseUrl acquisition error

#34

@Christopher-Hayes

Thank you, will get this released soon.


test issue

]

Hey @{name}! Thanks for opening the issue, but we are closing it because it looks like a feature request, feel free to send us a pool request or vote on it on Product Pains. :)


Move Bleve and Elastic code indexers to use a common cat-file --batch

Both bleve and elastic code indexers will call cat-file blob blobsha repeatedly for each file indexed. By using a single cat-file --batch we can reduce these multiple calls to a single common cat-file batch.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

Merging #14781 (b10ab24) into master (487f2ee) will decrease coverage by 0.01%.
The diff coverage is 38.15%.

@@            Coverage Diff             @@
##           master   #14781      +/-   ##
==========================================
- Coverage   42.21%   42.20%   -0.02%
==========================================
  Files         767      771       +4
  Lines       81624    82093     +469
==========================================
+ Hits        34458    34646     +188
- Misses      41531    41800     +269
- Partials     5635     5647      +12

Impacted Files
Coverage Δ

models/action.go
48.52% <0.00%> (-2.42%)
:arrow_down:

models/migrations/migrations.go
2.59% <ø> (ø)

models/migrations/v166.go
0.00% <0.00%> (ø)

models/migrations/v172.go
0.00% <0.00%> (ø)

models/migrations/v173.go
0.00% <0.00%> (ø)

models/oauth2.go
29.16% <0.00%> (-2.66%)
:arrow_down:

models/session.go
0.00% <0.00%> (ø)

models/user.go
53.05% <ø> (+0.38%)
:arrow_up:

modules/context/context.go
65.22% <0.00%> (+6.72%)
:arrow_up:

modules/git/pipeline/lfs_nogogit.go
0.00% <0.00%> (ø)

... and 64 more

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 42118c6...b10ab24. Read the comment docs.

🚀


Make link to issue via HTML anchor tag.

It appears that Markdown-style links do not work within HTML tags.  Use HTML
instead!

Thanks!


How to do a batch entry to the DB.

Goal is to allow a user to create datasets entries as a batch. Validating the data should be done:

Check if file exists.
Check if the file(s) are not duplicates.

The batch will be written in python. modifying or deleting existing entries will not be permitted.

Partial duplicate to #8

Fixed in #8


Add AUTHORS file

Since we lost prior git history when open sourcing the repos, it behooves us to include an AUTHORS.md file to list names from Jut 1.0 era.
Couple of examples (AUTHORS.md seems more popular):
https://github.com/caolan/nodeunit/blob/master/CONTRIBUTORS.md
https://github.com/asciidisco/grunt-requirejs/blob/master/AUTHORS.md
To keep auto-updating the authors file, something like this works.

@demmer you have the draft for juttle and juttle-viz, please merge it.


Add Box Input

Add ability to provide box input along with point input (with nice looking mousedown animation). Though I'm not sure if it's needed to be honest, point input works really well in general.

Hey sorry, did not get time to contribute in terms of code until this point. In future the box input will be required as a feature.
Reason: I had worked on a use-case where images were very wide, and the segmentation map was also very wide. I had to segment the LED ad-board. Example:

So, if you observe, we have multiple objects in between. If we just provide a single point input, it might not identify the entire board, hence I believe the BB will be required in such cases.

On a side note: The tagging tool is awesome.


Revert "[nrf noup] kconfig: Disallow FPU for SPM"

This reverts commit ee89a68db75bf0d52dbfc9ee0ad9b4e4dfc18500.
Signed-off-by: Joakim Andersson<EMAIL_ADDRESS>

Are you not supposed to use some special commit message tag to make sure that the tooling used for rebases automatically removes some patch commit?
Like here #919 ? Or is that only when a patch removes parts of another commit?

I think this is correct, your example is a fixup, and not a revert. Due to the rebase of sdk-zephyr we don't have any reverts left to compare.
@carlescufi @mbolivar-nordic Is this correct?

Are you not supposed to use some special commit message tag to make sure that the tooling used for rebases automatically removes some patch commit?
Like here #919 ? Or is that only when a patch removes parts of another commit?

I think this is correct, your example is a fixup, and not a revert. Due to the rebase of sdk-zephyr we don't have any reverts left to compare. @carlescufi @mbolivar-nordic Is this correct?

I am quite sure you are right, @joerchan. But I will ask @mbolivar-nordic to take another look just in case.

@joerchan is right -- just use git revert. The oss-history tooling looks for reverts when it's figuring out what commits to leave in NCS history after a rebase, so this is the only supported way to do this, and it's why upmerges always include a stack of reverts for downstream commits that conflict, followed by reapplications of conflict-free versions.
I could have sworn we had this documented somewhere, but I couldn't find it, so I wrote some new internal documentation to point people to if this comes up again and will point you all to it.


More explicit types in examples

And some other minor tidying.
Closes https://github.com/armanbilge/calico/issues/189. @hejfelix were these the ones you were thinking, any others I should add to?

Yeah. I think adding them to all the *.md code would hammer home the point that components are Resource[F, HtmlElement[F]].


Change the calculation method for numbers like 3

trying to calculate a factor for 4/3 have problematic results

A probable solution is to add more precision and let it play out


fix(amplify-codegen): Correct cli help re: codegen --maxDepth flag

Issue #, if available: https://github.com/aws-amplify/docs/issues/2720
Description of changes:
Previously, users could execute the amplify codegen command with a --max-depth flag. Accordingly, when users would run amplify codegen --help the above usage would be described. However, at some point in 2019, the above flag was changed to --maxDepth (see https://github.com/aws-amplify/amplify-cli/pull/2175). To date, neither the CLI help nor the official documentation reflect this change.

This PR addresses the CLI help output.
How are these changes tested:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Will merge this tomorrow unless there are any outstanding objections.


instancetype: inferFromVolume assumes directly referenced garbage collected DataVolumes have always created labelled PVCs

/area instancetype
What happened:
$subject, this isn't always the case if the existing DataVolume isn't itself labelled. For example, if a user independently creates a DataVolume pointing at a labelled PVC as the source. The DataVolume is eventually garbage collected and the created PVC isn't labelled leading to a failure to infer any instance type defaults.
Ultimately this is a something I need to address in CDI but I wanted to document it here as we will need to follow up with additional functional tests once a fix has landed in CDI.
What you expected to happen:
DataVolumes using a labelled PVC or DataSource as their source pass on these labels to the PVC they create before the DataVolume is itself garbage collected.
How to reproduce it (as minimally and precisely as possible):
See above.
Additional context:
I'll follow up with a CDI bug and PR here.
Environment:

KubeVirt version (use virtctl version): N/A
Kubernetes version (use kubectl version): N/A
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

i have the similar question, if i create dv with the label,  i want labels to be passed to pvc.

i have the similar question, if i create dv with the label,  i want labels to be passed to pvc.

That should be the behaviour of CDI at the moment, the issue described here is specifically for the non-labelled DV but labelled source use case.

/close


Fix Ui.png formatting in README

Pull Request Test Coverage Report for Build 430

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.551%

Totals

Change from base Build 429:
0.0%

Covered Lines:
2824

Relevant Lines:
3340

💛  - Coveralls


Improve the "view schedule" layout

Look into possibly finding another solution than using an HTML table
Write a unique CSS class for it that allows for changing the fill color of a course block
The dynamic table generation is somewhat spaghetti-code-ish right now; needs to be improved regardless of implementation
Add a "view course details" button to each course

Use a BufferedImage to render the graphics, then instead of the delete and more info buttons on each course, use a dropdown menu at the top of the page for deletions, and have a button that forwards to the search page pre-populated with all the courses on the schedule.

I'll work on this today (Thursday, 4/28/2016) but I doubt I'll be able to get it done for tomorrow's milestone; I'll try to have it done for the final presentation though.

Trying to keep using HTML table; tried keeping track of the number of rows (real and virtual) in each column with an independent counter for each column, and using that information to decide whether to add an empty cell; a little messed up, thought it might be because of the order it's going through the classes, so I wrote a custom comparator to sort the courses by time. Better, but not quite working yet.

IT FINALLY WORKS PERFECTLY. The time conflict checking needs some work though. Will open in a new issue.


Scaling option won't change render scale at all

Hello,
Thank you for your work!
So, for few months now, I noticed my kiosk render won't scale up anymore.
Changing SCALING to 2 or 3 or 0.5 won't affect the size of the content displayed.
Here is my configuration yaml:
HA_BASE_URL: https://192.168.1.XX:8123
HA_SCREENSHOT_URL: /lovelace/kindle?kiosk
HA_ACCESS_TOKEN: >-
  [mytoken]
LANGUAGE: fr
CRON_JOB: "* * * * *"
RENDERING_TIMEOUT: "60000"
RENDERING_DELAY: "0"
RENDERING_SCREEN_HEIGHT: 1448
RENDERING_SCREEN_WIDTH: 1072
BROWSER_LAUNCH_TIMEOUT: "30000"
ROTATION: 90
SCALING: 2
GRAYSCALE_DEPTH: "8"
IMAGE_FORMAT: png
COLOR_MODE: GrayScale
REMOVE_GAMMA: true
PREFERS_COLOR_SCHEME: light
HA_BATTERY_WEBHOOK: ""
ADDITIONAL_ENV_VARS: []

The content I'm trying to scale up is a Google Sheet integration on a lovelace view (panel)
Here is the content on /lovelace/kindle:
type: iframe
url: >-
  https://docs.google.com/spreadsheets/d/e/XXXXXXXXXXXXXXXX/pubhtml?gid=0&single=true&widget=true&headers=false
allow_open_top_navigation: false
aspect_ratio: "9:8"
show_name: false

Thank you in advance

Hi @Godigodi89, thanks for reaching out!
Did you try another website to find out whether it may be only Google Spreadsheets related?
I heard they're using a specific technique to render their website content (via canvas elements), which may ignore the browser's built-in scaling and zooming features for cases like this.
We may want to find a solution for Google Spreadsheets then.

Hi @sibbl, thank you for your reply.
I've tried with my main "Menu" lovelace view using kiosk, and scaling is working just fine with render. So I guess you are right.
Here is the idea I've been trying to work on so far on /lovelace/kindle:
type: iframe
url: >-
  https://docs.google.com/spreadsheets/d/e/XXXXXXXXXXXXXXXX/pubhtml?gid=0&single=true&widget=true&headers=false
allow_open_top_navigation: false
aspect_ratio: "9:8"
show_name: false
card_mod:
  style: |
    div#root iframe  {
      transform: scale(2);
      transform-origin: 0 0;
    }

Now if I use Firefox browser and Chrome browser to visit /lovelace/kindle?kiosk I get my spreadsheet rendered twice bigger as the original, as expected.
However, for some obscure reasons, the size won't change when rendered on your add-on, no matter the scaling value used.
I've also tried to set the RENDERING_DELAY to 10000 (10 seconds) just to test if the renderer was maybe a bit long to scale it up, with no success.
Could it be a difference between how Puppeteer/chromium is dealing with specific Google services ?


add a browser testing checklist

This adds the browser testing checklist from the Capital Framework docs. Once we all agree on this document, I'll update the docs to point to it so that we have a single source of truth.

This is a great baseline. Should we have a guide on how to test for each section, especially for people who have never done testing (I've only done a bit of accessibility testing).

Should we have a guide on how to test for each section, especially for people who have never done testing (I've only done a bit of accessibility testing).

Yes, definitely. This comes straight from the CF checklist, which was designed to be copy and pasted into issues/pull requests. This should probably be expanded beyond that though.

@ascott1 if you haven't seen it, [GHE]/flapjack/Getting-started-with-Flapjack/wiki#front-end has a lot of different types of testing resources.

@ascott1 if you haven't seen it, [GHE]/flapjack/Getting-started-with-Flapjack/wiki#front-end has a lot of different types of testing resources.

Whoa, that document is AMAZING. Should we close this in favor of porting that over? Is there value in having both documents?

I made the updates suggested, but let's answer my question above before merging.

Whoa, that document is AMAZING. Should we close this in favor of porting that over? Is there value in having both documents?

I don't think so. At least not beyond flapjack having flapjack-specific content. I think it would be good to bring the general stuff out into the open for sure. Doesn't necessary have to happen now, but up to whatever works for you @ascott1

I say we gradually add that stuff here... at least the stuff that we make use of.

Yeah, it's a living doc :)

Word. :shipit:

Nice. Push the button @Scotchester or @anselmbradford


Fix for label not always showing + distance calculation wrong for diagonals

This PR fixes two issues:

#337
I simply removed the

if (this.labels.children.length > segments.length) {
  this.labels.removeChildren(segments.length).forEach(c => c.destroy());
}

from ruler.js that was added by @TPNils in #329 . There was no explanation why this is needed - and removing it fixes the problem of the label disappearing with not apparent side effects.

#342
canvas.grid.measureDistances seems to return a wrong distance for diagonals in Foundry v12. There is a deprecation warning suggesting to use canvas.grid.measurePath instead, so I rewrote it to this. This fixes the problem - though the options are no longer relevant and I didn't test gridless stuff etc. because it's not needed for our game.

Additionally, I've updated some calls so that no more deprecation warnings get printed when dragging the ruler (except when routinglib is active).
If you need some small adjustments, just tell me - but overall the Foundry development experiment with the de-facto non-existing developer documentation didn't really encourage me to do more testing than "this works in exactly my case and that's good enough for me".

@manuelVo Please pull. this issue is annoying.

Please pull. Pythagoras is rolling over in his grave.

@manuelVo Please pull

@AshnakAGQ @smeeth123 @SilvesTheRog I've made my fork available for install until this PR is merged. You can install it by clicking on "Install Module" in Foundry and then manually copy/paste the following Manifest URL in the input field at the bottom:
https://raw.githubusercontent.com/Valerionn/foundryvtt-drag-ruler/master/module.json

This should replace your drag ruler version. If everything went right, you should see a module named "Drag Ruler [Fork - Valerionn]" with version "1.14.2f":

This should work completely out-of-the box but feel free to create an issue over at https://github.com/Valerionn/foundryvtt-drag-ruler.
I will update the manifest as soon as the original module here is updated so that you will automatically switch back to the original module when you update (but you can also always re-install the original package which should replace the fork).
Also, please remember that people develop these foundry modules for fun in their free time, so please don't spam the PR, I'm sure they'll look at it and merge it as soon as they have time & energy for this (even though I can understand that this issue is really annoying).


fix: Migration file import

Fixes the issue with failed import and directory listing.

well it works...

so does the rollback


Error while setting up platform authenticated

Version of the cusom_component
sensor.authenticated 0.2.0
supervisor 125
homeassistant 0.75.3

Describe the bug
After updating the sensor from 0.1.0 to 0.2.0 because of another bug I encountered (#24),
I enabled the component again and rebooted, after the reboot I got the following error:
Error while setting up platform authenticated.
Also I'm now noticing the error Login attempt or request with invalid authentication from <IP_ADDRESS>
which I think is new since updating this component. Might be unrelated but just wanted to mention.
For your info, I'm currently using the new auth_providers, legacy_api_password still enabled.
log
Log Details (ERROR)
Sat Aug 11 2018 20:26:40 GMT+0200 (Midden-Europese zomertijd)

Error while setting up platform authenticated
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 129, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.6/asyncio/tasks.py", line 358, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/config/custom_components/sensor/authenticated.py", line 54, in setup_platform
    add_devices([Authenticated(hass, notify, log, out, exclude)])
  File "/config/custom_components/sensor/authenticated.py", line 75, in __init__
    self.initial_run()
  File "/config/custom_components/sensor/authenticated.py", line 82, in initial_run
    for ip_address in file_content:
TypeError: 'NoneType' object is not iterable

is your .ip_authenticated.yaml file empty?
if so delete it


any android device(which is android Q) can apply this?

Hi @mathpopo usually this would be applied by the android device manufacturer, and installed and run as a system service.


Can't able to see my asset

i unable to see my asset as it can viewed on stellar lumen

It would be nice to have more context. Which asset? What's wrong with it?


cannot get the email address of users, even when authenticated

Hi,
Hope you are all well !
I cannot get the email address of users, even if I am authenticated.
Any reason why ? what should I change ?
Authenticated user &wordpress.User{
  ID:         9,
  AvatarURL:  "",
  AvatarURLs: wordpress.AvatarURLS{
    Size24: "https://secure.gravatar.com/avatar/33e01b4739dbfb8dc5b074553a77a6cc?s=24&d=mm&r=g",
    Size48: "https://secure.gravatar.com/avatar/33e01b4739dbfb8dc5b074553a77a6cc?s=48&d=mm&r=g",
    Size96: "https://secure.gravatar.com/avatar/33e01b4739dbfb8dc5b074553a77a6cc?s=96&d=mm&r=g",
  },
  Capabilities:      map[string]interface {}{},
  Description:       "",
  Email:             "",
  ExtraCapabilities: map[string]interface {}{},
  FirstName:         "",
  LastName:          "",
  Link:              "https://eedama.org/blog/author/luc/",
  Name:              "luc",
  Nickname:          "",
  RegisteredDate:    wordpress.Time{
    Time: 1-01-01 00:00:00 UTC,
  },
  Roles:    []string{},
  Slug:     "luc",
  URL:      "",
  Username: "",
  Password: "",
  Locale:   "",
}
exit status 1

Any insights or help would be wonderful !
Cheers,
Luc

was missing the context attribute


Best way to remove asg without rebuilding all of them.

When I remove group-01 it changes the indexes and forces a rebuild of group-02 and group-03. Is there a recommended way to avoid that?
  worker_groups = [
    {
      name                     = "group-01"
      instance_type            = "r5.2xlarge"
    },
    {
      name                     = "group-02"
      instance_type            = "m5.4xlarge"
    },
    {
      name                     = "group-03"
      instance_type            = "m5.8xlarge"
    }
  ]

I don't think you can do that actually. But since Terraform 0.12.6, we can now use for_each in resources. With for_each the resource reference is not an indice anymore. This let us remote specific resource within a list or a map.
More info here:

https://www.terraform.io/docs/configuration/resources.html#when-to-use-for_each-instead-of-count
https://github.com/hashicorp/terraform/issues/14275

Maybe this will you as workaround https://github.com/hashicorp/terraform/issues/14275#issuecomment-360245405

Cool thanks!. Are there any plans to move to for_each?

we have an eks cluster with five worker groups (asg's).  i wanted to upgrade them from the 12.7 ami to the 12.10 ami.  based on https://docs.aws.amazon.com/eks/latest/userguide/migrate-stack.html, i tried these steps:

helm delete --purge cluster-autoscaler
in our eks/main.tf which uses this module, duplicate the asg's inside the worker_groups list and update the ami's on the new worker groups.  this means add 5 new asg's to the end of the list.
tf apply; confirm ten asg's on 2 different launch configs
run ./drain-asgs.sh which is

#!/bin/bash

set -e

K8S_VERSION=1.12.7
nodes=$(kubectl  get nodes -o jsonpath="{.items[?(@.status.nodeInfo.kubeletVersion==\"v$K8S_VERSION\")].metadata.name}")
for node in ${nodes[@]}
do
    echo "Draining $node"
    kubectl drain $node --ignore-daemonsets --delete-local-data
done

delete original asg's from worker_groups list in eks/main.tf.  this means the list is back to its original size of 5 and all using the new 12.10 ami.
tf apply
Plan: 5 to add, 5 to change, 20 to destroy.

because the worker_groups logic is index-based, a bunch of chaos ensues and the new asg's actually end up deleted.
sounds like using for_each would allow worker_groups mgmt to move away from index-based logic and will support removing groups from the list.

I would like to work on this, but it sounds like it will force everyone to move theirs resources in states.
I don't know how this can be painful for users.
Any thoughts ? @max-rocket-internet @dpiddockcmp ?

i had the same concerns about existing tf state, but fortunately our team is in a spot where we can rebuild all of our envs.  so i forked somewhere in between 6.0.1 and 6.0.2 and implemented using a map of maps for worker_group_launch_templates instead of a list. our team also had to split the eks control plane from the worker groups as flipping bits for the eks api endpoint access vars was causing all the asg's to roll (i believe due to naming and kubeconfig/auth-map.rendered dependencies).
here's an example of how our eks-worker-groups module looks:
   "${var.env}-${var.cluster_id}-infra-${data.aws_availability_zones.available.names[0]}-20191003" = {
     instance_type                 = "m5.large"
     asg_min_size                  = 1
     asg_max_size                  = 2
     key_name                      = var.ssh_key_name
     subnets                       = [ data.terraform_remote_state.vpc.outputs.private_subnets[0] ]
     kubelet_extra_args            = "--node-labels=k8s-env=${local.full-cluster-name},nodegroup=infra --register-with-taints=infra=true:NoSchedule"
     autoscaling_enabled           = true
     root_volume_size              = 1024
     termination_policies          = [ "OldestInstance" ]
     ami_id                        = "ami-05d586e6f773f6abf"
     tags = [{
       key = "worker-type"
       value = "infra"
       propagate_at_launch = true
     }]
   },```

i am planning on getting a public repo up that can at least provide a starting point if someone wants to see how i handled all the for_each's.  we also made a couple other adjustments that would make submitting a PR not really possible.  but really want to at least contribute the concept back.

oh yeah forgot to mention that upgrading the cluster via the steps i outlined above works really nicely.

There's no way around it, moving to a map of maps and for_each will be painful for everyone upgrading.
I've done it to a few unrelated plans as part of our 0.12 upgrade efforts. You can't simply use terraform state mv resource[0] resource["key"] for the first item as TF gets confused. You have to either drop and import, manually edit the state file or let TF delete and recreate the resources. Not sure if TF > 0.12.7 has improved that. Need to test what has changed in 0.12.10
A lot of short term pain for all. Would make life much easier for people who change their worker_groups.

You have to either drop and import, manually edit the state file or let TF delete and recreate the resources

Hmmm, sounds painful.

When I remove group-01 it changes the indexes and forces a rebuild of group-02 and group-03.

Is it not possible to use terraform state mv resource[1] resource[0] for this?

Unfortunately not @max-rocket-internet . Take a look:
First, I tried to just move it:
$ terraform state mv module.eks.aws_autoscaling_group.workers[1] module.eks.aws_autoscaling_group.workers[0]
Acquiring state lock. This may take a few moments...

Error: Invalid target address

Cannot move to module.eks.aws_autoscaling_group.workers[0]:
there is already a resource instance at that address in the current state.

Then, I tried to remove the resource from index 0 and try to move again:
$ terraform state rm module.sc-eks.module.eks.aws_autoscaling_group.workers[0]
Removed module.sc-eks.module.eks.aws_autoscaling_group.workers[0]
Successfully removed 1 resource instance(s).

$ terraform state mv module.eks.aws_autoscaling_group.workers[1] module.eks.aws_autoscaling_group.workers[0]
Move "module.eks.aws_autoscaling_group.workers[1]" to "module.eks.aws_autoscaling_group.workers[0]"

Error: Invalid target address

Cannot move to module.eks.aws_autoscaling_group.workers[0]:
module.eks.aws_autoscaling_group.workers does not exist in the
current state.

I was able to workaround by moving the index 0 to index 2 and then move index 1 to 0. After that, I just ran the apply command again to destroy the old workers.

I wanted to try and work on this, I started with the worker_launch_template and iterate from here.
If someone have the time I'd like some feedback/help here
I'm having issues with the coalescelist and getting this error:

  on aws_auth.tf line 13, in data "template_file" "launch_template_worker_role_arns":
  13:         lookup(data.aws_iam_instance_profile.custom_worker_group_launch_template_iam_instance_profile[eac
h.key], "role_name", ""
    |----------------
    | data.aws_iam_instance_profile.custom_worker_group_launch_template_iam_instance_profile is object with no
attributes
    | each.key is "default-eu-west-3c"

The given key does not identify an element in this collection value.

Despite using a lookup here, it stills tried to access the attribute on an empty map. I'm stuck here, I don't know how to have the same behavior as coalescelist but with two maps.

Looking into what's been done for the node_group the best way would be to merge everything beforehand from what I understand here: https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/modules/node_groups/locals.tf

What if we support both in parallel?
Add worker_groups_launch_template_map so that new users can start using the _map variable, while old users can remain on the old one and can try to transition in the future

Any updates to this issue?
I would like to have worker_groups as a map too. That way I can delete and add groups without rebuilding all others which indexes are higher. Also I can address them by names in worker_asg_names rather than indexes.
Several days ago I wanted to delete groups 0 and 1. After considering the plan Terraform gave me I just scaled them to 0 not to rebuild all other groups :)

To treat the worker_groups as a map would need extensive changes to the module. It will also require every user of the module to recreate all worker groups when upgrading.

This is still a problem, can we please keep this issue open?

Stale Bump :)

https://github.com/terraform-aws-modules/terraform-aws-eks/pull/858 or https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1366#event-5261340999 will solve this issue, but this potencially is breaking change for existing users and will require moving terraform state resources


Compatibility issues with redstone pen

The redstone lines of this module will charge each other with the redstone pen;And if there are only two redstone lines (no other blocks are connected), they will remain active unless they are disconnected or a separate redstone line is used

Yes, this is why wires -> vanilla redstone power only goes one way. I haven't been able to find a good way to prevent this kind of circular powering situation.
The best work around I've found is simply to put a Diode between the two mods' wires in the direction you want the signal to travel.


Report additional fields in validation stream

This branch was initially created by @nbougalis, who is currently too busy to shepherd the pull request through the review.  So I'm re-opening the pull request in a form where I can easily handle any requests for changes.
Overview
The HardenedValidations amendment introduces additional fields in validations:

sfValidatedHash, if present, is the hash the of last ledger that the validator considers to be fully validated.
sfCookie, if present, is a 64-bit cookie (the default implementation selects it randomly at startup but other implementations are possible), which can be used to improve the detection and classification of duplicate validations.
sfServerVersion, if present, reports the version of the software that the validator is running. By surfacing this information, server operators gain additional insight about variety of software on the network.

If merged, this commit fixes #3797 by adding the fields to the validations stream as shown below:

sfValidateHash as validated_hash: a 256-bit hex string;
sfCookie as cookie: a 64-bit integer as a string; and
sfServerVersion as server_version: a 64-bit integer as a string.

Type of Change

[X] New feature (non-breaking change which adds functionality)
[X] Tests (You added tests for code that already exists, or your new feature included in this PR)
[X] Documentation updates are required

Tagging @wilsonianb who originally opened #3797.

@miguelportilla, would you like to weigh in on this pull request?  Or are you happy enough with reviews from @cjcobb23 and @ximinez?  Whatever you'd like.  Thanks.

Private communications suggest that @miguelportilla is currently tied up with other matters.  Given that we have approval from two reviewers, I'm going to squash this branch and, assuming it passes CI after the squash, mark it as passed.


Deal with energy spikes while maintaining large time step

When using a 10 or 20fs timestep, in the course of a simulation there will be energy spikes, up to the order of 1E12 kJ/mol. This is more prevalent for higher epsilon value (~2kJ/mol and higher) and at higher temperature (>350K). This causes invalid heat capacities, as well as other issues in the analysis. I looked further into what was happening, and the structures corresponding to the extremely high energy are badly distorted (bond lengths of 100's of angstrom, etc). So it is not simply an error with the reporting of energies.
It also doesn't seem like it is an issue with the exchanges. Looking more closely at one case, one spike spans a period of 6 frames (600 time steps), upon which the system recovers, and there are no exchanges accepted involving that replica. The LangevinDynamicsMove we are using is not metropolized, a simulation period of 100 time steps will always be accepted, even if the energy blows up. It is only the exchange moves that are accepted/rejected.
So far I have tried using the GHMCMove instead (https://openmmtools.readthedocs.io/en/0.18.1/api/generated/openmmtools.mcmc.GHMCMove.html#openmmtools.mcmc.GHMCMove), which is a metropolized form of Langevin dynamics and also uses the BAOAB scheme (recall our discussion here https://github.com/choderalab/openmmtools/issues/480), and it seems to be working with the 20fs step (no energy spikes at all). Will need to test it out on more force field parameter combinations.
GHMCMove is quite a bit slower than LangevinDynamicsMove (about 3x slower), yet the alternative of moving down from 20fs to 5fs time step with LangevinDynamicsMove would be worse. Other options are:

Sticking with LangevinDynamicsMove and filtering out data associated with unusually high energy, defined by some cutoff - not ideal.
Try LangevinSplittingDynamicsMove (non-metropolized but uses BAOAB scheme)

So it looks like the reason for energy spikes was due to the harmonic bonds being too weak relative to the 5kJ/mol epsilon parameter I was using. Increasing from k_bond=1,000kJ/mol/nm^2 to 10,000 kJ/mol/nm^2 seems to solve the bad overlap issue. This is the improvement in the sidechain-backbone rdf:

For the weaker bond force constant, the beads were nearly on top of eachother to double up the strong nonbond interactions.
Turning on the angles and torsions, and using the 10,000 kJ/mol/nm^2 bonds, we see no issues with the energy or rdf using a 20fs time step (as we would expect - even with those stiff bonds, the period of vibration for the bonds using masses of 100 amu is ~400fs). It is a bit surprising that the 1000 kJ/mol/nm^2 was so bad, since it is close to the Martini value of 1250 kJ/mol/nm^2 for 72 amu particles, but values of up to 20,000 kJ/mol/nm^2 are used in literature to mimic constrained bonds.
The nonbonded exceptions look fine, though I did find a bug for the case of include_angle_forces=False, where the 1-3 interactions were still being excluded. Will fix that in a later PR.

Great detective work, @cwalker7!

t is a bit surprising that the 1000 kJ/mol/nm^2 was so bad, since it is close to the Martini value of 1250 kJ/mol/nm^2

But they are generally using lower epsilon.

Yep - I think we should be able to use the faster LangevinDynamicsMove with 20fs step with the stiff bonds now. I also tried 2,000 and 5,000 kJ/mol/nm^2 bonds, and neither is strong enough to avoid the spikes with eps=5kJ/mol.

seems to solve the bad overlap issue. This is the improvement in the sidechain-backbone rdf:

So the large accumulation of sidechain/backbone RDF at low energy is 1-2 connected sidechain/backbones?  The LG 1-2 interactions are off, so there is no LJ attraction between these two - but does packing them together like this increase the total amount of LJ interaction between 1-4 and greater LJ contacts?  I'm just trying to get a good physical picture.

close to the Martini value of 1250 kJ/mol/nm^2

Note that the larger bond lengths might also help, as with large bonds, you can't collapse sidechains and backbones down together.

I also tried 2,000 and 5,000 kJ/mol/nm^2 bonds, and neither is strong enough to avoid the spikes with eps=5kJ/mol.
Good checking.

I think we should be able to use the faster LangevinDynamicsMove with 20fs step with the stiff bonds now

Just wondering (since it's sometimes useful to run things until they break) what happens with 25 or 30 fs?

Just wondering (since it's sometimes useful to run things until they break) what happens with 25 or 30 fs?

Haven't tried to larger time step yet but it could work, good idea.

So the large accumulation of sidechain/backbone RDF at low energy is 1-2 connected sidechain/backbones? The LG 1-2 interactions are off, so there is no LJ attraction between these two - but does packing them together like this increase the total amount of LJ interaction between 1-4 and greater LJ contacts?

Yeah I would imagine it does. If we turn the bond angles off, then they will go towards the backbone bead to interact will both 1-3 backbone beads. The 1-4 interactions are harder to picture. We see strange grouping of beads like this:

Just wondering (since it's sometimes useful to run things until they break) what happens with 25 or 30 fs?

30fs leads to lots of spiking but can usually recover.
40fs fails very quickly
I'd say 20fs is a good choice then.

Sounds like a plan.  We should keep thinking about overall energetic setups that might help us identify better ways to put together CG models - but this sounds like it works for now just fine.


Add GTX 1650 Mobile

I referenced these:

https://www.techpowerup.com/gpu-specs/geforce-gtx-1650-mobile.c3367
https://www.techpowerup.com/gpu-specs/geforce-gtx-1650-mobile.c3633

Thanks @tolgacangoz

Thanks for merging!


Bug report - constantly crashing devices/app

Describe the bug
I get my tuya app crashed frequently (many times a day). I have latest experimental version but stable version is crashing to. I get the red excl.marks on deviced. 89666d73-8c01-4d51-9ef4-c320cf8925b4 report, I would like to know if there is my homey problem or app problem. Thank you.
To Reproduce
Steps to reproduce the behavior:
N/A
Expected behavior
Stop crashing devices
App and Homey version
What Homey version are you running? 10.0.1
What version of Homey firmware do you use? <IP_ADDRESS>1
What version of the Tuya Zigbee App are you using? 0.2.17
Screenshots
N/a
Additional context
Add any other context about the problem here.

I have not seen this error in any reports for quite some time, if it still happens please start a new issue and send me a fresh diagnostic report.


WIP: Optimize config applying

Fixes https://github.com/istio/istio/issues/33335

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
77478224186109cfa3faa720299270679b66afd0
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
77478224186109cfa3faa720299270679b66afd0
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Not sure if your run was lucky – looks like postsubmit is anywhere from 18m to ~25m, but seems like a really good improvement.
Maybe a future cleanup would be moving some of our traffic test logic into echotest since we essentially have 2 frameworks here.

Maybe a future cleanup would be moving some of our traffic test logic into echotest since we essentially have 2 frameworks here.

Strongly agree

@howardjohn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Follower notifications in feed / separate

Looking at twitter this morning, they have the follower notifications out into a separate feed - 'notifications', and roll things up by day - e.g. X people followed you on Jun-14.

We should consider this /cc @MikaelaB @dmorgantini - wouldn't be a difficult refactor seguir side.  We could keep these notifications on the same page though, or push into the profile.

You could also just do this in the feed itself (e.g. if you have multiple follow events on a page, just roll them all up and display them in single cards).

I wonder if this sort of thing is not the responsibility of seguir and rather up to the consuming application to decide how to render feed items, how feed items should be aggregated, etc?

Thought a separate 'feed' concept such as notifications_timeline, might be useful - though I'm not sure how it differs from the user_timeline so perhaps we should discuss.

We had planned for it to be separated out in early discussions then merged into one column for mobile. This was the mvp version. I think merging all follow into one card would be an elegant solution, but needs thinking out for 2nd follows.
On 17 Jul 2015, at 10:01, David Morgantini <notifications<EMAIL_ADDRESS>wrote:
Thought a separate 'feed' concept such as notifications_timeline, might be useful - though I'm not sure how it differs from the user_timeline so perhaps we should discuss.
—
Reply to this email directly or view it on GitHubhttps://github.com/cliftonc/seguir/issues/35#issuecomment-122222946.
This e-mail message, including any attachments transmitted with it, is CONFIDENTIAL and may contain legally privileged or private information. This message is intended solely for the use of the individual or entity to whom it is addressed.
If you have received this message in error, please notify the sender or<EMAIL_ADDRESS>immediately and delete it from your system. You should not copy, store or use this email or any attachment(s) for any purpose, nor disclose their contents to any other person.
E-mail is not a 100% virus-free or secure medium. Whilst TSL scans all communications for viruses or other malicious software, we do not guarantee that this message is virus-free and accept no liability for any potential loss or damage that may arise as a result of receiving, storing and reading this message and any attachment(s).  It is your responsibility to ensure that viruses do not adversely affect your system and that your messages to us meet your own security requirements.
We reserve the right to read any e-mail or attachment entering or leaving our systems without notice.
TSL Education is a limited company registered in England and Wales (Company number 02017289) with its registered office at 26 Red Lion Square, London, WC1R 4HQ.

Ok - I'll leave as a client side feature for now, and we can revisit later.


Create issues to convert GLSL to HLSL

We can either use this ticket as a bucket to convert all GLSL to HLSL or we can create an issue per set of shaders. The end goal would be to have an HLSL counterpart for as many shaders as possible
Acceptance Criteria

Decide how we want to break down the workload
Close when GLSL shaders have a HLSL counterpart

I think we can close this. I already converted lots of shaders to HLSL and document my progress in #961.

Closing this for now, see #1014


MathProgBase require

You should put tight bounds on the MathProgBase line in REQUIRE, e.g.,
MathProgBase 0.5 0.6

MPB 0.6 may have breaking changes, and this line will prevent the package manager from upgrading MPB until ConicIP is updated.

fixed, thank you.


[REQUEST] Use Solid/Ageless while The Giving Land is active

Could be an option in use conditions of either menu.

It is possible right now, just check "Use when gathering crystals" box in the settings

The problem is that it uses it even when Giving Land is not active. The yield check doesn't work because Giving Land shows "1+?" yield.


Monorepo version maintainers minutes jul24

As ordered by @mashehu
Note npm run dev didn't work... so I don't know if this is renering properly

@mashehu @ewels this looks off, can you fix?

@mashehu @ewels feel free to merge when ready :)

and the dev preview command is now npm run dev -w sites/main-site

@nf-core-bot fix linting


mailto links break Sammy get()

Anytime a mailto link is clicked, the Sammy application will no longer update on hash changes. Breaks on all browers. Others also seem to be experiencing this issue – http://groups.google.com/group/sammyjs/browse_thread/thread/ca7c898d0f995756
Current workaround: I listen for all mailto clicks and restart the Sammy app via a delayed method call once a link is clicked.

When a mailto link is clicked, a window "onbeforeunload" event is fired. In Sammy, this event is binded to the unload() function.
Hop it help.


Added new city config for NYC

Ran pipeline and tested flask app, but doesn't show modes yet in the dropdown menu. Any thoughts why?

Sorry for the delay here: Do you mean in the showcase at insightlane.org? I believe we need to update that ourselves to make it show in there.  @j-t-t  @terryf82
If it's not showing locally, I can try and see why.  It might need some kind of additional config.

YAML configs (like the one in this P.R) are relevant to running the pipeline and generating output files (predictions & crashes).
Once those have been generated, the process for now is for me to upload them to Google Cloud, create an entry in the JS config and then re-deploy the showcase. @spbail - are the output files available somewhere I can download? (we usually use data.world for sharing but I can grab them from anywhere you like).

@bpben @terryf82 Apologies for the delay. I had to abandon my dev setup on my old laptop, but I will attempt to get this running again next week and will share the output. My question about the dropdown was that the output didn't show up in my local version, so yes, I'm thinking there should be a config I couldn't find to make things show up locally?

I would expect the dropdown should work. It's not immediately obvious to me what would be wrong. Can you point me to the crash dataset you're using and I can try to run it using your config on my machine?

@spbail Are you still interested on working to onboard NYC? If not, no worries, do you mind providing us the crash dataset you're working on and we can see if we can finish the onboarding process.  By the way, we've move to a new slack if you want to join us there: https://join.slack.com/t/insightlane/shared_invite/zt-ewlvaic7-ymYlps33v2M2~RhC4DFRGg

Codecov Report

Merging #299 (6edc5c8) into master (1259061) will decrease coverage by 0.69%.
The diff coverage is n/a.

:exclamation: Current head 6edc5c8 differs from pull request most recent head 0e44627.  Some notes:

I downloaded the collision data from https://data.cityofnewyork.us/Public-Safety/Motor-Vehicle-Collisions-Crashes/
I uploaded a small notebook with some exploration of the data here: https://drive.google.com/file/d/1rBVBs-TMAIrxAwSlz6OBeeljqtp0GXvv/view?usp=sharing

I also pinged you in the new Slack, happy to pair with someone to get this set up.

Dropdown seems fine, so merged


feat: render content type image

Render content type image

Changed

changed

I just want to tank you for this PR, and inform you that SVG support has moved from this repository to one that is more appropriate: https://github.com/mono/SkiaSharp.Extended
This new repository will make it easier to develop libraries that use SkiaSharp, but don't really have to be built with the main library. In addition, there will be no need to first build all the native code, just to test a fix for some SVG case.
Please open a new PR against this new repository, and we will be happy to merge it in.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v5.4.128",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6d120ab4dc39a543c6b63361e1d0541c382900a3"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "6d120ab4dc39a543c6b63361e1d0541c382900a3",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: ll_temac: Make sure to free skb when it is completely used\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.128 by commit 6d120ab4dc39a543c6b63361e1d0541c382900a3. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000933


Alignment is not correct.

Alignment of given images are not correct. I want to fix this issue.
Please assign this issue to me under gssoc-extd and hacktoberfest.

@Kajalmehta29  you can work on this issue.

Hey @Tejashri-Taral  @harikasayani  Please add level label too


Dependency package @types/inquirer has a new version available

We have identified a dependency on version 8.2.10 of @types/inquirer. A new version (9.0.7) is available for upgrade.
Following are the steps to upgrade package dependency.

Understand the breaking changes between the version being used and the version you want to upgrade to.

Identify all packages that take a dependency on this package.

Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.

Run rush update to ensure the new version is pulled in.

Make relevant changes to absorb the breaking changes.

Repeat steps 3 to 5 for each of the packages that have a dependency on this package.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.34575114,Service Bus:0.15636165,Azure.Identity:0.045208707'

PR #29155


Variable Data in trouble

Good Afternoon sir. it's hard to say that the variable that uses ".obs" in each of the variables didn't update the state. for example, i use var action = "".obs. next, I have to change action.value = "hello". but, it didn't update data although I have used Obx(() {}) inside of the widget build. I hope this information too very clear about my problem. thank you in advance

Is there any test code, and which getx version and flutter version are used?


The llm model must be served by triton inference server' ensemble scheduler?

Can i use a single model in triton model repository?

do tokenization and de-tokenization yourself?

do tokenization and de-tokenization yourself?

yes. custom backend based on triton python backend.

If you use bls model like https://github.com/triton-inference-server/tensorrtllm_backend/blob/main/all_models/inflight_batcher_llm/tensorrt_llm_bls/config.pbtxt, I think it's compatible as the model inputs are compatible.

The inputs and outputs of my custom model is above. How can i adjust my model to make it compatible?


Output HTML for generated favicons

When using the CLI's favicon generator, it would be helpful to output the HTML required to use the generated favicons

So there's one issue I've run into with this. Since I originally allowed an optional argument for a custom output target, other than src/client/public/favicons, it makes determining the final public path that the HTML should use a bit tricky. By default, the favicons are generated to ./src/client/public/favicons which will ultimately be built to ./public/favicons and then be referenced in a template with {{ PUBLIC_FILES_HOST }}/public/favicons.
I'm not sure the best way to determine the public path if a custom output directory was provided. In hindsight, that argument for a custom output directory probably wasn't necessary, but I don't know if we want to remove it now since that would technically be a breaking change.
@lxndrdagreat Any thoughts?


docs(spanner): set max_delay to 16s

Update the custom retry sample to use a max retry delay of 16 seconds, as that is smaller than the total timeout of 60 seconds. The current values are slightly confusing for users, as it could give the impression that retry delays are not counted towards the total timeout.

This change is

/gcbrun

Thanks for the PR.  It all looks good to me, but I will let @devbww decide as he owns this code.

Thanks for the PR. It all looks good to me, but I will let @devbww decide as he owns this code.

It's fine with me.  I'm only waiting to see if it exits draft mode.


Add multilevel wildcard support

Hi. If you don't mind I would also like to suggest this patch to add feature allowing developer to subscribe topics ending with multilevel wildcard (#). Also fixed the pom.xml so that maven will actually run the tests I added support last time.

Greate, thankyou! But i think it's better to modify it here.
    private static String replaceSymbols(String topic) {
        StringBuilder sb = new StringBuilder();
            ...
                case '+':
                    sb.append("[^/]+");
                    break;
+               case '#':
+                  sb.append(".*");
+                  break;
                default:
                    sb.append(ch);
            }
        }
-      return sb.toString().replaceAll("/#$", "/.*");
+      return sb.toString();
    }

Greate, thankyou! But i think it's better to modify it here.
    private static String replaceSymbols(String topic) {
        StringBuilder sb = new StringBuilder();
            ...
                case '+':
                    sb.append("[^/]+");
                    break;
+               case '#':
+                  sb.append(".*");
+                  break;
                default:
                    sb.append(ch);
            }
        }
-      return sb.toString().replaceAll("/#$", "/.*");
+      return sb.toString();
    }

Can do like that also, but I think it was more correct with replaceAll, since # only works as wildcard if it's alone or the topic ends with /#. Would have needed to change the loop more to code that in.

topic is verified on line 45 use MqttTopic.validate(), so if it doesn't conform to the specification, it will throw an exception.

topic is verified on line 45 use MqttTopic.validate(), so if it doesn't conform to the specification, it will throw an exception.

Ah, sorry. Missed that. Then definitely, it's the best now. Thank you!


Remove Lazy uses on NativeAOT

Only needed in two internal types, we can use simple manual caching instead and trim the type away.

Saves 7 KB, I'll take it ahah


schema/fs: Drop *.go files

With:
$ go get -u github.com/mjibson/esc
$ make schema/fs.go

now that #538 has landed.

while i like this idea, this also means the code can not be go getten and vendor'ed, right?

On Thu, Mar 09, 2017 at 11:07:37AM -0800, Vincent Batts wrote:

while i like this idea, this also means the code can not be go getten and vendor'ed, right?

This has no impact on ‘go get’, since all the schema/*.go is still
there.  All I'm doing is removing *.go which had been bundled into
fs.go.  All we use fs.go for is the *.json files, and those are
still there 1.

k. Prolly should add it to .gitignore too

Prolly should add it to .gitignore too

?  fs.go is still in version control after this commit.  I an only removing some unused content from fs.go.  What would I add to .gitignore.

i misunderstood. I thought (hoped?) you meant that schema/fs.go is removed and only generated as needed.

...only generated as needed

Well, only generated when .json changes (#538) should help a bit ;).

LGTM

I thought (hoped?) you meant that schema/fs.go is removed and only generated as needed.

we could try this elsewhere but this change is fine for now

LGTM


Not working with custom texts

I have copied and pasted the content of this blog https://codeforgeek.com/2015/01/nodejs-mysql-tutorial/ and passed it as a string in code below.
var retext = require('retext');
var keywords = require('retext-keywords');
var nlcstToString = require('nlcst-to-string');
var phraseData2 = "string of that web page";
retext()
  .use(keywords)
  .process(phraseData2, function (err, file) {
    if (err) throw err;

    console.log('Keywords:');
    file.data.keywords.forEach(function (keyword) {
      console.log(nlcstToString(keyword.matches[0].node));
    });

    console.log();
    console.log('Key-phrases:');
    file.data.keyphrases.forEach(function (phrase) {
      console.log(phrase.matches[0].nodes.map(nlcstToString).join(''));
    });
  }
);

it returns blank for keywords and phrases.

@codeforgeek Does the example in the readme work?

Yes that worked.

And what text did you paste in? I need a whole example.

Sure. Here it is.
Node.js and MySQL is one of the necessary binding needed for any web application. MySQL is one of the most popular open source database in world and efficient as well. Almost every popular programming language like Java or PHP provides driver to access and perform operations with MySQL. In this tutorial i am trying to cover code for learning and code for production. So if you know this already and looking for ready made code for production. Click here to jump there directly. Introduction: Node.js is rich with number of popular packages registered at package registry called NPM. Most of them are not so reliable to use for production but there are some on which we can rely upon. For MySQL there is one popular driver called node-mysql. In this tutorial i am going to cover following points related to Node.js and MySQL. Sample code to get started. Code for Production. Testing concurrent users. Sample code to get started. Project directory: ---node_modules -----+ mysql -----+ express ---index.js ---package.json package.json { 'name': 'node-mysql', 'version': '0.0.1', 'dependencies': { 'express': '^4.10.6', 'mysql': '^2.5.4' } } Install dependencies using npm install Here is sample code which connects to Database and perform SQL query. var mysql = require('mysql'); var connection = mysql.createConnection({ host : 'localhost', user : '< MySQL username >', password : '< MySQL password >', database : '' }); connection.connect(); connection.query('SELECT * from < table name >', function(err, rows, fields) { if (!err) console.log('The solution is: ', rows); else console.log('Error while performing Query.'); }); connection.end(); Make sure you have started MySQL on default port and changed the parameter in above code then run this code using node file_name.js Code for production : Above code is just for learning purpose and not for production payload. In production scenario is different, there may be thousands of concurrent users which turns into tons of MySQL queries. Above code won’t run for concurrent users and here is a proof. Let’s modify our code little bit and add Express routes in that, here it is. test.js ( Change database settings in code ) var express = require('express'); var mysql = require('mysql'); var connection = mysql.createConnection({ host : 'localhost', user : 'root', password : '', database : 'address_book' }); var app = express(); connection.connect(function(err){ if(!err) { console.log('Database is connected ... nn'); } else { console.log('Error connecting database ... nn'); } }); app.get("/",function(req,res){ connection.query('SELECT * from user LIMIT 2', function(err, rows, fields) { connection.end(); if (!err) console.log('The solution is: ', rows); else console.log('Error while performing Query.'); }); }); app.listen(3000); Install siege in your system. I use this command to install it in Ubuntu. apt-get install siege then run our node and server and following command. node test.js siege -c10 -t1M http://localhost:3000 Assuming you are running Node server on Port 3000. Here is the output. Node and mysql In above code, we are allowing it to run for standalone connection i.e one connection at a time but reality is bit different. You may get 100 or 1000 connection at one particular time and if your server is not powerful enough to serve those request then at least it should put them in queue. Pool connection in MySQL : Connection Pooling is mechanism to maintain cache of database connection so that connection can be reused after releasing it. In Node mysql, we can use pooling directly to handle multiple connection and reuse the connection. Let’s write same code with pooling and check whether it can handle multiple connection or not. test.js var express = require('express'); var mysql = require('mysql'); var app = express(); var pool = mysql.createPool({ connectionLimit : 100, //important host : 'localhost', user : 'root', password : '', database : 'address_book', debug : false }); function handle_database(req,res) { pool.getConnection(function(err,connection){ if (err) { res.json({'code' : 100, 'status' : 'Error in connection database'}); return; } console.log('connected as id ' + connection.threadId); connection.query('select * from user',function(err,rows){ connection.release(); if(!err) { res.json(rows); } }); connection.on('error', function(err) { res.json({'code' : 100, 'status' : 'Error in connection database'}); return; }); }); } app.get("/",function(req,res){- handle_database(req,res); }); app.listen(3000); Run the app using node test.js and fire 10 concurrent users for 1 minute using siege by using this command. siege -c10 -t1M http://localhost:3000 Here is output. Code is stable ! Final comments : Siege is really powerful tool for testing server under pressure. We have created 100 connection limit in code, so you might be wondering that after 100 concurrent connection code will break. Well let me answer it via code. Fire 1000 concurrent user for 1 minute and let’s see how our code reacts. siege -c1000 -t1M http://localhost:3000 If your MySQL server is configured to handle such traffic at one socket then it will run and our code will manage the scheduling of concurrent connection. It will serve 100 connection a time but rest 900 will be in queue. So code will not break. Conclusion : MySQL is one of widely used database engine in world and with Node it really works very well. Node-mysql pooling and event based debugging is really powerful and easy to code. Further reading: Node-mysql Github Pro MERN Stack: Full Stack Web App Development with Mongo, Express, React, and Node

...work for me:
var retext = require('retext');
var keywords = require('retext-keywords');
var nlcstToString = require('nlcst-to-string');

var doc = `Node.js and MySQL is one of the necessary binding needed for any web application. MySQL is one of the most popular open source database in world and efficient as well. Almost every popular programming language like Java or PHP provides driver to access and perform operations with MySQL. In this tutorial i am trying to cover code for learning and code for production. So if you know this already and looking for ready made code for production. Click here to jump there directly. Introduction: Node.js is rich with number of popular packages registered at package registry called NPM. Most of them are not so reliable to use for production but there are some on which we can rely upon. For MySQL there is one popular driver called node-mysql. In this tutorial i am going to cover following points related to Node.js and MySQL. Sample code to get started. Code for Production. Testing concurrent users. Sample code to get started. Project directory: ---node_modules -----+ mysql -----+ express ---index.js ---package.json package.json { 'name': 'node-mysql', 'version': '0.0.1', 'dependencies': { 'express': '^4.10.6', 'mysql': '^2.5.4' } } Install dependencies using npm install Here is sample code which connects to Database and perform SQL query. var mysql = require('mysql'); var connection = mysql.createConnection({ host : 'localhost', user : '< MySQL username >', password : '< MySQL password >', database : '' }); connection.connect(); connection.query('SELECT * from < table name >', function(err, rows, fields) { if (!err) console.log('The solution is: ', rows); else console.log('Error while performing Query.'); }); connection.end(); Make sure you have started MySQL on default port and changed the parameter in above code then run this code using node file_name.js Code for production : Above code is just for learning purpose and not for production payload. In production scenario is different, there may be thousands of concurrent users which turns into tons of MySQL queries. Above code won’t run for concurrent users and here is a proof. Let’s modify our code little bit and add Express routes in that, here it is. test.js ( Change database settings in code ) var express = require('express'); var mysql = require('mysql'); var connection = mysql.createConnection({ host : 'localhost', user : 'root', password : '', database : 'address_book' }); var app = express(); connection.connect(function(err){ if(!err) { console.log('Database is connected ... nn'); } else { console.log('Error connecting database ... nn'); } }); app.get("/",function(req,res){ connection.query('SELECT * from user LIMIT 2', function(err, rows, fields) { connection.end(); if (!err) console.log('The solution is: ', rows); else console.log('Error while performing Query.'); }); }); app.listen(3000); Install siege in your system. I use this command to install it in Ubuntu. apt-get install siege then run our node and server and following command. node test.js siege -c10 -t1M http://localhost:3000 Assuming you are running Node server on Port 3000. Here is the output. Node and mysql In above code, we are allowing it to run for standalone connection i.e one connection at a time but reality is bit different. You may get 100 or 1000 connection at one particular time and if your server is not powerful enough to serve those request then at least it should put them in queue. Pool connection in MySQL : Connection Pooling is mechanism to maintain cache of database connection so that connection can be reused after releasing it. In Node mysql, we can use pooling directly to handle multiple connection and reuse the connection. Let’s write same code with pooling and check whether it can handle multiple connection or not. test.js var express = require('express'); var mysql = require('mysql'); var app = express(); var pool = mysql.createPool({ connectionLimit : 100, //important host : 'localhost', user : 'root', password : '', database : 'address_book', debug : false }); function handle_database(req,res) { pool.getConnection(function(err,connection){ if (err) { res.json({'code' : 100, 'status' : 'Error in connection database'}); return; } console.log('connected as id ' + connection.threadId); connection.query('select * from user',function(err,rows){ connection.release(); if(!err) { res.json(rows); } }); connection.on('error', function(err) { res.json({'code' : 100, 'status' : 'Error in connection database'}); return; }); }); } app.get("/",function(req,res){- handle_database(req,res); }); app.listen(3000); Run the app using node test.js and fire 10 concurrent users for 1 minute using siege by using this command. siege -c10 -t1M http://localhost:3000 Here is output. Code is stable ! Final comments : Siege is really powerful tool for testing server under pressure. We have created 100 connection limit in code, so you might be wondering that after 100 concurrent connection code will break. Well let me answer it via code. Fire 1000 concurrent user for 1 minute and let’s see how our code reacts. siege -c1000 -t1M http://localhost:3000 If your MySQL server is configured to handle such traffic at one socket then it will run and our code will manage the scheduling of concurrent connection. It will serve 100 connection a time but rest 900 will be in queue. So code will not break. Conclusion : MySQL is one of widely used database engine in world and with Node it really works very well. Node-mysql pooling and event based debugging is really powerful and easy to code. Further reading: Node-mysql Github Pro MERN Stack: Full Stack Web App Development with Mongo, Express, React, and Node`;

retext()
  .use(keywords)
  .process(doc, function (err, file) {
    if (err) throw err;

    console.log('Keywords:');
    file.data.keywords.forEach(function (keyword) {
      console.log(nlcstToString(keyword.matches[0].node));
    });

    console.log();
    console.log('Key-phrases:');
    file.data.keyphrases.forEach(function (phrase) {
      console.log(phrase.matches[0].nodes.map(nlcstToString).join(''));
    });
  }
);

Yields:
Keywords:
code
MySQL
connection
database
users
var

Key-phrases:
code
MySQL
connection
users
function

How come.
I am getting this
node keyword.js
Keywords:
Key-phrases:

Probably related to older versions of dependencies? Or Node?

Copy pasted your code and it worked!
What was I doing wrong? Any guess?

Dunno? You didn’t provide the whole code so I’m not sure?


Unable to open SQLite database

Hey Mike,
Thanks for this script! It's super annoying having to manually copy 2FA codes from my phone so hopefully, this will speed things up.
Unfortunately, I couldn't get this script to work. At first, I was simply getting UnhandledPromiseRejectionWarning errors because there is no catch block on the open() at line 43.
After adding the catch, it showed some more details on the error and got rid of the promise rejection errors:
[Error: SQLITE_CANTOPEN: unable to open database file] {
  errno: 14,
  code: 'SQLITE_CANTOPEN'
}

Let me know if you need more details!

thanks for the report! can you pull the latest code? I changed the open flag to read-only (in case there's a permissions issue)

thanks! still getting the same error unfortunately

Hey Mike,
Thanks for this awesome script!
I had the same error as Mehedi.
The solution was to enable "Full Disk Access" in the macOS settings (for iTerm2):
https://osxdaily.com/2018/10/09/fix-operation-not-permitted-terminal-error-macos/
Now it works like a charm.
I'm looking forward to your next projects.
Thanks again,
Julian

Thank you! I added instruction to the README.


Add support for two factor auth

It's important to add support for two-factor auth accounts. I noticed about it when I tried to upload a single gist and the app threw me an error. This because my account has two-factor auth. I'll be working on that if you want 👍

It will be cool. I will suggest to have options for this. Because some don't have 2 factor authentication.

The gists lib don't have support for a two-factor account. Because of this, they recommend using the token instead. I'll be implementing in list command and edit command.


⚠ Bofrost.be has degraded performance

In 650184b, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 837 ms

Resolved: Bofrost.be performance has improved in 6c56a20.


Fix tbn uv shader generation using clearcoat

This PR fixes an invalid shader generation for this gltf test model.
The shader code for calculating tangent basis for material "ClearcoatNormalTest1Mat" was accessing an incorrect set of uvs.

NOTE: the gltf test model still does not render correctly. However loading it no longer results in shader compilation error.


Query/Question: Streaming web app slot deployment logs

Query/Question
We are getting very often java.net.SocketTimeoutException: timeout exception when calling the following API for streaming web app slot deployment logs,
https://github.com/Azure/azure-libraries-for-java/blob/f7875032154af14671484548d4f4c223c7d7e079/azure-mgmt-appservice/src/main/java/com/microsoft/azure/management/appservice/WebAppBase.java#L441
Is there any other way for streaming web app slot deployment logs by using Azure SDK for java?  Any advice on how to consume this streaming API. Thanks in advance!

Thanks for filing this question, @ivan-83.  Someone from the Management Plane SDK team will follow up with you shortly.

@ivan-83
Please consider using the new lib here https://aka.ms/azsdk/java/mgmt
For streaming, you might want to increase the READ timeout of the HttpClient, as streaming from webapp can have silence upto 2min. E.g.
HttpClient.createDefault(new HttpClientOptions().setReadTimeout(Duration.ofMinutes(3)));

Thanks, @weidongxu-microsoft for your response.  Quick question, are new libs/lib have full support for Azure App Services, VMSS, ARM, Bluprint templates, Resources...? I mean are libs/lib fully backward compatible or it is still in progress?
And, this is a migration guide to follow up, right? https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/docs/MIGRATION_GUIDE.md

@ivan-83
I am not sure about "Bluprint templates", I can find it for you if you have package name. Others is under "azure-resourcemanager".
Yes, migration guide is https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/docs/MIGRATION_GUIDE.md
Code is almost same, exception namespace change.
Other difference would be authentication, and some error handling.

Thank you @weidongxu-microsoft for confirmation. I've checked for Azure Blueprints templates but it seems APIs are not implemented/supported by java Azure SDK lib https://docs.microsoft.com/en-us/azure/governance/blueprints/

@ivan-83
I see. I think it does not have any Java SDK, old or new.
The spec should be here:
https://github.com/Azure/azure-rest-api-specs/tree/main/specification/blueprint/resource-manager
If you do need a Java SDK on blueprint, would you open another issue for it? I would need to contact service to confirm the api-version and get their blessing for a Java SDK.

Thank you @weidongxu-microsoft based on all of this we can safely do the migration on azure-resourcemanager-resources SDK. We will check for Azure Blueprint. You can close the ticket.

@ivan-83
I've marked the issue as addressed. If you still see problem with streaming logs, feel free to update/reopen the issue.


Update display if empty pointcloud2 is published

Currently, a PointCloud2 display keeps showing the old point cloud if an empty point cloud message is published. I consider this a bug, since rviz still shows old data which is invalid in the meantime.

Thanks for the report and pr, I'll investigate it asap. If you have time to provide it, a simple bag file that reproduces the problem would make it easier for me to test this.
As you can imagine, this is sensitive code (a break in this code would affect a lot of users), so I'll have to be quite cautious with it. If any other point cloud users can +1/-1 this I would appreciate it too.

Sure, attached you will find a bag publishing some points on /point_cloud followed by an empty point cloud.
test_pointcloud_2017-01-10-10-20-10.bag.zip

Sorry it took me so long to get back to you. I've reproduced what you've described and that your patch fixes it. Thanks for giving a clear description and a reproducible bag, makes my job a lot easier :smile:!
I'll still do a code review before merging, but it's looking good so far.

Backported in https://github.com/ros-visualization/rviz/pull/1110


Support for newer versions of Python (3.11, 3.12)

Currently, it's not possible to install Enterprise from the master branch, or using pip or conda, on Python 3.11, (although it is possible if you install from the nanograv:dev branch), and it's not possible to install on Python 3.12 at all (at least, without first patching the code to remove the version cap in setup.py). This can result in a situation where trying to install packages that depend on Enterprise (e.g., enterprise_extensions or pint_pal) on these newer Python versions results in a very old version of Enterprise (that didn't have a cap on the Python version) being installed, and ultimately in an unsolvable environment.
I ran into this in trying to set up an environment for the next NANOGrav data release, where we'd want something like an anaconda-env.yaml file or similar, and are trying to use the most recent Python version we can, so having a tagged release on PyPI / conda-forge that supports these newer Python versions would be ideal. I created an older issue about Python 3.11 support back in October (#350), which is now closed as completed, but the changes have only made it to the nanograv:dev branch, and not into a release.
It's possible that Enterprise could support Python 3.12 simply by lifting the version cap in setup.py, but I don't know if that will cause other things to break.

We should just merge dev into master, and do a new release. It's overdue

I was able to install enterprise:dev on py312 just by removing the limit in setup.py

There is now a new version of libstempo (v2.4.7) that should work for Python 3.11/3.12. The PyPI release is currently pinned for NumPy <2.0, but I'm planning to generate a NumPy 2.0 compatible version (probably v2.5.0) soon, which I expect would have to only be Python >=3.9 compatible.

Is there anything holding this back? This prevents us from updating the IPTA environments to Python 3.11 because of the strict setup.py restriction.
~ Joe G.


cmd/statspusher - Wrap errors

Description:
Issues affected:

Relates to #308

This change is

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Add support for database provided atomic operation

当前使用版本(必须填写清楚，否则不予处理)
3.2.0
In MySQL and Postgres, we use the syntax like insert on duplicate key do nothing or insert on duplicate key update to leverage the atomic guarantee that database provided.
We don't have to create a new standalone transaction and deal with several levels of isolation which is really hard to understand and really vulnerable.
Could you please add support for this kind of statement?

Suggest you to define a custimized base method, see sample


Identity 1.2

Issue Link:

major changes in the new identity

using new identity contract
removed identity registry
removed CentID
introduced DID as new identifier
removed all waiting for events gocelery tasks
removed identity struct
new version of anchor repository contract
added support for execute method (proxy contract)
new key purposes
new service for factory contract

calculation of the identity contract address

one service for identity contract


Need attention

Hello @tdurieux
Sorry to bother you with this new issue, but it has been a long time since you have replied to any of my updates.
Since the program is heading towards the end, I just wanna know that are you still tracking me?
If yes, then please let me know in this thread. An emoji/reaction will also be sufficient. 😃
Best
Abhay

Sorry I had a busy week, i will follow your progress with more attention :)


Albany, NY

DUE TO HIGH VOLUME EMPTY ISSUES WILL BE IMMEDIATELY CLOSED. PLEASE PROVIDE ALL INFORMATION. THANK YOU!!!! :^)
******* A subject message for the email
******* A list of emails (at least one) for the government officials you’d like to receive the message
******* A detailed message concerning the budgeting decisions that are at stake in your community
See our current links for examples at https://defund12.org.
Thank you!!

DUE TO HIGH VOLUME EMPTY ISSUES, OR ISSUES MISSING THE FOLLOWING INFORMATION WILL BE IMMEDIATELY CLOSED. THANK YOU!

A subject message for the email
A list of emails (at least one) for the government officials you’d like to receive the message
A detailed message concerning the budgeting decisions that are at stake in your community
Please read more about our email style guidelines here.

If this information is copied from an external source please provide a link to the original source.
See our current links for examples at https://defund12.org.
Thank you!!


su: user does not exist when tried to launch the wsl.

I'm getting su: user does not exist when tried to launch the wsl after installing main build.
I didn't face this issue in build21286 when installed earlier. Any idea?

I got this error when installing via windows

That's why went with manual installation on wsl and now facing the above issue. Please help


readme file referring to non-existing document

Describe the bug
README.md in the section "CLI usage with Docker" still refers to streetlights.yml that seem was deleted on tests/docs.
How to Reproduce

clone repository
follow guide to execute
docker run --rm -it \ -v ${PWD}/test/docs/streetlights.yml:/app/asyncapi.yml \ -v ${PWD}/output:/app/output \ asyncapi/generator -o ./output asyncapi.yml @asyncapi/html-template --force-write

https://github.com/asyncapi/generator/blob/master/README.md#cli-usage-with-docker
Expected behavior
Update reference to document dummy.yml for example

@apaezg Thanks a lot Antonio. Would you like to open a PR for that? it just needs to be changed to point to the dummy file instead of streetlights

@apaezg Thanks a lot Antonio. Would you like to open a PR for that? it just needs to be changed to point to the dummy file instead of streetlights

Hi @derberg, I think I have just opened the PR properly. It is my very first time contributing to an open source project, so, if there's anything wrong, sorry in advance, and let me know to fix it.

@apaezg first and perfect!!! thanks so much mate!


README problems

Hi there,
This looks like a great plugin.
I noticed some problems, when setting up according to the readme:

the terminal settings:

	term = {
		height = 0.7,
		width = 0.5,
		type = "smart",
		border = "single",
		jump_to_end = true,
		auto_close = false,
	},

should use kind instead of type, since that's what you use in your code.

it isn't mentioned anywhere that you require a global key in the custom_recipes table.  This is even true for your premade custom recipes require'recipe.ft'. They also don't contain the global and thus you get a bunch of errors, so you should change those, too or add a guard when using the global key in your code.

Thanks for the great work. Keep it up :)

Thanks for noticing it.
Yes, the global key should be nil checked. I am using a custom recipes in my neovim config, which is why I never encountered the issue

https://github.com/ten3roberts/recipe.nvim/tree/dev
I am currently restructuring to allow a more flexible and easier to extend library.
The new system allows you to write your own providers, or use the builting ones such as recipes.json or hardcored recipes.
This is similar to nvim-cmp sources, and will allow things such as vscode tasks, and rust-analyzer targets, and much much more.
The terminal settings are problematic because some are in term, but some are broader to the recipe and thus outside, like restart. I now use a component based architecture which will bring the best of both worlds.


[FEATURE REQUEST]: Add StatsD Exporter for Airflow --> Prometheus

Details

[x] Add Python dependency to Airflow image: pip install 'apache-airflow[statsd]' ✅ https://github.com/USACE/airflow-config/commit/d2bb7b2e8633049fc6c4dbe4d63fae4ae62be634
[x] Add environment variables to Airflow services

[x] Scheduler
[x] Webserver
[x] Worker

    AIRFLOW__METRICS__STATSD_ON: True
    AIRFLOW__METRICS__STATSD_HOST: airflow-statsd-exporter
    AIRFLOW__METRICS__STATSD_PORT: 9125
    AIRFLOW__METRICS__STATSD_PREFIX: airflow

[x] Add environment variable to Prometheus Sidecar (airflow-statsd-exporter.localvpc)
https://github.com/USACE/castle-cloud-metrics/blob/develop/docker-compose.yml#L23
[x] Add repository for airflow statsd exporter
[x] Add statsd service
[x] Github workflows for airflow-statsd-exporter

Deployments

[x] Develop Environment
[ ] Stable Environment

References

Airflow docs: https://airflow.apache.org/docs/apache-airflow/stable/logging-monitoring/metrics.html

Initial configuration complete. Monitoring services to confirm everything is working and we can adjust settings as necessary.

This appears to be working as designed per review of develop- grafana instance and newly available metrics.  @adamscarberry, when convenient, can you confirm that everything looks good from your vantage point?  If so, thinking we can deploy to the stable environment and close the task.

Thanks @brettpalmberg for setting this up.
Unfortunately, I'm not seeing all the expected metrics.
Examples:

dag_file_refresh_error
scheduler.tasks.running
scheduler_heartbeat
executor.running_tasks

There are many more missing, these were just examples of missing metrics we would like to use.

correct, looks like all the dag and task instance (ti) metrics are available.

All metrics are sending now after bouncing Airflow containers (I bet bouncing the scheduler was the key piece to start generating the missing metrics). Perhaps the scheduler was last deployed before the statsD service was online and it gave up trying to communicate with statsD after a while.  Mind checking everything from your side @adamscarberry to make sure everything is there now?

awesome!  Looks good now.

[x] Stable Environment

This appears done to me.  Closing...